From owner-freebsd-current@FreeBSD.ORG Sun Nov 16 05:41:44 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 61AD2F5F; Sun, 16 Nov 2014 05:41:44 +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 23B74B2B; Sun, 16 Nov 2014 05:41:44 +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 sAG5fggH033198 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 15 Nov 2014 21:41:42 -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 sAG5ff60033197; Sat, 15 Nov 2014 21:41:41 -0800 (PST) (envelope-from sgk) Date: Sat, 15 Nov 2014 21:41:41 -0800 From: Steve Kargl To: Hans Petter Selasky Subject: Re: USB locks up system -- WAS Re: shutdown or acpi problem Message-ID: <20141116054141.GA33186@troutmask.apl.washington.edu> References: <20141112224212.GA14013@troutmask.apl.washington.edu> <20141113172533.GA18690@troutmask.apl.washington.edu> <20141113180332.GA18990@troutmask.apl.washington.edu> <20141113181515.GA19117@troutmask.apl.washington.edu> <546515BF.6030508@selasky.org> <20141113212206.GA20802@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20141113212206.GA20802@troutmask.apl.washington.edu> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-current@freebsd.org 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 05:41:44 -0000 On Thu, Nov 13, 2014 at 01:22:06PM -0800, Steve Kargl wrote: > On Thu, Nov 13, 2014 at 09:34:07PM +0100, Hans Petter Selasky wrote: > > On 11/13/14 19:15, Steve Kargl wrote: > > > On Thu, Nov 13, 2014 at 10:03:32AM -0800, Steve Kargl wrote: > > >> On Thu, Nov 13, 2014 at 09:25:33AM -0800, Steve Kargl wrote: > > >>> On Wed, Nov 12, 2014 at 02:42:13PM -0800, Steve Kargl wrote: > > >>>> I have a kernel/world from r274273 sources, which is exhibiting a new > > >>>> issue on my old laptop. Neither 'shutdown -p now' nor 'shutdown -r now' > > >>>> work. I get to the end of shutdown and see for example > > >>>> > > >>>> All buffers synced > > >>>> Uptime: 4h23m15s > > >>>> > > >>>> and then the laptop just sits there. It does not power off with > > >>>> the -p option nor does it reboot with the -r. Has anyone else > > >>>> seen this behavior? > > >>>> > > >>> > > >>> The problem appears to be related to a recent change in the > > >>> USB stack. If I have the following drive plugged into a > > >>> usb port, the above behavior is observed on shutdown. > > >>> > > > > > > Adding > > > > > > hw.usb.no_shutdown_wait: 1 > > > > > > to /boot/loader.conf appears to work around the 'shutdown -p now' > > > and 'shutdown -r now' issue. Unfortunately, the bricking of the > > > laptop is not affected by this sysctl. Once a device is plugged > > > into a usb, it must remain plugged in. > > > > > > > Hi, > > > > Is using this sysctl/tunable a suitable solution for you? > > > > The sysctl is a suitable solution for the shutdown issues. > It is not suitable solution for the general use of using > a memory stick to for example quickly transfer files. Once > the memory stick is plugged into the usb port, it must > remain there unless one wants to reboot the system. > > I rebuilt the kernel with USB_DEBUG and CAMDEBUG enabled. > I need to wade through a rather large /var/log/messages > to see if anything appears unusual. > Well, this has been a waste of a day. 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. -- Steve