Bug 57768 - Installer hangs when loading aic-78xx driver
Summary: Installer hangs when loading aic-78xx driver
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 7.2
Hardware: i386
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: 2001-12-21 18:42 UTC by Mark Olton
Modified: 2005-10-31 22:00 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-01-05 03:37:56 UTC
Embargoed:


Attachments (Terms of Use)

Description Mark Olton 2001-12-21 18:42:53 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.4.2-2smp i686)

Description of problem:
I'm submitting this as a new bug, as it seems to be slightly different.  I
am using a dual AMD Athlon system, Tyan Thunder K7 mobo, 2 GB RAM and an
Adaptec
39160 (aic-78xx).  When the installer tries to load the driver, it hangs
giving me the error "Unexpected Bus Free in Data-in Phase" infinitely.  The
Experimental driver does the same thing, and since I'm not using an Intel
Board, but rather an AMD one, the updated boot disks do not work for me.  

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


How reproducible:
Always

Steps to Reproduce:
1. Install using either Adaptec driver
	

Additional info:

Right after the message "Tagging Queuing Enabled" I get the message
"Unexpected Bus Free in Data-in Phase" infinitely.

Comment 1 Jeremy Katz 2002-01-02 22:06:30 UTC
Arjan, any ideas here?

Comment 2 Arjan van de Ven 2002-01-04 13:41:48 UTC
Is this in the installer or in the normal kernel ?

Comment 3 Mark Olton 2002-01-05 03:37:51 UTC
It hangs in the installer.  Also, a lot of people have been referring me to 
the 440GX bug, but I'm not sure that it applies as this motherboard is using 
the AMD-760 MP chipset.

Comment 4 Doug Ledford 2002-01-17 02:46:10 UTC
The 440gx bug doesn't apply.  This is a cabling issue.  You have bad termination
or a bad cable.  Check all of your SCSI connectors to make sure none of them
have any bent pins and check to make sure that auto termination is enabled on
the SCSI controller and that there is a terminator on the end of the SCSI cable.
 IF neither of those things fixes the bug, then reopen with more details about
your SCSI configuration.


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