From: Frederik Himpe <fhimpe@telenet.be>
To: Michal Hocko <mhocko@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 3.5.0: BUG: Bad page state in process Compositor pfn:16834f
Date: Sat, 23 Apr 2016 19:10:48 +0200 [thread overview]
Message-ID: <1461431448.8450.2.camel@telenet.be> (raw)
In-Reply-To: <20160416202931.GB15128@dhcp22.suse.cz>
On za, 2016-04-16 at 16:29 -0400, Michal Hocko wrote:
> On Sat 16-04-16 18:37:53, Frederik Himpe wrote:
> >
> >
> > Apr 16 20:21:53 piranha kernel: [27926.414148] BUG: Bad page state
> > in process Compositor pfn:16834f
> > Apr 16 20:21:53 piranha kernel: [27926.414153]
> > page:ffffea0005a0d3c0 count:0 mapcount:0 mapping: (null)
> > index:0x0
> > Apr 16 20:21:53 piranha kernel: [27926.414155] flags:
> > 0x1ffff8000000000()
> Flags look weird
>
> >
> > Apr 16 20:21:53 piranha kernel: [27926.414156] page dumped because:
> > page still charged to cgroup
> > Apr 16 20:21:53 piranha kernel: [27926.414157] page-
> > >mem_cgroup:4000000000000000
> And we think that the page is still charged because page->mem_cgroup
> !=
> NULL. The value is not a pointer though. It seems like somebody is
> corrupting the struct page. Hard to tell who that might be though
> from
> the available information. This will be nasty to track down I am
> afraid.
> How reproducible is it?
I do not know how to reproduce this. I upgraded to 4.5.1, and with this
kernel however I experienced already multiple hard freezes. I suspect
they are the same problem, but there is nothing in the kernel logs. So
4.5 series is definitely unstable on this system.
--
Frederik Himpe <fhimpe@telenet.be>
prev parent reply other threads:[~2016-04-23 17:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-16 18:37 3.5.0: BUG: Bad page state in process Compositor pfn:16834f Frederik Himpe
2016-04-16 20:29 ` Michal Hocko
2016-04-23 17:10 ` Frederik Himpe [this message]
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=1461431448.8450.2.camel@telenet.be \
--to=fhimpe@telenet.be \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@kernel.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