Resuming from suspend on 4.8.6-hardened causes a kernel panic (every time). This is due to a recent change in grsecurity. The bug was caught (see archlinux bug tracker link), and the grsecurity team pushed a fix, which the changelog mentions fixes this issue. (see https://grsecurity.net/changelog-test.txt). This package is most likely built against an older version of the grsecurity patches. (Looking at the ebuild and the archive it sources from http://dev.gentoo.org/~blueness/hardened-sources/hardened-patches/, it seems to already include the newest patch. Something else must be interfering.) Reproducible: Always Steps to Reproduce: 1. Suspend to RAM (pm-suspend) 2. Attempt to resume from suspend Actual Results: Kernel panic hard crash (no logs) Expected Results: Resume from suspend
I did some testing and recompiled by changing arch/x86/kernel/setup.c such that the boot_cpu_data __read_only attribute is changed back to a __read_mostly (as it was in previous versions). After making this change and recompiling, all is working as expected. This is a potential fix for the maintainer and could help to diagnose which patches are breaking resume from suspend.
(In reply to anoteros from comment #1) > I did some testing and recompiled by changing arch/x86/kernel/setup.c such > that the boot_cpu_data __read_only attribute is changed back to a > __read_mostly (as it was in previous versions). After making this change and > recompiling, all is working as expected. > > This is a potential fix for the maintainer and could help to diagnose which > patches are breaking resume from suspend. Okay I've made upstream aware of this. To be clear, sys-kernel/hardened-sources-4.8.6 does use grsecurity-3.1-4.8.6-201611091800
(In reply to Anthony Basile from comment #2) > To be clear, sys-kernel/hardened-sources-4.8.6 does use > grsecurity-3.1-4.8.6-201611091800 grsecurity-3.1-4.8.7-201611102210 has the remaining fixes for the resume problem.
(In reply to PaX Team from comment #3) > (In reply to Anthony Basile from comment #2) > > To be clear, sys-kernel/hardened-sources-4.8.6 does use > > grsecurity-3.1-4.8.6-201611091800 > > grsecurity-3.1-4.8.7-201611102210 has the remaining fixes for the resume > problem. i've pushed out =sys-kernel/hardened-sources-4.8.7 which has that patch.
(In reply to Anthony Basile from comment #4) > i've pushed out =sys-kernel/hardened-sources-4.8.7 which has that patch. I just tested with sys-kernel/hardened-sources-4.8.7 and all is back to the way it should be. Thanks for your help!
