From owner-freebsd-current@FreeBSD.ORG Tue Dec 28 02:27:37 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F170A16A4CE; Tue, 28 Dec 2004 02:27:37 +0000 (GMT) Received: from diligence.flag.rootnode.com (adsl-65-67-81-98.dsl.ltrkar.swbell.net [65.67.81.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DEC943D46; Tue, 28 Dec 2004 02:27:37 +0000 (GMT) (envelope-from joe@osoft.us) Received: from [10.0.1.105] (coherence.flag.rootnode.com [10.0.1.105]) by diligence.flag.rootnode.com (Postfix) with ESMTP id 95AD7D4BA; Mon, 27 Dec 2004 20:27:36 -0600 (CST) Message-ID: <41D0C51D.8020800@osoft.us> Date: Mon, 27 Dec 2004 20:29:49 -0600 From: Joe Koberg User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: =?ISO-8859-1?Q?Zsolt_K=FAti?= References: <20041209183911.068c9a84.kutizs@axelero.hu> In-Reply-To: <20041209183911.068c9a84.kutizs@axelero.hu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Tue, 28 Dec 2004 13:34:32 +0000 cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: TIMEOUT - WRITE_DMA - A possible FIX! turn off ACPI X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Dec 2004 02:27:38 -0000 Zsolt Kúti wrote: >My system produces these messages that I already know well from this >list (as well ;): >ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=213249674 > > Like many people I was confronted with "TIMEOUT - READ_DMA" and "TIMEOUT - WRITE_DMA" errors on my drives. I was frustrated. But I found a workaround: Turning off ACPI. I just received a Highpoint RocketRaid 1640 controller, 2 Maxtor 300GB drives, and a Supermicro 5-drive SATA cage. I am testing this configuration for a storage server. I am using an old motherboard, DTK brand, Slot 1. 300A Celeron. Under a fresh install of 5.3-RELEASE I am unable to read or write both drives heavily at the same time. One drive alone seems to work OK. When I run dd blasting both drives with seqential IO, I get TIMEOUT - WRITE(READ)_DMA. Repeatably, within 15 seconds. However I got a good test before I installed 5.3-R, the box was running with 5.3-BETA. Only difference was I booted without ACPI. So I rebooted the freshly installed 5.3-R without ACPI, and It works! I can read at 50MB/s per drive concurrently (hitting PCI bus speed limit?), and write at 30MB/s per drive concurrently. No errors so far, and its been dd'ing for a half hour. I hope this report helps someone! Joe Koberg joe at osoft dot us dmesg: FreeBSD 5.3-RELEASE #0: Fri Nov 5 04:19:18 UTC 2004 root@harlow.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Pentium II/Pentium II Xeon/Celeron (307.84-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x660 Stepping = 0 Features=0x183f9ff real memory = 402587648 (383 MB) avail memory = 384270336 (366 MB) npx0: [FAST] npx0: on motherboard npx0: INT 16 interface pcib0: pcibus 0 on motherboard pir0: on motherboard pci0: on pcib0 agp0: mem 0xe0000000-0xe3ffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 uhci0: port 0xb000-0xb01f irq 10 at device 7.2 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ums0: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM), rev 1.10/3.00, addr 2, iclass 3/1 ums0: 5 buttons and Z dir. pci0: at device 7.3 (no driver attached) atapci1: port 0xc400-0xc4ff,0xc000-0xc003,0xbc00-0xbc07,0xb800-0xb803,0xb400-0xb407 irq 11 at device 17.0 on pci0 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 atapci2: port 0xd800-0xd8ff,0xd400-0xd403,0xd000-0xd007,0xcc00-0xcc03,0xc800-0xc807 irq 11 at device 17.1 on pci0 ata4: channel #0 on atapci2 ata5: channel #1 on atapci2 dc0: port 0xdc00-0xdcff mem 0xec000000-0xec0003ff irq 12 at device 18.0 on pci0 miibus0: on dc0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc0: Ethernet address: 00:04:5a:56:80:76 dc0: if_start running deferred for Giant dc0: [GIANT-LOCKED] pci0: at device 19.0 (no driver attached) cpu0 on motherboard orm0: at iomem 0xcc000-0xcdfff,0xc0000-0xc8fff on isa0 pmtimer0 on isa0 atkbdc0: at port 0x64,0x60 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] fdc0: at port 0x3f0-0x3f5 irq 6 drq 2 on isa0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources (port) unknown: can't assign resources (memory) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) Timecounter "TSC" frequency 307842170 Hz quality 800 Timecounters tick every 10.000 msec ad0: 43979MB [89355/16/63] at ata0-master UDMA33 ad4: 286188MB [581463/16/63] at ata2-master UDMA133 ad6: 286188MB [581463/16/63] at ata3-master UDMA133 Mounting root from ufs:/dev/ad0s1a >After these messages the two former cases result in FAILURE and finally >in panic. Even background fsck cannot run without another panic, only >single user mode can help. All these prevent using them on my HW. >However B7, although displays the messages as well, works seemingly >fine. For the time being this version is sufficent, but I'd like to >know - if possible at all - what the difference could be between the >versions and if one can expect to bring the actual 5.3 version's >state to B7's in this respect? > >Further to this, the different versions display the behavior of >relatively frequently (many time in an hour?) stalling their >responsivity for some seconds. Most of the times no message can be seen >on the consol after this. It is also more rare on B7. > >I also found that pendrive's sensing by 5.3 RELEASE/STABLE more >frequently results in panic than B7's. (As a matter of fact I have not >seen it with B7 for weeks since I installed it.) > >I use the following either with GENERIC or custom kernel: >Abit NF7-S (nVidia chipsets, SiI3112 on board), Athlon 2600+, >Samsung 120G SATA, LEXAR MEDIA JUMPDRIVE, rev 1.10/0.01 > > >Please cc it to me as well, since I'am not on the list for the time >being. >Many thanks! > >Zsolt > >-------------------- >Zsolt Kuti >_______________________________________________ >freebsd-current@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > >