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

"Jóhann B. Guðmundsson" johannbg at hi.is
Mon Mar 10 17:12:59 UTC 2008


Lubomir Kundrak wrote:
> On Mon, 2008-03-10 at 14:04 +0000, "Jóhann B. Guðmundsson" wrote:
>   
>> This has been going on of depending on kernels shipped with FC6-8 I 
>> noticed it...
>> ( HW: Dell inspiron 6000 ) ( yes with the latest kernel FC8 )
>>
>> Uhhuh. NMI received for unknown reason bX on CPU 0.
>> You have some hardware problem, likely on the PCI bus.
>> Dazed and confused, but trying to continue....
>>
>> Can we fix this messages somehow it's kinda misleading, it
>> suggest that the hw is failing when in 99% it's a buggy driver..
>>
>> When I read "You have some hardware problem" I think
>> my hardware is failing and I need to backup my data
>> and replace the part that is failing....
>>
>> Better would be..
>>
>> Uhhuh. NMI received for unknown reason bX on CPU 0.
>> I have been feed [ driver X ] buggy driver ...
>> Dazed and confused, but trying to continue....
>>     
>
> Why do you think it is a faulty driver? For me it seems that most
> obvious reason for triggering a NMI is a buggy hardware.
>
>   
I think it's a faulty driver because it varies on which kernel
i'm running  whether  I see this in my logs or not FC-6 - FC-8.....

Hence logic says that something that is being change between kernels
are causing this otherwise the kernel would ALWAYS being reporting
this...

The first time I saw it was when I made some custom kernel with hacks
to get better dvd playing experince in FC5 ( dvd playback was lagging )
When I ran the stock kernel in FC5 I did not receive the message..
 
Also see  https://bugzilla.redhat.com/show_bug.cgi?id=213227
Follow the Ubuntu links as well..

If this error is accurate, as in a buggy driver/wrong driver being used
( hardware configuration error ) which behaves similar but not exactly 
the same
( then the detection process on which driver to use is buggy ) cant 
cause this error
( trigger false signals on the NMI circuitry )
then ok I need to replace my hardware..

But if it can the msg needs rewriting...

If anyone can tell me how I can *debug* it further
I'm all ears..

Best regards
                   Johann B.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: johannbg.vcf
Type: text/x-vcard
Size: 380 bytes
Desc: not available
Url : http://lists.fedoraproject.org/pipermail/devel/attachments/20080310/0f89c94c/attachment-0002.vcf 


More information about the devel mailing list