Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AMDGPU kernel module crashes in Linux 5.18, when watching a YouTube video in Firefox #37439

Closed
RicArch97 opened this issue Jun 7, 2022 · 3 comments
Labels

Comments

@RicArch97
Copy link
Contributor

RicArch97 commented Jun 7, 2022

System

  • xuname:
    Void 5.18.2_1 x86_64 AuthenticAMD uptodate rrrmFFFFFFFFFFFFFFFFFFFF
  • package:
    linux5.18 5.18.2_1 and firefox 100.0.2_1

Expected behavior

Watching YouTube video's on Firefox should work without the entire AMDGPU module crashing. Note that I have VAAPI enabled in Firefox. It did work on previous kernels without issues. Watching a video in google-chrome does not cause any crashes however.

Actual behavior

The AMDGPU module crashes apparently, as there is no longer video output. Sounds still keeps playing. Switching TTY's is no longer possible at that point though, can only press the reset button on my PC to reboot.

2022-06-07T20:04:32.80709 kern.err: [  416.963373] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring vcn_dec_1 timeout, signaled seq=623, emitted seq=624
2022-06-07T20:04:32.80711 kern.err: [  416.963447] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process RDD Process pid 8773 thread firefox:cs0 pid 9173
2022-06-07T20:04:33.91925 kern.err: [  418.075832] amdgpu 0000:0d:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x001e address=0x56e300 flags=0x0000]
2022-06-07T20:04:33.91926 kern.err: [  418.075838] amdgpu 0000:0d:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x001e address=0x56e340 flags=0x0000]
2022-06-07T20:04:34.91812 kern.err: [  419.075098] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
2022-06-07T20:04:34.91909 kern.err: [  419.075290] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
2022-06-07T20:04:34.91909 kern.err: [  419.075371] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
2022-06-07T20:04:34.91910 kern.err: [  419.075503] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
2022-06-07T20:04:34.91910 kern.err: [  419.075510] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
2022-06-07T20:04:34.91910 kern.err: [  419.075561] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
2022-06-07T20:04:34.91911 kern.err: [  419.075676] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
2022-06-07T20:04:34.94609 kern.err: [  419.102446] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
2022-06-07T20:04:35.07411 kern.err: [  419.230270] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* got no status for stream 000000009f623f91 on acrtc00000000dff54296
2022-06-07T20:05:00.19015 kern.err: [  444.345664] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
2022-06-07T20:05:14.79114 kern.err: [  458.945685] [drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR* [CRTC:77:crtc-0] hw_done or flip_done timed out
2022-06-07T20:05:25.03133 kern.err: [  469.185052] [drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR* [CRTC:80:crtc-1] hw_done or flip_done timed out

Steps to reproduce the behavior

On kernel 5.18.2, enable VAAPI in Firefox by setting media.ffmpeg.vaapi.enabled to true in about:config. I personally use the Sway window manager and run Firefox with MOZ_ENABLE_WAYLAND=1 to enable the Wayland backend and MOZ_DISABLE_RDD_SANDBOX=1 to make sure VAAPI works correctly, as stated in the Arch wiki.
Then, watch a YouTube video.

@MPC7500
Copy link

MPC7500 commented Jun 9, 2022

That's the right place for amdgpu rlated bugs:
https://gitlab.freedesktop.org/drm/amd/-/issues

@RicArch97
Copy link
Contributor Author

You're right, but i though i should leave it here just in case anyone else comes across this issue, to be aware of it at least

@github-actions
Copy link

Issues become stale 90 days after last activity and are closed 14 days after that. If this issue is still relevant bump it or assign it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants