public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tilman Schmidt <tilman@imap.cc>
To: john stultz <johnstul@us.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux v2.6.18-rc1: printk delays
Date: Sat, 12 Aug 2006 15:14:26 +0200	[thread overview]
Message-ID: <44DDD432.8030302@imap.cc> (raw)
In-Reply-To: <1152233897.24656.179.camel@cog.beaverton.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 866 bytes --]

On Fri, 07 Jul 2006 17:06:09 +0200, john stultz wrote:
> Hmmm. Just to make sure I understand the situation: If you log in via
> ssh, and run dmesg, you do see your driver's output, but that output
> just doesn't get to syslog until you press a key on your keyboard?

Exactly. And it's only the system keyboard which does it - neither mouse
movements nor network traffic (like hitting keys in the ssh session) or
other system activity (like compiling the kernel of the day) will do.

FYI, the issue is still present in 2.6.18-rc4 and 2.6.18-rc3-mm2.

Please let me know if you need more information or if you want me to
test something.

Thanks,
Tilman

--
Tilman Schmidt                    E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeoeffnet mindestens haltbar bis: (siehe Rueckseite)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 253 bytes --]

  parent reply	other threads:[~2006-08-12 13:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6vtF8-99-7@gated-at.bofh.it>
2006-07-06 23:00 ` Linux v2.6.18-rc1: printk delays Tilman Schmidt
2006-07-06 23:46   ` john stultz
2006-07-07  0:18     ` Tilman Schmidt
2006-07-07  0:58       ` john stultz
2006-07-07 15:06         ` Tilman Schmidt
2006-07-17 17:02           ` Tilman Schmidt
2006-08-12 13:14         ` Tilman Schmidt [this message]
2006-07-06 23:40 ` Linux v2.6.18-rc1/reiserfs INFO: possible recursive locking detected Tilman Schmidt
2006-07-07  6:33   ` Arjan van de Ven
2006-07-07 17:28     ` Tilman Schmidt
2006-08-12 13:21   ` Tilman Schmidt

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=44DDD432.8030302@imap.cc \
    --to=tilman@imap.cc \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.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