From owner-freebsd-scsi Sun Mar 14 0: 8:19 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B91D14F3B for ; Sun, 14 Mar 1999 00:08:14 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id BAA11545; Sun, 14 Mar 1999 01:07:52 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199903140807.BAA11545@panzer.plutotech.com> Subject: Re: Strange SCSI QIC tape behaviour In-Reply-To: <19990314083709.50127@uriah.heep.sax.de> from J Wunsch at "Mar 14, 1999 8:37: 9 am" To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 14 Mar 1999 01:07:52 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org J Wunsch wrote... [ Matt can handle the tape problems ] > I also noticed that the sa driver doesn't claim device entries in > DEVFS. This should be easy to fix (and a lot more of the CAM entries > are missing, only the da's are there), so i could try to fix this > myself. IIRC, the problem is that the version of DEVFS that we have now can't handle device arrival/removal events from an interrupt context. Julian had a version of DEVFS/SLICE at one point that could handle being called from an interrupt context, however. Bruce looked into the DEVFS/CAM thing a while back, and conculded it wouldn't work for now. If you want details, ask him. So, the bottom line is, if you're using CAM, you can't use DEVFS. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message