The kernel can now show QR code's for DRM panics as summarized in this lwn.net article and discussions on enabling it in Fedora. Archweb could expose an url where we decode the zlib compressed data which includes the panic message and a backtrace an example JavaScript demo is available here.
Archweb could provide https://archlinux.org/panic_report where we decode the report using pako and guide the user in what the next steps would with reporting the issue.
We have to make sure that the decoded data does not end up on the server as this might? contain privacy sensitive information.
This feature can be tested if we enabled DRM_PANIC_DEBUG, and set CONFIG_DRM_PANIC_SCREEN_QR_CODE_URL=https://archlinux.org/panic_report#
The kernel can now show QR code's for DRM panics as summarized in this lwn.net article and discussions on enabling it in Fedora. Archweb could expose an url where we decode the zlib compressed data which includes the panic message and a backtrace an example JavaScript demo is available here.
Archweb could provide
https://archlinux.org/panic_reportwhere we decode the report using pako and guide the user in what the next steps would with reporting the issue.We have to make sure that the decoded data does not end up on the server as this might? contain privacy sensitive information.
This feature can be tested if we enabled DRM_PANIC_DEBUG, and set
CONFIG_DRM_PANIC_SCREEN_QR_CODE_URL=https://archlinux.org/panic_report#