Subject: Re: pciide0:0:1: lost interrupt problem...
To: None <port-i386@netbsd.org>
From: Antti Kantee <pooka@iki.fi>
List: port-i386
Date: 06/20/1999 19:00:27
On Sat Jun 19 1999 at 21:17:46 -0500, Brian Stark wrote:

> I'm getting some problems on a 1.4/i386 system (Pentium 166MHz) and maybe
> some here can tell me what is going on.
> 
> PROBLEM:
> 
> While copying a large file (about 17.8MB in size) from a file system 
> located on a Seagate disk (disk wd1) to a file system on a Western 
> Digital disk (disk wd2) the following error messages appear in the 
> window for the xconsole program (X Window System is running):
> 
> pciide0:0:1: lost interrupt
>         type: ata
>         c_bcount: 32768
>         c_skip: 0
> pciide0:0:1: Bus-Master DMA error: missing interrupt, status=0x61
> wd1e: DMA error reading fsbn 275929 of 275929-275992 (wd1 bn 275992; cn 273 tn 12 sn 52), retrying
> wd1: soft error (corrected)
> pciide0:0:1: lost interrupt
>         type: ata
>         c_bcount: 32768
>         c_skip: 0
> pciide0:0:1: Bus-Master DMA error: missing interrupt, status=0x61
> wd1e: DMA error reading fsbn 520601 of 520601-520664 (wd1 bn 520664; cn 516 tn 8 sn 32), retrying
> wd1: soft error (corrected)

I can confirm the exact same problem on both a Pentium and a PentiumII
1.4 and 1.4C with a disk of the following kind:

wd2 at pciide0 channel 0 drive 1: <ST51080A>
wd2: drive supports 32-sector pio transfers, lba addressing                  
wd2: 1033MB, 2100 cyl, 16 head, 63 sec, 512 bytes/sect x 2116800 sectors     
wd2: 32-bits data port
wd2: drive supports PIO mode 4, DMA mode 2

I've been meaning to investigate this problem for a while already, but
can't do anything since I've loaned the disk a friend of mine (sneaky,
eh?).

I've noticed that this problem does not occur with wdc (or perhaps I've
just been in luck), so using wdc instead of pciide should help in using
the disk until the problem gets fixed.

> Anyone know why this is happening?? Sometimes the system allows me to
> continmue after these messages come out, other times the system is
> "frozen" and I can't do anything. When that happens, I have to reboot and
> then deal with problems like fsck'ing the file systems.

When you get a 'hard error' it's tilt-time.

-- 
  "Never underestimate the power of the Lite side of the \Source/"
 Antti Kantee   /       NetBSD        \  Citius, Altius,  \    / o
<pooka@iki.fi> / http://www.netbsd.org \     Levytys       \  /  |
______________/ Free Multiplatform UN*X \___________________\/__ |