From nobody@FreeBSD.ORG  Mon Oct 23 02:41:03 2000
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id ADB1D37B4C5; Mon, 23 Oct 2000 02:41:03 -0700 (PDT)
Message-Id: <20001023094103.ADB1D37B4C5@hub.freebsd.org>
Date: Mon, 23 Oct 2000 02:41:03 -0700 (PDT)
From: toddpw@apricot.com
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@FreeBSD.org
Subject: unstable UDMA on Iwill VD133PL v1.6 (Apollo MVP3, IDE rev 0x10)
X-Send-Pr-Version: www-1.0

>Number:         22240
>Category:       i386
>Synopsis:       unstable UDMA on Iwill VD133PL v1.6 (Apollo MVP3, IDE rev 0x10)
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Oct 23 02:50:00 PDT 2000
>Closed-Date:    Tue May 29 06:41:17 PDT 2001
>Last-Modified:  Tue May 29 06:41:57 PDT 2001
>Originator:     Todd Whitesel
>Release:        4.1, 4.1.1
>Organization:
Anime Expo
>Environment:
FreeBSD yuri.toddpw.net 4.1.1-RELEASE FreeBSD 4.1.1-RELEASE #0: Tue Sep 26 00:46:59 GMT 2000     jkh@narf.osd.bsdi.com:/usr/src/sys/compile/GENERIC  i386

>Description:
Problem occurs after roughly 20 minutes of continual load.
Irreproducible SEGV's, and kernel mode segfaults that panic, or spontaneous reboots.
Happens with both UDMA66 and UDMA33 drives.
Forcing PIO mode with "sysctl -w hw.atamodes=pio,pio,pio,pio" restores sanity.
However it is not clear how to install such a machine without risk of corruption.
NetBSD 1.4.2 and 1.5ALPHA2 have similar trouble, but exhibit symptoms quicker (5 minutes instead of 20).
[NetBSD reports the IDE controller as VIA Technologies VT82C586A IDE Controller (IDE mass storage, interface 0x8a, revision 0x10)]

dmesg:

FreeBSD 4.1.1-RELEASE #0: Tue Sep 26 00:46:59 GMT 2000
    jkh@narf.osd.bsdi.com:/usr/src/sys/compile/GENERIC
