From owner-freebsd-bugs  Thu Jul  4  3:20: 7 2002
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id EACE037B400
	for <freebsd-bugs@hub.freebsd.org>; Thu,  4 Jul 2002 03:20:04 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9554543E09
	for <freebsd-bugs@hub.freebsd.org>; Thu,  4 Jul 2002 03:20:04 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1])
	by freefall.freebsd.org (8.12.4/8.12.4) with ESMTP id g64AK4JU012648
	for <freebsd-bugs@freefall.freebsd.org>; Thu, 4 Jul 2002 03:20:04 -0700 (PDT)
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.12.4/8.12.4/Submit) id g64AK3hf012646;
	Thu, 4 Jul 2002 03:20:03 -0700 (PDT)
Date: Thu, 4 Jul 2002 03:20:03 -0700 (PDT)
Message-Id: <200207041020.g64AK3hf012646@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
Cc: 
From: ripley@nostromo.in-berlin.de
Subject: Re: kern/39805: 4.6R install panics with umass0 device conne
Reply-To: ripley@nostromo.in-berlin.de
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-bugs.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-bugs>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-bugs>
X-Loop: FreeBSD.org

The following reply was made to PR kern/39805; it has been noted by GNATS.

From: ripley@nostromo.in-berlin.de
To: freebsd-gnats-submit@FreeBSD.org
Cc: ripley@nostromo.in-berlin.de
Subject: Re: kern/39805: 4.6R install panics with umass0 device conne
Date: Thu, 4 Jul 2002 12:16:57 +0200

 Further investigation indicates the umass0 driver is allergic to the device.
 I can look up the virtual scsi bus with camcontrol but any access to
 the device (like "fdisk da0" with medium inserted) results in a panic.
 
 It seems there are two issues at hand:
 1.) The device is not accessed properly (presumably it should just be
 like any other generic mass storage USB drive)
 2.) The driver's reaction on error conditions is faulty.
 
 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message