On Thu, May 17, 2018 at 08:13:35PM +0300, Ville Syrjälä wrote: > On Thu, May 17, 2018 at 06:49:47PM +0200, Michal Hocko wrote: > > On Thu 17-05-18 16:58:32, Ville Syrjälä wrote: > > > On Thu, May 17, 2018 at 04:36:29PM +0300, Ville Syrjälä wrote: > > > > On Thu, May 17, 2018 at 03:21:09PM +0200, Michal Hocko wrote: > > > > > On Thu 17-05-18 15:59:59, Ville Syrjala wrote: > > > > > > From: Ville Syrjälä <ville.syrjala@xxxxxxxxxxxxxxx> > > > > > > > > > > > > This reverts commit bad8c6c0b1144694ecb0bc5629ede9b8b578b86e. > > > > > > > > > > > > Make x86 with HIGHMEM=y and CMA=y boot again. > > > > > > > > > > Is there any bug report with some more details? It is much more > > > > > preferable to fix the issue rather than to revert the whole thing > > > > > right away. > > > > > > > > The machine I have in front of me right now didn't give me anything. > > > > Black screen, and netconsole was silent. No serial port on this > > > > machine unfortunately. > > > > > > Booted on another machine with serial: > > > > Could you provide your .config please? > > Attached. Not sure there's anything particularly useful in it though > since I've now seen this on all the highmem systems I've booted. > > > BTW I just noticed that the reported memory sizes look pretty crazy: > > Memory: 3926480K/3987424K available (5254K kernel code, 561K rwdata, > 2156K rodata, 572K init, 9308K bss, 56848K reserved, > 4096K cma-reserved, 3078532K highmem) > > vs. > > Memory: 7001976K/3987424K available (5254K kernel code, 561K rwdata, > 2156K rodata, 572K init, 9308K bss, 4291097664K reserved, > 4096K cma-reserved, 7005012K highmem) > > > > > [...] > > > [ 0.000000] cma: Reserved 4 MiB at 0x0000000037000000 > > [...] > > > [ 0.000000] BUG: Bad page state in process swapper pfn:377fe > > > [ 0.000000] page:f53effc0 count:0 mapcount:-127 mapping:00000000 index:0x0 > > > > OK, so this looks the be the source of the problem. -128 would be a > > buddy page but I do not see anything that would set the counter to -127 > > and the real map count updates shouldn't really happen that early. > > > > Maybe CONFIG_DEBUG_VM and CONFIG_DEBUG_HIGHMEM will tell us more. > > I'll see about grabbing another log. With DEBUG_VM the machine doesn't get far enough to print anything on the serial console. DEBUG_HIGHMEM didn't give me any new output. -- Ville Syrjälä Intel
