linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: David Campbell <david@pastornet.net.au>
Cc: suspend-devel@lists.sourceforge.net, linux-input@vger.kernel.org,
	Dmitry Torokhov <dtor@insightbb.com>
Subject: Re: [Suspend-devel] No keyboard after suspend & resume - help with diagnosing
Date: Sat, 8 Dec 2007 01:00:42 +0100	[thread overview]
Message-ID: <200712080100.43204.rjw@sisk.pl> (raw)
In-Reply-To: <200711260036.33841.rjw@sisk.pl>

On Monday, 26 of November 2007, Rafael J. Wysocki wrote:
> On Sunday, 25 of November 2007, David Campbell wrote:
> > Hi,
> > 
> > I have a Clevo D870P notebook running fedora 8, kernel 2.6.23.1-49.fc8 
> > and I usually use an external keyboard (PS2 connection).
> > 
> > However I find that when I suspend the notebook and then resume out of 
> > suspend, neither keyboards work most times.  The same was true under 
> > fedora 7.
> > 
> > If I then proceed to unplug the external keyboard and plug it back in 
> > again, then both keyboards work and dmesg reports something like:
> >    input: AT Translated Set 2 keyboard as /class/input/input11
> > 
> > I can't see any other related messages logged.
> > 
> > How can I diagnose and solve such a problem?
> 
> This is a kernel problem, forwarding to the right people.

Well, there's no response, so please file a bug report at
http://bugzilla.kernel.org/enter_bug.cgi?product=Drivers
against "Input devices" (please add my address to the CC list).

Thanks,
Rafael

      reply	other threads:[~2007-12-07 23:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4749FA52.9070001@pastornet.net.au>
2007-11-25 23:36 ` [Suspend-devel] No keyboard after suspend & resume - help with diagnosing Rafael J. Wysocki
2007-12-08  0:00   ` Rafael J. Wysocki [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200712080100.43204.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=david@pastornet.net.au \
    --cc=dtor@insightbb.com \
    --cc=linux-input@vger.kernel.org \
    --cc=suspend-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).