On Tue, 4 Jul 2006 23:50:25 +0200
Manuel Bouyer <bouyer@antioche.eu.org> wrote:
> On Tue, Jul 04, 2006 at 02:59:48PM +0200, Lars Nordlund wrote:
> > Jul  4 13:48:07 glengoyne /netbsd: satalink0:0:0: wait timed out
> > Jul  4 13:48:07 glengoyne /netbsd: wd0h: device timeout reading fsbn 136892512 o f 136892512-136892639 (wd0 bn 199803052; cn 198217 tn 5 sn 1), retrying

> Are you sure this is not a WD_QUIRK_SPLIT_MOD15_WRITE issue ?

Well, it just locked up with mod15_write, so I guess not. When I come
to think of it, it is probably PR 31826 that is haunting my system.

Agh, the agony of SATA. Pain everywhere. The other day I put this

pdcsata0 at pci2 dev 2 function 0
pdcsata0: Promise PDC40718 SATA300 controller (rev. 0x02)
pdcsata0: interrupting at ivec 14
pdcsata0: bus-master DMA support present

in this

NetBSD 3.99.21 sparc64

and using the disk gives a lot of these

pdcsata0:3:0: lost interrupt
        type: ata tc_bcount: 16384 tc_skip: 0
pdcsata0:3:0: lost interrupt
        type: ata tc_bcount: 10240 tc_skip: 0

The controller does however recover, so the system is at least usable.
Have not had time to investigate any further. This time the disk is a:

wd1 at atabus5 drive 0: <SAMSUNG HD300LJ>
wd1: drive supports 16-sector PIO transfers, LBA48 addressing
wd1: 279 GB, 581421 cyl, 16 head, 63 sec, 512 bytes/sect x 586072368
sectors wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 7
wd1(pdcsata0:3:0): using PIO mode 4, Ultra-DMA mode 6 (Ultra/133)
(using DMA)

I thought steering clear of Seagate was enough, but buying the only SATA
controller available in town, _before_ reading through the PR database
and the cvs log for the driver proved to be my downfall.


Best regards,
	Lars Nordlund