registry team mailing list archive

Thread
Date

[Bug 256637] Re: ata3: COMRESET failed (errno=-16)

To: registry@xxxxxxxxxxxxxxxxxxx
From: devsk <funtoos@xxxxxxxxx>
Date: Sat, 19 Jun 2010 18:09:02 -0000
Reply-to: Bug 256637 <256637@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

Is this really a corner case bug or is it just the hardware?

I have had this happen to me with 3 different drives and the drives are
brand new and they work fine otherwise.

I have checked the cabling and I have the locked SATAII cables. All the
drives are SATAII and nothing in the system is 1.5Gbps. So, this is not
a legacy drive phenomenon.

Could it be related to NCQ? When I saw these errors on a drive (which is
the oldest of the 3), I disabled NCQ on it (set qdepth to 1) and I
haven't seen this on that drive ever since.

Can other people having this issue try turning NCQ off and see if it
goes away?

-- 
ata3: COMRESET failed (errno=-16) 
https://bugs.launchpad.net/bugs/256637
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for Debian.