dri-devel June 2015

dri-devel@lists.freedesktop.org

188 participants
1140 discussions

[Bug 38364] New: Ignoring invalid EDID block 1 do entire edid is invalid and not just block 1
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=38364 Summary: Ignoring invalid EDID block 1 do entire edid is invalid and not just block 1 Product: DRI Version: XOrg CVS Platform: x86-64 (AMD64) OS/Version: All Status: NEW Severity: normal Priority: medium Component: General AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: zaverel(a)free.fr Hello , All is fine except i can't change resolution on my second monitor vga ,tv in fact, (reported as DVI-I-2 ) anymore with my 9400gt. Now , i'm on : linux-2.6.39-gentoo-r1 xorg-server-1.10.2 xf86-video-nouveau-0.0.16_pre20110323 libdrm-2.4.25 Errors in dmesg are: nouveau 0000:02:00.0: DVI-I-2: Ignoring invalid EDID block 1. [drm:drm_edid_block_valid] *ERROR* Raw EDID: <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ whatever i valid with xrandr is not really do on my tv although xrandr say it's good , my tv always report 1202x670 50hz I tried with and without xorg.conf My last kernel working is linux-2.6.36-gentoo-r6. If, i tweak drm_edid.c from kernel-2.6.39-gentoo-r1 like this: --- drm_edid.c 2011-06-10 22:37:36.605848000 +0200 +++ linux/drivers/gpu/drm/drm_edid.c 2011-06-13 13:04:43.136786102 +0200 @@ -292,7 +292,7 @@ block + (valid_extensions + 1) * EDID_LENGTH, j, EDID_LENGTH)) goto out; - if (drm_edid_block_valid(block + (valid_extensions + 1) * EDID_LENGTH)) { + if (drm_edid_block_valid(block + (valid_extensions + 0) * EDID_LENGTH)) { valid_extensions++; break; } that work good like before but i'm not sure that is safe. More info in http://lists.freedesktop.org/archives/nouveau/2011-June/008548.html I can post logs here too , just tell me. See you -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 1

