dri-devel May 2010

dri-devel@lists.freedesktop.org

69 participants
209 discussions

[Bug 8732] Composite breaks OpenGL
by bugzilla-daemon＠freedesktop.org 03 May '10

03 May '10

https://bugs.freedesktop.org/show_bug.cgi?id=8732 --- Comment #28 from Dotan Cohen <freedesktop-org(a)dotancohen.com> 2010-05-03 12:19:42 PDT --- > One of the main points of DRI2 was to fix GL + composite. It > will only work as expected with a DRI2 capable driver. DRI2 is > not a workaround, it is the fix. I have misunderstood, then. I understood this issue to be for improving OpenGL (and DRI) support for a specific driver. I was too quick to mark my own bug as a dupe (see comment 25). I will reopen that bug as a request to enable DRI in radeonhd. 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 0

[Bug 8732] Composite breaks OpenGL
by bugzilla-daemon＠freedesktop.org 03 May '10

03 May '10

https://bugs.freedesktop.org/show_bug.cgi?id=8732 Alex Deucher <agd5f(a)yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #27 from Alex Deucher <agd5f(a)yahoo.com> 2010-05-03 12:02:44 PDT --- One of the main points of DRI2 was to fix GL + composite. It will only work as expected with a DRI2 capable driver. DRI2 is not a workaround, it is the fix. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 0

[Bug 8732] Composite breaks OpenGL
by bugzilla-daemon＠freedesktop.org 03 May '10

03 May '10

https://bugs.freedesktop.org/show_bug.cgi?id=8732 Dotan Cohen <freedesktop-org(a)dotancohen.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #26 from Dotan Cohen <freedesktop-org(a)dotancohen.com> 2010-05-03 11:55:08 PDT --- Why is this marked as FIXED? I see that one poster found a workaround by manually enabling dri2 and uxa on Ubuntu, but the fix was never ported to the released version of the driver. That is, even on Ubuntu, users are bitten by this bug unless the know how to enable dri2 and uxa, and assuming that they know that they even have to. I am reopening until the issue is fixed, a workaround (or manually enabling dri2/uxa) is not a fix. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 0

[Bug 8732] Composite breaks OpenGL
by bugzilla-daemon＠freedesktop.org 03 May '10

03 May '10

1 0

[Bug 27866] New: d-r-t crashes at radeon_bo_unref()
by bugzilla-daemon＠freedesktop.org 03 May '10

03 May '10

