dri-devel January 2016

dri-devel@lists.freedesktop.org

194 participants
1200 discussions

[Bug 83531] New: radeon 6650m cannot boot without radeon.runpm=0
by bugzilla-daemon＠bugzilla.kernel.org 21 Oct '16

21 Oct '16

https://bugzilla.kernel.org/show_bug.cgi?id=83531 Bug ID: 83531 Summary: radeon 6650m cannot boot without radeon.runpm=0 Product: Drivers Version: 2.5 Kernel Version: 3.13-3.15.10 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: kvbevsauce(a)gmail.com Regression: No my laptop is a lenovo z575 with an amd a6-3420 apu and a 6650m for hybrid graphics. I am running fedora 20 with the latest kernel of 3.15.10 ever since I updated to kernel 3.13 sometime ago when hybrid DPM was enabled my laptop will not boot without the above kernel parameter. i have the plymouth boot screen disabled so it shows text based boot. the moment the boot text "fedora 20 hisenbug" shows up, between 3 and 5 seconds later the cursor will stop blinking and the system will be frozen. sometimes more boot text shows up after sometimes not. any help to get dynamic power management working. -- You are receiving this mail because: You are watching the assignee of the bug.

1 2

[Bug 90997] [apitrace] GPU lockup with Dishonored and Gallium Nine
by bugzilla-daemon＠freedesktop.org 29 Sep '16

29 Sep '16

https://bugs.freedesktop.org/show_bug.cgi?id=90997 Bug ID: 90997 Summary: [apitrace] GPU lockup with Dishonored and Gallium Nine Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: commendsarnex(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Hi guys, If I try to play Dishonored with Gallium Nine, I get a gpu lockup. If I play the game with normal wine, there is no issue. This apitrace consistently causes the lockup with Nine, but plays normally with wine. Apitrace: https://idontevenlift.no-ip.org/Dishonored.trace.xz I've attached a run of the apitrace with R600_DEBUG=ps,vs,trace_cs. There is no rlockup file created from the trace_cs, I've searched the whole computer and tried multiple times. I am using LLVM git, Mesa git, and kernel 4.0.5. My GPU is a Radeon HD 7950[Tahiti]. Thanks, sarnex -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 68571] New: GPU lockup on AMD Radeon HD6850 with DPM=1
by bugzilla-daemon＠bugzilla.kernel.org 20 Sep '16

20 Sep '16

https://bugzilla.kernel.org/show_bug.cgi?id=68571 Bug ID: 68571 Summary: GPU lockup on AMD Radeon HD6850 with DPM=1 Product: Drivers Version: 2.5 Kernel Version: 3.13-rc6 / 3.12 Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: kilobug(a)kilobug.org Regression: No Hi, When using dpm with my Radeon HD6850 I get frequent "GPU lockup", with the screen freezing for a few seconds. Sometimes (but not often) the system completely freezes (hard reset required). It happens both during playing OpenGL games and during normal (not GPU intensive) activities, slightly more often during games. I have the issue with both kernel 3.12 (manually enabling the DPM) and 3.13-rc6 (in which it's enabled by default). With DPM disabled, all is working fine. I'm using Mesa 10.0.1, but had the problem with Mesa 9.2.2 on kernel 3.12 too (didn't try Mesa 9.2.2 with kernel 3.13-rc6). I'm using Debian GNU/Linux 64-bits, all packages are from the Debian archive (Mesa 10 and Linux 3.13-rc6 from experimental), but I don't think the problem is Debian-specific so I prefer to report it here. I include a "dmesg" containing two of those lockups. The card itself is a Saphire HD6850 with 1Gb of GDDR5 memory, the CPU is a Intel(R) Core(TM)2 Duo CPU E8400, memory is 2x2Gb of DDR2, the motherboard a ASUSTeK P5E3. Feel free to ask for any additional information, or any test I could perform. Regards, -- You are receiving this mail because: You are watching the assignee of the bug.

1 83

[Bug 91278] Tonga GPU lock/reset fail with Unigine Valley
by bugzilla-daemon＠freedesktop.org 16 Sep '16

