From owner-freebsd-current@FreeBSD.ORG  Sun Oct 26 10:53:35 2014
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id EAFB6F3B
 for <freebsd-current@freebsd.org>; Sun, 26 Oct 2014 10:53:35 +0000 (UTC)
Received: from smtprelay03.ispgateway.de (smtprelay03.ispgateway.de
 [80.67.31.30])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id A9CCD9FF
 for <freebsd-current@freebsd.org>; Sun, 26 Oct 2014 10:53:35 +0000 (UTC)
Received: from [87.79.253.40] (helo=fabiankeil.de)
 by smtprelay03.ispgateway.de with esmtpsa (SSLv3:AES128-SHA:128)
 (Exim 4.84) (envelope-from <freebsd-listen@fabiankeil.de>)
 id 1XiLRu-0000ko-OI
 for freebsd-current@freebsd.org; Sun, 26 Oct 2014 11:53:26 +0100
Date: Sun, 26 Oct 2014 12:53:30 +0100
From: Fabian Keil <freebsd-listen@fabiankeil.de>
Cc: FreeBSD Current <freebsd-current@freebsd.org>
Subject: Re: Panic after USB deadlock followed by kldunload umass.ko
Message-ID: <7af2d4d6.5c73ae4f@fabiankeil.de>
In-Reply-To: <5449119B.8090401@selasky.org>
References: <03fafb9a.529c7f26@fabiankeil.de>
	<5449119B.8090401@selasky.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 boundary="Sig_/jBCTiW+Ox5SQQx9H=bWpUVb"; protocol="application/pgp-signature"
X-Df-Sender: Nzc1MDY3
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Oct 2014 10:53:36 -0000

--Sig_/jBCTiW+Ox5SQQx9H=bWpUVb
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hans Petter Selasky <hps@selasky.org> wrote:

> On 10/23/14 16:28, Fabian Keil wrote:

> > kldunload umass.ko lead to a panic, dumping didn't work.
> >
> > Screenshots are available at:
> > http://www.fabiankeil.de/bilder/freebsd/kernel-panic-r273434-usb/
> >
> > I've seen locked-up usbconfig processes in the past,
> > usually after executing a shell function that does:
> >
> > | usbconfig_output=3D"$(sudo usbconfig -d ${device} add_quirk UQ_MSC_NO=
_INQUIRY)"
> > | [... error handling snipped ]
> > | usbconfig_output=3D"$(sudo usbconfig -d ${device} reset)"
> >
> > Sometimes the second command seems to mess up the USB system.

> USB detach is synchronous. If for example umass fails to detach, due to=20
> reference counts not reaching zero, that might be the root cause. Try to=
=20
> get a backtrace from the "usb_process()" processes using kgdb, and=20
> you'll see right away what is going on.

Thanks for the quick response. So far I haven't been able to intentionally
reproduce the issue, but I'll try the above the next time I unintentionally
run into this again.

Fabian

--Sig_/jBCTiW+Ox5SQQx9H=bWpUVb
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlRM4LoACgkQBYqIVf93VJ0/5ACePA2VOIuPTluXisMcoEffN1Ha
wYYAn1CPV4W8B9yBuhwPN6zcTfJJtPER
=eLqz
-----END PGP SIGNATURE-----

--Sig_/jBCTiW+Ox5SQQx9H=bWpUVb--