https://bugs.freedesktop.org/show_bug.cgi?id=27866 Summary: d-r-t crashes at radeon_bo_unref() 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: aidan(a)cisco.com latest d-r-t pull (that had pm3 merged) crashes often in the last few hours on my rv790 with the same backtrace, doesn't seem to last more than 30 mins uptime doing normal boring desktop tasks. this is with dynpm=1. will try without dynpm. [ 5297.309664] [drm] Requested: e: 80000 m: 97500 p: 16 [ 5297.344857] [drm] not in vbl for pm change 00020002 at entry [ 5297.345295] [drm] Setting: e: 80000 [ 5297.945372] [drm] Requested: e: 50000 m: 97500 p: 16 [ 5298.162501] [drm] not in vbl for pm change 00020002 at entry [ 5298.162941] [drm] Setting: e: 50000 [ 5298.562080] [drm] Requested: e: 50000 m: 97500 p: 16 [ 5318.273565] BUG: unable to handle kernel paging request at 0000000000001c18 [ 5318.273569] IP: [<ffffffff814db764>] mutex_unlock+0x1/0x18 [ 5318.273574] PGD 2218b5067 PUD 33b06a067 PMD 0 [ 5318.273576] Oops: 0002 [#1] SMP [ 5318.273578] last sysfs file: /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-3/2-3:1.0/host6/target6:0:0/6:0:0:0/block/sdc/size [ 5318.273580] CPU 0 [ 5318.273581] Modules linked in: ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 ipt_addrtype xt_DSCP xt_dscp xt_NFQUEUE xt_MARK xt_mark xt_iprange xt_conntrack xt_CONNMARK xt_connmark nf_conntrack ip_tables autofs4 bridge stp llc tun kvm_intel kvm coretemp radeon ttm drm_kms_helper drm asus_atk0110 snd_ctxfi sky2 i2c_algo_bit cfbcopyarea cfbimgblt cfbfillrect [ 5318.273597] [ 5318.273599] Pid: 2780, comm: X Not tainted 2.6.34-rc5 #2 P6T DELUXE V2/System Product Name [ 5318.273600] RIP: 0010:[<ffffffff814db764>] [<ffffffff814db764>] mutex_unlock+0x1/0x18 [ 5318.273603] RSP: 0018:ffff880209d53c58 EFLAGS: 00010206 [ 5318.273604] RAX: ffff8801779d8a00 RBX: ffff880209d53ca0 RCX: ffff8801779da600 [ 5318.273606] RDX: ffff88033d320000 RSI: ffff880002000000 RDI: 0000000000001c00 [ 5318.273607] RBP: ffff880209d53c88 R08: 0000000000000000 R09: 0000000040086409 [ 5318.273608] R10: 0000000000000001 R11: dead000000200200 R12: ffff88033a538800 [ 5318.273610] R13: ffff88033a538820 R14: ffff880177e92a80 R15: ffffffffa0069400 [ 5318.273611] FS: 00007fae348c3840(0000) GS:ffff880002000000(0000) knlGS:0000000000000000 [ 5318.273613] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 5318.273614] CR2: 0000000000001c18 CR3: 0000000209cb6000 CR4: 00000000000006f0 [ 5318.273616] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 5318.273617] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [ 5318.273619] Process X (pid: 2780, threadinfo ffff880209d52000, task ffff88033b9f5b80) [ 5318.273620] Stack: [ 5318.273621] ffff880209d53c88 ffffffffa00d47c3 0000000000000282 0000000000000000 [ 5318.273623] <0> ffff880209d53c88 ffff880177e92a80 ffff880209d53cb8 ffffffffa00e4575 [ 5318.273625] <0> ffff8801792fa88c ffff8801779d8a00 ffff880209d53cb8 ffff880177e92a80 [ 5318.273627] Call Trace: [ 5318.273642] [<ffffffffa00d47c3>] ? radeon_bo_unref+0x4e/0x63 [radeon] [ 5318.273655] [<ffffffffa00e4575>] radeon_gem_object_free+0x30/0x47 [radeon] [ 5318.273661] [<ffffffffa005468c>] drm_gem_object_free_unlocked+0x54/0x64 [drm] [ 5318.273666] [<ffffffffa0054638>] ? drm_gem_object_free_unlocked+0x0/0x64 [drm] [ 5318.273670] [<ffffffff8128b965>] kref_put+0x43/0x4d [ 5318.273675] [<ffffffffa0054812>] drm_gem_object_unreference_unlocked+0x15/0x17 [drm] [ 5318.273680] [<ffffffffa005484f>] drm_gem_object_handle_unreference_unlocked+0x29/0x2d [drm] [ 5318.273686] [<ffffffffa0054a34>] drm_gem_close_ioctl+0x66/0x71 [drm] [ 5318.273691] [<ffffffffa005352b>] drm_ioctl+0x245/0x33e [drm] [ 5318.273696] [<ffffffffa00549ce>] ? drm_gem_close_ioctl+0x0/0x71 [drm] [ 5318.273699] [<ffffffff81253d06>] ? inode_has_perm+0x5f/0x61 [ 5318.273702] [<ffffffff810c93b7>] ? free_pages_and_swap_cache+0x21/0x7b [ 5318.273704] [<ffffffff81289485>] ? cpumask_any_but+0x29/0x36 [ 5318.273707] [<ffffffff810ea534>] vfs_ioctl+0x2d/0xa1 [ 5318.273709] [<ffffffff810eaa76>] do_vfs_ioctl+0x457/0x49d [ 5318.273711] [<ffffffff810eab0d>] sys_ioctl+0x51/0x74 [ 5318.273713] [<ffffffff810029ab>] system_call_fastpath+0x16/0x1b [ 5318.273715] Code: 89 65 a0 48 8d 46 28 89 5d a8 48 c7 45 c0 cf 40 05 81 48 89 45 c8 48 89 45 d0 e8 21 ff ff ff 48 83 c4 58 5b 41 5c 41 5d c9 c3 55 <48> c7 47 18 00 00 00 00 48 89 e5 f0 ff 07 7f 05 e8 02 00 00 00 [ 5318.273731] RIP [<ffffffff814db764>] mutex_unlock+0x1/0x18 [ 5318.273733] RSP <ffff880209d53c58> [ 5318.273734] CR2: 0000000000001c18 [ 5318.273735] ---[ end trace ccc350f8e0304ab4 ]--- -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 13

mmotm 2010-04-28 - nouveau driver issues
by Valdis.Kletnieks＠vt.edu 02 May '10

02 May '10

