I've been having the same problem using the latest kernel, 2.6.32-24. I don't have issues with the mainline kernels and I didn't have this problems with earlier versions of Ubuntu (I've run every version since 6.06 on this hardware). It could be hardware related as the newer kernels (in mainline) report corrupted low memory and as I understand they work around it. I only get the Oops after having resumed from S3 and it begins with the line "BUG: unable to handle kernel paging request at f76f0004".
I did get an unbootable system one time, where it complained about not being able to find init during startup. I had to run a rescue disk and fsck the fs (ext4) to fix it. Before the boot attempt, the system had put the root fs into readonly mode. I thought this might be the cause and if it was, that should influence its severity. I'm attaching the output from the last Oops. My root filesystem went to readonly mode so I got the report with dmesg | ssh remotehost "cat > oops.txt" -Randall ** Attachment added: "Kernel Oops Output" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/565172/+attachment/1571959/+files/fs_errors.txt -- BUG: unable to handle kernel paging request at f76ff01c https://bugs.launchpad.net/bugs/565172 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
