dri-devel January 2011

dri-devel@lists.freedesktop.org

70 participants
451 discussions

[Bug 30166] New: [wine] Shader issues in rthdribl 1.2
by bugzilla-daemon＠freedesktop.org 09 Jun '11

09 Jun '11

https://bugs.freedesktop.org/show_bug.cgi?id=30166 Summary: [wine] Shader issues in rthdribl 1.2 Product: Mesa Version: git Platform: Other URL: http://www.daionet.gr.jp/~masa/rthdribl/ 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=38671) --> (https://bugs.freedesktop.org/attachment.cgi?id=38671) Screenshot comparing llvmpipe and r300g The DirectX9 demo "rthdribl" isn't rendering correctly with r300g. This is partly a regression from the glsl2 merge, but probably not a problem in the GLSL compiler since llvmpipe seems to handle the demo. Rendering wasn't 100% prior to the glsl2 merge either. The "glare" filter causes the screen to be drawn mostly white, so be sure to turn it off: Options → Glare → Glare Type → Disable Version 1.2 of the demo can be downloaded here: http://www.daionet.gr.jp/~masa/rthdribl/ You'll also need mfc42.dll: http://www.dlldump.com/download-dll-files_new.php/dllfiles/M/mfc42.dll/6.0.… System environment: -- system architecture: 32-bit -- Linux distribution: Debian unstable -- GPU: RV570 -- Model: Asus EAX1950Pro 256MB -- Display connector: DVI -- xf86-video-ati: e9928fe036e9382fd7bc353f3f05531445f08977 -- xserver: 1.8.99.904 (1.9.0 RC 5) -- mesa: 6f839eb631511925505093be4d0509ac14f5675b -- drm: 23287f05cf2443ddf9e028e29beb5bd30979c6cf -- kernel: 2.6.35.4 -- 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 33389] New: Amesia (closed source game) segfaults
by bugzilla-daemon＠freedesktop.org 04 Jun '11

04 Jun '11

https://bugs.freedesktop.org/show_bug.cgi?id=33389 Summary: Amesia (closed source game) segfaults 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: r0ugh_l(a)yahoo.de When trying to run Amnesia (http://www.amnesiagame.com/#demo) on my system it gives me this output: [1] 619 segmentation fault ./Amnesia.bin64 It runs fine until the loading screen and then crashes. Steps to reproduce: Run Amnesia with r600 driver Additional information: It doesn't crash if I'm using the llvm-pipe driver. I've tested it at the lowest possible graphics settings. Backtrace: #0 0x000000000082ab08 in hpl::iParticleEmitter::GetMaterial() () #1 0x0000000000805de2 in hpl::iRenderer::RenderObjectZAndAddToRenderList(hpl::iRenderable*) () #2 0x0000000000805e59 in hpl::iRenderer::RenderObjectZAndAddToRenderListStaticCallback(hpl::iRenderer*, hpl::iRenderable*) () #3 0x0000000000807d8f in hpl::iRenderer::RenderAndAddNodeObjects(hpl::iRenderableContainerNode*, bool (*)(hpl::iRenderer*, hpl::iRenderable*), unsigned int) () #4 0x000000000080808a in hpl::iRenderer::CheckForVisibleObjectsAddToListAndRenderZ(hpl::cVisibleRCNodeTracker*, unsigned int, unsigned int, bool, bool (*)(hpl::iRenderer*, hpl::iRenderable*)) () #5 0x00000000007e4841 in hpl::cRendererDeferred::RenderObjects() () #6 0x0000000000809334 in hpl::iRenderer::Render(float, hpl::cFrustum*, hpl::cWorld*, hpl::cRenderSettings*, hpl::cRenderTarget*, bool, std::list<hpl::iRendererCallback*, std::allocator<hpl::iRendererCallback*> >*) () #7 0x000000000082496d in hpl::cScene::Render(float, unsigned int) () #8 0x0000000000925423 in hpl::cEngine::Run() () #9 0x0000000000689890 in hplMain(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) () #10 0x000000000090ff29 in main () Version Information: mesa: git 835c4ea1053730c8eea98337c9da1b14fcff6b5e OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD RV770 OpenGL version string: 2.1 Mesa 7.11-devel OpenGL shading language version string: 1.20 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 12

[Bug 30901] New: Heroes of Newerth won't start when mesa is compiled with --enable-gallium-llvm
by bugzilla-daemon＠freedesktop.org 26 May '11

26 May '11

https://bugs.freedesktop.org/show_bug.cgi?id=30901 Summary: Heroes of Newerth won't start when mesa is compiled with --enable-gallium-llvm Product: Mesa Version: git Platform: x86 (IA32) URL: http://dl.heroesofnewerth.com/HoNClient-1.0.14.sh OS/Version: Linux (All) Status: NEW Severity: minor Priority: medium Component: Drivers/Gallium/r300 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: drakkk(a)centrum.cz I usually configure mesa like this: "--enable-debug --enable-gallium-radeon --with-dri-drivers= --with-state-trackers=dri,glx", with this HoN starts and runs fine with r300g driver. However I was trying llvmpipe with some other apps and I noticed, when I add "--enable-gallium-llvm", HoN won't start with "K2 - Fatal Error: ARB_vertex_buffer_object not available." This is quite strange because glxinfo is identical and shows GL_ARB_vertex_buffer_object in both cases (and OpenGL vendor string: X.Org R300 Project, OpenGL renderer string: Gallium 0.4 on RV530, so its not like I was using some other driver). I'm quite sure I didn't messed up anything I even asked at #radeon if I'm doing something wrong. LIBGL_DRIVERS_PATH and LD_LIBRARY_PATH are both pointing to right mesa directories and I did git clean -fdx between builds. So far I wasn't able to reproduce this with any other app. This is with Fedora 14 i686, kernel 2.6.35.6-39.fc14, mesa from git, RV530. -- 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 28876] New: [radeon HD4250] Frequent lockups while screen locked
by bugzilla-daemon＠freedesktop.org 20 May '11

20 May '11

https://bugs.freedesktop.org/show_bug.cgi?id=28876 Summary: [radeon HD4250] Frequent lockups while screen locked Product: DRI Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: critical Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: ydirson(a)altern.org Created an attachment (id=36664) --> (https://bugs.freedesktop.org/attachment.cgi?id=36664) Xorg log file, with nearly 30k lines of repeated messages stripped Direct symptoms: - display left unattended with xscreensaver in simple blank mode - DPMS disabled (checked both with xset and xscreensaver-demo) - when coming back to my keyboard the monitor does not get a video signal - I can still login remotely through ssh and reboot the machine properly Hardware is an Asus "M4A88TD-V EVO/USB3" motherboard, featuring radeon HD4250 (RS780). OS is uptodate Debian/testing. syslog contains lines like the following. In this case, although I was not here, it may be that someone tried to use the box. In the 2 other occurences I have traces for, it I may even have been myself, but I did not dig at that time. However, although the Xorg.0.log error lines are not timestamped, the file timestamp itself matches the box' reboot. Since there are ~15000 occurences of the error, X may have been experiencing them since the error reported by the drm module. I can try to get more detailed facts next time (unless unnecessary, just tell). Jun 30 10:17:01 home /USR/SBIN/CRON[27295]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Jun 30 10:18:10 home kernel: [130052.418150] executing set pll Jun 30 10:18:10 home kernel: [130052.424023] executing set crtc timing Jun 30 10:18:10 home kernel: [130052.424072] [drm] TMDS-11: set mode 1920x1200 1b Jun 30 10:18:10 home acpid: client 2095[0:0] has disconnected Jun 30 10:18:10 home acpid: client connected from 27304[0:0] Jun 30 10:18:10 home acpid: 1 client rule loaded Jun 30 10:18:13 home kernel: [130055.829085] [drm:radeon_ib_get] *ERROR* radeon: IB(0:0x0000000010101000:668) Jun 30 10:18:13 home kernel: [130055.829088] [drm:radeon_ib_get] *ERROR* radeon: GPU lockup detected, fail to get a IB Jun 30 10:18:13 home kernel: [130055.829090] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib ! [...] Jun 30 10:18:42 home kernel: [130084.275900] [drm:radeon_ib_get] *ERROR* radeon: IB(0:0x0000000010101000:668) Jun 30 10:18:42 home kernel: [130084.275906] [drm:radeon_ib_get] *ERROR* radeon: GPU lockup detected, fail to get a IB Jun 30 10:18:42 home kernel: [130084.275912] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib ! Jun 30 11:17:01 home /USR/SBIN/CRON[27329]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) In older occurences (do not recall the precise set of events, although the "wishing to unlock screen" event has always been the only way to see the problem), the 3 error lines occur on a longer timespan, some in sync with the clock (??): Jun 27 19:17:01 home /USR/SBIN/CRON[26082]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Jun 27 19:18:09 home kernel: [21853.241075] executing set pll Jun 27 19:18:09 home kernel: [21853.248025] executing set crtc timing Jun 27 19:18:09 home kernel: [21853.248076] [drm] TMDS-11: set mode 1920x1200 1b Jun 27 19:18:12 home kernel: [21856.334252] [drm:radeon_ib_get] *ERROR* radeon: IB(0:0x0000000010101000:668) Jun 27 19:18:12 home kernel: [21856.334261] [drm:radeon_ib_get] *ERROR* radeon: GPU lockup detected, fail to get a IB Jun 27 19:18:12 home kernel: [21856.334269] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib ! [...] Jun 27 19:18:32 home kernel: [21876.279726] [drm:radeon_ib_get] *ERROR* radeon: IB(0:0x0000000010101000:668) Jun 27 19:18:32 home kernel: [21876.279733] [drm:radeon_ib_get] *ERROR* radeon: GPU lockup detected, fail to get a IB Jun 27 19:18:32 home kernel: [21876.279739] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib ! Jun 27 19:19:00 home kernel: [21904.282670] [drm:radeon_ib_get] *ERROR* radeon: IB(0:0x0000000010101000:668) Jun 27 19:19:00 home kernel: [21904.282678] [drm:radeon_ib_get] *ERROR* radeon: GPU lockup detected, fail to get a IB Jun 27 19:19:00 home kernel: [21904.282685] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib ! Jun 27 19:20:00 home kernel: [21964.322037] [drm:radeon_ib_get] *ERROR* radeon: IB(0:0x0000000010101000:668) Jun 27 19:20:00 home kernel: [21964.322045] [drm:radeon_ib_get] *ERROR* radeon: GPU lockup detected, fail to get a IB Jun 27 19:20:00 home kernel: [21964.322052] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib ! Jun 27 19:21:00 home kernel: [22024.321528] [drm:radeon_ib_get] *ERROR* radeon: IB(0:0x0000000010101000:668) Jun 27 19:21:00 home kernel: [22024.321537] [drm:radeon_ib_get] *ERROR* radeon: GPU lockup detected, fail to get a IB Jun 27 19:21:00 home kernel: [22024.321544] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib ! Jun 27 19:22:00 home kernel: [22084.321217] [drm:radeon_ib_get] *ERROR* radeon: IB(0:0x0000000010101000:668) Jun 27 19:22:00 home kernel: [22084.321225] [drm:radeon_ib_get] *ERROR* radeon: GPU lockup detected, fail to get a IB Jun 27 19:22:00 home kernel: [22084.321232] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib ! Jun 27 19:23:00 home kernel: [22144.367818] [drm:radeon_ib_get] *ERROR* radeon: IB(0:0x0000000010101000:668) Jun 27 19:23:00 home kernel: [22144.367827] [drm:radeon_ib_get] *ERROR* radeon: GPU lockup detected, fail to get a IB Jun 27 19:23:00 home kernel: [22144.367833] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib ! Jun 27 19:24:00 home kernel: [22204.414007] [drm:radeon_ib_get] *ERROR* radeon: IB(0:0x0000000010101000:668) Jun 27 19:24:00 home kernel: [22204.414015] [drm:radeon_ib_get] *ERROR* radeon: GPU lockup detected, fail to get a IB Jun 27 19:24:00 home kernel: [22204.414022] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib ! Jun 27 19:24:12 home kernel: [22216.304962] [drm:radeon_ib_get] *ERROR* radeon: IB(0:0x0000000010101000:668) Jun 27 19:24:12 home kernel: [22216.304970] [drm:radeon_ib_get] *ERROR* radeon: GPU lockup detected, fail to get a IB Jun 27 19:24:12 home kernel: [22216.304977] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib ! Xorg.0.log repeated messages are: (EE) RADEON(0): Timeout trying to update memory controller settings ! (EE) RADEON(0): You will probably crash now ... Package versions are as follows (dpkg -l|grep xserver): x11-xserver-utils 7.5+1 xserver-common 2:1.7.7-2 xserver-xephyr 2:1.7.7-2 xserver-xorg 1:7.5+6 xserver-xorg-core 2:1.7.7-2 xserver-xorg-core-dbg 2:1.7.7-2 xserver-xorg-input-all 1:7.5+6 xserver-xorg-input-evdev 1:2.3.2-6 xserver-xorg-input-synaptics 1.2.2-2 xserver-xorg-input-wacom 0.10.5+20100416-1 xserver-xorg-video-ati 1:6.13.0-2 xserver-xorg-video-fbdev 1:0.4.2-2 xserver-xorg-video-mach64 6.8.2-3 xserver-xorg-video-mga 1:1.4.11.dfsg-4 xserver-xorg-video-r128 6.8.1-3 xserver-xorg-video-radeon 1:6.13.0-2 xserver-xorg-video-radeon-dbg 1:6.13.0-2 xserver-xorg-video-vesa 1:2.3.0-3 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 4

