DV failed to configure device

From: Ian Soboroff
Date: Tue Dec 16 2003 - 16:28:33 EST



Running 2.4.23 I get the following message from the aic7xxx driver
during boot:

scsi1:A:3:0: DV failed to configure device. Please file a bug report against th
is driver.
(scsi1:A:3): 160.000MB/s transfers (80.000MHz DT, offset 31, 16bit)
Vendor: JetStor Model: III IDE Rev: 0001
Type: Direct-Access ANSI SCSI revision: 03
blk: queue c7d74418, I/O limit 524287Mb (mask 0x7fffffffff)
Vendor: JetStor Model: III IDE Rev: 0001
Type: Direct-Access ANSI SCSI revision: 03
blk: queue c7d74e18, I/O limit 524287Mb (mask 0x7fffffffff)
scsi1:A:3:0: Tagged Queuing enabled. Depth 253
scsi1:A:3:1: Tagged Queuing enabled. Depth 253
Attached scsi disk sdb at scsi1, channel 0, id 3, lun 0
Attached scsi disk sdc at scsi1, channel 0, id 3, lun 1
SCSI device sdb: 2941353984 512-byte hdwr sectors (1505973 MB)
sdb: sdb1
SCSI device sdc: 2451128320 512-byte hdwr sectors (1254978 MB)
sdc: sdc1

(The key bit is the first line... the rest are hopefully enough
context to make it useful ;-) This happens to be a RAID I have
attached to the HBA, a 39160, but I get this message with other,
smaller RAIDs as well.)

I am dutifully filing a bug report, but frankly I have no idea either
from the message or the driver README or the driver source if I should
actually care. Should I? What's DV, and how is the device not
configured? It seems to work ok.

I sent mail to Justin Gibbs but never got a response.

Ian

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/