On Wed, 28 Apr 2010 16:53:32 PDT, akpm(a)linux-foundation.org said: > The mm-of-the-moment snapshot 2010-04-28-16-53 has been uploaded to > > http://userweb.kernel.org/~akpm/mmotm/ The nouveau driver had issues during boot, caused plymouth to have indigestion and fall back to 24x80 character mode. This happened sometime between -mmotm0422 and -mmotm0428. Looks like something in linux-next, cc'ing anybody who apparently touched nouveau code. Will bisect if nobody has a good idea what happened. The X server was able to init the card and get gdm started just fine. lspci says: 01:00.0 VGA compatible controller: nVidia Corporation G98M [Quadro NVS 160M] (rev a1) [ 1.038152] [drm] nouveau 0000:01:00.0: Detected 256MiB VRAM [ 1.194505] [TTM] Zone kernel: Available graphics memory: 2013496 kiB. [ 1.194508] [ttm] Initializing pool allocator. [ 1.194896] ------------[ cut here ]------------ [ 1.194903] WARNING: at arch/x86/mm/ioremap.c:111 __ioremap_caller+0x238/0x3f4() [ 1.194906] Hardware name: Latitude E6500 [ 1.194908] Modules linked in: [ 1.194912] Pid: 1, comm: swapper Not tainted 2.6.34-rc5-mmotm0428 #1 [ 1.194915] Call Trace: [ 1.194921] [<ffffffff81038936>] warn_slowpath_common+0x80/0x98 [ 1.194925] [<ffffffff81038963>] warn_slowpath_null+0x15/0x17 [ 1.194929] [<ffffffff8102064a>] __ioremap_caller+0x238/0x3f4 [ 1.194934] [<ffffffff812b27ba>] ? ttm_mem_reg_ioremap+0x54/0x7b [ 1.194939] [<ffffffff810d6aff>] ? kmem_cache_alloc_notrace+0x68/0xc0 [ 1.194942] [<ffffffff8102088f>] ioremap_nocache+0x12/0x14 [ 1.194946] [<ffffffff812b27ba>] ttm_mem_reg_ioremap+0x54/0x7b [ 1.194950] [<ffffffff812b2b5c>] ttm_bo_move_memcpy+0x5e/0x3e0 [ 1.194954] [<ffffffff812a4d7d>] ? drm_mm_split_at_start+0x79/0x95 [ 1.194959] [<ffffffff8120ec2d>] ? do_raw_spin_unlock+0xd0/0xfa [ 1.194964] [<ffffffff812c21cf>] nouveau_bo_move+0x19e/0x222 [ 1.194968] [<ffffffff812afe79>] ttm_bo_handle_move_mem+0x1b4/0x2c0 [ 1.194972] [<ffffffff812b1d9e>] ttm_bo_move_buffer+0xf4/0x14d [ 1.194976] [<ffffffff81210b2d>] ? __list_add+0xb7/0xd2 [ 1.194980] [<ffffffff812b1ee3>] ttm_bo_validate+0xec/0x13e [ 1.194983] [<ffffffff8120e900>] ? do_raw_write_unlock+0x7e/0xc8 [ 1.194987] [<ffffffff812b2315>] ttm_bo_init+0x3e0/0x419 [ 1.194990] [<ffffffff812c2957>] nouveau_bo_new+0x394/0x405 [ 1.194994] [<ffffffff812c2510>] ? nouveau_bo_del_ttm+0x0/0xb3 [ 1.194997] [<ffffffff812a4cca>] ? drm_mm_init+0x63/0x6b [ 1.195015] [<ffffffff812ba319>] nouveau_mem_init+0x262/0x42f [ 1.195019] [<ffffffff812b7e02>] nouveau_card_init+0xb09/0xe35 [ 1.195023] [<ffffffff812b86de>] nouveau_load+0x4e6/0x50c [ 1.195028] [<ffffffff812a0fee>] drm_get_dev+0x3bf/0x4cc [ 1.195034] [<ffffffff8158c3be>] nouveau_pci_probe+0x10/0x12 [ 1.195039] [<ffffffff8121d71b>] local_pci_probe+0x12/0x16 [ 1.195043] [<ffffffff8121db88>] pci_device_probe+0x60/0x8f [ 1.195048] [<ffffffff813082e3>] ? driver_sysfs_add+0x47/0x6c [ 1.195052] [<ffffffff81308462>] driver_probe_device+0xde/0x178 [ 1.195056] [<ffffffff81308558>] __driver_attach+0x5c/0x80 [ 1.195060] [<ffffffff813084fc>] ? __driver_attach+0x0/0x80 [ 1.195063] [<ffffffff813084fc>] ? __driver_attach+0x0/0x80 [ 1.195067] [<ffffffff81307a47>] bus_for_each_dev+0x54/0x89 [ 1.195071] [<ffffffff8130829a>] driver_attach+0x19/0x1b [ 1.195075] [<ffffffff81307ee2>] bus_add_driver+0xb4/0x206 [ 1.195079] [<ffffffff81308857>] driver_register+0xb8/0x129 [ 1.195083] [<ffffffff8121ddbe>] __pci_register_driver+0x63/0xd3 [ 1.195088] [<ffffffff81b4f4c4>] ? nouveau_init+0x0/0x52 [ 1.195092] [<ffffffff8129ba89>] drm_init+0x6b/0xd1 [ 1.195096] [<ffffffff81b4f4c4>] ? nouveau_init+0x0/0x52 [ 1.195100] [<ffffffff81b4f514>] nouveau_init+0x50/0x52 [ 1.195104] [<ffffffff810001ef>] do_one_initcall+0x59/0x14e [ 1.195109] [<ffffffff81b2e68a>] kernel_init+0x144/0x1ce [ 1.195113] [<ffffffff81003414>] kernel_thread_helper+0x4/0x10 [ 1.195117] [<ffffffff81598a40>] ? restore_args+0x0/0x30 [ 1.195121] [<ffffffff81b2e546>] ? kernel_init+0x0/0x1ce [ 1.195125] [<ffffffff81003410>] ? kernel_thread_helper+0x0/0x10 [ 1.195192] ---[ end trace f31dec58d66d24a5 ]--- [ 1.195323] [drm] nouveau 0000:01:00.0: failed to reserve VGA memory [ 1.195360] resource map sanity check conflict: 0x0 0xfffff 0xa0000 0xbffff PCI Bus 0000:00 [ 1.195363] ------------[ cut here ]------------ [ 1.195366] WARNING: at arch/x86/mm/ioremap.c:98 __ioremap_caller+0x13b/0x3f4() [ 1.195369] Hardware name: Latitude E6500 [ 1.195371] Info: mapping multiple BARs. Your kernel is fine. [ 1.195373] Modules linked in: [ 1.195376] Pid: 1, comm: swapper Tainted: G W 2.6.34-rc5-mmotm0428 #1 [ 1.195378] Call Trace: [ 1.195382] [<ffffffff81038936>] warn_slowpath_common+0x80/0x98 [ 1.195386] [<ffffffff810389e2>] warn_slowpath_fmt+0x41/0x43 [ 1.195390] [<ffffffff8102054d>] __ioremap_caller+0x13b/0x3f4 [ 1.195394] [<ffffffff812b27ba>] ? ttm_mem_reg_ioremap+0x54/0x7b [ 1.195399] [<ffffffff81064ef0>] ? mark_held_locks+0x52/0x70 [ 1.195403] [<ffffffff810d6aff>] ? kmem_cache_alloc_notrace+0x68/0xc0 [ 1.195407] [<ffffffff8102088f>] ioremap_nocache+0x12/0x14 [ 1.195410] [<ffffffff812b27ba>] ttm_mem_reg_ioremap+0x54/0x7b [ 1.195414] [<ffffffff812b2b5c>] ttm_bo_move_memcpy+0x5e/0x3e0 [ 1.195418] [<ffffffff812a4d7d>] ? drm_mm_split_at_start+0x79/0x95 [ 1.195421] [<ffffffff8120ec2d>] ? do_raw_spin_unlock+0xd0/0xfa [ 1.195425] [<ffffffff812c21cf>] nouveau_bo_move+0x19e/0x222 [ 1.195429] [<ffffffff812afe79>] ttm_bo_handle_move_mem+0x1b4/0x2c0 [ 1.195433] [<ffffffff812b1d9e>] ttm_bo_move_buffer+0xf4/0x14d [ 1.195437] [<ffffffff81210b2d>] ? __list_add+0xb7/0xd2 [ 1.195441] [<ffffffff812b1ee3>] ttm_bo_validate+0xec/0x13e [ 1.195445] [<ffffffff8120e900>] ? do_raw_write_unlock+0x7e/0xc8 [ 1.195448] [<ffffffff812b2315>] ttm_bo_init+0x3e0/0x419 [ 1.195452] [<ffffffff812c2957>] nouveau_bo_new+0x394/0x405 [ 1.195455] [<ffffffff812c2510>] ? nouveau_bo_del_ttm+0x0/0xb3 [ 1.195459] [<ffffffff81064ef0>] ? mark_held_locks+0x52/0x70 [ 1.195463] [<ffffffff810d56ff>] ? trace_kmalloc+0x40/0xb4 [ 1.195468] [<ffffffff812ea53f>] nv50_instmem_populate+0x6d/0x11a [ 1.195473] [<ffffffff812bb78a>] nouveau_gpuobj_new+0x252/0x34c [ 1.195477] [<ffffffff812c0c36>] nouveau_sgdma_init+0x5f/0x241 [ 1.195481] [<ffffffff8121b8ae>] ? pci_find_capability+0x6d/0x7c [ 1.195485] [<ffffffff812ba3e7>] nouveau_mem_init+0x330/0x42f [ 1.195489] [<ffffffff812b7e02>] nouveau_card_init+0xb09/0xe35 [ 1.195493] [<ffffffff812b86de>] nouveau_load+0x4e6/0x50c [ 1.195497] [<ffffffff812a0fee>] drm_get_dev+0x3bf/0x4cc [ 1.195501] [<ffffffff8158c3be>] nouveau_pci_probe+0x10/0x12 [ 1.195505] [<ffffffff8121d71b>] local_pci_probe+0x12/0x16 [ 1.195509] [<ffffffff8121db88>] pci_device_probe+0x60/0x8f [ 1.195513] [<ffffffff813082e3>] ? driver_sysfs_add+0x47/0x6c [ 1.195517] [<ffffffff81308462>] driver_probe_device+0xde/0x178 [ 1.195521] [<ffffffff81308558>] __driver_attach+0x5c/0x80 [ 1.195525] [<ffffffff813084fc>] ? __driver_attach+0x0/0x80 [ 1.195528] [<ffffffff813084fc>] ? __driver_attach+0x0/0x80 [ 1.195532] [<ffffffff81307a47>] bus_for_each_dev+0x54/0x89 [ 1.195536] [<ffffffff8130829a>] driver_attach+0x19/0x1b [ 1.195540] [<ffffffff81307ee2>] bus_add_driver+0xb4/0x206 [ 1.195544] [<ffffffff81308857>] driver_register+0xb8/0x129 [ 1.195548] [<ffffffff8121ddbe>] __pci_register_driver+0x63/0xd3 [ 1.195552] [<ffffffff81b4f4c4>] ? nouveau_init+0x0/0x52 [ 1.195556] [<ffffffff8129ba89>] drm_init+0x6b/0xd1 [ 1.195560] [<ffffffff81b4f4c4>] ? nouveau_init+0x0/0x52 [ 1.195563] [<ffffffff81b4f514>] nouveau_init+0x50/0x52 [ 1.195567] [<ffffffff810001ef>] do_one_initcall+0x59/0x14e [ 1.195571] [<ffffffff81b2e68a>] kernel_init+0x144/0x1ce [ 1.195575] [<ffffffff81003414>] kernel_thread_helper+0x4/0x10 [ 1.195579] [<ffffffff81598a40>] ? restore_args+0x0/0x30 [ 1.195582] [<ffffffff81b2e546>] ? kernel_init+0x0/0x1ce [ 1.195586] [<ffffffff81003410>] ? kernel_thread_helper+0x0/0x10 [ 1.195588] ---[ end trace f31dec58d66d24a6 ]--- [ 1.195597] [drm] nouveau 0000:01:00.0: error getting PRAMIN backing pages: -12 [ 1.195693] [drm] nouveau 0000:01:00.0: Error creating sgdma object: -12 [ 1.195784] [drm] nouveau 0000:01:00.0: Error initialising PCI(E): -12 [ 1.196854] nouveau 0000:01:00.0: PCI INT A disabled [ 1.196863] nouveau: probe of 0000:01:00.0 failed with error -12

