mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Tilman Schmidt <tilman@imap.cc>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux v2.6.18-rc1: printk delays
Date: Thu, 06 Jul 2006 17:58:17 -0700	[thread overview]
Message-ID: <1152233897.24656.179.camel@cog.beaverton.ibm.com> (raw)
In-Reply-To: <44ADA84A.9000603@imap.cc>

On Fri, 2006-07-07 at 02:18 +0200, Tilman Schmidt wrote:
> On 07.07.2006 01:46, john stultz wrote:
> 
> > On Fri, 2006-07-07 at 01:00 +0200, Tilman Schmidt wrote:
> > 
> >>With kernel 2.6.18-rc1 [t]he last couple of printk
> >>lines only appear if I hit a key on the system keyboard. [...]
> > 
> > Hmmm. I'm assuming this is i386?
> 
> Yes, indeed. Sorry I didn't mention that.
> 
> > Could you send me a full dmesg?
> 
> Attached.

Thanks!

> > Also does booting w/ clocksource=jiffies change the behavior?
> 
> Nope. That didn't produce any discernible change.

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?


thanks again,
-john


  reply	other threads:[~2006-07-07  0:58 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 ` Tilman Schmidt
2006-07-06 23:46   ` john stultz
2006-07-07  0:18     ` Tilman Schmidt
2006-07-07  0:58       ` john stultz [this message]
2006-07-07 15:06         ` Tilman Schmidt
2006-07-17 17:02           ` Tilman Schmidt
2006-08-12 13:14         ` Tilman Schmidt
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=1152233897.24656.179.camel@cog.beaverton.ibm.com \
    --to=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tilman@imap.cc \
    /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
all inboxes | Powered by JetHome®