Indeed, I checked the logs and that's how I came to realize it was a kernel
update that caused problem. Thanks for the quick response!
>
> Can you look in /var/log/messages for the first 'oops' message? It will
> include the text 'Not tainted' rather than 'Tainted: G D'.
>
>
Here is what I found, let me know if I can do anything else:
*pde = 01420067 *pte =
Sep 8 14:34:58 doodad kernel: [ 175.244960] Modules link
Updating that I managed to flop around like a noob and still install the
linux-image-3.0.0.1-686-pae package to upgrade my kernel and it seems to
have fixed the problem. I don't know how to troubleshoot the original
problem, but if you need me to run any other diagnostics, I can still boot
into the
Package: linux-2.6
Version: 2.6.32-35squeeze1
Severity: important
I get a kernel oops at various random times with Google Chrome.
One other distro had similar problems that I could find:
https://bugzilla.novell.com/show_bug.cgi?id=693382
I'm not sure what else to include, but the kernel log is
4 matches
Mail list logo
