dri-devel June 2013

dri-devel@lists.freedesktop.org

132 participants
727 discussions

[Bug 52171] New: [gallium/r600/clover] Simple benchmarks failed to run
by bugzilla-daemon＠freedesktop.org 18 Nov '13

18 Nov '13

https://bugs.freedesktop.org/show_bug.cgi?id=52171 Bug #: 52171 Summary: [gallium/r600/clover] Simple benchmarks failed to run Classification: Unclassified Product: Mesa Version: git Platform: Other OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: alexxy(a)gentoo.org I get benchmarks from here http://www.bealto.com/gpu-benchmarks.html CPU ones runs fine while all gpu benchmarks failed with: Build failed, errors: clGetProgramInfo NUM_DEVICES failed HW is 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Turks [Radeon HD 6670] -- 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 65085] New: [radeonsi LLVM] Segfault during OpenCL kernel compilation
by bugzilla-daemon＠freedesktop.org 16 Nov '13

16 Nov '13

https://bugs.freedesktop.org/show_bug.cgi?id=65085 Priority: medium Bug ID: 65085 Assignee: dri-devel(a)lists.freedesktop.org Summary: [radeonsi LLVM] Segfault during OpenCL kernel compilation Severity: normal Classification: Unclassified OS: All Reporter: niels_ole(a)salscheider-online.de Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa Created attachment 79901 --> https://bugs.freedesktop.org/attachment.cgi?id=79901&action=edit Kernel that causes the segfault I get a segmentation fault in LLVM with Tom Stellard's recent radeonsi compute patches (http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20130520/175743…) with the attached kernel. I can work around the issue when executing the if-block in the kernel unconditionally or with the attached patch to LLVM. Desc.OpInfo[0].RegClass equals -1 when the segmentation fault occurs. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 31682] New: Radeon console output very slow with kms
by bugzilla-daemon＠bugzilla.kernel.org 15 Nov '13

15 Nov '13

