dri-devel June 2013

dri-devel@lists.freedesktop.org

132 participants
727 discussions

[Bug 40425] New: Maker3D graphics bugs with opensource ati drivers
by bugzilla-daemon＠freedesktop.org 26 Feb '16

26 Feb '16

https://bugs.freedesktop.org/show_bug.cgi?id=40425 Summary: Maker3D graphics bugs with opensource ati drivers Product: Mesa Version: unspecified Platform: All OS/Version: Linux (All) Status: NEW Severity: minor Priority: medium Component: Drivers/DRI/r300 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: gerilegend(a)freemail.hu Created an attachment (id=50619) --> (https://bugs.freedesktop.org/attachment.cgi?id=50619) gallium (left) - catalyst (right) These bugs appear with RadeonHD 3200 series IGP on linux. look the attached image for explanation. operating system: ubuntu 11.04 (built in graphics driver) demo version: http://ftp.sth.sze.hu/~andras/Maker3D_demo.zip homepage: http://Maker3D.tk -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 7

[Bug 46866] New: Piglit:Multiple failures observed while running quick-driver.tests
by bugzilla-daemon＠freedesktop.org 26 Feb '16

26 Feb '16

https://bugs.freedesktop.org/show_bug.cgi?id=46866 Bug #: 46866 Summary: Piglit:Multiple failures observed while running quick-driver.tests Classification: Unclassified Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: major Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: hysvats(a)gmail.com Driver Stack Details: ========================= 1) Kernel-3.0.0-12-generice-pae 2) drm-2.4.31 3) Mesa-8.1-devel (git-897af1d) 4) Xorg-server-1.11.4 5) xf86-video-ati- master System Environment: =================== Asic : EG CedarPro O.S. : Ubuntu-11.10 (32 bit) Processor : AMD Athlon(tm) 64 X2 @ 1 GHz Memory : 2 GB Steps to Reproduce: =================== 1) Install piglit from git clone git://anongit.freedesktop.org/git/piglit 2) #./piglit-run.py tests/quick-driver.tests results/quick-driver.results #./piglit-summary-html.py summary/quick-driver results/quick-driver.results Observation : Multiple failures observed while running quick-driver.tests =========== -- 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 28943] New: Red=cyan? Why?
by bugzilla-daemon＠freedesktop.org 26 Feb '16

26 Feb '16

https://bugs.freedesktop.org/show_bug.cgi?id=28943 Summary: Red=cyan? Why? Product: Mesa Version: unspecified Platform: Other OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/MGA AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: eblanca76(a)users.sourceforge.net I'm having a strange color replacement in ubuntu 10.04. Hardware is matrox g550 agp dual head, 32 MB. Well, running silent hill 2 in wine, I have cyan blood when it should be red! Here you can read the (closed) bug: http://bugs.winehq.org/show_bug.cgi?id=17741 (there are a lot of details about the bug) I thought it was due to wine but it isn't, so it was closed as invalid. Please note, this `bug' appears since a couple of years ago and even now, with mesa 7.7.1. -- 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 66352] New: GPU lockup in L4D2 on TURKS with HyperZ
by bugzilla-daemon＠freedesktop.org 19 Feb '16

19 Feb '16

