kernel BUG at /build/buildd/linux-2.6.24/debian/build/custom-source-rt/kernel/rtmutex.c:692!; EIP is at rt_spin_lock_slowlock+0x127/0x170

[Dmitriy Geels]

I got this crash twice since updating kernel to 2.6.24-17.
First time crash was really sudden, second time -- compiz crashed, then when I tried to run apport-cli, it crashed and left some backtrace (lost already), then, after about one minute, got kernel crash.

Crash looks like: screen flickers few times, then become blank/with some garbage. System doesn't respond to keyboard. Didn't try to connect via ssh, but I don't think, it's possible.

After reboot I looked into logs: there were only few lines, telling about BUG in rtmutex.c (see attached crash.log).

Also including almost all info, specified in Kernel Team Bug Policies.

[Dmitriy Geels (dmig)]

Just caught this crash with 2.6.24-18-rt
Now much more debug info

[Dmitriy Geels (dmig)]

Just caught a crash with 2.6.24-19-rt. Now without any information in logs about this crash (may be just lost in FS?).

[Dmitriy Geels (dmig)]

Again crash on 2.6.24-19-rt, now with death log.

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Dmitriy Geels (dmig)]

Leann, I'd like to install kernel 2.6.27 package for Hardy. Is it available?

[Leann Ogasawara (leannogasawara)]

Hi dmig,

The 2.6.27 kernel is available in the Intrepid repository. Unfortunately I don't think the -rt flavor is available yet for testing.

[Julian G. (julian-galbraith)]

Hi. I encountered a similar situation.
The 2.6.27-3-rt kernel randomly freezes. The generic is O.K.
The system is a bone stock Dell Dimension 5150.

Need any information?
Ubuntu 8.10 32bit

[Dmitriy Geels (dmig)]

I'll tell you how to get freeze info: after reboot look into system logs (gnome-system-log is good for this), find place where system was running before freeze, there should be some last words of kernel.

[Julian G. (julian-galbraith)]

The system completely locks up generally within 15 minutes while using the rt kernel, screen, keyboard, mouse. I dont see any information in the logs that could assist.
I am attaching everything I have for the past few days.
Some of the logs are for the generic kernel which appears to be operating flawlessly.

My first assumption after doing a bit of reading is that it is a bug related to a combination of the rt kernel and the intel 945 xorg video driver.
00:02.1 Display controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02)

I will test using the vesa driver and the rt kernel when I get a chance and see if the bug reproduces itself still.

[penalvch (penalvch)]

Dmitriy Geels, thank you for reporting this and helping make Ubuntu better. Hardy desktop reached EOL on May 12, 2011.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue on a supported release? If so, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in a supported release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]