From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Roey Katz <roey@sdf.lonestar.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup
Date: Wed, 5 Jan 2005 23:16:47 -0500 [thread overview]
Message-ID: <200501052316.48443.dtor_core@ameritech.net> (raw)
In-Reply-To: <200501040117.28803.dtor_core@ameritech.net>
On Tuesday 04 January 2005 01:17 am, Dmitry Torokhov wrote:
> On Tuesday 04 January 2005 12:49 am, Roey Katz wrote:
> > Dmitry,
> >
> > I have tried kernels 2.6.9-rc2-bk3 and 2.6.9-rc2-bk4. I first copied the
> > .config from the stripped-down 2.6.10 into the 2.6.9- directories and then
> > ran make oldconfig (hopefully make oldconfig works in reverse?). Then I
> > built and ran the kernels. Both exhibit the same behavior as 2.6.10
> > regarding the keyboard.
> >
> > The /var/log/{dmesg,syslog,messages,kern.log} files for both kernels are
> > available at:
> >
> > http://roey.freeshell.org/mystuff/kernel/
> >
> >
> > - Roey
> >
> > PS: I forgot the log_buf_len=131072, hope it's ok for you...
> > PPS: I also forgot "acpi=off". Should I re-run these tests?
> >
>
> Ok, it looks that the big input update is not to blame. Just to make sure
> could you re-run the tests with -bk3 and -bk4 but with powering the box
> down instead of simply rebooting to ensure that noth kernels get completely
> fresh start. If keyboard still does not work I am afraid you will have to
> resort to binary search to figure out which 2.6.9-*-bk is at fault.
>
Roey,
I just realized that -bk3 also had input changes. Could you try booting -bk2?
--
Dmitry
next prev parent reply other threads:[~2005-01-06 4:16 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
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 [this message]
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
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=200501052316.48443.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;
as well as URLs for NNTP newsgroup(s).