From: Dmitry Torokhov <dtor_core@ameritech.net>
To: linux-kernel@vger.kernel.org
Cc: Sascha Wilde <wilde@sha-bang.de>,
"David N. Welton" <davidw@eidetix.com>,
James Lamanna <jamesl@appliedminds.com>
Subject: Re: 2.6 kernel won't reboot on AMD system - 8042 problem?
Date: Sun, 8 Aug 2004 10:05:14 -0500 [thread overview]
Message-ID: <200408081005.14832.dtor_core@ameritech.net> (raw)
In-Reply-To: <20040808121837.GA912@kenny.sha-bang.local>
On Sunday 08 August 2004 07:18 am, Sascha Wilde wrote:
> On Fri, Aug 06, 2004 at 10:22:57AM +0200, David N. Welton wrote:
> > [ Re-added Sascha to the CC, as he's interested in this too. ]
> >
> > James Lamanna wrote:
> >
> > >Change i8042.c:62 to
> > >#define DEBUG
> > >And see what printk's you get on trying to reboot.
> > >i8042_command has a bunch in it that are turned off by default.
>
> I just did some further testing, the problem here is exactly the same
> as Davids. And thinking about the exact point of failure and that
> Davids reboot problem is related to the keyboard being attached or not
> I realized what causes the problems for me:
>
> I have a keyboard attached to the PS/2 port, but my mouse is attached
> to USB. So I pluged in a PS/2 mouse, and guess what? The box
> rebooted!
>
> Well, this is by no means a solution, but I think it's pretty clear
> now, what exactly causes the trouble. Now we have to find out, why
> the i8042 code in 2.6.x breaks things on sertain hardware when there
> are not devices present in all ports, while in 2.4.x everything went
> well...
>
You could also try out the following scenario: remove your USB mouse and
_do not_ plug PS/2 one... What you might be seeing is another case of USB
Legacy emulation thingy getting in your way.
--
Dmitry
next prev parent reply other threads:[~2004-08-08 15:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4112A626.1000706@appliedminds.com>
2004-08-06 8:22 ` 2.6 kernel won't reboot on AMD system - 8042 problem? David N. Welton
2004-08-06 16:55 ` James Lamanna
2004-08-08 12:18 ` Sascha Wilde
2004-08-08 15:05 ` Dmitry Torokhov [this message]
2004-08-11 20:06 ` Sascha Wilde
2004-08-11 14:14 Dmitry Torokhov
2004-08-11 17:56 ` Sascha Wilde
2004-08-12 17:00 ` David N. Welton
2004-08-12 17:23 ` David N. Welton
2004-08-13 21:29 ` Sascha Wilde
2004-08-12 20:13 ` Vojtech Pavlik
2004-08-13 10:13 ` David N. Welton
2004-08-13 12:03 ` Vojtech Pavlik
2004-08-13 12:58 ` David N. Welton
[not found] <auto-000000462036@appliedminds.com>
2004-08-09 8:28 ` David N. Welton
2004-08-10 9:37 ` Sascha Wilde
2004-08-10 15:38 ` James Lamanna
-- strict thread matches above, loose matches on Subject: below --
2004-07-28 17:51 2.6 kernel won't reboot on AMD system (no, not the BIOS...) David N. Welton
2004-08-05 12:48 ` 2.6 kernel won't reboot on AMD system - 8042 problem? David N. Welton
2004-08-05 19:25 ` Sascha Wilde
2004-08-11 6:31 ` Dmitry Torokhov
2004-08-11 8:36 ` David N. Welton
2004-08-11 12:27 ` Vojtech Pavlik
2004-08-11 12:45 ` David N. Welton
2004-08-11 13:43 ` Sascha Wilde
2004-08-11 14:17 ` Vojtech Pavlik
2004-08-11 13:55 ` David Ford
2004-08-11 20:14 ` Sascha Wilde
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=200408081005.14832.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=davidw@eidetix.com \
--cc=jamesl@appliedminds.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wilde@sha-bang.de \
/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