From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107432] Periodic complete system lockup with Vega M and Kernel 4.18-rc6+
Date: Tue, 31 Jul 2018 01:10:56 +0000 [thread overview]
Message-ID: <bug-107432-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 3011 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107432
Bug ID: 107432
Summary: Periodic complete system lockup with Vega M and Kernel
4.18-rc6+
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: rstrube@gmail.com
Created attachment 140902
--> https://bugs.freedesktop.org/attachment.cgi?id=140902&action=edit
System log leading up to hard crash
Description:
Periodically my system will begin to slow down dramatically (the mouse cursor
hitches as I try to move it) and I am unable to interact with anything on the
screen. Eventually the mouse cursor disappears altogether. Trying to switch
to a tty I do get prompted to login, but after entering my credentials nothing
happens. It appears to be a hard lockup. The only solution is to manually
power down my machine and reboot.
This probably happens one or two times a day, normally after starting a new
application.
Hardware:
Dell XPS 15 9575 2 in 1 (Kaby Lake G)
Versions:
Kernel 4.18-rc7
Mesa 18.1.5
Xorg 1.19.6
uCode for Vega M from Linux Firmware git (master) which includes the latest
18.20 uCode from AMD that was recently merged into Linux Firmware
I do have the two sinks available (one for the Intel iGPU and one for the AMD
Vega M), running:
xrandr --listproviders
Lists the following:
Providers: number : 2
Provider 0: id: 0x6f cap: 0x9, Source Output, Sink Offload crtcs: 3 outputs: 7
associated providers: 1 name:modesetting
Provider 1: id: 0x45 cap: 0x6, Sink Output, Source Offload crtcs: 6 outputs: 0
associated providers: 1 name:Unknown AMD Radeon GPU @ pci:0000:01:00.0
And running:
env DRI_PRIME=1 glxinfo | grep "OpenGL renderer"
Lists:
OpenGL renderer string: AMD VEGAM (DRM 3.26.0, 4.18.0-041800rc7-generic, LLVM
6.0.0)
So the Vega M is active and available in my system.
I noticed that this problem started happening after the release of kernel
4.18-rc6 and continues with 4.18-rc7. I've been using 4.18 since rc1 without
issue. This entry in the changelog caught my eye:
Leo Liu (1):
drm/amdgpu: Make sure IB tests flushed after IP resume
Not sure if this is at all related, but the reason I bring this up is because
the errors I see in my logs everytime I encounter this problem are:
kernel: amdgpu 0000:01:00.0: GPU pci config reset
kernel: [drm:amdgpu_device_ip_suspend [amdgpu]] *ERROR* suspend of IP block
<uvd_v6_0> failed -12
Please note that so far I have only encountered this problem when launching
applications that use my Intel iGPU (i.e. I am not setting DRI_PRIME=1).
I've attached my entire log to provide more context.
Thanks!
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4484 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 reply other threads:[~2018-07-31 1:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 1:10 bugzilla-daemon [this message]
2018-07-31 1:31 ` [Bug 107432] Periodic complete system lockup with Vega M and Kernel 4.18-rc6+ bugzilla-daemon
2018-07-31 9:00 ` bugzilla-daemon
2018-07-31 9:09 ` bugzilla-daemon
2018-08-02 5:47 ` bugzilla-daemon
2018-08-02 5:59 ` bugzilla-daemon
2018-08-02 8:16 ` bugzilla-daemon
2018-08-02 17:21 ` bugzilla-daemon
2018-08-02 17:23 ` bugzilla-daemon
2018-08-03 7:32 ` bugzilla-daemon
2018-08-03 17:32 ` bugzilla-daemon
2018-08-06 18:33 ` bugzilla-daemon
2018-08-14 10:52 ` bugzilla-daemon
2018-10-05 20:59 ` bugzilla-daemon
2018-10-09 10:01 ` bugzilla-daemon
2018-10-23 23:24 ` 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-107432-502@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;
as well as URLs for NNTP newsgroup(s).