Timecounter "i8254"  frequency 1193182 Hz
CPU: Pentium III/Pentium III Xeon/Celeron (731.47-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x683  Stepping = 3
  Features=0x383f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PA
T,PSE36,MMX,FXSR,XMM>
real memory  = 134152192 (131008K bytes)
avail memory = 126459904 (123496K bytes)
Preloaded elf kernel "kernel" at 0xc0416000.
Pentium Pro MTRR support enabled
md0: Malloc disk
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <Host to PCI bridge> on motherboard
pci0: <PCI bus> on pcib0
pcib2: <VIA 82C598MVP (Apollo MVP3) PCI-PCI (AGP) bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib2
pci1: <S3 Trio3D/2X graphics accelerator> at 0.0
isab0: <VIA 82C686 PCI-ISA bridge> at device 7.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <VIA 82C686 ATA66 controller> port 0xd000-0xd00f at device 7.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
ed0: <NE2000 PCI Ethernet (RealTek 8029)> port 0xe800-0xe81f irq 12 at device 11
.0 on pci0
ed0: address 00:80:c8:c0:e7:36, type NE2000 (16 bit)
pcib1: <Host to PCI bridge> on motherboard
pci2: <PCI bus> on pcib1
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
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 (EPP/NIBBLE) in COMPATIBLE mode
plip0: <PLIP network interface> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
ata1-slave: ata_command: timeout waiting for intr
ata1-slave: identify failed
ad0: 9729MB <ST310210A> [19767/16/63] at ata0-master using UDMA66
acd0: CDROM <FX162T4> at ata1-master using PIO3
Mounting root from ufs:/dev/ad0s1a

>How-To-Repeat:
Order an Iwill VD133Pro from www.motherboards.com.
You actually get a VD133PL but the price is correct so it's no big deal.
Mine were version 1.6, the current version according to www.iwill.net.
Set up a reasonable system (P3 733EB, 128MB PC133, Barracuda II ATA66).
Install FreeBSD 4.1 or 4.1.1; if that succeeds then do some compiles.
Two looping builds in parallel usually kill the machine in 20 minutes.
>Fix:
Use FreeBSD 2.2.6 or other earlier version which does not have atapci0.
Disable atapci0 and force the use of wdc0/wdc1 which are PIO only.

These are only workarounds however, and it is not clear how to bootstrap such a machine with just the install CD.


>Release-Note:
>Audit-Trail:

From: =?koi8-r?B?4c7E0sXKIP7F0s7P1w==?= <ache@nagual.pp.ru>
To: toddpw@apricot.com
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: i386/22240: unstable UDMA on Iwill VD133PL v1.6 (Apollo MVP3, IDE rev 0x10)
Date: Mon, 23 Oct 2000 13:59:40 +0400

 On Mon, Oct 23, 2000 at 02:41:03AM -0700, toddpw@apricot.com wrote:
 > Forcing PIO mode with "sysctl -w hw.atamodes=pio,pio,pio,pio" restores sanity.
 > However it is not clear how to install such a machine without risk of corruption.
 > NetBSD 1.4.2 and 1.5ALPHA2 have similar trouble, but exhibit symptoms quicker (5 minutes instead of 20).
 > [NetBSD reports the IDE controller as VIA Technologies VT82C586A IDE Controller (IDE mass storage, interface 0x8a, revision 0x10)]
 
 I can confirm this problem, it occurse for me with Pro133A/Pro133Z VIA
 chipsets (ASUS motherboards). Setting atamodes to pio really not fix the
 problem, but makes it much harder to occurse, so I don't think it is ATA
 driver but VIA chipset itself.
 
 -- 
 Andrey A. Chernov
 http://ache.pp.ru/
 

From: Soren Schmidt <sos@freebsd.dk>
To: toddpw@apricot.com
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: i386/22240: unstable UDMA on Iwill VD133PL v1.6 (Apollo MVP3, IDE rev 0x10)
Date: Mon, 23 Oct 2000 12:58:50 +0200 (CEST)

 It seems toddpw@apricot.com wrote:
 > Problem occurs after roughly 20 minutes of continual load.
 > Irreproducible SEGV's, and kernel mode segfaults that panic, or spontaneous reboots.
 > Happens with both UDMA66 and UDMA33 drives.
 > Forcing PIO mode with "sysctl -w hw.atamodes=pio,pio,pio,pio" restores sanity.
 > However it is not clear how to install such a machine without risk of corruption.
 > NetBSD 1.4.2 and 1.5ALPHA2 have similar trouble, but exhibit symptoms quicker (5 minutes instead of 20).
 > [NetBSD reports the IDE controller as VIA Technologies VT82C586A IDE Controller (IDE mass storage, interface 0x8a, revision 0x10)]
 
 > atapci0: <VIA 82C686 ATA66 controller> port 0xd000-0xd00f at device 7.1 on pci0
 > ata0: at 0x1f0 irq 14 on atapci0
 > ata1: at 0x170 irq 15 on atapci0
 > ata1-slave: identify failed
 > ad0: 9729MB <ST310210A> [19767/16/63] at ata0-master using UDMA66
 > acd0: CDROM <FX162T4> at ata1-master using PIO3
 
 Are you using a prober ATA66 compliant cable ?
 
 At any rate I have the same VIA chip (82c686)  on two boards here, and I have
 absolutely _no_ problems with them, however you say it should be a 82c586
 are you sure of that ? (check the mothernboard itself), as this could be
 a screwup in versioning of the VIA chips (they have a weird idea of how
 to differentiate the different chips)...
 
 -Sren
 

From: "Todd P. Whitesel" <toddpw@apricot.com>
To: sos@freebsd.dk (Soren Schmidt)
Cc: toddpw@apricot.com, freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: i386/22240: unstable UDMA on Iwill VD133PL v1.6 (Apollo MVP3, IDE rev 0x10)
Date: Mon, 23 Oct 2000 13:48:33 -0700 (PDT)

 > Are you using a prober ATA66 compliant cable ?
 
 It's the one Iwill supplies with the motherboard, and looks right.
 Symptoms were the same when I replaced the UDMA66 drive with a UDMA33 drive.
 
 > At any rate I have the same VIA chip (82c686)  on two boards here, and I have
 > absolutely _no_ problems with them, however you say it should be a 82c586
 
 Just reporting what dmesg said, nothing more than that.
 
 > are you sure of that ? (check the mothernboard itself), as this could be
 > a screwup in versioning of the VIA chips (they have a weird idea of how
 > to differentiate the different chips)...
 
 That would appear to be the case.
 
 	VT82C686A
 	0025CG   TAIWAN
 	13C0N7100
 
 -- 
 Todd Whitesel					Anime Expo Information at
 toddpw @ apricot.com				http://www.anime-expo.org
 

From: "Todd P. Whitesel" <toddpw@apricot.com>
To: toddpw@apricot.com (Todd P. Whitesel)
Cc: sos@freebsd.dk, toddpw@apricot.com,
	freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: i386/22240: unstable UDMA on Iwill VD133PL v1.6 (Apollo MVP3, IDE rev 0x10)
Date: Tue, 24 Oct 2000 12:02:45 -0700 (PDT)

 FYI the NetBSD PR for this is kern/11293
 
 -- 
 Todd Whitesel					Anime Expo Information at
 toddpw @ apricot.com				http://www.anime-expo.org
 

From: "Todd P. Whitesel" <toddpw@apricot.com>
To: toddpw@apricot.com (Todd P. Whitesel)
Cc: toddpw@apricot.com, sos@freebsd.dk,
	freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: i386/22240: unstable UDMA on Iwill VD133PL v1.6 (Apollo MVP3, IDE rev 0x10)
Date: Wed, 25 Oct 2000 01:41:12 -0700 (PDT)

 --- NOTE ---
 
 After two days of success, the PIO-only tests have exhibited similar failures
 on both FreeBSD 4.1.1 and NetBSD 1.5_ALPHA2.
 
 So that would suggest that this is not a strictly UDMA issue after all,
 but some subtle problem with the VIA 133 chipset... yuck.
 
 -- 
 Todd Whitesel					Anime Expo Information at
 toddpw @ apricot.com				http://www.anime-expo.org
 

From: "Bryan K. Ogawa" <bkogawa@primenet.com>
To: "Todd P. Whitesel" <toddpw@apricot.com>
Cc: <sos@freebsd.dk>, <freebsd-gnats-submit@FreeBSD.ORG>
Subject: Re: i386/22240: unstable UDMA on Iwill VD133PL v1.6 (Apollo MVP3,
 IDE rev 0x10)
Date: Sun, 11 Feb 2001 02:06:21 -0800 (PST)

 Has there been any resolution to this problem (other than avoiding VIA 133
 chipset mobos?)  I have a FIC 503+ (MVP3 chipset, the 586 according to
 4.2-RELEASE and a 586B according to the writing on the chip) which
 reliably fails to install by panicing as I attempt to install bits.  I
 even replaced the HD in hopes that this would help.
 
 Of course, it could be some entirely different problem for me.
 
 -- 
 bryan k ogawa  <bkogawa@primenet.com>   http://www.primenet.com/~bkogawa/
 
 

From: "Todd P. Whitesel" <toddpw@apricot.com>
To: bkogawa@primenet.com (Bryan K. Ogawa)
Cc: toddpw@apricot.com, sos@freebsd.dk,
	freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: i386/22240: unstable UDMA on Iwill VD133PL v1.6 (Apollo MVP3, IDE rev 0x10)
Date: Sun, 11 Feb 2001 20:58:18 -0800 (PST)

 > Has there been any resolution to this problem (other than avoiding VIA 133
 > chipset mobos?)  I have a FIC 503+ (MVP3 chipset, the 586 according to
 > 4.2-RELEASE and a 586B according to the writing on the chip) which
 > reliably fails to install by panicing as I attempt to install bits.  I
 > even replaced the HD in hopes that this would help.
 
 My resolution was to use an ASUS CUSL2 (i815E) mobo -- but one of the drives
 seems to be having problems in ATA66 mode: ata0 device disappeared and some
 such (so I took the drive out of service in desperation, I finally started
 running more tests this weekend as a matter of fact).
 
 This is the first and last time I try to build a server out of current
 generation PC hardware. I almost went with a PC100/UDMA33/440BX system
 and if I had done that, I would have two fully working servers now and
 not flushed five weeks of spare time down the toilet.
 
 -- 
 Todd Whitesel					Anime Expo Information at
 toddpw @ apricot.com				http://www.anime-expo.org
 
State-Changed-From-To: open->closed 
State-Changed-By: sos 
State-Changed-When: Tue May 29 06:41:17 PDT 2001 
State-Changed-Why:  
There is no outstanding problems with the VIA chips anymore, 
so if problem persists its more likely hardware. 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=22240 
>Unformatted:
