From owner-freebsd-usb@FreeBSD.ORG Mon Jun 11 16:57:51 2012 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 D20F7106564A; Mon, 11 Jun 2012 16:57:51 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe05.c2i.net [212.247.154.130]) by mx1.freebsd.org (Postfix) with ESMTP id 2949B8FC1B; Mon, 11 Jun 2012 16:57:50 +0000 (UTC) X-T2-Spam-Status: No, hits=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 Received: from [176.74.212.201] (account mc467741@c2i.net HELO laptop015.hselasky.homeunix.org) by mailfe05.swip.net (CommuniGate Pro SMTP 5.4.4) with ESMTPA id 281919100; Mon, 11 Jun 2012 18:57:43 +0200 From: Hans Petter Selasky To: freebsd@nagilum.org Date: Mon, 11 Jun 2012 18:57:12 +0200 User-Agent: KMail/1.13.7 (FreeBSD/9.0-STABLE; KDE/4.7.4; amd64; ; ) References: <201105280113.p4S1DWgM081572@red.freebsd.org> <201105281635.57055.hselasky@c2i.net> In-Reply-To: <201105281635.57055.hselasky@c2i.net> X-Face: 'mmZ:T{)),Oru^0c+/}w'`gU1$ubmG?lp!=R4Wy\ELYo2)@'UZ24N@d2+AyewRX}mAm; Yp |U[@, _z/([?1bCfM{_"B<.J>mICJCHAzzGHI{y7{%JVz%R~yJHIji`y>Y}k1C4TfysrsUI -%GU9V5]iUZF&nRn9mJ'?&>O MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201206111857.12147.hselasky@c2i.net> Cc: freebsd-gnats-submit@freebsd.org, freebsd-usb@freebsd.org Subject: usb/168743: panic: double fault caused by umass 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: Mon, 11 Jun 2012 16:57:51 -0000 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