From: Sascha Wilde <wilde@sha-bang.de>
To: "David N. Welton" <davidw@eidetix.com>
Cc: jamesl@appliedminds.com, linux-kernel@vger.kernel.org
Subject: Re: 2.6 kernel won't reboot on AMD system - 8042 problem?
Date: Tue, 10 Aug 2004 11:37:34 +0200 [thread overview]
Message-ID: <20040810093734.GA1089@kenny.sha-bang.local> (raw)
In-Reply-To: <411735BD.3000303@eidetix.com>
On Mon, Aug 09, 2004 at 10:28:45AM +0200, David N. Welton wrote:
> The shutdown sequence is not hanging, though, as far as I can tell.
Yes, I think I pointed out before, that not any code of the kernel,
but the hardware itself hangs during the reboot.
> You can triple fault the machine immediately after the first WCTR
> command during initialization (triple fault reboots it just fine
> just before the same command) and it doesn't cause a reboot, and yet
> it's no longer executing instructions from the kernel (or at least
> not printk's or anything meaningful). I don't think it's the
> parameters that it's passing to the WCTR command either, because if
> you look in the previous batch of printk's, it's putting back in
> exactly what it got out.
Right, in fact the problem occures from the first writing to the i8042
register. When you comment out all of the lines sending a
"I8042_CMD_CTL_WCTR" from i8042.c the resulting kernel will reboot
under al conditions (at least it does here) -- but unfortunatly that
renders the local Keyboard unusable...
Putting only one of them back in, (for example the one in
i8042_activate_port(), which brings the keyboard back to life) the
reboot hangs again.
Big question: how was the initialisation of the PS/2 ports managed in
2.4.x? Ther seems to be no similar code to i8042.c in it[0], and all I
have found till now is a bunch ob obscure jump-rables in
arch/i386/kernel/setup.c ...
cheers
sascha
[0] In fact, the only code mentioning the i8042 in 2.4 is related to
HP HIL devices...
--
Sascha Wilde : "Lies, was ich meine, nicht, was ich schreibe."
: (Urs Traenkner in de.alt.admin)
next prev parent reply other threads:[~2004-08-10 9:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <auto-000000462036@appliedminds.com>
2004-08-09 8:28 ` David N. Welton
2004-08-10 9:37 ` Sascha Wilde [this message]
2004-08-10 15:38 ` James Lamanna
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] <4112A626.1000706@appliedminds.com>
2004-08-06 8:22 ` David N. Welton
2004-08-06 16:55 ` James Lamanna
2004-08-08 12:18 ` Sascha Wilde
2004-08-08 15:05 ` Dmitry Torokhov
2004-08-11 20:06 ` Sascha Wilde
-- 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=20040810093734.GA1089@kenny.sha-bang.local \
--to=wilde@sha-bang.de \
--cc=davidw@eidetix.com \
--cc=jamesl@appliedminds.com \
--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
all inboxes | Powered by JetHome®