Bug 47816 - Installer hangs when loading megaraid module
Installer hangs when loading megaraid module
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
7.1
i686 Linux
medium Severity high
: ---
: ---
Assigned To: Arjan van de Ven
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-07-07 16:15 EDT by Jason Watson
Modified: 2007-04-18 12:34 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-06-06 10:21:29 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jason Watson 2001-07-07 16:15:59 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)

Description of problem:
Tried running install of RH 7.1 on a C440GX+ and a L440GX+ (both running 
dual processor) with a AMI Megaraid 1200 (428) and a Express 200 (466).  
VC4 will show a SCSI timeout error after it tries to scan the channel (or 
in the 428's case, the first channel) for devices.  Installer will refuse 
to continue afterwards.  Worked fine with RH 7.0 and upgrade to kernel 
2.4.5.  Tried text, expert and both boot images from CD and floppy.

How reproducible:
Always

Steps to Reproduce:
1.Run the installer on a L440GX+ or C440GX+ and a Megaraid card
2.Installer will hang on running insmod on the megaraid driver
3.
	

Actual Results:  Installer hung.  VC4 reported a SCSI timeout error after 
trying to scan the first channel or only channel.

Additional info:
Comment 1 Need Real Name 2001-07-10 16:14:04 EDT
Same bug encountered with AHA274x/284x/294x driver for the AIC-7896/7 Ultra2 
SCSI host adapter. The Install simply hangs when trying to insert the module, 
indicating SCSI timout.
Comment 2 Matt Wilson 2001-07-10 17:16:33 EDT
looks like kernel apic bug
Comment 3 Arjan van de Ven 2001-07-10 17:24:42 EDT
Please try booting with "noapic" on the syslinux prompt; that might just help.

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