[Bug 32318] New: [r300g] Titan's atmosphere in celestia is blue with OpenGL 2.0 rendering path.
by bugzilla-daemon＠freedesktop.org 02 May '11

02 May '11

https://bugs.freedesktop.org/show_bug.cgi?id=32318 Summary: [r300g] Titan's atmosphere in celestia is blue with OpenGL 2.0 rendering path. 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: rankincj(a)googlemail.com Created an attachment (id=41009) --> (https://bugs.freedesktop.org/attachment.cgi?id=41009) Titan, as seen with OpenGL 2.0 rendering path Celestia 1.5.1, with r300g from git, RV350 card. When viewing Saturn's moon Titan with atmospheres enabled (Ctrl-A), the atmosphere appears orange for basic, multitexture and OpenGL vertex program rendering paths, but blue for OpenGL 2.0 rendering path. (Cycle through available rendering paths using Ctrl-V.) This inconsistency is suspicious - I suspect a 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 5

[Bug 28627] New: 2.6.31.6 is the last kernel where KMS works well on an RV515 card for regular PCI
by bugzilla-daemon＠freedesktop.org 01 May '11

01 May '11

https://bugs.freedesktop.org/show_bug.cgi?id=28627 Summary: 2.6.31.6 is the last kernel where KMS works well on an RV515 card for regular PCI Product: DRI Version: unspecified Platform: x86 (IA32) OS/Version: All Status: NEW Severity: major Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: connor.behan(a)gmail.com After constant regressions, I thought I would post this. dmesg.good: http://pastebin.com/kL3iXTU3 xorglog.good: http://pastebin.com/n7diwRCL glxinfo.good: http://pastebin.com/aDajgYQC dmesg.bad: http://pastebin.com/JSKSD8Dn xorglog.bad: http://pastebin.com/QdDhfknr glxinfo.bad: http://pastebin.com/AWabZKN8 dmesg.reallybad: http://pastebin.com/Jc4sqySK xorglog.reallybad: http://pastebin.com/fzMEJfZH glxinfo.reallybad: http://pastebin.com/tkJgTgKa Good is kernel 2.6.31.6 where I get glxgears frame rates of ~300fps. This is all I can expect from a slow PCI bus. Bad is kenel 2.6.33.4 where the glxgears frame rates are a little slower, maybe 250fps and quitting X fails. Logging out of my desktop environment, Ctrl+Alt+F2, Ctrl+Alt+Backspace, chvt commands, all of these freeze my system. Reallybad is kernel 2.6.33.4 where glxgears has no consistent frame rate. It jumps around between 5fps and 60fps and all graphical programs are incredibly slow. This is in addition to the zapping issue described above. I am not sure why 2.6.33.4 is sometimes bad and sometimes reallybad. It might have to do with what USB devices are connected when it boots up. Please do not tell me to upgrade my userspace programs. I have tried every combination of xorg-server, mesa, xf86-video-ati and libdrm and none of them have any effect. The kernel is the ONLY package that changes how bad this bug is. Also please do not tell me to upgrade the kernel unless you are very sure that the version you are suggesting fixes this bug and you can tell me why it fixes it. I am not looking for a kernel that works. I KNOW which kernel works. I am trying to understand WHY it is the only one that works and hopefully help you fix this. Thank-you very much. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 28

[Bug 29495] New: [r300g] Shadowgrounds: character portraits rendered wrong
by bugzilla-daemon＠freedesktop.org 01 May '11

01 May '11

