Bug 11179 - Kernel Panic with Dell Dual channel and Quad channel controller together
Summary: Kernel Panic with Dell Dual channel and Quad channel controller together
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kudzu   
(Show other bugs)
Version: 6.2
Hardware: i386 Linux
Target Milestone: ---
Assignee: Matt Wilson
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2000-05-02 16:03 UTC by Brian Highers
Modified: 2008-05-01 15:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-06-22 19:55:31 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Brian Highers 2000-05-02 16:03:33 UTC
If you install with the Dell Dual channel and the Dell Quad channel
together, and the you install the OS to a disk controlled by either one of
these controllers, you will receive a kernel panic when the system
reboots. After further examination we notice that the initrd is not being
created in /mnt/sysimage/boot.  If you perform the same install with two
of the quad channel controllers or two of the dual channel controllers the
problem does not occur.  It is only a problem with one of each together
during install.

Comment 1 Jay Turner 2000-05-03 14:06:59 UTC
This issue has been sent up the chain at Dell and they, along with AMI are
taking a look at this.  Red Hat does not have the hardware in-house, so we will
wait to hear from Dell/AMI.

Comment 2 Tesfamariam Michael 2000-05-18 15:48:59 UTC
There is an updated kudzu RPM that fixes this problem which can be downloaded
from http://people.redhat.com/notting/kudzu/
Another work around to this problem is to go to the bash shell after
installation is completed but before exiting, get to root mode, comment out the
line 'alias scsi_hostadapter* unknown', make the initrd.img and updating lilo

Comment 3 Bill Nottingham 2000-06-26 16:21:35 UTC
Closing, as this particular bug was fixed in the kudzu currently
in rawhide.

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