https://bugs.freedesktop.org/show_bug.cgi?id=66352 Priority: medium Bug ID: 66352 Assignee: dri-devel(a)lists.freedesktop.org Summary: GPU lockup in L4D2 on TURKS with HyperZ Severity: normal Classification: Unclassified OS: FreeBSD Reporter: russianneuromancer(a)ya.ru Hardware: x86-64 (AMD64) Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI Created attachment 81668 --> https://bugs.freedesktop.org/attachment.cgi?id=81668&action=edit dmesg Lockup described in bug 64220 was happen right after campaign start (in first minute) but this lockup usually happen later - in first hour of playing. This lockup is not reproducible when HyperZ is disabled, so probably (like bug 64220) is related to HyperZ. [ 2160.750951] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec [ 2160.750966] radeon 0000:01:00.0: GPU lockup (waiting for 0x000000000002525f last fence id 0x000000000002525c) [ 2160.786068] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000174118 and cpu addr 0xffffc9000681c118 [ 2160.787147] radeon 0000:01:00.0: Saved 183 dwords of commands on ring 0. [ 2160.787166] radeon 0000:01:00.0: GPU softreset: 0x00000019 [ 2160.787175] radeon 0000:01:00.0: GRBM_STATUS = 0xE7730CA0 [ 2160.787177] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0xFC000001 [ 2160.787180] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 [ 2160.787182] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 [ 2160.787184] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 [ 2160.787186] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x01000000 [ 2160.787189] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x000D1000 [ 2160.787191] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00068506 [ 2160.787193] radeon 0000:01:00.0: R_008680_CP_STAT = 0x80878647 [ 2160.787196] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [ 2160.787356] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x00007F6B [ 2160.787410] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100 [ 2160.788559] radeon 0000:01:00.0: GRBM_STATUS = 0x00003828 [ 2160.788561] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000007 [ 2160.788563] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 [ 2160.788565] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 [ 2160.788568] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 [ 2160.788570] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [ 2160.788572] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 [ 2160.788574] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 [ 2160.788576] radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000 [ 2160.788579] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [ 2160.788589] radeon 0000:01:00.0: GPU reset succeeded, trying to resume [ 2160.793777] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000). [ 2160.793895] radeon 0000:01:00.0: WB enabled [ 2160.793900] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff8801fb519c00 [ 2160.793904] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff8801fb519c0c [ 2160.796145] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000174118 and cpu addr 0xffffc900079b2118 [ 2160.812389] [drm] ring test on 0 succeeded in 2 usecs [ 2160.812457] [drm] ring test on 3 succeeded in 1 usecs [ 2160.987496] [drm] ring test on 5 succeeded in 1 usecs [ 2160.987512] [drm] UVD initialized successfully. [ 2161.219416] [drm] ib test on ring 0 succeeded in 0 usecs [ 2161.219497] [drm] ib test on ring 3 succeeded in 1 usecs [ 2161.370073] [drm:r600_uvd_ib_test] *ERROR* radeon: failed to get create msg (-22). [ 2161.370094] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on ring 5 (-22). ~$ lspci | grep VGA 00:01.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI BeaverCreek [Radeon HD 6620G] 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Whistler [Radeon HD 6600M/6700M/7600M Series] (DRI_PRIME is used to launch game.) Linux 3.10-rc7 libdrm 2.4.45+git20130607.a0178c00 Mesa 9.2.0~git20130627.15085b47 xserver-xorg-video-radeon 7.1.99+git20130531.bd2557ea Xserver 1.13.4~git20130508+server-1.13-branch.10c42f57 Kubuntu 13.04 x86_64 updated from Xorg Edgers PPA. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 51189] New: TTM errors when suspending (call trace)
by bugzilla-daemon＠freedesktop.org 29 Jan '16

29 Jan '16

