Red Hat Bugzilla – Bug 165538
PIIX locking [OLDIDE]
Last modified: 2012-06-20 12:01:20 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr-FR; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Description of problem:
when i install RHEL 4 AS and install all package , after reboot of system
Grub try to load the system , but i got i message Error :
Uncompressing linux....OK,Booting the kernel.
Red hat nash version 4118 starting
kernel panic - not syncing :drivers :drivers/ide/pci/piix.C : 390 : spin_lock(drivers/ide/ide.c / 036b8e8) already locked by drivers /ide/ide-iops.C/1234
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.if fact i don't want to scratch my installation so i will not touch the system until i will find a possible solution
Expected Results: my rhel should run well :)
"kernel panic - not syncing :drivers "
Try booting to the UP kernel and upgrading to the kernel.
i don't think it's a good idea , i need in fact to use a 2.4.X kernel ; but when
i try to boot with rescue mode and have a shell to access to the system ,
command like up2date did work proprely...
is there somone ! up there?
You installed RHEL4, not RHEL4 U1? Also what kind of machine is it?
yes i installed RHEL4 it's a HP pc :
I'm somewhat confused as to why you don't want to scratch your
installation when it sounds like it never actually booted? If at all
possible, I would suggest installing RHEL4 U1, or waiting for RHEL4 U2,
rather than using RHEL4 GA, in case this is not hardware specific and
has already been resolved.
That hardware does not show up in our certification page
(https://hardware.redhat.com/hwcert/index.cgi), so it may not be supported
by Red Hat. As this seems to be an urgent thing, you might be best off
going through our support. In order to file a support issue, please
either contact Red Hat's Technical Support line at 888-GO-REDHAT or file
a web ticket at http://www.redhat.com/apps/support/. Bugzilla is not an
official support channel, has no response guarantees, and may not route
your issue to the correct area to assist you. Using the official support
channels above will guarantee that your issue is handled appropriately
and routed to the individual or group which can best assist you with
this issue and will also allow Red Hat to track the issue, ensuring
that any applicable bug fix is included in all releases and is not
dropped from a future update or major release.
ok thanks to have answer ; i think that i'm going to try RHEL4 U/U2
any luck with U2?
nop i had hope to switch to U2 .U2 have the same problem ...
so i use RHEL 3 and it work like a charm
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life.
Please See https://access.redhat.com/support/policy/updates/errata/
If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.