From: Michael Neuling <mikey@neuling.org>
To: Kay Sievers <kay@vrfy.org>
Cc: linuxppc-dev@ozlabs.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Wu Fengguang <fengguang.wu@intel.com>,
Joe Perches <joe@perches.com>,
"Paul E. McKenney" <paulmck@us.ibm.com>
Subject: Re: [PATCH v3] printk: Have printk() never buffer its data
Date: Fri, 06 Jul 2012 13:39:39 +1000 [thread overview]
Message-ID: <29711.1341545979@neuling.org> (raw)
In-Reply-To: <CAPXgP12_F_H2XPpo2wFmb-u3jBdV__=h67R-LVYbqHuLh7tqLg@mail.gmail.com>
Kay Sievers <kay@vrfy.org> wrote:
> On Fri, Jul 6, 2012 at 2:41 AM, Michael Neuling <mikey@neuling.org> wrote:
>
> >> > Does this happen only very early during bootup, or also later when the
> >> > box fully initialized?
> >
> > I'm seeing during boot but not later (xmon (ppc kernel debugger) doesn't
> > see it if I do 'echo x > /proc/sysrq-trigger') . I wouldn't say
> > it's "very early boot". It's a secondary CPU coming up and the primary
> > is waiting for it. We've already configured the console when this
> > happens.
>
> Sounds like an early boot console.
>
> >> > The output of 'dmesg' later looks always correct, right?
> >
> > No, dmesg also has the extra new lines: eg
> >
> > <4>NIP: c00000000004e234 LR: c00000000004e230 CTR: 0000000000000000
> > <4>REGS: c00000007c3b7b50 TRAP: 0700 Tainted: G W (3.5.0-rc4-mikey)
> > <4>MSR: 9000000000021032
> > <4><
> > <4>SF
> > <4>,HV
> > <4>,ME
> > <4>,IR
> > <4>,DR
> > <4>,RI
> > <4>>
> > <4> CR: 28000042 XER: 22000000
>
> Can you please paste the output of /dev/kmsg of this section? So we
> can see the timestamps and what really went into the record buffer.
Sure.
4,89,24561;NIP: c000000000048164 LR: c000000000048160 CTR: 0000000000000000
4,90,24576;REGS: c00000007e59fb50 TRAP: 0700 Tainted: G W (3.5.0-rc4-mikey)
4,91,24583;MSR: 9000000000021032
4,92,24586;<
4,93,24591;SF
4,94,24596;,HV
4,95,24601;,ME
4,96,24606;,IR
4,97,24611;,DR
4,98,24616;,RI
4,99,24619;>
4,100,24628; CR: 28000042 XER: 22000000
>
> >> Could you possibly try this patch?
> >
> > Sorry, doesn't help. It also reprints the entire boot log to the
> > console once the console get inited.
>
> Which is the normal behaviour to do that, right? We should not have
> touched any of that logic.
Not until this patch you asked me to try. Hence why I noted it.
Mikey
next prev parent reply other threads:[~2012-07-06 3:39 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-25 19:05 [PATCH v3] printk: Have printk() never buffer its data Steven Rostedt
2012-06-25 22:07 ` Andrew Morton
2012-06-25 23:55 ` Greg Kroah-Hartman
2012-06-26 0:01 ` Linus Torvalds
2012-06-26 0:23 ` Greg Kroah-Hartman
2012-06-26 0:40 ` Linus Torvalds
2012-06-26 0:56 ` Kay Sievers
2012-06-26 1:40 ` Linus Torvalds
2012-06-26 16:07 ` Kay Sievers
2012-06-26 16:30 ` Joe Perches
2012-06-26 16:58 ` Greg Kroah-Hartman
2012-06-26 17:00 ` Kay Sievers
2012-06-26 17:02 ` Greg Kroah-Hartman
2012-06-26 18:34 ` Greg Kroah-Hartman
2012-06-26 18:38 ` Greg Kroah-Hartman
2012-06-26 18:48 ` Greg Kroah-Hartman
2012-06-27 15:13 ` Steven Rostedt
2012-06-27 15:18 ` Steven Rostedt
2012-06-27 15:26 ` Kay Sievers
2012-06-28 7:38 ` Kay Sievers
2012-06-28 1:48 ` Greg Kroah-Hartman
2012-06-28 1:54 ` Steven Rostedt
2012-06-28 2:55 ` Steven Rostedt
2012-06-29 5:30 ` Greg Kroah-Hartman
2012-06-29 11:18 ` Steven Rostedt
2012-06-29 15:40 ` Greg Kroah-Hartman
2012-06-28 5:00 ` Joe Perches
2012-07-05 7:03 ` Michael Neuling
2012-07-05 8:39 ` Kay Sievers
2012-07-05 8:53 ` Kay Sievers
2012-07-05 10:20 ` Michael Neuling
2012-07-05 11:47 ` Kay Sievers
2012-07-05 12:50 ` Kay Sievers
2012-07-06 0:41 ` Michael Neuling
2012-07-06 0:56 ` Kay Sievers
2012-07-06 3:39 ` Michael Neuling [this message]
2012-07-06 3:47 ` Michael Neuling
2012-07-06 10:46 ` Kay Sievers
2012-07-06 15:12 ` Kay Sievers
2012-07-06 21:04 ` Michael Neuling
2012-07-08 17:55 ` Kay Sievers
2012-07-09 17:09 ` Greg Kroah-Hartman
2012-07-09 17:15 ` Joe Perches
2012-07-09 22:36 ` Michael Neuling
2012-07-09 21:42 ` Joe Perches
2012-07-09 22:10 ` Kay Sievers
2012-07-09 22:29 ` Joe Perches
2012-07-09 22:40 ` Kay Sievers
2012-07-09 23:32 ` Joe Perches
2012-07-09 23:41 ` Joe Perches
2012-06-26 0:18 ` Joe Perches
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=29711.1341545979@neuling.org \
--to=mikey@neuling.org \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=kay@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mingo@elte.hu \
--cc=paulmck@us.ibm.com \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).