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 17:47:56 +0100 [thread overview]
Message-ID: <20050128164756.GA2154@suse.de> (raw)
In-Reply-To: <d120d500050128084345bb1abd@mail.gmail.com>
On Fri, Jan 28, Dmitry Torokhov wrote:
> > i8042_write_data(56) swapper(1):c0,j4294674787 enter 96
> > i8042_write_data(58) swapper(1):c0,j4294674787 leave 96
>
> So this trace is without printk but with udelay, right? This time
> keyboard does not hang but NAKs everything instead... What if you aso
> add udelay(20) after calls to i8042_write_data()?
Its with 2 printk in i8042_write_data(), just adding a printk after outb
in i8042_write_data fixes the hang.
> > md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
> > NET: Registered protocol family 2
> > .. here it hangs again.
>
> Do you know where exactly? Is it some IO port access again?
Havent debugged that one, yet. Hopefully a different issue. According to
the logs from 2.6.5, the next message would be
NET: Registered protocol family 2
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
NET: Registered protocol family 1
NET: Registered protocol family 17
next prev parent reply other threads:[~2005-01-28 16:48 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
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 [this message]
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=20050128164756.GA2154@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).