kernel: Uhhuh. NMI received for unknown reason...

[darrell pfeifer]

On Mon, Mar 10, 2008 at 2:18 PM, Dave Airlie <airlied at redhat.com> wrote:
> On Mon, 2008-03-10 at 14:11 -0400, Alan Cox wrote:
>  > > Hence logic says that something that is being change between kernels
>  > > are causing this otherwise the kernel would ALWAYS being reporting
>  > > this...
>  >
>  > Unlikely - hardware problems are often dependant on alignment of objects
>  > and other chance happenings. If you've got bad RAM and the faulty bits happen
>  > to land in a location where the faulty bits don't show a fault (its often
>  > combination based) you'll see exactly what is described.
>  >
>  > > If anyone can tell me how I can *debug* it further
>  > > I'm all ears..
>  >
>  > memtest86 full night run is what I usually start with for such cases.
>  >
>  >
>
>  I've seen this problem on a Dell Insprion 6000 as well, its definitely a
>  machine problem as opposed to a bad RAM case... I've never tracked down
>  what triggers it though... it may be heat related ...
>

I have a Dell Inspiron 9300. A few months ago the NMI problem suddenly
appeared and was happening almost daily. I update from Rawhide pretty
much daily and after a week or so the problem disappeared.

After today's kernel update

2.6.25-0.113.rc5.git2.fc9

the problem reappeared (so much for taking pleasure in the misfortune
of others, sigh)

I'm also more inclined to think that it is a driver problem rather
than a hardware problem.

darrell