From: Olaf Hering <olh@suse.de>
To: dtor_core@ameritech.net
Cc: linuxppc-dev@ozlabs.org, Vojtech Pavlik <vojtech@suse.cz>,
linux-kernel@vger.kernel.org
Subject: Re: atkbd_init lockup with 2.6.11-rc1
Date: Fri, 28 Jan 2005 15:55:11 +0100 [thread overview]
Message-ID: <20050128145511.GA29340@suse.de> (raw)
In-Reply-To: <d120d50005012806435a17fe98@mail.gmail.com>
On Fri, Jan 28, Dmitry Torokhov wrote:
> On Fri, 28 Jan 2005 14:58:27 +0100, Olaf Hering <olh@suse.de> wrote:
> > On Fri, Jan 28, Olaf Hering wrote:
> >
> > >
> > > My IBM RS/6000 B50 locks up with 2.6.11rc1, it dies in atkbd_init():
> >
> > It fails also on PReP, not only on CHRP. 2.6.10 looks like this:
> >
> > Calling initcall 0xc03bc430: atkbd_init+0x0/0x2c()
> > atkbd.c: keyboard reset failed on isa0060/serio1
> > atkbd.c: keyboard reset failed on isa0060/serio0
> >
>
> So it could not reset it even before, but it was not getting stuch
> tough... What about passing atkbd.reset=0?
I will try that.
Adding a printk after the outb() fixes it as well.
Do you have a version of that i8042 delay patch for 2.6.11-rc2-bk6?
Maybe it will help.
next prev parent reply other threads:[~2005-01-28 14:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-28 13:22 atkbd_init lockup with 2.6.11-rc1 Olaf Hering
2005-01-28 13:58 ` Dmitry Torokhov
2005-01-28 14:02 ` Olaf Hering
2005-01-28 13:58 ` Olaf Hering
2005-01-28 14:43 ` Dmitry Torokhov
2005-01-28 14:55 ` Olaf Hering [this message]
2005-01-28 15:22 ` Dmitry Torokhov
2005-01-28 16:17 ` Olaf Hering
2005-01-28 16:43 ` Dmitry Torokhov
2005-01-28 16:47 ` Olaf Hering
2005-01-28 17:34 ` Dmitry Torokhov
2005-01-28 17:37 ` Olaf Hering
2005-01-28 19:00 ` Olaf Hering
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=20050128145511.GA29340@suse.de \
--to=olh@suse.de \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=vojtech@suse.cz \
/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).