Date: Fri, 11 Jan 2013 11:22:49 -0500 From: Jason Selwitz <jselwitz@verizon.net> To: Ian Smith <smithi@nimnet.asn.au> Cc: freebsd-acpi@freebsd.org Subject: Re: No keyboard after Suspend/Resume Message-ID: <50F03C59.3010605@verizon.net> In-Reply-To: <20130112020013.N62930@sola.nimnet.asn.au> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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 On 01/11/2013 10:18, Ian Smith wrote: > On Fri, 11 Jan 2013 09:12:08 -0500, Jason Selwitz wrote: > > Hello Ian, > > > > Thanks for taking a look at this, I have included a verbose dmesg for > > you in this e-mail, if you have a ny additional suggestions I'd love to > > hear them thank again, take care.. > > > > Jason > > Hi Jason. Please cc or reply-all to include the list. I'm only good > for, if anything, soliciting more detail. Your verbose dmesg should be > helpful for those who know, it looks clean and complete to me is about > the best I can offer. The list may handle a 75K attachment if need be, > but could you post it somewhere and provide an URL? > > In addition - cut and paste will do - I still think that: > > > > 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 > > The RESET_KBD messages from debug.log you later posted me: > > Jan 11 09:31:04 idoru kernel: kbdc: RESET_KBD return code:00fa > Jan 11 09:31:04 idoru kernel: kbdc: RESET_KBD status:00aa > > match mine, but I see you're using ukbd0 so there's USB too. Someone > may suggest other debugging options/levels but I'm staying in my depth. > > cheers, Ian > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50F03C59.3010605>