freebsd stable - May 2008 - any available patches for sata: "ad4: warning - setfeatures set transfer mode taskqueue timeout - completing request directly"

Hi,
I got :
--------------------------------
ad4: warning - setfeatures set transfer mode taskqueue timeout -
completing request directly
ad4: warning - setfeatures enable rcache taskqueue timeout -
completing request directly
ad4: warning - setfeatures enable wcache taskqueue timeout -
completing request directly
ad4: timeout - flushcache retrying (0 retries left)
geom_journal: flush cache of ad4s1d: error=5
ad4: timeout - write_dma retrying (1 retry left) LBA=4139103
-------------------------------
I read: http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues

and strange output from dmesg:
ad4: 305245MB <WDC WD3200AAKS-00VYA0 12.01B02> at ata2-master UDMA33

                                  ^^^^^^^^^^^
any available patches ?


best regards,

-dikshie-
--------------------------------
Copyright (c) 1992-2008 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
        The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 7.0-STABLE #19: Sat May 10 15:41:00 JST 2008
    dikshie@dhcp-143-221.sfc.wide.ad.jp:/usr/obj/usr/src/sys/BARU
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Core(TM)2 Duo CPU     E6550  @ 2.33GHz (2333.34-MHz K8-class CPU)
  Origin = "GenuineIntel"  Id = 0x6fb  Stepping = 11
 
Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
 
Features2=0xe3fd<SSE3,RSVD2,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM>
  AMD Features=0x20100800<SYSCALL,NX,LM>
  AMD Features2=0x1<LAHF>
  Cores per package: 2
