From owner-freebsd-scsi Sun Apr 29 3:30:49 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from eal.miknet.net (eal.miknet.net [202.174.235.5]) by hub.freebsd.org (Postfix) with ESMTP id B71E237B423 for ; Sun, 29 Apr 2001 03:30:44 -0700 (PDT) (envelope-from michael@miknet.net) Received: from michael by eal.miknet.net with local (Exim 3.22 #1 (Debian)) id 14toT2-0005Ob-00; Sun, 29 Apr 2001 20:30:16 +1000 Date: Sun, 29 Apr 2001 20:30:16 +1000 To: "Kenneth D. Merry" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: NULL pointer deref in scsi_sense_desc Message-ID: <20010429203016.A20311@miknet.net> References: <20010428114711.A7571@miknet.net> <20010428234800.A37675@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.17i In-Reply-To: <20010428234800.A37675@panzer.kdm.org>; from ken@kdm.org on Sat, Apr 28, 2001 at 11:48:00PM -0600 From: Michael Samuel Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Apr 28, 2001 at 11:48:00PM -0600, Kenneth D. Merry wrote: > Hmm, that would cause the code to deference a null pointer, which is bad. > It's probably a bug to do that without checking the pointer first, since a > drive could theoretically return a bogus sense key and cause a panic. Yes, that's exactly what the bug was. It died on that line, and the instruction it got the page fault in was a "movl 0x8(%eax), %eax" (from memory...), and I'm guessing that %eax would have been 0. This drive has been known in other systems to return bogus (or at-least uncommon) sense keys. The tape drive is a little bit stuffed, and has been causing hard lockups (not even ctrl-alt-esc responds) when I try to use it now. > Would it be possible for you to get a stack trace? If you need info on how > to get a stack trace: > > http://www.freebsd.org/doc/en_US.ISO_8859-1/books/handbook/kerneldebug.html Unfortunately, I had crash dumps turned off at the time, so when I rebooted (to examine the crash from the comfort of gdb), savecore failed. (oops) > What I'm looking for is what the sense key, asc, and ascq are. I think we > should have all existing sense keys covered, but if we don't I'd like to > know about it. (It would also be useful to know if the drive is just > returning a bogus sense key.) It's a seagate AIT drive, which in dmesg is reported as a "SEAGATE AIT 03j5", but has no other distinguishing marks, as far as I can tell. It was in a funny state at the time of the crash... > The attached patch should fix your problem. Let me know how it works. The patch looks "obviously correct", but maybe a debug message would be nice, to allow users to look up the sense key manually if they wish. (Or does it get printed anyway?) BTW, the same bug exists in scsi_error_action()... -- Michael Samuel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message 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 From owner-freebsd-scsi Sun Apr 29 10: 0:17 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 6AC1E37B440 for ; Sun, 29 Apr 2001 10:00:09 -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 TAA04792 for freebsd-scsi@FreeBSD.ORG; Sun, 29 Apr 2001 19:00:08 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f3TGrrs30690 for freebsd-scsi@FreeBSD.ORG; Sun, 29 Apr 2001 18:53:53 +0200 (MET DST) (envelope-from j) Date: Sun, 29 Apr 2001 18:53:53 +0200 From: J Wunsch To: freebsd-scsi@FreeBSD.ORG Subject: Re: Another problem with the new CAM error handling Message-ID: <20010429185353.C50185@uriah.heep.sax.de> Reply-To: Joerg Wunsch References: <20010426110542.A50185@uriah.heep.sax.de> <200104261435.f3QEZLs23573@aslan.scsiguy.com> <20010426190714.E50185@uriah.heep.sax.de> <20010428231227.A37369@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20010428231227.A37369@panzer.kdm.org>; from ken@kdm.org on Sat, Apr 28, 2001 at 11:12:27PM -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: > The old code retried unit attentions unconditionally without decrementing > the retry count if SF_RETRY_UA was set. If SF_RETRY_UA wasn't set, it > would still retry unit attentions, but would decrement the retry count. Ah, yes, that would explain it. Thanks for the analyzation, i didn't get a grip about it when looking at the code. > The attached patch should fix your problem. OK, i'll test that. > A better name might be 'camcontrol detach'. You're right, such an option > might help with reviving dead peripherals. Hopefully we can make things > robust enough so that a peripheral isn't declared "dead" unless it really > is dead. I think there's always a chance that something is being misdetected as `dead' when you can actually revive it somehow. Would it be much work to implement a "camcontrol detach"? Also, i'd like to prefer that over issuing a bus reset in case a temporarily added SCSI device is being manually removed. > ! start_ccb->ccb_h.ccb_state = PT_CCB_BUFFER_IO; ... > ! start_ccb->ccb_h.ccb_state = PT_CCB_BUFFER_IO_UA; Well, it's _that_ simple, ain't it? :-) -- 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 From owner-freebsd-scsi Sun Apr 29 10: 3:55 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id CD05E37B424 for ; Sun, 29 Apr 2001 10:03:51 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA20556; Sun, 29 Apr 2001 10:03:48 -0700 Date: Sun, 29 Apr 2001 10:03:48 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Joerg Wunsch Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: sa(4) jamming In-Reply-To: <20010429185005.B50185@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 29 Apr 2001, 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. > > 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 No, it's not. 4.2 shipped with the QLogic driver completely broken WRT Sense handling (also NetBSD 1.5). I only had a couple of complaints. > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Apr 29 16: 6: 6 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 2BA6137B423 for ; Sun, 29 Apr 2001 16:05:58 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id RAA41789; Sun, 29 Apr 2001 17:05:41 -0600 (MDT) (envelope-from ken) Date: Sun, 29 Apr 2001 17:05:40 -0600 From: "Kenneth D. Merry" To: Michael Samuel Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: NULL pointer deref in scsi_sense_desc Message-ID: <20010429170540.A41755@panzer.kdm.org> References: <20010428114711.A7571@miknet.net> <20010428234800.A37675@panzer.kdm.org> <20010429203016.A20311@miknet.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="3MwIy2ne0vdjdPXF" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20010429203016.A20311@miknet.net>; from michael@miknet.net on Sun, Apr 29, 2001 at 08:30:16PM +1000 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --3MwIy2ne0vdjdPXF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sun, Apr 29, 2001 at 20:30:16 +1000, Michael Samuel wrote: > On Sat, Apr 28, 2001 at 11:48:00PM -0600, Kenneth D. Merry wrote: > > Hmm, that would cause the code to deference a null pointer, which is bad. > > It's probably a bug to do that without checking the pointer first, since a > > drive could theoretically return a bogus sense key and cause a panic. > > Yes, that's exactly what the bug was. It died on that line, and the > instruction it got the page fault in was a "movl 0x8(%eax), %eax" (from > memory...), and I'm guessing that %eax would have been 0. > > This drive has been known in other systems to return bogus (or at-least > uncommon) sense keys. The tape drive is a little bit stuffed, and has been > causing hard lockups (not even ctrl-alt-esc responds) when I try to use it > now. It would be nice to know what those bogus sense keys are. > > Would it be possible for you to get a stack trace? If you need info on how > > to get a stack trace: > > > > http://www.freebsd.org/doc/en_US.ISO_8859-1/books/handbook/kerneldebug.html > > Unfortunately, I had crash dumps turned off at the time, so when I rebooted > (to examine the crash from the comfort of gdb), savecore failed. (oops) Could you try to reproduce the problem with crash dumps turned on? > > What I'm looking for is what the sense key, asc, and ascq are. I think we > > should have all existing sense keys covered, but if we don't I'd like to > > know about it. (It would also be useful to know if the drive is just > > returning a bogus sense key.) > > It's a seagate AIT drive, which in dmesg is reported as a "SEAGATE AIT 03j5", > but has no other distinguishing marks, as far as I can tell. It was in a > funny state at the time of the crash... > > > The attached patch should fix your problem. Let me know how it works. > > The patch looks "obviously correct", but maybe a debug message would be nice, > to allow users to look up the sense key manually if they wish. (Or does it > get printed anyway?) The numeric values generally only get printed for ASC/ASCQ pairs, since it is much more common to see unknown sense codes than sense keys. I've attached a patch that will print it, at least in the standard sense printing case. There isn't much space to do it in the da(4) or cd(4) drivers, and those drivers don't print out numbers for unknown asc/ascq'ss either. > BTW, the same bug exists in scsi_error_action()... Should be fixed in this patch. Ken -- Kenneth Merry ken@kdm.org --3MwIy2ne0vdjdPXF Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="scsi_all.sense_desc.20010429" ==== //depot/FreeBSD-ken/src/sys/cam/scsi/scsi_all.c#9 - /usr/home/ken/perforce/FreeBSD-ken/src/sys/cam/scsi/scsi_all.c ==== *** /tmp/tmp.1035.0 Sun Apr 29 17:00:00 2001 --- /usr/home/ken/perforce/FreeBSD-ken/src/sys/cam/scsi/scsi_all.c Sun Apr 29 16:58:47 2001 *************** *** 1570,1576 **** &sense_entry, &asc_entry); ! *sense_key_desc = sense_entry->desc; if (asc_entry != NULL) *asc_desc = asc_entry->desc; --- 1570,1579 ---- &sense_entry, &asc_entry); ! if (sense_entry != NULL) ! *sense_key_desc = sense_entry->desc; ! else ! *sense_key_desc = NULL; if (asc_entry != NULL) *asc_desc = asc_entry->desc; *************** *** 1637,1644 **** if (asc_entry != NULL && (asc != 0 || ascq != 0)) action = asc_entry->action; ! else action = sense_entry->action; if (sense_key == SSD_KEY_RECOVERED_ERROR) { /* --- 1640,1649 ---- if (asc_entry != NULL && (asc != 0 || ascq != 0)) action = asc_entry->action; ! else if (sense_entry != NULL) action = sense_entry->action; + else + action = SS_RETRY|SSQ_DECREMENT_COUNT|SSQ_PRINT_SENSE; if (sense_key == SSD_KEY_RECOVERED_ERROR) { /* *************** *** 1950,1956 **** ascq = (sense->extra_len >= 6) ? sense->add_sense_code_qual : 0; scsi_sense_desc(sense_key, asc, ascq, inq_data, &sense_key_desc, &asc_desc); ! sbuf_cat(sb, sense_key_desc); info = scsi_4btoul(sense->info); --- 1955,1964 ---- ascq = (sense->extra_len >= 6) ? sense->add_sense_code_qual : 0; scsi_sense_desc(sense_key, asc, ascq, inq_data, &sense_key_desc, &asc_desc); ! if (sense_key_desc != NULL) ! sbuf_cat(sb, sense_key_desc); ! else ! sbuf_printf(sb, "Unknown Sense Key %#x", sense_key); info = scsi_4btoul(sense->info); ==== //depot/FreeBSD-ken/src/sys/cam/scsi/scsi_cd.c#16 - /usr/home/ken/perforce/FreeBSD-ken/src/sys/cam/scsi/scsi_cd.c ==== *** /tmp/tmp.1035.1 Sun Apr 29 17:00:00 2001 --- /usr/home/ken/perforce/FreeBSD-ken/src/sys/cam/scsi/scsi_cd.c Sun Apr 29 16:57:07 2001 *************** *** 1718,1728 **** &sense_key_desc, &asc_desc); snprintf(announce_buf, ! sizeof(announce_buf), ! "Attempt to query device " ! "size failed: %s, %s", ! sense_key_desc, ! asc_desc); } else if (SID_TYPE(&cgd.inq_data) == T_CDROM) { /* * We only print out an error for --- 1718,1730 ---- &sense_key_desc, &asc_desc); snprintf(announce_buf, ! sizeof(announce_buf), ! "Attempt to query device " ! "size failed: %s, %s", ! sense_key_desc ? ! sense_key_desc: ! "Unknown Sense Key", ! asc_desc); } else if (SID_TYPE(&cgd.inq_data) == T_CDROM) { /* * We only print out an error for ==== //depot/FreeBSD-ken/src/sys/cam/scsi/scsi_da.c#17 - /usr/home/ken/perforce/FreeBSD-ken/src/sys/cam/scsi/scsi_da.c ==== *** /tmp/tmp.1035.2 Sun Apr 29 17:00:00 2001 --- /usr/home/ken/perforce/FreeBSD-ken/src/sys/cam/scsi/scsi_da.c Sun Apr 29 16:58:10 2001 *************** *** 1377,1387 **** &sense_key_desc, &asc_desc); snprintf(announce_buf, ! sizeof(announce_buf), ! "Attempt to query device " ! "size failed: %s, %s", ! sense_key_desc, ! asc_desc); } else { if (have_sense) scsi_sense_print( --- 1377,1389 ---- &sense_key_desc, &asc_desc); snprintf(announce_buf, ! sizeof(announce_buf), ! "Attempt to query device " ! "size failed: %s, %s", ! sense_key_desc ? ! sense_key_desc : ! "Unknown Sense Key", ! asc_desc); } else { if (have_sense) scsi_sense_print( --3MwIy2ne0vdjdPXF-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Apr 29 16:20:56 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 50A3D37B422 for ; Sun, 29 Apr 2001 16:20:51 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id RAA41908; Sun, 29 Apr 2001 17:20:47 -0600 (MDT) (envelope-from ken) Date: Sun, 29 Apr 2001 17:20:47 -0600 From: "Kenneth D. Merry" To: Joerg Wunsch Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: sa(4) jamming Message-ID: <20010429172047.A41838@panzer.kdm.org> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20010429185005.B50185@uriah.heep.sax.de>; from j@uriah.heep.sax.de on Sun, Apr 29, 2001 at 06:50:06PM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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 From owner-freebsd-scsi Sun Apr 29 16:24:36 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id AA14A37B424 for ; Sun, 29 Apr 2001 16:24:32 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id RAA41926; Sun, 29 Apr 2001 17:24:26 -0600 (MDT) (envelope-from ken) Date: Sun, 29 Apr 2001 17:24:26 -0600 From: "Kenneth D. Merry" To: Joerg Wunsch Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Another problem with the new CAM error handling Message-ID: <20010429172426.B41838@panzer.kdm.org> References: <20010426110542.A50185@uriah.heep.sax.de> <200104261435.f3QEZLs23573@aslan.scsiguy.com> <20010426190714.E50185@uriah.heep.sax.de> <20010428231227.A37369@panzer.kdm.org> <20010429185353.C50185@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20010429185353.C50185@uriah.heep.sax.de>; from j@uriah.heep.sax.de on Sun, Apr 29, 2001 at 06:53:53PM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Apr 29, 2001 at 18:53:53 +0200, J Wunsch wrote: > As Kenneth D. Merry wrote: > > > The old code retried unit attentions unconditionally without decrementing > > the retry count if SF_RETRY_UA was set. If SF_RETRY_UA wasn't set, it > > would still retry unit attentions, but would decrement the retry count. > > Ah, yes, that would explain it. Thanks for the analyzation, i didn't > get a grip about it when looking at the code. > > > The attached patch should fix your problem. > > OK, i'll test that. Thanks. > > A better name might be 'camcontrol detach'. You're right, such an option > > might help with reviving dead peripherals. Hopefully we can make things > > robust enough so that a peripheral isn't declared "dead" unless it really > > is dead. > > I think there's always a chance that something is being misdetected as > `dead' when you can actually revive it somehow. Would it be much work > to implement a "camcontrol detach"? Also, i'd like to prefer that > over issuing a bus reset in case a temporarily added SCSI device is > being manually removed. Do you mean "bus rescan" instead of "bus reset"? I'm not sure how hard it would be to do a 'camcontrol detach'. I'd have to think about that a little bit. It may be as simple as sending an async notification, but I'm not positive on that. > > ! start_ccb->ccb_h.ccb_state = PT_CCB_BUFFER_IO; > ... > > ! start_ccb->ccb_h.ccb_state = PT_CCB_BUFFER_IO_UA; > > Well, it's _that_ simple, ain't it? :-) Yeah, the hooks were already in there. :) Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Apr 30 11:39: 6 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 56C0F37B424 for ; Mon, 30 Apr 2001 11:39:01 -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 UAA13039; Mon, 30 Apr 2001 20:38:51 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f3UIa4l62360; Mon, 30 Apr 2001 20:36:04 +0200 (MET DST) (envelope-from j) Date: Mon, 30 Apr 2001 20:36:04 +0200 From: J Wunsch To: "Kenneth D. Merry" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: sa(4) jamming Message-ID: <20010430203604.E50864@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> <20010429185005.B50185@uriah.heep.sax.de> <20010429172047.A41838@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20010429172047.A41838@panzer.kdm.org>; from ken@kdm.org on Sun, Apr 29, 2001 at 05:20:47PM -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: > 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 usually, too. My reason for upgrading recently was the acquisition of new hardware (i finally got rid of my old P133 box as the main workstation). > > 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") }, [etc] Hmm, i can't seem to trigger them, patched or unpatched system. After looking into the SCSI-2 documents, it seems they are not returned as sense codes but in the Audio Status field of an READ SUB-CHANNEL command. > 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. Well, i did this, on my test machine. Since i already did that previously (without setting action_string), i knew it fixes the ILI problem, but exposes the filemark -> EIO problem. That still happens, also with the addition of setting action_string (of course). Also, hitting the filemark yields a NO SENSE situation: (sa0:sym0:0:1:0): READ(06). CDB: 8 0 0 80 0 0 (sa0:sym0:0:1:0): CAM Status: SCSI Status Error (sa0:sym0:0:1:0): SCSI Status: Check Condition (sa0:sym0:0:1:0): NO SENSE info:8000 asc:0,1 (sa0:sym0:0:1:0): Filemark detected (sa0:sym0:0:1:0): Retries Exhausted (sa0:sym0:0:1:0): error 5 (sa0:sym0:0:1:0): Unretryable Error I can't seem to trigger printing the action_string ("No Recovery Action Needed") in either situation (ILI or filemark), however. Anyway, it seems that patch is the right thing: diff -u -r1.33 cam_periph.c --- /sys/cam/cam_periph.c 2001/03/28 09:17:49 1.33 +++ /sys/cam/cam_periph.c 2001/04/29 16:49:40 @@ -1369,6 +1369,9 @@ switch (err_action & SS_MASK) { case SS_NOP: + action_string = "No Recovery Action Needed"; + error = 0; + break; case SS_RETRY: action_string = "Retrying Command"; error = ERESTART; -- 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 From owner-freebsd-scsi Mon Apr 30 11:39: 8 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 B8D4037B43F for ; Mon, 30 Apr 2001 11:39:03 -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 UAA13047 for freebsd-scsi@FreeBSD.ORG; Mon, 30 Apr 2001 20:39:03 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f3UIbGZ62375 for freebsd-scsi@FreeBSD.ORG; Mon, 30 Apr 2001 20:37:16 +0200 (MET DST) (envelope-from j) Date: Mon, 30 Apr 2001 20:37:16 +0200 From: J Wunsch To: freebsd-scsi@FreeBSD.ORG Subject: Re: Another problem with the new CAM error handling Message-ID: <20010430203716.F50864@uriah.heep.sax.de> Reply-To: Joerg Wunsch References: <20010426110542.A50185@uriah.heep.sax.de> <200104261435.f3QEZLs23573@aslan.scsiguy.com> <20010426190714.E50185@uriah.heep.sax.de> <20010428231227.A37369@panzer.kdm.org> <20010429185353.C50185@uriah.heep.sax.de> <20010429172426.B41838@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20010429172426.B41838@panzer.kdm.org>; from ken@kdm.org on Sun, Apr 29, 2001 at 05:24:26PM -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: > > Also, i'd like to prefer that > > over issuing a bus reset in case a temporarily added SCSI device is > > being manually removed. > > Do you mean "bus rescan" instead of "bus reset"? You're right, i was confused. OK, since it's only a rescan, it's not such a tragedy. So a `camcontrol detach' is a nice to have item, but nothing even remotely urgent. -- 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 From owner-freebsd-scsi Mon Apr 30 12: 1:43 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 0D47137B422 for ; Mon, 30 Apr 2001 12:01:34 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id NAA48014; Mon, 30 Apr 2001 13:01:17 -0600 (MDT) (envelope-from ken) Date: Mon, 30 Apr 2001 13:01:17 -0600 From: "Kenneth D. Merry" To: Michael Samuel Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: NULL pointer deref in scsi_sense_desc Message-ID: <20010430130117.A47971@panzer.kdm.org> References: <20010428114711.A7571@miknet.net> <20010428234800.A37675@panzer.kdm.org> <20010429203016.A20311@miknet.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="PNTmBPCT7hxwcZjr" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20010429203016.A20311@miknet.net>; from michael@miknet.net on Sun, Apr 29, 2001 at 08:30:16PM +1000 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --PNTmBPCT7hxwcZjr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sun, Apr 29, 2001 at 20:30:16 +1000, Michael Samuel wrote: > On Sat, Apr 28, 2001 at 11:48:00PM -0600, Kenneth D. Merry wrote: > > Hmm, that would cause the code to deference a null pointer, which is bad. > > It's probably a bug to do that without checking the pointer first, since a > > drive could theoretically return a bogus sense key and cause a panic. > > Yes, that's exactly what the bug was. It died on that line, and the > instruction it got the page fault in was a "movl 0x8(%eax), %eax" (from > memory...), and I'm guessing that %eax would have been 0. > > This drive has been known in other systems to return bogus (or at-least > uncommon) sense keys. The tape drive is a little bit stuffed, and has been > causing hard lockups (not even ctrl-alt-esc responds) when I try to use it > now. After looking at it some more, a better fix for the problem would be adding sense key table entries for the only two entries that aren't defined -- blank check and data protect. Your drive was probably returning one of those two errors. All sense key values are defined by the spec (although "equal" is listed as obsolete and 0xf is reserved), and with the attached patch, all sense keys are defined in the table. So with this patch it should be impossible to get a bogus sense_entry pointer; if it is, we should panic, since that's a bug. Ken -- Kenneth Merry ken@kdm.org --PNTmBPCT7hxwcZjr Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="scsi_all.c.sense_key.20010430" ==== //depot/FreeBSD-adaptec/src/sys/cam/scsi/scsi_all.c#3 - /usr/home/ken/perforce/FreeBSD-adaptec/src/sys/cam/scsi/scsi_all.c ==== *** /tmp/tmp.10514.0 Mon Apr 30 12:55:56 2001 --- /usr/home/ken/perforce/FreeBSD-adaptec/src/sys/cam/scsi/scsi_all.c Mon Apr 30 12:55:36 2001 *************** *** 711,716 **** --- 711,718 ---- { SSD_KEY_HARDWARE_ERROR, SS_RDEF, "HARDWARE FAILURE" }, { SSD_KEY_ILLEGAL_REQUEST, SS_FATAL|EINVAL, "ILLEGAL REQUEST" }, { SSD_KEY_UNIT_ATTENTION, SS_FATAL|ENXIO, "UNIT ATTENTION" }, + { SSD_KEY_DATA_PROTECT, SS_FATAL|EACCES, "DATA PROTECT" }, + { SSD_KEY_BLANK_CHECK, SS_FATAL|ENOSPC, "BLANK CHECK" }, { SSD_KEY_Vendor_Specific, SS_FATAL|EIO, "Vendor Specific" }, { SSD_KEY_COPY_ABORTED, SS_FATAL|EIO, "COPY ABORTED" }, { SSD_KEY_ABORTED_COMMAND, SS_RDEF, "ABORTED COMMAND" }, --PNTmBPCT7hxwcZjr-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Apr 30 12:53:10 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.johnrshannon.com (mail.johnrshannon.com [208.141.183.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D28C37B422 for ; Mon, 30 Apr 2001 12:53:08 -0700 (PDT) (envelope-from john@johnrshannon.com) Received: from pablo.johnrshannon.com (pablo.johnrshannon.com [192.168.1.3]) by mail.johnrshannon.com (Postfix) with ESMTP id BE0D21D881 for ; Mon, 30 Apr 2001 13:53:06 -0600 (MDT) Received: (from john@localhost) by pablo.johnrshannon.com (8.11.3/8.11.3) id f3UJr6r00657 for freebsd-scsi@freebsd.org; Mon, 30 Apr 2001 13:53:06 -0600 (MDT) (envelope-from john) Content-Type: text/plain; charset="iso-8859-1" From: "John R. Shannon" Reply-To: john@johnrshannon.com Organization: johnrshannon.com To: freebsd-scsi@freebsd.org Subject: Disk geomerty Date: Mon, 30 Apr 2001 13:53:06 -0600 X-Mailer: KMail [version 1.2] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <01043013530600.00636@pablo.johnrshannon.com> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 4.3-RELASE Tekram DC-3900U3 SCSI controller Quantum Atlas 102 TY092LDDD6 (9.1 GB) I'm confused about configuring the disk geometry. The diskcontroller offers options for CHS mapping of "Plug and Play Mapping" or "Alternate CHS Mapping" without explanation. The FAQ refers to "extended translation support". Does this correspond to one of these modes? What should I use? -- John R. Shannon john@johnrshannon.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Apr 30 13:59:11 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id BB8FB37B422 for ; Mon, 30 Apr 2001 13:58:55 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id OAA48648; Mon, 30 Apr 2001 14:58:15 -0600 (MDT) (envelope-from ken) Date: Mon, 30 Apr 2001 14:58:15 -0600 From: "Kenneth D. Merry" To: Joerg Wunsch Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: sa(4) jamming Message-ID: <20010430145815.A48398@panzer.kdm.org> 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> <20010429172047.A41838@panzer.kdm.org> <20010430203604.E50864@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20010430203604.E50864@uriah.heep.sax.de>; from j@uriah.heep.sax.de on Mon, Apr 30, 2001 at 08:36:04PM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Apr 30, 2001 at 20:36:04 +0200, J Wunsch wrote: > As Kenneth D. Merry wrote: > > > 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 usually, too. My reason for upgrading recently was the acquisition > of new hardware (i finally got rid of my old P133 box as the main > workstation). > > > > 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") }, > > [etc] > > Hmm, i can't seem to trigger them, patched or unpatched system. After > looking into the SCSI-2 documents, it seems they are not returned as > sense codes but in the Audio Status field of an READ SUB-CHANNEL > command. Hmm, yeah, maybe those sense codes are from an older spec or something. > > 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. > > Well, i did this, on my test machine. Since i already did that > previously (without setting action_string), i knew it fixes the ILI > problem, but exposes the filemark -> EIO problem. That still happens, > also with the addition of setting action_string (of course). Also, > hitting the filemark yields a NO SENSE situation: > > (sa0:sym0:0:1:0): READ(06). CDB: 8 0 0 80 0 0 > (sa0:sym0:0:1:0): CAM Status: SCSI Status Error > (sa0:sym0:0:1:0): SCSI Status: Check Condition > (sa0:sym0:0:1:0): NO SENSE info:8000 asc:0,1 > (sa0:sym0:0:1:0): Filemark detected > (sa0:sym0:0:1:0): Retries Exhausted > (sa0:sym0:0:1:0): error 5 > (sa0:sym0:0:1:0): Unretryable Error > > I can't seem to trigger printing the action_string ("No Recovery > Action Needed") in either situation (ILI or filemark), however. Hmm. At least in the above case we aren't getting an error action of SS_NOP, but rather SS_RETRY. With ILI, we would probably get back SS_NOP. Are you getting any error messages prior to the ones printed above? Do you get any printfs when the ILI problem happens? Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Apr 30 15:13:31 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 71F2737B423 for ; Mon, 30 Apr 2001 15:13:27 -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 AAA16172 for freebsd-scsi@FreeBSD.ORG; Tue, 1 May 2001 00:13:26 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f3UM0Oe67367 for freebsd-scsi@FreeBSD.ORG; Tue, 1 May 2001 00:00:24 +0200 (MET DST) (envelope-from j) Date: Tue, 1 May 2001 00:00:24 +0200 From: J Wunsch To: freebsd-scsi@FreeBSD.ORG Subject: Re: sa(4) jamming Message-ID: <20010501000024.H50864@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> <20010429185005.B50185@uriah.heep.sax.de> <20010429172047.A41838@panzer.kdm.org> <20010430203604.E50864@uriah.heep.sax.de> <20010430145815.A48398@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20010430145815.A48398@panzer.kdm.org>; from ken@kdm.org on Mon, Apr 30, 2001 at 02:58:15PM -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: > > > /* R */{SST(0x00, 0x12, SS_NOP, > > > "Audio play operation paused") }, > > > > [etc] > > > > Hmm, i can't seem to trigger them, patched or unpatched system. After > > looking into the SCSI-2 documents, it seems they are not returned as > > sense codes but in the Audio Status field of an READ SUB-CHANNEL > > command. > > Hmm, yeah, maybe those sense codes are from an older spec or something. I see them also in the ASC/ASCQ table of SCSI-2 (and thus they are certainly also in SCSI-3), but the reference in the text for those messages is only for READ SUB-CHANNEL. Nevermind. > > (sa0:sym0:0:1:0): READ(06). CDB: 8 0 0 80 0 0 > > (sa0:sym0:0:1:0): CAM Status: SCSI Status Error > > (sa0:sym0:0:1:0): SCSI Status: Check Condition > > (sa0:sym0:0:1:0): NO SENSE info:8000 asc:0,1 > > (sa0:sym0:0:1:0): Filemark detected > > (sa0:sym0:0:1:0): Retries Exhausted > > (sa0:sym0:0:1:0): error 5 > > (sa0:sym0:0:1:0): Unretryable Error ... > Are you getting any error messages prior to the ones printed above? > Do you get any printfs when the ILI problem happens? Nope, the ILI case doesn't cause any message to be printed. Obviously, cam_periph_error() eventually returns to saerror() with a return code of 0, and without printing anything. (Just to clarify: bootverbose was set, of course.) -- 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 From owner-freebsd-scsi Mon Apr 30 15:13:35 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 87D9437B424 for ; Mon, 30 Apr 2001 15:13:31 -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 AAA16176; Tue, 1 May 2001 00:13:30 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f3UMCYU67449; Tue, 1 May 2001 00:12:34 +0200 (MET DST) (envelope-from j) Date: Tue, 1 May 2001 00:12:34 +0200 (MET DST) Message-Id: <200104302212.f3UMCYU67449@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden 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 References: <01043013530600.00636@pablo.johnrshannon.com> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: Disk geomerty X-Original-Newsgroups: local.freebsd.scsi To: freebsd-scsi@freebsd.org Cc: "John R. Shannon" Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "John R. Shannon" wrote: > The diskcontroller offers options for CHS mapping of "Plug and Play > Mapping" or "Alternate CHS Mapping" without explanation. The FAQ > refers to "extended translation support". Does this correspond to > one of these modes? No idea what they really mean. Anyway, based on my own experience the Tekrams are rather forgiving and don't stupidly insist on a particular mapping. The worst that happens (like it could be for `dangerously dedicated' mode) is that they warn you about a supposedly bad fdisk table, and pause for 10 seconds at boot time. While the message then says `Hit any key to continue', they actually even continue automatically after 10 seconds. If you are cautious, just give one of those modes a try with a minimal installation. If it's not what you like, after installation blank out the first sectors of your disk with dd if=/dev/zero of=/dev/da0 count=100 and then immediately reboot and reinstall using the alternative option. The above command will fake a `virgin' disk to the controller BIOS, so they can't try to adapt to a previously installed fdisk table, and have to restart from scratch. -- 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 From owner-freebsd-scsi Mon Apr 30 16: 8:45 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 88D6437B424 for ; Mon, 30 Apr 2001 16:08:42 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id RAA49833; Mon, 30 Apr 2001 17:08:39 -0600 (MDT) (envelope-from ken) Date: Mon, 30 Apr 2001 17:08:39 -0600 From: "Kenneth D. Merry" To: Joerg Wunsch Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: sa(4) jamming Message-ID: <20010430170839.A49771@panzer.kdm.org> 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> <20010429172047.A41838@panzer.kdm.org> <20010430203604.E50864@uriah.heep.sax.de> <20010430145815.A48398@panzer.kdm.org> <20010501000024.H50864@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20010501000024.H50864@uriah.heep.sax.de>; from j@uriah.heep.sax.de on Tue, May 01, 2001 at 12:00:24AM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, May 01, 2001 at 00:00:24 +0200, J Wunsch wrote: > As Kenneth D. Merry wrote: > > > (sa0:sym0:0:1:0): READ(06). CDB: 8 0 0 80 0 0 > > > (sa0:sym0:0:1:0): CAM Status: SCSI Status Error > > > (sa0:sym0:0:1:0): SCSI Status: Check Condition > > > (sa0:sym0:0:1:0): NO SENSE info:8000 asc:0,1 > > > (sa0:sym0:0:1:0): Filemark detected > > > (sa0:sym0:0:1:0): Retries Exhausted > > > (sa0:sym0:0:1:0): error 5 > > > (sa0:sym0:0:1:0): Unretryable Error > ... > > > Are you getting any error messages prior to the ones printed above? > > Do you get any printfs when the ILI problem happens? > > Nope, the ILI case doesn't cause any message to be printed. > Obviously, cam_periph_error() eventually returns to saerror() with a > return code of 0, and without printing anything. > > (Just to clarify: bootverbose was set, of course.) I think it's doing the correct thing in both cases. In the case above (filemark detected) it is correctly stating that retries have been exhaused, because the sa(4) driver uses a retry count of 0 for reads and writes. In the ILI case, the ASC/ASCQ are probably 0x00,0x00, which we translate into a nop with no sense printing, as opposed to retrying and printing sense. Anyway, thanks for testing the patch, I checked it in in revision 1.36 of cam_periph.c. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 1 7:59:55 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.johnrshannon.com (mail.johnrshannon.com [208.141.183.125]) by hub.freebsd.org (Postfix) with ESMTP id 3757E37B423 for ; Tue, 1 May 2001 07:59:53 -0700 (PDT) (envelope-from john@johnrshannon.com) Received: from pablo.johnrshannon.com (pablo.johnrshannon.com [192.168.1.3]) by mail.johnrshannon.com (Postfix) with ESMTP id C0AF41D881 for ; Tue, 1 May 2001 08:59:51 -0600 (MDT) Received: (from john@localhost) by pablo.johnrshannon.com (8.11.3/8.11.3) id f41ExpE00649 for freebsd-scsi@freebsd.org; Tue, 1 May 2001 08:59:51 -0600 (MDT) (envelope-from john) Content-Type: text/plain; charset="iso-8859-1" From: "John R. Shannon" Reply-To: john@johnrshannon.com Organization: johnrshannon.com To: freebsd-scsi@freebsd.org Subject: Re: Disk geomerty Date: Tue, 1 May 2001 08:59:51 -0600 X-Mailer: KMail [version 1.2] References: <01043013530600.00636@pablo.johnrshannon.com> <200104302212.f3UMCYU67449@uriah.heep.sax.de> In-Reply-To: <200104302212.f3UMCYU67449@uriah.heep.sax.de> MIME-Version: 1.0 Message-Id: <01050108595100.00646@pablo.johnrshannon.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm still having problems. When I set the disk 9318/64/32 with fdisk, FreeBSD installs but will not boot. Fiddling with the SCSI BIOS settings has no effect; the BIOS reports 1025/255/63. I can fdisk the geometry to 1024/255/63, install and boot. The only problem is that the only 8.475 GB is used on a 9.1 GB drive. On Monday 30 April 2001 04:12 pm, you wrote: > "John R. Shannon" wrote: > > The diskcontroller offers options for CHS mapping of "Plug and Play > > Mapping" or "Alternate CHS Mapping" without explanation. The FAQ > > refers to "extended translation support". Does this correspond to > > one of these modes? > > No idea what they really mean. Anyway, based on my own experience the > Tekrams are rather forgiving and don't stupidly insist on a particular > mapping. The worst that happens (like it could be for `dangerously > dedicated' mode) is that they warn you about a supposedly bad fdisk > table, and pause for 10 seconds at boot time. While the message then > says `Hit any key to continue', they actually even continue > automatically after 10 seconds. > > If you are cautious, just give one of those modes a try with a minimal > installation. If it's not what you like, after installation blank out > the first sectors of your disk with > > dd if=/dev/zero of=/dev/da0 count=100 > > and then immediately reboot and reinstall using the alternative > option. The above command will fake a `virgin' disk to the controller > BIOS, so they can't try to adapt to a previously installed fdisk > table, and have to restart from scratch. -- John R. Shannon john@johnrshannon.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 1 9:49:50 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 1FC9D37B423 for ; Tue, 1 May 2001 09:49:46 -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 SAA04497; Tue, 1 May 2001 18:49:44 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f41Gksj70945; Tue, 1 May 2001 18:46:54 +0200 (MET DST) (envelope-from j) Date: Tue, 1 May 2001 18:46:54 +0200 (MET DST) Message-Id: <200105011646.f41Gksj70945@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden 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 References: <01043013530600.00636@pablo.johnrshannon.com> <200104302212.f3UMCYU67449@uriah.heep.sax.de> <01050108595100.00646@pablo.johnrshannon.com> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: Disk geomerty X-Original-Newsgroups: local.freebsd.scsi To: freebsd-scsi@freebsd.org Cc: "John R. Shannon" Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "John R. Shannon" wrote: > When I set the disk 9318/64/32 with fdisk, FreeBSD installs but will > not boot. Fiddling with the SCSI BIOS settings has no effect; the > BIOS reports 1025/255/63. You should always have fdisk use what the BIOS reports. IMHO that should be the default for fdisk, anyway. (I'm not sure, i haven't been using fdisk tables for years now, all my disks are `dangerously dedicated', thus i don't need to care for the fdisk crap with its ficticuous `cylinders' &c.) > I can fdisk the geometry to 1024/255/63, install and boot. The only > problem is that the only 8.475 GB is used on a 9.1 GB drive. That's certainly normal. Well, you've got the typical disk drive manufacturer lie^H^H^Hmisinterpretation of `Gigabyte' here. Since the numbers look larger, disk manufacturers always use Giga = 10^9, while computer technicians always use Giga = 2^30. % bc bc 1.06 Copyright 1991-1994, 1997, 1998, 2000 Free Software Foundation, Inc. This is free software with ABSOLUTELY NO WARRANTY. For details type `warranty'. scale=3 9.1 * 10^9 / 2^30 8.475 ^D So there you are. Note that when not using `dangerously dedicated' mode you lose a few additional sectors since fdisk partitions are by definition constrained to cylinder boundaries (for what fdisk believe were a `cylinder'), but that's negligible. > On Monday 30 April 2001 04:12 pm, you wrote: >> "John R. Shannon" wrote: [Please, no full quotes.] -- 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 From owner-freebsd-scsi Tue May 1 19:34:46 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from arjun.niksun.com (gwnew.niksun.com [63.148.27.34]) by hub.freebsd.org (Postfix) with ESMTP id CB05B37B423; Tue, 1 May 2001 19:34:41 -0700 (PDT) (envelope-from ath@niksun.com) Received: from stiegl.niksun.com (stiegl.niksun.com [10.0.0.44]) by arjun.niksun.com (8.9.3/8.9.3) with ESMTP id WAA22111; Tue, 1 May 2001 22:34:41 -0400 (EDT) (envelope-from ath@stiegl.niksun.com) Received: from stiegl.niksun.com (localhost.niksun.com [127.0.0.1]) by stiegl.niksun.com (8.9.2/8.8.7) with ESMTP id WAA11069; Tue, 1 May 2001 22:34:41 -0400 (EDT) (envelope-from ath@stiegl.niksun.com) Message-Id: <200105020234.WAA11069@stiegl.niksun.com> From: Andrew Heybey To: msmith@freebsd.org Cc: freebsd-scsi@freebsd.org Subject: AMI MegaRAID on 4.2-RELEASE and bus_dmamap_load errors Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: Tue, 01 May 2001 22:34:41 -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org When running rawio on an (unmounted) partition, the kernel starts logging many messages of the form: Apr 23 11:00:03 raid /kernel: bus_dmamap_load: Too many segs! buf_len = 0x900 Apr 23 11:00:03 raid /kernel: bus_dmamap_load: Too many segs! buf_len = 0x100 Apr 23 11:00:03 raid /kernel: bus_dmamap_load: Too many segs! buf_len = 0xf00 Apr 23 11:00:03 raid last message repeated 4 times Relevant boot messages: amr0: mem 0xf8000000-0xfbffffff irq 11 at device 0.0 on pci4 amr0: Firmware l148, BIOS 3.11, 64MB RAM amrd0: on amr0 amrd0: 140008MB (286736384 sectors) RAID 5 (optimal) amrd1: on amr0 amrd1: 140008MB (286736384 sectors) RAID 5 (optimal) System is an Intel L440GX+, 512MB RAM. It is currently set up to stripe (using ccd) across the two RAID 5 arrays. The rawio is run on /dev/rccd0c. I found an exchange on freebsd-scsi in January about a similar problem with Mylex controllers: > > If you need someone to do testing of FreeBSD patches, revisions, etc for > > these controllers, the RAID cards and PC in question is just a > > play-around with PC and doesn't hold any critical data. I can > > format/destroy/reload stuff at will with no problems. Just let me know. > > I'll keep you on file. 8) If you have any C hacking experience, I > *really* need to know why the 'too many segs' error is being thrown. All > the indications I've received so far are that the region in question > shouldn't have "too many" segments, so I'm a bit confused. I added the following to sys/i386/i386/busdma_machdep.c: @@ -470,8 +470,13 @@ } while (buflen > 0); if (buflen != 0) { - printf("bus_dmamap_load: Too many segs! buf_len = 0x%lx\n", - (u_long)buflen); + int i; + printf("bus_dmamap_load: Too many segs! buf_len = 0x%lx, seg = %d, nseg = %d\n", + (u_long)buflen, seg, dmat->nsegments); + for (i = 0; i < dmat->nsegments; i++) + printf("bus_dmamap_load: seg %d addr 0x%lx len %d\n", + i, (u_long)dm_segments[i].ds_addr, + dm_segments[i].ds_len); error = EFBIG; } Then I get: bus_dmamap_load: Too many segs! buf_len = 0xea0, seg = 17, nseg = 16 bus_dmamap_load: seg 0 addr 0x8dabea0 len 352 bus_dmamap_load: seg 1 addr 0x8f8c000 len 4096 bus_dmamap_load: seg 2 addr 0x8f6d000 len 4096 bus_dmamap_load: seg 3 addr 0x8dae000 len 4096 bus_dmamap_load: seg 4 addr 0x8b0f000 len 4096 bus_dmamap_load: seg 5 addr 0x8c30000 len 4096 bus_dmamap_load: seg 6 addr 0x8e31000 len 4096 bus_dmamap_load: seg 7 addr 0x8b12000 len 4096 bus_dmamap_load: seg 8 addr 0x8cb3000 len 4096 bus_dmamap_load: seg 9 addr 0x8954000 len 4096 bus_dmamap_load: seg 10 addr 0x8ad5000 len 4096 bus_dmamap_load: seg 11 addr 0x8ab6000 len 4096 bus_dmamap_load: seg 12 addr 0x8bd7000 len 4096 bus_dmamap_load: seg 13 addr 0x8af8000 len 4096 bus_dmamap_load: seg 14 addr 0x8b79000 len 4096 bus_dmamap_load: seg 15 addr 0x7b7a000 len 4096 Someone is trying to do a 64k DMA to a non-page-aligned address. This requires 17 segments, but there are only 16 available. Any suggestions? thanks, andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 2 6: 1:33 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from arjun.niksun.com (gwnew.niksun.com [63.148.27.34]) by hub.freebsd.org (Postfix) with ESMTP id 8DC1437B424; Wed, 2 May 2001 06:01:30 -0700 (PDT) (envelope-from ath@niksun.com) Received: from stiegl.niksun.com (stiegl.niksun.com [10.0.0.44]) by arjun.niksun.com (8.9.3/8.9.3) with ESMTP id JAA17799; Wed, 2 May 2001 09:01:29 -0400 (EDT) (envelope-from ath@stiegl.niksun.com) Received: (from ath@localhost) by stiegl.niksun.com (8.9.2/8.8.7) id JAA14775; Wed, 2 May 2001 09:01:29 -0400 (EDT) (envelope-from ath) To: msmith@FreeBSD.ORG Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: AMI MegaRAID on 4.2-RELEASE and bus_dmamap_load errors References: <200105020234.WAA11069@stiegl.niksun.com> From: Andrew Heybey Date: 02 May 2001 09:01:29 -0400 In-Reply-To: Andrew Heybey's message of "Tue, 01 May 2001 22:34:41 -0400" Message-ID: <85y9sf7vme.fsf@stiegl.niksun.com> Lines: 39 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org To follow up on my own email: If I change rawio to page-align the buffer it uses for I/O, then the error messages go away. I also note that (for example), dev/aic7xxx_frebbsd.h has: /* * The number of dma segments supported. The sequencer can handle any number * of physically contiguous S/G entrys. To reduce the driver's memory * consumption, we limit the number supported to be sufficient to handle * the largest mapping supported by the kernel, MAXPHYS. Assuming the * transfer is as fragmented as possible and unaligned, this turns out to * be the number of paged sized transfers in MAXPHYS plus an extra element * to handle any unaligned residual. The sequencer fetches SG elements * in 128 byte chucks, so make the number per-transaction a nice multiple * of 16 (8 byte S/G elements). */ /* XXX Worth the space??? */ #define AHC_NSEG (roundup(btoc(MAXPHYS) + 1, 16)) While dev/amr/amrreg.h has: /* * We could actually use all 17 segments, but using only 16 means that * each scatter/gather map is 128 bytes in size, and thus we don't have to worry about * maps crossing page boundaries. * * The AMI documentation says that the limit is 26. Unfortunately, there's no way to * cleanly fit more than 16 entries in without a page boundary. But is this a concern, * since we allocate the s/g maps contiguously anyway? */ #define AMR_NSEG 16 I did not feel comfortable changing AMR_NSEG without fully understanding the problem with crossing a page boundary. andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 2 10:47:10 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mobile.hub.org (mobile.acadiau.ca [131.162.137.70]) by hub.freebsd.org (Postfix) with ESMTP id 108F837B423 for ; Wed, 2 May 2001 10:47:08 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by mobile.hub.org (8.11.3/8.11.1) with ESMTP id f42Hl6v54487 for ; Wed, 2 May 2001 14:47:07 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: mobile.hub.org: scrappy owned process doing -bs Date: Wed, 2 May 2001 14:47:06 -0300 (ADT) From: The Hermit Hacker To: Subject: Can a SCSI drive be *too* busy? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm trying to debug a hanging problem on one of our servers ... two drives in it, both appears to be hitting ~200tps simultaneously before it hangs ... is it possible to have to *too* busy that it will just hang? thanks ... Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 3 9:26:15 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from ct980320-b.blmngtn1.in.home.com (ct980320-b.blmngtn1.in.home.com [65.8.207.32]) by hub.freebsd.org (Postfix) with ESMTP id C04D037B423 for ; Thu, 3 May 2001 09:26:12 -0700 (PDT) (envelope-from mikes@ct980320-b.blmngtn1.in.home.com) Received: (from mikes@localhost) by ct980320-b.blmngtn1.in.home.com (8.11.3/8.11.3) id f43GQ5L62815; Thu, 3 May 2001 11:26:05 -0500 (EST) (envelope-from mikes) From: Mike Squires Message-Id: <200105031626.f43GQ5L62815@ct980320-b.blmngtn1.in.home.com> Subject: Re: Can a SCSI drive be *too* busy? In-Reply-To: "from The Hermit Hacker at May 2, 2001 02:47:06 pm" To: The Hermit Hacker Date: Thu, 3 May 2001 11:26:05 -0500 (EST) Cc: freebsd-scsi@freebsd.org X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I'm trying to debug a hanging problem on one of our servers ... two drives My information is based on experience with older hardware. Are the drives running too hot? You should be able to touch the drive board without discomfort. Drives running too hot will act strangely. Are the drives up to date on firmware? Early versions of the Seagate Barracuda and Cheetah had this kind of problem; the 9GB Barracuda wasn't stable until firmware 020. The update had to be factory-installed at the time. I also had this problem with Quantum Atlas II drives; in that case the firmware was flashable and I was able to download the firmware and flash my own drives after talking with vendor tech support. Is the controller up to date on firmware - this is especially a problem if the drives are newer than the controller. Try another controller - FBSD will boot of most of them without making any changes to the disks. I've heard of weird problems with onboard SCSI, possibly due to the lack of firmware updates (which have to come from the board vendor usually, and which may not be available at the same level as separate controllers). This is likely to be discussed on the comp.periph.scsi (sp?) newsgroup. I would also do the usual - replacing cabling, checking power supply connections and power supply, etc. I've had weird problems with a server which had a marginal (in terms of quality) power supply which put spikes onto the 5V bus when the fan started to fail. Try changing termination - if using drive termination, try an active terminator plugged into the cabling. I worked with a number of Archive 458XNP DAT changers which only worked reliably when using an NEC 6X CD-ROM as the terminating device (with an Adaptec 2940UW controller), and didn't work reliably (to the extent that they ever did work reliably) with either their own termination or a passive terminator plugged into the cable. MLS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 3 15:35: 8 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from relay.ioffe.rssi.ru (relay.ioffe.rssi.ru [194.85.224.33]) by hub.freebsd.org (Postfix) with ESMTP id 215F137B423; Thu, 3 May 2001 15:35:05 -0700 (PDT) (envelope-from kopts@astro.ioffe.rssi.ru) Received: from astro.ioffe.rssi.ru (astro.ioffe.rssi.ru [194.85.229.130]) by relay.ioffe.rssi.ru (8.9.1/8.9.1) with ESMTP id CAA20893; Fri, 4 May 2001 02:35:03 +0400 (MSD) Received: by astro.ioffe.rssi.ru (8.9.3/Clnt-2.14-AS-eef) id CAA93122; Fri, 4 May 2001 02:33:53 +0400 (MSD) Date: Fri, 4 May 2001 02:33:53 +0400 (MSD) From: Alexey Koptsevich To: Mike Smith Cc: scsi@freebsd.org Subject: Re: IDE RAID In-Reply-To: <200104191949.f3JJnge01789@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, > > BWT, is 3ware supported by FreeBSD in raid5 mode? > > 'man twe' tells only about 0 and 1 somewhy. > > Yes, it is. I haven't had any time lately to test it, but it's known to > work. I have asked 3ware tech support about RAID5 and have got the following: > 1. Is RAID5 supported now? If yes, what does the phrase "Drive arrays may > be configured in RAID 0, 1, 5 (available mid calendar year 2001)" in your > white paper about DiskSwitch architecture, > http://www.3ware.com/products/disk_switch_architecture.shtml > > RAID 5 is not currently availabel. For futher information on RAID 5 see: > http://www.3ware.com/support/raid5techbulletin.shtml What do you think about it? Has anybody tried RAID5 under FreeBSD? Thanks, Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 4 0: 3:12 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from cx587235-a.chnd1.az.home.com (cx587235-a.chnd1.az.home.com [24.1.255.253]) by hub.freebsd.org (Postfix) with ESMTP id 7DB7D37B424 for ; Fri, 4 May 2001 00:03:10 -0700 (PDT) (envelope-from jjreynold@home.com) Received: from whale.home-net (whale [192.168.1.2]) by cx587235-a.chnd1.az.home.com (8.11.3/8.11.3) with ESMTP id f4473AO25070 for ; Fri, 4 May 2001 00:03:10 -0700 (MST) (envelope-from jjreynold@home.com) Received: (from jjreynold@localhost) by whale.home-net (8.11.3/8.11.3) id f44738u24328; Fri, 4 May 2001 00:03:08 -0700 (MST) (envelope-from jjreynold@home.com) From: John Reynolds MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15090.21548.734131.478636@whale.home-net> Date: Fri, 4 May 2001 00:03:08 -0700 To: scsi@freebsd.org Subject: Yamaha CRW8824S is supported by cdrecord -- for archives X-Mailer: VM 6.88 under Emacs 20.7.1 Cc: Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just for archive purposes (for the next poor schlep searching for this answer), cdrecord definitely does support the Yamaha CDW8824S drive even though it's not listed on the webpage explicitly. cd1 at ahc0 bus 0 target 4 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 20.000MB/s transfers (20.000MHz, offset 15) I've been able to successfully burn audio CDs, multi-session CDs, and CDRW's at full 8x speed. Weeee!!! So, if you happen to pick one up cheap, you need not worry about it working with cdrecord under FreeBSD (4.3-STABLE as of this writing). One note though: "tosha" does NOT like the drive (whereas it liked the 4416S model). No biggie though--just use cdda2wav that comes with the cdrecord port. Works beautifully and rips at a approx 10-12x. -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation jreynold@sedona.ch.intel.com My opinions are mine, not Intel's. Running jjreynold@home.com FreeBSD 4.3-STABLE. FreeBSD: The Power to Serve. http://www.reynoldsnet.org/ Come join us!!! @ http://www.FreeBSD.org/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 4 11:49:22 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 C151E37B43C for ; Fri, 4 May 2001 11:49:18 -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 UAA23795; Fri, 4 May 2001 20:49:15 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f44IR2R92623; Fri, 4 May 2001 20:27:02 +0200 (MET DST) (envelope-from j) Date: Fri, 4 May 2001 20:27:02 +0200 (MET DST) Message-Id: <200105041827.f44IR2R92623@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden 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 References: <15090.21548.734131.478636@whale.home-net> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: Yamaha CRW8824S is supported by cdrecord -- for archives X-Original-Newsgroups: local.freebsd.scsi To: freebsd-scsi@freebsd.org Cc: Oliver Fromme Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org John Reynolds wrote: > cd1: Removable CD-ROM SCSI-2 device > One note though: "tosha" does NOT like the drive (whereas it liked > the 4416S model). I found tosha to be well-configurable. I've got a uriah # camcontrol inquiry cd1 pass5: Removable CD-ROM SCSI-2 device pass5: Serial Number ' pass5: 10.000MB/s transfers (10.000MHz, offset 7) (strange serial number, isn't it? :) It doesn't work with tosha out of the box. But looking into /usr/local/etc/tosharc, i found that adding "YAMAHA" "CRW4260" "" 0xd8 0 0x00 0 10 0 "YAMAHA" "CRW4416" "" 0xd8 0 0x00 0 10 0 "YAMAHA" "CRW2100S" "" 0xd8 0 0x00 0 10 0 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ "YAMAHA" "" "" 0x28 1 0x00 0 10 0 that line did the trick. Didn't feed that back to Olliver Fromme by now... Ok, Cc'ed. -- 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 From owner-freebsd-scsi Sat May 5 1: 9:33 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from amsmta06-svc.chello.nl (mail-out.chello.nl [213.46.240.7]) by hub.freebsd.org (Postfix) with ESMTP id 9927437B422 for ; Sat, 5 May 2001 01:09:28 -0700 (PDT) (envelope-from rklinkien@chello.nl) Received: from sonic ([213.93.216.127]) by amsmta06-svc.chello.nl (InterMail vK.4.03.02.00 201-232-124 license f747fce8063b429e7fcd66ee14ce8c58) with SMTP id <20010505081100.CPSM471.amsmta06-svc@sonic> for ; Sat, 5 May 2001 10:11:00 +0200 Message-ID: <013401c0d53a$f1663280$0404a8c0@smalweer.nl> From: "Ron Klinkien" To: Subject: Recovered data with positive head offset field replaceable unit msg Date: Sat, 5 May 2001 10:11:09 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0131_01C0D54B.B4CD70C0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0131_01C0D54B.B4CD70C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi SCSI wizards, On one of my FreeBSD machines I found this rather strange scsi message: > (da1:sym0:0:8:0): READ(06). CDB: 8 8 1 90 10 0 > (da1:sym0:0:8:0): RECOVERED ERROR info:80198 asc:17,2 > (da1:sym0:0:8:0): Recovered data with positive head offset field = replaceable unit: df sks:80,12 Can anybody point me to what kind of message this is? Scsi driver, bad = block remapped? I have this controller: sym0: <875> port 0xd000-0xd0ff mem = 0xe0000000-0xe0000fff,0xe0800000-0xe08000ff irq 12 at device 10.0 o n pci0 sym0: Symbios NVRAM, ID 7, Fast-20, SE, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. sym0: SCAN FOR LUNS disabled for targets 0 1 2 3 4 5 6. And da1 is: da1 at sym0 bus 0 target 8 lun 0 da1: Fixed Direct Access SCSI-2 device=20 da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing = Enabled da1: 4094MB (8385121 512 byte sectors: 255H 63S/T 521C) Thanks in advance. Regards, Ron. ------=_NextPart_000_0131_01C0D54B.B4CD70C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi SCSI wizards,
 
On one of my FreeBSD machines I = found
this rather strange scsi = message:
 
> (da1:sym0:0:8:0): READ(06). CDB: 8 = 8 1 90 10=20 0
> (da1:sym0:0:8:0): RECOVERED ERROR info:80198 asc:17,2
>=20 (da1:sym0:0:8:0): Recovered data with positive head offset field = replaceable=20 unit: df sks:80,12
 
Can anybody point me to what kind of = message this=20 is? Scsi driver, bad block remapped?
 
I have this controller:
sym0: <875> port 0xd000-0xd0ff = mem=20 0xe0000000-0xe0000fff,0xe0800000-0xe08000ff irq 12 at device 10.0 o
n = pci0
sym0: Symbios NVRAM, ID 7, Fast-20, SE, parity checking
sym0: = open=20 drain IRQ line driver, using on-chip SRAM
sym0: using = LOAD/STORE-based=20 firmware.
sym0: SCAN FOR LUNS disabled for targets 0 1 2 3 4 5=20 6.
 
And da1 is:
da1 at sym0 bus 0 target 8 lun = 0
da1:=20 <SEAGATE ST34371W SUN4.2G 7462> Fixed Direct Access SCSI-2 device =
da1:=20 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing=20 Enabled
da1: 4094MB (8385121 512 byte sectors: 255H 63S/T=20 521C)
 
 
Thanks in advance.
 
Regards,
Ron.
 
------=_NextPart_000_0131_01C0D54B.B4CD70C0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat May 5 4:55:58 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from ureach.com (mail.ureach.com [63.150.151.36]) by hub.freebsd.org (Postfix) with ESMTP id 87BCA37B424 for ; Sat, 5 May 2001 04:55:51 -0700 (PDT) (envelope-from pechter@ureach.com) Received: from stage21.ureach.com (stage21.ureach.com [172.16.2.232]) by ureach.com (8.9.1/8.8.5) with ESMTP id HAA17789; Sat, 5 May 2001 07:55:49 -0400 Received: (from nobody@localhost) by stage21.ureach.com (8.9.3/8.9.1) id HAA22713; Sat, 5 May 2001 07:55:49 -0400 Date: Sat, 5 May 2001 07:55:49 -0400 Message-Id: <200105051155.HAA22713@stage21.ureach.com> To: "Ron Klinkien" , freebsd-scsi@FreeBSD.ORG From: Bill Pechter Reply-To: Subject: Re: Recovered data with positive head offset field replaceable unit msg Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-vsuite-type: e Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi SCSI wizards, > > On one of my FreeBSD machines I found > this rather strange scsi message: > > > (da1:sym0:0:8:0): READ(06). CDB: 8 8 1 90 10 0 > > (da1:sym0:0:8:0): RECOVERED ERROR info:80198 asc:17,2 > (da1:sym0:0:8:0): Recovered data with positive head offset field replaceable unit: df sks:80,12 > > Thanks in advance. > > Regards, > Ron. Haven't seen something like that in years. In the old days of SMD disks and DEC RP06's and RM05's (mid 80's), I'd have said it was a servo tracking issue with the heads missing the data by a bit (possible bad spot on disk) which was recovered by the disk controller offsetting the heads a bit towards the center of the drive just a bit. The data was recoverable... by the drive moving the head just a little. Things like this were caused by bad spot on disk (servo platter or data platter) misalignment, dirt on the drive rails that caused the heads to bounce a bit while seeking or trying to stay on track, power fluctuations. Some idiot banging into the disks during a read operation. Folks -- do things like this still happen with modern scsi drives. Misalignment is probably out. Embedded servo's tend to eliminate a weak servo head. Dirt on drive rails -- nah. If it's a one shot error I wouldn't worry much -- but if it reoccurs... it's a problem. I've got a problem on one of the drives here that I know is the drive.da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da1: 8669MB (17755614 512 byte sectors: 255H 63S/T 1105C) I get errors like this repeatedly on some parts of the disk: I plan to reformat it... I've considered turning off tagged queueing... sym0:1:control msgout: 80 20 79 d. sym0:1:control msgout: 80 20 6b d. (da1:sym0:0:1:0): WRITE(10). CDB: 2a 0 0 e2 4b 15 0 0 10 0 (da1:sym0:0:1:0): ABORTED COMMAND info:cf4b25 asc:4e,0 (da1:sym0:0:1:0): Overlapped commands attempted field replaceable unit: 1 sym0:1:control msgout: 80 20 1b d. sym0:1: message d sent on bad reselection. --Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat May 5 7:36:47 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from amsmta01-svc.chello.nl (mail-out.chello.nl [213.46.240.7]) by hub.freebsd.org (Postfix) with ESMTP id 846BB37B422 for ; Sat, 5 May 2001 07:36:42 -0700 (PDT) (envelope-from rklinkien@chello.nl) Received: from sonic ([213.93.216.127]) by amsmta01-svc.chello.nl (InterMail vK.4.03.02.00 201-232-124 license f747fce8063b429e7fcd66ee14ce8c58) with SMTP id <20010505142955.ENBN23593.amsmta01-svc@sonic> for ; Sat, 5 May 2001 16:29:55 +0200 Message-ID: <001d01c0d571$09711300$0404a8c0@smalweer.nl> From: "Ron Klinkien" To: Subject: Re: Recovered data with positive head offset field replaceable unit msg Date: Sat, 5 May 2001 16:38:23 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Bill, Back in the old days (1994) I ported ProbeSCSI from Solaris to the Amiga OS, so I know some things about SCSI, but these kind off messages make me a bit nervous.. ;-) Luckily I only got one of them. After investigation of the box (my firewall/mail/web server) I placed an extra fan between my 2 SCSI drives to cool them a bit. Did some buildworlds and stuff, and didn't found anything strange, so i'm a bit more relaxed now... The SCSI drive is not that old btw, it even has an SCA80 connector, it's an hot swappable disk that SUN uses in it's E450 machines for example. Thanks for your reply. Ron. > ----- Original Message ----- > From: "Bill Pechter" > To: "Ron Klinkien" ; > Sent: Saturday, May 05, 2001 1:55 PM > Subject: Re: Recovered data with positive head offset field replaceable unit > msg > > > > > Hi SCSI wizards, > > > > > > On one of my FreeBSD machines I found > > > this rather strange scsi message: > > > > > > > (da1:sym0:0:8:0): READ(06). CDB: 8 8 1 90 10 0 > > > > (da1:sym0:0:8:0): RECOVERED ERROR info:80198 asc:17,2 > > > (da1:sym0:0:8:0): Recovered data with positive head offset > > field replaceable unit: df sks:80,12 > > > > > > Thanks in advance. > > > > > > Regards, > > > Ron. > > > > Haven't seen something like that in years. > > In the old days of SMD disks and DEC RP06's and RM05's (mid > > 80's), I'd have said it was a servo tracking issue with the > > heads missing the data by a bit (possible bad spot on disk) > > which was recovered by the disk controller offsetting the heads > > a bit towards the center of the drive just a bit. > > > > The data was recoverable... by the drive moving the head just a > > little. Things like this were caused by bad spot on disk (servo > > platter or data platter) misalignment, dirt on the drive rails > > that caused the heads to bounce a bit while seeking or trying to > > stay on track, power fluctuations. Some idiot banging into the > > disks during a read operation. > > > > Folks -- do things like this still happen with modern scsi > > drives. Misalignment is probably out. Embedded servo's tend to > > eliminate a weak servo head. Dirt on drive rails -- nah. > > > > If it's a one shot error I wouldn't worry much -- but if it > > reoccurs... it's a problem. > > > > I've got a problem on one of the drives here that I know is the > > > > drive.da1: Fixed Direct Access SCSI-2 > > device > > da1: 10.000MB/s transfers (10.000MHz, offset 15), Tagged > > Queueing Enabled > > da1: 8669MB (17755614 512 byte sectors: 255H 63S/T 1105C) > > > > I get errors like this repeatedly on some parts of the disk: > > I plan to reformat it... I've considered turning off tagged > > queueing... > > > > sym0:1:control msgout: 80 20 79 d. > > sym0:1:control msgout: 80 20 6b d. > > (da1:sym0:0:1:0): WRITE(10). CDB: 2a 0 0 e2 4b 15 0 0 10 0 > > (da1:sym0:0:1:0): ABORTED COMMAND info:cf4b25 asc:4e,0 > > (da1:sym0:0:1:0): Overlapped commands attempted field > > replaceable unit: 1 > > > > sym0:1:control msgout: 80 20 1b d. > > sym0:1: message d sent on bad reselection. > > > > --Bill > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat May 5 10:17:52 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 753E837B42C for ; Sat, 5 May 2001 10:17:47 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA12269; Sat, 5 May 2001 10:17:39 -0700 Date: Sat, 5 May 2001 10:17:38 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Ron Klinkien Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Recovered data with positive head offset field replaceable unit msg In-Reply-To: <013401c0d53a$f1663280$0404a8c0@smalweer.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org y On Sat, 5 May 2001, Ron Klinkien wrote: > Hi SCSI wizards, > > On one of my FreeBSD machines I found > this rather strange scsi message: > > > (da1:sym0:0:8:0): READ(06). CDB: 8 8 1 90 10 0 > > (da1:sym0:0:8:0): RECOVERED ERROR info:80198 asc:17,2 > > (da1:sym0:0:8:0): Recovered data with positive head offset field replaceable unit: df sks:80,12 > > > Can anybody point me to what kind of message this is? Scsi driver, bad block remapped? Heh. Tsk. It's the drive saying "I was able to read the data, but only after I offset the head toward the drive center by a sub-track width amount". I haven't seen such messages since SMD days.... Do you have the drive in a strange physical position? Or did you kick the system at some point? > > I have this controller: > sym0: <875> port 0xd000-0xd0ff mem 0xe0000000-0xe0000fff,0xe0800000-0xe08000ff irq 12 at device 10.0 o > n pci0 > sym0: Symbios NVRAM, ID 7, Fast-20, SE, parity checking > sym0: open drain IRQ line driver, using on-chip SRAM > sym0: using LOAD/STORE-based firmware. > sym0: SCAN FOR LUNS disabled for targets 0 1 2 3 4 5 6. > > > And da1 is: > da1 at sym0 bus 0 target 8 lun 0 > da1: Fixed Direct Access SCSI-2 device > da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled > da1: 4094MB (8385121 512 byte sectors: 255H 63S/T 521C) > > > > Thanks in advance. > > Regards, > Ron. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat May 5 11:17:21 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from amsmta05-svc.chello.nl (mail-out.chello.nl [213.46.240.7]) by hub.freebsd.org (Postfix) with ESMTP id 015CF37B422 for ; Sat, 5 May 2001 11:17:19 -0700 (PDT) (envelope-from rklinkien@chello.nl) Received: from sonic ([213.93.216.127]) by amsmta05-svc.chello.nl (InterMail vK.4.03.02.00 201-232-124 license f747fce8063b429e7fcd66ee14ce8c58) with SMTP id <20010505181946.FPGW14682.amsmta05-svc@sonic>; Sat, 5 May 2001 20:19:46 +0200 Message-ID: <002601c0d58f$dabe0620$0404a8c0@smalweer.nl> From: "Ron Klinkien" To: Cc: References: Subject: Re: Recovered data with positive head offset field replaceable unit msg Date: Sat, 5 May 2001 20:18:58 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > (da1:sym0:0:8:0): Recovered data with positive head offset field replaceable unit: df sks:80,12 > > > > > > Can anybody point me to what kind of message this is? Scsi driver, bad block remapped? > > > Heh. Tsk. It's the drive saying "I was able to read the data, but only after > I offset the head toward the drive center by a sub-track width amount". > > I haven't seen such messages since SMD days.... > > Do you have the drive in a strange physical position? Or did you kick > the system at some point? Hi Matthew, The drive is normally mounted in a midi-tower case, and the system stands in the corner of a room. I guess it's one of those msgs you only see ones in your life, so I make a wish; please HDD continue don't fail on me...;-) Regards, Ron. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat May 5 11:18:46 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 0B83E37B422 for ; Sat, 5 May 2001 11:18:44 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA12438; Sat, 5 May 2001 11:18:42 -0700 Date: Sat, 5 May 2001 11:18:41 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Ron Klinkien Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Recovered data with positive head offset field replaceable unit msg In-Reply-To: <002601c0d58f$dabe0620$0404a8c0@smalweer.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 5 May 2001, Ron Klinkien wrote: > > > > (da1:sym0:0:8:0): Recovered data with positive head offset field > replaceable unit: df sks:80,12 > > > > > > > > > Can anybody point me to what kind of message this is? Scsi driver, bad > block remapped? > > > > > > Heh. Tsk. It's the drive saying "I was able to read the data, but only > after > > I offset the head toward the drive center by a sub-track width amount". > > > > I haven't seen such messages since SMD days.... > > > > Do you have the drive in a strange physical position? Or did you kick > > the system at some point? > > Hi Matthew, > > The drive is normally mounted in a midi-tower case, and the system stands in > the > corner of a room. > > I guess it's one of those msgs you only see ones in your life, so I make a > wish; please HDD continue don't fail on me...;-) If you have the money, I'd get another. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message