https://bugs.freedesktop.org/show_bug.cgi?id=51189 Bug #: 51189 Summary: TTM errors when suspending (call trace) Classification: Unclassified 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: h.judt(a)gmx.at Linux 3.4.0+ #53 SMP PREEMPT Mon Jun 11 15:16:31 CEST 2012 x86_64 Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz GenuineIntel GNU/Linux Recently I found these messages in dmesg when I tried to suspend the machine: Freezing user space processes ... (elapsed 0.01 seconds) done. Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. Suspending console(s) (use no_console_suspend to debug) sd 1:0:0:0: [sdb] Synchronizing SCSI cache sd 0:0:0:0: [sda] Synchronizing SCSI cache sd 0:0:0:0: [sda] Stopping disk sd 1:0:0:0: [sdb] Stopping disk serial 00:09: disabled serial 00:09: wake-up capability disabled by ACPI i8042 kbd 00:08: wake-up capability enabled by ACPI ACPI handle has no context! ACPI handle has no context! ACPI handle has no context! kworker/u:20: page allocation failure: order:0, mode:0x28010 Pid: 9562, comm: kworker/u:20 Tainted: G O 3.4.0+ #53 Call Trace: [<ffffffff8108f86f>] warn_alloc_failed+0x110/0x125 [<ffffffff810998bf>] ? try_to_free_pages+0x68/0x6a [<ffffffff81091fd2>] __alloc_pages_nodemask+0x6c1/0x6f7 [<ffffffff81006336>] dma_generic_alloc_coherent+0xaf/0x119 [<ffffffff8101cd7f>] x86_swiotlb_alloc_coherent+0x1c/0x3d [<ffffffff812b0fae>] ttm_dma_populate+0x487/0x74f [<ffffffff812d662a>] radeon_ttm_tt_populate+0x3d/0x18d [<ffffffff812a9848>] ttm_tt_bind+0x2c/0x4f [<ffffffff812ab15d>] ttm_bo_handle_move_mem+0x132/0x33e [<ffffffff812abcd3>] ? ttm_bo_mem_space+0xfb/0x2c9 [<ffffffff812d5c00>] ? radeon_sync_obj_ref+0xa/0xb [<ffffffff812c4810>] ? cail_reg_write+0x16/0x18 [<ffffffff812ab616>] ttm_bo_evict+0x2ad/0x2f6 [<ffffffff812aef5b>] ? ttm_eu_list_ref_sub+0x24/0x38 [<ffffffff812ab7ed>] ttm_mem_evict_first+0x18e/0x1c9 [<ffffffff812ab88a>] ttm_bo_force_list_clean+0x62/0xa4 [<ffffffff812ab916>] ttm_bo_evict_mm+0x4a/0x4c [<ffffffff812d7331>] radeon_bo_evict_vram+0x15/0x17 [<ffffffff812c5a0f>] radeon_suspend_kms+0x10d/0x1c8 [<ffffffff812b14e2>] radeon_pci_suspend+0x22/0x24 [<ffffffff81233074>] pci_legacy_suspend+0x34/0xb8 [<ffffffff81233774>] pci_pm_suspend+0x45/0xfa [<ffffffff8123372f>] ? pci_pm_resume+0x99/0x99 [<ffffffff8132cfba>] dpm_run_callback.isra.5+0x2a/0x58 [<ffffffff8132d8bd>] __device_suspend+0x145/0x1c6 [<ffffffff810419e9>] ? async_schedule+0x12/0x12 [<ffffffff8132db7b>] async_suspend+0x1a/0x85 [<ffffffff81041a86>] async_run_entry_fn+0x9d/0x14f [<ffffffff81038b67>] process_one_work+0x1b9/0x2e8 [<ffffffff810370da>] ? need_to_create_worker+0xd/0x21 [<ffffffff810390f2>] worker_thread+0x15b/0x21c [<ffffffff81038f97>] ? manage_workers.isra.28+0x16a/0x16a [<ffffffff8103ca10>] kthread+0x86/0x8e [<ffffffff81044222>] ? schedule_tail+0x50/0xb1 [<ffffffff81414014>] kernel_thread_helper+0x4/0x10 [<ffffffff8103c98a>] ? kthread_freezable_should_stop+0x4d/0x4d [<ffffffff81414010>] ? gs_change+0xb/0xb Mem-Info: Node 0 DMA per-cpu: CPU 0: hi: 0, btch: 1 usd: 0 CPU 1: hi: 0, btch: 1 usd: 0 CPU 2: hi: 0, btch: 1 usd: 0 CPU 3: hi: 0, btch: 1 usd: 0 CPU 4: hi: 0, btch: 1 usd: 0 CPU 5: hi: 0, btch: 1 usd: 0 CPU 6: hi: 0, btch: 1 usd: 0 CPU 7: hi: 0, btch: 1 usd: 0 Node 0 DMA32 per-cpu: CPU 0: hi: 186, btch: 31 usd: 172 CPU 1: hi: 186, btch: 31 usd: 30 CPU 2: hi: 186, btch: 31 usd: 179 CPU 3: hi: 186, btch: 31 usd: 176 CPU 4: hi: 186, btch: 31 usd: 167 CPU 5: hi: 186, btch: 31 usd: 158 CPU 6: hi: 186, btch: 31 usd: 8 CPU 7: hi: 186, btch: 31 usd: 31 Node 0 Normal per-cpu: CPU 0: hi: 186, btch: 31 usd: 75 CPU 1: hi: 186, btch: 31 usd: 117 CPU 2: hi: 186, btch: 31 usd: 67 CPU 3: hi: 186, btch: 31 usd: 146 CPU 4: hi: 186, btch: 31 usd: 118 CPU 5: hi: 186, btch: 31 usd: 82 CPU 6: hi: 186, btch: 31 usd: 153 CPU 7: hi: 186, btch: 31 usd: 155 active_anon:113306 inactive_anon:132606 isolated_anon:0 active_file:365473 inactive_file:3041451 isolated_file:0 unevictable:184211 dirty:16 writeback:2 unstable:0 free:33437 slab_reclaimable:111913 slab_unreclaimable:9741 mapped:198967 shmem:3493 pagetables:9976 bounce:0 Node 0 DMA free:14500kB min:64kB low:80kB high:96kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15648kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:0kB slab_unreclaimable:16kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? yes lowmem_reserve[]: 0 2978 16075 16075 Node 0 DMA32 free:64580kB min:12512kB low:15640kB high:18768kB active_anon:49216kB inactive_anon:72588kB active_file:45872kB inactive_file:2672020kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:3050368kB mlocked:0kB dirty:0kB writeback:0kB mapped:52kB shmem:0kB slab_reclaimable:81412kB slab_unreclaimable:1636kB kernel_stack:120kB pagetables:3736kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no lowmem_reserve[]: 0 0 13096 13096 Node 0 Normal free:54668kB min:55004kB low:68752kB high:82504kB active_anon:404008kB inactive_anon:457836kB active_file:1416020kB inactive_file:9493784kB unevictable:736844kB isolated(anon):0kB isolated(file):0kB present:13410432kB mlocked:737408kB dirty:64kB writeback:8kB mapped:795816kB shmem:13972kB slab_reclaimable:366240kB slab_unreclaimable:37312kB kernel_stack:2984kB pagetables:36168kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no lowmem_reserve[]: 0 0 0 0 Node 0 DMA: 1*4kB 0*8kB 0*16kB 1*32kB 0*64kB 1*128kB 0*256kB 0*512kB 0*1024kB 1*2048kB 3*4096kB = 14500kB Node 0 DMA32: 217*4kB 122*8kB 85*16kB 52*32kB 53*64kB 38*128kB 35*256kB 17*512kB 17*1024kB 8*2048kB 0*4096kB = 64580kB Node 0 Normal: 586*4kB 196*8kB 133*16kB 175*32kB 176*64kB 5*128kB 2*256kB 8*512kB 6*1024kB 6*2048kB 2*4096kB = 54776kB 3594629 total pagecache pages 0 pages in swap cache Swap cache stats: add 0, delete 0, find 0/0 Free swap = 4194300kB Total swap = 4194300kB 4192240 pages RAM 87569 pages reserved 3071034 pages shared 1215016 pages non-shared kworker/u:20: page allocation failure: order:0, mode:0x20010 There are many of these. Further below: [TTM] radeon 0000:01:00.0: Failed to set 4 pages to wc! [TTM] radeon 0000:01:00.0: Failed to fill wc pool (r:-22)! [TTM] radeon 0000:01:00.0: Failed to set 4 pages to wc! [TTM] radeon 0000:01:00.0: Failed to fill wc pool (r:-22)! [TTM] radeon 0000:01:00.0: Failed to set 4 pages to wc! [TTM] radeon 0000:01:00.0: Failed to fill wc pool (r:-22)! [TTM] radeon 0000:01:00.0: Failed to set 4 pages to wc! [TTM] radeon 0000:01:00.0: Failed to fill wc pool (r:-22)! [TTM] radeon 0000:01:00.0: Failed to set 4 pages to wc! [TTM] radeon 0000:01:00.0: Failed to fill wc pool (r:-22)! [TTM] radeon 0000:01:00.0: Failed to set 4 pages to wc! [TTM] radeon 0000:01:00.0: Failed to fill wc pool (r:-22)! [TTM] radeon 0000:01:00.0: Failed to set 4 pages to wc! [TTM] radeon 0000:01:00.0: Failed to fill wc pool (r:-22)! [TTM] radeon 0000:01:00.0: Failed to set 4 pages to wc! [TTM] radeon 0000:01:00.0: Failed to fill wc pool (r:-22)! [TTM] radeon 0000:01:00.0: Failed to set 4 pages to wc! [TTM] radeon 0000:01:00.0: Failed to fill wc pool (r:-22)! [TTM] radeon 0000:01:00.0: Failed to set 4 pages to wc! [TTM] radeon 0000:01:00.0: Failed to fill wc pool (r:-22)! [TTM] radeon 0000:01:00.0: Failed to set 4 pages to wc! [TTM] radeon 0000:01:00.0: Failed to fill wc pool (r:-22)! [TTM] radeon 0000:01:00.0: Failed to set 4 pages to wc! [TTM] radeon 0000:01:00.0: Failed to fill wc pool (r:-22)! [TTM] radeon 0000:01:00.0: Failed to set 4 pages to wc! [TTM] radeon 0000:01:00.0: Failed to fill wc pool (r:-22)! [TTM] radeon 0000:01:00.0: Failed to set 4 pages to wc! [TTM] radeon 0000:01:00.0: Failed to fill wc pool (r:-22)! SLUB: Unable to allocate memory on node -1 (gfp=0xd0) cache: kmalloc-64, object size: 64, buffer size: 64, default order: 0, min order: 0 node 0: slabs: 1245, objs: 79680, free: 0 [TTM] radeon 0000:01:00.0: Unable to get page 2 [TTM] radeon 0000:01:00.0: Failed to set 2 pages to wc! [TTM] radeon 0000:01:00.0: Failed to fill wc pool (r:-12)! SLUB: Unable to allocate memory on node -1 (gfp=0xd0) cache: kmalloc-64, object size: 64, buffer size: 64, default order: 0, min order: 0 node 0: slabs: 1245, objs: 79680, free: 0 [TTM] radeon 0000:01:00.0: Unable to get page 1 [TTM] radeon 0000:01:00.0: Failed to set 1 pages to wc! [TTM] radeon 0000:01:00.0: Failed to fill wc pool (r:-12)! [TTM] Buffer eviction failed [TTM] radeon 0000:01:00.0: Failed to set 4 pages to wc! [TTM] radeon 0000:01:00.0: Failed to fill wc pool (r:-22)! [TTM] radeon 0000:01:00.0: Failed to set 4 pages to wc! [TTM] radeon 0000:01:00.0: Failed to fill wc pool (r:-22)! [TTM] radeon 0000:01:00.0: Failed to set 4 pages to wc! [TTM] radeon 0000:01:00.0: Failed to fill wc pool (r:-22)! [TTM] radeon 0000:01:00.0: Failed to set 4 pages to wc! [TTM] radeon 0000:01:00.0: Failed to fill wc pool (r:-22)! [TTM] radeon 0000:01:00.0: Failed to set 4 pages to wc! [TTM] radeon 0000:01:00.0: Failed to fill wc pool (r:-22)! [TTM] radeon 0000:01:00.0: Failed to set 4 pages to wc! [TTM] radeon 0000:01:00.0: Failed to fill wc pool (r:-22)! [TTM] radeon 0000:01:00.0: Failed to set 4 pages to wc! [TTM] radeon 0000:01:00.0: Failed to fill wc pool (r:-22)! [TTM] radeon 0000:01:00.0: Failed to set 4 pages to wc! [TTM] radeon 0000:01:00.0: Failed to fill wc pool (r:-22)! [TTM] radeon 0000:01:00.0: Failed to set 4 pages to wc! [TTM] radeon 0000:01:00.0: Failed to fill wc pool (r:-22)! [TTM] radeon 0000:01:00.0: Failed to set 4 pages to wc! [TTM] radeon 0000:01:00.0: Failed to fill wc pool (r:-22)! [TTM] radeon 0000:01:00.0: Failed to set 4 pages to wc! [TTM] radeon 0000:01:00.0: Failed to fill wc pool (r:-22)! [TTM] radeon 0000:01:00.0: Failed to set 4 pages to wc! [TTM] radeon 0000:01:00.0: Failed to fill wc pool (r:-22)! [TTM] radeon 0000:01:00.0: Failed to set 4 pages to wc! [TTM] radeon 0000:01:00.0: Failed to fill wc pool (r:-22)! [TTM] radeon 0000:01:00.0: Failed to set 4 pages to wc! [TTM] radeon 0000:01:00.0: Failed to fill wc pool (r:-22)! [TTM] radeon 0000:01:00.0: Failed to set 4 pages to wc! [TTM] radeon 0000:01:00.0: Failed to fill wc pool (r:-22)! [TTM] radeon 0000:01:00.0: Failed to set 4 pages to wc! [TTM] radeon 0000:01:00.0: Failed to fill wc pool (r:-22)! [TTM] radeon 0000:01:00.0: Failed to set 4 pages to wc! [TTM] radeon 0000:01:00.0: Failed to fill wc pool (r:-22)! [TTM] Failed allocating page table [TTM] Buffer eviction failed PM: suspend of devices complete after 719.845 msecs PM: late suspend of devices complete after 0.096 msecs pcieport 0000:00:1c.7: wake-up capability enabled by ACPI pcieport 0000:00:1c.6: wake-up capability enabled by ACPI pcieport 0000:00:1c.5: wake-up capability enabled by ACPI ehci_hcd 0000:00:1d.0: wake-up capability enabled by ACPI ehci_hcd 0000:00:1a.0: wake-up capability enabled by ACPI PM: noirq suspend of devices complete after 54.969 msecs ACPI: Preparing to enter system sleep state S3 PM: Saving platform NVS memory Disabling non-boot CPUs ... _cpu_down: attempt to take down CPU 1 failed Error taking CPU1 down: -12 Non-boot CPUs are not disabled ACPI: Waking up from system sleep state S3 ehci_hcd 0000:00:1a.0: wake-up capability disabled by ACPI ehci_hcd 0000:00:1d.0: wake-up capability disabled by ACPI pcieport 0000:00:1c.5: wake-up capability disabled by ACPI pcieport 0000:00:1c.6: wake-up capability disabled by ACPI PM: noirq resume of devices complete after 121.294 msecs PM: early resume of devices complete after 0.024 msecs ehci_hcd 0000:00:1a.0: setting latency timer to 64 ahci 0000:00:1f.2: setting latency timer to 64 ehci_hcd 0000:00:1d.0: setting latency timer to 64 pcieport 0000:00:1c.7: wake-up capability disabled by ACPI usb usb1: root hub lost power or was reset usb usb2: root hub lost power or was reset usb usb3: root hub lost power or was reset usb usb4: root hub lost power or was reset snd_hda_intel 0000:00:1b.0: irq 58 for MSI/MSI-X i8042 kbd 00:08: wake-up capability disabled by ACPI snd_hda_intel 0000:01:00.1: irq 59 for MSI/MSI-X xhci_hcd 0000:05:00.0: irq 60 for MSI/MSI-X xhci_hcd 0000:04:00.0: irq 61 for MSI/MSI-X serial 00:09: activated r8169 0000:0c:00.0: eth0: link down [drm] PCIE GART of 512M enabled (table at 0x0000000000141000). radeon 0000:01:00.0: WB enabled [drm] fence driver on ring 0 use gpu addr 0x80000c00 and cpu addr 0xffff880427833c00 [drm] fence driver on ring 1 use gpu addr 0x80000c04 and cpu addr 0xffff880427833c04 [drm] fence driver on ring 2 use gpu addr 0x80000c08 and cpu addr 0xffff880427833c08 Suspend failed once but worked on the second try, and everything worked fine after resume. Anyway, I thought I'd post that here, maybe it is of some help to someone. -- 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 39287] New: Framebuffer object extension is exposed, but appears never supported by radeon on R200
by bugzilla-daemon＠freedesktop.org 01 Dec '15

