From: Dmitry Torokhov <dtor_core@ameritech.net>
To: linux-kernel@vger.kernel.org
Cc: Roey Katz <roey@sdf.lonestar.org>
Subject: Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup
Date: Mon, 3 Jan 2005 01:23:58 -0500 [thread overview]
Message-ID: <200501030123.58884.dtor_core@ameritech.net> (raw)
In-Reply-To: <Pine.NEB.4.61.0501030536110.14662@sdf.lonestar.org>
On Monday 03 January 2005 12:37 am, Roey Katz wrote:
> Dmitry,
>
> I have the contents of 'kern.log' at:
>
> http://roey.freeshell.org/mystuff/kernel/kern.log-2.6.10
>
The following looks very suspicious:
Jan 2 23:05:17 tits kernel: drivers/input/serio/i8042.c: f2 -> i8042 (kbd-data) [4842]
Jan 2 23:05:17 tits kernel: drivers/input/serio/i8042.c: fa <- i8042 (interrupt, kbd, 1, timeout) [4866]
Jan 2 23:05:17 tits kernel: drivers/input/serio/i8042.c: ab <- i8042 (interrupt, kbd, 1, timeout) [4874]
Jan 2 23:05:17 tits kernel: drivers/input/serio/i8042.c: 41 <- i8042 (interrupt, kbd, 1, timeout) [4882]
Jan 2 23:05:17 tits kernel: drivers/input/serio/i8042.c: ed -> i8042 (kbd-data) [4882]
Jan 2 23:05:17 tits kernel: drivers/input/serio/i8042.c: fa <- i8042 (interrupt, kbd, 1) [4894]
Jan 2 23:05:17 tits kernel: drivers/input/serio/i8042.c: 00 -> i8042 (kbd-data) [4894]
Jan 2 23:05:17 tits kernel: drivers/input/serio/i8042.c: fa <- i8042 (interrupt, kbd, 1) [4906]
atkbd driver tries to get ID from the attached device but although the
controller responds with valid keyboard ID it also for some reason indicates
that the connected device times out. Wierd...
Could you try booting with "acpi=off"?
--
Dmitry
next prev parent reply other threads:[~2005-01-03 6:24 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-01 8:27 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup Roey Katz
2005-01-01 21:31 ` Dmitry Torokhov
2005-01-02 6:28 ` Roey Katz
2005-01-02 6:52 ` Dmitry Torokhov
2005-01-02 6:59 ` Roey Katz
2005-01-03 2:53 ` Roey Katz
2005-01-03 3:06 ` Dmitry Torokhov
2005-01-03 5:37 ` Roey Katz
2005-01-03 6:23 ` Dmitry Torokhov [this message]
2005-01-03 13:21 ` Roey Katz
2005-01-03 16:35 ` Dmitry Torokhov
2005-01-03 16:54 ` Roey Katz
2005-01-04 5:49 ` Roey Katz
2005-01-04 6:17 ` Dmitry Torokhov
2005-01-04 6:26 ` Roey Katz
2005-01-06 4:16 ` Dmitry Torokhov
2005-01-06 4:29 ` Roey Katz
2005-01-07 4:06 ` Roey Katz
2005-01-07 5:45 ` Dmitry Torokhov
2005-01-07 13:37 ` Roey Katz
2005-01-07 15:20 ` Dmitry Torokhov
2005-01-09 5:14 ` Roey Katz
2005-01-09 5:35 ` Dmitry Torokhov
2005-01-09 14:24 ` Roey Katz
2005-01-09 16:02 ` Dmitry Torokhov
2005-01-10 1:09 ` Roey Katz
2005-01-11 7:39 ` Dmitry Torokhov
2005-01-13 3:19 ` Roey Katz
2005-01-13 3:42 ` Dmitry Torokhov
2005-01-14 23:06 ` Matthew Harrell
2005-01-15 0:29 ` Matthew Harrell
2005-01-15 1:31 ` Dmitry Torokhov
2005-01-15 2:28 ` Matthew Harrell
2005-01-15 2:58 ` Matthew Harrell
2005-01-15 3:57 ` Dmitry Torokhov
2005-01-17 19:56 ` Vojtech Pavlik
2005-01-17 19:58 ` Matthew Harrell
2005-01-17 20:03 ` Vojtech Pavlik
2005-01-15 7:23 ` Roey Katz
2005-02-12 17:50 ` Roey Katz
2005-02-13 6:45 ` Dmitry Torokhov
2005-03-03 13:26 ` Roey Katz
2005-01-03 3:03 ` Roey Katz
-- strict thread matches above, loose matches on Subject: below --
2005-01-15 11:05 Marco Cipullo
2005-01-15 17:42 ` Dmitry Torokhov
2005-01-15 18:02 ` marco
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=200501030123.58884.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=roey@sdf.lonestar.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