From owner-freebsd-usb@FreeBSD.ORG Mon Jul 14 17:05:13 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 53E9D1065675 for ; Mon, 14 Jul 2008 17:05:13 +0000 (UTC) (envelope-from prvs=pschmehl_lists=0746e7376@tx.rr.com) Received: from ip-relay-002.utdallas.edu (ip-relay-002.utdallas.edu [129.110.20.112]) by mx1.freebsd.org (Postfix) with ESMTP id 3AA158FC0A for ; Mon, 14 Jul 2008 17:05:13 +0000 (UTC) (envelope-from prvs=pschmehl_lists=0746e7376@tx.rr.com) X-Group: RELAYLIST X-IronPort-AV: E=Sophos;i="4.30,360,1212382800"; d="scan'208";a="3692344" Received: from smtp3.utdallas.edu ([129.110.20.110]) by ip-relay-002.utdallas.edu with ESMTP; 14 Jul 2008 11:36:39 -0500 Received: from utd65257.utdallas.edu (utd65257.utdallas.edu [129.110.3.28]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp3.utdallas.edu (Postfix) with ESMTPSA id 22ADE23DE3 for ; Mon, 14 Jul 2008 11:36:40 -0500 (CDT) Date: Mon, 14 Jul 2008 11:36:38 -0500 From: Paul Schmehl To: freebsd-usb@freebsd.org Message-ID: <3632806C83D31F1A23DE0F0A@utd65257.utdallas.edu> X-Mailer: Mulberry/4.0.6 (Linux/x86) X-Munged-Reply-To: Figure it out MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Crash when booting with umass device connected X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Paul Schmehl List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2008 17:05:13 -0000 I'd like to work with someone to provide useful information about this problem. Ever since upgrading my workstation to 7.0 STABLE, I cannot boot with my umass device connected. Once the system is up and running, I can mount the device with no problems. During the boot process, the device is detected, but then it causes a kernel panic. I'm logging the console to console.log, but there is no useful information there. I've enabled USB_DEBUG and rebuilt the kernel, but I have no idea how to capture the information printed to the console when this failure occurs. (I'm seriously considering taking a photograph of the screen since I can't do a screenshot and I can't find the information in any logs.) I'd post a bug, but without some trace information, it's kind of worthless. If I can get help from someone knowledgeable, I'll provide whatever information is needed to track this problem down. -- Paul Schmehl As if it wasn't already obvious, my opinions are my own and not those of my employer.