https://bugzilla.kernel.org/show_bug.cgi?id=31682 Summary: Radeon console output very slow with kms Product: Drivers Version: 2.5 Kernel Version: 2.6.38 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: kurt(a)roeckx.be Regression: No Hi, When I try to use KMS, the console output is very slow. I've seen a lot of people complain about this, but I can't find any bug about this. It's not really usable when KMS is enabled. If I disable KMS (and use radeonfb), things work normally. It takes for instance about 1 second for me to just redraw the screen, while the same thing is _at least_ 10 times faster, probably more like 100, when KMS is disabled. When booting with KMS enabled I get this in dmesg: Mar 21 19:07:50 intrepid kernel: [ 8.735138] [drm] Initialized drm 1.1.0 20060810 Mar 21 19:07:50 intrepid kernel: [ 8.887517] [drm] radeon kernel modesetting enabled. Mar 21 19:07:50 intrepid kernel: [ 8.887709] radeon 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 Mar 21 19:07:50 intrepid kernel: [ 8.891920] [drm] initializing kernel modesetting (RV280 0x1002:0x5964). Mar 21 19:07:50 intrepid kernel: [ 8.892029] [drm] register mmio base: 0xFD400000 Mar 21 19:07:50 intrepid kernel: [ 8.892084] [drm] register mmio size: 65536 Mar 21 19:07:50 intrepid kernel: [ 8.896084] agpgart-amd64 0000:00:00.0: AGP 3.5 bridge Mar 21 19:07:50 intrepid kernel: [ 8.896339] agpgart-amd64 0000:00:00.0: putting AGP V3 device into 8x mode Mar 21 19:07:50 intrepid kernel: [ 8.896458] radeon 0000:01:00.0: putting AGP V3 device into 8x mode Mar 21 19:07:50 intrepid kernel: [ 8.896519] radeon 0000:01:00.0: GTT: 64M 0xF8000000 - 0xFBFFFFFF Mar 21 19:07:50 intrepid kernel: [ 8.896578] [drm] Generation 2 PCI interface, using max accessible memory Mar 21 19:07:50 intrepid kernel: [ 8.896638] radeon 0000:01:00.0: VRAM: 128M 0x00000000E8000000 - 0x00000000EFFFFFFF (128M used) Mar 21 19:07:50 intrepid kernel: [ 8.896714] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). Mar 21 19:07:50 intrepid kernel: [ 8.896772] [drm] Driver supports precise vblank timestamp query. Mar 21 19:07:50 intrepid kernel: [ 8.896866] [drm] radeon: irq initialized. Mar 21 19:07:50 intrepid kernel: [ 8.897063] [drm] Detected VRAM RAM=128M, BAR=128M Mar 21 19:07:50 intrepid kernel: [ 8.897123] [drm] RAM width 64bits DDR Mar 21 19:07:50 intrepid kernel: [ 8.897256] [TTM] Zone kernel: Available graphics memory: 1030408 kiB. Mar 21 19:07:50 intrepid kernel: [ 8.897314] [TTM] Initializing pool allocator. Mar 21 19:07:50 intrepid kernel: [ 8.897392] [drm] radeon: 128M of VRAM memory ready Mar 21 19:07:50 intrepid kernel: [ 8.897447] [drm] radeon: 64M of GTT memory ready. Mar 21 19:07:50 intrepid kernel: [ 8.899585] radeon 0000:01:00.0: WB disabled Mar 21 19:07:50 intrepid kernel: [ 8.900265] [drm] Loading R200 Microcode Mar 21 19:07:50 intrepid kernel: [ 9.381958] [drm] radeon: ring at 0x00000000F8001000 Mar 21 19:07:50 intrepid kernel: [ 9.382034] [drm] ring test succeeded in 1 usecs Mar 21 19:07:50 intrepid kernel: [ 9.384821] [drm] radeon: ib pool ready. Mar 21 19:07:50 intrepid kernel: [ 9.384959] [drm] ib test succeeded in 0 usecs Mar 21 19:07:50 intrepid kernel: [ 9.386362] [drm] Radeon Display Connectors Mar 21 19:07:50 intrepid kernel: [ 9.386417] [drm] Connector 0: Mar 21 19:07:50 intrepid kernel: [ 9.386469] [drm] VGA Mar 21 19:07:50 intrepid kernel: [ 9.386522] [drm] DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60 0x60 Mar 21 19:07:50 intrepid kernel: [ 9.386578] [drm] Encoders: Mar 21 19:07:50 intrepid kernel: [ 9.386630] [drm] CRT1: INTERNAL_DAC1 Mar 21 19:07:50 intrepid kernel: [ 9.386684] [drm] Connector 1: Mar 21 19:07:50 intrepid kernel: [ 9.386736] [drm] DVI-D Mar 21 19:07:50 intrepid kernel: [ 9.386787] [drm] HPD1 Mar 21 19:07:50 intrepid kernel: [ 9.386839] [drm] DDC: 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 Mar 21 19:07:50 intrepid kernel: [ 9.386895] [drm] Encoders: Mar 21 19:07:50 intrepid kernel: [ 9.386947] [drm] DFP1: INTERNAL_TMDS1 Mar 21 19:07:50 intrepid kernel: [ 9.387001] [drm] Connector 2: Mar 21 19:07:50 intrepid kernel: [ 9.387053] [drm] S-video Mar 21 19:07:50 intrepid kernel: [ 9.387105] [drm] Encoders: Mar 21 19:07:50 intrepid kernel: [ 9.387157] [drm] TV1: INTERNAL_DAC2 Mar 21 19:07:50 intrepid kernel: [ 9.800245] [drm] fb mappable at 0xE8040000 Mar 21 19:07:50 intrepid kernel: [ 9.800303] [drm] vram apper at 0xE8000000 Mar 21 19:07:50 intrepid kernel: [ 9.802396] [drm] size 7680000 Mar 21 19:07:50 intrepid kernel: [ 9.802448] [drm] fb depth is 24 Mar 21 19:07:50 intrepid kernel: [ 9.802500] [drm] pitch is 6400 Mar 21 19:07:50 intrepid kernel: [ 10.023003] Console: switching to colour frame buffer device 200x75 Mar 21 19:07:50 intrepid kernel: [ 10.139398] fb0: radeondrmfb frame buffer device Mar 21 19:07:50 intrepid kernel: [ 10.139400] drm: registered panic notifier Mar 21 19:07:50 intrepid kernel: [ 10.140945] [drm] Initialized radeon 2.8.0 20080528 for 0000:01:00.0 on minor 0 When KMS is disabled I see this instead: Mar 21 19:10:55 intrepid kernel: [ 9.011140] [drm] Initialized radeon 1.33.0 20080528 for 0000:01:00.0 on minor 0 [...] Mar 21 19:10:55 intrepid kernel: [ 13.332368] radeonfb: Found Intel x86 BIOS ROM Image Mar 21 19:10:55 intrepid kernel: [ 13.332430] radeonfb: Retrieved PLL infos from BIOS Mar 21 19:10:55 intrepid kernel: [ 13.332487] radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=200.00 Mhz, System=166.00 MHz Mar 21 19:10:55 intrepid kernel: [ 13.332556] radeonfb: PLL min 20000 max 40000 Mar 21 19:10:55 intrepid kernel: [ 13.684011] radeonfb: Monitor 1 type DFP found Mar 21 19:10:55 intrepid kernel: [ 13.684072] radeonfb: EDID probed Mar 21 19:10:55 intrepid kernel: [ 13.684124] radeonfb: Monitor 2 type CRT found Mar 21 19:10:55 intrepid kernel: [ 13.684178] radeonfb: EDID probed Mar 21 19:10:55 intrepid kernel: [ 13.747450] Console: switching to colour frame buffer device 200x75 Mar 21 19:10:55 intrepid kernel: [ 13.799573] radeonfb (0000:01:00.0): ATI Radeon 5964 "Yd" Kurt -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 7

