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 16:46:39 -0700	[thread overview]
Message-ID: <1152229599.24656.175.camel@cog.beaverton.ibm.com> (raw)
In-Reply-To: <44AD9605.6000601@imap.cc>

On Fri, 2006-07-07 at 01:00 +0200, Tilman Schmidt wrote:
> With kernel 2.6.18-rc1 I am experiencing strange delays before printk
> messages from my driver appear in the syslog. The last couple of printk
> lines only appear if I hit a key on the system keyboard. Even just
> pressing and releasing a shift key will do. Other input, like connecting
> with ssh from another computer and typing into that session or moving or
> clicking the mouse, doesn't help. At the same time, userspace syslog
> messages like those from sshd appear just fine.
> 
> Example excerpt from /var/log/messages:
> 
> > Jul  7 00:16:08 gx110 kernel: [  746.583136] gigaset: 0: if_write()
> > Jul  7 00:16:08 gx110 kernel: [  746.583154] gigaset: CMD Transmit (10 bytes):
> > Jul  7 00:16:08 gx110 kernel: [  746.583203] bas_gigaset: setting ATREADY time
> > Jul  7 00:16:08 gx110 kernel: [  746.585887] bas_gigaset: write_command: sent 
> > Jul  7 00:16:08 gx110 kernel: [  746.612869] gigaset: received response (6 byt
> > Jul  7 00:16:28 gx110 sshd[6134]: Accepted publickey for ts from 192.168.59.12
> > Jul  7 00:28:26 gx110 kernel: [  746.687844] gigaset: 0: if_write()
> > Jul  7 00:28:26 gx110 kernel: [  746.687944] gigaset: CMD Transmit (17 bytes):
> > Jul  7 00:28:26 gx110 kernel: [  746.688002] bas_gigaset: setting ATREADY time
> > Jul  7 00:28:26 gx110 kernel: [  746.690803] bas_gigaset: write_command: sent 
> 
> Note how the PRINTK_TIME timestamps increase in sub-second increments
> while syslogd's timestamps show an enormous gap after 00:16:08.
> 
> With kernel 2.6.17.1 on the same machine there are no such delays. All
> printk messages appear immediately, and the deltas in PRINTK_TIME and
> syslogd timestamps are quite consistent.

Hmmm. I'm assuming this is i386? Could you send me a full dmesg?

Also does booting w/ clocksource=jiffies change the behavior?

thanks
-john



  reply	other threads:[~2006-07-06 23:46 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 [this message]
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
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=1152229599.24656.175.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®