usable memory = 2000646144 (1907 MB)
avail memory  = 1926553600 (1837 MB)
ACPI APIC Table: <Nvidia NVDAACPI>
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
ACPI Warning (tbfadt-0505): Optional field "Pm2ControlBlock" has zero
address or length:        0       0/1 [20070320]
ioapic0: Changing APIC ID to 4
ioapic0 <Version 1.1> irqs 0-23 on motherboard
kbd1 at kbdmux0
cryptosoft0: <software crypto> on motherboard
acpi0: <Nvidia NVDAACPI> on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
acpi0: reservation of 100000, 7fdf0000 (3) failed
acpi0: reservation of 0, a0000 (3) failed
Timecounter "ACPI-safe" frequency 3579545 Hz quality 850
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
acpi_hpet0: <High Precision Event Timer> iomem 0xfeff0000-0xfeff03ff on
acpi0
Timecounter "HPET" frequency 25000000 Hz quality 900
cpu0: <ACPI CPU> on acpi0
est0: <Enhanced SpeedStep Frequency Control> on cpu0
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 72a072a0600072a
device_attach: est0 attach returned 6
p4tcc0: <CPU Frequency Thermal Control> on cpu0
cpu1: <ACPI CPU> on acpi0
est1: <Enhanced SpeedStep Frequency Control> on cpu1
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 72a072a0600072a
device_attach: est1 attach returned 6
p4tcc1: <CPU Frequency Thermal Control> on cpu1
acpi_button0: <Power Button> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pci0: <memory, RAM> at device 0.1 (no driver attached)
pci0: <memory, RAM> at device 1.0 (no driver attached)
pci0: <memory, RAM> at device 1.1 (no driver attached)
pci0: <memory, RAM> at device 1.2 (no driver attached)
pci0: <memory, RAM> at device 1.3 (no driver attached)
pci0: <memory, RAM> at device 1.4 (no driver attached)
pci0: <memory, RAM> at device 1.5 (no driver attached)
pci0: <memory, RAM> at device 1.6 (no driver attached)
pci0: <memory, RAM> at device 2.0 (no driver attached)
isab0: <PCI-ISA bridge> at device 3.0 on pci0
isa0: <ISA bus> on isab0
pci0: <serial bus, SMBus> at device 3.1 (no driver attached)
pci0: <memory, RAM> at device 3.2 (no driver attached)
pci0: <memory, RAM> at device 3.4 (no driver attached)
ohci0: <OHCI (generic) USB controller> mem 0xeffff000-0xefffffff irq
21 at device 4.0 on pci0
ohci0: [GIANT-LOCKED]
ohci0: [ITHREAD]
usb0: OHCI version 1.0, legacy support
usb0: SMM does not respond, resetting
usb0: <OHCI (generic) USB controller> on ohci0
usb0: USB revision 1.0
uhub0: <nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0
uhub0: 10 ports with 10 removable, self powered
ehci0: <EHCI (generic) USB 2.0 controller> mem 0xefffe000-0xefffe0ff
irq 22 at device 4.1 on pci0
ehci0: [GIANT-LOCKED]
ehci0: [ITHREAD]
usb1: EHCI version 1.0
usb1: companion controller, 10 ports each: usb0
usb1: <EHCI (generic) USB 2.0 controller> on ehci0
usb1: USB revision 2.0
uhub1: <nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb1
uhub1: 10 ports with 10 removable, self powered
umass0: <Generic USB2.0-CRW, class 0/0, rev 2.00/11.22, addr 2> on uhub1
atapci0: <nVidia nForce MCP73 UDMA133 controller> port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 8.0 on
pci0
ata0: <ATA channel 0> on atapci0
ata0: [ITHREAD]
ata1: <ATA channel 1> on atapci0
ata1: [ITHREAD]
pci0: <multimedia> at device 9.0 (no driver attached)
pcib1: <ACPI PCI-PCI bridge> at device 10.0 on pci0
pci1: <ACPI PCI bus> on pcib1
pcib2: <ACPI PCI-PCI bridge> at device 11.0 on pci0
pci2: <ACPI PCI bus> on pcib2
pcib3: <ACPI PCI-PCI bridge> at device 12.0 on pci0
pci3: <ACPI PCI bus> on pcib3
pcib4: <ACPI PCI-PCI bridge> at device 13.0 on pci0
pci4: <ACPI PCI bus> on pcib4
re0: <RealTek 8168/8111B PCIe Gigabit Ethernet> port 0xde00-0xdeff mem
0xefdff000-0xefdfffff irq 16 at device 0.0 on pci4
miibus0: <MII bus> on re0
rgephy0: <RTL8169S/8110S/8211B media interface> PHY 1 on miibus0
rgephy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
1000baseT-FDX, auto
re0: Ethernet address: 00:e0:4d:66:7a:72
re0: [FILTER]
atapci1: <nVidia ATA controller> port
0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xf700-0xf70f mem
0xefff8000-0xefff9fff irq 20 at device 14.0 on pci0
atapci1: [ITHREAD]
ata2: <ATA channel 0> on atapci1
ata2: [ITHREAD]
ata3: <ATA channel 1> on atapci1
ata3: [ITHREAD]
vgapci0: <VGA-compatible display> mem
0xed000000-0xedffffff,0xd0000000-0xdfffffff,0xee000000-0xeeffffff irq
21 at device 16.0 on pci0
acpi_tz0: <Thermal Zone> on acpi0
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on
acpi0
sio0: type 16550A
sio0: [FILTER]
ppc0: <Parallel port> port 0x378-0x37f,0x778-0x77b irq 7 drq 3 on acpi0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/16 bytes threshold
ppbus0: <Parallel port bus> on ppc0
ppbus0: [ITHREAD]
plip0: <PLIP network interface> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppc0: [GIANT-LOCKED]
ppc0: [ITHREAD]
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
orm0: <ISA Option ROM> at iomem 0xd0000-0xd3fff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
orm0: <ISA Option ROM> at iomem 0xd0000-0xd3fff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
ums0: <Logitech USB Mouse, class 0/0, rev 1.10/6.10, addr 2> on uhub0
ums0: 3 buttons and Z dir.
Timecounters tick every 1.000 msec
IPsec: Initialized Security Association Processing.
ad4: 305245MB <WDC WD3200AAKS-00VYA0 12.01B02> at ata2-master UDMA33
acd0: DVDR <HL-DT-ST DVDRAM GH20NS10/EL00> at ata3-slave UDMA33
GEOM_JOURNAL: Journal 3398879317: ad4s1d contains data.
GEOM_JOURNAL: Journal 3398879317: ad4s1d contains journal.
GEOM_JOURNAL: Journal ad4s1d clean.
GEOM_JOURNAL: Journal 2420032810: ad4s1e contains data.
GEOM_JOURNAL: Journal 2420032810: ad4s1e contains journal.
GEOM_JOURNAL: Journal ad4s1e clean.
GEOM_JOURNAL: Journal 2035336235: ad4s1f contains data.
GEOM_JOURNAL: Journal 2035336235: ad4s1f contains journal.
GEOM_JOURNAL: Journal ad4s1f clean.
GEOM_JOURNAL: Journal 811662893: ad4s1g contains data.
GEOM_JOURNAL: Journal 811662893: ad4s1g contains journal.
GEOM_JOURNAL: Journal ad4s1g clean.
SMP: AP CPU #1 Launched!
da0 at umass-sim0 bus 0 target 0 lun 0
da0: <Generic- Compact Flash 1.00> Removable Direct Access SCSI-0 device
da0: 40.000MB/s transfers
da0: Attempt to query device size failed: NOT READY, Medium not present
da1 at umass-sim0 bus 0 target 0 lun 1
da1: <Generic- SM/xD-Picture 1.00> Removable Direct Access SCSI-0 device
da1: 40.000MB/s transfers
da1: Attempt to query device size failed: NOT READY, Medium not present
da2 at umass-sim0 bus 0 target 0 lun 2
da2: <Generic- SD/MMC 1.00> Removable Direct Access SCSI-0 device
da2: 40.000MB/s transfers
da2: Attempt to query device size failed: NOT READY, Medium not present
da3 at umass-sim0 bus 0 target 0 lun 3
da3: <Generic- MS/MS-Pro 1.00> Removable Direct Access SCSI-0 device
da3: 40.000MB/s transfers
da3: Attempt to query device size failed: NOT READY, Medium not present
Trying to mount root from ufs:/dev/ad4s1a
-----------------------------------------------------------

On Mon, May 12, 2008 at 01:17:16PM +0900, dikshie wrote:
> and strange output from dmesg:
> ad4: 305245MB <WDC WD3200AAKS-00VYA0 12.01B02> at ata2-master UDMA33
>                                   ^^^^^^^^^^^
> any available patches ?
What's strange about this?

-- 
| Jeremy Chadwick                                jdc at parodius.com |
| Parodius Networking                       http://www.parodius.com/ |
| UNIX Systems Administrator                  Mountain View, CA, USA |
| Making life hard for others since 1977.              PGP: 4BD6C0CB |

dikshie wrote:
> atapci1: <nVidia ATA controller> port
> 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xf700-0xf70f mem
> 0xefff8000-0xefff9fff irq 20 at device 14.0 on pci0
It seems your controller detected as generic ATA.
Can you show `pciconf -l` output from your system?

-- 
WBR, Andrey V. Elsukov

On Mon, May 12, 2008 at 02:14:37PM +0900, dikshie wrote:
> On Mon, May 12, 2008 at 2:11 PM, Jeremy Chadwick <koitsu@freebsd.org>
wrote:
> > On Mon, May 12, 2008 at 01:17:16PM +0900, dikshie wrote:
> >> and strange output from dmesg:
> >> ad4: 305245MB <WDC WD3200AAKS-00VYA0 12.01B02> at
ata2-master UDMA33
> >>                                   ^^^^^^^^^^^
> >> any available patches ?
> >
> > What's strange about this?
> 
> i mean for "UDMA33" it should be SATA300
> do have to upgrade BIOS?
Your carets are pointing to the drive firmware revision, which is why I
was confused.  :-) Yes, it should say either SATA150 or SATA300 (more on
that in a moment), but based on your dmesg output, it appears your SATA
controller does not have an attached driver, thus is operating
generically.  Andrey recommended showing pciconf -lv output; please do.

Your drive is *probably* operating in SATA150/300 mode, despite UDMA33
being printed, however.  Assuming you know your disk can push >33MB/sec,
you could try some simple read I/O and use gstat to watch the speed.
dd if=/dev/ad4 of=/dev/null bs=1m should suffice.

Regarding SATA150 vs. SATA300: your drive has a physical jumper,
labelled OPT1 in the below photo, which limits the drive to SATA150
capability.  You can remove this jumper and get SATA300.  This doesn't
explain the UDMA33 issue, though.

http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_faqid=1400&p_created=1134597011

Also, please don't remove the mailing list from the CC; others need to
know what information you've provided, and future users may find this
thread useful.

-- 
| Jeremy Chadwick                                jdc at parodius.com |
| Parodius Networking                       http://www.parodius.com/ |
| UNIX Systems Administrator                  Mountain View, CA, USA |
| Making life hard for others since 1977.              PGP: 4BD6C0CB |

On Mon, May 12, 2008 at 02:42:40PM +0900, dikshie wrote:
> i just phone computer store and check together the BIOS.
> it seems my computer store put the disk on IDE mode NOT on AHCI mode.
> after change to AHCI now FreeBSD can detect SATA 300 (for WDC) and
> SATA 150 (for DVD-R).
Great, there you go.  :-)
> BUT sometimes I still getting:
> ad4: warning - setfeatures set transfer mode taskqueue timeout -completing
request directly
> ad4: warning - setfeatures enable rcache taskqueue timeout - completing
request directly
> ad4: warning - setfeatures enable wcache taskqueue timeout - completing
request directly
> ad4: timeout - flushcache retrying (0 retries left)
> geom_journal: flush cache of ad4s1d: error=5
> ad4: timeout - write_dma retrying (1 retry left) LBA=4139103
1) Have you checked SMART statistics of the drive, or run SMART tests?
Install ports/sysutils/smartmontools and use smartctl -a /dev/ad4, and
provide the output.

2) Is the error always on ad4?  If so, is the error always at LBA
4139103, or "around there" (give or take a few thousand addressing
blocks)?  If so, the ad4 disk may be going bad.  Otherwise, I would say
this is probably the issue I've documented on my Common Issues page.

-- 
| Jeremy Chadwick                                jdc at parodius.com |
| Parodius Networking                       http://www.parodius.com/ |
| UNIX Systems Administrator                  Mountain View, CA, USA |
| Making life hard for others since 1977.              PGP: 4BD6C0CB |