dri-devel September 2014

dri-devel@lists.freedesktop.org

173 participants
1045 discussions

[Bug 73792] New: UVD usage with HD makes X11 quite unstable on Samsung ATIV Book Lite 9 (A4-1450 CPU, KABINI graphics))
by bugzilla-daemon＠freedesktop.org 02 Aug '15

02 Aug '15

https://bugs.freedesktop.org/show_bug.cgi?id=73792 Priority: medium Bug ID: 73792 Assignee: dri-devel(a)lists.freedesktop.org Summary: UVD usage with HD makes X11 quite unstable on Samsung ATIV Book Lite 9 (A4-1450 CPU, KABINI graphics)) Severity: normal Classification: Unclassified OS: All Reporter: rvdb(a)cryptolab.net Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa Created attachment 92387 --> https://bugs.freedesktop.org/attachment.cgi?id=92387&action=edit Dmesg output I have a Smasung ATIV Bool Lite 9 notebook on which I installed a Slackware-current system which works roughly well except suspend and UVD playback. About the later, I run a Kernel 3.12.8 with less-than-a-week-ago git pulls of libdrm, glamor, mesa, mesa-glu and xfree-video-ati. Desktop graphic and compositing work well without glitch and no specific lag. I use libvdpau 0.7 and less-than-a-week-ago git pulls of ffmpeg, x264 and vlc. vlc is configured to use VDPAU and this the UVD chip in the processor. When running SD h264 videos, everything works fine and the CPU usage is low (less than 75% of total W11/KWin/vlc on a GHz core, that's fine with me). I get issues when trying to run HD h264 videos. The CPU usage is still fine, the video starts but after some time, the video hangs, the system becomes unresponsive then the screen turns black, as displaying a black image, it's a bit less black then when the screen is turned of. At this point, either I need to reboot or at some point, the screen seems to turn of, then light up again and resume where I was, though sometimes the video remains black and I have to move the VLC slider to get some images. Then the film can play several seconds then the whole pattern occurs again. And so on until the system does not resume and I must reboot. I've attached dmesg, syslog, glxinfo et vdpauinfo outputs. -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 82886] New: [RadeonSI]GPU Lockup with Linux 3.16 & Mesa Git
by bugzilla-daemon＠freedesktop.org 02 Aug '15

02 Aug '15

