dri-devel October 2011

dri-devel@lists.freedesktop.org

82 participants
530 discussions

[Bug 42117] New: r200 driver performance, ums, all mesa versions from 7.6
by bugzilla-daemon＠freedesktop.org 03 Nov '17

03 Nov '17

https://bugs.freedesktop.org/show_bug.cgi?id=42117 Bug #: 42117 Summary: r200 driver performance, ums, all mesa versions from 7.6 Classification: Unclassified Product: Mesa Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/DRI/r200 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: majkell10(a)interia.pl With disabled ModeSetting, performance in some 3d applications drop almost to zero. glxgears runs flawlessly, few maps in openarena is unplayable, extremetuxracer is unplayable. oprofile with tuxracer: CPU: Athlon, speed 1399.45 MHz (estimated) Counted CPU_CLK_UNHALTED events (Cycles outside of halt state) with a unit mask of 0x00 (No unit mask) count 100000 samples % symbol name 146220 16.6991 sample_lambda_2d 123695 14.1267 fetch_texel_2d_f_argb8888 102183 11.6699 sample_linear_2d 86150 9.8388 linear_texel_locations.clone.23 79573 9.0877 interpolate_texcoords 69939 7.9874 _swrast_fog_rgba_span 55210 6.3053 _swrast_texture_span 54151 6.1843 _swrast_compute_lambda 50989 5.8232 radeonReadDepthSpan_z24_s8 21567 2.4631 radeonReadRGBASpan_ARGB8888 11802 1.3479 radeonWriteRGBASpan_ARGB8888 I've tested almost all mesa versions from 7.6 to 7.11, unsuccessfully. With mesa 7.5 all works great. Mesa 7.6.1 compiled with folders radeon and r200 copied from 7.5.2, also works great. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 19

[Bug 29322] New: Software rendering with UMS on radeon 9000 AGP (rv250)
by bugzilla-daemon＠freedesktop.org 03 Nov '17

03 Nov '17

https://bugs.freedesktop.org/show_bug.cgi?id=29322 Summary: Software rendering with UMS on radeon 9000 AGP (rv250) Product: Mesa Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/r200 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: support.intranet(a)libero.it Created an attachment (id=37460) --> (https://bugs.freedesktop.org/attachment.cgi?id=37460) dmesg Booting with radeon.modeset=0 (kernel 2.6.34.1) makes every 3D app (except from glxgears and OpenBVE so far) run in software rendering, at about 0.2 fps. With KMS 3d works in hardware, but is very sluggish (together with 2D). This happens with mesa 7.7 through git. -- 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 37696] New: [RADEON:KMS:PLL] frequent colored lines appear on screen
by bugzilla-daemon＠freedesktop.org 17 Oct '17

17 Oct '17

https://bugs.freedesktop.org/show_bug.cgi?id=37696 Summary: [RADEON:KMS:PLL] frequent colored lines appear on screen Product: DRI Version: unspecified Platform: x86-64 (AMD64) OS/Version: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: roysjosh(a)gmail.com Hello, I'm back again! This bug is about the same hardware as in https://bugs.freedesktop.org/show_bug.cgi?id=19960 . ASUS monitor VH226H, ASUS motherboard M3A78-E, HD3200 (rs780). 01:05.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon HD 3200 Graphics [1002:9610] (prog-if 00 [VGA controller]) I just upgraded from f14 to f15 (2.6.38.6-27.fc15.x86_64) and some frequently occurring but not frequent in number colored lines have appeared on my screen... they don't necessarily go all the way across the screen either. I grabbed the "good" registers from bug 19960 and diff'd them to the current regs: [...] 258c258 < 00000404 00000002 (2) --- > 00000404 00000003 (3) 269c269 < 00000430 00910032 (9502770) --- > 00000430 00da0030 (14286896) 275c275 < 00000448 159ec704 (362727172) --- > 00000448 1593a704 (361998084) 278c278 < 00000454 6c012003 (1812013059) --- > 00000454 6c010003 (1812004867) [...] Settings these regs gets rid of the red/white/blue/etc lines: # ./avivotool regset 0x404 0x2 ; ./avivotool regset 0x430 0x910032 OLD: 0x404 (0404) 0x00000003 (3) NEW: 0x404 (0404) 0x00000002 (2) OLD: 0x430 (0430) 0x00da0030 (14286896) NEW: 0x430 (0430) 0x00910032 (9502770) And 0x43c was already set to 7: # ./avivotool regmatch 0x43c 0x43c 0x00000007 (7) Thanks! -- 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 29725] New: EXT_framebuffer_object extension with free radeon driver
by bugzilla-daemon＠freedesktop.org 08 Oct '17