16 Sep '16

https://bugs.freedesktop.org/show_bug.cgi?id=91278 Bug ID: 91278 Summary: Tonga GPU lock/reset fail with Unigine Valley Product: DRI Version: XOrg git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: adf.lists(a)gmail.com R9 285 kernel agd5f amdgpu with or without patches from https://bugs.freedesktop.org/show_bug.cgi?id=91141 mesa is agd5f with a few patches from mainline to build with current llvm. ddx is git against older xorg. Simpler games like openarena don't lock. Valley settings ultra, 8xAA, fullscreen 1920x1080. Doesn't show in this log but I've also seen some [drm:amdgpu_gem_va_ioctl [amdgpu]] *ERROR* Couldn't update BO_VA (-35) around the lock/reset on previous tests. -- You are receiving this mail because: You are the assignee for the bug.

1 50

[Bug 91667] Tonga Oopses with uvd + agd5f drm-next-4.3-wip
by bugzilla-daemon＠freedesktop.org 15 Sep '16

15 Sep '16

https://bugs.freedesktop.org/show_bug.cgi?id=91667 Bug ID: 91667 Summary: Tonga Oopses with uvd + agd5f drm-next-4.3-wip Product: DRI Version: DRI git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: adf.lists(a)gmail.com Created attachment 117730 --> https://bugs.freedesktop.org/attachment.cgi?id=117730&action=edit Oops 1 Tried the newly updated agd5f drm-next-4.3-wip today and got some oopses with uvd. These are provoked by repeatedly starting a vid with mpplayer - a known issue, but the change for me on Tonga is getting the Oopses. On other kernels amdgpu/amd-staging/drm-fixes the same test would provoke a ring 9 lock (rarely ring 0) and a failed reset, which at least would leave me alive enough to get a VT. I notice GPU stall detection has now been disabled - but testing various 4.3-wips over some weeks I have never got one anyway. Doing something like this test or running valley would just lock the display and log nothing. SysRq worked OK as it still does - just now I get some logging (though not for the one Unigine Valley lock I just provoked). I am now running mesa/drm mesa/mesa Git Xorg with DRI3 enabled. While testing I noticed the tree got another update - retested and still get the same. The first 2 are from the older tree, the second long as secondary Oopses were provoked. The third is current. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 92544] Tonga fails second resume from mem sleep.
by bugzilla-daemon＠freedesktop.org 15 Sep '16

15 Sep '16

