I just compiled a 1.5Q kernel, Dec 29 sources, and now I get:

esp0 at obio0: address 0x83f000: NCR53C96, 25MHz, SCSI ID 7
scsibus0 at esp0: 8 targets, 8 luns per target
[ ... ]
scsibus0: waiting 2 seconds for devices to settle...
esp0: !TC on MSG OUT [intr 10, stat 82, step 2] prevphase 6, resid 0
sd0 at scsibus0 target 0 lun 0: <QUANTUM, FIREBALL540S, 1Q09> SCSI2 0/direct fixed
sd0: 520 MB, 3835 cyl, 2 head, 138 sec, 512 bytes/sect x 1065235 sectors
sd1 at scsibus0 target 1 lun 0: <IBM, DFHSS2F, 4141> SCSI2 0/direct fixed
sd1: 2150 MB, 4390 cyl, 8 head, 125 sec, 512 bytes/sect x 4404489 sectors
esp0: !TC on MSG OUT [intr 10, stat 82, step 2] prevphase 6, resid 0
cd0 at scsibus0 target 3 lun 0: <SONY, CD-ROM CDU-8003A, 1.9a> SCSI2 5/cdrom removable
esp0: !TC on MSG OUT [intr 10, stat 82, step 2] prevphase 6, resid 0
uk0 at scsibus0 target 4 lun 0: <HP, C2500A, 3332> SCSI2 3/processor fixed
uk0: unknown device

Those "!TC on MSG OUT" messages weren't there before...

But I've got an really weird problem, which probably isn't even related
to that: "ls" no longer works; "ls -a" for example shows nothing at all,
not even "." and "..". However, if I know the name of a file, I can
still "cat" it. I sent a PR (11731) about ls not showing files in the
lower layer of a union mount, if the lower layer is a NFS filesystem,
but in this case, it's a plain FFS filesystem (the root directory).

Anyone else seeing this? Centris 660av, btw, which doesn't use the DAFB
"quick SCSI" code that many other Quadras use...
-- 
Name: Dave Huang     |   Mammal, mammal / their names are called /
INet: khym@bga.com   |   they raise a paw / the bat, the cat /
FurryMUCK: Dahan     |   dolphin and dog / koala bear and hog -- TMBG
Dahan: Hani G Y+C 25 Y++ L+++ W- C++ T++ A+ E+ S++ V++ F- Q+++ P+ B+ PA+ PL++