From: walt <w41ter@gmail.com>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: linux-kernel@vger.kernel.org, Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: commit a802dd0e breaks console keyboard input
Date: Fri, 24 Oct 2008 16:13:59 -0700 [thread overview]
Message-ID: <490256B7.1050906@gmail.com> (raw)
In-Reply-To: <20081024194414.GB4155@osiris.boeblingen.de.ibm.com>
Heiko Carstens wrote:
> On Fri, Oct 24, 2008 at 05:52:57AM -0700, w41ter@gmail.com wrote:
>> On Fri, 24 Oct 2008, Heiko Carstens wrote:
>>> On Thu, Oct 23, 2008 at 05:09:24PM -0700, walt wrote:
>>>> Hi team,
>>>>
>>>> commit a802dd0eb5fc97a50cf1abb1f788a8f6cc5db635
>>>> Author: Heiko Carstens<heiko.carstens@de.ibm.com>
>>>> Date: Mon Oct 13 23:50:08 2008 +0200
>>>>
>>>> Call init_workqueues before pre smp initcalls.
>>>>
>>>> This commit causes the console login prompt to ignore my keystrokes
>>>> so I'm unable to log in (though ssh works fine). Oddly, if I hit
>>>> ctrl-alt-delete the machine does reboot, but no other keystrokes
>>>> appear on the screen or have any effect that I can detect...
> Please try the patch below. It basically reverts the whole stop_machine
> patches. That way we should know if it really comes from the moved init
> call or if it is some other weird bug. I would have expected more bug
> reports if the stop_machine patches would be broken. Hmmm...
<second patch snipped for brevity>
Yes your second patch fixes the keyboard problem, thanks. The lack of
other complainers is what made me think of a BIOS bug, but that's just
wild guesswork on my part. I'm happy to keep trying patches if you can
keep making them :-)
next prev parent reply other threads:[~2008-10-24 23:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-24 0:09 walt
2008-10-24 7:28 ` Heiko Carstens
2008-10-24 11:07 ` Heiko Carstens
2008-10-24 12:52 ` w41ter
2008-10-24 19:44 ` Heiko Carstens
2008-10-24 23:13 ` walt [this message]
2008-10-25 14:16 ` Heiko Carstens
2008-10-25 18:48 ` Hugh Dickins
2008-10-25 20:36 ` walt
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=490256B7.1050906@gmail.com \
--to=w41ter@gmail.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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
Powered by JetHome