From owner-freebsd-hackers Wed Feb 5 09:48:55 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA19911 for hackers-outgoing; Wed, 5 Feb 1997 09:48:55 -0800 (PST) Received: from hda.hda.com (ip57-max1-fitch.ziplink.net [199.232.245.57]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA19841 for ; Wed, 5 Feb 1997 09:48:51 -0800 (PST) Received: (from dufault@localhost) by hda.hda.com (8.6.12/8.6.12) id MAA01252; Wed, 5 Feb 1997 12:43:08 -0500 From: Peter Dufault Message-Id: <199702051743.MAA01252@hda.hda.com> Subject: Re: probing scsi bus after boot? In-Reply-To: <199702051714.MAA01169@hda.hda.com> from Peter Dufault at "Feb 5, 97 12:14:34 pm" To: dufault@hda.com (Peter Dufault) Date: Wed, 5 Feb 1997 12:43:07 -0500 (EST) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@freebsd.org, jlk@pavilion.co.uk X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Re: Reprobe with no devices > Once you've compiled with ssc: > > > device ssc0 at scbus? #SCSI control device More like: > device su0 # Fixed entry devices > device ssc0 # SCSI control device (...) > And apply a "probe all" to it: > > > scsi -f /dev/scsi.ctl -p And it will find the devices on the bus and panic with a corrupt stack. -- Peter Dufault (dufault@hda.com) Realtime Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936