From: Nick Bowler <nbowler@elliptictech.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BUG: Bad rss-counter state
Date: Thu, 21 Jun 2012 09:31:11 -0400 [thread overview]
Message-ID: <20120621133111.GA13820@elliptictech.com> (raw)
In-Reply-To: <20120621095024.GA10745@tiehlicka.suse.cz>
On 2012-06-21 11:50 +0200, Michal Hocko wrote:
> On Wed 20-06-12 15:49:08, Nick Bowler wrote:
> > Hi folks,
> >
> > I just noticed the following couple lines in my kernel log for Linux
> > 3.4.2:
> >
> > Jun 20 14:57:54 emergent kernel: BUG: Bad rss-counter state mm:ffff88000ff1f400 idx:1 val:-2
> > Jun 20 14:57:54 emergent kernel: BUG: Bad rss-counter state mm:ffff88000ff1f400 idx:2 val:2
> >
> > I have no idea what these messages mean, nor what I was doing exactly
> > at 14:57:54 today, nor whether they've been fixed in newer kernels.
> > Regardless, they appear to be telling me that there's a kernel problem
> > since they contain the word "BUG", so I figured I had better report them
> > nonetheless. Other than the fact that these messages were printed, the
> > system is operating normally.
>
> The issue is known and the fix can be found at
> https://lkml.org/lkml/2012/6/9/47
Ah, and it appears to have been merged by Linus yesterday.
Thanks,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
next prev parent reply other threads:[~2012-06-21 13:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 19:49 BUG: Bad rss-counter state Nick Bowler
2012-06-21 9:50 ` Michal Hocko
2012-06-21 13:31 ` Nick Bowler [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-16 4:48 cheung wall
2012-06-15 19:19 Ralf Hildebrandt
2012-04-08 11:39 Markus Trippelsdorf
2012-04-08 11:39 ` Markus Trippelsdorf
2012-04-09 5:58 ` Markus Trippelsdorf
2012-04-09 5:58 ` Markus Trippelsdorf
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=20120621133111.GA13820@elliptictech.com \
--to=nbowler@elliptictech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.cz \
/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.