Subject: Re: apm (Re: Anyone running NetBSD on an IBM ThinkPad [A|T]21?)
To: None <port-i386@netbsd.org>
From: Chuck Cranor <chuck@xxx.research.att.com>
List: port-i386
Date: 01/22/2001 17:44:03
In article <20010122022800.1AEFB35C42@smb.research.att.com>,
Steven M. Bellovin <smb@research.att.com> wrote:
>I installed the patches to npx_isa.c and apm.c, and suspend works much 
>better now on my Thinkpad 600E.  

excellent.

>However, on two occasions, I also got the following messages:
>pciide0:0:0: lost interrupt
>        type: ata tc_bcount: 8192 tc_skip: 0
>pciide0:0:0: intr with DRQ (st=0x58)
>wd0: transfer error, downgrading to Ultra-DMA mode 1
>wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 1 (using DMA data transfers)
>wd0a: device timeout writing fsbn 30432 of 30432-30447 (wd0 bn 5156112; cn 5456 tn 3 sn 3), retrying
>wd0: soft error (corrected)

>I assume that that happened because a disk operation was in progress 
>during the suspend request.



now that i have a working apm i enabled "atactl wd0 setidle 5" on
my laptop (5 second idle powerdown) when running on battery.   as
a result i started getting these when ever the disk powered up (no
apm stuff going on):

pciide0:0:0: lost interrupt
        type: ata tc_bcount: 0 tc_skip: 0
pciide0:0:0: intr with DRQ (st=0x58)
wd0a: device timeout writing fsbn 243424 of 243424-243427 (wd0 bn 10509904; cn 1
1121 tn 8 sn 55), retrying
wd0: soft error (corrected)
pciide0:0:0: lost interrupt
        type: ata tc_bcount: 0 tc_skip: 0
pciide0:0:0: intr with DRQ (st=0x58)
wd0a: device timeout writing fsbn 243424 of 243424-243427 (wd0 bn 10509904; cn 1
1121 tn 8 sn 55), retrying
wd0: soft error (corrected)

...
pciide0:0:0: lost interrupt
        type: ata tc_bcount: 0 tc_skip: 0
pciide0:0:0: lost interrupt
        type: ata tc_bcount: 0 tc_skip: 0
(tons of these)
...

wd0a: device timeout writing fsbn 243440 of 243440-243447 (wd0 bn 10509920; cn 1
1121 tn 9 sn 8), retrying
pciide0:0:0: lost interrupt
        type: ata tc_bcount: 0 tc_skip: 0
wd0: soft error (corrected)

etc.


if i "atactl wd0 setidle 0" the disk runs constantly and the 
errors do not occur.

i was hoping Manuel might have some ideas about this?


chuck

-- 
Chuck Cranor                            http://www.research.att.com/info/chuck
Senior Technical Staff Member		chuck@research.att.com
Internet and Networking Systems Research Lab
AT&T Labs-Research, Florham Park, NJ