dri-devel April 2013

dri-devel@lists.freedesktop.org

142 participants
765 discussions

[Bug 34708] New: running piglit on r600 causes gkrellm to lose text color
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=34708 Summary: running piglit on r600 causes gkrellm to lose text color Product: Mesa Version: 7.10 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: hramrach(a)gmail.com Created an attachment (id=43790) --> (https://bugs.freedesktop.org/attachment.cgi?id=43790) screenshot of part of the gkrellm window After running some 3d apps (eg. piglit) parts of gkrellm lose text color. Firefox does not seem affected, nor are terminals. While taking the screenshot the Lock and Shoot buttons which were previously OK lost color while they were redrawn. As all the text that loses color is the value text (as opposed to the label text) it looks like any newly drawn text is not colored (black). -- 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 34373] New: RV620 : r600g : game ET:quakewars demo: GPU lockup
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=34373 Summary: RV620 : r600g : game ET:quakewars demo: GPU lockup Product: Mesa Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: aderumier(a)odiso.com Hi, now than s3tc works with r600g, i can test enemy territory quakewars. i'm using last drm-radeon-testing kernel and mesa-git. I have a freeze in game, maybe 5 seconds after i'm in the maps. (i can move in the maps, and the rendering is almost perfect). here the dmesg radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec ------------[ cut here ]------------ WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:248 radeon_fence_wait+0x318/0x370 [radeon]() Hardware name: Studio 1537 GPU lockup (waiting for 0x00144636 last fence id 0x00144633) Modules linked in: tun aes_i586 aes_generic ipv6 usbhid hid joydev uvcvideo arc4 videodev ecb snd_hda_codec_hdmi iwlagn snd_seq_dummy snd_hda_codec_idt snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device iwlcore snd_hda_intel mac80211 snd_hda_codec snd_pcm_oss psmouse snd_hwdep dell_wmi sparse_keymap firewire_ohci sdhci_pci rtc_cmos tg3 sdhci snd_pcm firewire_core uhci_hcd snd_mixer_oss snd_timer serio_raw mmc_core crc_itu_t rtc_core snd dell_laptop cfg80211 intel_agp ehci_hcd libphy wmi soundcore rtc_lib ac iTCO_wdt button battery thermal processor evdev sg dcdbas intel_gtt snd_page_alloc rfkill pcspkr i2c_i801 usbcore iTCO_vendor_support fuse ext4 mbcache jbd2 crc16 sr_mod cdrom sd_mod ahci libahci libata scsi_mod radeon ttm drm_kms_helper drm agpgart i2c_algo_bit i2c_core Pid: 23839, comm: etqw.x86 Tainted: G W 2.6.38-rc4-43255-g52280c2-dirty #1 Call Trace: [<c10443ed>] ? warn_slowpath_common+0x6d/0xa0 [<f8232aa8>] ? radeon_fence_wait+0x318/0x370 [radeon] [<f8232aa8>] ? radeon_fence_wait+0x318/0x370 [radeon] [<c104449e>] ? warn_slowpath_fmt+0x2e/0x30 [<f8232aa8>] ? radeon_fence_wait+0x318/0x370 [radeon] [<c10612d0>] ? autoremove_wake_function+0x0/0x40 [<f82332ac>] ? radeon_sync_obj_wait+0xc/0x10 [radeon] [<f80edc0e>] ? ttm_bo_wait+0xce/0x160 [ttm] [<f80f07d6>] ? ttm_bo_move_accel_cleanup+0x86/0x2a0 [ttm] [<f8233531>] ? radeon_move_blit.clone.0+0x131/0x1b0 [radeon] [<f823395c>] ? radeon_bo_move+0x3ac/0x3c0 [radeon] [<f80ee65d>] ? ttm_bo_list_ref_sub+0x1d/0x20 [ttm] [<f80eeece>] ? ttm_bo_handle_move_mem+0x10e/0x320 [ttm] [<f82335b0>] ? radeon_bo_move+0x0/0x3c0 [radeon] [<f80efdf5>] ? ttm_bo_move_buffer+0x115/0x130 [ttm] [<f80ee65d>] ? ttm_bo_list_ref_sub+0x1d/0x20 [ttm] [<f80efeb8>] ? ttm_bo_validate+0xa8/0x120 [ttm] [<f82347eb>] ? radeon_bo_list_validate+0x6b/0xc0 [radeon] [<f824b819>] ? radeon_cs_parser_relocs+0x1f9/0x240 [radeon] [<f824ba9a>] ? radeon_cs_parser_init+0x23a/0x2c0 [radeon] [<f824bc40>] ? radeon_cs_ioctl+0x70/0x180 [radeon] [<f8091ba1>] ? drm_ioctl+0x1e1/0x470 [drm] [<f824bbd0>] ? radeon_cs_ioctl+0x0/0x180 [radeon] [<c10dcfdc>] ? handle_pte_fault+0x38c/0x860 [<f80919c0>] ? drm_ioctl+0x0/0x470 [drm] [<c110a7f9>] ? do_vfs_ioctl+0x79/0x580 [<c1028316>] ? do_page_fault+0x1a6/0x440 [<c106ac36>] ? getnstimeofday+0x46/0x120 [<c10fcc9c>] ? fget_light+0x6c/0xb0 [<c110ad7f>] ? sys_ioctl+0x7f/0x90 [<c100389f>] ? sysenter_do_call+0x12/0x28 ---[ end trace 5e931a5b1aa3b579 ]--- [drm] Disabling audio support HDMI hot plug event: Pin=3 Presence_Detect=0 ELD_Valid=0 radeon 0000:01:00.0: GPU softreset radeon 0000:01:00.0: R_008010_GRBM_STATUS=0xA25334E0 radeon 0000:01:00.0: R_008014_GRBM_STATUS2=0x00000103 radeon 0000:01:00.0: R_000E50_SRBM_STATUS=0x200000C0 radeon 0000:01:00.0: R_008020_GRBM_SOFT_RESET=0x00007FEE radeon 0000:01:00.0: R_008020_GRBM_SOFT_RESET=0x00000001 radeon 0000:01:00.0: R_008010_GRBM_STATUS=0xA0003030 radeon 0000:01:00.0: R_008014_GRBM_STATUS2=0x00000003 radeon 0000:01:00.0: R_000E50_SRBM_STATUS=0x200080C0 radeon 0000:01:00.0: GPU reset succeed radeon 0000:01:00.0: WB enabled [drm] ring test succeeded in 1 usecs [drm] ib test succeeded in 1 usecs [drm] Enabling audio support HDMI hot plug event: Pin=3 Presence_Detect=0 ELD_Valid=0 radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec ------------[ cut here ]------------ WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:248 radeon_fence_wait+0x318/0x370 [radeon]() Hardware name: Studio 1537 GPU lockup (waiting for 0x0014463B last fence id 0x00144637) Modules linked in: tun aes_i586 aes_generic ipv6 usbhid hid joydev uvcvideo arc4 videodev ecb snd_hda_codec_hdmi iwlagn snd_seq_dummy snd_hda_codec_idt snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device iwlcore snd_hda_intel mac80211 snd_hda_codec snd_pcm_oss psmouse snd_hwdep dell_wmi sparse_keymap firewire_ohci sdhci_pci rtc_cmos tg3 sdhci snd_pcm firewire_core uhci_hcd snd_mixer_oss snd_timer serio_raw mmc_core crc_itu_t rtc_core snd dell_laptop cfg80211 intel_agp ehci_hcd libphy wmi soundcore rtc_lib ac iTCO_wdt button battery thermal processor evdev sg dcdbas intel_gtt snd_page_alloc rfkill pcspkr i2c_i801 usbcore iTCO_vendor_support fuse ext4 mbcache jbd2 crc16 sr_mod cdrom sd_mod ahci libahci libata scsi_mod radeon ttm drm_kms_helper drm agpgart i2c_algo_bit i2c_core Pid: 23839, comm: etqw.x86 Tainted: G W 2.6.38-rc4-43255-g52280c2-dirty #1 Call Trace: [<c10443ed>] ? warn_slowpath_common+0x6d/0xa0 [<f8232aa8>] ? radeon_fence_wait+0x318/0x370 [radeon] [<f8232aa8>] ? radeon_fence_wait+0x318/0x370 [radeon] [<c104449e>] ? warn_slowpath_fmt+0x2e/0x30 [<f8232aa8>] ? radeon_fence_wait+0x318/0x370 [radeon] [<c10612d0>] ? autoremove_wake_function+0x0/0x40 [<f82332ac>] ? radeon_sync_obj_wait+0xc/0x10 [radeon] [<f80edc0e>] ? ttm_bo_wait+0xce/0x160 [ttm] [<f80f07d6>] ? ttm_bo_move_accel_cleanup+0x86/0x2a0 [ttm] [<f8233531>] ? radeon_move_blit.clone.0+0x131/0x1b0 [radeon] [<f823395c>] ? radeon_bo_move+0x3ac/0x3c0 [radeon] [<f80ee65d>] ? ttm_bo_list_ref_sub+0x1d/0x20 [ttm] [<f80eeece>] ? ttm_bo_handle_move_mem+0x10e/0x320 [ttm] [<f82335b0>] ? radeon_bo_move+0x0/0x3c0 [radeon] [<f80efdf5>] ? ttm_bo_move_buffer+0x115/0x130 [ttm] [<f80ee65d>] ? ttm_bo_list_ref_sub+0x1d/0x20 [ttm] [<f80efeb8>] ? ttm_bo_validate+0xa8/0x120 [ttm] [<f82347eb>] ? radeon_bo_list_validate+0x6b/0xc0 [radeon] [<f824b819>] ? radeon_cs_parser_relocs+0x1f9/0x240 [radeon] [<f824ba9a>] ? radeon_cs_parser_init+0x23a/0x2c0 [radeon] [<f824bc40>] ? radeon_cs_ioctl+0x70/0x180 [radeon] [<c1032860>] ? __wake_up+0x40/0x50 [<f8091ba1>] ? drm_ioctl+0x1e1/0x470 [drm] [<f824bbd0>] ? radeon_cs_ioctl+0x0/0x180 [radeon] [<c10dccce>] ? handle_pte_fault+0x7e/0x860 [<c10c5a55>] ? __free_pages+0x35/0x40 [<c10da875>] ? __pte_alloc+0xa5/0xb0 [<f80919c0>] ? drm_ioctl+0x0/0x470 [drm] [<c110a7f9>] ? do_vfs_ioctl+0x79/0x580 [<c1028316>] ? do_page_fault+0x1a6/0x440 [<c10def5a>] ? remove_vma+0x3a/0x50 [<c10e03a6>] ? do_munmap+0x1f6/0x270 [<c10fcc9c>] ? fget_light+0x6c/0xb0 [<c110ad7f>] ? sys_ioctl+0x7f/0x90 [<c100389f>] ? sysenter_do_call+0x12/0x28 ---[ end trace 5e931a5b1aa3b57a ]--- [drm] Disabling audio support HDMI hot plug event: Pin=3 Presence_Detect=0 ELD_Valid=0 radeon 0000:01:00.0: GPU softreset radeon 0000:01:00.0: R_008010_GRBM_STATUS=0xA23334E0 radeon 0000:01:00.0: R_008014_GRBM_STATUS2=0x00000003 radeon 0000:01:00.0: R_000E50_SRBM_STATUS=0x200000C0 radeon 0000:01:00.0: R_008020_GRBM_SOFT_RESET=0x00007FEE radeon 0000:01:00.0: R_008020_GRBM_SOFT_RESET=0x00000001 radeon 0000:01:00.0: R_008010_GRBM_STATUS=0xA0003030 radeon 0000:01:00.0: R_008014_GRBM_STATUS2=0x00000003 radeon 0000:01:00.0: R_000E50_SRBM_STATUS=0x200080C0 radeon 0000:01:00.0: GPU reset succeed radeon 0000:01:00.0: WB enabled -- 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 33796] New: projtex demo doesn't work on 760G
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=33796 Summary: projtex demo doesn't work on 760G Product: Mesa Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: randrik(a)mail.ru I see no image inside black square. It works with swrast. Software config: Kernel - 2.6.37 vanilla ddx - 66eb81b62e5ae8e1d7bd44ed8a179e5ec1ca69af (UMS: Slightly improve xserver version check.) libdrm - 550fe2ca3b29ad2191eab4fdfbed9ed21e25492d (intel: compile fix for previous commit after rebasing) xserver - 1.9 branch up to 089a510dc9511721817df63bf9a968a10b842198 (mi: Fix the debug message) Hardware: 01:05.0 VGA compatible controller: ATI Technologies Inc 760G [Radeon 3000] (prog-if 00 [VGA controller]) Subsystem: Giga-byte Technology Device d000 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 18 Region 0: Memory at d0000000 (32-bit, prefetchable) [size=256M] Region 1: I/O ports at ee00 [size=256] Region 2: Memory at fdfe0000 (32-bit, non-prefetchable) [size=64K] Region 5: Memory at fde00000 (32-bit, non-prefetchable) [size=1M] Expansion ROM at <unassigned> [disabled] Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+ Address: 0000000000000000 Data: 0000 Kernel driver in use: radeon Kernel modules: radeon -- 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 30651] New: r600g: gl output in mplayer have no colors if used with a fragment program with additional lookup and bicubic B-spline filtering
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=30651 Summary: r600g: gl output in mplayer have no colors if used with a fragment program with additional lookup and bicubic B-spline filtering Product: Mesa Version: git Platform: All OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: virtuousfox(a)gmail.com when i try to play video in mplayer with option 'gl:yuv=4,lscale=1,cscale=1' and r600g in use, it displays no colors. if it's 'gl:yuv=3', colors are ok. 'gl:yuv=5' seems also ok. sorry, i haven't tested yuv=4 without 'lscale=1,cscale=1' and immediately rebuilded mesa without gallium, so i don't know which of those to blame actually. my bet is 'yuv=4' and "a fragment program with additional lookup". by the way, what yuv and *scale options do you recommend for use with ATI/AMD >=r600 cards in terms of performance and quality ? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 10

[Bug 62578] New: r300: Implementation error: Render targets are too big in r300_set_framebuffer_state, refusing to bind framebuffer state!
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=62578 Priority: medium Bug ID: 62578 Assignee: dri-devel(a)lists.freedesktop.org Summary: r300: Implementation error: Render targets are too big in r300_set_framebuffer_state, refusing to bind framebuffer state! Severity: major Classification: Unclassified OS: All Reporter: orion(a)cora.nwra.com Hardware: x86 (IA32) Status: NEW Version: 9.1 Component: Drivers/DRI/r300 Product: Mesa Created attachment 76846 --> https://bugs.freedesktop.org/attachment.cgi?id=76846&action=edit Xorg.0.log Running KDE 4.10.1 on Fedora 18. After login, screen flickers a bit but nothing is displayed other than the background image. .xsession-errors contains: OpenGL vendor string: X.Org R300 Project OpenGL renderer string: Gallium 0.4 on ATI RV370 OpenGL version string: 2.1 Mesa 9.1 OpenGL shading language version string: 1.20 Driver: R300G GPU class: R300 OpenGL version: 2.1 GLSL version: 1.20 Mesa version: 9.1 Linux kernel version: 3.8.3 Direct rendering: yes Requires strict binding: yes GLSL shaders: limited Texture NPOT support: limited Virtual Machine: no r300: Implementation error: Render targets are too big in r300_set_framebuffer_state, refusing to bind framebuffer state! this r300 messages keeps repeating. kernel 3.8.3-203.fc18.i686.PAE 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV370 5B60 [Radeon X300 (PCIE)] Just updated from Fedora 16 where this system was working fine. -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 61883] New: wine shader_generate_glsl_declarations fail
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=61883 Priority: medium Bug ID: 61883 Assignee: dri-devel(a)lists.freedesktop.org Summary: wine shader_generate_glsl_declarations fail Severity: normal Classification: Unclassified OS: Linux (All) Reporter: victoraur.santos(a)gmail.com Hardware: All Status: NEW Version: 9.1 Component: Drivers/DRI/r300 Product: Mesa Trying to run RE4 on my r300 freeze completely system Submitted on wine bug tracker and suggested to report here. ---- err:winediag:shader_generate_glsl_declarations The hardware does not support enough uniform components to run this shader, it may not render correctly. ---- and lot of: ---- r300: ERROR: FS input fog unassigned, not enough hardware slots. (it's not a bug, do not report it) ---- for more details and full log see: http://bugs.winehq.org/show_bug.cgi?id=33129 -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 60965] New: [r300g] Anno1701: flickering colorful corruption over some models
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=60965 Priority: medium Bug ID: 60965 Assignee: dri-devel(a)lists.freedesktop.org Summary: [r300g] Anno1701: flickering colorful corruption over some models Severity: normal Classification: Unclassified OS: All Reporter: pavel.ondracka(a)email.cz Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/r300 Product: Mesa Created attachment 74949 --> https://bugs.freedesktop.org/attachment.cgi?id=74949&action=edit RADEON_DEBUG=fp,vp In Anno1701, there are flickering colorful spots over some models. It looks similar to the bug 60552, except the spots are colorful instead of black and they don't go away with RADEON_DEBUG=noopt. Setting Wine to use ARB shader rendering backend instead of GLSL makes the problem go away indicating another bug in the shader compiler. Apitrace here http://pavel.ondracka.cz/Anno1701.trace (renders fine with proprietary NVIDIA drivers). Wine: 1.5.23 GPU: RV530 Mesa: f1ab67c13ab97f19c08d99c6ba101edc7d7b80e6 Kernel: 3.7.3-101.fc17.i686 -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 60963] New: [r300g] Anno1701: some models are red
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=60963 Priority: medium Bug ID: 60963 Assignee: dri-devel(a)lists.freedesktop.org Summary: [r300g] Anno1701: some models are red Severity: normal Classification: Unclassified OS: All Reporter: pavel.ondracka(a)email.cz Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/r300 Product: Mesa Created attachment 74948 --> https://bugs.freedesktop.org/attachment.cgi?id=74948&action=edit RADEON_DEBUG=fp,vp In Anno1701, some models are red, however they are rendered with correct colors when RADEON_DEBUG=noopt is used (or with glsl disabled in Wine). Apitrace here http://pavel.ondracka.cz/Anno1701.trace (renders fine with proprietary NVIDIA drivers). Wine: 1.5.23 GPU: RV530 Mesa: f1ab67c13ab97f19c08d99c6ba101edc7d7b80e6 Kernel: 3.7.3-101.fc17.i686 -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 60555] New: [r300g] RADEON_NO_TCL=1 hardlock
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=60555 Priority: lowest Bug ID: 60555 Assignee: dri-devel(a)lists.freedesktop.org Summary: [r300g] RADEON_NO_TCL=1 hardlock Severity: trivial Classification: Unclassified OS: All Reporter: pavel.ondracka(a)email.cz Hardware: Other Status: NEW Version: git Component: Drivers/DRI/r300 Product: Mesa This is not really a bug as normal user will never encounter this, just some nuisance I discovered when I tried to investigate bug 60552 a little bit. When RADEON_NO_TCL=1 is used (which is useful in diagnosing compiler bugs), the whole machine sometimes hardlocks. App from bug 60552 is a good way to reproduce this. This debug option should be either fixed, or if it no longer considered useful, then it should be removed. BTW this was working not a year ago, so I can probably run a bisect if needed. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 60552] New: [r300g] Carvisualizer webgl demo: black flickering spots over the car
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=60552 Priority: medium Bug ID: 60552 Assignee: dri-devel(a)lists.freedesktop.org Summary: [r300g] Carvisualizer webgl demo: black flickering spots over the car Severity: normal Classification: Unclassified OS: All Reporter: pavel.ondracka(a)email.cz URL: http://carvisualizer.plus360degrees.com/threejs/ Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/r300 Product: Mesa Created attachment 74497 --> https://bugs.freedesktop.org/attachment.cgi?id=74497&action=edit screenshot In the Car Visualizer Webgl demo, there are some flickering black spots on the car. This is probably a bug in the shader compiler, as RADEON_DEBUG=noopt works around this. Specifically its the register_rename pass that causes this, when it is disabled in r3xx_fragprog.c, everything is fine. Also when I disable only the dataflow optimize pass, there is still some flickering but much less. Firefox 18.0 GPU:RV530 Mesa: 0e2f26d5ea26febd16173aa8bbf7427b090e320f Kernel: 3.7.3-101.fc17.i686 -- You are receiving this mail because: You are the assignee for the bug.

1 4

← Newer
1
...
14
15
16
17
18
19
20
...
77
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel April 2013