darrell pfeifer wrote:
On Mon, Mar 10, 2008 at 2:18 PM, Dave Airlie <airlied@xxxxxxxxxx> 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
could take a look at the running temperature on the laptop
when it's reporting this..
( confirming or not confirming it could be heat related.. )
Best regards
Johann B.
begin:vcard
fn:Johann B. Gudmundsson
n:Gudmundsson;Johann B.
org:Reiknistofnun - University of Iceland;IT Management
adr:Dunhagi 5;;Taeknigardur;Reykavik;;107;Iceland
email;internet:johannbg@xxxxx
title:Unix System Engineer RHCE,CCSA
tel;work:+3545254267
tel;fax:+3545528801
tel;pager:N/A
tel;home:N/A
tel;cell:N/A
url:http://www.rhi.hi.is
version:2.1
end:vcard
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
