dri-devel April 2011

dri-devel@lists.freedesktop.org

93 participants
440 discussions

[Bug 32350] New: Radeon laptop screen goes crazy after unplugging hardware
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=32350 Summary: Radeon laptop screen goes crazy after unplugging hardware 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: evillanueva(a)roundbox.com Created an attachment (id=41066) --> (https://bugs.freedesktop.org/attachment.cgi?id=41066) Xorg log Using Fedora 14 and radeon DRI driver. After unplugging the power adapter the screen starts flashing corrupted video. Looks like stair stepping effect. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 38

[Bug 32325] New: [radeon] DRM version check only looks at minor number.
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=32325 Summary: [radeon] DRM version check only looks at minor number. Product: Mesa Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: rankincj(a)googlemail.com Created an attachment (id=41020) View: https://bugs.freedesktop.org/attachment.cgi?id=41020 Review: https://bugs.freedesktop.org/review?bug=32325&attachment=41020 [PATCH] Enable HyperZ and microtiling for R100 if DRM >= v2.x I have noticed that Mesa 7.9 prints the following message with a recent 2.6.3x kernel: "DRM version 1.6 too old to support HyperZ, disabling." The reason for this is that the DRM in the 2.6.36 kernel is v2.6: [drm] Initialized radeon 2.6.0 20080528 for 0000:01:00.0 on minor 0 and Mesa only checks the minor version number. (Assuming that the major version number is always 1.) I have attached a patch that will also enable both HyperZ and texture microtiling(?) on R100 if DRM >= v2.x. -- 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 30924] New: incorrect checking of return value of driAllocateTexture
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=30924 Summary: incorrect checking of return value of driAllocateTexture Product: Mesa Version: 7.8 Platform: All OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: ssb(a)umn.edu driAllocateTexture returns -1 for failure to allocate the texture. The code checks against NULL. [driAllocateTexture:631] unable to allocate texture Backtrace: 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80ef15b] 1: /usr/bin/X (0x8048000+0x5cff5) [0x80a4ff5] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xffffe410] 3: /usr/lib/dri/radeon_dri.so (0xb433a000+0x381bf) [0xb43721bf] 4: /usr/lib/libdrm_radeon.so.1 (radeon_cs_emit+0x14) [0xb70973d4] 5: /usr/lib/dri/radeon_dri.so (0xb433a000+0x35c78) [0xb436fc78] 6: /usr/lib/dri/radeon_dri.so (0xb433a000+0x35d2c) [0xb436fd2c] 7: /usr/lib/dri/radeon_dri.so (0xb433a000+0x35f32) [0xb436ff32] 8: /usr/lib/dri/radeon_dri.so (0xb433a000+0x17e0a) [0xb4351e0a] 9: /usr/lib/dri/radeon_dri.so (0xb433a000+0x75ccb) [0xb43afccb] 10: /usr/lib/dri/radeon_dri.so (0xb433a000+0x17b3c8) [0xb44b53c8] 11: /usr/lib/xorg/modules/extensions/libglx.so (0xb71b7000+0x83a0) [0xb71bf3a0] 12: /usr/lib/xorg/modules/extensions/libglx.so (0xb71b7000+0x31c45) [0xb71e8c45] 13: /usr/lib/xorg/modules/extensions/libglx.so (0xb71b7000+0x3645e) [0xb71ed45e] 14: /usr/bin/X (0x8048000+0x23707) [0x806b707] 15: /usr/bin/X (0x8048000+0x1dbb5) [0x8065bb5] 16: /lib/libc.so.6 (__libc_start_main+0xe6) [0xb7333a66] 17: /usr/bin/X (0x8048000+0x1d781) [0x8065781] Segmentation fault at address 0x14 -- 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

