From: ebiederman@uswest.net (Eric W. Biederman)
To: Pavel Machek <pavel@suse.cz>
Cc: Nicholas Berry <nikberry@med.umich.edu>,
root@mauve.demon.co.uk, linux-kernel@vger.kernel.org
Subject: Re: Odd keyboard related crashes.
Date: 08 Oct 2001 09:18:02 -0600 [thread overview]
Message-ID: <m1eloew47p.fsf@frodo.biederman.org> (raw)
In-Reply-To: <sbbd8e9c.096@mail-02.med.umich.edu> <20011007092352.A454@bug.ucw.cz>
In-Reply-To: <20011007092352.A454@bug.ucw.cz>
Pavel Machek <pavel@suse.cz> writes:
> Hi!
>
> > >>> 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.
> > >Thinking this must just have been a wierd coincidence, after the system
> > >came back up, I tried it again, and again it crashed a few seconds
> afterwards.
>
> >
> > >It doesn't seem to want to do this again though.
> >
> > 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.
>
> > If you ever want to switch a keyboard between PCs, make sure you leave power
> supplied to it at all times.
>
>
> BIOS is not alive enough at the time linux boots. This can't be BIOS
> issue.
Unless the BIOS has some weird power management issues, then it may be almost
impossible to kill. I had one machine once where the BIOS misreported
it's memory usage, and there wasn't an option to disable power
management. Then the BIOS and the kernel were both using the top of
memory and weird things happened.
That being said I have seen at least one machine where there was a
crash with hot plugging the keyboard and at the time I figured it was
simply bad hardware that couldn't handle it for some reason.
And unless a BIOS is doing something really strange it shouldn't
touch the keyboard after linux is going.
Eric
next prev parent reply other threads:[~2001-10-08 15:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-05 14:42 Odd keyboard related crashes Nicholas Berry
2001-10-07 7:23 ` Pavel Machek
2001-10-08 15:18 ` Eric W. Biederman [this message]
2001-10-08 16:21 ` Ian Stirling
-- strict thread matches above, loose matches on Subject: below --
2001-10-09 10:51 Nicholas Berry
2001-10-09 16:28 ` James Simmons
2001-10-09 16:02 ` Daniel Egger
[not found] <sbbd8e9c.095@mail-02.med.umich.edu>
2001-10-05 21:24 ` 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=m1eloew47p.fsf@frodo.biederman.org \
--to=ebiederman@uswest.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nikberry@med.umich.edu \
--cc=pavel@suse.cz \
--cc=root@mauve.demon.co.uk \
/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