From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Pat Erley <pat-lkml@erley.org>,
Linux-Next <linux-next@vger.kernel.org>,
kirill.shutemov@linux.intel.com, linux-mm <linux-mm@kvack.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: BUG: non-zero nr_pmds on freeing mm: 1
Date: Mon, 9 Feb 2015 18:42:48 +0200 [thread overview]
Message-ID: <20150209164248.GA29522@node.dhcp.inet.fi> (raw)
In-Reply-To: <CA+icZUVTVdHc3QYD1LkWn=Xt-Zz6RcXPcjL6Xbpz0FZ6rdA5CQ@mail.gmail.com>
On Sat, Feb 07, 2015 at 08:33:02AM +0100, Sedat Dilek wrote:
> On Sat, Feb 7, 2015 at 6:12 AM, Pat Erley <pat-lkml@erley.org> wrote:
> > I'm seeing the message in $subject on my Xen DOM0 on next-20150204 on
> > x86_64. I haven't had time to bisect it, but have seen some discussion on
> > similar topics here recently. I can trigger this pretty reliably by
> > watching Netflix. At some point (minutes to hours) into it, the netflix
> > video goes black (audio keeps going, so it still thinks it's working) and
> > the error appears in dmesg. Refreshing the page gets the video going again,
> > and it will continue playing for some indeterminate amount of time.
> >
> > Kirill, I've CC'd you as looking in the logs, you've patched a false
> > positive trigger of this very recently(patch in kernel I'm running). Am I
> > actually hitting a problem, or is this another false positive case? Any
> > additional details that might help?
> >
> > Dmesg from system attached.
>
> [ CC some mm folks ]
>
> I have seen this, too.
>
> root# grep "BUG: non-zero nr_pmds on freeing mm:" /var/log/kern.log | wc -l
> 21
>
> Checking my logs: On next-20150203 and next-20150204.
>
> I am here not in a VM environment and cannot say what causes these messages.
Sorry, my fault.
The patch below should fix that.
next prev parent reply other threads:[~2015-02-09 16:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-07 7:33 Sedat Dilek
2015-02-07 8:42 ` Sedat Dilek
2015-02-07 8:56 ` Pat Erley
2015-02-07 9:20 ` Sedat Dilek
2015-02-07 9:30 ` Sedat Dilek
2015-02-07 22:27 ` Pat Erley
2015-02-07 22:33 ` Sedat Dilek
2015-02-08 7:32 ` Pat Erley
2015-02-09 16:42 ` Kirill A. Shutemov [this message]
2015-02-09 17:06 ` Sedat Dilek
2015-02-09 17:13 ` Kirill A. Shutemov
2015-02-09 17:45 ` Pat Erley
2015-02-09 17:50 ` Sedat Dilek
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=20150209164248.GA29522@node.dhcp.inet.fi \
--to=kirill@shutemov.name \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=pat-lkml@erley.org \
--cc=sedat.dilek@gmail.com \
/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