[Bug 91009] [radeonsi, R9 270X] Random system lockup when start to play H.264 video in mplayer with VDPAU
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=91009 Bug ID: 91009 Summary: [radeonsi, R9 270X] Random system lockup when start to play H.264 video in mplayer with VDPAU Product: Mesa Version: 10.6 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: yurikoles(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 116559 --> https://bugs.freedesktop.org/attachment.cgi?id=116559&action=edit dmesg As I can count, it's happens about every 10-15 start of VDPAU decoding, kernel traces vary. -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 90668] vertical stripes/glitches on secondary screen r9 280x
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=90668 Bug ID: 90668 Summary: vertical stripes/glitches on secondary screen r9 280x Product: Mesa Version: 10.5 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: net(a)ianni.de QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 116062 --> https://bugs.freedesktop.org/attachment.cgi?id=116062&action=edit photo This is my first bug report here, so I hope i got everything right. My system is Fedora 22. My GPU is a Sapphire 280x OC. My secondary screen, connected via dvi, is showing strange vertical stripes, ca 3 cm wide. It seems like someone cut the actual image in stripes and glued it together slightly overlapping with flickering borders. If I take a screenshot everything looks normal (as it actually should look). If I use it as the only screen, the stripes are also there. (Is it a problem with the screen or the dvi connection?) I tried the second dvi connection with the same result. Using Windows, the screen has no issues. output of xrandr: http://paste.fedoraproject.org/225798/67516614 output of glxinfo: http://paste.fedoraproject.org/225799/43267525 As mentioned, screenshots show the image as it should be, I had to take a photo of the screen. I used a text file with the repeated series if numbers from 1 to 7.So one can see where the overlapping I mentioned happens (also in the spacing of the buttons, missing glyphs etc..) for example, after the first 1-7 sequence, the 1 and 2 are left out and so on. I am sorry but I found no better way to show it, except making a video If you need more information please let me know. -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 90515] memory use increase with vdpau
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=90515 Bug ID: 90515 Summary: memory use increase with vdpau Product: Mesa Version: 10.4 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: fabrice(a)bellet.info QA Contact: dri-devel(a)lists.freedesktop.org I noticed a constant increase of rss memory while playing a video using vdpau + radeonsi, caused by X events accumulating in read_packet (c=0x8275a0) at xcb_in.c:333, and never flushed, and corresponding to this backtrace : Breakpoint 6, read_packet (c=0x8275a0) at xcb_in.c:333 (gdb) bt #0 0x00007fffec99b281 in read_packet (c=0x8275a0) at xcb_in.c:333 #1 0x00007fffec99c742 in _xcb_in_read (c=0x8275a0) at xcb_in.c:936 #2 0x00007fffec999ae4 in _xcb_conn_wait (c=0x8275a0, cond=0x7fffe1636960, vector=0x0, count=0x0) at xcb_conn.c:495 #3 0x00007fffec99b78b in wait_for_reply (c=0x8275a0, request=207, e=0x0) at xcb_in.c:493 #4 0x00007fffec99b8a4 in xcb_wait_for_reply (c=0x8275a0, request=207, e=0x0) at xcb_in.c:523 #5 0x00007fffea7c5ac8 in xcb_dri2_swap_buffers_reply (c=0x8275a0, cookie=..., e=0x0) at dri2.c:893 #6 0x00007fffe6a982f0 in vl_dri2_get_flush_reply (scrn=0x83cab0) at ../../../../src/gallium/auxiliary/vl/vl_winsys_dri.c:103 #7 0x00007fffe6a984b4 in vl_dri2_destroy_drawable (scrn=0x83cab0) at ../../../../src/gallium/auxiliary/vl/vl_winsys_dri.c:146 #8 0x00007fffe6a98524 in vl_dri2_set_drawable (scrn=0x83cab0, drawable=41943041) at ../../../../src/gallium/auxiliary/vl/vl_winsys_dri.c:162 #9 0x00007fffe6a988ed in vl_screen_get_timestamp (vscreen=0x83cab0, drawable=41943041) at ../../../../src/gallium/auxiliary/vl/vl_winsys_dri.c:269 #10 0x00007fffe6aa193d in vlVdpPresentationQueueGetTime (presentation_queue=11, current_time=0x7fffe1636b80) at presentation.c:189 #11 0x00007fffe6aa1f04 in vlVdpPresentationQueueBlockUntilSurfaceIdle (presentation_queue=11, surface=13, first_presentation_time=0x7fffe1636b80) at presentation.c:335 #12 0x00007fffe719fb51 in put_surface () at /usr/lib64/dri/radeonsi_drv_video.so #13 0x00007fffe719fdcf in vdpau_PutSurface () at /usr/lib64/dri/radeonsi_drv_video.so #14 0x00007fffed5ead37 in gst_vaapi_texture_glx_put_surface (flags=0, crop_rect=0x7fffe1636d20, surface=0x7fffdc08fd90, base_texture=0x7fffcc1385a0) at gstvaapitexture_glx.c:315 #15 0x00007fffed5ead37 in gst_vaapi_texture_glx_put_surface (texture=0x7fffcc1385a0, surface=0x7fffdc08fd90, crop_rect=0x7fffe1636d20, flags=0) at gstvaapitexture_glx.c:378 #16 0x00007fffedf6e1b1 in gst_vaapi_texture_put_surface (texture=0x7fffcc1385a0, surface=0x7fffdc08fd90, crop_rect=<optimized out>, flags=<optimized out>) at gstvaapitexture.c:332 #17 0x00007fffe99118ec in _do_upload_with_meta (context=<optimized out>, upload=0x7fffdc029600 [GstGLUpload]) at gstglupload.c:357 #18 0x00007fffe9913198 in _run_message_sync (message=0x7fffe1e37840) at gstglwindow.c:353 #19 0x00007fffe9917a82 in _run_message (message=0x7fffd8001b60) at gstglwindow_x11.c:598 #20 0x00007ffff73857fb in g_main_context_dispatch (context=0x7fffcc010980) at gmain.c:3111 #21 0x00007ffff73857fb in g_main_context_dispatch (context=context@entry=0x7fffcc010980) at gmain.c:3710 #22 0x00007ffff7385b98 in g_main_context_iterate (context=0x7fffcc010980, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3781 #23 0x00007ffff7385ec2 in g_main_loop_run (loop=0x7fffcc010b70) at gmain.c:3975 #24 0x00007fffe9901cf7 in gst_gl_context_create_thread (context=0x7fffdc023260 [GstGLContextGLX]) at gstglcontext.c:959 #25 0x00007ffff73ac3d5 in g_thread_proxy (data=0x7fffdc0234a0) at gthread.c:764 #26 0x00007ffff6f2352a in start_thread (arg=0x7fffe1637700) at pthread_create.c:310 #27 0x00007ffff6c5f22d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 The commands generating this case is : # ln -s vdpau_drv_video.so /usr/lib64/dri/radeonsi_drv_video.so $ export VDPAU_DRIVER=radeonsi $ wget http://samples.mplayerhq.hu/MPEG-4/NeroRecodeSample-MP4/NeroRecodeSample.mp4 $ gst-launch-1.0 filesrc location=NeroRecodeSample.mp4 ! qtdemux ! mpeg4videoparse ! vaapidecode ! videoconvert ! glimagesink The two malloc() occuring in libxcb in read_packet() are sufficient to make gst-launch-1.0 memory use grow out of control. It seems to occur because vl_dri2_set_drawable() is called alternatively with two different drawables, each call destroying the previous drawable. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 90217] Counter Strike Global Offensive: GPU fault after a while
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=90217 Bug ID: 90217 Summary: Counter Strike Global Offensive: GPU fault after a while Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: haagch(a)frickel.club QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 115406 --> https://bugs.freedesktop.org/attachment.cgi?id=115406&action=edit dmesg 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Wimbledon XT [Radeon HD 7970M] (rev ff) mesa git, llvm recent revision, with PRIME. linux 4.1rc1, but with 4.0 it was the same. Counter Strike GO seems to be problematic anyway. Even with 1366x768 and settings on low I get bad performance drops, see video: https://www.youtube.com/watch?v=HVDZowUGlSc There is flickering all over the place. At the end of the video there is one of the GPU hangs: perf interrupt took too long (4996 > 4960), lowering kernel.perf_event_max_sample_rate to 25200 radeon 0000:01:00.0: GPU fault detected: 146 0x08e2c804 radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0000EBC7 radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x020C8004 VM fault (0x04, vmid 1) at page 60359, read from TC (200) radeon 0000:01:00.0: ring 0 stalled for more than 10490msec radeon 0000:01:00.0: GPU lockup (current fence id 0x00000000008a0d3c last fence id 0x00000000008a0d57 on ring 0) radeon 0000:01:00.0: ring 0 stalled for more than 10990msec radeon 0000:01:00.0: GPU lockup (current fence id 0x00000000008a0d3c last fence id 0x00000000008a0d57 on ring 0) radeon 0000:01:00.0: ring 0 stalled for more than 11490msec radeon 0000:01:00.0: GPU lockup (current fence id 0x00000000008a0d3c last fence id 0x00000000008a0d57 on ring 0) and then only further stalled messages It happens after 15-60 minutes or something like that. -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 90182] Qt Applications won't start on the dedicated GPU (SIGABRT)
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=90182 Bug ID: 90182 Summary: Qt Applications won't start on the dedicated GPU (SIGABRT) Product: Mesa Version: 10.5 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: paul(a)konecny.at QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 115334 --> https://bugs.freedesktop.org/attachment.cgi?id=115334&action=edit GLXINFO of radeon Hi, I was trying to test the new kdenlive development build I noticed that it wouldn't even start with DRI_PRIME=1 kdenlive. I immediatedly got a SIGABRT Same happened with an easy example program from the Qt project "openglunderqml" "LANG=C R600_DEBUG=cs DRI_PRIME=1 QSG_INFO=1 '/home/paul/hybrid test/build-openglunderqml-Desktop-Debug/openglunderqml' QML debugging is enabled. Only use this in a safe environment. openglunderqml: dri2.c:518: dri2_allocate_textures: Assertion `drawable->textures[statt]' failed. Abgebrochen (Speicherabzug geschrieben)" As Xonotic worked more or less ok on the radeon I filed a bug report at the Qt project https://bugreports.qt.io/browse/QTBUG-45686 Laszlo Agocs from the Qt project states the following: "Might be a difficult one and not just because we lack any such hw to test on. Cannot do much when glXMakeCurrent() crashes deep inside the driver. Any chance for a backtrace with symbols? In the absence of that running with QSG_INFO=1 could be helpful too. Anyway, it's most likely happening in QGLXContext::queryDummyContext() where we attempt to make a pbuffer surface current in order to query a few GL things. Other apps may not rely on pbuffers and thus may not exhibit the issue." I'm not a programmer so please go easy on me. If you need additional info let me know (and maybe tell me how to fetch it for you ;) ) Thanks! Hardware: HP EliteBook 850 G1 with Intel (HD4400) / AMD (HD8750M, OLAND) hybrid graphics Software: ArchLinux (Antergos) Linux 3.19.3 mesa 10.5.4 Intel / Radeon exact glxinfo outputs are attached Qt 5.4.1 -- You are receiving this mail because: You are the assignee for the bug.

1 26

[Bug 88886] GPU fault detected on luxmark luxball HDR test with AMD Tahiti
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=88886 Bug ID: 88886 Summary: GPU fault detected on luxmark luxball HDR test with AMD Tahiti 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: commiethebeastie(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Luxmark 3.1b1 Luxball HDR test. agd5f drm-next-3.20-wip kernel System doesn`t respond to sysrq "B" key. Latest mesa-git with llvm-3.7svn build. -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 88461] The computer sometimes freezes after waking up when playing vdpau accelerated video
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=88461 Bug ID: 88461 Summary: The computer sometimes freezes after waking up when playing vdpau accelerated video Product: Mesa Version: 10.4 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: maaniv(a)gmail.com Created attachment 112293 --> https://bugs.freedesktop.org/attachment.cgi?id=112293&action=edit dmesg log I use smplayer (mplayer gui frontend) to watching video. Linux 3.17.6-1-ARCH #1 SMP PREEMPT Sun Dec 7 23:43:32 UTC 2014 x86_64 GNU/Linux Radeon 7850 2GB -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 87278] Packet0 not allowed and GPU fault detected errors with Serious Engine games
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=87278 Bug ID: 87278 Summary: Packet0 not allowed and GPU fault detected errors with Serious Engine games Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: daniel(a)constexpr.org Created attachment 110808 --> https://bugs.freedesktop.org/attachment.cgi?id=110808&action=edit dmesg output with the GPU fault errors filtered out Running Serious Sam 3 or The Talos Principle spams dmesg with thousands of these errors: [ 6001.212237] radeon 0000:01:00.0: GPU fault detected: 147 0x02528801 [ 6001.212243] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0FF02192 [ 6001.212246] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x12088001 [ 6001.212249] VM fault (0x01, vmid 9) at page 267395474, read from TC (136) There are also a few "Packet0 not allowed" errors (followed by a hex dump): [15446.473341] radeon 0000:01:00.0: Packet0 not allowed! So far it's only these errors in dmesg - I haven't observed any actual rendering issues, crashes, GPU lockups because of this. I have only attached a filtered kernel log with the GPU fault errors removed - the full log is available at http://constexpr.org/tmp/serious-dmesg.log (140 MiB). Both of these games use the Serious Engine 3.5 (Serious Sam 3) or 4 (The Talos Principle). This is also reproducible with The Talos Principle Public Test which as of now is still available as a free download on Steam. Kernel: 3.18.0-gentoo GPU: Radeon HD 7950 Driver: radeonsi, Mesa 10.5.0-devel (git-ff96537) This might be related to bug 84500 - however those spurious Packet0 have been gone for a while now with updated Mesa - now I got them again but only while running Serious Engine games. -- You are receiving this mail because: You are the assignee for the bug.

1 33

[Bug 86781] enabling glamor causes jumpy VDPAU playback with 2x framerate DI
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=86781 Bug ID: 86781 Summary: enabling glamor causes jumpy VDPAU playback with 2x framerate DI Product: Mesa Version: 10.3 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: warpme(a)o2.pl VDPAU playback of interlaced content starts to be jumpy when user enables glamor and DI is set to 2x. Issue is seen under MythTV. Playback log reports: 2014-11-13 13:47:01.013753 I Player(1): Video is 3.18365 frames behind audio (too slow), dropping frame to catch up. 2014-11-13 13:47:01.013783 I AOBase: Pause 1 2014-11-13 13:47:01.014047 I Player(1): Video is 3.45023 frames behind audio (too slow), dropping frame to catch up. 2014-11-13 13:47:01.014064 I AOBase: Pause 1 2014-11-13 13:47:01.014171 I Player(1): Video is 3.40015 frames behind audio (too slow), dropping frame to catch up. 2014-11-13 13:47:01.014188 I AOBase: Pause 1 2014-11-13 13:47:01.014286 I Player(1): Video is 3.1126 frames behind audio (too slow), dropping frame to catch up. 2x DI problem manifests only with enabled glamor. On Brazos with EXA, 2x DI works perfect while enabling glamor triggers 2x DI issue. On Kabini issue is always present as Kabini mandatory requires glamor. Tests were done with mesa 10.2.8/10.3.3 and xserver 1.16.1/1.16.2 -- You are receiving this mail because: You are the assignee for the bug.

1 3

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel June 2015