From: "R. J. Wysocki" <rjwysocki@sisk.pl>
To: Grzegorz Kulewski <kangur@polcom.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.5: keyboard lockup on a Toshiba laptop
Date: Wed, 7 Apr 2004 13:21:01 +0200 [thread overview]
Message-ID: <200404071321.01520.rjwysocki@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.58.0404071227430.10871@alpha.polcom.net>
On Wednesday 07 of April 2004 12:33, Grzegorz Kulewski wrote:
> On Wed, 7 Apr 2004, R. J. Wysocki wrote:
> > Hi,
> >
> > FYI, I've just had a keyboard lockup on a Toshiba laptop (Satellite
> > 1400-103) with the 2.6.5 kernel.
> >
> > It occured when I was typing some text in kmail. Everything worked just
> > fine except for the keyboard that was locked (dead - even capslock did
> > not work). Fortunately the (USB) mouse worked, so I could reboot the
> > machine "gently" to get my keyboard back in order.
> >
> > I use RH9 with some modifications to support the 2.6.x kernels. Attached
> > is the .config.
>
> Hi,
>
> Was anything in your logs about that?
No sign of anything related to the keyboard.
> I think that maybe you should disable PREEMPTION.
Well, maybe, but I was using all of the previous 2.6.x _with_ the preepmtion
enabled and nothing like this happened before.
> Or use different distribution than RH9. They often modify gcc and other
> programs, maybe even X - maybe try to compile your kernel on "vanilla" gcc
> 3.3.3. I can give you a shell on computer with Gentoo and working gcc. Or
> change distribution: Gentoo works ok for me and my friends! :-)
Look, I've been using different variants of the 2.6.x kernels on this very
machine/distro since early 2.6.0-test and I hadn't seen _anything_ like this
before 2.6.5-rc2 (then I saw something like this first). I _really_ don't
think it's a distribution-related issue.
--
Rafael J. Wysocki,
SiSK
[tel. (+48) 605 053 693]
----------------------------
For a successful technology, reality must take precedence over public
relations, for nature cannot be fooled.
-- Richard P. Feynman
next prev parent reply other threads:[~2004-04-07 11:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 10:22 R. J. Wysocki
2004-04-07 10:33 ` Grzegorz Kulewski
2004-04-07 10:39 ` Ralf Hildebrandt
2004-04-07 10:51 ` Grzegorz Kulewski
2004-04-07 10:56 ` Ralf Hildebrandt
[not found] ` <20040407105522.GN20293@charite.de>
2004-04-07 11:03 ` Grzegorz Kulewski
2004-04-07 11:06 ` Ralf Hildebrandt
2004-04-07 11:31 ` Grzegorz Kulewski
2004-04-09 14:12 ` R. J. Wysocki
2004-04-09 16:30 ` Grzegorz Kulewski
2004-04-07 11:21 ` R. J. Wysocki [this message]
2004-04-07 11:30 ` Vojtech Pavlik
2004-04-15 18:54 ` Ralf Hildebrandt
2004-04-15 19:47 ` Vojtech Pavlik
2004-04-07 10:47 ` Meelis Roos
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=200404071321.01520.rjwysocki@sisk.pl \
--to=rjwysocki@sisk.pl \
--cc=kangur@polcom.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome