Bug#852324: Disable CONFIG_DEBUG_WX in order to avoid this issue.
On Wed, 2017-07-26 at 19:23 +0200, Helio Loureiro wrote:
> Hi,
>
> I already sent.
Please provide a full serial log when booting with the bad kernel.
Also please let us know what version of Xen you are running and whether
this was running as a guest or as dom0.
> And in the first post in this bug it says:
>
> "
> When I boot my system with Xen, I get the following section in dmesg:
[ 13.588386] WARNING: CPU: 18 PID: 1 at /build/linux-zDY19G/linux-4.8.15/arch/x86/mm/dump_pagetables.c:225 note_page+0x5e8/0x790
> [...]
> [ 13.588392] CPU: 18 PID: 1 Comm: swapper/0 Not tainted 4.8.0-2-amd64 #1 Debian 4.8.15-2
> [...]
> But when I boot my system 'normally', ie without Xen, the error does
> not
> show up."
> He clearly states it isn't booting. It is crashing.
The original bug report was running the same kernel as the splat at the
point where reportbug was run, so it is booting at least far enough to
do that. See the "Kernel: Linux 4.8.0-2-amd64" in the original report,
which is also in the warning message.
There is no suggestion anywhere that it isn't booting in the original
report, just that when it does boot this message appears in the logs.
All he says is that this warning (he says "error", but that doesn't
imply a boot failure either) doesn't appear with the normal kernel.
See also the logs at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
852324#25 which show the system continuing to successfully boot after
the splat.
> How could that not be related?
Because you are experiencing some other bug later on, or perhaps the
check which resulting in a WARNING for the original poster has a bug in
it which is causing a hang for you, please provide us with the
information we need in order to diagnose which it is rather than
continuing to assert that it is the same issue, otherwise no progress
is going to happen here.
Ian.
Reply to: