Subject: port-sparc/17891: Sparc5 no longer boots with -current kernels after 5 Aug 2002
To: None <gnats-bugs@gnats.netbsd.org>
From: None <rquinn@sec.sprint.net>
List: netbsd-bugs
Date: 08/09/2002 04:21:40
>Number:         17891
>Category:       port-sparc
>Synopsis:       Sparc5 no longer boots with -current kernels after 5 Aug 2002
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    port-sparc-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Aug 09 04:22:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Rob Quinn
>Release:        1.6E works, 1.6F does not
>Organization:
>Environment:
NetBSD struck.sec.sprint.net 1.6E NetBSD 1.6E (STRUCK) #87: Fri Aug  2 03:56:47 EDT 2002     root@struck.sec.sprint.net:/usr/obj/STRUCK sparc

>Description:
 I rebuild my -current kernels each morning. Starting Tuesday morning (6 Aug) my
sparc5 would no longer boot, 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

 A kernel from 8 Aug didn't even detect sd0.

 I will be out of town and unable to reply to any questions until the 13th.

>How-To-Repeat:
Boot with new kernel.
>Fix:
Roll back to earlier kernel.
>Release-Note:
>Audit-Trail:
>Unformatted: