Bug 44063

Summary: ATA Tags (TQ) problems on 4.7-STABLE
Product: Base System Reporter: Alexey Dokuchaev <danfe>
Component: kernAssignee: Søren Schmidt <sos>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 4.7-STABLE   
Hardware: Any   
OS: Any   

Description Alexey Dokuchaev 2002-10-14 21:30:02 UTC
It seems that certain IBM hard drives confuse FreeBSD ata TQ code:

ad0: 76319MB <MAXTOR 4K080H4> [155060/16/63] at ata0-master UDMA100
ad1: 58644MB <IC35L060AVVA07-0> [119150/16/63] at ata0-slave tagged UDMA100
ad2: 117800MB <IC35L120AVVA07-0> [239340/16/63] at ata1-master tagged UDMA100
Waiting 2 seconds for SCSI devices to settle
sa0 at ahc0 bus 0 target 2 lun 0
sa0: <HP T4000s 1.07> Removable Sequential Access SCSI-2 device
sa0: 3.300MB/s transfers
Mounting root from ufs:/dev/ad0s1a
ad0: READ command timeout tag=0 serv=0 - resetting
ata0: resetting devices .. ad0: DMA limited to UDMA33, non-ATA66 cable or device

ad1: invalidating queued requests
done
ad0: READ command timeout tag=0 serv=0 - resetting
ata0: resetting devices .. ad0: DMA limited to UDMA33, non-ATA66 cable or device

ad1: invalidating queued requests
done
ad0: READ command timeout tag=0 serv=0 - resetting
ata0: resetting devices .. ad0: DMA limited to UDMA33, non-ATA66 cable or device

ad1: invalidating queued requests
done
ad0: READ command timeout tag=0 serv=0 - resetting
ad0: timeout sending command=ef s=d0 e=04
ad0: trying fallback to PIO mode
ata0: resetting devices .. ad1: invalidating queued requests
done

Fix: 

N/A
How-To-Repeat: echo hw.ata.tags=1 >> /boot/loader.conf && reboot
Comment 1 Johan Karlsson freebsd_committer freebsd_triage 2002-10-25 09:53:53 UTC
Responsible Changed
From-To: freebsd-bugs->sos

Over ro ATA maintainer.
Comment 2 Søren Schmidt freebsd_committer freebsd_triage 2003-04-28 19:39:48 UTC
State Changed
From-To: open->feedback

Does this still happen on 4.8 or later ? 
If problem still exists, a full dmesg would be nice.
Comment 3 Søren Schmidt freebsd_committer freebsd_triage 2003-09-08 20:04:12 UTC
State Changed
From-To: feedback->closed

feedback timeout