From owner-freebsd-usb@FreeBSD.ORG Mon Jun 11 18:00:27 2012 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 306F31065670 for ; Mon, 11 Jun 2012 18:00:27 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1CB888FC08 for ; Mon, 11 Jun 2012 18:00:27 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q5BI0QeA048397 for ; Mon, 11 Jun 2012 18:00:26 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q5BI0Qtq048396; Mon, 11 Jun 2012 18:00:26 GMT (envelope-from gnats) Date: Mon, 11 Jun 2012 18:00:26 GMT Message-Id: <201206111800.q5BI0Qtq048396@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: FreeBSD@nagilum.org Cc: Subject: Re: usb/168743: panic: double fault caused by umass X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: FreeBSD@nagilum.org List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 18:00:27 -0000 The following reply was made to PR usb/168743; it has been noted by GNATS. From: FreeBSD@nagilum.org To: Hans Petter Selasky Cc: freebsd-usb@freebsd.org, freebsd-gnats-submit@freebsd.org Subject: Re: usb/168743: panic: double fault caused by umass Date: Mon, 11 Jun 2012 19:53:51 +0200 I'm compiling a new kernel with those options as I type. Yes, this is very much reproduceable. If you look at the dmesg you will also see the previous reboot for the same reason but with a different device - a WLAN stick that also includes some mass storage for the windows driver and probably another for the mini-sd or whatever card fits in there.. The Pendrive I then used is a 64MB (yes, megabytes) so from that you can probably guess how ancient that thing is so it should not have any new and fancy options aka quirks ;). What I haven't tried yet is simply loading the module while no device is attached. I'll try that when I have the new kernel booted. It will take some time though since this is a 500MHz Geode.. I think I also saw a few other bugreports related to this issue maybe someone else already included a backtrace. Thanks for looking into this, Alex. Zitat von Hans Petter Selasky : > Hi, > > This sounds like a missing MODULE_DEPEND() issue or your pendrive is > returning > an error code to some of the SCSI commands which is not handled properly. > > > Could you add these options to the kernel config file: > > options KDB # Kernel debugger related code > options KDB_TRACE # Print a stack trace for a panic > > Then get full backtrace. > > Is this issue reproducable. I cannot reproduce over here using a 9-stable > GENERIC kernel without "device umass". > > --HPS