Date: Sun, 29 Apr 2001 17:20:47 -0600 From: "Kenneth D. Merry" <ken@kdm.org> To: Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de> Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: sa(4) jamming Message-ID: <20010429172047.A41838@panzer.kdm.org> In-Reply-To: <20010429185005.B50185@uriah.heep.sax.de>; from j@uriah.heep.sax.de on Sun, Apr 29, 2001 at 06:50:06PM %2B0200 References: <200104271649.f3RGmts35017@aslan.scsiguy.com> <200104271700.f3RH01s35435@aslan.scsiguy.com> <20010428210359.Q50185@uriah.heep.sax.de> <20010428233306.A37621@panzer.kdm.org> <20010429185005.B50185@uriah.heep.sax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Apr 29, 2001 at 18:50:06 +0200, J Wunsch wrote:
> 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.
Yep.
> 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.
Hopefully that's true. :) I think another part of it may be that not as
many people are brave enough to run -current. :) (I go quite a long time
before updating some of my machines.)
> > 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?
It's possible you could do it with a CDROM drive. There are a couple of
audio-related sense codes that return SS_NOP:
/* R */{SST(0x00, 0x12, SS_NOP,
"Audio play operation paused") },
/* R */{SST(0x00, 0x13, SS_NOP,
"Audio play operation successfully completed") },
/* R */{SST(0x00, 0x15, SS_NOP,
"No current audio status to return") },
The rest are mostly for blocks on a disk getting reallocated.
You could always just disable the sa(4) driver patch and do it that way.
That would probably be the easiest way to test it.
> > (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.
Yep, it's fatal:
============
===> usr.bin/xlint/llib
/usr/obj/usr/home/ken/perforce/FreeBSD-ken/src/usr.bin/xlint/llib/../xlint/xlint -Cposix
/usr/home/ken/perforce/FreeBSD-ken/src/usr.bin/xlint/llib/llib-lposix
/usr/libexec/ld-elf.so.1: Shared object "libc.so.5" not found
*** Error code 1
Stop in /usr/home/ken/perforce/FreeBSD-ken/src/usr.bin/xlint/llib.
*** Error code 1
Stop in /usr/home/ken/perforce/FreeBSD-ken/src/usr.bin/xlint.
*** Error code 1
Stop in /usr/home/ken/perforce/FreeBSD-ken/src/usr.bin.
*** Error code 1
Stop in /usr/home/ken/perforce/FreeBSD-ken/src.
*** Error code 1
Stop in /usr/home/ken/perforce/FreeBSD-ken/src.
*** Error code 1
Stop in /usr/home/ken/perforce/FreeBSD-ken/src.
============
Peter fixed it last night I think.
> I've patched my source tree, but have to rebuild/reboot before it
> takes effect.
Ahh.
Ken
--
Kenneth Merry
ken@kdm.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010429172047.A41838>