From owner-freebsd-acpi@FreeBSD.ORG Fri Jan 11 06:03:27 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 5B420120 for ; Fri, 11 Jan 2013 06:03:27 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) by mx1.freebsd.org (Postfix) with ESMTP id D5C27142 for ; Fri, 11 Jan 2013 06:03:26 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id r0B63Itw098644; Fri, 11 Jan 2013 17:03:18 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Fri, 11 Jan 2013 17:03:17 +1100 (EST) From: Ian Smith To: Jason Selwitz Subject: Re: No keyboard after Suspend/Resume In-Reply-To: <50EF1928.5000005@verizon.net> Message-ID: <20130111163803.G62930@sola.nimnet.asn.au> References: <50EEECD8.30201@verizon.net> <50EF1928.5000005@verizon.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-acpi@freebsd.org 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 06:03:27 -0000 On Thu, 10 Jan 2013 14:40:24 -0500, Jason Selwitz wrote: > Hello I thought I would write and see if anyone had any suggestions on > this problem.. for the most part an S3 suspend works the way it should > with one problem.. the system will not resume keyboard input, either via > USB or PS/2 the keyboard gets power again and it responds to minor > things like numlock and cabs lock but the system does not register any > text input. I'm running Freebsd 9.1 release. I have included a dmesg and > can supply an acpidump in needed, if someone has any other suggestions I > would be happy to try anything thanks! I don't know if any of the ACPI error messages in your basic dmesg are relevant to this issue, or not. It could be helpful to see the tail of dmesg, after booting with verbose logging, from before to after a suspend / resume cycle. Among those messages will be RESET_KBD (and TEST_AUX_PORT and RESET_AUX, perhaps). These messages also appear after resume in /var/log/debug.log if verbose logging is enabled, and of course also in /var/log/messages. A verbose dmesg would also show initial keyboard initialisation, perhaps a clue there? Given you have two hdac devices, you'll almost certainly need to increase kern.msgbufsize from 64K to maybe twice that to get a full verbose dmesg, as kbd initialisation occurs very early. cheers, Ian