08 Oct '17

https://bugs.freedesktop.org/show_bug.cgi?id=29725 Summary: EXT_framebuffer_object extension with free radeon driver Product: Mesa Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: bioinfornatics(a)gmail.com hi, i am fedora packager and i package this game: http://os.wildfiregames.com/ i see for radeon driver a crash because with EXT_framebuffer_object extension with free radeon driver. beta rpm can be found here: http://koji.fedoraproject.org/koji/taskinfo?taskID=2415654 rpm -qa | grep mesa mesa-dri-drivers-7.8.1-8.fc13.x86_64 mesa-libGL-devel-7.8.1-8.fc13.x86_64 mesa-libGL-7.8.1-8.fc13.x86_64 mesa-debuginfo-7.8.1-8.fc13.x86_64 mesa-libGLU-devel-7.8.1-8.fc13.x86_64 mesa-libGLU-7.8.1-8.fc13.x86_64 -- 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 41503] New: Oops with Linux 3.0.0 and radeon driver: shmem_truncate_range
by bugzilla-daemon＠freedesktop.org 05 Aug '17

05 Aug '17

https://bugs.freedesktop.org/show_bug.cgi?id=41503 Summary: Oops with Linux 3.0.0 and radeon driver: shmem_truncate_range Product: DRI Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: paulepanter(a)users.sourceforge.net Created an attachment (id=52032) --> (https://bugs.freedesktop.org/attachment.cgi?id=52032) Photo of monitor displaying Kernel messages like call trace This report is a follow up for my message sent to the mailing list [1]. Unfortunately the Bugzilla instance of Linux [2] is still down due to the security breach in August and therefore I am reporting this issue here in the FreeDesktop Bugzilla [3]. Having a lot of windows open using the Awesome window manager [4] the X server crashed printing the following to the monitor. Please see the attached image for the complete message. Pid: 1503, comm: Xorg Tainted: G C 3.0.0-1-amd64 #1 LENOVO INVALID/Bali […] Process Xorg (pid: 1503, threadinfo ffff88010c208000, task ffff88011950d790 Stack: […] Call Trace: pagevec_move_tail+0x30/0x30 shmem_evict_inode+0x58/0xea evict+0x7b/0x119 dentry_kill+0x136/0x155 dput+0xdb/0xea fput+0x17b/0x1a2 remove_vma+0x3d/0x71 do_munmap+0x2da/0x2f3 sys_shmdt+0x9a/0x127 system_call_fastpath+0x16/0x1b Code: 00 00 00 00 00 48 8b 94 24 a0 00 00 00 48 8d 45 28 48 ff 44 24 10 48 c7 44 24 50 00 00 … RIP […] shmem_truncate_range+0x45c/0x6a1 RSP <ffff88010c209cf8> Unfortunately for debugging this issue this is the first time it happened and the issue is not reproducible. Debian Wheezy/testing is running on this system with Linux 3.0.0-3 [5] and the (non-free) firmware for the graphics card. [1] http://lists.freedesktop.org/archives/dri-devel/2011-October/015011.html [2] https://bugzilla.kernel.org/l [3] https://bugs.freedesktop.org/ [4] http://awesome.naquadah.org/ [5] http://packages.debian.org/changelogs/pool/main/l/linux-2.6/linux-2.6_3.0.0… [6] http://packages.debian.org/changelogs/pool/non-free/f/firmware-nonfree/firm… -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 3