1 0

[PATCH] drm/radeon/kms: fix tv dac conflict resolver
by Alex Deucher 02 May '10

02 May '10

>From 837feb147c531219c7315857a6f17e145af8f750 Mon Sep 17 00:00:00 2001 From: Alex Deucher <alexdeucher(a)gmail.com> Date: Thu, 15 Apr 2010 13:31:12 -0400 Subject: [PATCH] drm/radeon/kms: fix tv dac conflict resolver On systems with the tv dac shared between DVI and TV, we can only use the dac for one of the connectors. However, when using a digital monitor on the DVI port, you can use the dac for the TV connector just fine. Check the use_digital status when resolving the conflict. Fixes fdo bug 27649, possibly others. Signed-off-by: Alex Deucher <alexdeucher(a)gmail.com> Cc: stable <stable(a)kernel.org> --- drivers/gpu/drm/radeon/radeon_connectors.c | 5 +++++ 1 files changed, 5 insertions(+), 0 deletions(-) diff --git a/drivers/gpu/drm/radeon/radeon_connectors.c b/drivers/gpu/drm/radeon/radeon_connectors.c index 5c5776d..c489346 100644 --- a/drivers/gpu/drm/radeon/radeon_connectors.c +++ b/drivers/gpu/drm/radeon/radeon_connectors.c @@ -162,12 +162,14 @@ radeon_connector_analog_encoder_conflict_solve(struct drm_connector *connector, { struct drm_device *dev = connector->dev; struct drm_connector *conflict; + struct radeon_connector *radeon_conflict; int i; list_for_each_entry(conflict, &dev->mode_config.connector_list, head) { if (conflict == connector) continue; + radeon_conflict = to_radeon_connector(conflict); for (i = 0; i < DRM_CONNECTOR_MAX_ENCODER; i++) { if (conflict->encoder_ids[i] == 0) break; @@ -177,6 +179,9 @@ radeon_connector_analog_encoder_conflict_solve(struct drm_connector *connector, if (conflict->status != connector_status_connected) continue; + if (radeon_conflict->use_digital) + continue; + if (priority == true) { DRM_INFO("1: conflicting encoders switching off %s\n", drm_get_connector_name(conflict)); DRM_INFO("in favor of %s\n", drm_get_connector_name(connector)); -- 1.5.6.3

3 10

[Bug 27904] New: r300g segfaults on M56GL
by bugzilla-daemon＠freedesktop.org 02 May '10

02 May '10

https://bugs.freedesktop.org/show_bug.cgi?id=27904 Summary: r300g segfaults on M56GL 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: pavel(a)rojtberg.net current git, linux 2.6.32-21-generic (ubuntu lucid) Starting program: /usr/bin/glxgears [Thread debugging using libthread_db enabled] Program received signal SIGSEGV, Segmentation fault. 0x004e68e9 in rc_pair_regalloc (c=0xbfffee8c, maxtemps=1) at radeon_pair_regalloc.c:347 Line number 347 out of range; radeon_pair_regalloc.c has 280 lines. (gdb) bt #0 0x004e68e9 in rc_pair_regalloc (c=0xbfffee8c, maxtemps=1) at radeon_pair_regalloc.c:347 #1 0x004e03dd in r3xx_compile_fragment_program (c=0xbfffee8c) at r3xx_fragprog.c:159 #2 0x004db6f3 in r300_translate_fragment_shader (r300=<value optimized out>, shader=0x80d0ad8, tokens=0x80ef010) at r300_fs.c:276 #3 0x004dbea7 in r300_pick_fragment_shader (r300=0x8066f08) at r300_fs.c:346 #4 0x004d217f in r300_bind_fs_state (pipe=0x8066f08, shader=0x4e6780) at r300_state.c:718 #5 0x00628946 in cso_set_fragment_shader_handle (ctx=0x80e84d8, handle=0x4e6780) at cso_cache/cso_context.c:742 #6 0x005f29e0 in update_fp (st=0x80c3e88) at state_tracker/st_atom_shader.c:174 #7 0x005ef9b3 in st_validate_state (st=0x80c3e88) at state_tracker/st_atom.c:167 #8 0x005f6859 in st_Clear (ctx=0x8087258, mask=18) at state_tracker/st_cb_clear.c:460 #9 0x005a3936 in _mesa_Clear (mask=0) at main/clear.c:178 #10 0x080493d7 in ?? () #11 0x0804a762 in ?? () #12 0x00305bd6 in __libc_start_main (main=0x804a230, argc=1, ubp_av=0xbffff484, init=0x804ad80, fini=0x804ad70, rtld_fini=0x11e0c0 <_dl_fini>, stack_end=0xbffff47c) at libc-start.c:226 -- 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

Nouveau / Mesa gets X11 libraries overwritten sometimes
by Alex Buell 01 May '10

01 May '10

As this has now happened twice in the last two weeks, I thought I'd write this up. This morning I came back to my laptop to find it had locked up, even ssh couldn't gain access to the machine. I rebooted the machine and tried to start X. X refused to start, so I looked at the logs where it locked up before I'd even woken up and found the following: May 1 08:37:16 lithium kernel: __ratelimit: 60 callbacks suppressed May 1 08:37:16 lithium kernel: X: page allocation failure. order:1, mode:0x10d0 May 1 08:37:16 lithium kernel: Pid: 11594, comm: X Not tainted 2.6.32-gentoo-r7 #4 May 1 08:37:16 lithium kernel: Call Trace: May 1 08:37:16 lithium kernel: [<c1050e9f>] ? __alloc_pages_nodemask +0x439/0x47b May 1 08:37:16 lithium kernel: [<c106a52e>] ? cache_alloc_refill +0x240/0x411 May 1 08:37:16 lithium kernel: [<c106a765>] ? __kmalloc+0x66/0x9d May 1 08:37:16 lithium kernel: [<f91ee2b5>] ? agp_alloc_page_array +0x22/0x3c [agpgart] May 1 08:37:16 lithium kernel: [<f91ee330>] ? agp_generic_alloc_user +0x61/0xc3 [agpgart] May 1 08:37:16 lithium kernel: [<f91ee45a>] ? agp_allocate_memory +0x35/0xb3 [agpgart] May 1 08:37:16 lithium kernel: [<f89e00a6>] ? 0xf89e00a6 May 1 08:37:16 lithium kernel: [<f89e0b9b>] ? ttm_tt_populate +0x4d/0x382 [ttm] May 1 08:37:16 lithium kernel: [<f89e0bc6>] ? ttm_tt_populate +0x78/0x382 [ttm] May 1 08:37:16 lithium kernel: [<f89e1c67>] ? ttm_bo_unmap_virtual +0x124/0x455 [ttm] May 1 08:37:16 lithium kernel: [<f89e2db1>] ? ttm_bo_mem_space +0x7a3/0x88b [ttm] May 1 08:37:16 lithium kernel: [<c1022a7f>] ? select_task_rq_fair +0x4c8/0x81d May 1 08:37:16 lithium kernel: [<f89e29a8>] ? ttm_bo_mem_space +0x39a/0x88b [ttm] May 1 08:37:16 lithium kernel: [<f89e31f2>] ? ttm_bo_move_buffer +0x84/0xda [ttm] May 1 08:37:16 lithium kernel: [<f89e32c7>] ? ttm_bo_validate+0x7f/0xc1 [ttm] May 1 08:37:16 lithium kernel: [<f8bc78b0>] ? nouveau_gem_ioctl_cpu_prep+0x23f/0x42c [nouveau] May 1 08:37:16 lithium kernel: [<f8bc8654>] ? nouveau_gem_ioctl_pushbuf +0xbb7/0xbd2 [nouveau] May 1 08:37:16 lithium kernel: [<f93ad46e>] ? drm_ioctl+0x200/0x282 [drm] May 1 08:37:16 lithium kernel: [<f8bc7a9d>] ? nouveau_gem_ioctl_pushbuf +0x0/0xbd2 [nouveau] May 1 08:37:16 lithium kernel: [<f93ad26e>] ? drm_ioctl+0x0/0x282 [drm] May 1 08:37:16 lithium kernel: [<c1078967>] ? vfs_ioctl+0x1c/0x5f May 1 08:37:16 lithium kernel: [<c1078ea2>] ? do_vfs_ioctl+0x451/0x488 May 1 08:37:16 lithium kernel: [<c12e1db8>] ? _spin_unlock_irq+0xd/0x20 May 1 08:37:16 lithium kernel: [<c1029fc1>] ? do_setitimer+0x15c/0x18a May 1 08:37:16 lithium kernel: [<c102a034>] ? sys_setitimer+0x45/0x6f May 1 08:37:16 lithium kernel: [<c1078f05>] ? sys_ioctl+0x2c/0x42 May 1 08:37:16 lithium kernel: [<c10028f4>] ? sysenter_do_call +0x12/0x26 There are about 8 different instances of this, there's a copy of the part I cut out of the logs attached with this e-mail. On trying to start X, I subsequently observed the following in the logs May 1 09:46:27 lithium kernel: [drm] nouveau 0000:01:00.0: Allocating FIFO number 1 May 1 09:46:27 lithium kernel: [drm] nouveau 0000:01:00.0: nouveau_channel_alloc: initialised FIFO 1 May 1 09:46:27 lithium kernel: [drm] nouveau 0000:01:00.0: Setting dpms mode 3 on vga encoder (output 0) May 1 09:46:27 lithium kernel: [drm] DAC-7: set mode 1600x1200 44 May 1 09:46:27 lithium kernel: [drm] nouveau 0000:01:00.0: Setting dpms mode 0 on vga encoder (output 0) May 1 09:46:27 lithium kernel: [drm] nouveau 0000:01:00.0: Output VGA-1 is running on CRTC 0 using output A May 1 09:46:27 lithium kernel: [drm] nouveau 0000:01:00.0: Allocating FIFO number 2 May 1 09:46:27 lithium kernel: [drm] nouveau 0000:01:00.0: nouveau_channel_alloc: initialised FIFO 2 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/2 Mthd 0x0000 Data 0x88000001 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/2 Mthd 0x0180 Data 0x88000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/3 Mthd 0x0000 Data 0x88000002 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/3 Mthd 0x0184 Data 0xbeef0201 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/3 Mthd 0x0188 Data 0xbeef0201 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/4 Mthd 0x0000 Data 0x88000003 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/4 Mthd 0x0180 Data 0x88000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/4 Mthd 0x019c Data 0x88000002 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/4 Mthd 0x02fc Data 0x00000003 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/5 Mthd 0x0000 Data 0x88000004 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: nouveau_channel_free: freeing fifo 2 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/5 Mthd 0x0180 Data 0x88000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/5 Mthd 0x0198 Data 0x88000002 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/5 Mthd 0x02fc Data 0x00000003 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/5 Mthd 0x0304 Data 0x00000002 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/6 Mthd 0x0000 Data 0x88000005 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x0000 Data 0x88000006 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x0000 Data 0xbeef3097 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x0180 Data 0xbeef0301 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x0184 Data 0xbeef0201 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x0188 Data 0xbeef0202 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x018c Data 0xbeef0201 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x0194 Data 0xbeef0201 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x0198 Data 0xbeef0201 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x019c Data 0xbeef0201 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x01a0 Data 0xbeef0202 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x01a4 Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x01a8 Data 0xbeef0302 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x01ac Data 0xbeef0201 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x01b0 Data 0xbeef0201 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x02c8 Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x02cc Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x02d0 Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x02d4 Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x02d8 Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x02dc Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x02e0 Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x02e4 Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x02e8 Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x02ec Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x02f0 Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x02f4 Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x02f8 Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x02fc Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x0220 Data 0x00000001 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x03b0 Data 0x00100000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x1454 Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x1d80 Data 0x00000003 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x1450 Data 0x00030004 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x1e98 Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x17e0 Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x17e4 Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x17e8 Data 0x3f800000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x1f80 Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x1f84 Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x1f88 Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x1f8c Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x1f90 Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x1f94 Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x1f98 Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x1f9c Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x1fa0 Data 0x0000ffff May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x1fa4 Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x1fa8 Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x1fac Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x1fb0 Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x1fb4 Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x1fb8 Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x1fbc Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x0120 Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x0124 Data 0x00000001 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x0128 Data 0x00000002 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x1d88 Data 0x00001200 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x08fc Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x0394 Data 0x00000000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x0398 Data 0x3f800000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x1d7c Data 0xffff0000 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x1e94 Data 0x00000013 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: nouveau_channel_free: freeing fifo 1 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: Setting dpms mode 3 on vga encoder (output 0) May 1 09:46:31 lithium kernel: [drm] DAC-7: set mode 2048x1536 42 May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: Setting dpms mode 0 on vga encoder (output 0) May 1 09:46:31 lithium kernel: [drm] nouveau 0000:01:00.0: Output VGA-1 is running on CRTC 0 using output A I then booted into a different kernel, put back the Nvidia orignal driver, tried to start X, with no joy. In the logs was this: ay 1 10:30:44 lithium kernel: NVRM: Xid (0001:00): 1, Channel 00000000 Method 00000000 Data 01014700 May 1 10:30:44 lithium kernel: NVRM: Xid (0001:00): 36, L1 -> L0 Hmm. Then I had an idea, I tried to run a X11 program (evolution) through a ssh session from another of my machines. At this point I realised what the problem was. One of the X11 libraries had got overwritten somehow. After sshing into the machine from another machine, I ran evolution and it said that libXi was corrupted. The last time this happened, libdl-2.10.1.so got corrupted, which needed a recovery by booting a rescue CD and copying back a new libdl. I'm thinking the interaction between the GART, buffers and the memory on the card itself may, sometimes, overwrite something on rare occasions. This only happens with the Nouveau driver, I have never seen this happen before I switched over. Any ideas this is happening? I'm running the following: nouveau-drm 20100316 xf86-video-nouveau 0.0.15_pre20100329 mesa.git (mesa branch instead of master) linux kernel 2.6.32.8 Thanks -- http://www.munted.org.uk One very high maintenance cat living here.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel May 2010