[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1461431448.8450.2.camel@telenet.be>
Date: Sat, 23 Apr 2016 19:10:48 +0200
From: Frederik Himpe <fhimpe@...enet.be>
To: Michal Hocko <mhocko@...nel.org>
Cc: linux-kernel@...r.kernel.org
Subject: Re: 3.5.0: BUG: Bad page state in process Compositor pfn:16834f
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@...enet.be>
Powered by blists - more mailing lists