Red Hat Bugzilla – Bug 187608
BUG: Spinlock recursion on CPU #0
Last modified: 2015-01-04 17:26:26 EST
kernel-smp-2.6.16-1.2069_FC4 on a Dual Opteron machine. See bug 179272 for detailed hardware info. While attempting to find a workaround for bug 179272, I booted the kernel with "noacpi pci=noacpi" arguments. The kernel seem to boot past the point where it normally hits bug 179272, but then a short time later it halts with this bug. The console output was short enough for me to copy down by hand. This is the only diagnostic that came up on the console: Starting kernel logger: BUG: spinlock recursion on CPU #0, swapper/0 (Not tainted) lock: ffff81007f6d8340, .magic: dead4ead, .owner: swapper/0, .owner_cpu: 0, kernel panic - not syncing: bad locking I tried to attach a serial console in other to capture the entire boot process, but when I did that, booting with the console on ttyS0 @ 9600bps triggers bug 179272 before the kernel hits this bug.
[This comment added as part of a mass-update to all open FC4 kernel bugs] FC4 has now transitioned to the Fedora legacy project, which will continue to release security related updates for the kernel. As this bug is not security related, it is unlikely to be fixed in an update for FC4, and has been migrated to FC5. Please retest with Fedora Core 5. Thank you.
A new kernel update has been released (Version: 2.6.18-1.2200.fc5) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. In the last few updates, some users upgrading from FC4->FC5 have reported that installing a kernel update has left their systems unbootable. If you have been affected by this problem please check you only have one version of device-mapper & lvm2 installed. See bug 207474 for further details. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. If this bug has been fixed, but you are now experiencing a different problem, please file a separate bug for the new problem. Thank you.
This bug has been mass-closed along with all other bugs that have been in NEEDINFO state for several months. Due to the large volume of inactive bugs in bugzilla, this is the only method we have of cleaning out stale bug reports where the reporter has disappeared. If you can reproduce this bug after installing all the current updates, please reopen this bug. If you are not the reporter, you can add a comment requesting it be reopened, and someone will get to it asap. Thank you.