aic7xxx: DV failed to configure device
I'm testing an Adaptec SCSI controller + an IBM drive. All the things used to be fine before I had made the low-level format of the drive (thru the Ctrl-A Adaptec's menu). And now after
modprobe aic7xxx
I have:
scsi0 : 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 SCBsscsi0:A:0:0: DV failed to configure device. Please file a bug report against this driver. (scsi0:A:0): 160.000MB/s transfers (80.000MHz DT, offset 63, 16bit)
Vendor: IBM Model: DDYS-T09170N Rev: S80D
Type: Direct-Access ANSI SCSI revision: 03
scsi0:A:0:0: Tagged Queuing enabled. Depth 32
SCSI device sda: 17916240 512-byte hdwr sectors (9173 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 17916240 512-byte hdwr sectors (9173 MB)
SCSI device sda: drive cache: write back
sda: unknown partition table
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
The message
scsi0:A:0:0: DV failed to configure device. Please file a bug report against this driver.
had never appeared before the low-level format. But it seems that after the format the drive still works fine.
So, what does this message mean? And can I just ignore it?
Some additional info: it's the PCI64 card installed in a 32-bit PCI slot, Domain Validation is turned on thru the Adaptec BIOS setup.
Thanks in advance.
Quoted 5 lines · Denis Zaitsev
I'm testing an Adaptec SCSI controller + an IBM drive. All the things used to be fine before I had made the low-level format of the drive (thru the Ctrl-A Adaptec's menu). And now after
modprobe aic7xxx
you failed to mention which exact kernel you were using... (that matters since the aic7xxx driver changes a lot over time, and especially it changed recently in this area a lot)
Quoted 9 lines · Arjan van de Ven
Quoted 5 lines · Denis Zaitsev
I'm testing an Adaptec SCSI controller + an IBM drive. All the things used to be fine before I had made the low-level format of the drive (thru the Ctrl-A Adaptec's menu). And now after
modprobe aic7xxx
you failed to mention which exact kernel you were using...
Yes, I'm sorry. 2.6.10.
Quoted 1 line · Denis Zaitsev
Yes, I'm sorry. 2.6.10.
That particular code was completely changed for 2.6.12-rc5; could you see what that kernel makes of this, please?
Thanks,
James
Quoted 5 lines · James Bottomley
Quoted 1 line · Denis Zaitsev
Yes, I'm sorry. 2.6.10.
That particular code was completely changed for 2.6.12-rc5; could you see what that kernel makes of this, please?
Ok, 2.6.12-rc5:
scsi0 : 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 Vendor: IBM Model: DDYS-T09170N Rev: S80D
Type: Direct-Access ANSI SCSI revision: 03
scsi0:A:0:0: Tagged Queuing enabled. Depth 32
target0:0:0: Beginning Domain Validation
WIDTH IS 1
(scsi0:A:0): 6.600MB/s transfers (16bit)
target0:0:0: Domain Validation skipping write tests
(scsi0:A:0): 160.000MB/s transfers (80.000MHz DT, offset 63, 16bit)
target0:0:0: Ending Domain Validation
SCSI device sda: 17916240 512-byte hdwr sectors (9173 MB) SCSI device sda: drive cache: write back
SCSI device sda: 17916240 512-byte hdwr sectors (9173 MB) SCSI device sda: drive cache: write back
sda: unknown partition table
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
It seems that things are in order, do I understand right? So, why and how the low-level format affects the old driver's behaviour?
Thanks in advance.
Quoted 2 lines · Denis Zaitsev
It seems that things are in order, do I understand right? So, why and how the low-level format affects the old driver's behaviour?
I can't answer that ... part of the reason for ditching the in-driver aic7xxx DV is that it was where an astonishing number of bugs kept turning up.
James