Subject: Re: SBC probs
To: Hauke Fath <saw@sun0.urz.uni-heidelberg.de>
From: Hauke Fath <saw@sun0.urz.uni-heidelberg.de>
List: port-mac68k
Date: 09/07/1996 15:19:35
At 22:15 Uhr 06.09.1996, Hauke Fath wrote:
>This has happened here for the third time with MOs now. Every time there
>was a SCSI related crash before the 'medium error' messages, every time
>this crash had happened during a write access.
To folIow-up my own mail:
I...
o formatted a different MO disk
o newfs'ed it under MacBSD
o mounted it under /usr/src
o said: "umask 002; tar -xpf /var/tmp/usr.src.tar &"
o and then...
## 7 Sept 1996
#
# -current sbc kernel of 25 Jun, splimp() = 4
# Write-back cache OFF
# NetBSD 1.2_ALPHA (EIBE) #5: Tue Jun 25 19:11:57 GMT 1996
# booted to serial console
#
# Action: Untar'ing large archive to (freshly formatted) MO
root:/usr # umask 002; tar -xpf /var/tmp/usr.src.tar &
[1] 132
root:/usr # sbc0: can not transfer more data
sbc0: aborting, but phase=DATA_OUT (reset)
sbc0: reset SCSI bus for TID=2 LUN=0
panic: ncr5380_scsi_cmd: polled request, abort failed
Stopped at _Debugger+0x6: unlk a6
db> t
_Debugger(19600,7ab8,89bbd8,1013,89bbf0) + 6
_panic(7ab8,0,7,2,3) + 34
_ncr5380_scsi_cmd(6c06f80) + 80
_scsi_done(6c06f80,79d0,6c048ac,6c04800,6c048ac) + 6a
_ncr5380_scsi_cmd(6c04800) + 352
_ncr5380_scsi_cmd(6c04800) + 1950
_ncr5380_scsi_cmd(6c04800) + 650
_ncr5380_scsi_cmd(6c06f80) + 110
_scsi_execute_xs(6c06f80) + 28
_scsi_scsi_cmd(6c05de0,89bd0c,6,6e49000,2000,4,2710,760ba8,1001) + 8a
_sdstart(6c02200,6c022a6,760ba8) + 1ca
_sdstrategy(760ba8,89bd70,283e2,89bd68,0) + b4
_spec_strategy(89bd68) + 24
_bwrite(760ba8,0,81a4,1,6c45700) + d8
_ffs_update(89bdd0) + 182
_ufs_makeinode(81a4,6c3b580,89bef8,89bf0c,89be94) + 168
_ufs_create(89be20) + 2a
_vn_open(89bee8,60e,1a4) + d8
_sys_open(6c4c300,89bf88,89bf80) + 72
_syscall(5) + 10a
_trap0() + e
db>
#
# And then again...
root:~ # fsck /dev/rsd2g
sd2(sbc0:2:0): illegal request, data = 80 20 01 00 00 00 c4 1d 10 00 00 00 22 60
6d b6 db 6d b6 db 1a 00 04 00
sd2: could not mode sense (4); using fictitious geometry
Sep 7 11:37:40 se30 /netbsd: sd2(sbc0:2:0): illegal request, data = 80 20 01 00
00 00 c4 1d 10 00 00 00 22 60 6d b6 db 6d b6 db 1a 00 04 00
Sep 7 11:37:40 se30 /netbsd: sd2(sbc0:2:0): illegal request, data = 80 20 01 00
00 00 c4 1d 10 00 00 00 22 60 6d b6 db 6d b6 db 1a 00 04 00
Sep 7 11:37:40 se30 /netbsd: sd2: could not mode sense (4); using fictitious ge
ometry
Sep 7 11:37:40 se30 /netbsd: sd2: could not mode sense (4); using fictitious ge
ometry
** /dev/rsd2g
** Last Mounted on /usr/src
** Phase 1 - Check Blocks and Sizes
sbc0: pdma_in: timeout len=8192 count=8192
sd2(sbc0:2:0): medium error, info = 361030 (decimal), data = 18 00 23 20 23 00 a
2 00 00 00 00 00 8a 21 6d b6 db 6d b6 db 08 05 82 45
Sep 7 11:37:51 se30 /netbsd: sbc0: pdma_in: timeout len=8192 count=8192
Sep 7 11:37:51 se30 /netbsd: sbc0: pdma_in: timeout len=8192 count=8192
Sep 7 11:37:52 se30 /netbsd: sd2(sbc0:2:0): medium error, info = 361030 (decima
l), data = 18 00 23 20 23 00 a2 00 00 00 00 00 8a 21 6d b6 db 6d b6 db 08 05 82
45
Sep 7 11:37:52 se30 /netbsd: sd2(sbc0:2:0): medium error, info = 361030 (decima
l), data = 18 00 23 20 23 00 a2 00 00 00 00 00 8a 21 6d b6 db 6d b6 db 08 05 82
45
CANNOT READ: BLK 360864
CONTINUE? [yn] n
Program terminated
root:~ #
Looks like I can reproduce the fault at will, doesn't it?
But then - the MacBSD 1.0 kernel was next to unusable (ADB), as was the 1.1
kernel (SCSI driver) - why break with good traditions...
No pun intended -- if I can help, say so.
hauke
---
"It's never straight up and down" (DEVO)