Subject: Recent boot failures with -current?
To: None <port-sparc@netbsd.org>
From: Rob Quinn <rquinn@sec.sprint.net>
List: port-sparc
Date: 08/07/2002 08:08:46
Starting yesterday morning (and again this morning) my sparc5 running -current
stopped booting and hung right after the first SCSI disk was recognized. A
kernel from Monday morning (cvs update on Aug 5th, ~1:30am EDT) doesn't have a
problem.
The last message on the dead boot is (copied by hand):
sd0: 2063MB, 6703 cyl, 5 head, 126 sec, 512 bytes/sect x 4226725 sectors
sd0: sync (100.0ns offset 15), 8-bit (10.000MB/s) transfers, tagged queueing
With the Monday morning kernel, that's followed by:
sd1 at scsibus0 target 3 lun 0: <SEAGATE, ST32430W SUN2.1G, 0508> SCSI2 0/direct fixed
sd1: 2049 MB, 3992 cyl, 9 head, 116 sec, 512 bytes/sect x 4197405 sectors
sd1: sync (100.0ns offset 15), 8-bit (10.000MB/s) transfers, tagged queueing
st0 at scsibus0 target 4 lun 0: <EXABYTE, EXB-8505SMBANSH2, 0793> SCSI2 1/sequential removable
st0: density code 21, 1024-byte blocks, write-enabled
st0: sync (200.0ns offset 11), 8-bit (5.000MB/s) transfers
cd0 at scsibus0 target 6 lun 0: <TOSHIBA, XM5701TASUN12XCD, 0997> SCSI2 5/cdrom removable
cd0: sync (100.0ns offset 8), 8-bit (10.000MB/s) transfers
'trace' gives several pages of function calls, the last few being:
scsi_bus_probe
scsibus_config_interrupts
config_process_deferred
configure
main
startmap_done
Yesterday the machine was probably hung up for 5 or 10 min before I discovered
it, so I don't think it will recover on its own. Changing my config file to
'sd0 at scsibus' from 'sd*' doesn't change anything. Anyone else seeing this?