https://bugs.freedesktop.org/show_bug.cgi?id=92544 Bug ID: 92544 Summary: Tonga fails second resume from mem sleep. Product: DRI Version: DRI git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: adf.lists(a)gmail.com R9285 resumes OK after doing echo mem >/sys/power/state, but will not sleep/resume a second time. Tested with a few kernels 4.4 wip 4.3 and 4.2. Nothing is logged in dmesg for 4.4 and 4.3 X bails after some time with - [ 29371.315] (EE) Backtrace: [ 29371.326] (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0x584559] [ 29371.326] (EE) 1: /usr/bin/X (0x400000+0x188459) [0x588459] [ 29371.326] (EE) 2: /lib/libpthread.so.0 (0x7f74cfb8a000+0xf2a0) [0x7f74cfb992a0] [ 29371.326] (EE) 3: /lib/libc.so.6 (0x7f74ce1cb000+0x8a7e7) [0x7f74ce2557e7] [ 29371.327] (EE) 4: /usr/lib/xorg/modules/libglamoregl.so (0x7f74cdd80000+0x196ab) [0x7f74cdd996ab] [ 29371.327] (EE) 5: /usr/bin/X (0x400000+0x111a9f) [0x511a9f] [ 29371.327] (EE) 6: /usr/bin/X (miPaintWindow+0x20c) [0x56802c] [ 29371.327] (EE) 7: /usr/bin/X (miHandleValidateExposures+0x47) [0x57c767] [ 29371.327] (EE) 8: /usr/bin/X (SetRootClip+0x2b5) [0x465905] [ 29371.327] (EE) 9: /usr/bin/X (0x400000+0xb81d2) [0x4b81d2] [ 29371.327] (EE) 10: /usr/bin/X (xf86VTEnter+0x12b) [0x47420b] [ 29371.327] (EE) 11: /usr/bin/X (WakeupHandler+0x6b) [0x43b59b] [ 29371.327] (EE) 12: /usr/bin/X (WaitForSomething+0x1ba) [0x58173a] [ 29371.327] (EE) 13: /usr/bin/X (0x400000+0x3699e) [0x43699e] [ 29371.328] (EE) 14: /usr/bin/X (0x400000+0x3aacb) [0x43aacb] [ 29371.328] (EE) 15: /lib/libc.so.6 (__libc_start_main+0xed) [0x7f74ce1ec36d] [ 29371.328] (EE) 16: /usr/bin/X (0x400000+0x262a1) [0x4262a1] [ 29371.328] (EE) [ 29371.328] (EE) Bus error at address 0x7f74c7003320 [ 29371.328] (EE) Fatal server error: [ 29371.328] (EE) Caught signal 7 (Bus error). Server aborting fbcon is still functional at this point but trying again to startx will hang, last lines of xorg log = [ 10618.330] (II) Loading sub module "dri2" [ 10618.330] (II) LoadModule: "dri2" [ 10618.330] (II) Module "dri2" already built-in On 4.2 I see logged at this point lots of - GPU lockup (current fence id 0x0000000000000147 last fence id 0x0000000000000148 on ring 0) ring 0 stalled for more than 61125msec Waiting with 4.3 or 4.4 does not produce a hung task backtrace. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 69076] New: weston+rs690: triangle flickering
by bugzilla-daemon＠freedesktop.org 09 Sep '16

09 Sep '16

https://bugs.freedesktop.org/show_bug.cgi?id=69076 Priority: medium Bug ID: 69076 Assignee: dri-devel(a)lists.freedesktop.org Summary: weston+rs690: triangle flickering Severity: major Classification: Unclassified OS: Linux (All) Reporter: david.heidelberger(a)ixit.cz Hardware: x86-64 (AMD64) Status: NEW Version: DRI CVS Component: DRM/Radeon Product: DRI How to reproduce: 1.boot 2. kdm (xorg/mesa init) 3. systemctl stop kdm 4. weston // problematic 5. alt-ctrl-bckspace 6. systemctl start kdm 7. desktop (without effects or 3D) 8. logout 9. systemctl stop kdm 10. weston (without described flickering) Screenshots: http://212.158.157.7/20130907_001.jpg (weston start - triangle damaged title) http://212.158.157.7/20130907_002.jpg (first input in terminal) http://212.158.157.7/20130907_003.jpg (terminal filled) On every redraw (input from keyboard), all damaged content (triangles) flicker. Kernel 3.9.1, mesa git, llvm git, weston+wayland git. -- You are receiving this mail because: You are the assignee for the bug.

1 15

[Bug 100871] New: radeon fails to initialize one DisplayPort monitor
by bugzilla-daemon＠bugzilla.kernel.org 06 Sep '16

06 Sep '16

