From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] AMDGPU kernel module crashes in Linux 5.18, when watching a YouTube video in Firefox
Date: Sun, 25 Sep 2022 04:14:42 +0200 [thread overview]
Message-ID: <20220925021442.-cGCminkZ8YSq0j4zl4lDuq0anuBYPBzE0KlzmAgmEY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37439@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 3613 bytes --]
Closed issue by RicArch97 on void-packages repository
https://github.com/void-linux/void-packages/issues/37439
Description:
<!-- Don't request update of package. We have a script for that. https://repo-default.voidlinux.org/void-updates/void-updates.txt. However, a quality pull request may help. -->
### 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.
prev parent reply other threads:[~2022-09-25 2:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 20:27 [ISSUE] " RicArch97
2022-06-09 0:01 ` MPC7500
2022-06-09 1:27 ` RicArch97
2022-09-10 2:14 ` github-actions
2022-09-25 2:14 ` github-actions [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220925021442.-cGCminkZ8YSq0j4zl4lDuq0anuBYPBzE0KlzmAgmEY@z \
--to=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).