Date: Sun, 26 Feb 2006 20:10:16 -0800 (PST) From: Jason Spence <jspence@lightconsulting.com> To: FreeBSD-gnats-submit@FreeBSD.org Subject: kern/93885: ata(4) failure: SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! Message-ID: <200602270410.k1R4AGKk000774@graendal.dyndns.org> Resent-Message-ID: <200602270410.k1R4A844022210@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 93885 >Category: kern >Synopsis: ata(4) failure: SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Feb 27 04:10:08 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Jason Spence <jspence@lightconsulting.com> >Release: FreeBSD 6.1-PRERELEASE i386 >Organization: none >Environment: System: FreeBSD graendal 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #2: Sun Feb 26 18:10:01 PST 2006 root@graendal:/usr/obj/usr/src/sys/GRAENDAL i386 Via EPIA M10000 LVDS motherboard http://www.via.com.tw/en/products/mainboards/mini_itx/epia_m/ Promise Fasttrack TX2200 http://www.promise.com/product/product_detail_eng.asp?segment=RAID%200/1%20HBAs&product_id=128 atapci1@pci0:20:0: class=0x010400 card=0x3571105a chip=0x3571105a rev=0x02 hdr=0x00 vendor = 'Promise Technology Inc' class = mass storage subclass = RAID 2x WDC WD2500JS-00MHB0 disks, firmware 02.01C03 http://www.wdc.com/en/products/Products.asp?DriveID=135&Language=en Disks are configured as a RAID 1 mirror, detected as ar0: [jspence@graendal ~]> sudo atacontrol status ar0 ar0: ATA RAID1 subdisks: ad4 ad6 status: READY >Description: Under heavy disk load, such as a find / loop, the following message occurs: ad?: req=0x???????? SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! The question mark characters change for each incident. The message comes from ata-queue.c. The machine becomes unresponsive even to power button events. A hard reset is required. This bug is similar to or identical to kern/91408. >How-To-Repeat: Duplicate the above hardware configuration. Execute the following script: #!/bin/sh while true; do find / done Wait a few minutes. >Fix: No fix known. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200602270410.k1R4AGKk000774>