From owner-freebsd-acpi@FreeBSD.ORG Fri Jan 11 17:29:34 2013 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 8F569D43 for ; Fri, 11 Jan 2013 17:29:34 +0000 (UTC) (envelope-from sendtomatt@gmail.com) Received: from mail-pb0-f52.google.com (mail-pb0-f52.google.com [209.85.160.52]) by mx1.freebsd.org (Postfix) with ESMTP id 6BB00826 for ; Fri, 11 Jan 2013 17:29:34 +0000 (UTC) Received: by mail-pb0-f52.google.com with SMTP id ro2so1062986pbb.11 for ; Fri, 11 Jan 2013 09:29:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=kPfbmUHSuw4Y+ThOY1aungZTkOKUIVgjtKBQfH5QMYY=; b=Dun+aJv8e8cga90PhyqDzSwiWezI9dl2pD9+XfeEkpeFKgLvqUGUMIK1Zqr1RuQ3G0 ++8o3PF0POyu/0GH/sfHk7CsSME6IGt4OBxf2UQTttwSYiBdYm94RMDCXS4+K2aLlu7/ 56Gai22KYAZVdxELYsDblkPetZX1R1XjcPp/WOd+GPlQkKeijJk9XqqjxIfwTo96kM7k RZK5ppW3m5bctj81B2ROWC19SQxe0VORQ1oW0rDAEM/4XOzSPCaQDPAdOkG+6SdY8E5T 6yyqYKyJhDIw9lkIS+yBaebsz2xMMZsQSyAKfPL3COk0byn5ohsMXIdXXFwIWy/gdXMG NRAg== X-Received: by 10.66.82.73 with SMTP id g9mr209434286pay.5.1357925000579; Fri, 11 Jan 2013 09:23:20 -0800 (PST) Received: from bakeneko.local (108-213-216-134.lightspeed.sntcca.sbcglobal.net. [108.213.216.134]) by mx.google.com with ESMTPS id uk9sm3098553pbc.63.2013.01.11.09.23.18 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 11 Jan 2013 09:23:19 -0800 (PST) Message-ID: <50F04A5D.1060201@gmail.com> Date: Fri, 11 Jan 2013 09:22:37 -0800 From: matt User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121203 Thunderbird/10.0.11 MIME-Version: 1.0 To: Jason Selwitz Subject: Re: No keyboard after Suspend/Resume References: <50EEECD8.30201@verizon.net> <50EF1928.5000005@verizon.net> <20130111163803.G62930@sola.nimnet.asn.au> <50F01DB8.404@verizon.net> <20130112020013.N62930@sola.nimnet.asn.au> <50F03C59.3010605@verizon.net> In-Reply-To: <50F03C59.3010605@verizon.net> X-Enigmail-Version: 1.3.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org, Ian Smith X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jan 2013 17:29:34 -0000 On 01/11/13 08:22, Jason Selwitz wrote: > Thought I would shoot off a quick detail of my setup, maybe this will > help shed more light on the issue.. > > firstly this system is a Laptop, in a docking station, the keyboard is > connected to the docking station via both the PS/2 port and a USB > connection, it can also be set up to use 2 USB connections (perhaps the > PS/2 connection is not coming back fully after a suspend/resume cycle). > however after a little more testing after a resume, even the laptops > built in keyboard does not respond though I am able to pull the ps2 > connection remove the adapter and connect it to a USB port and have the > keyboard work again, though if the keyboard is in a USB port during the > suspend/resume I see the system reattaching the keyboard but it does not > allow text input until it is physically unplugged then reconnected. I'll > keep trying a few things and send any interesting debug info that I come > across.. thanks again to all.. > > Jason > > > > > Just some generic hardware wrangling ideas :) Just want to check if this is in the console, X, or both...Just saw a post about "unplugging and replugging" keyboard issues with X/hal (I've had some configs that had similar issues with mice as a pebkac with hal setup). If you've only tried in X switching to a VT and trying in the console (or not starting X) and testing again may be worthwhile to rule out high level problems. You could also try putting something in rc.resume using usbconfig to reset the bus? I'm not sure if there's a way to just send reset, but you could send power_off and then power_on to the specific device/bus combo for the keyboard. Try setting hw.pci.do_power_resume=1 and hw.pci.do_power_suspend=0 in case it's a PCI D state issue. Other combos might be worthwhile, some will likely break resume or suspend however. Might as well set hw.usb.ukbd.debug=1 and check the dmesg on resume as well. Matt