dri-devel March 2015

dri-devel@lists.freedesktop.org

196 participants
1117 discussions

[Bug 84519] New: GPU hang xbmc tvheadend uvd
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=84519 Priority: medium Bug ID: 84519 Assignee: dri-devel(a)lists.freedesktop.org Summary: GPU hang xbmc tvheadend uvd Severity: normal Classification: Unclassified OS: All Reporter: serafean(a)gmail.com Hardware: Other Status: NEW Version: unspecified Component: Drivers/Gallium/r600 Product: Mesa Created attachment 107140 --> https://bugs.freedesktop.org/attachment.cgi?id=107140&action=edit dmesg from around the hang When playing back a live TV stream using xbmc and tvheadend I immediately get a GPU hang. relevant dmesg attached. 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7480D] Anything more I could do, please tell me. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 84292] New: Radeonsi crashes in Tropico 5 with Radeon HD 5xxx
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=84292 Priority: medium Bug ID: 84292 Assignee: dri-devel(a)lists.freedesktop.org Summary: Radeonsi crashes in Tropico 5 with Radeon HD 5xxx Severity: normal Classification: Unclassified OS: Linux (All) Reporter: armandos.styl(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: 10.2 Component: Drivers/Gallium/radeonsi Product: Mesa Created attachment 106807 --> https://bugs.freedesktop.org/attachment.cgi?id=106807&action=edit System information text doc Two users (one of them myself) have experienced trouble with Tropico 5. "Last patch made it run the menu but starting the new game renders the system unusable and requires a reboot :( Last message in the system log is this: kernel: radeon 0000:01:00.0: ring 0 stalled for more than 10000msec GPU is Mobility Radeon HD 5730 with mesa 10.2.8 drivers on kernel 3.16.3." (steam fora) And me: "Tried both Tropico 5 main and linuxbeta, on intel i7 CPU 930 and AMD Radeon HD 5870. Had to work around the black screen issue but, upon reaching the main menu and clicking on New Campaign or Tutorial, the screen would flash and glitch and sound would repeat. After that, my monitor would turn on and off and display Refresh rate out of range (approx. 43.1 KHz - 41 Hz) and the system would need a cold reboot. Tried to run it with both the updated kernel and without, realising I had never let it run for more than 30 seconds after the freeze. Result was that the fans inside my computer began spinning like crazy, the system restarted with 4-5 ping sounds and the fans still running full-speed. Only after a cold shutdown did the fans stop. So I suspect this process almost fried my CPU or GPU." I am running updated Mesa and Gallium through oibaf ppa. -- You are receiving this mail because: You are the assignee for the bug.

1 16

[Bug 83422] New: i was opening systemsettings, chose workspace design and the default look and feel screen just stays black when resizing the window or chosing another option on the left panel, it crashes
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=83422 Priority: medium Bug ID: 83422 Assignee: dri-devel(a)lists.freedesktop.org Summary: i was opening systemsettings, chose workspace design and the default look and feel screen just stays black when resizing the window or chosing another option on the left panel, it crashes Severity: normal Classification: Unclassified OS: Linux (All) Reporter: simonlang1984(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: unspecified Component: Drivers/Gallium/r600 Product: Mesa Created attachment 105657 --> https://bugs.freedesktop.org/attachment.cgi?id=105657&action=edit logfile i was opening systemsettings, chose workspace design and the default look and feel screen just stays black when resizing the window or chosing another option on the left panel, it crashes. could not reproduce the crash, but the black window thing remains. Reproducible: Always Steps to Reproduce: 1. open system settings 2. chose workspace design 3. see the problem Actual Results: i was opening systemsettings, chose workspace design and the default look and feel screen just stays black when resizing the window or chosing another option on the left panel, it crashes. could not reproduce the crash, but the black window thing remains. Expected Results: should not crash and should show the contents. http://s18.postimg.org/a460edqah/Bildschirmfoto1.png -- You are receiving this mail because: You are the assignee for the bug.

1 20

[Bug 83319] New: [r600g] GPU lockup in gsraytrace (Mesa-demo-8.2.0) - RV730
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=83319 Priority: medium Bug ID: 83319 Assignee: dri-devel(a)lists.freedesktop.org Summary: [r600g] GPU lockup in gsraytrace (Mesa-demo-8.2.0) - RV730 Severity: critical Classification: Unclassified OS: Linux (All) Reporter: Dieter(a)nuetzel-hh.de Hardware: x86 (IA32) Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa Created attachment 105518 --> https://bugs.freedesktop.org/attachment.cgi?id=105518&action=edit dmesg-3.16.1-7.g90bc0f1-desktop-gsraytrace.log GL_RENDERER = Gallium 0.4 on AMD RV730 GL_VERSION = 3.0 Mesa 10.4.0-devel (git-5598458) GL_VENDOR = X.Org GShader thing? mesa-demos/glsl> ./vsraytrace ATTENTION: default value of option vblank_mode overridden by environment. GL_RENDERER = Gallium 0.4 on AMD RV730 47.590482 FPS (238 frames in 5.001000 seconds) 62.325210 FPS (312 frames in 5.006000 seconds) 65.407555 FPS (329 frames in 5.030000 seconds) mesa-demos/glsl> ./fsraytrace ATTENTION: default value of option vblank_mode overridden by environment. GL_RENDERER = Gallium 0.4 on AMD RV730 503.000000 FPS (2515 frames in 5.000000 seconds) 626.800000 FPS (3134 frames in 5.000000 seconds) 577.600000 FPS (2888 frames in 5.000000 seconds) mesa-demos/glsl> ./gsraytrace ATTENTION: default value of option vblank_mode overridden by environment. GL_RENDERER = Gallium 0.4 on AMD RV730 ESC = exit demo left mouse + drag = rotate camera 0.044960 FPS (1 frames in 22.242000 seconds) 0.047201 FPS (1 frames in 21.186000 seconds) ESC / CNTRL+C (several/hundred times) => 2 times switching between blank (black) full screen (console) and desktop (KDE 4.13.3) before the system comes back NO, no LLVM this time... (Michel?) Maybe related: bug 76394 -- You are receiving this mail because: You are the assignee for the bug.

1 18

[Bug 83285] New: GPU Lockup using wine d3d
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=83285 Priority: medium Bug ID: 83285 Assignee: dri-devel(a)lists.freedesktop.org Summary: GPU Lockup using wine d3d Severity: blocker Classification: Unclassified OS: Linux (All) Reporter: josepwnz(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa Created attachment 105479 --> https://bugs.freedesktop.org/attachment.cgi?id=105479&action=edit Kern.log Hi, im getting some gpu resets (sometimes even reboot computer) playing some games (League of legends & starcraft2) using wine (patched for d3d) I have to say it only happens using certain settings, for example using "character quality" option from league of legends setting to very low/low game loads normally. if i set to medium or higher then causes GPU reset loops untill game crash/computer completly freeze(need reboot)/or if i'm enough faster, kill process from tty. If you need, i can try to make a movie showing problem Linux mint 17 Kernel 3.16.0 OpenGL ES 3.0 Mesa 10.4.0-devel (git-932b0ef 2014-08-30 trusty-oibaf-ppa) ATI 6670 -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 83274] New: XCom Enemy Unknown segfault at src/gallium/drivers/radeon/r600_texture.c:602
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=83274 Priority: medium Bug ID: 83274 Assignee: dri-devel(a)lists.freedesktop.org Summary: XCom Enemy Unknown segfault at src/gallium/drivers/radeon/r600_texture.c:602 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: jzinkweg(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: 10.2 Component: Drivers/Gallium/r600 Product: Mesa Created attachment 105468 --> https://bugs.freedesktop.org/attachment.cgi?id=105468&action=edit GDB backtrace XCOM: Enemy Unknown segfaults frequently during gameplay. I have not been able to reliably reproduce a secenario, but playing 10-20 minutes usually ends in a crash to desktop, so if extra data is needed it is not that difficult for me to provide... I've attached GDB backtraces (simple and full) which suggest the crash is located in src/gallium/drivers/radeon/r600_texture.c. Running Debian Jessie 64 bit, with libgl1-mesa-dri 10.2.5 on an 512 MB ATI Mobility RADEON HD 4570 graphics card. -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 83022] New: memory leak
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=83022 Priority: medium Bug ID: 83022 Assignee: dri-devel(a)lists.freedesktop.org Summary: memory leak Severity: normal Classification: Unclassified OS: All Reporter: pavol(a)klacansky.com Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa I am using VisIt to produce movies, however it seems that each state file leak memory and I cannot process all of them. I have tested it on nvidia workstation with proprietary drivers without problem. Can you point me how to identify if it is a driver's problem or VisIt's? -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 83012] New: horrible performance with vblank_mode=1 which is the default
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=83012 Priority: medium Bug ID: 83012 Assignee: dri-devel(a)lists.freedesktop.org Summary: horrible performance with vblank_mode=1 which is the default Severity: normal Classification: Unclassified OS: All Reporter: aaalmosss(a)gmail.com Hardware: Other Status: NEW Version: unspecified Component: Drivers/Gallium/r600 Product: Mesa For example, Unigine Tropics benchmark gives 20fps, but with vblank_mode=0 it's 54fps. Games that don't turn off vsync by themselves suffer from this as well. -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 82919] New: Screen flickers when playing video.
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=82919 Priority: medium Bug ID: 82919 Assignee: dri-devel(a)lists.freedesktop.org Summary: Screen flickers when playing video. Severity: normal Classification: Unclassified OS: All Reporter: barz621(a)gmail.com Hardware: Other Status: NEW Version: 10.2 Component: Drivers/Gallium/r600 Product: Mesa Created attachment 105059 --> https://bugs.freedesktop.org/attachment.cgi?id=105059&action=edit Xorg.0.log With HW acceleration enabled on the r600 driver using gstreamer gst-vaapi the screen flickers when the uvd changes its power state. This happens when you play a video on firefox (youtube, vimeo vine etc.) or with vlc. It flickers upon starting/ stopping and then a few more times. The monitor is connected with DP in case it matters. glxinfo: glxinfo | grep -i opengl OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD BARTS OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.2.5 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.0 Mesa 10.2.5 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 10.2.5 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.0 OpenGL ES profile extensions: This is what happens when you start youtube play one video and stop it. journal: journalctl -f -- Logs begin at Mon 2013-04-22 10:20:09 EEST. -- Aug 21 22:41:16 mainland kernel: status: c Aug 21 22:41:16 mainland kernel: switching to power state: Aug 21 22:41:16 mainland kernel: ui class: performance Aug 21 22:41:16 mainland kernel: internal class: none Aug 21 22:41:16 mainland kernel: caps: Aug 21 22:41:16 mainland kernel: uvd vclk: 0 dclk: 0 Aug 21 22:41:16 mainland kernel: power level 0 sclk: 10000 mclk: 15000 vddc: 950 vddci: 950 Aug 21 22:41:16 mainland kernel: power level 1 sclk: 60000 mclk: 100000 vddc: 1100 vddci: 1100 Aug 21 22:41:16 mainland kernel: power level 2 sclk: 77500 mclk: 100000 vddc: 1150 vddci: 1100 Aug 21 22:41:16 mainland kernel: status: r Aug 21 22:42:42 mainland kernel: switching from power state: Aug 21 22:42:42 mainland kernel: ui class: performance Aug 21 22:42:42 mainland kernel: internal class: none Aug 21 22:42:42 mainland kernel: caps: Aug 21 22:42:42 mainland kernel: uvd vclk: 0 dclk: 0 Aug 21 22:42:42 mainland kernel: power level 0 sclk: 10000 mclk: 15000 vddc: 950 vddci: 950 Aug 21 22:42:42 mainland kernel: power level 1 sclk: 60000 mclk: 100000 vddc: 1100 vddci: 1100 Aug 21 22:42:42 mainland kernel: power level 2 sclk: 77500 mclk: 100000 vddc: 1150 vddci: 1100 Aug 21 22:42:42 mainland kernel: status: c Aug 21 22:42:42 mainland kernel: switching to power state: Aug 21 22:42:42 mainland kernel: ui class: none Aug 21 22:42:42 mainland kernel: internal class: uvd Aug 21 22:42:42 mainland kernel: caps: video Aug 21 22:42:42 mainland kernel: uvd vclk: 54000 dclk: 40000 Aug 21 22:42:42 mainland kernel: power level 0 sclk: 30000 mclk: 100000 vddc: 950 vddci: 1100 Aug 21 22:42:42 mainland kernel: power level 1 sclk: 30000 mclk: 100000 vddc: 950 vddci: 1100 Aug 21 22:42:42 mainland kernel: power level 2 sclk: 77500 mclk: 100000 vddc: 1150 vddci: 1100 Aug 21 22:42:42 mainland kernel: status: r Aug 21 22:42:53 mainland kernel: switching from power state: Aug 21 22:42:53 mainland kernel: ui class: none Aug 21 22:42:53 mainland kernel: internal class: uvd Aug 21 22:42:53 mainland kernel: caps: video Aug 21 22:42:53 mainland kernel: uvd vclk: 54000 dclk: 40000 Aug 21 22:42:53 mainland kernel: power level 0 sclk: 30000 mclk: 100000 vddc: 950 vddci: 1100 Aug 21 22:42:53 mainland kernel: power level 1 sclk: 30000 mclk: 100000 vddc: 950 vddci: 1100 Aug 21 22:42:53 mainland kernel: power level 2 sclk: 77500 mclk: 100000 vddc: 1150 vddci: 1100 Aug 21 22:42:53 mainland kernel: status: c Aug 21 22:42:53 mainland kernel: switching to power state: Aug 21 22:42:53 mainland kernel: ui class: performance Aug 21 22:42:53 mainland kernel: internal class: none Aug 21 22:42:53 mainland kernel: caps: Aug 21 22:42:53 mainland kernel: uvd vclk: 0 dclk: 0 Aug 21 22:42:53 mainland kernel: power level 0 sclk: 10000 mclk: 15000 vddc: 950 vddci: 950 Aug 21 22:42:53 mainland kernel: power level 1 sclk: 60000 mclk: 100000 vddc: 1100 vddci: 1100 Aug 21 22:42:53 mainland kernel: power level 2 sclk: 77500 mclk: 100000 vddc: 1150 vddci: 1100 Aug 21 22:42:53 mainland kernel: status: r Aug 21 22:43:00 mainland kernel: switching from power state: Aug 21 22:43:00 mainland kernel: ui class: performance Aug 21 22:43:00 mainland kernel: internal class: none Aug 21 22:43:00 mainland kernel: caps: Aug 21 22:43:00 mainland kernel: uvd vclk: 0 dclk: 0 Aug 21 22:43:00 mainland kernel: power level 0 sclk: 10000 mclk: 15000 vddc: 950 vddci: 950 Aug 21 22:43:00 mainland kernel: power level 1 sclk: 60000 mclk: 100000 vddc: 1100 vddci: 1100 Aug 21 22:43:00 mainland kernel: power level 2 sclk: 77500 mclk: 100000 vddc: 1150 vddci: 1100 Aug 21 22:43:00 mainland kernel: status: c Aug 21 22:43:00 mainland kernel: switching to power state: Aug 21 22:43:00 mainland kernel: ui class: none Aug 21 22:43:00 mainland kernel: internal class: uvd Aug 21 22:43:00 mainland kernel: caps: video Aug 21 22:43:00 mainland kernel: uvd vclk: 54000 dclk: 40000 Aug 21 22:43:00 mainland kernel: power level 0 sclk: 30000 mclk: 100000 vddc: 950 vddci: 1100 Aug 21 22:43:00 mainland kernel: power level 1 sclk: 30000 mclk: 100000 vddc: 950 vddci: 1100 Aug 21 22:43:00 mainland kernel: power level 2 sclk: 77500 mclk: 100000 vddc: 1150 vddci: 1100 Aug 21 22:43:00 mainland kernel: status: r Aug 21 22:43:02 mainland kernel: switching from power state: Aug 21 22:43:02 mainland kernel: ui class: none Aug 21 22:43:02 mainland kernel: internal class: uvd Aug 21 22:43:02 mainland kernel: caps: video Aug 21 22:43:02 mainland kernel: uvd vclk: 54000 dclk: 40000 Aug 21 22:43:02 mainland kernel: power level 0 sclk: 30000 mclk: 100000 vddc: 950 vddci: 1100 Aug 21 22:43:02 mainland kernel: power level 1 sclk: 30000 mclk: 100000 vddc: 950 vddci: 1100 Aug 21 22:43:02 mainland kernel: power level 2 sclk: 77500 mclk: 100000 vddc: 1150 vddci: 1100 Aug 21 22:43:02 mainland kernel: status: c Aug 21 22:43:02 mainland kernel: switching to power state: Aug 21 22:43:02 mainland kernel: ui class: performance Aug 21 22:43:02 mainland kernel: internal class: none Aug 21 22:43:02 mainland kernel: caps: Aug 21 22:43:02 mainland kernel: uvd vclk: 0 dclk: 0 Aug 21 22:43:02 mainland kernel: power level 0 sclk: 10000 mclk: 15000 vddc: 950 vddci: 950 Aug 21 22:43:02 mainland kernel: power level 1 sclk: 60000 mclk: 100000 vddc: 1100 vddci: 1100 Aug 21 22:43:02 mainland kernel: power level 2 sclk: 77500 mclk: 100000 vddc: 1150 vddci: 1100 Aug 21 22:43:02 mainland kernel: status: r -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 82791] New: GPU lock when using "Death Dance" in Tales of Maj'Eyal
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=82791 Priority: medium Bug ID: 82791 Assignee: dri-devel(a)lists.freedesktop.org Summary: GPU lock when using "Death Dance" in Tales of Maj'Eyal Severity: major Classification: Unclassified OS: Linux (All) Reporter: bugzilla.20.kamdrimar(a)spamgourmet.com Hardware: x86-64 (AMD64) Status: NEW Version: 10.2 Component: Drivers/Gallium/r600 Product: Mesa Created attachment 104850 --> https://bugs.freedesktop.org/attachment.cgi?id=104850&action=edit dmesg showing GPU lock Symptoms: GPU locks and attempts to recover (screen goes black) and locks again upon recovery. Any further attempt to use X11 (even restarting it) locks the GPU, and system must be rebooted to use X11 again. Steps to reproduce: 1) Download Tales of Maj'Eyal 1.2.3 full for Linux 64-bit - http://te4.org/download 2) Extract the game to a convenient location. 3) Run the t-engine binary from the base game directory, then exit the game. 4) Download a gzip of a character I created - - and extract to: ~/.t-engine/4.0/tome/save/ 5) Run t-engine again, load the save game "Pennies". 6) Use the ability "Death Dance" in game. (If for some reason my save won't work, you need to create a Berserker class character in-game, get it to level 8 and 28 strength, and unlock Death Dance.) Workarounds attempted: use different window manager/DE - Failed, bug is reproducible in KDE4, KDE5, Awesome, and Enlightenment 18 pass radeon.audio=0 to kernel command line at boot - Failed, no effect pass radeon.dpm=0 to kernel - Failed, screen now stays black after GPU lock Note: this bug may be related to other GPU locks I've been experiencing with Mesa 10.2.x, but this is the only repeatable instance of it so far. -- You are receiving this mail because: You are the assignee for the bug.

1 6

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel March 2015