Subject: Re: VIA chipset problems - what is recommended solution / workaround?
To: None <port-i386@NetBSD.ORG>
From: Kent Polk <kent@goathill.org>
List: port-i386
Date: 05/13/2001 19:26:55
On 3 May 2001 17:10:00 -0500, Manuel Bouyer wrote:
> On Thu, May 03, 2001 at 09:22:18PM +0200, Ingolf Steinbach wrote:
>> Hi,
>> 
>> with the computer I bought recently (before I was aware of the VIA chipset
>> problems) I too get the "pciide0:0:0: lost interrupt" behaviour. See the
>> part from my dmesg output below.
>> 
>> What is the recommended solution or workaround for this? If I turn off
>> UDMA via the bios, everything seems to work (but of course it's unnecessary
>> slow). Is it possible to downgrade wd0 to an UDMA mode less than 5 via
>> config(8)?
> 
> Yes, see the wd(4) man page. But this won't help you in this case.
> The kernel isn't aware that your motherboard can do UDMA5 at the moment
> and will use UDMA2 (that's part of the problem)
> 
> however in the dmesg I notice the kernel doesn't use Ultra-DMA at all.
> Did you put flags to disable Ultra-DMA in your kernel config file ?

I thought I'd contribute a little bit of possibly interesting information.

I just picked up a :
wd1 at pciide0 channel 1 drive 0: <FUJITSU MPF3102AH>
wd1: drive supports 16-sector PIO transfers, LBA addressing
wd1: 9773 MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 20016348 sectors
wd1: 32-bit data port
wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 4 (Ultra/66)

in addition to my :
wd0 at pciide0 channel 0 drive 0: <Maxtor 83201A6>
wd0: drive supports 16-sector PIO transfers, LBA addressing
wd0: 3060 MB, 6218 cyl, 16 head, 63 sec, 512 bytes/sect x 6267744 sectors
wd0: 32-bit data port
wd0: drive supports PIO mode 4, DMA mode 2

I have an Epox 8KTA3 with:

NetBSD 1.5R (GENERIC) #1: Tue Feb  6 20:45:15 CET 2001
    tron@lyssa.zhadum.de:/src/NetBSD-current/src/sys/arch/i386/compile/GENERIC
cpu0: AMD Athlon Model 4 (Thunderbird) (686-class), 1336.44 MHz
cpu0: features 183f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR>
cpu0: features 183f9ff<PGE,MCA,CMOV,FGPAT,PSE36,MMX,FXSR>
total memory = 255 MB
avail memory = 231 MB
using 3296 buffers containing 13184 KB of memory
BIOS32 rev. 0 found at 0xfb3c0
mainbus0 (root)
pci0 at mainbus0 bus 0: configuration mode 1
pci0: i/o space, memory space enabled
pchb0 at pci0 dev 0 function 0
pchb0: VIA Technologies VT8363 KT133 System Controller (rev. 0x03)
ppb0 at pci0 dev 1 function 0: VIA Technologies VT8363 KT133 PCI to AGP Bridge
(rev. 0x00)
pci1 at ppb0 bus 1
pci1: i/o space, memory space enabled
vga1 at pci1 dev 0 function 0: Matrox MGA G200 AGP (rev. 0x01)
wsdisplay0 at vga1: console (80x25, vt100 emulation)
pcib0 at pci0 dev 7 function 0
pcib0: VIA Technologies VT82C686A (Apollo KX133) PCI-ISA Bridge (rev. 0x40)
pciide0 at pci0 dev 7 function 1: VIA Tech VT82C586A IDE Controller (rev. 0x06)
pciide0: bus-master DMA support present
pciide0: primary channel configured to compatibility mode


When I run the MPF3102AH as wd0, it experiences all of the
"pciide0:0:0: lost interrupt" behaviours that have been mentioned.
Basically it can't run as wd0.

However, it runs just fine as wd1... Right now I'm booting off of
wd1 and it's working great.

Any ideas as to why would running it off of the second controller
would work and running it off the first controller won't?