[PATCH wq#for-linus] drm: fix a fallout from slow-work -> wq conversion
by Tejun Heo 19 Jun '18

19 Jun '18

Commit 991ea75c (drm: use workqueue instead of slow-work), which made drm to use wq instead of slow-work, didn't account for the return value difference between delayed_slow_work_enqueue() and queue_delayed_work(). The former returns 0 on success and -errno on failures while the latter never fails and only uses the return value to indicate whether the work was already pending or not. This misconversion triggered spurious error messages. Remove the now unnecessary return value check and error message. Signed-off-by: Tejun Heo <tj(a)kernel.org> Reported-by: Markus Trippelsdorf <markus(a)trippelsdorf.de> Cc: David Airlie <airlied(a)linux.ie> Cc: dri-devel(a)lists.freedesktop.org --- Markus, it's almost trivial but it would be great if you can test this one too. David, may I route this wq#for-linus? Thanks. drivers/gpu/drm/drm_crtc_helper.c | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/drivers/gpu/drm/drm_crtc_helper.c b/drivers/gpu/drm/drm_crtc_helper.c index 4598130..211ed7e 100644 --- a/drivers/gpu/drm/drm_crtc_helper.c +++ b/drivers/gpu/drm/drm_crtc_helper.c @@ -839,7 +839,6 @@ static void output_poll_execute(struct work_struct *work) struct drm_connector *connector; enum drm_connector_status old_status, status; bool repoll = false, changed = false; - int ret; mutex_lock(&dev->mode_config.mutex); list_for_each_entry(connector, &dev->mode_config.connector_list, head) { @@ -874,11 +873,8 @@ static void output_poll_execute(struct work_struct *work) dev->mode_config.funcs->output_poll_changed(dev); } - if (repoll) { - ret = queue_delayed_work(system_nrt_wq, delayed_work, DRM_OUTPUT_POLL_PERIOD); - if (ret) - DRM_ERROR("delayed enqueue failed %d\n", ret); - } + if (repoll) + queue_delayed_work(system_nrt_wq, delayed_work, DRM_OUTPUT_POLL_PERIOD); } void drm_kms_helper_poll_disable(struct drm_device *dev)

4 4

[Bug 28771] New: Vsync always on
by bugzilla-daemon＠freedesktop.org 12 Jun '18

12 Jun '18

https://bugs.freedesktop.org/show_bug.cgi?id=28771 Summary: Vsync always on Product: Mesa Version: git Platform: Other 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 With kernel 2.6.35, there doesn't seem to be a way to turn off vsync/vblank. E.g. "vblank_mode=0 glxgears" has no effect. This seems to be the same for both r300c and r300g. System environment: -- system architecture: 32-bit -- Linux distribution: Debian unstable -- GPU: RV570 -- Model: Asus EAX1950Pro 256MB -- Display connector: DVI -- xf86-video-ati: 801e83227a59a29eea425ea612083bbf2b536c30 -- xserver: 1.8.1.901 -- mesa: a5c44986a3f19936df448fe4ae47ca77ece9b0ce -- drm: 6ea2bda5f5ec8f27359760ce580fdad3df0464df -- kernel: 2.6.35-rc3 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 38

[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 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 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 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

[Bug 35988] New: Power management not working on ATI M92 LP [Mobility Radeon HD 4300]
by bugzilla-daemon＠freedesktop.org 26 Feb '16

26 Feb '16

https://bugs.freedesktop.org/show_bug.cgi?id=35988 Summary: Power management not working on ATI M92 LP [Mobility Radeon HD 4300] 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: s.j.turner(a)uqconnect.net A launchpad user reports "If I deactivate the ATI restricted driver, and then restart my computer, GPU temp is between 70-80 degrees Celsius instead of the usual 40-50, without doing anything, no application running, no effects." lspci -nn | grep VGA 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc M92 LP [Mobility Radeon HD 4300 Series] [1002:9552] MachineType: Hewlett-Packard HP ProBook 4710s This was originally reported on Ubuntu 9.10 "Karmic Koala" with a 2.6.31-based kernel (which of course does not have power management support), but persists on an Ubuntu 11.04 "Natty Narwhal" pre-release with a 2.6.38-based kernel. The problem is that this user reports "I've tried setting the power (management) profile settings and dynpm, but nothing has changed, still running above 70 degrees Celsius." -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 11

← Newer
1
2
3
4
5
6
7
8
9
...
44
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel April 2011