Re: [RFT] major libata update

Tejun Heo
2006-05-17T04:49:09Z

Hello, Andrew.

Andrew Morton wrote:
[--snip--]
> [ 44.719422] ata2.00: cfg 49:0f00 82:0000 83:0000 84:0000 85:0000 86:0000 87:0000 88:101f
> [ 44.719425] ata2.00: ATAPI, max UDMA/66
> [ 44.765263] ata2.00: applying bridge limits
> [ 74.928836] ata2.01: qc timeout (cmd 0xa1)
> [ 74.977811] ata2.01: failed to IDENTIFY (I/O error, err_mask=0x4)
> [ 75.468853] ata2.00: cfg 49:0f00 82:0000 83:0000 84:0000 85:0000 86:0000 87:0000 88:101f
> [ 75.468856] ata2.00: ATAPI, max UDMA/66
> [ 75.514678] ata2.00: applying bridge limits
> [ 105.674130] ata2.01: qc timeout (cmd 0xa1)

Did this device work with previous versions of kernel?

libata used to give up on the first failure during probe, so the boot
time would have been shorter in failure cases. I think controlled
retries during boot probe is a good thing, but the timeout of 30s for
IDENTIFY commands can be shortened, I guess.

--
tejun