Date: Tue, 11 Jun 1996 18:26:14 -0400 (EDT) From: "matthew c. mead" <mmead@Glock.COM> To: se@zpr.uni-koeln.de (Stefan Esser) Cc: hackers@freebsd.org Subject: Re: ST43400N Message-ID: <199606112226.SAA00264@Glock.COM> In-Reply-To: <199606112010.AA13884@Sisyphos> from "Stefan Esser" at Jun 11, 96 10:10:41 pm
next in thread | previous in thread | raw e-mail | index | archive | help
Stefan Esser writes: > On Jun 11, 16:01, "matthew c. mead" wrote: > } Subject: Re: ST43400N > } > If you are running a -current kernel, then please try > } > one built with "options FAILSAFE". This will disable > } > use of tagged command queues, which are the most likely > } > cause of the problem you report. > } > If the drive works with tags disabled, then I'll send > } > further directions to find out whether it is possible > } > to work around that problem. (You may comment out the > } > call to scsi_start_unit() in /sys/scsi/sd.c for a test.) > } Do the above two paragraphs apply to a 2.1.0-RELEASE > } kernel as well? This drive is on a 2.1.0-R system. > Look at /sys/pci/ncr.c (line 6242 in -stable): > ncr_setmaxtags (tp, SCSI_NCR_MAX_TAGS); > Change this into: > ncr_setmaxtags (tp, 0); > This is part of what FAILSAFE does in current kernels ... > The paragraph about scsi_start_unit() applies to 2.1.0R. Ahh, thanks for all of these tips. I didn't end up having to use any of them, thankfully. The drive started working just fine after I low level formatted it. Thanks to everyone that gave me suggestions and detailed their drive configurations! -matt -- Matthew C. Mead mmead@goof.com http://www.goof.com/~mmead/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606112226.SAA00264>