From owner-freebsd-scsi Sun Apr 29 10: 0:13 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 3372637B43F for ; Sun, 29 Apr 2001 10:00:07 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id TAA04791 for freebsd-scsi@FreeBSD.ORG; Sun, 29 Apr 2001 19:00:05 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f3TGo6v30670 for freebsd-scsi@FreeBSD.ORG; Sun, 29 Apr 2001 18:50:06 +0200 (MET DST) (envelope-from j) Date: Sun, 29 Apr 2001 18:50:06 +0200 From: J Wunsch To: freebsd-scsi@FreeBSD.ORG Subject: Re: sa(4) jamming Message-ID: <20010429185005.B50185@uriah.heep.sax.de> Reply-To: Joerg Wunsch References: <200104271649.f3RGmts35017@aslan.scsiguy.com> <200104271700.f3RH01s35435@aslan.scsiguy.com> <20010428210359.Q50185@uriah.heep.sax.de> <20010428233306.A37621@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20010428233306.A37621@panzer.kdm.org>; from ken@kdm.org on Sat, Apr 28, 2001 at 11:33:06PM -0600 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 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Kenneth D. Merry wrote: > What surprised me is that we didn't get any bug reports after the > changes first went into the tree on March 27th. Your bug reports > are (as far as I can remember) the first. Well, there's another one in the -current list now, as you've already seen. Perhaps this basically means that the rate of hitting a SCSI error is not all that high. ;-) Also, there's such a variety of error possibilities, and certainly only very few of them are now misbehaving. > I think your patch was on target, but the action string needs to be > set as well. Ah, OK. If you're on track now, it's OK. I only wanted to make sure it's not getting forgotten. > Anyway, I've attached a patch. It needs to be tested. I won't be > able to test it until I get one of my machines upgraded to -current. I could test that, but i'm not sure, how to trigger a SS_NOP again? My tape driver is already patched, so it doesn't call cam_periph_error() anymore in the case of an ILI. What else would trigger a NO SENSE situation? > (My > buildworld blew up in xlint.) Is that really fatal? I usually end up in "make -k buildworld", and if the log file doesn't expose any serious errors, i ignore minor blowups then. I've patched my source tree, but have to rebuild/reboot before it takes effect. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message