Red Hat Bugzilla – Bug 183211
Panic on mount with rescue CD
Last modified: 2007-11-30 17:07:23 EST
Description of problem:
When using the installation CD in an attempt to recover a crashed machine, the
kernel panics on attempting to read the machine's hard disk.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot from installation CD
2. Mount hard drive
3. Read hard drive
Able to read and modify data on disk
This happens with RHEL 4 CD1, for the original release CD, Update 2, and the
latest beta of Update 3.
The error message (using rescue mode, though this happens on attempts to do an
upgrade install too) is:
sh-3.00# Kernel panic - not syncing: drivers/ide/pci/piix.c: 394: spin_lock
(drivers/ide/ide.c: c037bb68) already locked by drivers/ide/ide_ops.c/1234
with Update 2 - with the original disk set, it is:
sh-3.00# Kernel panic - not syncing: drivers/ide/pci/piix.c: 390: spin_lock
(drivers/ide/ide.c: c036b8e8) already locked by drivers/ide/ide_ops.c/1234
and with the beta of U3 it's:
sh-3.00# Kernel panic - not syncing: drivers/ide/pci/piix.c: 396: spin_lock
(drivers/ide/ide.c: c037dd68) already locked by drivers/ide/ide_ops.c/1234
This bug is not found when using the Fedora Core 3 or 4 (release) CDs.
Hardware is a Super Micro P6SBA motherboard and a Seagate ST340015A hard disk
and a CDR-8428B CD-ROM.
not sure who does ide bugs...
Created attachment 129606 [details]
patch submitted to rhkernel-list
committed in stream U5 build 42.5. A test kernel with this patch is available
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
QE ack for 4.5.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.