From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108710] Since 4.20 kernel Vega 56 hangs when I surf pages in steam client
Date: Thu, 15 Nov 2018 16:46:05 +0000 [thread overview]
Message-ID: <bug-108710-502-j8TJ4kO9dh@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108710-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2121 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108710
--- Comment #8 from mikhail.v.gavrilov@gmail.com ---
Oh I see again messages (even with proposed patch and Mesa 18.3.0-rc2):
[ 1784.721401] gmc_v9_0_process_interrupt: 1 callbacks suppressed
[ 1784.721406] amdgpu 0000:0b:00.0: [mmhub] VMC page fault (src_id:0 ring:169
vmid:0 pasid:0, for process pid 0 thread pid 0)
[ 1784.721409] amdgpu 0000:0b:00.0: in page starting at address
0x000000010001a000 from 18
[ 1784.721410] amdgpu 0000:0b:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00040152
[ 1795.007321] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma1 timeout,
signaled seq=74616, emitted seq=74621
[ 1795.007324] [drm] GPU recovery disabled.
[ 1795.011389] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout,
signaled seq=233554, emitted seq=233557
[ 1795.011391] [drm] GPU recovery disabled.
$ inxi -bM
System: Host: localhost.localdomain Kernel:
4.20.0-0.rc2.git0.1.local.fc30.x86_64 x86_64 bits: 64 Desktop: Gnome 3.31.2
Distro: Fedora release 30 (Rawhide)
Machine: Type: Desktop Mobo: ASUSTeK model: ROG STRIX X470-I GAMING v: Rev
1.xx serial: <root required>
UEFI: American Megatrends v: 0901 date: 07/23/2018
CPU: 8-Core: AMD Ryzen 7 2700X type: MT MCP speed: 2506 MHz min/max:
2200/4000 MHz
Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Vega 10 XL/XT [Radeon RX
Vega 56/64] driver: amdgpu v: kernel
Display: wayland server: Fedora Project X.org 1.20.3 driver: amdgpu
resolution: 3840x2160~60Hz
OpenGL: renderer: Radeon RX Vega (VEGA10 DRM 3.27.0
4.20.0-0.rc2.git0.1.local.fc30.x86_64 LLVM 7.0.0)
v: 4.5 Mesa 18.3.0-rc2
Network: Device-1: Intel I211 Gigabit Network driver: igb
Device-2: Realtek RTL8822BE 802.11a/b/g/n/ac WiFi adapter driver:
r8822be
Drives: Local Storage: total: 11.36 TiB used: 5.95 TiB (52.4%)
Info: Processes: 443 Uptime: 15m Memory: 31.34 GiB used: 15.94 GiB (50.9%)
Shell: bash inxi: 3.0.27
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2940 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-11-15 16:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-11 11:46 [Bug 108710] Since 4.20 kernel Vega 56 hangs when I surf pages in steam client bugzilla-daemon
2018-11-12 6:00 ` bugzilla-daemon
2018-11-14 3:59 ` bugzilla-daemon
2018-11-14 4:00 ` bugzilla-daemon
2018-11-14 14:52 ` bugzilla-daemon
2018-11-14 19:35 ` bugzilla-daemon
2018-11-14 19:36 ` bugzilla-daemon
2018-11-15 16:43 ` bugzilla-daemon
2018-11-15 16:46 ` bugzilla-daemon [this message]
2018-11-22 3:45 ` bugzilla-daemon
2018-12-02 12:15 ` bugzilla-daemon
2018-12-04 22:04 ` bugzilla-daemon
2018-12-04 22:05 ` bugzilla-daemon
2019-11-19 9:03 ` bugzilla-daemon
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=bug-108710-502-j8TJ4kO9dh@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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