Skip to contentSkip to conversation

SCSI adaptec 2940 : problem since 2.6.9 and up to 2.6.9-bk6

DISCUSSION Eric Valette 1 participant 2 messages Oct 22, 2004

lore
Share & tools
lore
#0 lore raw

Here is the log message I get :

scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
<Adaptec 2940 Ultra SCSI adapter>
aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs

(scsi0:A:3:0): Unexpected busfree in Message-out phase SEQADDR == 0x16f
(scsi0:A:3:0): Unexpected busfree in Message-out phase SEQADDR == 0x16f
(scsi0:A:3:0): Unexpected busfree in Message-out phase SEQADDR == 0x16f

several ten's of such lines removed
...

The second different model works fine though :

scsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36

        <Adaptec 29160 Ultra160 SCSI adapter>
        aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs

(scsi1:A:6): 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Vendor: QUANTUM Model: ATLAS10K3_36_WLS Rev: 020W
Type: Direct-Access ANSI SCSI revision: 03
scsi1:A:6:0: Tagged Queuing enabled. Depth 64

Furthermore, my HP DAT allthough correctly detected/probed by SCSI BIOS is no more detected...

Signature · 7 lines
   __
  /  `                   	Eric Valette
 /--   __  o _.          	6 rue Paul Le Flem
(___, / (_(_(__         	35740 Pace

Tel: +33 (0)2 99 85 26 76	Fax: +33 (0)2 99 85 26 76
E-mail: [email protected]
#1 lore raw
Quoted 13 lines · Eric Valette

Here is the log message I get :

scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
<Adaptec 2940 Ultra SCSI adapter>
aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs

(scsi0:A:3:0): Unexpected busfree in Message-out phase SEQADDR == 0x16f
(scsi0:A:3:0): Unexpected busfree in Message-out phase SEQADDR == 0x16f
(scsi0:A:3:0): Unexpected busfree in Message-out phase SEQADDR == 0x16f

Quoted 2 lines

several ten's of such lines removed
...

After some more investigation it looks like a hardware problem on the DAT itself. I hven't touched it for years (maybe too many...) and saw the complaint and the recent change so I was rather sure it was the driver/scsi layer changes .

So forget it,

-- eric