From owner-freebsd-current@FreeBSD.ORG Sun Nov 16 19:30:00 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 AD43FF0C; Sun, 16 Nov 2014 19:30:00 +0000 (UTC) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask.apl.washington.edu", Issuer "troutmask.apl.washington.edu" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6B3DAD63; Sun, 16 Nov 2014 19:30:00 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.9/8.14.9) with ESMTP id sAGJTxBq036379 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 16 Nov 2014 11:29:59 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.9/8.14.9/Submit) id sAGJTxJS036378; Sun, 16 Nov 2014 11:29:59 -0800 (PST) (envelope-from sgk) Date: Sun, 16 Nov 2014 11:29:59 -0800 From: Steve Kargl To: Hans Petter Selasky Subject: Re: USB locks up system -- WAS Re: shutdown or acpi problem Message-ID: <20141116192959.GB36339@troutmask.apl.washington.edu> References: <20141116175102.GA35649@troutmask.apl.washington.edu> <1416162070.4781.186.camel@revolution.hippie.lan> <1416162718.4781.192.camel@revolution.hippie.lan> <4F3B4E02-0ADD-46EB-BB90-BF360E810585@FreeBSD.org> <20141116185141.GB36021@troutmask.apl.washington.edu> <4443FEFB-17F1-4516-959F-4C70AB2A4382@FreeBSD.org> <20141116190344.GC36021@troutmask.apl.washington.edu> <5468F814.6010702@selasky.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5468F814.6010702@selasky.org> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: Adrian Chadd , freebsd-current , Ian Lepore , Dag-Erling Sm?rgrav 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: Sun, 16 Nov 2014 19:30:00 -0000 On Sun, Nov 16, 2014 at 08:16:36PM +0100, Hans Petter Selasky wrote: > On 11/16/14 20:03, Steve Kargl wrote: > > On Sun, Nov 16, 2014 at 06:55:53PM +0000, Mark R V Murray wrote: > >> > >>> On 16 Nov 2014, at 18:51, Steve Kargl wrote: > >>> > >>> If you have not read the entire thread, once the laptop keyboard and > >>> video output lock up, I can ssh into the laptop. If I run usbconfig, > >>> it hangs, ^T tells me it is stuck in SX Lock, and the /dev/da0* devices > >>> have not been destroyed. > >> > >> Weirder and weirder :-(. > >> > >> Something with SX locks? Hmm. I do use those for attach and detach for > >> RNG sources. Could it be that that stick of yours is somehow getting > >> involved in the RNG source locks? > >> > > > > It's not limited to a single usb device. Plugging in/Unplugging > > a logitech mouse dongle, the memstick, a Western Digital MY Passport > > external usb hard drive, all lead to the locked keyboard and video. > > > > I tried adding both RANDOM_DEBUG and USBDEBUG to the kernel, but the > > mount of output is mind numbing. > > > > > Can you enter kgdb when the usbconfig is froozen, and backtrace all > kernel threads. You should see exactly what locks are the problem. > > Maybe some lock didn't get properly unlocked! > I haven't tried kgdb. I did try to attach gdb to the usbconfig process via its pid, but gdb dumped core. I haven't looked at locks in kgdb, what command or commands should I try. -- Steve