[Bug 55941] New: Hybrid graphics i915/radeon. Switch to radeon results to black screen
by bugzilla-daemon＠bugzilla.kernel.org 13 Nov '13

13 Nov '13

https://bugzilla.kernel.org/show_bug.cgi?id=55941 Summary: Hybrid graphics i915/radeon. Switch to radeon results to black screen Product: Drivers Version: 2.5 Kernel Version: 3.8.4 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: damigos(a)freemail.gr Regression: No Created an attachment (id=96611) --> (https://bugzilla.kernel.org/attachment.cgi?id=96611) lspci I have installed Arch Linux on a Dell Inspiron R15 with hybrid Intel/AMD graphics. vga_switcheroo is enabled and I can control radeon power with "echo ON/OFF > /sys/kernel/debug/vgaswitcheroo/switch". But when I try to switch to radeon in console with "echo DIS > /sys/kernel/debug/vgaswitcheroo/switch" the screen turns off. I can switch back to intel with "echo IGD > /sys/kernel/debug/vgaswitcheroo/switch" by blind typing it, and then the screen turns back on. -- 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 8

[Bug 57921] New: NULL pointer dereference in radeon_bo_create
by bugzilla-daemon＠bugzilla.kernel.org 13 Nov '13

13 Nov '13

https://bugzilla.kernel.org/show_bug.cgi?id=57921 Summary: NULL pointer dereference in radeon_bo_create Product: Drivers Version: 2.5 Kernel Version: 3.9.0 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: luke-jr+linuxbugs(a)utopios.org CC: alexdeucher(a)gmail.com Regression: No Created an attachment (id=101041) --> (https://bugzilla.kernel.org/attachment.cgi?id=101041) Full dmesg This might be invalid, as I'm a kernel newbie trying to workaround a host issue with my hacky patch, but it *seems* to be unrelated to that issue. Any pointers would be welcome. [ 133.921546] BUG: unable to handle kernel NULL pointer dereference at 00000020 [ 133.922104] IP: [<f80efb94>] drm_pcie_get_speed_cap_mask+0x24/0xc0 [drm] [ 133.922104] *pde = 00000000 [ 133.922104] Oops: 0000 [#1] PREEMPT SMP [ 133.922104] Modules linked in: radeon(+) ipv6 hwmon drm_kms_helper ttm drm evdev 8250 serial_core sr_mod i2c_piix4 button i2c_algo_bit cdrom psmouse [last unloaded: radeon] [ 133.922104] Pid: 4983, comm: modprobe Not tainted 3.9.0-gentoo #5 Bochs Bochs [ 133.922104] EIP: 0060:[<f80efb94>] EFLAGS: 00010286 CPU: 0 [ 133.922104] EIP is at drm_pcie_get_speed_cap_mask+0x24/0xc0 [drm] [ 133.922104] EAX: f6a96000 EBX: f4073c30 ECX: 00000000 EDX: f4073c30 [ 133.922104] ESI: 00000000 EDI: f6b5b070 EBP: f4073c24 ESP: f4073c00 [ 133.922104] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 [ 133.922104] CR0: 8005003b CR2: 00000020 CR3: 361d8000 CR4: 000006d0 [ 133.922104] DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000 [ 133.922104] DR6: ffff0ff0 DR7: 00000400 [ 133.922104] Process modprobe (pid: 4983, ti=f4072000 task=f6b325d0 task.ti=f4072000) [ 133.922104] Stack: [ 133.922104] f4073c4c f8828415 00000001 f63ca614 00000001 00000000 00000000 f41e0000 [ 133.922104] ffffffff f4073c3c f886e79d 00001000 00000000 f41e0000 f41e0000 f4073c80 [ 133.922104] f886e8c0 00000000 f6b5b070 f4073c68 f8829403 00000001 00000004 00000000 [ 133.922104] Call Trace: [ 133.922104] [<f8828415>] ? radeon_bo_create+0x145/0x180 [radeon] [ 133.922104] [<f886e79d>] evergreen_pcie_gen2_enable+0x8d/0x1a0 [radeon] [ 133.922104] [<f886e8c0>] evergreen_startup+0x10/0x1970 [radeon] [ 133.922104] [<f8829403>] ? radeon_gart_table_vram_alloc+0x53/0x60 [radeon] [ 133.922104] [<f8853eb9>] ? r600_pcie_gart_init+0x59/0x60 [radeon] [ 133.922104] [<f887039c>] evergreen_init+0x17c/0x290 [radeon] [ 133.922104] [<f8813559>] radeon_device_init+0x559/0x610 [radeon] [ 133.922104] [<f8812180>] ? cail_mc_write+0x20/0x20 [radeon] [ 133.922104] [<f8814dd8>] radeon_driver_load_kms+0x78/0x120 [radeon] [ 133.922104] [<f80efd5b>] drm_get_pci_dev+0x12b/0x240 [drm] [ 133.922104] [<f88120e1>] radeon_pci_probe+0x81/0xa0 [radeon] [ 133.922104] [<c120efdb>] pci_device_probe+0x7b/0xc0 [ 133.922104] [<c129207c>] driver_probe_device+0x5c/0x1e0 [ 133.922104] [<c120e6da>] ? pci_match_device+0xaa/0xc0 [ 133.922104] [<c1292289>] __driver_attach+0x89/0x90 [ 133.922104] [<c1292200>] ? driver_probe_device+0x1e0/0x1e0 [ 133.922104] [<c1290a82>] bus_for_each_dev+0x42/0x70 [ 133.922104] [<c1291c7c>] driver_attach+0x1c/0x30 [ 133.922104] [<c1292200>] ? driver_probe_device+0x1e0/0x1e0 [ 133.922104] [<c129186c>] bus_add_driver+0xcc/0x220 [ 133.922104] [<c120ee90>] ? pci_dev_put+0x20/0x20 [ 133.922104] [<c1292715>] driver_register+0x65/0x130 [ 133.922104] [<c120f0be>] __pci_register_driver+0x2e/0x40 [ 133.922104] [<f80eff65>] drm_pci_init+0xf5/0x100 [drm] [ 133.922104] [<f88ba052>] radeon_init+0x52/0x6f [radeon] [ 133.922104] [<c100113f>] do_one_initcall+0x2f/0x170 [ 133.922104] [<c10d765e>] ? __vunmap+0x6e/0xd0 [ 133.922104] [<f88ba000>] ? 0xf88b9fff [ 133.922104] [<c1081ce4>] load_module+0x1ad4/0x2050 [ 133.922104] [<c10d5a93>] ? vmap_page_range_noflush+0x103/0x190 [ 133.922104] [<c11f83a0>] ? _copy_from_user+0x30/0x50 [ 133.922104] [<c10822da>] sys_init_module+0x7a/0xa0 [ 133.922104] [<c1397c60>] syscall_call+0x7/0xb [ 133.922104] Code: 90 90 90 90 90 90 90 55 89 e5 83 ec 24 89 5d f8 89 d3 89 75 fc c7 02 00 00 00 00 8b 80 f0 01 00 00 85 c0 74 10 8b 40 08 8b 70 1c <0f> b7 46 20 66 3d 66 11 75 0f b8 ea ff ff ff 8b 5d f8 8b 75 fc [ 133.922104] EIP: [<f80efb94>] drm_pcie_get_speed_cap_mask+0x24/0xc0 [drm] SS:ESP 0068:f4073c00 [ 133.922104] CR2: 0000000000000020 [ 133.977137] ---[ end trace 71ff26e878f5734b ]--- -- 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 6

[Bug 59101] New: Gnome shell crashes after sleep mode
by bugzilla-daemon＠bugzilla.kernel.org 13 Nov '13

13 Nov '13

https://bugzilla.kernel.org/show_bug.cgi?id=59101 Summary: Gnome shell crashes after sleep mode Product: Drivers Version: 2.5 Kernel Version: 3.9.4-200.fc18.x86_64 Platform: All OS/Version: Linux Tree: Fedora Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: cx42net(a)gmail.com Regression: No Hi! I opened a ticket at Gnome bugzilla about this crash, but it appears to be a problem regarding my driver from the graphic card : When I have Gnome-shell that crashes, I can close the session (via the Aww snap message) and re-open a session, I can then show dmesg which displays everytime this message : > [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12! I tried to install the proprietary drivers, but it's not supported by Fedora 18. For information, I work with a Dual Screen, and I'm using Fedora 18. If you need any more information, please ask :) For information, here's the ticket I opened at Gnome : https://bugzilla.gnome.org/show_bug.cgi?id=701248 Thanks. -- 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 6

[Bug 58671] New: Nvidia drivers fail compile
by bugzilla-daemon＠bugzilla.kernel.org 12 Nov '13

12 Nov '13

https://bugzilla.kernel.org/show_bug.cgi?id=58671 Summary: Nvidia drivers fail compile Product: Drivers Version: 2.5 Kernel Version: 3.10-rc* Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: Acidphase(a)gmail.com Regression: No Since 3.10-rc1 the proprietary nvidia drivers fail to build against the kernels rc1 and rc2. Attached is the build log. Running Gentoo x86_64 (amd64), Even though in this attempt I tried to merge the 319.17 version I had also tried previous versions with the same result. -- 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 4