https://bugzilla.kernel.org/show_bug.cgi?id=100871 Bug ID: 100871 Summary: radeon fails to initialize one DisplayPort monitor Product: Drivers Version: 2.5 Kernel Version: v3.19-7478-g796e1c55717e Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: cra(a)wpi.edu Regression: No Ever since Fedora 21 was updated to kernel-4.x, the radeon drm driver fails to initialize one DisplayPort monitor of a multi-monitor setup. Setup is four mini-DP ports on [AMD/ATI] Cedar GL [FirePro 2460], two Dell U2410 monitors connected via DP, and two Dell 2001FP monitors connected via DVI using DP-to-DVI adapters. 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar GL [FirePro 2460] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device 2002 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 29 Region 0: Memory at e0000000 (64-bit, prefetchable) [size=256M] Region 2: Memory at f7e20000 (64-bit, non-prefetchable) [size=128K] Region 4: I/O ports at e000 [size=256] Expansion ROM at f7e00000 [disabled] [size=128K] Capabilities: <access denied> Kernel driver in use: radeon Kernel modules: radeon I did a git bisect between Linux v3.19-6676-g1fa185ebcbce and v3.19-7478-g796e1c55717e and found: # bad: [e55bca26188e45f209597abf986c87cc5a49894a] radeon/audio: enable DP audio git bisect bad e55bca26188e45f209597abf986c87cc5a49894a # first bad commit: [e55bca26188e45f209597abf986c87cc5a49894a] radeon/audio: enable DP audio commit e55bca26188e45f209597abf986c87cc5a49894a Author: Slava Grigorev <slava.grigorev(a)amd.com> Date: Fri Dec 12 17:01:42 2014 -0500 radeon/audio: enable DP audio Reviewed-by: Christian König <christian.koenig(a)amd.com> Signed-off-by: Slava Grigorev <slava.grigorev(a)amd.com> Signed-off-by: Alex Deucher <alexander.deucher(a)amd.com> See also https://bugzilla.redhat.com/show_bug.cgi?id=1232562 -- You are receiving this mail because: You are watching the assignee of the bug.

1 17

[Bug 89746] Mesa and LLVM 3.6+ break opengl for genymotion
by bugzilla-daemon＠freedesktop.org 01 Sep '16

01 Sep '16

https://bugs.freedesktop.org/show_bug.cgi?id=89746 Bug ID: 89746 Summary: Mesa and LLVM 3.6+ break opengl for genymotion Product: Mesa Version: 10.5 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: spupazza(a)hotmail.com QA Contact: dri-devel(a)lists.freedesktop.org I found out LLVM 3.6 + Mesa 10.5 (and newer) might have some sort of regression breaking opengl with radeonsi drivers at least. I use genymotion (android emulator) which relies on virtualbox and make use of opengl acceleration. On 2 different machines with 2 different distros (ubuntu 14.10/15.04 and manjaro 0.9 pre4) I had the same problem: as soon as LLVM 3.6 or 3.7git (the latter with utopic when I added paulo dias ppa) gets installed genymotion stop working (the screen of the vm disappear 1-2 seconds after the machine gets started, and while the screen disappear the machine keeps running in the background). On the terminal I get this error: Port 22468 will be used for OpenGL data connections Unknown TCPCLI command 1003 LLVM ERROR: 'main' label emitted multiple times to assembly file With LLVM 3.5 genymotion (with the same distros and machines) was working just fine. Another proof that the issue is with LLVM is that as to temporarily sort this problem out, I installed the proprietary drivers (fgrlx) and the issue vanished (since proprietary drivers do not make use of LLVM). To reproduce the bug, you need a radeon vga (possibly one using the radeonsi drivers so with GCN architecture) , install vitualbox and genymotion, Setup a virtual device and having installed LLVM 3.6 or newer. Then start the device you created. I reported this bug to the llvm bug-tracker system and they told me to report it to you. -- You are receiving this mail because: You are the assignee for the bug.

1 20

[Bug 77892] New: [RV635] when GPU locks up, reset happens but X is unresponsive except mouse
by bugzilla-daemon＠freedesktop.org 31 Aug '16

31 Aug '16

https://bugs.freedesktop.org/show_bug.cgi?id=77892 Priority: medium Bug ID: 77892 Assignee: dri-devel(a)lists.freedesktop.org Summary: [RV635] when GPU locks up, reset happens but X is unresponsive except mouse Severity: critical Classification: Unclassified OS: Linux (All) Reporter: shawn.starr(a)rogers.com Hardware: x86-64 (AMD64) Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI For a long time now, I don't recall which 3.x broke this but there's been many changes since and now, when the GPU does randomly reset, the display goes blank, X display is restored, but I can only move mouse, cannot interact with X. Can someone point me to some debugging approaches to see if there's some lock being held somewhere thats causing this? I am able to ssh into the laptop so, this seems to point to some sort of lock thats not released. Bisecting radeon drm will be difficult if I have to start from near the beginning of r600g drm support. -- You are receiving this mail because: You are the assignee for the bug.

1 4

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel January 2016