Bug 59710 - SCSI timeout before going to partition screen during install
Summary: SCSI timeout before going to partition screen during install
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 7.3
Hardware: i686
OS: Linux
high
high
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-02-12 00:10 UTC by Danny Trinh
Modified: 2005-10-31 22:00 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-02-12 20:41:44 UTC
Embargoed:


Attachments (Terms of Use)

Description Danny Trinh 2002-02-12 00:10:34 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows 98)

Description of problem:
When i select manually partition HDD, I got blue screen. I switch to VC4 and 
saw that aic7xxx driver is trying to load HDD information but not successful. 
VC4 generates the following messages:
<4> SCSI host 0 reset (pid 247) timed out - trying harder
<4> SCSI bus is being reset for host 0 channel 0.


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.Remove ROMB by using BIOS setup on PE2550
2.Boot from Hampton beta1 CD, and select text mode
3.At the screen to choose autopartition, select manually partition. I'm sure 
this also happens on autopartition too.
4.You will see a blue screen with nothing, switch to VC4 and you will see the 
timed out error.
	

Actual Results:  Can't not install Hampton.

Expected Results:  Must be able to install Hampton on this PE2550.

Additional info:

I know that these HDDs and PE2550 system are good, because I have done RH7.2 on 
this system last week.

Comment 1 Michael Fulbright 2002-02-12 17:49:11 UTC
Matt does this sound like a kernel issue?

Comment 2 Matt Wilson 2002-02-12 20:41:14 UTC
yes, kernel


Comment 3 John A. Hull 2002-03-15 19:39:01 UTC
Fixed in Beta 2


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