Date: Sun, 21 Jul 1996 10:05:48 +0200 (MET DST) From: J Wunsch <j@uriah.heep.sax.de> To: freebsd-hackers@freebsd.org (FreeBSD hackers) Subject: Re: cvs commit: src/sys/i386/isa aha1542.c Message-ID: <199607210805.KAA05424@uriah.heep.sax.de> In-Reply-To: <199607210426.OAA24600@godzilla.zeta.org.au> from Bruce Evans at "Jul 21, 96 02:26:37 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
(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. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199607210805.KAA05424>