Hello,
On 11/16/2009 12:57 PM, Erik Postma wrote:
> 2009/11/15 Erik Postma <e.j.postma+linux-ide@xxxxxxxxx>:
>> (...)
>> [7.7.] Other information that might be relevant to the problem
>> (please look in /proc and include all information that you
>> think to be relevant):
>>
>> Here's dmesg:
>> (...)
>
> Just now I had a boot where it did something different; here's what I
> guess is the relevant part of dmesg. This is the same kernel and of
> course the same hardware as described in the earlier email. Does the
> fact that it's unpredictable mean there's possibly hardware issues?
> Still have not seen any sign of trouble on 2.6.30 or earlier.
>
> [ 6.872066] ata4.00: qc timeout (cmd 0xa0)
> [ 6.872123] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action
> 0x6 frozen
> [ 6.872183] ata4.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
> [ 6.872184] cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00
> [ 6.872186] res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask
> 0x5 (timeout)
> [ 6.872337] ata4.00: status: { DRDY ERR }
> [ 6.872417] ata4: soft resetting link
> [ 7.052604] ata4.00: configured for UDMA/33
> [ 7.053051] ata4: EH complete
Timeouts on TURs. These seem pretty common for optical drives for
some reason. I can't think of anything which has changed since .30
which could have affected execution of NODATA command. Is the drive
useable once those timeouts passed? Does having a media in the drive
or not make any difference?
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
