From nobody@FreeBSD.org  Mon May  1 18:48:13 2000
Return-Path: <nobody@FreeBSD.org>
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP id 4312E37B865
	for <freebsd-gnats-submit@FreeBSD.org>; Mon,  1 May 2000 18:48:13 -0700 (PDT)
	(envelope-from nobody@FreeBSD.org)
Received: (from nobody@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id SAA38909;
	Mon, 1 May 2000 18:48:12 -0700 (PDT)
	(envelope-from nobody@FreeBSD.org)
Message-Id: <200005020148.SAA38909@freefall.freebsd.org>
Date: Mon, 1 May 2000 18:48:12 -0700 (PDT)
From: lyamog@infiniteinfo.com
Sender: nobody@FreeBSD.org
To: freebsd-gnats-submit@FreeBSD.org
Subject: FreeBSD 4.0 has a "WRITE command timeout - resetting" problem on VIA chipset
X-Send-Pr-Version: www-1.0

>Number:         18335
>Category:       kern
>Synopsis:       FreeBSD 4.0 has a "WRITE command timeout - resetting" problem on VIA chipset
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    sos
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon May  1 18:50:01 PDT 2000
>Closed-Date:    Tue Nov 14 00:23:42 PST 2000
>Last-Modified:  Fri Dec  8 08:00:02 PST 2000
>Originator:     Jun Yamog
>Release:        4.0
>Organization:
Infinite Info
>Environment:
Sorry can't machine is not booting anymore.
>Description:
FreeBSD 4.0 has a "WRITE command timeout - resetting" problem on VIA 
chipset.  This VIA chipset is Apollo Pro133, the older one with NO AGP4x
support.  More specifically VT82C693A North bridge and VT82C596B South 
bridge.  Kernel does detect upto UDMA 2 or ATA-33 and the chipset.  
Disabling the UDMA makes it ok but I don't want to disable the UDMA.

The motherboard is an ASUS P3V133.  I have the same setup at home using
an ASUS P3B-F with an Intel BX chipset, works fine at UDMA 2.
>How-To-Repeat:
Turn on UDMA from the BIOS any 0,1,2,3,4 will repeat this problem.
I have done this 3 times.  Installation will only work with UDMA disabled.

>Fix:


>Release-Note:
>Audit-Trail:

From: Jeff Blaine <jblaine@linus.mitre.org>
To: freebsd-gnats-submit@freebsd.org, lyamog@infiniteinfo.com
Cc:  
Subject: Re: kern/18335: FreeBSD 4.0 has a "WRITE command timeout - resetting" 
 problem on VIA chipset
Date: Tue, 08 Aug 2000 10:03:28 -0400

 Count me in on this one, only nothing I have tried will fix it and I
 am completely hosed right now.
 
 My Celeron 300A running on an Abit BH6 (Intel BX chipset, not VIA)
 has the same problem.  I am completely unable to install 4.0-RELEASE
 or 4.1-RELEASE and have no working FreeBSD box.
 
 Turning off UDMA does NOT fix the problem in my situation.
 
 Changing the PIO mode to any other setting in the BIOS does NOT
 fix the problem in my situation.
 
 My machine is NOT overclocked.
 
 ad0: WRITE command timeout - resetting
 ata0: resetting devices .. done
 
Responsible-Changed-From-To: freebsd-bugs->sos 
Responsible-Changed-By: sheldonh 
Responsible-Changed-When: Tue Aug 8 07:45:34 PDT 2000 
Responsible-Changed-Why:  
Over to the maintainer. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=18335 
State-Changed-From-To: open->closed 
State-Changed-By: sos 
State-Changed-When: Tue Nov 14 00:23:42 PST 2000 
State-Changed-Why:  
Please try4.2 or later, if the problem persists contact me with the 
boot details HW config etc etc. 


http://www.freebsd.org/cgi/query-pr.cgi?pr=18335 

From: mark tinguely <tinguely@web.cs.ndsu.NoDak.edu>
To: freebsd-gnats-submit@FreeBSD.org, lyamog@infiniteinfo.com
Cc:  
Subject: Re: kern/18335: FreeBSD 4.0 has a "WRITE command timeout - resetting" 
 problem on VIA chipset
Date: Fri, 08 Dec 2000 09:50:54 -0600

 FYI:
 
 The ata driver still gives "WRITE command timeouts" in 4.2-RELEASE.
 
 I updated a machine from 3.5-RELEASE to 4.2-RELEASE and hit this
 problem. I tried both
 DMA and the default non-DMA in the ata driver, with no change. BTW,
 someone else posted
 to the FreeBSD newsgroup with a "READ command  timeout" problem on Intel
 PIIX4 ATA33
 controller.
 
 I compiled the kernel with the wd driver and this machine is now running
 okay.
 
 This machine is also a Celeron running on a cheap (for shame on me) FIC
 motherboard.
 Below is the output with the ata driver:
 
 pcib2: <VIA 82C598MVP (Apollo MVP3) PCI-PCI (AGP) bridge> at device 1.0
 on pci0
 pci1: <PCI bus> on pcib2
 isab0: <VIA 82C596B PCI-ISA bridge> at device 7.0 on pci0
 isa0: <ISA bus> on isab0
 atapci0: <VIA 82C596 ATA33 controller> port 0xe000-0xe00f at device 7.1
 on pci0
 ata0: at 0x1f0 irq 14 on atapci0
 ad0: 8063MB <Maxtor 90845D4> [16383/16/63] at ata0-master UDMA33
 Mounting root from ufs:/dev/ad0s1a
 ad0: WRITE command timeout tag=0 serv=0 - resetting
 ata0: resetting devices .. done
 
 
 
>Unformatted:
