Bug#852324: Disable CONFIG_DEBUG_WX in order to avoid this issue.

2018-08-15 Thread Helio Loureiro
Hi, Today I faced again the same isse with the same error. Searching web by term "x86/mm: Checked W+X mappings: FAILED" I stumbled upon this bug again. And no answers. After some hours working in my VM to try to fix this issue, I found the root cause. It is some bug between xen and grub. My

Bug#852324: Disable CONFIG_DEBUG_WX in order to avoid this issue.

2017-07-26 Thread Helio Loureiro
Hi, I don't owe the server. Just have a VM that was running flawless with Debian since Squeeze. And for the first time Debian became a sour option. I was going to compile another kernel when I found also kernel-package isn't released because of unwatched issues. Best Regards, Helio

Bug#852324: Disable CONFIG_DEBUG_WX in order to avoid this issue.

2017-07-26 Thread Ian Campbell
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 b

Bug#852324: Disable CONFIG_DEBUG_WX in order to avoid this issue.

2017-07-26 Thread Helio Loureiro
Hi, I already sent. 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.588381] [ cut here ] [ 13.588386] WARNING: CPU: 18 PID: 1 at /build/linux-zDY19G/linux-4.8.15/arch/x86/mm/dump_pagetables.c:22

Bug#852324: Disable CONFIG_DEBUG_WX in order to avoid this issue.

2017-07-26 Thread Ian Campbell
On Wed, 2017-07-26 at 18:51 +0200, Helio Loureiro wrote: > Hi, > > It can't be.  It is the same bug as describe in this one. > > If you read the first post, it can't boot and shows the same content > as in the bug I detected now on my system. Nowhere there does it say anything about failing to b

Bug#852324: Disable CONFIG_DEBUG_WX in order to avoid this issue.

2017-07-26 Thread Helio Loureiro
Hi, It can't be. It is the same bug as describe in this one. If you read the first post, it can't boot and shows the same content as in the bug I detected now on my system. So it isn't a new bug. It was introduced since kernel 4.4 became available on upstream and not handled. Best Regards, He

Bug#852324: Disable CONFIG_DEBUG_WX in order to avoid this issue.

2017-07-26 Thread Helio Loureiro
Hi, And `reportbug kernel` won't work cause it requires the system or kernel to be up and running. It isn't the case. This bug is leading the system to an outage on boot. Best Regards, Helio Loureiro http://helio.loureiro.eng.br https://se.linkedin.com/in/helioloureiro http://twitter.com/helio

Bug#852324: Disable CONFIG_DEBUG_WX in order to avoid this issue.

2017-07-26 Thread Ian Campbell
This option does not (per its intent) present booting, it is just a check & warning. There may be a bug with the check which is causing a failure to boot, but you are the first to report that aspect and that isn't what #852324 was about until now. Please use `reportbug kernel` to report a fresh b

Bug#852324: Disable CONFIG_DEBUG_WX in order to avoid this issue.

2017-07-26 Thread Helio Loureiro
Hi, VM doesn't boot with this parameter enabled, as confirmed by Linus mail. So my upgraded to Stretch leaded to a complete system outage because of this parameter. I held on kernel 3.19 from Jessie meanwhile. Best Regards, Helio Loureiro http://helio.loureiro.eng.br https://se.linkedin.com/in/h

Bug#852324: Disable CONFIG_DEBUG_WX in order to avoid this issue.

2017-07-26 Thread Ian Campbell
On Wed, 2017-07-26 at 17:13 +0200, Helio Loureiro wrote: > Hi, > > As much it sounds correct to protect systems in this way, you broke > compatibility.  I'm back to kernel 3.19 until this is fixed. > > So in order to have such parameter enabled, you should at the least > provide a bootparam optio

Bug#852324: Disable CONFIG_DEBUG_WX in order to avoid this issue.

2017-07-26 Thread Ben Hutchings
On Wed, 2017-07-26 at 17:13 +0200, Helio Loureiro wrote: > Hi, > > As much it sounds correct to protect systems in this way, you broke > compatibility.  I'm back to kernel 3.19 until this is fixed. > > So in order to have such parameter enabled, you should at the least provide > a bootparam optio

Bug#852324: Disable CONFIG_DEBUG_WX in order to avoid this issue.

2017-07-26 Thread Helio Loureiro
Hi, As much it sounds correct to protect systems in this way, you broke compatibility. I'm back to kernel 3.19 until this is fixed. So in order to have such parameter enabled, you should at the least provide a bootparam option to toggle enabled or not. >From my point of view as user, you should

Bug#852324: Disable CONFIG_DEBUG_WX in order to avoid this issue.

2017-07-26 Thread Ben Hutchings
On Mon, 2017-07-24 at 20:18 +0200, Helio Loureiro wrote: > Hi, > > First an errata: I don't see messages since March, not January as I stated > wrongly before. > > And I tracked similar messages on other distros and found a message from > Linus himself about a way to avoid such error: > > https:

Bug#852324: Disable CONFIG_DEBUG_WX in order to avoid this issue.

2017-07-24 Thread Helio Loureiro
Hi, First an errata: I don't see messages since March, not January as I stated wrongly before. And I tracked similar messages on other distros and found a message from Linus himself about a way to avoid such error: https://lkml.org/lkml/2015/12/14/670 Checking standard Debian kernel settings, I