Subject: port-mac/2074: lockup when nothing's attached to adb
To: None <gnats-bugs@NetBSD.ORG>
From: Chris Jones <cjones@rupert.oscs.montana.edu>
List: netbsd-bugs
Date: 02/13/1996 11:46:31
>Number:         2074
>Category:       port-mac
>Synopsis:       lockup when nothing's attached to adb
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    gnats-admin (GNATS administrator)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Feb 13 14:20:07 1996
>Last-Modified:
>Originator:     Chris Jones
>Organization:
***********************cjones@rupert.oscs.montana.edu*********************
* Chris  | "You can't say that Microsoft hasn't ever put the buggy       *
*  Jones |  before the horse."                             -Mark Wistey  *
**************************************************************************
>Release:        1.1
>Environment:
	
System: NetBSD rupert.oscs.montana.edu 1.1 NetBSD 1.1 (SLIM) #0: Wed Nov 22 13:02:54 MST 1995 cjones@rupert.oscs.montana.edu:/home/src/sys/arch/mac68k/compile/SLIM mac68k

Mac IIcx
extended keyboard
100 dpi mouse

>Description:
What happens when no devices are attached to the adb chain and the
kernel tries to init?  My experience is that it locks up after
printing "adb:  bus subsystem" (or whatever).
	
>How-To-Repeat:
Unfortunately, I wasn't able to do comprehensive testing (trying
different combinations of devices attached and not attached) because
I'm trying to keep my machine online to keep my users somewhat happy.
If you want, I can do some better testing some morning.
	
>Fix:
I just plugged in the keyboard and mouse.
	
>Audit-Trail:
>Unformatted: