dri-devel June 2011

dri-devel@lists.freedesktop.org

101 participants
499 discussions

[Bug 36611] New: [wine] The Witcher: Crash in u_vbuf_mgr_draw_begin
by bugzilla-daemon＠freedesktop.org 11 Jun '11

11 Jun '11

https://bugs.freedesktop.org/show_bug.cgi?id=36611 Summary: [wine] The Witcher: Crash in u_vbuf_mgr_draw_begin 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=46094) --> (https://bugs.freedesktop.org/attachment.cgi?id=46094) Backtrace The game The Witcher (running in Wine) crashes shortly after start: u_vbuf_mgr_draw_begin+0x198(mgrb=0x7c5937c0, info=0x1c6ec5c, buffers_updated="À`¬d|", uploader_flushed="") [/home/sa/Programming/gfx/mesa/mesa/src/gallium/auxiliary/util/u_vbuf_mgr.c:549] in r300_dri.so (0x01c6e9f4) This does not happen in 7.10. Bisecting leads to this commit: c95bc1224a4b20b9470ddcb37b5f78975991073b is the first bad commit commit c95bc1224a4b20b9470ddcb37b5f78975991073b Author: Marek Olšák <maraeo(a)gmail.com> Date: Mon Feb 7 02:00:44 2011 +0100 r300g: use the new vertex buffer manager :040000 040000 4be08dc19f4fa4e1de6b1b259c6bd481b2fc33e5 28f8c721e519137890b5082fdff66671dbcfacb0 M src I'm attaching a backtrace, but I'm not sure how helpful it is, as getting it from Wine was quite tricky. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 2

[Bug 37475] New: [wine] Crysis: series of soft GPU hangs in menu
by bugzilla-daemon＠freedesktop.org 11 Jun '11

11 Jun '11

https://bugs.freedesktop.org/show_bug.cgi?id=37475 Summary: [wine] Crysis: series of soft GPU hangs in menu Product: Mesa Version: git Platform: Other URL: http://www.gamershell.com/download_21700.shtml OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: sa(a)whiz.se Created an attachment (id=47015) --> (https://bugs.freedesktop.org/attachment.cgi?id=47015) dmesg output The demo of the game Crysis (running in Wine) is causing a series of soft GPU resets in the menu. The game runs for a few seconds, freezes, the screen flickers and the GPU resets, the game continues to run etc. I tried to use apitrace, but it does not recreate the bug, in fact, just using glxtrace.so seems to be enough to work around the bug. System environment: -- system architecture: 32-bit -- Linux distribution: Debian unstable -- GPU: REDWOOD -- Model: XFX Radeon HD 5670 1GB -- Display connector: DVI -- xf86-video-ati: 6.14.1 -- xserver: 1.10.1 -- mesa: git-fd6f2d6 -- drm: 2.4.25 -- kernel: 2.6.39 -- 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 38182] New: "Trine" Game does not work with r600g (Card: HD2600). Complains about shader compiler error.
by bugzilla-daemon＠freedesktop.org 11 Jun '11

11 Jun '11

https://bugs.freedesktop.org/show_bug.cgi?id=38182 Summary: "Trine" Game does not work with r600g (Card: HD2600). Complains about shader compiler error. Product: Mesa Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/R600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: da1l6(a)douwd.org Created an attachment (id=47848) --> (https://bugs.freedesktop.org/attachment.cgi?id=47848) Trine log file The Game "Trine" (from HumbleBundle 3) does not run with the r600g driver, even with all graphics settings to minimum. Message displayed: "Fatal error: Error compiling shaders. Make sure your GPU supports Shader Model 3.0. Additional details may be found in the log." Logfile excerpt (Full log attached): INFO: Compiling program depthpass_mesh_pixel entry point mesh_deferred_all ERROR: Cg error: 1 1 (The compile returned an error.) ERROR: data/shader/cg/depthpass_mesh_pixel.cg(26) : error C5102: output semantic attribute "COLOR" has too big of a numeric index (1) data/shader/cg/depthpass_mesh_pixel.cg(27) : error C5102: output semantic attribute "COLOR" has too big of a numeric index (2) data/shader/cg/depthpass_mesh_pixel.cg(26) : error C5041: cannot locate suitable resource to bind parameter "oColor1" data/shader/cg/depthpass_mesh_pixel.cg(27) : error C5041: cannot locate suitable resource to bind parameter "oColor2" Hardware: 01:00.0 VGA compatible controller: ATI Technologies Inc M76 [Radeon Mobility HD 2600 Series] Mesa: OpenGL renderer string: Gallium 0.4 on AMD RV630 OpenGL version string: 2.1 Mesa 7.11-devel (git-da8b4c0) OS: Linux 2.6.39.1 (Archlinux) -- 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

[Bug 37112] GPU lockup when trying to use profile based frequency switching
by bugzilla-daemon＠bugzilla.kernel.org 11 Jun '11

11 Jun '11

https://bugzilla.kernel.org/show_bug.cgi?id=37112 --- Comment #8 from Hrvoje Senjan <hrvoje.senjan(a)gmail.com> 2011-06-11 15:38:06 --- I forgot to say 2 things: a)i tried your suggestion with 3.0.0-rc2 ,b) NO lockups :) -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 0

[Bug 37112] GPU lockup when trying to use profile based frequency switching
by bugzilla-daemon＠bugzilla.kernel.org 11 Jun '11

11 Jun '11

https://bugzilla.kernel.org/show_bug.cgi?id=37112 --- Comment #7 from Hrvoje Senjan <hrvoje.senjan(a)gmail.com> 2011-06-11 15:29:50 --- Yes it helps! :) Using default profile: default engine clock: 600000 kHz current engine clock: 594000 kHz default memory clock: 500000 kHz current memory clock: 495000 kHz voltage: 1100 mV PCIE lanes: 16 using low: default engine clock: 600000 kHz current engine clock: 109680 kHz default memory clock: 500000 kHz current memory clock: 495000 kHz voltage: 900 mV PCIE lanes: 16 -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 0

Valid VCO range on 855GME platform
by "David Müller (ELSOFT AG)" 11 Jun '11

11 Jun '11

Hello I have a problem using a 1024x768@60Hz LVDS panel attached to a 855GME based system running under Linux-2.6.39. As long as the system is under VGA BIOS control, everything is fine (panel refresh rate is 60.1Hz). As soon as the i915 Linux driver is taking over control, the refresh rate raises to 61.4Hz. As far as i can see the i915 driver is (wrongly) reprogramming the Pipe B PLL to a higher dot clock as shown below: PLL values set up by VGA BIOS: N=4, M1=18, M2=12, P1=1, P2=14 => dot clock: 65.142 MHz, refresh rate: 60.1Hz PLL values set up by i915 driver: N=5, M1=22, M2=14, P1=1, P2=14 => dot clock: 66.612MHz, refresh rate: 61.4Hz According to "intel_PLL_is_valid()" the PLL values used by the VGA BIOS are invalid because of a "vco out of range" condition. Is the "I8XX_VCO_MIN" in "drivers/gpu/drm/i915/intel_display.c" correctly set or should it be set to a lower value? Dave

1 0

[Bug 37112] GPU lockup when trying to use profile based frequency switching
by bugzilla-daemon＠bugzilla.kernel.org 11 Jun '11

11 Jun '11

https://bugzilla.kernel.org/show_bug.cgi?id=37112 Rafał Miłecki <zajec5(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zajec5(a)gmail.com --- Comment #6 from Rafał Miłecki <zajec5(a)gmail.com> 2011-06-11 07:36:36 --- (In reply to comment #5) > My first guess is , that kernel changes memory clock too low - with fglrx > lowest memory clock is at 400MHz , but with radeon module/low frequency it > changes it to 300MHz. Please, edit drivers/gpu/drm/radeon/radeon_pm.c, find: > if (rdev->asic->set_memory_clock && (mclk != rdev->pm.current_mclk)) { and make it > if (0) { Does it help? -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 0

[Bug 37112] GPU lockup when trying to use profile based frequency switching
by bugzilla-daemon＠bugzilla.kernel.org 11 Jun '11

11 Jun '11

https://bugzilla.kernel.org/show_bug.cgi?id=37112 --- Comment #5 from Hrvoje Senjan <hrvoje.senjan(a)gmail.com> 2011-06-11 06:45:28 --- My first guess is , that kernel changes memory clock too low - with fglrx lowest memory clock is at 400MHz , but with radeon module/low frequency it changes it to 300MHz. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 0

Questions about libdrm programming
by Zachary Catlin 11 Jun '11

11 Jun '11

I'm interested in (1) using my graphics card for computations and (2) low-level shader code, and I'm looking for guidance on how I would go about doing the following operations with libdrm (sans Mesa): * client-side initialization * loading textures into the GPU * loading a bytecode shader into the GPU * creating a texture on the GPU without uploading data * running the shader using the uploaded textures as inputs and the non-uploaded texture as the output * transferring the output texture into main memory * tear-down, finalization The GPU in question is a Radeon RV730, if any hardware-dependent discussion is needed. I've tried to understand the workflow by looking at the Mesa and Plymouth sources and the documentation I've found for the DRI/DRM, but I could still use some guidance.

2 2

multiple framebuffer drm maps
by Tormod Volden 10 Jun '11

10 Jun '11

In commit 41c2e75e60200a860a74b7c84a6375c105e7437f "drm: Make drm_local_map use a resource_size_t offset" [1] the support for multiple _DRM_FRAMEBUFFER maps per device was taken away. This change made the savage drivers upset, since these cards have several apertures (the layout is different between card families) for which the kernel drm driver sets up maps. And these maps are now mixed up into one broken one. The drivers (drm, ddx, mesa) for instance expects a framebuffer map and a tiled aperture map, and the broken maps show up as rendering corruption [2] and allocation failures. I have tried to come up with userland workarounds but it seems impossible since the kernel will only return the handle to a broken map and there is no way to remap it correctly. Would it be possible to reintroduce this support? One solution could be a new flag _DRM_IGNORE_FB_OFFSET that can be used by those drivers that need it, or the other way around, a _DRM_CHECK_FB_OFFSET to be added by the savage drivers and others in the same situation. I can of course try to write a patch if people think this is a good idea. Best regards, Tormod [1] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h… [2] https://bugs.freedesktop.org/show_bug.cgi?id=32511

3 11

← Newer
1
...
41
42
43
44
45
46
47
...
50
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel June 2011