From owner-freebsd-usb@FreeBSD.ORG Tue Apr 22 21:03:17 2008 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DBC3B106564A; Tue, 22 Apr 2008 21:03:17 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from hosted.kievnet.com (hosted.kievnet.com [193.138.144.10]) by mx1.freebsd.org (Postfix) with ESMTP id 9B1808FC1C; Tue, 22 Apr 2008 21:03:17 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from localhost ([127.0.0.1] helo=edge.pp.kiev.ua) by hosted.kievnet.com with esmtpa (Exim 4.62) (envelope-from ) id 1JoOuG-0003V2-Up; Tue, 22 Apr 2008 23:16:01 +0300 Message-ID: <480E4780.6010106@icyb.net.ua> Date: Tue, 22 Apr 2008 23:16:00 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.12 (X11/20080320) MIME-Version: 1.0 To: freebsd-usb@freebsd.org, freebsd-scsi@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Subject: issue with umass plugged-in during boot up X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Apr 2008 21:03:18 -0000 This is sort of a follow up to the issue of kernel panic when a system is booted with umass device plugged in. Cursory point: I remember having the issue myself when I loaded scsi_low and cam as modules. I blamed it on sg being present in cam.ko, but I have no facts. After I added scsi devices to kernel (sans sg) I stopped having the panics. BTW, I use RELENG_7, i386, UP. Anyway, I see a different issue with booting while a umass device is connected. First issue was that k3b hasn't found my two cd/atapicam devices. Then I executed camcontrol rescan all, it failed with EINVAL. camcontrol reset all - the same error. ktrace showed that the error came from ioctl on xpt device. I rebooted without the umass device and everything went back to normal. I'll try to do more debugging later. -- Andriy Gapon