All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Konstantin Khlebnikov <khlebnikov@openvz.org>,
	Oleg Nesterov <oleg@redhat.com>
Subject: Re: linux-next: boot problem with next-20120607
Date: Thu, 7 Jun 2012 15:05:49 -0700	[thread overview]
Message-ID: <20120607150549.63f3ab81.akpm@linux-foundation.org> (raw)
In-Reply-To: <20120607135320.7a1298385346bc238a0f92b0@canb.auug.org.au>

On Thu, 7 Jun 2012 13:53:20 +1000
Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi Andrew,
> 
> My boot of next-20120607 in PowerPC produces lots of these warnings:
> 
> BUG: Bad rss-counter state mm:c000000278508000 idx:0 val:-27
> BUG: Bad rss-counter state mm:c000000278284000 idx:0 val:-27
> BUG: Bad rss-counter state mm:c000000279e13000 idx:0 val:-27
> BUG: Bad rss-counter state mm:c000000278285400 idx:0 val:-27
> 
> And so on (with different mm, idx and val numbers).  Searching showed me
> commit "mm: correctly synchronize rss-counters at exit/exec" which seems
> to be there to fix this exact problem?

Well that's a worry.  Are you really sure
mm-correctly-synchronize-rss-counters-at-exit-exec.patch was applied at
the time?

There's been an extended amount of inconclusive waffling on that patch,
but I thought it concerned the best way to fix it, rather than
*whether* it fixes it.

  reply	other threads:[~2012-06-07 22:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-07  3:53 linux-next: boot problem with next-20120607 Stephen Rothwell
2012-06-07 22:05 ` Andrew Morton [this message]
2012-06-07 22:20   ` Stephen Warren
2012-06-07 23:57   ` Stephen Rothwell
2012-06-08  0:50     ` Stephen Rothwell

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=20120607150549.63f3ab81.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=khlebnikov@openvz.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.