https://bugs.freedesktop.org/show_bug.cgi?id=93784
Bug ID: 93784 Summary: Hybrid graphics: GPU lockup when running glxgears Product: Mesa Version: 11.0 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel@lists.freedesktop.org Reporter: nioko1337@googlemail.com QA Contact: dri-devel@lists.freedesktop.org
Created attachment 121146 --> https://bugs.freedesktop.org/attachment.cgi?id=121146&action=edit dmesg output
My laptop has the following discrete graphics card (lspci output):
0a:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Sun LE [Radeon HD 8550M / R5 M230] (rev ff)
When running glxgears (or any graphical application) with DRI_PRIME=1, the window appears but it stays just black (also it does not print any FPS in the console).
After starting glxgears the first time, the GPU locks up (see dmesg.txt).
https://bugs.freedesktop.org/show_bug.cgi?id=93784
Nicolas Koch nioko1337@googlemail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nioko1337@googlemail.com
--- Comment #1 from Nicolas Koch nioko1337@googlemail.com --- I just noticed after failing glxgears, the radeonsi driver (or at least a kworker) eats up an entire CPU core of my machine until I reboot.
https://bugs.freedesktop.org/show_bug.cgi?id=93784
--- Comment #2 from Alex Deucher alexdeucher@gmail.com --- Does booting with radeon.runpm=0 on the kernel command line in grub help?
https://bugs.freedesktop.org/show_bug.cgi?id=93784
--- Comment #3 from Nicolas Koch nioko1337@googlemail.com --- No it doesn't :(
Additionally, here is my output of `glxinfo | grep -i renderer`: OpenGL renderer string: Gallium 0.4 on AMD HAINAN (DRM 2.43.0, LLVM 3.7.0)
https://bugs.freedesktop.org/show_bug.cgi?id=93784
--- Comment #4 from Nicolas Koch nioko1337@googlemail.com --- Forgot to mention, of course I ran glxinfo with DRI_PRIME=1
https://bugs.freedesktop.org/show_bug.cgi?id=93784
--- Comment #5 from bartos.petr@gmail.com --- (In reply to Nicolas Koch from comment #4)
Forgot to mention, of course I ran glxinfo with DRI_PRIME=1
Same problem here with ThinkPad L450
05:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Jet XT [Radeon R5 M240] (rev ff)
I found than setting both integrated and discrete gpu to DRI3 allows to run glxgears, however it hard-freezes once any gpu intensive application is run for more than few minutes. Using additional vblank_mode=0 causes this hard-freeze to appear faster. Before hard-freeze there is massive fps drop during which it is possible to kill the application and avoid freeze.
Also using
echo "DDIS" > /sys/kernel/debug/vgaswitcheroo/switch
and restarting X causes black screen (with backlight turned of) but that might be another bug
https://bugs.freedesktop.org/show_bug.cgi?id=93784
--- Comment #6 from bartos.petr@gmail.com --- I'm on Mesa 11.1.0 (git-525f3c2). Happens with kernel 4.3.x and 4.4.x on Fedora 23
https://bugs.freedesktop.org/show_bug.cgi?id=93784
--- Comment #7 from Nicolas Koch nioko1337@googlemail.com --- I could fix this problem by enabling DRI3 for the intel driver like this:
cat /etc/X11/xorg.conf.d/020-intel.conf
Section "Device" Identifier "Intel Graphics" Driver "intel" Option "TearFree" "true" Option "DRI" "3" EndSection
No more GPU hangups and other funny stuff happening, at least glxgears works now (no more black screen).
It would be nice, if someone found out why this is behaving strange when only DRI2 is enabled, though.
https://bugs.freedesktop.org/show_bug.cgi?id=93784
GitLab Migration User gitlab-migration@fdo.invalid changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |MOVED
--- Comment #8 from GitLab Migration User gitlab-migration@fdo.invalid --- -- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1228.
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠freedesktop.org