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#52970 - [linux-grsec] AMDGPU: Possible size overflow detected by PaX
Attached to Project:
Community Packages
Opened by manni (manik) - Wednesday, 15 February 2017, 05:13 GMT
Last edited by Daniel Micay (thestinger) - Saturday, 18 March 2017, 06:09 GMT
Opened by manni (manik) - Wednesday, 15 February 2017, 05:13 GMT
Last edited by Daniel Micay (thestinger) - Saturday, 18 March 2017, 06:09 GMT
|
DetailsDescription:
When using the grsec kernel on AMD gpus (using the new amdgpu driver), the boot process does not finish and pax creates the following log message in the journal: PAX: size overflow detected in function ttm_bo_handle_move_mem drivers/gpu/drm/ttm/ttm_bo.c:388 cicus.459_185 max, count: 5, decl: offset; num: 0; context: ttm_buffer_object; This issue is already know upstream and will probably be solved by a kernel update: https://forums.grsecurity.net/viewtopic.php?f=3&t=4667 https://bugzilla.kernel.org/show_bug.cgi?id=194579 Meanwhile this bugreport can provide information to other users wondering about this issue. Also, since there are ways to make exceptions for pax, is there maybe a way to workaround this issue until a new kernel version is released? |
This task depends upon
Closed by Daniel Micay (thestinger)
Saturday, 18 March 2017, 06:09 GMT
Reason for closing: Upstream
Additional comments about closing: Not going to be doing anything about these issues downstream.
Saturday, 18 March 2017, 06:09 GMT
Reason for closing: Upstream
Additional comments about closing: Not going to be doing anything about these issues downstream.
Comment by manni (manik) -
Friday, 17 February 2017, 07:26 GMT
The current version 4.9.10 in testing, still has the same issue.
Comment by Daniel Micay (thestinger) -
Saturday, 18 February 2017, 08:06 GMT
You can add pax_size_overflow_report_only on the kernel command line.
Comment by manni (manik) -
Saturday, 18 February 2017, 13:00 GMT
Thanks alot, that solved the issue for now.