From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; .NET CLR 1.1.4322) Description of problem: Will not bot after Kernel update to kernel-2.6.10-1.737_FC3 from kernel-2.6.9-1.681_FC3. Error at boot up is : Kernel Panic - not syncing: driver/ide/pci/piix.c.232: spin_lock (drivers/ide/ide.c:c0364f68) already locked by driver/ide/ide- iops.c/1222 Version-Release number of selected component (if applicable): kernel-2.6.10-1.737_FC3 How reproducible: Always Steps to Reproduce: 1. Load kernel-2.6.10-1.737_FC3 2. 3. Actual Results: Kernel Panic - not syncing: driver/ide/pci/piix.c.232: spin_lock (drivers/ide/ide.c:c0364f68) already locked by driver/ide/ide-iops.c/1222 Expected Results: Should have booted Additional info:
*** Bug 144768 has been marked as a duplicate of this bug. ***
Getting the exact same thing here, except the driver involved is the es1968 driver. It panics during the "Initializing hardware" step. No cut-n-paste log, for obvious reasons. ;-) I'd be happy to supply any additional system information that might be helpful.
Problem solved as of 2.6.10-1.737_FC3; I boot up just fine now.
Updated to kernel-2.6.10-1.741_FC3 and still will not boot.
The same here: almost the same message, but with (drivers/ide/ide.c:c0365448) already locked by driver/ide/ide-iops.c/1222. This is kernel-2.6.10-1.741_FC3. Seems very nasty too me.
Same with kernel-2.6.10-1.750_FC3. Can we make this priority high?
Created attachment 110420 [details] The kernel panic on booting 2.6.10-1.750
The same with 2.6.10-1.760
I get the same problem. similar to: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=145097
I also have the same problem, except it only occurs if a DVD is in the DVD drive on boot up, CD's do not cause a problem. This happens with kernel 2.6.10-1.12_FC2 The DVD is /dev/hda, the Hard Drive is a SATA on /dev/hdc The Message is : remounting root filesystem in read-write mode [OK] kernel panic - not syncing: drivers/ide/pci/atiixp.c:129: spin_lock(drivers/ide/ide.c:c037a5a8) already locked by drivers/ide/ide-iops.c/1222
Having the same problem with kernel-2.6.10-1.14_FC2. It comes right after "Red Hat nash version 3.5.22 starting". Booting with kernel-2.6.9-1.6_FC2 doens't cause any problems. Output was: Kernel panic - not syncing: drivers/ide/pci/piix.c:232: spin_lock(drivers/ide/ide.c:c037a5a8) already locked by drivers/ide/ide-iops.c/1222
As posted on LinuxQuestions.org http://www.linuxquestions.org/questions/showthread.php?s=&postid=1567773#post1567773 I am able to boot with kernel 2.6.9-1.681_FC3 but not any newer versions. If I add the kernel parameter "ide=nodma" and add USE_DMA=0 to /etc/sysconfig/harddisks , the system will boot but my buffered reads off my disk drop to some silly low number of about 3MB/s. Is this bug related? https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=145097
As per the linuxquestions.org link, I posted there that I had this bug hit me on 2.6.10-1.8_FC2 on a E7205 chipset with DupliDisk1 hardware RAID1. Turning off all DMA allowed me to boot OK. The DD1 has always had problems with DMA on most chipsets, but the FC1 kernels would boot and either work with DMA or disable it for me.
I am also seeing this bug. FC3 kernel 2.6.9-1.667 will boot. FC3 kernel 2.6.10-1.770_14.rhfc3.at and FC3 kernel 2.6.11-1.14_FC3 lock after ~2 min. Using 2.6.9 kernel I will see the following message, but the system will operate: timout waiting for DMA drivers/ide/pci/atiixp.c:205: spin_lock(drivers/ide/ide.c:0236e3a8) already locked by drivers/ide/ide-io.c/168 drivers/ide/ide-io.c:186: sin_unlock(drivers/ide/ide.c:0236e3a8) not locked Using the other kernels results in: kernel panic - not syncing: drivers/ide/pci/atiixp.c:109: spin_lock(drivers/ide/ide.c:c03dc408) already locked by drivers/ide/ide-io.c/169. (Not tainted) System specs: ASUS Pundit-R system 250GB Maxtor SATA HDD (model 7y250m0) Glad to provide more info if needed.
Same here as the original poster, but with 2.6.10-1.770. Silicon Image PCI0680 card. Will try now with 2.6.11-1.14
No joy with that kernel, either. Original FC3 2.6.9-1.667 kernel boots fine. Removing my acpi=force on the 2.6.10-1.770 has no effect either. The system remains unusable. I've seen a couple of posts and patches floating around, but am not eager to try them as they're not in bugzilla :-) Given that I really *need* the UATA performance, disabling IDE DMA is just not a workable solution. Reverting to 2.6.9-1.667 kernel until further notice.
[CentOS] Kernel Panic - not syncing: drivers - "Enabling 32 bit mode for the drives in the BIOS cured this problem." http://lists.centos.org/pipermail/centos/2005-April/004831.html Hmm, next opportunity I have, I'll check my BIOS. Not too sure whether I have the luxury or not. Info posted here so others may benefit.
FWIW - moving to kernel 2.6.12-rc3 has resolved the kernel panic issues However, DMA remains off to the DVD drive, resulting in poor DVD performance. enabling DMA on the DVD and accessing results in errors in message log: hda: DMA timeout retry hda: timeout waiting for DMA drivers/ide/pci/atiixp.c:109: spin_lock(drivers/ide/ide.c:c03f11a8) already locked by drivers/ide/ide-io.c/116 drivers/ide/ide-io.c:127: spin_unlock(drivers/ide/ide.c:c03f11a8) not locked hda: cdrom_decode_status: staus=0x51 { DriveReady SeekComplete Error } hda: cdrom_decode_status: error=0x44 { AbortedCommand LastFailseSense 0x04 } ide: failed opcode was: unknown <more errors follow> dma appears to be on for /dev/hdc (main HDD)
I just tried fiddling with /etc/sysconfig/harddisks[aef] with DMA enabled in the kernel but with DMA turned off via these files. Zero effect, still collapses.
Interestingly enough, forcing DMA and other nice stuff in /etc/sysconfig/harddisks causes the errors as seen in comment #19 with a 2.6.9 kernel, but no panic either. (Following settings are through /etc/sysconfig/harddiskhd[aef] /dev/hda (onboard controller) USE_DMA=1 EIDE_32BIT=3 LOOKAHEAD=1 EXTRA_PARAMS="-u1 -k1" /dev/hd[ef] SIL0680 USE_DMA=0 EIDE_32BIT=3 LOOKAHEAD=1 EXTRA_PARAMS="-u1 -k1"
ooh, hda just threw CRC errors. turning off DMA there too :(
Argh, too many kernel/BIOS/system parameters to fully test out. opefully someone from redhat will get around to posting info here.
goes the kernel at http://people.redhat.com/davej/kernels/Fedora/FC3 fix this ?
Ugh, without DMA that took forever to install ;-). At least this is a good reminder to me to place your repo in my yum configs. This message is to let you know I'm taking a look at it. I grabbed the i686 uniprocessor kernel. I'll do some fiddling throughout the day as time allows, and get back to you as soon as I have a reasonable response.
er, in a word. No. Same error as before if booting with DMA. Well, almost the same. Now it tells me: Kernel panic - not syncing: drivers/ide/pci/piix.c:231: spin_lock(drivers/ide/ide.c:c03cef28) already locked by driver/ide/ide-iops.c/1153. (Not tainted)
Might there be any point in trying out the 2.6.11-1.21 kernel you put up on the 29th?
*** Bug 153280 has been marked as a duplicate of this bug. ***
two possibilities.. http://people.redhat.com/davej/kernels/Fedora/FC3/ hsa the next 2.6.11 based test kernel http://people.redhat.com/davej/kernels/test/ has a more experimental backport of the FC4 kernel to FC3. (Though this has had little to no testing at all yet, so be careful). Both of these have numerous IDE layer fixes, so I'm interested to hear feedback how they behave.
I've just tried the 2.6.11-1.27_FC3 kernel, boots fine. I want to leave it run for 24 hours to rough-check stability, then I'll give your test kernels a spin around the park.
both the .27 and .33 kernels seem to get stuck in a infinite loop panic after an unknown period of time.
I had to reinstall both FC3 and FC4t3 (different discs - same computer) Before the reinstall, both would boot with the latest kernels, Now, neither will boot with the 2.6.11 kernel. The FC3 install will boot with the "original" kernel provided with the iso set. The FC4 cannot even be installed because the kernel panics during the setup. Any suggestions?
I just saw this while installing FC4 to an old PC. Started out as a panic whenever I tried to access /dev/hdc (didn't save the syslog, sorry). Rearranged drives/cables and got this: Kernel panic - not syncing: drivers/ide/pci/piix.c:232: spin_lock (drivers/ ide/ide.c:c03de668) already locked by drivers/ide/ide-iops.c/1235. (Not tainted) Setup that caused errors on /dev/hdc: Primary IDE controller: (80-conductor cable) Master device: 8GB boot drive (Quantum Fireball) Slave device: 200GB storage drive (Seagate Barracuda 7200-7) Secondary controller: (40-conductor cable) Master device: 200GB storage drive (Seagate Barracuda 7200-7) Slave device: CD-ROM (Dell OEM) Setup that caused panic on boot: Primary IDE controller: (40-conductor cable) Master device: 8GB boot drive (Quantum Fireball) Slave device: CD-ROM (Dell OEM) Secondary controller: (80-conductor cable) Master device: 200GB storage drive (Seagate Barracuda 7200-7) Slave device: 200GB storage drive (Seagate Barracuda 7200-7) I replaced the 40-wire IDE ribbon cable, and the problem went away. If you're seeing this, check your cables!!
Still happens with 2.6.12-1.1387_FC4 (on an old Asus P2L97 mainboard with Intel 440LX chipset)
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which may contain a fix for your problem. Please update to this new kernel, and report whether or not it fixes your problem. If you have updated to Fedora Core 4 since this bug was opened, and the problem still occurs with the latest updates for that release, please change the version field of this bug to 'fc4'. Thank you.
After updating to 2.6.12-1.1372_FC3 the problem has been fixed on my machine. Thank You!
Hi Dave, Saw the release notes, and installed the kernel earlier today. I did not update #30, as I experienced similar to #31. I'll try and get a 7 day uptime before upadting, but at least it's booting without warnings. If I forget to update this, assume all is fine ;-)
After updating to Kernel 2.6.12-1.1372_FC3 it now boots. The only error I am seeing at boot is just after: Red Hat Nash version 4.1.18 starting target0:0:3: Domain Validation detected failure, dropping back target0:0:3: Domain Validation detected failure, dropping back target0:0:3: Domain Validation detected failure, dropping back
This latest 2.6.12-1.1372_FC3 appears to solve the problem for us. I can boot it with or without ide=nodma and it boots. No panic/spinlock like before. Bug appears to be fixed. (DMA still doesn't work with our DupliDisk1, but that's another story and not necessarily (in fact almost definitely not) linux's fault.)
This broke our default config, whatever you did in the last couple of days within the FC3 train, it boots fine on the normal kernel that comes with the ISOs but when we run yum update and we grab the new kernel it gives us a kernel panic when it boots... we have about 60 or so servers running in a cluster on this config :D
You sure you aren't getting hit with bug #163437? That's separate from this bug. Make some noise on the now very popular 163437.
Been a few days. I've driven the system pretty hard. I'm happy. As far as I'm concerned, this is closed for me.
After 2.6.9_981, 2.6.12-1.1372_FC3 is the first kernel that seems to be working properly on my PC. My hardware is PIII and 810e chipset motherboard. I could not install FC4 on this hardware because of kernel panic during installation due to syncing problem. How can i modify FC4 ISO to include FC4 version of this kernel so as to install FC4 on this hardware.
(In reply to comment #43) > After 2.6.9_981, 2.6.12-1.1372_FC3 is the first kernel that seems to be working > properly on my PC. My hardware is PIII and 810e chipset motherboard. I could not > install FC4 on this hardware because of kernel panic during installation due to > syncing problem. How can i modify FC4 ISO to include FC4 version of this kernel > so as to install FC4 on this hardware. It is 2.6.9-1.681_FC3, not 2.6.9_981
This issue should be fixed in the latest errata, please open new bugs for any of the other issues (or add comments to existing bugs). Thanks.