From: Ian Stirling <root@mauve.demon.co.uk>
To: nikberry@med.umich.edu (Nicholas Berry)
Cc: root@mauve.demon.co.uk, linux-kernel@vger.kernel.org
Subject: Re: Odd keyboard related crashes.
Date: Fri, 5 Oct 2001 22:24:11 +0100 (BST) [thread overview]
Message-ID: <200110052124.WAA20832@mauve.demon.co.uk> (raw)
In-Reply-To: <sbbd8e9c.095@mail-02.med.umich.edu> from "Nicholas Berry" at Oct 05, 2001 10:42:16 AM
> >>> Ian Stirling <root@mauve.demon.co.uk> 10/05/01 05:01AM >>>
> >I'm running 2.4.10, and the ps/2 keyboard came out of it's socket.
>
> >On plugging back in, all worked fine, until 10 seconds later there was a
> >crash. (the keyboard worked after being plugged in)
> >No oops, just a reboot.
<snip>
> When the keyboard is powered up (or plugged in), it goes through a self =
> test, and reports the status back to the PC. Normally, a start up dialogue =
> takes place between the PC and the keyboard at this point.
> That's fine when you boot your PC, but if you unplug then re-plug the =
> keyboard, the PC will be sent data it's really not expecting, and the BIOS =
> will be very confused.
I should have said.
Both times this happened, the keyboard was working fine after being
plugged in, correctly recognising 30 or so keypresses before the crash.
It happened ~10 seconds after the keyboard was plugged in, with the
system and keyboard remaining functional, with no keyboard related messages
sysloged (remote syslog, so I'm sure), which is why I suspect it may
not be hardware.
next parent reply other threads:[~2001-10-05 21:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <sbbd8e9c.095@mail-02.med.umich.edu>
2001-10-05 21:24 ` Ian Stirling [this message]
2001-10-09 10:51 Nicholas Berry
2001-10-09 16:28 ` James Simmons
2001-10-09 16:02 ` Daniel Egger
-- strict thread matches above, loose matches on Subject: below --
2001-10-05 14:42 Nicholas Berry
2001-10-07 7:23 ` Pavel Machek
2001-10-08 15:18 ` Eric W. Biederman
2001-10-08 16:21 ` Ian Stirling
2001-10-05 9:17 Thomas Foerster
2001-10-05 9:01 Ian Stirling
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=200110052124.WAA20832@mauve.demon.co.uk \
--to=root@mauve.demon.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=nikberry@med.umich.edu \
/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
all inboxes | Powered by JetHome®