Date: Sat, 12 Jan 2013 02:18:51 +1100 (EST) From: Ian Smith <smithi@nimnet.asn.au> To: Jason Selwitz <jselwitz@verizon.net> Cc: freebsd-acpi@freebsd.org Subject: Re: No keyboard after Suspend/Resume Message-ID: <20130112020013.N62930@sola.nimnet.asn.au> In-Reply-To: <50F01DB8.404@verizon.net> References: <50EEECD8.30201@verizon.net> <50EF1928.5000005@verizon.net> <20130111163803.G62930@sola.nimnet.asn.au> <50F01DB8.404@verizon.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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?20130112020013.N62930>