From nobody@FreeBSD.org  Fri May 28 02:01:49 2004
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6765016A4D1
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 28 May 2004 02:01:49 -0700 (PDT)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5DB8243D41
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 28 May 2004 02:01:49 -0700 (PDT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.12.11/8.12.11) with ESMTP id i4S91N0q066709
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 28 May 2004 02:01:23 -0700 (PDT)
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.12.11/8.12.11/Submit) id i4S91NeM066695;
	Fri, 28 May 2004 02:01:23 -0700 (PDT)
	(envelope-from nobody)
Message-Id: <200405280901.i4S91NeM066695@www.freebsd.org>
Date: Fri, 28 May 2004 02:01:23 -0700 (PDT)
From: Daan Goedkoop <dgoedkoop@web.de>
To: freebsd-gnats-submit@FreeBSD.org
Subject: UltraDMA on VIA VT82C586 leads to DMA WRITE timeouts
X-Send-Pr-Version: www-2.3

>Number:         67280
>Category:       i386
>Synopsis:       UltraDMA on VIA VT82C586 leads to DMA WRITE timeouts
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    sos
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri May 28 02:10:25 PDT 2004
>Closed-Date:    Mon Aug 16 12:06:27 GMT 2004
>Last-Modified:  Mon Aug 30 13:10:27 GMT 2004
>Originator:     Daan Goedkoop
>Release:        5.2.1
>Organization:
>Environment:
Bug is present on at least 4.8, 4.9, 5.0, 5.1 and 5.2. I am not going to download boot floppies for them all.
>Description:
When I try to install FreeBSD on my computer, sometimes the computer pauses for a few seconds and then a DMA WRITE timeout message appears. As the installation continues, this occurs more and more often, and also multiple times after eachother. Eventually, the installation progress practically stalls due to this bug.
>How-To-Repeat:
Re-enable UltraDMA on a computer that has the VIA VT82C586 controller, as it was by default.
>Fix:
I reported this bug before, and then disabling UltraDMA was the solution.

Actually, I don't see this as a fix, as Windows, Linux, NetBSD and OpenBSD all support UltraDMA properly on the VIA VT82C586, and additionally the ata(4) man page implicitly says that UltraDMA is supported for it.
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: bms 
State-Changed-When: Sat Jul 3 06:57:50 GMT 2004 
State-Changed-Why:  
Please extract a full dmesg (as per the Handbook) of the symptoms 
you're experiencing and include a full kernel configuration. 


Responsible-Changed-From-To: freebsd-bugs->sos 
Responsible-Changed-By: bms 
Responsible-Changed-When: Sat Jul 3 06:57:50 GMT 2004 
Responsible-Changed-Why:  
sos@ is the ata(4) maintainer 

http://www.freebsd.org/cgi/query-pr.cgi?pr=67280 
State-Changed-From-To: feedback->closed 
State-Changed-By: sos 
State-Changed-When: Mon Aug 16 12:04:47 GMT 2004 
State-Changed-Why:  
Feedback timeout.  
Verified that we can use DMA on the '586 here in the lab.. 

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

