Re: any available patches for sata: ad4: warning - setfeatures set transfer mode taskqueue timeout - completing request directly
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 Chadwickjdc 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 | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: any available patches for sata: ad4: warning - setfeatures set transfer mode taskqueue timeout - completing request directly
On Mon, May 12, 2008 at 3:00 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote: 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. dhcp-143-221# smartctl -a /dev/ad4 smartctl version 5.38 [amd64-portbld-freebsd7.0] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Second Generation Serial ATA family Device Model: WDC WD3200AAKS-00VYA0 Serial Number:WD-WCARW2314765 Firmware Version: 12.01B02 User Capacity:320,072,933,376 bytes Device is:In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is:Mon May 12 15:27:24 2008 JST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (8760) seconds. Offline data collection capabilities:(0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities:(0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability:(0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time:( 2) minutes. Extended self-test routine recommended polling time:( 104) minutes. Conveyance self-test routine recommended polling time:( 5) minutes. SCT capabilities: (0x303f) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 200 200 051Pre-fail Always - 0 3 Spin_Up_Time0x0003 155 155 021Pre-fail Always - 5233 4 Start_Stop_Count0x0032 100 100 000Old_age Always - 11 5 Reallocated_Sector_Ct 0x0033 200 200 140Pre-fail Always - 0 7 Seek_Error_Rate 0x000e 200 200 051Old_age Always - 0 9 Power_On_Hours 0x0032 099 099 000Old_age Always - 940 10 Spin_Retry_Count0x0012 100 253 051Old_age Always - 0 11 Calibration_Retry_Count 0x0012 100 253 051Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000Old_age Always - 11 192 Power-Off_Retract_Count 0x0032 200 200 000Old_age Always - 8 193 Load_Cycle_Count0x0032 200 200 000Old_age Always - 11 194 Temperature_Celsius 0x0022 114 108 000Old_age Always - 33 196 Reallocated_Event_Count 0x0032 200 200 000Old_age Always - 0 197 Current_Pending_Sector 0x0012 200 200 000Old_age Always - 0 198 Offline_Uncorrectable 0x0010 200 200 000Old_age Offline - 0 199 UDMA_CRC_Error_Count0x003e 200 200 000Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 051Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure
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 [EMAIL PROTECTED]:/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=0xbfebfbffFPU,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=0xe3fdSSE3,RSVD2,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM AMD Features=0x20100800SYSCALL,NX,LM AMD Features2=0x1LAHF 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 10, 7fdf (3) failed acpi0: reservation of 0, a (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 0xfeff-0xfeff03ff on acpi0 Timecounter HPET frequency 2500 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 0xe000-0xefff 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
Re: any available patches for sata: ad4: warning - setfeatures set transfer mode taskqueue timeout - completing request directly
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 Chadwickjdc 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 | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: any available patches for sata: ad4: warning - setfeatures set transfer mode taskqueue timeout - completing request directly
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 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: any available patches for sata: ad4: warning - setfeatures set transfer mode taskqueue timeout - completing request directly
On Mon, May 12, 2008 at 02:14:37PM +0900, dikshie wrote: On Mon, May 12, 2008 at 2:11 PM, Jeremy Chadwick [EMAIL PROTECTED] 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=1400p_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 Chadwickjdc 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 | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
