The other thread isn't a kernel panic. The first line of the call trace says "warn_alloc_failed" if it's nothing to worry about, but "panic" if it is. This says "panic".

There's normally a lot more after this in the dump, particularly a Mem-Info section. That will determine, at a glance, if it's an actual bug or if you're just running out of memory. (Free swap = 0kB means you ran out of memory.)

_________________

/* TODO: need to add signature to posts */

What should I do to prevent this panic?

Oops...must learn to read posts fully

_________________
Paid support
How to ask for help
1. Give details of your problem
2. Post any errors
3. Post relevant logs.
4. Don't hide details i.e. your domain, it just makes things harder
5. Be polite or you'll be eaten by a grue

How can I eliminate this? I'm sorry still new to this OS.

What does the rest of the panic say? You might need to use the 'logview' command from the Linode LISH shell to do it (not your system's console):

ssh linodexxxxx@citynameyyy.linode.com logview
Password: (your LISH password, set on the Remote Access page)

I'd bet a substantial portion of the cash in my wallet it will say "Free swap = 0kB" in there. If so, you're running out of memory. I'd also bet on Apache and PHP being involved... if you're using PHP-related stuff and Apache, check your apache2.conf's MaxClients setting in the mpm_prefork section. If it's greater than about 25 or so, you're likely to have a bad time.

(The default is 150, for reasons we'll chalk up to naive optimism guarded by a fierce bureaucracy.)