This might be upstream problem, but since I'm using gentoo-sources and I'm not sure in what they exactly differ from vanilla, I'm posting it here. Please, tell me if it should be reported to upstream. I have an x60s laptop with up-to-date ~x86 Gentoo. (more hw info attached) Kernels starting from 2.6.34 crashes in random time after boot (even if idle). After a few hours (it happend today after 7-8 hours) my machine is locked up and does not react on anything (except power-off button pushed for a few seconds...). So I set up network console on another computer and logged it all there (don't have serial and don't think USB converter is so much better than network). I received: [21067.404724] Uhhuh. NMI received for unknown reason b1 on CPU 0. [21067.404724] You have some hardware problem, likely on the PCI bus. [21067.404724] Dazed and confused, but trying to continue And then nothing. This happend only with 2.6.34 kernels (an newer, this was captured with 2.6.35-r2 from portage). With my 2.6.33-r2 everything works, I've tried for several days and it didn't crashed. Note that I've been experiencing strange problems with my temperature sensor - it seems to be sometimes mistaken and thinks my cpu is really hot - 126 deg. C (which is way too much for my Core1Duo, Yonah, L2400) and just shuts itself down (with proper message in syslog). Could this be related or is it just a coincidence? I don't remember this happening with 2.6.35, but I don't use it enough to notice it. Well, I know this isn't much to work with, but I don't know what else could be done (except bisecting kernel, which is way too much work because of the relatively long time between the bug appears). If you need more info, just tell me how to get it and I'll do it. Reproducible: Always
Created attachment 244283 [details] emerge --info
Created attachment 244285 [details] gentoo-sources-2.6.35-r2 config
Created attachment 244287 [details] gentoo-sources-2.6.33-r2 config
Created attachment 244289 [details] lspci output
Created attachment 244291 [details] lspci -v output
I've just tested with latest vanilla kernel from git and it happened too (even a lot sooner).
I don't know if you've seen it, but d2_racing's post here: http://forums.gentoo.org/viewtopic-p-4833359.html?sid=54fe6c4f345fcd73e8610e21755441c7 at Wed Feb 06, 2008 11:25 pm, seems interesting since you share the same wireless NIC.
I've seen it but doesn't fit. My problems started only with 2.6.34 - this thread is two years old and about 2.6.24 kernel. Another thing is that in all test cases my wireless card is off (rfkilled, so the driver should be inactive). Nevertheless, it's worth a try. In the mean time, I've started bisecting the kernel, but it will take at least a week to finish..
Same for me. This bug is dup of 328889 . And blocks 317231 . Please update status.
Ladislav, Can you please test with gentoo-sources-2.6.34-r6. It has fixes in for crashing and I want to see if this fixes your issue.
Compiling now, will post more info in a day or so (depends on the result).
Nope, 2.6.34-r6 still freezing. I wonder, if you meant 2.6.35-r6? I'll try and see.
Running 2.6.35-gentoo-r5 for a day and so, and no freez yet. Seems to be fixed between -r2 and -r5.
