Bug 60864

Summary: Quantum Atlas IV (U160) drives + Hendrix were timed out when using aic7xxx driver
Product: [Retired] Red Hat Linux Reporter: Danny Trinh <danny_trinh>
Component: kernelAssignee: Arjan van de Ven <arjanv>
Status: CLOSED CURRENTRELEASE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3CC: afom_m, clay_cooper, dale_kaisner, danny_trinh, dean_oliver, gary_lerhaupt, john_hull, joshua_giles, matt_domsch, michael_e_brown, robert_hentosh, rogelio_noriega
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-03-21 02:38:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
dmesg none

Description Danny Trinh 2002-03-08 00:54:12 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20011019
Netscape6/6.2

Description of problem:
SCSI bus reset when trying to read Quantum Atlas IV HDD. This happens only when
Adaptec 39160 (7899) hooks up to Hendrix. However, if I configure to use ROMB
and create a RAID, then the HDDs are working fine (use aacraid driver).  

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


How reproducible:
Always

Steps to Reproduce:
1.A server with onboard 7899, or 39160 card + Hendrix + Quantum Atlas IV HDDs.
2.Boot from CD, and switch to VC 4 to see the errors.
3.Use the same Hardware configuration but ROMB instead of SCSI. There is no
time-out occurs.
	

Actual Results:  Failed to read, identify, use of Quantum Atlas IV drive. This
also happens on IBM drives too (U160).

Expected Results:  aic7xxx driver should work with those drives when they are in
Hendrix.

Additional info:

Also, If using those HDDs as internal drives (Not plug-in to Hendrix), then they
are working as expect.
Comment 1 Arjan van de Ven 2002-03-08 10:18:12 UTC 
Could you try the aic7xxx_old driver to see if that one works ?
(to see if it's driver or hardware)
Comment 2 Danny Trinh 2002-03-09 00:00:10 UTC 
Created attachment 47980 [details]
dmesg
Comment 3 Danny Trinh 2002-03-09 00:01:34 UTC 
aic7xxx_old driver does the same thing.
Comment 4 Danny Trinh 2002-03-11 17:05:56 UTC 
I can "insmod aic7xxx" when I use UP kernel. fdisk, mke2fs work fine also. This 
problem seems to happens on SMP kernel only (well, maybe on bigmem kernel too).
Comment 5 Arjan van de Ven 2002-03-11 17:13:43 UTC 
Can you try the pensacola beta.40 kernel? this can be one of those interrupt bugs ;(
Comment 6 Danny Trinh 2002-03-11 20:49:32 UTC 
Pensacola is working fine (beta.40 kernel).
Comment 7 Jay Turner 2002-03-21 02:37:55 UTC 
So, did the patch from Pensacola make it into the Hampton kernel?
Comment 8 Danny Trinh 2002-03-21 22:44:48 UTC 
fixed in beta3