Subject: Re: Kernel asm compile errors
To: , Allen Briggs <briggs@wasabisystems.com>
From: David Rogers <drogers@halo7.net>
List: port-mac68k
Date: 01/16/2001 22:18:15
These errors seem to happen to me most often when moving a large amounts of
data to my drive over the network.  I don=B9t know if this helps at all but i=
t
may be something to look into.

Dave

>=20
> Hmm,
>=20
> I'm not seeing the first line of messages, but I'm seeing the rest of it,
> often with varying amounts of "xfer":
>=20
> Jan  8 16:21:34 alchemy /netbsd: dmaintr: DMA xfer of zero xferred 65509
> Jan  8 16:21:34 alchemy /netbsd: esp0: !TC on DATA XFER [intr 10, stat 83=
,
> step
> 4
> ] prevphase 0, resid 1f0
> Jan  8 16:21:34 alchemy /netbsd: dmaintr: DMA xfer of zero xferred 65493
> Jan  8 16:21:34 alchemy /netbsd: esp0: !TC on DATA XFER [intr 10, stat 83=
,
> step
> 4
> ] prevphase 0, resid 7e0
>=20
> This is on a Quadra 650 with kernel from 1.5Q sources as of about Jan 3rd=
.
> These particular messages were seen while fsck'ing the filesystem during
> boot.  I usually see these now when I try to make a kernel or do any
> compiling.
>=20
> Not sure if that helps any or muddles the picture.
>=20
> Steve
>=20
> Allen Briggs wrote:
>=20
>>> While using anoncvs I got the following messages on my quadra 650:
>>>=20
>>> esp_quick_dma_setup called with 141e000, 0, 0, 0
>>> dmaintr: DMA xfer of zero xferred 65504
>>> esp0: !TC on DATA XFER [intr 10, stat 83, step 4] prevphase 0, resid 15=
f0
>>>=20
>>> sd0(esp0:0:0): esp0: timed out [ecb 0x1043068 (flags 0x1, dleft 15f0, s=
tat
>>> 0)], <state 5, nexus 0x1043068, phase(l 3, c 3, p 3), resid 0, msg(q 0,=
o 0)
>>>>=20
>>>=20
>>> I remember seeing something recently on the list about stuff like that.
>>> I've reproduced this several times with different numbers here and ther=
e.
>>=20
>> There does seem to be a small epidemic of this going around.  I'm
>> interested to know if the 65504 number is different for anyone, or
>> if the second 0 in:
>>=20
>>> esp_quick_dma_setup called with 141e000, 0, 0, 0
>>=20
>> is ever a 1.  That would mean that this is happening on reads as well
>> as on writes.
>>=20
>> Thanks,
>> -allen
>>=20
>> --
>>  Allen Briggs                     briggs@wasabisystems.com
>>  http://www.wasabisystems.com/    Quality NetBSD CDs, Sales, Support, Se=
rvice