https://bugs.freedesktop.org/show_bug.cgi?id=82886 Priority: medium Bug ID: 82886 Assignee: dri-devel(a)lists.freedesktop.org Summary: [RadeonSI]GPU Lockup with Linux 3.16 & Mesa Git Severity: normal Classification: Unclassified OS: Linux (All) Reporter: mmstickman(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa My Radeon HD 7950 GPU locks up and/or Xorg completely crashes whenever the system is graphics card is stressed slightly sometimes (even so much as displaying a web page) -- forcing me to have to reboot the system. I've also been able to trigger it simply by running a game like Tesseract, where it will completely crash Xorg on the main menu. [104725.380514] radeon 0000:01:00.0: ring 0 stalled for more than 10033msec [104725.380524] radeon 0000:01:00.0: GPU lockup (waiting for 0x000000000085f665 last fence id 0x000000000085f65a on ring 0) [104725.921526] radeon 0000:01:00.0: Saved 957 dwords of commands on ring 0. [104725.921574] radeon 0000:01:00.0: GPU softreset: 0x00000068 [104725.921576] radeon 0000:01:00.0: GRBM_STATUS = 0xA0003028 [104725.921578] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000006 [104725.921580] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000006 [104725.921582] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 [104725.921617] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 [104725.921619] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [104725.921621] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00010000 [104725.921623] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000002 [104725.921625] radeon 0000:01:00.0: R_008680_CP_STAT = 0x80010243 [104725.921626] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [104725.921628] radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG = 0x44E84246 [104725.921630] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 [104725.921632] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 [104726.446215] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x0000DDFF [104726.446269] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000140 [104726.447426] radeon 0000:01:00.0: GRBM_STATUS = 0x00003028 [104726.447428] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000006 [104726.447430] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000006 [104726.447432] radeon 0000:01:00.0: SRBM_STATUS = 0x20000AC0 [104726.447467] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 [104726.447469] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [104726.447470] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 [104726.447472] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 [104726.447474] radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000 [104726.447476] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [104726.447478] radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57 [104726.447562] radeon 0000:01:00.0: GPU reset succeeded, trying to resume [104726.496373] [drm] probing gen 2 caps for device 1002:5a16 = 31cd02/0 [104726.496376] [drm] PCIE gen 2 link speeds already enabled [104726.499844] [drm] PCIE GART of 1024M enabled (table at 0x0000000000276000). [104726.499980] radeon 0000:01:00.0: WB enabled [104726.499983] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x00000000c0000c00 and cpu addr 0xffff880420106c00 [104726.499985] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x00000000c0000c04 and cpu addr 0xffff880420106c04 [104726.499987] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x00000000c0000c08 and cpu addr 0xffff880420106c08 [104726.499989] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x00000000c0000c0c and cpu addr 0xffff880420106c0c [104726.499990] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x00000000c0000c10 and cpu addr 0xffff880420106c10 [104726.500376] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc90011cb5a18 [104726.672097] [drm] ring test on 0 succeeded in 1 usecs [104726.672103] [drm] ring test on 1 succeeded in 1 usecs [104726.672107] [drm] ring test on 2 succeeded in 1 usecs [104726.672167] [drm] ring test on 3 succeeded in 2 usecs [104726.672174] [drm] ring test on 4 succeeded in 1 usecs [104726.869612] [drm] ring test on 5 succeeded in 2 usecs [104726.869617] [drm] UVD initialized successfully. [104736.885653] radeon 0000:01:00.0: ring 0 stalled for more than 10000msec [104736.885663] radeon 0000:01:00.0: GPU lockup (waiting for 0x000000000085f66b last fence id 0x000000000085f65a on ring 0) [104736.885689] [drm:r600_ib_test] *ERROR* radeon: fence wait failed (-35). [104736.885696] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on GFX ring (-35). [104736.885700] radeon 0000:01:00.0: ib ring test failed (-35). [104737.072553] radeon 0000:01:00.0: ring 0 stalled for more than 10186msec [104737.072563] radeon 0000:01:00.0: GPU lockup (waiting for 0x000000000085f665 last fence id 0x000000000085f65a on ring 0) [104737.395007] radeon 0000:01:00.0: GPU softreset: 0x00000048 [104737.395010] radeon 0000:01:00.0: GRBM_STATUS = 0xA0003028 [104737.395012] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000006 [104737.395014] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000006 [104737.395016] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 [104737.395051] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 [104737.395053] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [104737.395055] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00010000 [104737.395057] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00400002 [104737.395059] radeon 0000:01:00.0: R_008680_CP_STAT = 0x84010243 [104737.395061] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [104737.395062] radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57 [104737.395065] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 [104737.395067] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 [104737.895759] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x0000DDFF [104737.895829] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100 [104737.896987] radeon 0000:01:00.0: GRBM_STATUS = 0x00003028 [104737.896989] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000006 [104737.896991] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000006 [104737.896993] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 [104737.897027] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 [104737.897067] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [104737.897071] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 [104737.897073] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 [104737.897075] radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000 [104737.897078] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [104737.897080] radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57 [104737.897164] radeon 0000:01:00.0: GPU reset succeeded, trying to resume [104737.914092] [drm] probing gen 2 caps for device 1002:5a16 = 31cd02/0 [104737.914095] [drm] PCIE gen 2 link speeds already enabled [104737.917563] [drm] PCIE GART of 1024M enabled (table at 0x0000000000276000). [104737.917737] radeon 0000:01:00.0: WB enabled [104737.917739] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x00000000c0000c00 and cpu addr 0xffff880420106c00 [104737.917741] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x00000000c0000c04 and cpu addr 0xffff880420106c04 [104737.917743] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x00000000c0000c08 and cpu addr 0xffff880420106c08 [104737.917745] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x00000000c0000c0c and cpu addr 0xffff880420106c0c [104737.917747] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x00000000c0000c10 and cpu addr 0xffff880420106c10 [104737.918131] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc90011cb5a18 [104738.088583] [drm] ring test on 0 succeeded in 1 usecs [104738.088588] [drm] ring test on 1 succeeded in 1 usecs [104738.088592] [drm] ring test on 2 succeeded in 1 usecs [104738.088652] [drm] ring test on 3 succeeded in 2 usecs [104738.088658] [drm] ring test on 4 succeeded in 1 usecs [104738.286093] [drm] ring test on 5 succeeded in 2 usecs [104738.286098] [drm] UVD initialized successfully. [104738.286119] [drm] ib test on ring 0 succeeded in 0 usecs [104738.286137] [drm] ib test on ring 1 succeeded in 0 usecs [104738.286155] [drm] ib test on ring 2 succeeded in 0 usecs [104738.286173] [drm] ib test on ring 3 succeeded in 0 usecs [104738.286190] [drm] ib test on ring 4 succeeded in 0 usecs [104738.457645] [drm:uvd_v1_0_ib_test] *ERROR* radeon: failed to get destroy ib (-22). [104738.457650] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on ring 5 (-22). [104738.457665] [drm:radeon_pm_resume_dpm] *ERROR* radeon: dpm resume failed -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 82887] New: [RadeonSI] Firefox Error in radeonsi_dri.so
by bugzilla-daemon＠freedesktop.org 02 Aug '15

