public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Norman Diamond <ndiamond@wta.att.ne.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test2: lost mouse  synchronization after apm-suspend
Date: Mon, 11 Aug 2003 13:50:48 -0700	[thread overview]
Message-ID: <20030811205048.GA18476@kroah.com> (raw)
In-Reply-To: <3bba01c35e5f$ba01f3a0$97ee4ca5@DIAMONDLX60>

On Sat, Aug 09, 2003 at 07:13:17PM +0900, Norman Diamond wrote:
> "Greg KH" <greg@kroah.com> wrote to someone else:
> 
> > Unload all usb drivers before suspending please.
> 
> I hope this isn't a general rule?  I can't keep up with the list, but I saw
> this message, and it looks like a disaster.

Right now, yes that is the response if anyone has any problems with
this, sorry.

> There are a lot of small-size desktop machines that depend on USB keyboards
> because they don't have PS/2 ports.  In some cases the keyboard includes a
> PS/2 hub for a PS/2 mouse, but in some cases the keyboard doesn't even have
> that so the mouse is also USB.  In all of these cases the connection to the
> CPU goes through a USB port.
> 
> How should the user restore their keyboard after resuming from suspend?  A
> modprobe or insmod command?  In the vast majority of these cases the input
> of a command would depend on having the USB keyboard already working.

Have the resume script re-load the drivers.  A lot of people are already
doing this.

thanks,

greg k-h

  reply	other threads:[~2003-08-11 20:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-09 10:13 2.6.0-test2: lost mouse synchronization after apm-suspend Norman Diamond
2003-08-11 20:50 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-08-07 14:33 frahm
2003-08-07 16:23 ` Greg KH

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=20030811205048.GA18476@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ndiamond@wta.att.ne.jp \
    /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