From owner-freebsd-hackers Sun Jul 21 01:20:32 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA20399 for hackers-outgoing; Sun, 21 Jul 1996 01:20:32 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA20390 for ; Sun, 21 Jul 1996 01:20:28 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id KAA15995 for ; Sun, 21 Jul 1996 10:20:26 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA07634 for freebsd-hackers@freebsd.org; Sun, 21 Jul 1996 10:20:25 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id KAA05424 for freebsd-hackers@freebsd.org; Sun, 21 Jul 1996 10:05:48 +0200 (MET DST) From: J Wunsch Message-Id: <199607210805.KAA05424@uriah.heep.sax.de> Subject: Re: cvs commit: src/sys/i386/isa aha1542.c To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Sun, 21 Jul 1996 10:05:48 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199607210426.OAA24600@godzilla.zeta.org.au> from Bruce Evans at "Jul 21, 96 02:26:37 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (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 (Moved to -hackers, committers is not a discussion list.) As Bruce Evans wrote: > > People who want them to break into the debugger can always set the > > breakpoint explicitly. The existing behaviour was a misfeature from > > Yes, code with Debugger() in it (except code to explicitly trap to the > debugger) shouldn't be committed. ...unless inside #ifdef DEBUG. > > the beginning, in the (wrong) assumption that the SCSI controller must > > always be of essential importance to the entire system. > > It is, if the alterative is to write corrupted data. Nope, you're making the same (wrong) assumption as the author of the driver that any SCSI adapter must necessarily serve things that are of vital interest for the sanity of the system. In my case, the machine booted diskless, and the SCSI adapter was there to play with various SCSI devices, like a CDROM changer. It was perfectly okay to have a hung SCSI bus, and volunteerely reboot the machine in case i could not unwedge it by any other means. My point is that this should not be a matter of opinion of the author of some disk driver, but a decision of the system administrator. Perhaps (ick!) yet another option ``SCSI_PARANOID''. :) Btw., i wonder why the bus jams unrecoverably. The SCSI BIOS seems to be able to recover it fine. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)