Date: Fri, 10 Oct 1997 21:23:37 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: scsi@FreeBSD.ORG Cc: tarkhil@mgt.msk.ru Subject: Re: Trouble with dump on ncr Message-ID: <19971010212337.WB21205@uriah.heep.sax.de> In-Reply-To: <199710100624.KAA06724@asteroid.mgt.msk.ru>; from Alexander B. Povolotsky on Oct 10, 1997 10:24:19 %2B0400 References: <199710100624.KAA06724@asteroid.mgt.msk.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
As Alexander B. Povolotsky wrote: > I'm trying to make dump, and constantly unable to do it. > asteroid#/usr/FreeBSD-CVS/src 138_> Oct 10 10:21:06 asteroid /kernel: assertion "cp" failed: file "../../pci/ncr.c", line 6191 > Oct 10 10:21:07 asteroid /kernel: assertion "cp" failed: file "../../pci/ncr.c", line 6191 > Oct 10 10:21:07 asteroid /kernel: sd0(ncr0:0:0): COMMAND FAILED (4 28) @f0461000. > (ncr0:0:0): "IBM DALS-3540 S60E" type 0 fixed SCSI 2 > sd0(ncr0:0:0): Direct-Access > sd0(ncr0:0:0): 10.0 MB/s (100 ns, offset 8) > 516MB (1056768 512 byte sectors) Re-read the freebsd-scsi archives... and then either disable tagged command queuing (``options FAILSAFE''), or alternatively remove all calls to scsi_start_unit() in /sys/scsi/sd.c. Btw., i think we are safe to make the latter change anyway. As i've already mentioned in a private mail to Justin, i've recently proven that the calls to scsi_start_unit() are completely useless and don't work. (I had taken down a disk manually, and later tried to implicitly start it by opening it again.) Thus, by removing these calls, we won't break anything that's not already broken. Anybody objecting? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19971010212337.WB21205>