[Bug 565172] Re: BUG: unable to handle kernel paging request at f76ff01c

[crazybyte]

The problem is that I tried Lucid kernel before this, because initialy I used Karmic (after almost  2 years of Hardy  without any  such oopses) and seeing this I upgraded to Lucid hoping that the bug will go away.
On Lucid with the 2.6.32 (I don't know the exact sub version, but I remember that was the version that came with Lucid Beta 2)  I had the same issue (after that I switched back to Karmic until Lucid becomes production worthy). 
I first thought that the culprit is apparmor but deinstalling it didn't change anything so after using ksymoops I saw that there are a lot of errors concerning APIC so I tried to use noapic option in the kernel command line. That seems solves the issue momentarily(I'm running the laptop last two days with this option without any problems) so I'm using it as a workaround for now. The above bug report was done when I quit using the noapic option to see if that was what it momentarily solved the issue.

On Hardy I also had some issues (not linked to Ubuntu, because the same
bug appeared on other distros too) due to some buggy BIOS data that
caused the kernel to wrongly setup the CPUs (related to C3 state) which
caused a full freeze on boot. That I solved using the idle=mwait option
in kernel command line. I saw that this issue was solved in the Karmic
and Lucid kernels. I think that the issue I'm experiencing now is
somewhat related to that (to the bad BIOS data) but I'm not sure. Also
I'm not entirely sure what the noapic option does beside disabling the
use of the APIC (what subsystems or components are disabled).

@John Johansen: If you think that the 2.6.32-21 kernel could possibly
solve the issue I will try it and dual boot.

Thanks!

-- 
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 Kernel
Bugs, which is subscribed to linux in ubuntu.