https://bugs.freedesktop.org/show_bug.cgi?id=29495 Summary: [r300g] Shadowgrounds: character portraits rendered wrong Product: Mesa Version: git Platform: Other URL: http://demofiles.linuxgamepublishing.com/shadowgrounds / OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/r300 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: sa(a)whiz.se Created an attachment (id=37778) --> (https://bugs.freedesktop.org/attachment.cgi?id=37778) Screenshot of the bug Character portraits (visible during dialogue segments) in the game Shadowgrounds are not rendered correctly. This is not a problem with r300c or softpipe. I'm using git master 8dd4308b5e29fd684d6e516161513d3045e5ff9e This is reproducible with the demo of the game. -- 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 31083] New: R600 misrenders irrlicht demo (01helloworld)
by bugzilla-daemon＠freedesktop.org 29 Apr '11

29 Apr '11

https://bugs.freedesktop.org/show_bug.cgi?id=31083 Summary: R600 misrenders irrlicht demo (01helloworld) Product: Mesa Version: 7.9 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: curaga(a)operamail.com Created an attachment (id=39738) --> (https://bugs.freedesktop.org/attachment.cgi?id=39738) Software renderer (correct output) The R600 driver misrenders the first demo of Irrlicht (irrlicht.sourceforge.net) when edited to use OpenGL instead of irrlicht's software renderer. The demo loads an animated md2 model with a bmp texture. Tested on Mesa 7.8.2 and 7.9, r600 fails on both, software renderer works on both. Screenshots attached. HW: Radeon HD4350 -- 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] drm: Recover DPMS properly after XRandr re-enablement
by Chris Wilson 18 Apr '11

18 Apr '11

