From: Kay Sievers <kay@vrfy.org>
To: Dave Jones <davej@redhat.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Greg Kroah-Hartmann <greg@kroah.com>
Subject: Re: 3.5-rc6 printk formatting problem during oom-kill.
Date: Mon, 09 Jul 2012 20:48:51 +0200 [thread overview]
Message-ID: <1341859731.801.0.camel@mop> (raw)
In-Reply-To: <CAPXgP11oP4aKyg=HUNrb3z_ZbPjU+_u338sD6uhxKyJ43Z8sgQ@mail.gmail.com>
On Mon, 2012-07-09 at 20:27 +0200, Kay Sievers wrote:
> On Mon, Jul 9, 2012 at 8:03 PM, Dave Jones <davej@redhat.com> wrote:
> > I noticed that the format of the oom-killer output seems to have changed, and
> > now it spews stuff like..
> >
> > [49461.758070] lowmem_reserve[]:
> > [49461.758071] 0
> > [49461.758071] 2643
> > [49461.758071] 3878
> > [49461.758072] 3878
> > [49461.758072]
> > [49461.758072] Node 0
>
> > Does the oom-killer code need modifying, or the printk code ?
> > I know there's been some regressions in this area recently, but this is still
> > happening on the current tree (8c84bf4166a4698296342841a549bbee03860ac0)
>
> This likely fixes it:
> http://git.kernel.org/?p=linux/kernel/git/kay/patches.git;a=blob;f=kmsg-merge-cont.patch;hb=HEAD
>
> Let me check if it does, and if I can reproduce it.
It looks fine here with the above mentioned patch:
[ 0.000000] lowmem_reserve[]:
[ 0.000000] 0
[ 0.000000] 0
[ 0.000000] 0
[ 0.000000] 0
[ 0.000000]
[ 0.000000] DMA:
[ 0.000000] 1*4kB
[ 0.000000] 0*8kB
[ 0.000000] 0*16kB
[ 0.000000] 1*32kB
[ 0.000000] 2*64kB
[ 0.000000] 1*128kB
[ 0.000000] 1*256kB
[ 0.000000] 0*512kB
[ 0.000000] 1*1024kB
[ 0.000000] 1*2048kB
[ 0.000000] 3*4096kB
[ 0.000000] = 15908kB
becomes:
[ 0.000000] lowmem_reserve[]: 0 0 0 0
[ 0.000000] DMA: 1*4kB 0*8kB 0*16kB 1*32kB 2*64kB 1*128kB 1*256kB 0*512kB 1*1024kB 1*2048kB 3*4096kB = 15908kB
Thanks,
Kay
next prev parent reply other threads:[~2012-07-09 18:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 18:03 3.5-rc6 printk formatting problem during oom-kill Dave Jones
2012-07-09 18:27 ` Kay Sievers
2012-07-09 18:48 ` Kay Sievers [this message]
2012-07-09 20:31 ` Joe Perches
2012-07-09 20:40 ` Greg Kroah-Hartmann
2012-07-09 20:44 ` Joe Perches
2012-07-09 20:48 ` Kay Sievers
2012-07-09 21:08 ` Joe Perches
2012-07-09 20:56 ` Greg Kroah-Hartmann
2012-07-11 0:11 ` Dave Jones
2012-07-11 0:15 ` Greg Kroah-Hartmann
2012-07-12 0:54 ` Dave Jones
2012-07-12 13:52 ` Kay Sievers
2012-07-12 14:05 ` Dave Jones
2012-07-12 16:47 ` Kay Sievers
2012-07-12 17:02 ` Dave Jones
2012-07-12 17:11 ` Linus Torvalds
2012-07-12 18:25 ` Kay Sievers
2012-07-12 22:28 ` Kay Sievers
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=1341859731.801.0.camel@mop \
--to=kay@vrfy.org \
--cc=davej@redhat.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.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