Comment 13 for bug 116752

Revision history for this message
Manuel (manuel-schulte) wrote : Re: Uhhuh. NMI received for unknown reason a0 on CPU 0

Hi all,

I have an Acer Aspire 1802WSMI, 2Go RAM, ATI X600 Mobility, Wifi (NDISWrapper), Pentium 4 HT 3.0GHz, Ubuntu Feisty.

I had the same problem; Although freezed (as described in previous posts) sometimes the computer was still remotely (ssh...) accessible sometimes not.

Though it did not entirely solved the issue, this helped:
1/ add kernel directive "noapic" in the kernel's startup options (/boot/grub/menu.lst).
2/ stop using Beryl...

Since I did 1/; the problem never occurred when not running Beryl!!!
When using Beryl, it still occurs, but far less frequently.

SIDE EFFECT: sometimes, the synaptic hardware (touchpad & laptop's keyboard) do not initialise properly at boot time! As a result, I end up in front the GDM screen without being able to log in or do anything whatsoever (no keyboard). Luckily, as I'm using an external usb mouse, I still have some control and I'm able to reboot. Note that sometimes I need to do it several times before it succeeds to initialise the synaptic hardware... This problem occurs almost systematically when I have my external usb HDD connected to the laptop. Unplugging the HDD helps reducing the frequency of this nasty side effect.
For now I live with this problem because I prefer it to random freezes...

Hope this will help.
Cheers,
Manu