From owner-freebsd-current@FreeBSD.ORG Thu Nov 13 21:22:08 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 C9F4BDA3 for ; Thu, 13 Nov 2014 21:22:08 +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 A6052866 for ; Thu, 13 Nov 2014 21:22:08 +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 sADLM73W020870 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 13 Nov 2014 13:22:07 -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 sADLM6cX020869; Thu, 13 Nov 2014 13:22:06 -0800 (PST) (envelope-from sgk) Date: Thu, 13 Nov 2014 13:22:06 -0800 From: Steve Kargl To: Hans Petter Selasky Subject: Re: USB locks up system -- WAS Re: shutdown or acpi problem Message-ID: <20141113212206.GA20802@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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <546515BF.6030508@selasky.org> 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: Thu, 13 Nov 2014 21:22:08 -0000 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. -- Steve