Bug 42563

Summary: ATA Tagged Queuing wedges -STABLE
Product: Base System Reporter: Mark Knight <markk>
Component: kernAssignee: Søren Schmidt <sos>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 4.7-PRERELEASE   
Hardware: Any   
OS: Any   

Description Mark Knight 2002-09-08 22:40:04 UTC
ad0: READ command timeout tag=0 serv=0 - resetting
ad0: invalidating queued requests
ata0: resetting devices .. ad0: invalidating queued requests
ad0: DMA limited to UDMA33, non-ATA66 cable or device
ad1: invalidating queued requests
done
ad0: timeout waiting for READY
ad0: invalidating queued requests
 - resetting
ata0: resetting devices .. ad0: invalidating queued requests
ad0: DMA limited to UDMA33, non-ATA66 cable or device
ad1: invalidating queued requests
ad0: no request for tag=0
...
until the system wedges solid

Further information: http://www.knigma.org/freebsd/tagdeath/info.txt

Fix: 

Don't set hw.ata.tags="1".
How-To-Repeat: 
Occured twice.  I was using dump from ad0 -> a file on ad1.  At the same
time, I was browsing some large .jpg's on ad0 using xzgv.  On both occations
the dump had been running for several hours before the failure.  The
simultaneous xzgv appeared to be the trigger.

Before setting hw.ata.tags="1" today, to test 4.7-PRERELEASE (first time I've
every tried tagged queuing), the system was very stable.
Comment 1 Kris Kennaway freebsd_committer freebsd_triage 2003-07-14 10:28:32 UTC
Responsible Changed
From-To: freebsd-bugs->sos

Assign to ATA maintainer
Comment 2 Søren Schmidt freebsd_committer freebsd_triage 2003-08-11 20:43:37 UTC
State Changed
From-To: open->closed

Try to upgrade to 4.8. If that doesn't help, disable tags. 
I've decided not to support tags anymore due to the endless 
problems with it, and only former IBM did mak disks with it.