[Bug 37724] New: occlusion queries are messed up in ut2004 (regression, bisected)
by bugzilla-daemon＠freedesktop.org 11 Mar '17

11 Mar '17

https://bugs.freedesktop.org/show_bug.cgi?id=37724 Summary: occlusion queries are messed up in ut2004 (regression, bisected) Product: Mesa Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r300 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: aaalmosss(a)gmail.com The majority of the 3d objects disappear periodically since this commit: f76787b3eae3f0b8af839fabfb24b57715a017f6 is the first bad commit commit f76787b3eae3f0b8af839fabfb24b57715a017f6 Author: Marek Olšák <maraeo(a)gmail.com> Date: Sun May 29 04:36:36 2011 +0200 r300g: fix occlusion queries when depth test is disabled or zbuffer is missing From now on, depth test is always enabled in hardware. If depth test is disabled in Gallium, the hardware Z function is set to ALWAYS. If there is no zbuffer set, the colorbuffer0 memory is set as a zbuffer to silence the CS checker. This fixes piglit: - occlusion-query-discard - NV_conditional_render/bitmap - NV_conditional_render/drawpixels - NV_conditional_render/vertex_array :040000 040000 baeff41ffed8952cbb1666d04941c6d5d01ca4fc cdb64f4b684804b818df4b65c04109eaad568e11 M src -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 22

[Bug 34643] New: ut2004/doom3 looping in submenu on r300g/PageFlip
by bugzilla-daemon＠freedesktop.org 19 Mar '16

19 Mar '16

https://bugs.freedesktop.org/show_bug.cgi?id=34643 Summary: ut2004/doom3 looping in submenu on r300g/PageFlip Product: Mesa Version: git Platform: Other OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r300 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: krzysztof.krakowiak(a)gmail.com Created an attachment (id=43736) --> (https://bugs.freedesktop.org/attachment.cgi?id=43736) gdb/ut2k4 output and backraces. ut2004(32/64bit) and doom3(32bit) are looping everytime in submenu on r300g/PageFlip. I believe that bug occured during last two weeks, but bisecting would be hard, because I was bisecting for: https://bugs.freedesktop.org/show_bug.cgi?id=34418 And everytime supertuxkart wasnt working, ut2k4 also and vice versa, altough bugs were definitely different. Now previous bug is fixed(which affected only 64bit apps), but ut2004/doom3 got very similar behaviour(like looped video tape or something, moving forward and back), similar spam in console, but a bit different at output. Disabling PageFLip fixes this problem definitely, but I was happpy pflip user from a long time. Kernel is fresh D-R-T, DDX/DRM/Mesa from master. --- UT2004 dmesg --- [...] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0xe [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x1f [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0xe [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x1f [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! [...] --- EOF UT2004 dmesg --- --- UT2004 gdb output/backtrace --- [...] [Thread 0x7fffe50cd700 (LWP 5934) exited] [New Thread 0x7fffe50cd700 (LWP 5935)] [Thread 0x7fffe50cd700 (LWP 5935) exited] [New Thread 0x7fffe50cd700 (LWP 5936)] [...] [Thread 0x7fffe50cd700 (LWP 6540) exited] [New Thread 0x7fffe50cd700 (LWP 6541)] radeon: The kernel rejected CS, see dmesg for more information. [Thread 0x7fffe50cd700 (LWP 6541) exited] [...] Program received signal SIGINT, Interrupt. 0x00007ffff6e0a1f3 in poll () from /lib64/libc.so.6 (gdb) bt #0 0x00007ffff6e0a1f3 in poll () from /lib64/libc.so.6 #1 0x00007ffff65eac6a in ?? () from /usr/lib64/libxcb.so.1 #2 0x00007ffff65ec2ff in xcb_wait_for_reply () from /usr/lib64/libxcb.so.1 #3 0x00007ffff684392d in _XReply () from /usr/lib64/libX11.so.6 #4 0x00007fffe6c1748c in DRI2GetBuffersWithFormat () from /opt/xorg/lib64/libGL.so.1 #5 0x00007fffe6c14bf9 in dri2GetBuffersWithFormat () from /opt/xorg/lib64/libGL.so.1 #6 0x00007fffe56de4d8 in dri2_allocate_textures () from /opt/xorg/lib64/dri/gallium/r300_dri.so #7 0x00007fffe56dfb77 in dri_st_framebuffer_validate () from /opt/xorg/lib64/dri/gallium/r300_dri.so #8 0x00007fffe573f132 in st_framebuffer_validate () from /opt/xorg/lib64/dri/gallium/r300_dri.so #9 0x00007fffe5740916 in st_manager_validate_framebuffers () from /opt/xorg/lib64/dri/gallium/r300_dri.so #10 0x00007fffe58e3c1e in st_validate_state () from /opt/xorg/lib64/dri/gallium/r300_dri.so #11 0x00007fffe58ebb3a in st_Clear () from /opt/xorg/lib64/dri/gallium/r300_dri.so #12 0x0000000000d291d9 in FOpenGLRenderInterface::Clear(int, FColor, int, float, int, unsigned int) () #13 0x000000000069d234 in UGameEngine::Draw(UViewport*, int, unsigned char*, int*) () #14 0x0000000000d1d106 in USDLViewport::Repaint(int) () #15 0x0000000000d1ab09 in USDLClient::Tick() () #16 0x00000000006a0f54 in UGameEngine::Tick(float) () #17 0x000000000053d2a3 in CMainLoop::RunLoop() () #18 0x000000000053344f in ?? () #19 0x000000000052f1a0 in main () --- UT2004 gdb output/backtrace --- --- Doom3 output --- [...] radeon: The kernel rejected CS, see dmesg for more information. radeon: The kernel rejected CS, see dmesg for more information [...] --- EOF Doom3 output --- TIP: For full logs, look into attachements (but nothing special in xorg.log) -- 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 40024] New: Power management does not work on ATI Mobility Radeon 9700
by bugzilla-daemon＠freedesktop.org 26 Feb '16

26 Feb '16

https://bugs.freedesktop.org/show_bug.cgi?id=40024 Summary: Power management does not work on ATI Mobility Radeon 9700 Product: Mesa Version: 7.10 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: robegrassi(a)gmail.com Created an attachment (id=50139) --> (https://bugs.freedesktop.org/attachment.cgi?id=50139) output of dmesg Hi, I have an old Asus laptop with a Mobility Radeon 9700 card: $ lspci -nn | grep VGA 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10] [1002:4e50] I am using Xubuntu 11.04 with KMS and Gallium driver. I would like to set the card to a lower power state because the fan goes often high and the laptop gets hot. The problem is that these three files are missing: cat: /sys/class/drm/card0/device/power_method: No such file or directory cat: /sys/class/drm/card0/device/power_profile: No such file or directory cat: /sys/kernel/debug/dri/0/radeon_pm_info: No such file or directory Does it mean that my card does not support power management? Thank you very much for your help, Roberto -- 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 36817] New: RV670 - Kernel fails to enable acceleration when RAM greater than 32-bit limit
by bugzilla-daemon＠freedesktop.org 26 Feb '16

26 Feb '16

https://bugs.freedesktop.org/show_bug.cgi?id=36817 Summary: RV670 - Kernel fails to enable acceleration when RAM greater than 32-bit limit Product: DRI Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: reg(a)achart.me.uk I sure hope I'm in the right place... Using a Radeon HD3870 that works fine under Windows (64-bit). After a supposed initial success using a pre-release version of KMS drivers (which may be a red herring), I have been unable to get 3D acceleration on any Ubuntu release from Lucid, unless I use a non-PAE kernel (I have 4GB RAM). My Ubuntu bug ticket (including logs) is here: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/574884 Another bug that looks similar: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/657576 A similar looking bug with a similar workaround (which I'll shortly try on mine) on SUSE: http://web.archiveorange.com/archive/v/wmeLDauZzOL6SFQx1uKY -- 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 36598] New: [RS880] Slow resume from suspend generates kernel oops
by bugzilla-daemon＠freedesktop.org 26 Feb '16