[Bug 60929] New: [r600-llvm] mono games with opengl are blocking on start
by bugzilla-daemon＠freedesktop.org 11 Nov '13

11 Nov '13

https://bugs.freedesktop.org/show_bug.cgi?id=60929 Priority: medium Bug ID: 60929 Assignee: dri-devel(a)lists.freedesktop.org Summary: [r600-llvm] mono games with opengl are blocking on start Severity: normal Classification: Unclassified OS: All Reporter: lordheavym(a)gmail.com Hardware: Other Status: NEW Version: git Component: Drivers/DRI/R600 Product: Mesa Mono games using opengl (Rochard, Bastion, Splice, ...) are blocking on start when llvm is in use. The only way to make them start is to define R600_LLVM=0 * Mesa from git * llvm from tstellar repo * radeon HD6870 I've tried to trace through strace/MONO_LOG_LEVEL=debug/apitrace without much success. It seem (for bastion) always stuck in 'glXGetCurrentContext' -- You are receiving this mail because: You are the assignee for the bug.

1 28

[Bug 41079] New: xorg-r600: display (sometimes) doesn't get updated or only partially
by bugzilla-daemon＠freedesktop.org 03 Nov '13

03 Nov '13

https://bugs.freedesktop.org/show_bug.cgi?id=41079 Summary: xorg-r600: display (sometimes) doesn't get updated or only partially Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: debian(a)carbon-project.org Created an attachment (id=51451) --> (https://bugs.freedesktop.org/attachment.cgi?id=51451) Xorg.0.log from the R600G run (version: Mesa/4a96a02d) DDX: Mesa/Gallium/xorg-r600 (Git master/4a96a02d) X: 1.11.0 libdrm2: 2.4.26 This bug can be seen in many applications, e.g. on loading of a website in Iceweasel or in less, when displaying a text file. AFAIKT it's always reproducible in Konsole/less: 1. Open a text file. 2. Press End. Instead of immediately displaying the end of the file, nothing (visible) happens*, only when you press the up arrow (down arrow doesn't work for me), the display gets updated and you see almost the end of the file (except the last line due to the up arrow key depression). * The blinking cursor gets displayed in the middle of the file name in the lower left corner. Again (as with bug #40986), no screenshot possible, because as soon as I press Print, the screen also gets updated and the updated screen ends up in the screenshot. Please let me know, when you need more information. -- 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 40986] New: xorg-r600: graphical glitches on cursor display
by bugzilla-daemon＠freedesktop.org 03 Nov '13

03 Nov '13

https://bugs.freedesktop.org/show_bug.cgi?id=40986 Summary: xorg-r600: graphical glitches on cursor display 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: debian(a)carbon-project.org Created an attachment (id=51309) --> (https://bugs.freedesktop.org/attachment.cgi?id=51309) X.org Log of the R600G run Git snapshot of: Mesa/ee09c1e1 I've tested Mesa's r600 DDX (xorg state-tracker) with X.org 1.11.0 and KDE 4.6.5. Immediately after KDM is launched, the mouse cursor is distorted (wrong proportions, longer than wide) and is overlayed with a blue strip pattern (horizontal) in a rather large square area around the actual cursor. Underneath the distorted cursor is visible. There are further graphical glitches (like when you open something in less, Pos1 and End seem to have no effect, only when you press an arrow key, the display is updated partially, after the second arrow key press, you get a full update, waiting doesn't help) or slow reaction to pressing keys (entering something takes like a felt extra second per key, ie. between pressing the key and seeing the result on screen), but I guess those are different bugs, right? If you need further information, just let me know. -- 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

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel June 2013