Summary: | lm-sensors causes Oops when inserting w83871d module | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Axel Reimann <axel.privat> |
Component: | Current packages | Assignee: | x86-kernel (DEPRECATED) <x86-kernel> |
Status: | RESOLVED INVALID | ||
Severity: | critical | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | ksymoops output |
Description
Axel Reimann
2004-01-09 13:26:29 UTC
Can you please emerge ksymoops, and do: ``ksymoops < file_with_OOPS > file_out'' on the kernel which is causing this and paste file_out into this bug? file_with_OOPS should contain the stack data from your initial post. Created attachment 23535 [details]
ksymoops output
ksymoops output
Ok, I did as you said (see attachment above). Even though I saw ksymoops output for the first time, it looked rather dubious to me (lots of warnings). Therefore, I decided to reboot the box in order to reproduce the error and have a clean syslog to begin with. Funny thing: This error is NOT reproducible. I've rebooted a couple of times now, and everytime lm-sensors started (and worked) as advertised. Side note: Tonight the automated update has updated a couple of packages and init scripts on this box. So, while this mysteriously fixed my problem, I now caught bug #37375, but that's a different story... If no one else encountered my problem, I apologize for wasting your time. The good thing is, however, that next time I'll report a kernel hickup, I know now right away how to use ksymoops to make it more useful. Thank you for helping me out! Those warnings may be the reason you got the OOPS - the symbols don't match for some reason in the running i2c-core and the one you have on disk - which may explain why it OOPSes as it can't manage to cooperate. Not sure how it randomly fixed itself, though. I'm resolving this as INVALID, if you get this again, please reopen this bug. |