From owner-freebsd-usb@FreeBSD.ORG Tue Dec 1 16:20:03 2009 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D5BB71065679 for ; Tue, 1 Dec 2009 16:20:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C2A968FC1A for ; Tue, 1 Dec 2009 16:20:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nB1GK3Jp096768 for ; Tue, 1 Dec 2009 16:20:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nB1GK3tr096767; Tue, 1 Dec 2009 16:20:03 GMT (envelope-from gnats) Date: Tue, 1 Dec 2009 16:20:03 GMT Message-Id: <200912011620.nB1GK3tr096767@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: Brandon Gooch Cc: Subject: Re: usb/140160: USB ports are no longer "active" after ACPI suspend/resume cycle. X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Brandon Gooch List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Dec 2009 16:20:03 -0000 The following reply was made to PR usb/140160; it has been noted by GNATS. From: Brandon Gooch To: bug-followup@FreeBSD.org, jamesbrandongooch@gmail.com Cc: Subject: Re: usb/140160: USB ports are no longer "active" after ACPI suspend/resume cycle. Date: Tue, 1 Dec 2009 15:56:22 +0000 I manage to keep the USB ports usable by building and loading all USB components as modules: /boot/loader.conf: usb_load="YES" ehci_load="YES" uhci_load="YES" umass_load="YES" ukbd_load="YES" ums_load="YES" uhid_load="YES" ucom_load="YES" umct_load="YES" uplcom_load="YES" ...and unloading uhci(4) in /etc/rc.suspend: kldunload uhci ...then reloading uhci(4) in /etc/rc.resume: kldload uhci Only uhci(4) should be unloaded/reloaded, as any other USB component being unloaded/reloaded seems to put a kink in things. As of a few hours testing, this is functional as a work-around.