02 Aug '15

https://bugs.freedesktop.org/show_bug.cgi?id=82887 Priority: medium Bug ID: 82887 Assignee: dri-devel(a)lists.freedesktop.org Summary: [RadeonSI] Firefox Error in radeonsi_dri.so Severity: normal Classification: Unclassified OS: All Reporter: mmstickman(a)gmail.com Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa When launching firefox, the following error is displayed in syslog: [10307.788195] traps: firefox[28314] general protection ip:7ff7a77102df sp:7fffed90c970 error:0 in radeonsi_dri.so[7ff7a7448000+768000] -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 82397] New: some GLSL demo render badly on Radeon 7870
by bugzilla-daemon＠freedesktop.org 02 Aug '15

02 Aug '15

https://bugs.freedesktop.org/show_bug.cgi?id=82397 Priority: medium Bug ID: 82397 Assignee: dri-devel(a)lists.freedesktop.org Summary: some GLSL demo render badly on Radeon 7870 Severity: normal Classification: Unclassified OS: All Reporter: nowaker(a)geozone.pl Hardware: Other Status: NEW Version: 10.1 Component: Drivers/Gallium/radeonsi Product: Mesa The demo doesn't render correctly on Radeon 7870 (glamoregl+radeonsi) on Mesa 10.1. I didn't try Mesa 10.2 because of critical bug #65963, so others are welcome to validate on Mesa 10.2. Demo: http://glsl.heroku.com/e#18749.0 Rendered on my friend's blob: http://x.rushbase.net/62726ab9e439bc355ce7a4846ea1cafd67a5b628/glsl.mp4 How it looks for me: http://upload.nowaker.net/nwkr/1407613451_blah.png I will soon check on Mesa 10.2. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 82488] New: Error: couldn't get an RGB, Double-buffered visual
by bugzilla-daemon＠freedesktop.org 02 Aug '15

02 Aug '15

https://bugs.freedesktop.org/show_bug.cgi?id=82488 Priority: medium Bug ID: 82488 Assignee: dri-devel(a)lists.freedesktop.org Summary: Error: couldn't get an RGB, Double-buffered visual Severity: normal Classification: Unclassified OS: All Reporter: 407883775(a)qq.com Hardware: Other Status: NEW Version: 10.2 Component: Drivers/Gallium/radeonsi Product: Mesa My computer arch is sparc. The system is linux 64 bit I am compiler Mesa(10.2.5) and kernel(3.10.0). when i userd commond startx start X, but the glxgears it can not running . message : glxgears: Error: couldn't get an RGB, Double-buffered visual glxinfo : name of display: :0.0 Error: couldn't find RGB GLX visual or fbconfig -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 69196] New: gpu lockup and full crash when starting some games in wine
by bugzilla-daemon＠freedesktop.org 02 Aug '15

02 Aug '15

https://bugs.freedesktop.org/show_bug.cgi?id=69196 Priority: medium Bug ID: 69196 Assignee: dri-devel(a)lists.freedesktop.org Summary: gpu lockup and full crash when starting some games in wine Severity: normal Classification: Unclassified OS: Linux (All) Reporter: maxmusterm(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/DRI/R600 Product: Mesa Created attachment 85587 --> https://bugs.freedesktop.org/attachment.cgi?id=85587&action=edit kernel log from the crash First of I searched the bugs and found some similar looking bugs but none which stroke me as the same bug. lspci tells me my graphics card is 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770 GHz Edition] I always use everything mesa and kernel vanilla from git. My kernel has the version 3.11.0-1-08716-g26b0332-dirty.The mesa checkout is 4 days old. glxinfo tells me Mesa 9.3.0-devel (git-0f6fce1) (if this is relevant) I tested it with hyperz enabled and disabled both time it failed the same way. First the display turns dark (no signal) and then after being responsive for a few seconds the pc crashes completly. If I kill the process in time it doesn't die completly on me. I don't know if this is of any relevance but the firmware for the card was missing and I grabbed the file from here: http://people.freedesktop.org/~agd5f/radeon_ucode/VERDE_smc.bin I'll refrain from parsin anything specific from the kernel log since I don't know which lines are relevant -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 81290] New: [radeonsi] DRI crash
by bugzilla-daemon＠freedesktop.org 02 Aug '15

