From owner-freebsd-stable@FreeBSD.ORG Thu Oct 13 18:43:11 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8A12E1065670 for ; Thu, 13 Oct 2011 18:43:11 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe06.c2i.net [212.247.154.162]) by mx1.freebsd.org (Postfix) with ESMTP id 194958FC1C for ; Thu, 13 Oct 2011 18:43:10 +0000 (UTC) X-T2-Spam-Status: No, hits=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe06.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 190194644; Thu, 13 Oct 2011 20:33:06 +0200 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Thu, 13 Oct 2011 20:30:00 +0200 User-Agent: KMail/1.13.5 (FreeBSD/8.2-STABLE; KDE/4.4.5; amd64; ; ) References: <201110131806.p9DI6YpS057427@lurza.secnetix.de> In-Reply-To: <201110131806.p9DI6YpS057427@lurza.secnetix.de> X-Face: *nPdTl_}RuAI6^PVpA02T?$%Xa^>@hE0uyUIoiha$pC:9TVgl.Oq, NwSZ4V"|LR.+tj}g5 %V,x^qOs~mnU3]Gn; cQLv&.N>TrxmSFf+p6(30a/{)KUU!s}w\IhQBj}[g}bj0I3^glmC( :AuzV9:.hESm-x4h240C`9=w MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201110132030.00413.hselasky@c2i.net> Cc: freebsd-stable@freebsd.org, Oliver Fromme Subject: Re: panic: umass1: Unknown state 1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Oct 2011 18:43:11 -0000 On Thursday 13 October 2011 20:06:34 Oliver Fromme wrote: > I just got this panic on a recent stable/8 amd/64 system: > panic: umass1: Unknown state 1 > > Here's a screen shot from the KVM console: > > http://www.secnetix.de/olli/tmp/umass-panic.jpg > > Unfortunately, the crash dump that was written seems to be > lost. A quick search on the PRs doesn't reveal anything > either ... has anyone seen this type of panic before? > > It happened when I was switching virtual remote drives in > the management application of an IBM blade center, i.e. > the USB drive is actually a virtual drive emulated by the > blade management system. I did similar things a few times > before without a panic, so this isn't 100% reproducable. > Also, I'm reluctant to try again because this is a quite > important production server. > Hi, ehci_softintr() is not part of the USB stack in 8-stable and 9-stable. Must be 7-stable you are running. --HPS