Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#51767 - [linux-grsec] Kernel panic when resuming from suspend
Attached to Project:
Community Packages
Opened by Joe Gabinsky (SpuriousStar) - Wednesday, 09 November 2016, 16:29 GMT
Last edited by Daniel Micay (thestinger) - Thursday, 10 November 2016, 12:23 GMT
Opened by Joe Gabinsky (SpuriousStar) - Wednesday, 09 November 2016, 16:29 GMT
Last edited by Daniel Micay (thestinger) - Thursday, 10 November 2016, 12:23 GMT
|
DetailsDescription:
I got kernel panic after resuming from suspend with a black screen. Even pax_size_overflow_report_only option command in boot doesn't help. It's a hard freeze so there aren't any logs left. Vanilla kernel works ok. Previous grsec kernels works ok. I don't use any out of tree kernel modules. My hardware is a laptop with intel broadwell cpu/gpu. I'm using plasma 5 X11 session Additional info: * linux-grsec-1:4.8.6.r201611082138-1-x86_64.pkg.tar.xz |
This task depends upon
Closed by Daniel Micay (thestinger)
Thursday, 10 November 2016, 12:23 GMT
Reason for closing: Fixed
Additional comments about closing: 201611091800.patch fixes this per the changelog, and it's now packaged
Thursday, 10 November 2016, 12:23 GMT
Reason for closing: Fixed
Additional comments about closing: 201611091800.patch fixes this per the changelog, and it's now packaged
Comment by PaX Team (paxteam) -
Wednesday, 09 November 2016, 19:14 GMT
thanks for the report (next time perhaps notify us directly ;), this will be fixed in the next patch. as a temporary workaround you can remove the forced constification of boot_cpu_data in arch/x86/kernel/setup.c (the __read_only attribute).
Comment by Joe Gabinsky (SpuriousStar) -
Wednesday, 09 November 2016, 20:16 GMT
I was considering reporting upstream but without logs I wasn't sure if I can get any feedback from you. I'll try next time, thanks.
Comment by PaX Team (paxteam) -
Wednesday, 09 November 2016, 21:29 GMT
no problem, fortunately i managed to reproduce it in qemu which is something you can also try for hard cases like this.