02 Aug '15

https://bugs.freedesktop.org/show_bug.cgi?id=81290 Priority: medium Bug ID: 81290 Assignee: dri-devel(a)lists.freedesktop.org Summary: [radeonsi] DRI crash Severity: normal Classification: Unclassified OS: All Reporter: RalfPeter.Rohbeck(a)quantum.com Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Created attachment 102697 --> https://bugs.freedesktop.org/attachment.cgi?id=102697&action=edit Xorg.0.log I did a little torture testing with a fully updated Debian sid. This one happened (I think) playing some random video from my disk with VLC but it might also have been been caused by iceweasel with a couple of large images open. xserver-xorg-core 2:1.15.99.904-1 libgl1-mesa-dri 10.2.3-1 vlc 2.1.4-1+b3 iceweasel 30.0-2 Sorry no symbols, I just installed them - will try to reproduce it with symbols. -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 79842] New: Performance drop since mesa 10.1.4
by bugzilla-daemon＠freedesktop.org 02 Aug '15

02 Aug '15

https://bugs.freedesktop.org/show_bug.cgi?id=79842 Priority: medium Bug ID: 79842 Assignee: dri-devel(a)lists.freedesktop.org Summary: Performance drop since mesa 10.1.4 Severity: normal Classification: Unclassified OS: All Reporter: kontakt(a)ib-guder.de Hardware: Other Status: NEW Version: 10.1 Component: Drivers/Gallium/radeonsi Product: Mesa Created attachment 100755 --> https://bugs.freedesktop.org/attachment.cgi?id=100755&action=edit The results from fumark benchmark Hello. I've noticed a performancedrop since mesa 10.1.4 (and also with 10.2.1 now). I ran fumark_benchmark and unigine_valley. I append the results for fumark. I don't know if it is kernel or mesa problem. I use radeonsi. Best regards! Tom -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 32312] New: openvg "lion" demo freezes the system & lockup GPU with r600g
by bugzilla-daemon＠freedesktop.org 02 Aug '15

02 Aug '15

https://bugs.freedesktop.org/show_bug.cgi?id=32312 Summary: openvg "lion" demo freezes the system & lockup GPU with r600g Product: Mesa Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: virtuousfox(a)gmail.com in time of bug #30684 r600g were giving poor performance with "lion" demo (about ~30 fps on my system) but not long ago i've noticed big, x10 time speedup (up to ~350 fps). however, it was not for long: with 783e7caadf945f176cb297b8791769e2855fc9ef revision launching "lion" demo on my system results in 1) video system freeze 2) 100% CPU time usage on all cores and total system freeze up if i not act quickly and not kill demo process via ssh fast if killed in time - all goes back to normal, in exception of launching gles1gears demo right after which results in same behaviour. however, repeated launch of gles1gears results in working demo but with some artefacts. third launch is all ok. i'm pretty sure that regression was introduced in r600g in last 48 ~hours (same revision but with r300g work ok) but i haven't done bisect. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 10

[Bug 83998] New: Oopses on R9270X using UVD since radeon/uvd: use PIPE_USAGE_STAGING for msg&fb buffers
by bugzilla-daemon＠freedesktop.org 30 Jul '15

30 Jul '15

https://bugs.freedesktop.org/show_bug.cgi?id=83998 Priority: medium Bug ID: 83998 Assignee: dri-devel(a)lists.freedesktop.org Summary: Oopses on R9270X using UVD since radeon/uvd: use PIPE_USAGE_STAGING for msg&fb buffers Severity: normal Classification: Unclassified OS: All Reporter: adf.lists(a)gmail.com Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa R9270X Getting rareish Oopses and once oomkiller since - commit 6327b584155d040ae089e65fd6747186bdd9666b Author: Christian König <christian.koenig(a)amd.com> Date: Thu Sep 11 09:50:00 2014 +0200 radeon/uvd: use PIPE_USAGE_STAGING for msg&fb buffers That better matches the actual userspace use case, the kernel will force it to VRAM if the hardware requires it. To trigger this I need to repeatedly start mplayer using uvd - it's takes some time, I ended up making a script to do it for me while AFK. I am 99% sure the above is it - I spent a day and a half trying on the commit before (radeon/video: use the hw to initial clear the buffers) with no crash. The Oopses don't mention radeon or uvd. They will hit as soon as mplayer launches before it renders anything - screen locked, no mouse cursor or vt switch but SysRq works, box is still up in some ways for a while (one time I had music playing for 30s-1min after). One time oomkiller put on its blindfold and ran around killing :-) -- You are receiving this mail because: You are the assignee for the bug.

1 11

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel September 2014