All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jason Munro" <jason@stdbev.com>
To: "Oleg Drokin" <green@linuxhacker.ru>
Cc: Fernando.Paredes@sun.com, linux-kernel@vger.kernel.org
Subject: Re: Toshiba keyboard lockups
Date: Thu, 10 Jun 2004 15:46:24 -0500	[thread overview]
Message-ID: <efc4b1ba19898906eb0aec7ac9c22fcd@stdbev.com> (raw)
In-Reply-To: <200406101915.i5AJFCBu197611@car.linuxhacker.ru>

On 2:15:12 pm 06/10/04 Oleg Drokin <green@linuxhacker.ru> wrote:
> Hello!
>
> Fernando Paredes <Fernando.Paredes@sun.com> wrote:
>
> FP> Applied these patches. Nothing while tail'ing /var/log/messages.
> Nothing FP> in the root console that I can see either.
> FP> Patched the source to 2.6.6. Still get the same lockups, totally
> random. FP> Any more ideas?
>
> Not sure if I have exact problem like you do, but at least I have
> something similar. Once in a while keyboard suddenly stopps working,
> touchpad still work though (I have Toshiba Satellite Pro (centrino
> based) laptop here). I figured out that if I leave the keyboard for
> some time (up to 2 minutes), it starts to work again, at least this
> was the case with XFree 4.4, during those no-keyboard times, mouse
> cursor was moving with small jumps (when keyboard works it moves
> smoothly). I upgraded to FC2 (and hence to xorg X server) today, and
> lockup happened once already, the "wait for some time" strategy did
> not work, so I remembered initially I thought this was something bad
> pressed on keyboard 

I have had similar issues with a toshiba laptop keyboard with 2.6+ kernels
for awhile. I have found that repeating the last key combination pressed
will "unlock" it. No logs or dmesg entries are produced when the lockup
occurs.

Its a Toshiba Satellite 1410-S173, currently running 2.6.7-rc2-mm2

\__ Jason Munro
 \__ jason@stdbev.com
  \__ http://hastymail.sourceforge.net/



  reply	other threads:[~2004-06-10 20:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-11 23:33 Toshiba keyboard lockups Fernando Paredes
2004-05-12  9:49 ` R. J. Wysocki
2004-06-09 21:58   ` Fernando Paredes
2004-06-10 19:15     ` Oleg Drokin
2004-06-10 20:46       ` Jason Munro [this message]
2004-06-10 22:05         ` Fernando Paredes
2004-07-06  8:48           ` Ralf Hildebrandt
2004-07-12  9:20             ` Ralf Hildebrandt
2004-06-15  7:51         ` Sean Legassick
2004-06-17 22:37           ` Gabriel Lavoie
2004-06-19 18:36             ` Vojtech Pavlik
2004-06-19 19:48               ` R. J. Wysocki

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=efc4b1ba19898906eb0aec7ac9c22fcd@stdbev.com \
    --to=jason@stdbev.com \
    --cc=Fernando.Paredes@sun.com \
    --cc=green@linuxhacker.ru \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.