[ On Tuesday, September 3, 2002 at 22:41:10 (+0100), David Brownlee wrote: ]
> Subject: Re: 1.6 on IPC (tagged queuing bug still there)
>
> 	If its been seen on a sparc10 and IPC I believe they have quite
> 	different esp revisions.

Yes, though if it's not every SS10 then perhaps it's just a plain old
disk device issue?

The SS10 must have an ESP200, no?

The EPS100 apparently requires that the driver implements tagged queuing
with a different mechanism than "normal" for more modern hardware.
Perhaps that different mechanism is more sensitive to problems in some
drives (i.e. the drive works fine with tagged queuing on more modern
host adapters, but won't work with the ESP100).

There are more details in the "1.6 woes" thread that started back in July.

I had no trouble with 1.3.2, 1.4, or now 1.5W doing basic testing on an
SS1 with its on-board ESP100, though recently the disk in that machine
started getting too many bad sectors to do any more than just boot (and
I'm not 100% sure that disk could to tagged queuing ... no, according to
the following it probably doesn't):

Booting from: sd(0,0,0) 
>> NetBSD/sparc Secondary Boot, Revision 1.9
>> (woods@sometimes, Wed Apr  4 20:03:42 EDT 2001)
Booting netbsd
2394842+93672+232048 [68+158960+118222]=0x2ec000
[ using 277704 bytes of netbsd ELF symbol table ]

Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001
    The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
    The Regents of the University of California.  All rights reserved.

NetBSD 1.5W (GENERIC) #14: Sun Jul  1 01:35:50 EDT 2001
    woods@sometimes:/build/NetBSD-obj/arch/sparc/compile/GENERIC
total memory = 16336 KB
avail memory = 12464 KB
using 128 buffers containing 512 KB of memory
bootpath: /sbus0/esp0/sd@0,0
mainbus0 (root): Sun 4/60
cpu0 at mainbus0: MB86900/1A or L64801 @ 20 MHz, WTL3170/2 FPU
cpu0: 64K byte write-through, 16 bytes/line, sw flush: cache enabled
memreg0 at mainbus0 ioaddr 0xf4000000
clock0 at mainbus0 ioaddr 0xf2000000: mk48t02: hostid 5100cff4
timer0 at mainbus0 ioaddr 0xf3000000 ipl 10 delay constant 7
auxreg0 at mainbus0 ioaddr 0xf7400000
zs0 at mainbus0 ioaddr 0xf1000000 ipl 12 softpri 6
zstty0 at zs0 channel 0 (console i/o)
zstty1 at zs0 channel 1
zs1 at mainbus0 ioaddr 0xf0000000 ipl 12 softpri 6
kbd0 at zs1 channel 0
ms0 at zs1 channel 1
fdc0 at mainbus0 ioaddr 0xf7200000 ipl 11 softpri 4: chip 82072
audioamd0 at mainbus0 ioaddr 0xf7201000 ipl 13 softpri 4
audio0 at audioamd0: full duplex
sbus0 at mainbus0 ioaddr 0xf8000000: clock = 25 MHz
dma0 at sbus0 slot 0 offset 0x400000: dma rev 1
esp0 at sbus0 slot 0 offset 0x800000 level 3: ESP100, 25MHz, SCSI ID 7
scsibus0 at esp0: 8 targets, 8 luns per target
le0 at sbus0 slot 0 offset 0xc00000 level 5: address 08:00:20:08:78:30
le0: 8 receive buffers, 2 transmit buffers
scsibus0: waiting 2 seconds for devices to settle...
sd0 at scsibus0 target 3 lun 0: <MAXTOR, 7120SCS, 3235> SCSI1 0/direct fixed
sd0: 121 MB, 1498 cyl, 4 head, 41 sec, 512 bytes/sect x 248502 sectors
sd0: async, 8-bit transfers
root on sd0a dumps on sd0b
WARNING: clock gained 27 days -- CHECK AND RESET THE DATE!
root file system type: ffs

[[ hmmm... this time it made it all the way to muli-user mode! ]]

-- 
								Greg A. Woods

+1 416 218-0098;            <g.a.woods@ieee.org>;           <woods@robohack.ca>
Planix, Inc. <woods@planix.com>; VE3TCP; Secrets of the Weird <woods@weird.com>