Bug 8043

Summary: Upgrade selects wrong SCSI module - after restart, kernel panic
Product: [Retired] Red Hat Linux Reporter: jkarun
Component: installerAssignee: Michael Fulbright <msf>
Status: CLOSED WORKSFORME QA Contact:
Severity: high Docs Contact:
Priority: medium    
Version: 6.1   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-06-12 18:05:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description jkarun 1999-12-29 14:23:36 UTC
While upgrading from version 5.2 to 6.1 I experienced the following bug:

I have an Adaptec 2920 scsi card which, of course, requires aic7xxx.o to
run.  The install/upgrade program detects the right board and loads the
driver appropriately.  However, for some reason, the install program places
the aic151 module in conf.modules and consequently gets the wrong driver
built into the ramsdisk.  When my server restarted I could see the scsi
driver failing to load and, of course, kernel panic.  I have been able to
work around this problem by putting the right entry in conf.modules during
the install program (escaping to console, copying file to another machine
and editing - a long process, especially if the local filesystems are not
mounted)

Thanks - I hope I provided you with good information

Comment 1 Derek Tattersall 2000-04-25 18:21:59 UTC
Unfortunately, we don't have a 2920.  Itried with a 2940 which uses the same
aic7xxx driver.  I installed 5.2, then upgraded to 6.1 and had no problems.  I
also installed 5.2 and upgraded to 6.2 and had no problems.  conf.modules was
correct each time.