[intrepid] WARNING while booting 2.6.27 on Thinkpad X300

[Chris Jones]

While booting intrepid's 2.6.27 kernel on my Thinkpad X300, I get the attached OOPS. The kernel does not panic, and the system continues to boot apparently normally (although I am seeing crashes from screensaver activity, but I cannot be sure if they are directly related and will be filed separately).

[Chris Coulson (chrisccoulson)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.

Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
4. Could you please say whether this happened in kernel 2.6.26, or does it only happen with 2.6.27?

For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance!

[Chris Jones (cmsj)]

-(cmsj@kodachi)-(~)- uname -a
Linux kodachi 2.6.27-1-generic #1 SMP Sat Aug 23 23:20:09 UTC 2008 i686 GNU/Linux

[Chris Jones (cmsj)]

lspci requested

[Chris Jones (cmsj)]

I did the upgrade to intrepid after 2.6.27 went into the archives, so I don't know if it happened with .26

[Chris Jones (cmsj)]

http://kerneltrap.org/mailarchive/linux-kernel/2008/6/17/2155814/thread seems like it might be relevant

[Chris Jones (cmsj)]

similarly http://groups.google.com/group/linux.kernel/browse_thread/thread/c1758d21407c221e/ae795f823f0097c7?lnk=raot

[Chris Jones (cmsj)]

and just because I haven't spammed this bug enough yet, I think this might be the most relevant, but there seem to be quite a few OOPSes out there which are similar to this one. It does seem to be drm related though.

http://kerneltrap.org/mailarchive/linux-kernel/2008/7/25/2677834/thread

[Brian Murray (brian-murray)]

This is actually a warning not an Oops:

WARNING: at /build/buildd/linux-2.6.27/kernel/softirq.c:136 local_bh_enable_ip+0x68/0xa0()

[Chris Coulson (chrisccoulson)]

Chris - You reported this with kernel version 2.6.27-1. Would you mind trying with the latest Intrepid kernel (2.6.27-4) to see if this is still an issue? Thanks

[Chris Jones (cmsj)]

This no longer seems to appear with 2.6.27-4

[Chris Coulson (chrisccoulson)]

Thanks for the feedback