From: Takashi Iwai <tiwai(a)suse.de> When the output is turned off via "xrandr --off" and re-enabled again with the same mode, drm doesn't reset DPMS, thus it results in a black screen. A typical example is something like: % xrandr --output LVDS1 --mode 1024x768 % xrandr --output VGA1 --mode 1024x768 % xrandr --output LVDS1 --off % xrandr --output LVDS1 --mode 1024x768 Also, there is another problem with DPMS: the sysfs entries don't match with the actual state. In the case above, LVDS1 shows always Off, while VGA1 shows On. A part of the cause is that there are (still) two places to keep the actual DPMS values. In dpms field of drm_connector and in the device property. Thus we need to sync between them. Another problem is that the DPMS state is always set to ON forcibly in drm_crtc_helper_set_config() (via commit bf9dc102e284a5aa78c73fc9d72e11d5ccd8669f). This results in another inconsistency. For recovering the DPMS, we need to set DPMS actaully ON there. This patch adds a new helper function to manage the drm_connector DPMS so that it can be called commonly in both places. Signed-off-by: Takashi Iwai <tiwai(a)suse.de> --- drivers/gpu/drm/drm_crtc.c | 25 ++++++++++++++++++------- drivers/gpu/drm/drm_crtc_helper.c | 7 ++++--- include/drm/drm_crtc.h | 1 + 3 files changed, 23 insertions(+), 10 deletions(-) diff --git a/drivers/gpu/drm/drm_crtc.c b/drivers/gpu/drm/drm_crtc.c index 2baa670..3a58337 100644 --- a/drivers/gpu/drm/drm_crtc.c +++ b/drivers/gpu/drm/drm_crtc.c @@ -2383,6 +2383,18 @@ int drm_mode_connector_update_edid_property(struct drm_connector *connector, } EXPORT_SYMBOL(drm_mode_connector_update_edid_property); +int drm_connector_set_dpms(struct drm_connector *connector, int mode) +{ + if (connector->funcs->dpms) + (*connector->funcs->dpms)(connector, mode); + connector->dpms = mode; + drm_connector_property_set_value(connector, + connector->dev->mode_config.dpms_property, + mode); + return 0; +} +EXPORT_SYMBOL(drm_connector_set_dpms); + int drm_mode_connector_property_set_ioctl(struct drm_device *dev, void *data, struct drm_file *file_priv) { @@ -2440,15 +2452,14 @@ int drm_mode_connector_property_set_ioctl(struct drm_device *dev, /* Do DPMS ourselves */ if (property == connector->dev->mode_config.dpms_property) { - if (connector->funcs->dpms) - (*connector->funcs->dpms)(connector, (int) out_resp->value); + drm_connector_set_dpms(connector, (int) out_resp->value); ret = 0; - } else if (connector->funcs->set_property) + } else if (connector->funcs->set_property) { ret = connector->funcs->set_property(connector, property, out_resp->value); - - /* store the property value if successful */ - if (!ret) - drm_connector_property_set_value(connector, property, out_resp->value); + /* store the property value if successful */ + if (!ret) + drm_connector_property_set_value(connector, property, out_resp->value); + } out: mutex_unlock(&dev->mode_config.mutex); return ret; diff --git a/drivers/gpu/drm/drm_crtc_helper.c b/drivers/gpu/drm/drm_crtc_helper.c index bede10a..fee755d 100644 --- a/drivers/gpu/drm/drm_crtc_helper.c +++ b/drivers/gpu/drm/drm_crtc_helper.c @@ -669,9 +669,10 @@ int drm_crtc_helper_set_config(struct drm_mode_set *set) } DRM_DEBUG_KMS("Setting connector DPMS state to on\n"); for (i = 0; i < set->num_connectors; i++) { - DRM_DEBUG_KMS("\t[CONNECTOR:%d:%s] set DPMS on\n", set->connectors[i]->base.id, - drm_get_connector_name(set->connectors[i])); - set->connectors[i]->dpms = DRM_MODE_DPMS_ON; + struct drm_connector *connector = set->connectors[i]; + DRM_DEBUG_KMS("\t[CONNECTOR:%d:%s] set DPMS on\n", connector->base.id, + drm_get_connector_name(connector)); + drm_connector_set_dpms(connector, DRM_MODE_DPMS_ON); } kfree(save_connectors); diff --git a/include/drm/drm_crtc.h b/include/drm/drm_crtc.h index 029aa68..c9a5a80 100644 --- a/include/drm/drm_crtc.h +++ b/include/drm/drm_crtc.h @@ -676,6 +676,7 @@ extern void drm_mode_set_crtcinfo(struct drm_display_mode *p, extern void drm_mode_connector_list_update(struct drm_connector *connector); extern int drm_mode_connector_update_edid_property(struct drm_connector *connector, struct edid *edid); +extern int drm_connector_set_dpms(struct drm_connector *connector, int mode); extern int drm_connector_property_set_value(struct drm_connector *connector, struct drm_property *property, uint64_t value); -- 1.7.3.1

3 3

[Bug 33755] New: System hangs with x-testing and gtkperf tests
by bugzilla-daemon＠freedesktop.org 18 Apr '11

18 Apr '11

https://bugs.freedesktop.org/show_bug.cgi?id=33755 Summary: System hangs with x-testing and gtkperf tests Product: Mesa Version: git Platform: x86 (IA32) OS/Version: All Status: NEW Severity: major Priority: high Component: Drivers/DRI/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: mrgkavitha(a)gmail.com Created an attachment (id=42746) --> (https://bugs.freedesktop.org/attachment.cgi?id=42746) Xorg log file KMS Driver Stack Details: ========================= 1) Kernel-2.6.35-22-generic-pae 2) Libdrm-2.4.21 3) Mesa-7.9-rc1 4) Xorg-server-1.9.0 5) ddx: xf86-video-ati-6.13.99 System Environment: =================== O.S. - Ubuntu-10.10(32 bit) ASIC – Juniper LE [HD5750] CPU - Intel(R) Core(TM) 2 CPU 6300 @1.86GHz Steps to Reproduce: =================== 1) Connect display: DFP 2) startx 3) Install phoronix test suite as below a.Down load test suite from the below location http://www.phoronix-test-suite.com/releases/repo/pts.debian/files/phoronix-… b.sudo dpkg -i phoronix-test-suite_2.8.2_all.deb c.Install any dependency related to PHP with synaptic 4) Run X-testing application as below using phoronix-test-suite FORCE_TIMES_TO_RUN=1 phoronix-test-suite run x-testing Observation: Test runs for some time and after that System gets hang. Keyboard and Mouse are not working but able to ping the system IP. Additional Information: ----------------------------------- -->Issue is also observed with Redwood LP -->Issue is also observed with gtkperf test [FORCE_TIMES_TO_RUN=1 phoronix-test-suite run gtkperf] -->Issue is not observed with Cedar Pro [Bass] ASIC -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 4

← Newer
1
...
11
12
13
14
15
16
17
...
46
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel January 2011