Subject: Continuing asc0 SCSI problems on DEC 3000/300
To: None <>
From: Paul Mather <>
List: port-alpha
Date: 01/24/2001 13:05:26
I'm still having flakiness problems with the current -current kernel,
except now it is more flaky than ever.  (My machine thinks it is a
Windoze machine these days in that it will crash quickly, and apparently
at random.:)

Although the latest kernel will now probe my CD-RW, for some reason it
probes it as asc0:6:1 instead of asc0:6:0 as in times past.  Also, I
still get "max sync rate 20.83MB/s" initially for my fast/narrow IBM
SCSI drive (later negotiated to 5.00MB/s).  IMHO, "20.83MB/s" just feels
wrong for some reason.  (Similarly for the "unrecognized MESSAGE
EXTENDED; sending REJECT" messages, which never happened before.)

I compiled the kernel with the DDB option this time.  I've been getting
panics in setrunqueue and other places.  With the latest kernel, it will
usually panic during multi-user boot, or not long thereafter.  Here is
the latest crash 'n' burn:


NetBSD/alpha 1.5_ALPHA FFS Primary Bootstrap
Jumping to entry point...

NetBSD/alpha 1.5_ALPHA Secondary Bootstrap, Revision 1.10
(paul@hawkwind, Jul 23 05:04:49 EDT 2000)

VMS PAL rev: 0x100010538
OSF PAL rev: 0x2012d
Switch to OSF PAL code succeeded.

Boot flags: A
2252344+272032 [85+151920+81769]=0x2a1990

Entering netbsd at 0xfffffc00003010c0...
[ using 234680 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.5Q (HAWKWIND) #3: Wed Jan 24 11:12:49 EST 2001
DEC 3000 - M300, 150MHz, s/n
8192 byte page size, 1 processor.
total memory = 256 MB
(2048 KB reserved for PROM, 254 MB used by NetBSD)
avail memory = 180 MB
using 8125 buffers containing 65000 KB of memory
mainbus0 (root)
cpu0 at mainbus0: ID 0 (primary), 21064-1
tcasic0 at mainbus0
tc0 at tcasic0: 12.5 MHz clock
sfb0 at tc0 slot 6 offset 0x2000000: 1280 x 1024, 8bpp
wsdisplay0 at sfb0
ioasic0 at tc0 slot 5 offset 0x0: slow mode
le0 at ioasic0 offset 0xc0000: address 08:00:2b:95:61:12
le0: 32 receive buffers, 8 transmit buffers
zsc0 at ioasic0 offset 0x100000
vsms0 at zsc0 channel 0
wsmouse0 at vsms0
zstty0 at zsc0 channel 1 (console i/o)
                                      zsc1 at ioasic0 offset 0x180000
lkkbd0 at zsc1 channel 0
wskbd0 at lkkbd0
zsc1: channel 1 not configured
mcclock0 at ioasic0 offset 0x200000: mc146818 or compatible
bba0 at ioasic0 offset 0x240000
audio0 at bba0: full duplex, mmap
tcds0 at tc0 slot 4 offset 0x0: TurboChannel Dual SCSI (baseboard)
tcds0: fast mode set for chip 0
asc0 at tcds0 chip 0: NCR53C94, 25MHz, SCSI ID 7
scsibus0 at asc0: 8 targets, 8 luns per target
le (LANCE Ethernet) at tc0 slot 0 offset 0x0 not configured
scsibus0: waiting 2 seconds for devices to settle...
probe(asc0:0:0): max sync rate 20.83MB/s
asc0: target 0: sync negotiation
sd0 at scsibus0 target 0 lun 0: <IBM OEM, DCHS04Z, 6161> SCSI2 0/direct
sd0(asc0:0:0): max sync rate 5.00MB/s
sd0: 4340 MB, 6077 cyl, 9 head, 162 sec, 512 bytes/sect x 8888543
probe(asc0:4:0): unrecognized MESSAGE EXTENDED; sending REJECT
probe(asc0:4:0): max sync rate 10.00MB/s
asc0: target 4: sync negotiation
sd1 at scsibus0 target 4 lun 0: <IBMRISC, DFHSS4W, 4242> SCSI2 0/direct
sd1(asc0:4:0): max sync rate 5.00MB/s
sd1: 4303 MB, 4392 cyl, 16 head, 125 sec, 512 bytes/sect x 8813870
asc0: target 5: sync negotiation
sd2 at scsibus0 target 5 lun 0: <DEC, RX26     (C) DEC, 0070> SCSI1
0/direct removable
sd2: drive offline
asc0: target 6: sync negotiation
cd0 at scsibus0 target 6 lun 0: <YAMAHA, CRW8824S, 1.00> SCSI2 5/cdrom
probe(asc0:6:1): max sync rate 5.00MB/s
pool_get: fdescpl: curpage NULL, nitems 4294966272
panic: pool_get: nitems inconsistent

Stopped in pid 0 (swapper) at   cpu_Debugger+0x4:       ret
db> trace
cpu_Debugger() at cpu_Debugger+0x4
panic() at panic+0xfc
_pool_get() at _pool_get+0x320
fdcopy() at fdcopy+0x3c
fork1() at fork1+0x2bc
main() at main+0x62c
locorestart() at locorestart+0x68
--- root of call graph ---

Has anyone else been suffering these problems?  I've run the PROM tests,
and everything passes except my framebuffer (which has had bad RAM for
ages).  Could the fact that I now have wscons support compiled in be
causing these problems, given the duff framebuffer???  (I recently
switched over to the TCWSCONS kernel config file, with slight




"Without music to decorate it, time is just a bunch of boring production
 deadlines or dates by which bills must be paid."
        --- Frank Vincent Zappa