From owner-freebsd-current@FreeBSD.ORG Thu Oct 23 14:28:09 2014 Return-Path: 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 1A609E19 for ; Thu, 23 Oct 2014 14:28:09 +0000 (UTC) Received: from smtprelay04.ispgateway.de (smtprelay04.ispgateway.de [80.67.31.32]) (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 CF44FD83 for ; Thu, 23 Oct 2014 14:28:08 +0000 (UTC) Received: from [78.35.190.95] (helo=fabiankeil.de) by smtprelay04.ispgateway.de with esmtpsa (SSLv3:AES128-SHA:128) (Exim 4.84) (envelope-from ) id 1XhJMt-0004FL-Ie for freebsd-current@freebsd.org; Thu, 23 Oct 2014 16:27:59 +0200 Date: Thu, 23 Oct 2014 16:28:02 +0200 From: Fabian Keil To: FreeBSD Current Subject: Panic after USB deadlock followed by kldunload umass.ko Message-ID: <03fafb9a.529c7f26@fabiankeil.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/s5nvohQ8Nk7qDj5.PtNTFjz"; 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Oct 2014 14:28:09 -0000 --Sig_/s5nvohQ8Nk7qDj5.PtNTFjz Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable A few days ago a couple of usbconfig processed did not exit: fk@r500 ~ $sudo procstat -kk $(pgrep usbconfig) PID TID COMM TDNAME KSTACK = =20 1624 100781 usbconfig - mi_switch+0xe1 sleepq_wait+0= x3a _sx_xlock_hard+0x522 _sx_xlock+0x5d usbd_enum_lock+0x3a usb_ref_device+= 0x157 usb_open+0xbf devfs_open+0x122 VOP_OPEN_APV+0xa1 vn_open_vnode+0x234 = vn_open_cred+0x351 kern_openat+0x26f amd64_syscall+0x3fb Xfast_syscall+0xfb= =20 1617 100779 usbconfig - mi_switch+0xe1 sleepq_wait+0= x3a _sx_xlock_hard+0x522 _sx_xlock+0x5d usbd_enum_lock+0x3a usb_ref_device+= 0x157 usb_open+0xbf devfs_open+0x122 VOP_OPEN_APV+0xa1 vn_open_vnode+0x234 = vn_open_cred+0x351 kern_openat+0x26f amd64_syscall+0x3fb Xfast_syscall+0xfb= =20 1615 100777 usbconfig - mi_switch+0xe1 sleepq_wait+0= x3a _sx_xlock_hard+0x522 _sx_xlock+0x5d usbd_enum_lock+0x3a usb_ref_device+= 0x157 usb_open+0xbf devfs_open+0x122 VOP_OPEN_APV+0xa1 vn_open_vnode+0x234 = vn_open_cred+0x351 kern_openat+0x26f amd64_syscall+0x3fb Xfast_syscall+0xfb= =20 1601 100774 usbconfig - mi_switch+0xe1 sleepq_timedw= ait+0x3a _sleep+0x294 pause_sbt+0xd0 usb_pause_mtx+0x85 usb_ioctl+0x3e7 dev= fs_ioctl_f+0x13b kern_ioctl+0x3cd sys_ioctl+0x13c amd64_syscall+0x3fb Xfast= _syscall+0xfb=20 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_INQ= UIRY)" | [... error handling snipped ] | usbconfig_output=3D"$(sudo usbconfig -d ${device} reset)" Sometimes the second command seems to mess up the USB system. Fabian --Sig_/s5nvohQ8Nk7qDj5.PtNTFjz Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlRJEHIACgkQBYqIVf93VJ3FHACfWPshJ/KvdhOR8mHBRERYzH7N ZUAAoITGDWnTy9aPsJWFke4XNZKxHvU8 =0pE3 -----END PGP SIGNATURE----- --Sig_/s5nvohQ8Nk7qDj5.PtNTFjz--