01 Dec '15

https://bugs.freedesktop.org/show_bug.cgi?id=39287 Summary: Framebuffer object extension is exposed, but appears never supported by radeon on R200 Product: DRI Version: XOrg CVS Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: b7.10110111(a)gmail.com Created an attachment (id=49182) --> (https://bugs.freedesktop.org/attachment.cgi?id=49182) Test program See test program. A framebuffer object is created there, and a color attachment of 2^n x 2^m is attached to it. Regardless of using depth renderbuffer attachment, framebuffer status is always GL_FRAMEBUFFER_UNSUPPORTED. Test program continues execution nonetheless, to see if something is drawn. In some circumstances, i do see some part of the image for several frames, but they disappear after that. -- 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 44568] New: Half-Life 1 engine has poor fps is large areas
by bugzilla-daemon＠freedesktop.org 26 Nov '15

26 Nov '15

https://bugs.freedesktop.org/show_bug.cgi?id=44568 Bug #: 44568 Summary: Half-Life 1 engine has poor fps is large areas 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: toni.spets(a)iki.fi Created attachment 55280 --> https://bugs.freedesktop.org/attachment.cgi?id=55280 Slow GLTrace I've been following the fps of this engine for a few years, pre-gallium and lately gallium. There is a noticable fps drop in maps that contain water or a lot of models. Normally, a fps drop from 100 to ~15 happens in action situations with smoke, other players, water etc. Taken that the engine is over 10 years old, is using standard OpenGL and it runs very fine at 100fps on windows, my guesstimate is that it is using some unoptimized GL path. Attached slow gltrace is from viewing an area where my fps in 800x600 resolution is around 56 with a lot of models on the screen and the fast trace is from a map that doesn't have that drop at all when nothing is happening. The traces are around from the same period of time but the fast trace went at ~25 fps and the slow at ~5 fps when it was logged. Both traces start and end with the game menu but only briefly. Would appreciate if someone could finally take a shot at fixing this. -- 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 36782] New: textures on Earth in Celestia contain pixels from other windows
by bugzilla-daemon＠freedesktop.org 17 Nov '15

17 Nov '15

https://bugs.freedesktop.org/show_bug.cgi?id=36782 Summary: textures on Earth in Celestia contain pixels from other windows Product: Mesa Version: 7.10 Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/R600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: acelists(a)atlas.sk Created an attachment (id=46261) --> (https://bugs.freedesktop.org/attachment.cgi?id=46261) See the blue dotted band around the planet - it is a window titlebar. Textures on the planet Earth are rendered garbled with data pixel taken from other windows (programs), probably taken from released GPU memory. Note it only happens on Earth. The garbled texture is not the planet surface one, but it is the clouds layer. That is loaded from a file that is 1024x512. It does not happen when lowres textures are selected. Then a 128x64px file is used for the clouds. -- 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 56659] New: DRI_PRIME: triangle, rendering inside of which occurs with a noticeable delay
by bugzilla-daemon＠freedesktop.org 08 Sep '15

08 Sep '15

https://bugs.freedesktop.org/show_bug.cgi?id=56659 Priority: medium Bug ID: 56659 Assignee: dri-devel(a)lists.freedesktop.org Summary: DRI_PRIME: triangle, rendering inside of which occurs with a noticeable delay Severity: normal Classification: Unclassified OS: All Reporter: runetmember(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Created attachment 69414 --> https://bugs.freedesktop.org/attachment.cgi?id=69414&action=edit Example of artifact Hello! Please look at attached screenshot - there is triangle where we still see part of old frame, that was displayed on screen few frames before. I doesn't sure about terminology, but from my point of view looks like rendering in this triangle is lag behind rest of the screen. This issue happen for me only for applications launched with enabled offloading rendering (DRI_PRIME=1). It's reproducible not only in "Left 4 Dead 2" but also in other applications. Even in Chromium (if you launch it with "--ignore-gpu-blacklist" option that enabled hardware rendering on Mesa, and "DRI_PRIME=1" that enable offloading rendering) display same artifact (triangle) while scrolling pages. Also you may notice this artifact in glxgears, if you you run it in fullscreen mode. Software: Kubuntu 12.10 x86_64 updated from Xorg Edgers PPA. Mesa: 9.1~git20121029.00e6819e libdrm-radeon1: git20121025.bc494b31 xserver-xorg-video-radeon: git20120928.e8cb0b72 xserver-xorg-core: 1.13.0+git20120920.70e57668 Enabled or disabled V-Sync in KWin settings doesn't make the difference. Enabled or disabled V-Sync in game settings doesn't make the difference. Screenshot taken with stock Kubuntu kernel (3.5.0-17). With 3.7rc3 kernel issue still reproducible, but just a bit less noticeable. Hardware: Acer Aspire 7560G laptop, AMD APU A8-3500M with integrated Radeon HD 6620G (SUMO) Discrete AMD Radeon HD 6650M (TURKS) "xrandr --listproviders" output: Providers: number : 2 Provider 0: id: 138 cap: 0xd, Source Output, Source Offload, Sink Offload crtcs: 2 outputs: 3 associated providers: 1 name:radeon Provider 1: id: 85 cap: 0xd, Source Output, Source Offload, Sink Offload crtcs: 6 outputs: 0 associated providers: 1 name:radeon -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 66384] New: VDPAU playback hangs when moving window between xrandr monitors
by bugzilla-daemon＠freedesktop.org 20 Aug '15

20 Aug '15

https://bugs.freedesktop.org/show_bug.cgi?id=66384 Priority: medium Bug ID: 66384 Assignee: dri-devel(a)lists.freedesktop.org Summary: VDPAU playback hangs when moving window between xrandr monitors Severity: normal Classification: Unclassified OS: All Reporter: mgorny(a)gentoo.org Hardware: Other Status: NEW Version: unspecified Component: Drivers/Gallium/r600 Product: Mesa I'm running live xorg/mesa with Radeon HD5450. I have two monitors connected and set up side-by-side using xrandr like the following: $ xrandr --output VGA-0 --mode 1280x960 --right-of DVI-0 Now, when I play a movie using mplayer2 with VDPAU driver and move the movie onto second monitor without pausing it first, the playback hangs for a minute or two. Then it resumes like nothing happened, no messages neither on console nor in dmesg. What's interesting is that it seems to happen only after moving half of the window. If I have it partially on both monitors, it plays back fine. After the hang it plays fine again, and if I then move it back to the first monitor, it again hangs after moving half of it. -- You are receiving this mail because: You are the assignee for the bug.

1 10

← Newer
1
...
25
26
27
28
29
30
31
...
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