From owner-freebsd-hardware Fri Jun 1 9:36:11 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id 74AC837B42C for ; Fri, 1 Jun 2001 09:36:06 -0700 (PDT) (envelope-from jose@we.lc.ehu.es) Received: from v-ger.we.lc.ehu.es (v-ger [158.227.6.51]) by polaris.we.lc.ehu.es (8.11.1/8.11.1) with ESMTP id f51Ga4P17292 for ; Fri, 1 Jun 2001 18:36:04 +0200 (MET DST) Received: from we.lc.ehu.es (localhost [127.0.0.1]) by v-ger.we.lc.ehu.es (8.11.3/8.11.3) with ESMTP id f51Ga0K14279 for ; Fri, 1 Jun 2001 18:36:00 +0200 (CEST) (envelope-from jose@we.lc.ehu.es) Message-ID: <3B17C46F.134DE268@we.lc.ehu.es> Date: Fri, 01 Jun 2001 18:35:59 +0200 From: "Jose M. Alcaide" Organization: Universidad del Pais Vasco - Dpto. de Electricidad y Electronica X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: es-ES, es, en-US, en MIME-Version: 1.0 To: hardware@FreeBSD.org Subject: ad0 write command timeouts after upgrading to 4.3-RELEASE Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello, I have just upgraded to 4.3-RELEASE a machine based on a Gigabyte 7ZX motherboard (KT133 chipset, VIA 686A ATA66 controller). Since that moment, when I stress the disk with many writes (for example, untar an large archive), the kernel complaints with these messages: ata0: resetting devices .. done ad0: WRITE command timeout tag=0 serv=0 - resetting The disk ATA mode does not fall back to PIO; eventually, the untar finishes. Surprisingly, if I enable write caching the problem seems to dissapear. Maybe I did not see this problem with 4.2-RELEASE because WC was enabled by default. I did the same tests on other machine with the same motherboard and processor (Duron 800MHz), but different disk, and everything works fine. These are the relevant lines of dmesg output on the problem machine: atapci0: port 0xffa0-0xffaf at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 .... ad0: 19546MB [39714/16/63] at ata0-master UDMA66 acd0: CDROM at ata1-master using WDMA2 Bad disk firmware? Cheers, -- JMA ****** Jose M. Alcaide // jose@we.lc.ehu.es // jmas@FreeBSD.org ****** ** "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein ** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message