From owner-freebsd-current@FreeBSD.ORG Sun Nov 16 18:51:48 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 9E497B60; Sun, 16 Nov 2014 18:51:48 +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 5ACB3A35; Sun, 16 Nov 2014 18:51:48 +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 sAGIpf2a036160 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 16 Nov 2014 10:51:41 -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 sAGIpfZX036159; Sun, 16 Nov 2014 10:51:41 -0800 (PST) (envelope-from sgk) Date: Sun, 16 Nov 2014 10:51:41 -0800 From: Steve Kargl To: Mark R V Murray Subject: Re: USB locks up system -- WAS Re: shutdown or acpi problem Message-ID: <20141116185141.GB36021@troutmask.apl.washington.edu> References: <546515BF.6030508@selasky.org> <20141113212206.GA20802@troutmask.apl.washington.edu> <20141116054141.GA33186@troutmask.apl.washington.edu> <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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4F3B4E02-0ADD-46EB-BB90-BF360E810585@FreeBSD.org> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: Hans Petter Selasky , Adrian Chadd , freebsd-current , Dag-Erling Sm?rgrav , Ian Lepore 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 18:51:48 -0000 On Sun, Nov 16, 2014 at 06:34:42PM +0000, Mark R V Murray wrote: > > > On 16 Nov 2014, at 18:31, Ian Lepore wrote: > > > > The point I'm trying to make here is that you trimmed away the important > > part of the prior messages and replied only to the part where Steve's > > debugging efforts were somewhat speculating. The non-speculative part > > was where he bisected the failure to an exact commit: > > > >>>> The problem is caused > >>>> by r273872. This is the recent random device patch. I have no > >>>> idea why removing a usb device would cause the system to lock > >>>> up other than random is probably trying to harvest some entropy. > > I?m sorry my commit caused the problem. > Nothing to be sorry about. This is -current afterall. > I?m also trying to find out why, but I don?t know enough about USB or > mass-storage devices to know why, so this may take me a while. In the > meanwhile, I?ll try to help by pointing out things I do know. Yes, I did the bisection to find that r273872 exposes the problem. What I don't know is if this is hardware specific to a Dell Latitude D530 laptop, USB specific, or some weird interaction between the random and USB. What I also find odd is that I seem to be the only person seeing this behavior when it is trivial for me to reproduce: boot laptop, plug in usb device, wait usb recognizes the device, then unplug the device. 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. -- Steve