Bug 55086

Summary: 3w-xxxx module does not work properly (at least) with 3w 6200 card
Product: [Retired] Red Hat Linux Reporter: Jure Pecar <jure.pecar>
Component: installerAssignee: Brent Fox <bfox>
Status: CLOSED ERRATA QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.2   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-10-25 10:42:27 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 Jure Pecar 2001-10-25 10:42:22 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.12-ac3 i686)

Description of problem:
3w-xxxx  module inserts properly, but when fdisk wants to access a raid1
volume configured on escalade 6200 card, some error is printed and that the
array is then not available for any r/w operations, so RedHat cannot be
installed on it.

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

How reproducible:

Steps to Reproduce:
1. have a 3w escalade card in the system
2. configure a raid1 array on it
3. try to install redhat on it ... 

Actual Results:  the error:

3w-xxxx: tw_interrupt(): Bad response, status = 0xc1, flags = 0x11, unit =
3w-xxxx: tw_scsi_eh_reset(): Reset succeeded for card 1.
3w-xxxx: tw_interrupt(): Bad response, status = 0xc1, flags 0x11, unit 0x0.
scsi: device set offline - not ready or command retry failed after host
reset: host 1 channel 0 id 0 lun 0
SCSI disk error : host 1 channel 0 id 0 lun 0 return code = 80000
 I/O error: dev 08:00, sector 19539040
get_last_sector ioctl: bread returned NULL.

Expected Results:  I have 3ware cards in other systems but they don't boot
from them. I never had any problems with the 3w-xxxx module on various
kernels, so i see no reason that the module in the boot kernel doesn't

Additional info:

Comment 1 Brock Organ 2001-10-25 13:56:46 UTC
an erratum to fix this issue is available at:


it specifically provides an anaconda updates disk:


Good luck and thanks for your report! :)