public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Simon Farnsworth <simon.farnsworth@onelan.com>
To: Joe Korty <joe.korty@ccur.com>
Cc: Ingo Molnar <mingo@elte.hu>, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] printk timestamp post-boot suppression
Date: Wed, 27 Aug 2008 16:26:52 +0100	[thread overview]
Message-ID: <48B5723C.4020705@onelan.com> (raw)
In-Reply-To: <20080827151613.GA10325@tsunami.ccur.com>

Joe Korty wrote:
> Suppress printk timestamping after system boot.
> 
> The timestamp printk prefix seems most useful during boot,
> where it easily shows where the boot sequence is spending
> its time.
> 
It's also very useful while the system is running. We've had problems
with systems where the HDD or libata was "hiccuping" and stalling the
entire system for 30 seconds; our logs were useless, as syslog was
timestamping with the timestamp *after* the stall ended (as that was
when it received the message), and dmesg had no timestamps.

In this case, our problem ran away and hid when we turned on printk
timestamps, but if it recurred, we'd want the timestamps available to
let us work out which operation was taking lots of time, without having
to rebuild the kernel.
-- 
Simon Farnsworth


  reply	other threads:[~2008-08-28  8:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-27 15:16 [PATCH] printk timestamp post-boot suppression Joe Korty
2008-08-27 15:26 ` Simon Farnsworth [this message]
2008-08-27 16:16 ` Mark Brown
2008-08-27 17:04   ` [PATCH] printk timestamp post-boot suppression, v2 Joe Korty
2008-08-27 17:13     ` Simon Farnsworth
2008-08-27 17:22       ` Joe Korty
2008-08-27 17:27         ` Joe Korty
2008-08-27 17:22     ` Andi Kleen
2008-08-28  9:40     ` Ingo Molnar

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=48B5723C.4020705@onelan.com \
    --to=simon.farnsworth@onelan.com \
    --cc=joe.korty@ccur.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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