From: "Daan Goedkoop" <dgoedkoop@gmx.net>
To: <freebsd-gnats-submit@FreeBSD.org>, <dgoedkoop@web.de>
Cc:  
Subject: Re: i386/67280: UltraDMA on VIA VT82C586 leads to DMA WRITE timeouts
Date: Mon, 30 Aug 2004 14:59:58 +0200

 Sorry, I forgot to check for replies, and so I didn't see you requested
 additional information. Anyways, I tried it again, so now I can provide some
 extra information. Below is the output of dmesg. Notes:
 - My harddisk is really 40 GB, but needs to be set into 32 GB mode for the
 BIOS to recognise it. I don't think this is the problem, as without DMA
 everything works fine, and IIRC the problem also occured with a 6 GB Western
 Digital hard drive.
 - I do not know why ls(1) crashes everytime I use it, even when no DMA
 timeout occurs.
 - As I mentioned earlier, DMA works fine on Windows 98, Windows 2000, Linux,
 NetBSD and OpenBSD. Therefore I don't see how it can be a hardware problem,
 so I wonder why everything works fine on your test machine.
 
 Daan Goedkoop.
 
 Copyright (c) 1992-2004 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 4.10-RELEASE #0: Tue May 25 22:47:12 GMT 2004
     root@perseus.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
 Timecounter "i8254"  frequency 1193182 Hz
 CPU: Pentium II/Pentium II Xeon/Celeron (350.80-MHz 686-class CPU)
   Origin = "GenuineIntel"  Id = 0x652  Stepping = 2
 
 Features=0x183f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,
 PAT,PSE36,MMX,FXSR>
 real memory  = 134217728 (131072K bytes)
 avail memory = 125165568 (122232K bytes)
 Preloaded elf kernel "kernel" at 0xc0551000.
 Pentium Pro MTRR support enabled
 md0: Malloc disk
 Using $PIR table, 6 entries at 0xc00f85c0
 npx0: <math processor> on motherboard
 npx0: INT 16 interface
 pcib0: <Host to PCI bridge> on motherboard
 pci0: <PCI bus> on pcib0
 agp0: <VIA 82C691 (Apollo Pro) host to PCI bridge> mem 0xe0000000-0xe7ffffff
 at device 0.0 on pci0
 pcib1: <VIA 82C598MVP (Apollo MVP3) PCI-PCI (AGP) bridge> at device 1.0 on
 pci0
 pci1: <PCI bus> on pcib1
 pci1: <SiS 6326 SVGA controller> at 0.0
 isab0: <VIA 82C586 PCI-ISA bridge> at device 7.0 on pci0
 isa0: <ISA bus> on isab0
 atapci0: <VIA 82C586 ATA33 controller> port 0xffa0-0xffaf at device 7.1 on
 pci0
 ata0: at 0x1f0 irq 14 on atapci0
 ata1: at 0x170 irq 15 on atapci0
 uhci0: <VIA 83C572 USB controller> port 0xde00-0xde1f irq 10 at device 7.2
 on pci0
 usb0: <VIA 83C572 USB controller> on uhci0
 usb0: USB revision 1.0
 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
 uhub0: 2 ports with 2 removable, self powered
 pci0: <unknown card> (vendor=0x1106, dev=0x3040) at 7.3
 vr0: <VIA VT6105 Rhine III 10/100BaseTX> port 0xdc00-0xdcff mem
 0xefffff00-0xefffffff irq 10 at device 8.0 on pci0
 vr0: Ethernet address: 00:40:f4:8c:63:fb
 miibus0: <MII bus> on vr0
 ukphy0: <Generic IEEE 802.3u media interface> on miibus0
 ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 pci0: <unknown card> (vendor=0x1057, dev=0x5600) at 10.0 irq 10
 orm0: <Option ROM> at iomem 0xc0000-0xc7fff on isa0
 pmtimer0 on isa0
 fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
 fdc0: FIFO enabled, 8 bytes threshold
 fd0: <1440-KB 3.5" drive> on fdc0 drive 0
 atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
 atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
 kbd0 at atkbd0
 psm0: <PS/2 Mouse> irq 12 on atkbdc0
 psm0: model IntelliMouse, device ID 3
 vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
 sc0: <System console> 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
 ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode
 ppc0: FIFO with 16/16/16 bytes threshold
 plip0: <PLIP network interface> on ppbus0
 lpt0: <Printer> on ppbus0
 lpt0: Interrupt-driven port
 ppi0: <Parallel I/O> on ppbus0
 ad0: 32253MB <Maxtor 6E040L0> [65531/16/63] at ata0-master UDMA33
 acd0: DVD-ROM <SAMSUNG DVD-ROM SD-616E> at ata1-master PIO4
 acd1: CD-RW <AOPEN CD-RW CRW5232 1.02 20030718> at ata1-slave PIO4
 Mounting root from ufs:/dev/ad0s2a
 ad0: WRITE command timeout tag=0 serv=0 - resetting
 ata0: resetting devices .. done
 ad0: WRITE command timeout tag=0 serv=0 - resetting
 ata0: resetting devices .. done
 ad0: WRITE command timeout tag=0 serv=0 - resetting
 ata0: resetting devices .. done
 ad0: WRITE command timeout tag=0 serv=0 - resetting
 ata0: resetting devices .. done
 pid 114 (ls), uid 0: exited on signal 12 (core dumped)
 ad0: WRITE command timeout tag=0 serv=0 - resetting
 ata0: resetting devices .. done
 pid 115 (ls), uid 0: exited on signal 12 (core dumped)
 
>Unformatted:
