dri-devel December 2012

dri-devel@lists.freedesktop.org

121 participants
687 discussions

[Bug 42002] New: graphical glitches when using Xorg state tracker and 2D acceleration enabled
by bugzilla-daemon＠freedesktop.org 05 Dec '12

05 Dec '12

https://bugs.freedesktop.org/show_bug.cgi?id=42002 Bug #: 42002 Summary: graphical glitches when using Xorg state tracker and 2D acceleration enabled Classification: Unclassified Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r300 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: martinstolpe(a)gmail.com Created attachment 52529 --> https://bugs.freedesktop.org/attachment.cgi?id=52529 Screenshot of Firefox when 2d acceleration is enabled I've attached some screenshots of Firefox and Notepad++ when 2D acceleration is enabled and disabled. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 8

[Bug 42622] New: [mesa] [r300] mupen64plus invalid command stream
by bugzilla-daemon＠freedesktop.org 05 Dec '12

05 Dec '12

https://bugs.freedesktop.org/show_bug.cgi?id=42622 Bug #: 42622 Summary: [mesa] [r300] mupen64plus invalid command stream Classification: Unclassified Product: Mesa Version: 7.11 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/r300 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: yoshi314(a)gmail.com I've just built mupen64 plus emulator and it crashed after a few seconds (after emulator intro screen). When running it, i get something like this : Core: R4300: starting 64-bit dynamic recompiler at: 0xbc0200 radeon: The kernel rejected CS, see dmesg for more information. inspecting dmesg gives this output: [ 4250.120602] [drm:r100_cs_packet_next_reloc] *ERROR* No packet3 for relocation for packet at 1140. [ 4250.120607] [drm] ib[1140]=0x000013C6 [ 4250.120609] [drm] ib[1141]=0x00000001 [ 4250.120611] [drm:r100_packet3_load_vbpntr] *ERROR* No reloc for packet3 47 [ 4250.120613] [drm] ib[1131]=0xC0052F00 [ 4250.120615] [drm] ib[1132]=0x00000003 [ 4250.120617] [drm] ib[1133]=0x0A020804 [ 4250.120618] [drm] ib[1134]=0x103A0980 [ 4250.120620] [drm] ib[1135]=0x00000000 [ 4250.120622] [drm] ib[1136]=0x00000A02 [ 4250.120623] [drm] ib[1137]=0x00000000 [ 4250.120625] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream ! the same behavior is on current mesa git. hardware is RV515 (x1300 pro) on 64bit system. i'd like to know if that's a program issue, or mesa bug? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 9

[Bug 41579] New: R300 Segfaults when using mupen64plus
by bugzilla-daemon＠freedesktop.org 05 Dec '12

05 Dec '12

https://bugs.freedesktop.org/show_bug.cgi?id=41579 Summary: R300 Segfaults when using mupen64plus Product: Mesa Version: 7.11 Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/DRI/r300 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: krthurow(a)gmail.com Created an attachment (id=52103) --> (https://bugs.freedesktop.org/attachment.cgi?id=52103) Backtrace from r300 segfault when running mupen64plus. When starting up the emulator mupen64plus with a ROM, it crashes before loading the ROM, showing a segfault. Video card is a Mobility Radeon X1700. Using gdb I traced the segfault back to r300_dri.so The issues seems to be at line 864 of src/gallium/drivers/r300/r300_emit.c 'buf' is getting set to 0 instead of a proper address. My backtrace is attached. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 6

[Bug 36952] New: segfault in crackberg xscreensaver on ATI RS482 in mesa git running kms & gallium
by bugzilla-daemon＠freedesktop.org 05 Dec '12

05 Dec '12

https://bugs.freedesktop.org/show_bug.cgi?id=36952 Summary: segfault in crackberg xscreensaver on ATI RS482 in mesa git running kms & gallium Product: Mesa Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r300 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: writemeanddie(a)hotmail.com system 32 bit gentoo video card ATI RS482 configured to share 128MB system RAM kernel 2.6.38.4 xorg-server 1.10.1 mesa git commit 37058c3497850f452bdaf70a5dda07ee4840b6b9 May 4 2011 xf86-video-ati git commit 62a4cd180fe884dca24586d453395472516e6496 May 4, 2011 mesa compile flags: classic egl gallium llvm nptl openvg shared-dricore video_cards_r300 video_cards_radeon xscreensaver 5.12 When running the xscreensaver 'crackberg' on mesa from git the screen freezes for 20-60 seconds (I think memory is filling up and swapping out RAM) and then the program exits with a segfault. The message in /var/log/kern.log is kernel: crackberg[30926]: segfault at b5a30000 ip b653b2c1 sp bf943e30 error 4. If I downgrade to mesa 7.10.2-r1 the screensaver works as expected. If I run with ums the screensaver works as expected. Other screensavers are affected as well, I can compile a list if necessary. Any other logs or info that I can collect is no problem. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 18

[Bug 37220] New: RS482: Screen starts flashing after screensaver with KDE KWin desktop effects enabled
by bugzilla-daemon＠freedesktop.org 05 Dec '12

05 Dec '12

https://bugs.freedesktop.org/show_bug.cgi?id=37220 Summary: RS482: Screen starts flashing after screensaver with KDE KWin desktop effects enabled Product: Mesa Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/Gallium/r300 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: jlp.bugs(a)gmail.com After a very long time I have got my old laptop with integrated ATI Radeon Xpress 200M. I remeber running it with desktop effects enabled and classic mesa r300 driver just fine. Well now wit Gallium I have this annoying problem: I have the screensaver set to Solar Winds from KDE's kdeartwork/screensaver package. As usually I left the computer alone and when I came back and moved the mouse screensaver turned off. But what started happening was that the screen was flashing. Parts of it (rectangular) were becoming black or werw coming from black to normal. Thoose parts are the parts that the mouse was traveling over. Just as if the damaged areas which needed redrawing. To make this go away I had to turn off the desktop effects (using Alt+Shift+F12) and then turn them back on (with same keybiard shortcut). The flashing effect is especially visible if I have the KDE's Screen Saver control center module open and test OpenGL screensavers from there. Reproducable: always Software in use: * mesa: git-bd5b7a6 * kde: 4.6.3 * xorg server: 1.10.1.901 * linux kernel: 2.6.39-rc7 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 6

[Bug 34097] New: Screen clearing issues in Minecraft and Blender
by bugzilla-daemon＠freedesktop.org 05 Dec '12

05 Dec '12

https://bugs.freedesktop.org/show_bug.cgi?id=34097 Summary: Screen clearing issues in Minecraft and Blender Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r300 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: sa(a)whiz.se Created an attachment (id=43170) --> (https://bugs.freedesktop.org/attachment.cgi?id=43170) Minecraft after switching from fullscreen When switching between fullscreen and window in the game Minecraft, or when pressing F12 to render the scene in Blender, I'm getting a a corrupt screen. Sometimes it looks like it contains traces of a previously running gl application, so maybe some buffer or something isn't cleared properly? This isn't a new bug (seems to be present at least as far back as 7.9) or a very important one, but would be nice if it could be fixed. System environment: -- system architecture: 32-bit -- Linux distribution: Debian unstable -- GPU: RV570 -- Model: Asus EAX1950Pro 256MB -- Display connector: DVI -- xf86-video-ati: 6.13.2 -- xserver: 1.9.4 -- mesa: 04c5cc5b8bec1f34f2405b08fd0d9ed6bd70ea61 -- drm: 2.4.23 -- kernel: 2.6.37 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 7

[Bug 40554] New: r200 falls back to software when clearing FBOs
by bugzilla-daemon＠freedesktop.org 05 Dec '12

05 Dec '12

https://bugs.freedesktop.org/show_bug.cgi?id=40554 Summary: r200 falls back to software when clearing FBOs Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/r200 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: stefandoesinger(a)gmx.at Created an attachment (id=50814) --> (https://bugs.freedesktop.org/attachment.cgi?id=50814) Sample application glClear(GL_COLOR_BUFFER_BIT) causes a software fallback when a FBO is bound. The line in the debug output that signals this fallback is r200Clear: swrast clear, mask: 100 0x100 is BUFFER_BIT_COLOR0 as far as I can see, which is indeed not handled in that function. I have attached a sample application that is a side product of attempting to reproduce bug 40552. The sample doesn't crash(yet), but it reproduces the software fallback. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 5

[PATCH 0/3] drm/exynos: modify usage of wait for vblank
by Prathyush K 05 Dec '12

05 Dec '12

This patchset fixes a few issues with use of wait for vblank in exynos drm. Please apply these three patches without "drm/exynos: release fb pended by page flip" patch. Patch 1: modify wait for vsync functions to use wait queues This modifies the wait_for_vblank functions to use wait queues thus ensuring that the current task goes to sleep without taking up CPU while waiting. Patch 2: move wait_for_vblank to manager_ops Currently, we do not call wait for vblank if encoder is in DPMS_OFF state inside exynos_drm_encoder_complete_scanout function. This is because wait for vblank is treated as an overlay op. This can be modified to a manager_op thus removing the above check for DPMS_OFF. This fixes a crash while removing a fb. While removing the current fb (crtc->fb == fb) the encoder dpms off is called and then the framebuffer is removed. So in this case, the wait for vblank is not called thus leading to a crash (since fb might get removed before dma is finished) Patch 3: do not disable crtc if already off We should not disable the overlay if the crtc is in DPMS_OFF state. Also, the disable function should not call DPMS_OFF of the crtc. This is required to ensure we are able to wait for vblank before freeing any framebuffers after disabling the crtc. With these three patches and without "drm/exynos: release fb pended by page flip" I could not find any crash/page_fault in drm with fimd/hdmi during hotplug and page flips. Prathyush K (3): drm/exynos: modify wait for vsync functions to use wait queues drm/exynos: move wait_for_vblank to manager_ops drm/exynos: do not disable crtc if already off drivers/gpu/drm/exynos/exynos_drm_crtc.c | 6 +++- drivers/gpu/drm/exynos/exynos_drm_drv.h | 20 ++------------ drivers/gpu/drm/exynos/exynos_drm_encoder.c | 15 +++-------- drivers/gpu/drm/exynos/exynos_drm_fimd.c | 37 ++++++++++++++++++-------- drivers/gpu/drm/exynos/exynos_drm_hdmi.c | 22 ++++++++-------- drivers/gpu/drm/exynos/exynos_drm_hdmi.h | 2 +- drivers/gpu/drm/exynos/exynos_mixer.c | 37 +++++++++++++++++--------- 7 files changed, 73 insertions(+), 66 deletions(-)

4 8

[RFC libdrm] Add NVIDIA Tegra support
by Thierry Reding 05 Dec '12

05 Dec '12

Hi, I mentioned in a reply to Terje's patch series for 2D acceleration that I had prototyped some libdrm support a few weeks back. I've spent a bit of time cleaning it up and decided to post it for early review. There's really not much interesting code here. A basic API is provided along with two IOCTLs that can be used to create Tegra-specific GEM, as opposed to dumb buffer objects. Given the various comments on Terje's proposed IOCTLs I wanted to make sure that these will be safe. I've seen that other chips use 64-bit fields for the size and offset of buffer objects and I wonder if those are really necessary. Linux kernel patches for the IOCTLs are also in the works and I hope to get around to posting them this week. Obviously there will be some overlap between this and what Terje posted in his series, but it should be easy to synchronize. Thierry Thierry Reding (1): libdrm: Add NVIDIA Tegra support Makefile.am | 6 +- configure.ac | 15 ++- include/drm/Makefile.am | 1 + include/drm/tegra_drm.h | 48 ++++++++++ tegra/Makefile.am | 17 ++++ tegra/libdrm_tegra.pc.in | 11 +++ tegra/tegra.c | 227 ++++++++++++++++++++++++++++++++++++++++++++++ tegra/tegra.h | 51 +++++++++++ tests/modetest/modetest.c | 2 +- tests/vbltest/vbltest.c | 2 +- 10 files changed, 376 insertions(+), 4 deletions(-) create mode 100644 include/drm/tegra_drm.h create mode 100644 tegra/Makefile.am create mode 100644 tegra/libdrm_tegra.pc.in create mode 100644 tegra/tegra.c create mode 100644 tegra/tegra.h -- 1.8.0.1

3 5

[Bug 51301] [-next-20121129] memory leak/page allocator fragmentation?
by bugzilla-daemon＠bugzilla.kernel.org 05 Dec '12

05 Dec '12

https://bugzilla.kernel.org/show_bug.cgi?id=51301 --- Comment #6 from Peter Hurley <peter(a)hurleysoftware.com> 2012-12-05 00:57:08 --- This is filesystem/block or memory manager-related. I just built -next-20121204 and by the end of the build a 10gb machine had < 100mb of zone DMA32 and < 70mb zone NORMAL. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching someone on the CC list of the bug.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel December 2012