From owner-freebsd-scsi Mon Nov 27 04:21:52 1995 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id EAA26480 for freebsd-scsi-outgoing; Mon, 27 Nov 1995 04:21:52 -0800 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id EAA26468 for ; Mon, 27 Nov 1995 04:21:26 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id NAA18111; Mon, 27 Nov 1995 13:21:10 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id NAA05592; Mon, 27 Nov 1995 13:21:26 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id KAA05088; Mon, 27 Nov 1995 10:04:45 +0100 From: J Wunsch Message-Id: <199511270904.KAA05088@uriah.heep.sax.de> Subject: Re: kern/820: scsi tape problems To: mark@linus.demon.co.uk (Mark Valentine) Date: Mon, 27 Nov 1995 10:04:44 +0100 (MET) Cc: julian@ref.tfs.com, joerg_wunsch@uriah.heep.sax.de, freebsd-scsi@freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199511250259.CAA00258@linus.demon.co.uk> from "Mark Valentine" at Nov 25, 95 02:59:21 am X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 457 Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk As Mark Valentine wrote: > > This allowed to me to successfully read the tape (yes, my tape drive > really did take >100s to read that block!). Peter? Do you remember our discussion about SCSI adaptor timeouts? We should bring this up again in freebsd-scsi. I could bury out the old mails. -- 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. ;-) From owner-freebsd-scsi Mon Nov 27 06:41:07 1995 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id GAA03794 for freebsd-scsi-outgoing; Mon, 27 Nov 1995 06:41:07 -0800 Received: from hda.com (hda.com [199.232.40.182]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id GAA03785 for ; Mon, 27 Nov 1995 06:41:01 -0800 Received: (from dufault@localhost) by hda.com (8.6.11/8.6.9) id JAA04871; Mon, 27 Nov 1995 09:35:05 -0500 From: Peter Dufault Message-Id: <199511271435.JAA04871@hda.com> Subject: Re: kern/820: scsi tape problems To: joerg_wunsch@uriah.heep.sax.de Date: Mon, 27 Nov 1995 09:35:04 -0500 (EST) Cc: mark@linus.demon.co.uk, julian@ref.tfs.com, freebsd-scsi@freebsd.org In-Reply-To: <199511270904.KAA05088@uriah.heep.sax.de> from "J Wunsch" at Nov 27, 95 10:04:44 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1619 Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk > > This allowed to me to successfully read the tape (yes, my tape drive > > really did take >100s to read that block!). > > Peter? Do you remember our discussion about SCSI adaptor timeouts? > > We should bring this up again in freebsd-scsi. I could bury out the > old mails. Host adapter timeouts or transaction timeouts? I have mail on transaction timeouts and on my "TODO someday soon" list, and I don't think it applies in this case - we talked about both retrying "forever" for a "device is in the process of becoming ready" error and to delay a bit (where "a bit" gets longer between each retry) instead of doing an immediate retry - I don't think we talked about something that takes an unexpectedly long amount of time (100s for a read of a tape block) and that we (think we) can't abort. This case was a transaction that timed out, and then we tried to abort it (I'm not sure what the 1542 firmware does when you tell it to abort a transaction - I don't know if it does a BUS DEVICE RESET or what, and I don't have a 1542 manual) and we apparently then decided our host adapter was dead when it couldn't abort that transaction in four seconds. So there are two problems here, one general and one 1542 specific: 1. It would be nice to be able to tune the timeouts on a device by device basis for when you have a device with an unusually long timeout; 2. That "abort transaction" / "host adapter is hosed" branch needs some fixing. -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-scsi Mon Nov 27 18:07:43 1995 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA20604 for freebsd-scsi-outgoing; Mon, 27 Nov 1995 18:07:43 -0800 Received: from wiley.csusb.edu (wiley.csusb.edu [139.182.2.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id SAA20597 for ; Mon, 27 Nov 1995 18:07:38 -0800 Received: (from rmallory@localhost) by wiley.csusb.edu (8.6.11/8.6.11) id SAA25717 for freebsd-scsi@freefall.cdrom.com; Mon, 27 Nov 1995 18:12:27 -0800 From: Rob Mallory Message-Id: <199511280212.SAA25717@wiley.csusb.edu> Subject: NCR825 and 810 on ASUSTP4xe To: freebsd-scsi@freefall.FreeBSD.org Date: Mon, 27 Nov 1995 18:12:26 -0800 (PST) X-Mailer: ELM [version 2.4 PL22] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 828 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk I have been running a generic NCR825 with bios 3.04 for some time. my ASUS tp4xe has 3.07 NCR bios in it. (will this drive the 825?) I've been trying to get my new NCR810 working also but can't find the magic incantation. When both are installed, the 3.07 boots up and locks up(nothing gets probed). the 810 alone works fine. I've also noticed some bios geometry bugs in the 3.04 bios in which slowaris, freebsd, and win NT all seem to grab a different bios geom and therefore fdisk/write the bootblock the drive differently on install. is there any way I can disable the 825 rom, (removing it didn' work) or easily get a 3.07 rom... I know I can 'play' a bit more and force some sane geometries, but I'd really like to be RTLB (running the latest bios:) ...any ideas? -Rob Mallory [rmallory@csusb.edu] From owner-freebsd-scsi Thu Nov 30 16:10:45 1995 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA06503 for freebsd-scsi-outgoing; Thu, 30 Nov 1995 16:10:45 -0800 Received: from tcptest.psc.edu (tcptest.psc.edu [128.182.61.120]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA06498 for ; Thu, 30 Nov 1995 16:10:42 -0800 Received: (from peterb@localhost) by tcptest.psc.edu (8.7.1/8.7.1) id TAA19504; Thu, 30 Nov 1995 19:18:14 -0500 (EST) Date: Thu, 30 Nov 1995 19:18:14 -0500 (EST) Message-Id: <199512010018.TAA19504@tcptest.psc.edu> From: Peter Berger To: freebsd-scsi@freebsd.org Subject: question: Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk what's the rationale for returning EACCES when trying to ioctl a device mounted read-only? inquiring minds want to know. (I encountered this problem with xmcd, which was failing because of it. I decided it was easier to change the kernel than to compile Motif, so....) From owner-freebsd-scsi Thu Nov 30 17:35:35 1995 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA11501 for freebsd-scsi-outgoing; Thu, 30 Nov 1995 17:35:35 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id RAA11470 for ; Thu, 30 Nov 1995 17:35:22 -0800 Received: (from julian@localhost) by ref.tfs.com (8.6.12/8.6.9) id RAA13235; Thu, 30 Nov 1995 17:33:47 -0800 From: Julian Elischer Message-Id: <199512010133.RAA13235@ref.tfs.com> Subject: Re: question: To: peterb@tcptest.psc.edu (Peter Berger) Date: Thu, 30 Nov 1995 17:33:46 -3200 (PST) Cc: freebsd-scsi@freebsd.org In-Reply-To: <199512010018.TAA19504@tcptest.psc.edu> from "Peter Berger" at Nov 30, 95 07:18:14 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 484 Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk The ioctls can do things like 'format device' (what do you mean 'mounted' read only) you shouldn't be accessing a device for ioctls when it's 'mounted' (as in mounting a disk partition). > > > what's the rationale for returning EACCES when trying to ioctl a > device mounted read-only? inquiring minds want to know. > > (I encountered this problem with xmcd, which was failing because of > it. I decided it was easier to change the kernel than to compile > Motif, so....) > From owner-freebsd-scsi Thu Nov 30 17:46:28 1995 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA12318 for freebsd-scsi-outgoing; Thu, 30 Nov 1995 17:46:28 -0800 Received: from tcptest.psc.edu (tcptest.psc.edu [128.182.61.120]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id RAA12312 for ; Thu, 30 Nov 1995 17:46:26 -0800 Received: (from peterb@localhost) by tcptest.psc.edu (8.7.1/8.7.1) id UAA19782; Thu, 30 Nov 1995 20:53:57 -0500 (EST) Date: Thu, 30 Nov 1995 20:53:57 -0500 (EST) Message-Id: <199512010153.UAA19782@tcptest.psc.edu> From: Peter Berger To: julian@ref.tfs.com CC: freebsd-scsi@freebsd.org In-reply-to: <199512010133.RAA13235@ref.tfs.com> (message from Julian Elischer on Thu, 30 Nov 1995 17:33:46 -3200 (PST)) Subject: Re: question: Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk > From: Julian Elischer > Date: Thu, 30 Nov 1995 17:33:46 -3200 (PST) > Cc: freebsd-scsi@freebsd.org > X-Mailer: ELM [version 2.4 PL24] > Content-Type: text > > The ioctls can do things like 'format device' > (what do you mean 'mounted' read only) > you shouldn't be accessing a device for ioctls when it's 'mounted' > (as in mounting a disk partition). I mis-spoke; I meant "opened" read only. Is this a standard 4.4BSD Lite feature, or a specific FreeBSD-ism? > > > > > > what's the rationale for returning EACCES when trying to ioctl a > > device mounted read-only? inquiring minds want to know. > > > > (I encountered this problem with xmcd, which was failing because of > > it. I decided it was easier to change the kernel than to compile > > Motif, so....) > > > > From owner-freebsd-scsi Thu Nov 30 17:48:13 1995 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA12466 for freebsd-scsi-outgoing; Thu, 30 Nov 1995 17:48:13 -0800 Received: from tcptest.psc.edu (tcptest.psc.edu [128.182.61.120]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id RAA12446 ; Thu, 30 Nov 1995 17:48:05 -0800 Received: (from peterb@localhost) by tcptest.psc.edu (8.7.1/8.7.1) id UAA19491; Thu, 30 Nov 1995 20:55:35 -0500 (EST) Date: Thu, 30 Nov 1995 20:55:35 -0500 (EST) Message-Id: <199512010155.UAA19491@tcptest.psc.edu> From: Peter Berger To: julian@ref.tfs.com CC: freebsd-scsi@freebsd.org, freebsd-doc@freebsd.org In-reply-to: <199512010133.RAA13235@ref.tfs.com> (message from Julian Elischer on Thu, 30 Nov 1995 17:33:46 -3200 (PST)) Subject: Re: question: Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk One more note; the ioctl(2) man page does not list EACCES as a possible error, so it should probably be updated. Peter > From: Julian Elischer > Date: Thu, 30 Nov 1995 17:33:46 -3200 (PST) > Cc: freebsd-scsi@freebsd.org > X-Mailer: ELM [version 2.4 PL24] > Content-Type: text > > The ioctls can do things like 'format device' > (what do you mean 'mounted' read only) > you shouldn't be accessing a device for ioctls when it's 'mounted' > (as in mounting a disk partition). > > > > > > > > > what's the rationale for returning EACCES when trying to ioctl a > > device mounted read-only? inquiring minds want to know. > > > > (I encountered this problem with xmcd, which was failing because of > > it. I decided it was easier to change the kernel than to compile > > Motif, so....) > > > >