Bug 174274 - Kernel panic - not syncing spin_lock on boot
Summary: Kernel panic - not syncing spin_lock on boot
Status: CLOSED DUPLICATE of bug 169613
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 4
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2005-11-27 02:05 UTC by Tim Charman
Modified: 2015-01-04 22:23 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-12-10 06:16:26 UTC
Type: ---

Attachments (Terms of Use)

Description Tim Charman 2005-11-27 02:05:54 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4

Description of problem:
On boot, right after uncompressing linux, get the following:

kernel panic - not syncing: drivers/ide/pci/piix.c:232: spin_lock (drivers/ide/ide.c:c03eb708) already locked by drivers/ide/ide-iops.c/1235 (not tainted)
BUG: soft lockup detected on CPU#0!

The boot then hangs.  Work around: set ide=nodma in the boot string, but most things appear slow with this setting.  Makes system almost unusable.

IDE devices - 1x160Gb ATA HD with boot block & Windows, 1x80Gb ATA HD with Linux (FC4, kernel version 2.6.11-1.1369_FC4), 1xCDRW, 1xDVDRW.  Made sure to try booting with nothing in CDRW and DVDRW.  Same error each time tried (about 6 times) without the ide=nodma setting.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Boot
2. Wait (not very long)


Additional info:

Comment 1 Dave Jones 2005-12-10 06:16:26 UTC
This was fixed in a later update kernel.    If you're seeing this during the
installation, there's not a workaround for this problem.

The bug I'm duping this against has pointers to an unofficial FC4.2 which has
this fixed. If for some reason you can't get that to work, FC5test1 is your best

*** This bug has been marked as a duplicate of 169613 ***

Note You need to log in before you can comment on or make changes to this bug.