26 Feb '16

https://bugs.freedesktop.org/show_bug.cgi?id=36598 Summary: [RS880] Slow resume from suspend generates kernel oops Product: DRI Version: XOrg CVS Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: steve(a)stevemurphy.org Created an attachment (id=46075) --> (https://bugs.freedesktop.org/attachment.cgi?id=46075) dmesg output for boot and suspend, showing the issue around 78.3 I'm forwarding this bug from ubuntu - https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/764788 Problem] Resume from suspend triggers a kernel oops due to the radeon kms module taking more than 10 seconds to resume [Discussion] When resuming from the suspend state, a popup box is displayed indicating an error has occured and "Your system might become unstable now and might need to be restarted.". In the dmesg output, the following lines are present before the kernel oops, showing that the radeon driver took 11408.919 msecs to resume and the kernel oops is due to resume taking longer than 10 seconds total (11430 msecs). Interesting lines in the dmesg output when the error occurs are below (with kernel.drm=0x04 set, adding a bit of verbosity when the radeon driver is restoring): [ 69.792851] PM: resume of drv:scsi_disk dev:2:0:0:0 complete after 2644.379 msecs [ 70.122093] [drm:output_poll_execute], [CONNECTOR:15:VGA-1] status updated from 2 to 2 [ 70.124058] [drm:radeon_atombios_connected_scratch_regs], DFP1 disconnected [ 70.124062] [drm:output_poll_execute], [CONNECTOR:17:HDMI-A-1] status updated from 2 to 2 [ 71.960104] [drm:radeon_atom_encoder_dpms], encoder dpms 21 to mode 3, devices 00000001, active_devices 00000000 [ 71.960113] [drm:radeon_atom_encoder_dpms], encoder dpms 30 to mode 3, devices 00000008, active_devices 00000000 [ 71.960136] [drm:radeon_compute_pll_avivo], 7187, pll dividers - fb: 130.5 ref: 2, post 13 [ 71.980174] [drm:drm_crtc_helper_set_mode], [ENCODER:12:LVDS-12] set [MODE:30:1366x768] [ 76.950136] [drm:avivo_crtc_load_lut], 0 [ 76.950200] [drm:radeon_atom_encoder_dpms], encoder dpms 31 to mode 0, devices 00000002, active_devices 00000002 [ 76.960133] [drm:radeon_atom_encoder_dpms], encoder dpms 31 to mode 3, devices 00000002, active_devices 00000002 [ 78.303704] [drm:radeon_atom_encoder_dpms], encoder dpms 21 to mode 3, devices 00000001, active_devices 00000000 [ 78.303713] [drm:radeon_atom_encoder_dpms], encoder dpms 30 to mode 3, devices 00000008, active_devices 00000000 [ 78.303734] [drm:avivo_crtc_load_lut], 0 [ 78.303790] [drm:radeon_atom_encoder_dpms], encoder dpms 31 to mode 0, devices 00000002, active_devices 00000002 [ 78.310132] PM: resume of drv:radeon dev:0000:01:05.0 complete after 11408.919 msecs [ 78.310148] PM: resume of drv:drm dev:controlD64 complete after 8513.702 msecs [ 78.310173] PM: resume of devices complete after 11409.422 msecs [ 78.330262] PM: resume devices took 11.430 seconds [ 78.330265] ------------[ cut here ]------------ [ 78.330272] WARNING: at /build/buildd/linux-2.6.38/kernel/power/suspend_test.c:53 suspend_test_finish+0x86/0x90() [ 78.330274] Hardware name: 1215T [ 78.330277] Component: resume devices, time: 11430 Upon investigating further, it looks like portions of the the following workarounds were discovered that allow resume from suspend to work as expected, by avoid the radeon driver: [Workarounds] 1. Add "nomodeset" to the linux command line in grub 2. Use the proprietary FGLRX driver. [System Environment] ASUS 1215T running a fresh install of 11.04 beta or 11.04 beta2. -- 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

← Newer
1
...
8
9
10
11
12
13
14
...
53
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel October 2011