Date: Mon, 13 Mar 1995 10:55:00 -0500 (EST) From: Peter Dufault <dufault@hda.com> To: joerg_wunsch@uriah.heep.sax.de Cc: freebsd-bugs@FreeBSD.org Subject: Re: 950210-SNAP Problems ... Message-ID: <199503131555.KAA03172@hda.com> In-Reply-To: <199503130720.IAA02105@uriah.heep.sax.de> from "J Wunsch" at Mar 13, 95 08:20:41 am
next in thread | previous in thread | raw e-mail | index | archive | help
J Wunsch writes: > > As Peter Dufault wrote: > > > > > /kernel: sd0(ncr0:0:0): ABORTED COMMAND asc:47 fru:02, retries:4 > > > > ASC 47 is "SCSI parity error". > > Just an idea: wouldn't it make sense to print another line at least > for the most commons ASC's? Something like: > > /kernel: sd0(ncr0:0:0): asc 47 = PARITY ERROR > Yes, except that if you have the SCSI spec look at how many there are: four pages. I'd guess there are roughly 200. The field is 16 bits consisting of ASC and ASCQ. Parity error is for ASC=47 ASCQ=0. I hate putting stuff in the kernel. One thing I've thought about is adding a "/dev/scsi-sense-0-0" (for sense data for ID 0 LUN 0) that would have a kernel ring buffer of sense information. Then you could either have a logging utility or just read out of it for debugging using debugging utilities. Of course 200 codes times about 24 bytes per code is only 4800 bytes. Peter -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199503131555.KAA03172>