11:16:30, robert shteynfeld wrote:
> > Attached is the dmesg from patched kernel.
>
> Your Node1 physical memory range precedes Node0 which is quite unusual
> but it shouldn't be a huge problem on its own. But memory ranges are
> not aligned to the memory section
>
&g
it scrolled by too quickly (and boot_delay
froze the output).
On Fri, Jan 25, 2019 at 10:58 AM Michal Hocko wrote:
>
> On Fri 25-01-19 10:52:06, robert shteynfeld wrote:
> > The person who pointed to mm/page_alloc.c commits likely causing the
> > issue did not have time to b
The person who pointed to mm/page_alloc.c commits likely causing the
issue did not have time to build a patched/reverted kernel to confirm
his hypothesis. When I tried backing out the two separate commits he
suggested, the first commit (ie. the one in the subject) was the one
that when backed out
-- Forwarded message -
From: robert shteynfeld
Date: Thu, Jan 24, 2019 at 9:21 AM
Subject: kernel panic due to
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2830bf6f05fb3e05bc4743274b806c821807a684
To: ,
Cc:
Hi,
It looks like the above commit
4 matches
Mail list logo
