[Bug 64471] Radeon HD6570 lockup in Brütal Legend
https://bugs.freedesktop.org/show_bug.cgi?id=64471 --- Comment #2 from Alex Deucher --- Does disabling hyperZ help? set env var R600_HYPERZ=0 -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130511/ebf84794/attachment.html>
[Bug 64449] xorg hangs randomly with Radeon HD 7450A
https://bugs.freedesktop.org/show_bug.cgi?id=64449 Alex Deucher changed: What|Removed |Added Assignee|xorg-driver-ati at lists.x.org |dri-devel at lists.freedesktop ||.org QA Contact|xorg-team at lists.x.org | Product|xorg|Mesa Version|7.7 (2011) |unspecified Component|Driver/Radeon |Drivers/Gallium/r600 --- Comment #1 from Alex Deucher --- Please attach your dmesg output as well. Is this a hybrid system with both an integrated Intel GPU and the discrete AMD GPU? Does updating to mesa 9.1.2 or mesa from git help? -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130511/053a0426/attachment.html>
[Bug 64475] Slow work and low brightness in Euro Track Simulator II game with HD6850
https://bugs.freedesktop.org/show_bug.cgi?id=64475 commiethebeastie at gmail.com changed: What|Removed |Added Attachment #79172|text/plain |image/png mime type|| -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130511/d316432f/attachment.html>
[Bug 64475] New: Slow work and low brightness in Euro Track Simulator II game with HD6850
https://bugs.freedesktop.org/show_bug.cgi?id=64475 Priority: medium Bug ID: 64475 Assignee: dri-devel at lists.freedesktop.org Summary: Slow work and low brightness in Euro Track Simulator II game with HD6850 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: commiethebeastie at gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/DRI/R600 Product: Mesa Created attachment 79172 --> https://bugs.freedesktop.org/attachment.cgi?id=79172=edit Euro Truck Simulator screenshot I tried to run the game with STEAM_RUNTIME="1" R600_LLVM=0 R600_HYPERZ=0 steam Driver "radeon" Option "SwapbuffersWait" "on" Option "ColorTiling" "off" Option "ColorTiling2D" "off" Option "EnablePageFlip" "on" Option "AccelMethod" "EXA" and STEAM_RUNTIME="1" R600_LLVM=1 R600_HYPERZ=1 R600_DEBUG=sb steam Driver "radeon" Option "SwapbuffersWait" "off" Option "ColorTiling" "on" Option "ColorTiling2D" "on" Option "EnablePageFlip" "off" Option "AccelMethod" "EXA" options But all times the game runs slowly and with low brightness. In the mirrors is visible to normal brightness. Also I can put apitrace file here. direct rendering: Yes OpenGL renderer string: Gallium 0.4 on AMD BARTS OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.0 (git-5471e39) OpenGL core profile shading language version string: 1.40 Linux localhost 3.9.0-next-20130509 #1 SMP PREEMPT Thu May 9 12:49:14 MSK 2013 x86_64 AMD FX(tm)-8120 Eight-Core Processor AuthenticAMD GNU/Linux -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130511/e2253519/attachment.html>
Radeon GPU lockup with Brütal Legend
2013-05-11 13:36 keltez?ssel, Boszormenyi Zoltan ?rta: > Hi, > > I just bought the Humble Bundle Double Fine Bundle and tried Br?tal Legend. > I got this when the second cutscene started and my Radeon HD6570 locked up. > > [18695.779736] radeon :01:00.0: GPU lockup CP stall for more than > 1msec > [18695.779745] radeon :01:00.0: GPU lockup (waiting for > 0x001805f9 last > fence id 0x001805f0) > [18695.779759] [drm] Disabling audio support > [18695.780874] radeon :01:00.0: Saved 631 dwords of commands on ring 0. > [18695.780911] BUG: unable to handle kernel paging request at c900120b2118 > [18695.781010] IP: [] radeon_fence_process+0x8e/0x160 > [radeon] > [18695.781128] PGD 42e00f067 PUD 42e030067 PMD 421d91067 PTE 0 > [18695.781213] Oops: [#1] SMP > [18695.781272] Modules linked in: ip6table_filter(F) ip6_tables(F) > ebtable_nat(F) > ebtables(F) ipt_MASQUERADE(F) iptable_nat(F) nf_nat_ipv4(F) nf_nat(F) > nf_conntrack_ipv4(F) nf_defrag_ipv4(F) xt_con > ntrack(F) nf_conntrack(F) xt_CHECKSUM(F) iptable_mangle(F) fuse(F) > be2iscsi(F) bnep(F) > iscsi_boot_sysfs(F) bluetooth(F) bnx2i(F) cnic(F) uio(F) bridge(F) stp(F) > llc(F) > cxgb4i(F) cxgb4(F) cxgb3i(F) > cxgb3(F) mdio(F) libcxgbi(F) ib_iser(F) rdma_cm(F) ib_addr(F) iw_cm(F) > ib_cm(F) ib_sa(F) > ib_mad(F) ib_core(F) iscsi_tcp(F) libiscsi_tcp(F) libiscsi(F) it87(F) > hwmon_vid(F) > scsi_transport_iscsi(F) s > nd_hda_codec_hdmi(F) snd_hda_codec_realtek(F) snd_hda_intel(F) > snd_hda_codec(F) > snd_hwdep(F) snd_seq(F) snd_seq_device(F) snd_pcm(F) snd_page_alloc(F) > snd_timer(F) > r8169(F) edac_core(F) usblp(F) sp > 5100_tco(F) snd(F) mii(F) > [18695.782361] i2c_piix4(F) edac_mce_amd(F) soundcore(F) fam15h_power(F) > k10temp(F) > eeepc_wmi(F) asus_wmi(F) microcode(F) pcspkr(F) serio_raw(F) sparse_keymap(F) > rfkill(F) > video(F) nfsd(F) auth_rp > cgss(F) nfs_acl(F) lockd(F) vhost_net(F) tun(F) macvtap(F) macvlan(F) > kvm_amd(F) kvm(F) > sunrpc(F) binfmt_misc(F) uinput(F) usb_storage(F) crc32c_intel(F) > ghash_clmulni_intel(F) > firewire_ohci(F) fir > ewire_core(F) 3w_9xxx(F) crc_itu_t(F) mxm_wmi(F) radeon(F) i2c_algo_bit(F) > drm_kms_helper(F) ttm(F) drm(F) i2c_core(F) wmi(F) [last unloaded: > ipmi_msghandler] > [18695.783094] CPU: 6 PID: 1107 Comm: Xorg Tainted: GF 3.9.0+ #1 > [18695.783172] Hardware name: To be filled by O.E.M. To be filled by > O.E.M./M5A99X EVO, > BIOS 1604 10/16/2012 > [18695.783281] task: 880421789770 ti: 88040049a000 task.ti: > 88040049a000 > [18695.783367] RIP: 0010:[] [] > radeon_fence_process+0x8e/0x160 [radeon] > [18695.783499] RSP: 0018:88040049bbc8 EFLAGS: 00010246 > [18695.783561] RAX: c900120b2118 RBX: 0002 RCX: > > [18695.783642] RDX: 0041 RSI: RDI: > 880425cde000 > [18695.783724] RBP: 88040049bc28 R08: 880425cdedc0 R09: > 880425cde208 > [18695.783805] R10: R11: 0005 R12: > 000c > [18695.783887] R13: 880425cdee08 R14: 0002 R15: > 880425cde000 > [18695.783969] FS: 7fee008b2940() GS:88043ed8() > knlGS:f7607780 > [18695.784062] CS: 0010 DS: ES: CR0: 8005003b > [18695.784153] CR2: c900120b2118 CR3: 0004229c3000 CR4: > 000407e0 > [18695.784238] DR0: DR1: DR2: > > [18695.784320] DR3: DR6: 0ff0 DR7: > 0400 > [18695.784401] Stack: > [18695.784427] 8804221a3c48 a0122cb0 88042814fd80 > 88040049bc30 > [18695.784526] 88040049bc18 813edd5e 880425cde000 > 880425cde000 > [18695.784624] 0005 880425cdee38 88040049bcf0 > 88040049bdd0 > [18695.784725] Call Trace: > [18695.784769] [] ? __dev_printk+0x5e/0x90 > [18695.784859] [] radeon_fence_count_emitted+0x20/0x70 > [radeon] > [18695.788569] [] radeon_ring_backup+0x58/0x150 [radeon] > [18695.792332] [] radeon_gpu_reset+0x93/0x230 [radeon] > [18695.796254] [] radeon_gem_handle_lockup.part.2+0xe/0x20 > [radeon] > [18695.800352] [] radeon_gem_wait_idle_ioctl+0xc8/0xe0 > [radeon] > [18695.804731] [] drm_ioctl+0x4d3/0x570 [drm] > [18695.806470] [] ? __set_task_blocked+0x37/0x80 > [18695.808120] [] ? radeon_gem_busy_ioctl+0x100/0x100 > [radeon] > [18695.809764] [] ? fpu_finit+0x22/0x40 > [18695.811338] [] ? init_fpu+0x61/0xc0 > [18695.812931] [] do_vfs_ioctl+0x97/0x580 > [18695.814507] [] ? > inode_has_perm.isra.32.constprop.62+0x2a/0x30 > [18695.816106] [] ? file_has_perm+0x97/0xb0 > [18695.817635] [] SyS_ioctl+0x91/0xb0 > [18695.819150] [] tracesys+0xdd/0xe2 > [18695.820695] Code: 49 87 55 00 48 39 d0 48 89 c3 41 ba 01 00 00 00 73 46 41 > 80 bf a0 > 16 00 00 00 4d 8b b1 f8 0b 00 00 0f 84 8a 00 00 00 49 8b 40 10 <8b> 00 48 89 > da 89 c0 48 > 21 ca 48 09 d0 48 39 c3 76 0b 4c 89 f2 > [18695.823912] RIP []
Radeon GPU lockup with Brütal Legend
Hi, I just bought the Humble Bundle Double Fine Bundle and tried Br?tal Legend. I got this when the second cutscene started and my Radeon HD6570 locked up. [18695.779736] radeon :01:00.0: GPU lockup CP stall for more than 1msec [18695.779745] radeon :01:00.0: GPU lockup (waiting for 0x001805f9 last fence id 0x001805f0) [18695.779759] [drm] Disabling audio support [18695.780874] radeon :01:00.0: Saved 631 dwords of commands on ring 0. [18695.780911] BUG: unable to handle kernel paging request at c900120b2118 [18695.781010] IP: [] radeon_fence_process+0x8e/0x160 [radeon] [18695.781128] PGD 42e00f067 PUD 42e030067 PMD 421d91067 PTE 0 [18695.781213] Oops: [#1] SMP [18695.781272] Modules linked in: ip6table_filter(F) ip6_tables(F) ebtable_nat(F) ebtables(F) ipt_MASQUERADE(F) iptable_nat(F) nf_nat_ipv4(F) nf_nat(F) nf_conntrack_ipv4(F) nf_defrag_ipv4(F) xt_con ntrack(F) nf_conntrack(F) xt_CHECKSUM(F) iptable_mangle(F) fuse(F) be2iscsi(F) bnep(F) iscsi_boot_sysfs(F) bluetooth(F) bnx2i(F) cnic(F) uio(F) bridge(F) stp(F) llc(F) cxgb4i(F) cxgb4(F) cxgb3i(F) cxgb3(F) mdio(F) libcxgbi(F) ib_iser(F) rdma_cm(F) ib_addr(F) iw_cm(F) ib_cm(F) ib_sa(F) ib_mad(F) ib_core(F) iscsi_tcp(F) libiscsi_tcp(F) libiscsi(F) it87(F) hwmon_vid(F) scsi_transport_iscsi(F) s nd_hda_codec_hdmi(F) snd_hda_codec_realtek(F) snd_hda_intel(F) snd_hda_codec(F) snd_hwdep(F) snd_seq(F) snd_seq_device(F) snd_pcm(F) snd_page_alloc(F) snd_timer(F) r8169(F) edac_core(F) usblp(F) sp 5100_tco(F) snd(F) mii(F) [18695.782361] i2c_piix4(F) edac_mce_amd(F) soundcore(F) fam15h_power(F) k10temp(F) eeepc_wmi(F) asus_wmi(F) microcode(F) pcspkr(F) serio_raw(F) sparse_keymap(F) rfkill(F) video(F) nfsd(F) auth_rp cgss(F) nfs_acl(F) lockd(F) vhost_net(F) tun(F) macvtap(F) macvlan(F) kvm_amd(F) kvm(F) sunrpc(F) binfmt_misc(F) uinput(F) usb_storage(F) crc32c_intel(F) ghash_clmulni_intel(F) firewire_ohci(F) fir ewire_core(F) 3w_9xxx(F) crc_itu_t(F) mxm_wmi(F) radeon(F) i2c_algo_bit(F) drm_kms_helper(F) ttm(F) drm(F) i2c_core(F) wmi(F) [last unloaded: ipmi_msghandler] [18695.783094] CPU: 6 PID: 1107 Comm: Xorg Tainted: GF 3.9.0+ #1 [18695.783172] Hardware name: To be filled by O.E.M. To be filled by O.E.M./M5A99X EVO, BIOS 1604 10/16/2012 [18695.783281] task: 880421789770 ti: 88040049a000 task.ti: 88040049a000 [18695.783367] RIP: 0010:[] [] radeon_fence_process+0x8e/0x160 [radeon] [18695.783499] RSP: 0018:88040049bbc8 EFLAGS: 00010246 [18695.783561] RAX: c900120b2118 RBX: 0002 RCX: [18695.783642] RDX: 0041 RSI: RDI: 880425cde000 [18695.783724] RBP: 88040049bc28 R08: 880425cdedc0 R09: 880425cde208 [18695.783805] R10: R11: 0005 R12: 000c [18695.783887] R13: 880425cdee08 R14: 0002 R15: 880425cde000 [18695.783969] FS: 7fee008b2940() GS:88043ed8() knlGS:f7607780 [18695.784062] CS: 0010 DS: ES: CR0: 8005003b [18695.784153] CR2: c900120b2118 CR3: 0004229c3000 CR4: 000407e0 [18695.784238] DR0: DR1: DR2: [18695.784320] DR3: DR6: 0ff0 DR7: 0400 [18695.784401] Stack: [18695.784427] 8804221a3c48 a0122cb0 88042814fd80 88040049bc30 [18695.784526] 88040049bc18 813edd5e 880425cde000 880425cde000 [18695.784624] 0005 880425cdee38 88040049bcf0 88040049bdd0 [18695.784725] Call Trace: [18695.784769] [] ? __dev_printk+0x5e/0x90 [18695.784859] [] radeon_fence_count_emitted+0x20/0x70 [radeon] [18695.788569] [] radeon_ring_backup+0x58/0x150 [radeon] [18695.792332] [] radeon_gpu_reset+0x93/0x230 [radeon] [18695.796254] [] radeon_gem_handle_lockup.part.2+0xe/0x20 [radeon] [18695.800352] [] radeon_gem_wait_idle_ioctl+0xc8/0xe0 [radeon] [18695.804731] [] drm_ioctl+0x4d3/0x570 [drm] [18695.806470] [] ? __set_task_blocked+0x37/0x80 [18695.808120] [] ? radeon_gem_busy_ioctl+0x100/0x100 [radeon] [18695.809764] [] ? fpu_finit+0x22/0x40 [18695.811338] [] ? init_fpu+0x61/0xc0 [18695.812931] [] do_vfs_ioctl+0x97/0x580 [18695.814507] [] ? inode_has_perm.isra.32.constprop.62+0x2a/0x30 [18695.816106] [] ? file_has_perm+0x97/0xb0 [18695.817635] [] SyS_ioctl+0x91/0xb0 [18695.819150] [] tracesys+0xdd/0xe2 [18695.820695] Code: 49 87 55 00 48 39 d0 48 89 c3 41 ba 01 00 00 00 73 46 41 80 bf a0 16 00 00 00 4d 8b b1 f8 0b 00 00 0f 84 8a 00 00 00 49 8b 40 10 <8b> 00 48 89 da 89 c0 48 21 ca 48 09 d0 48 39 c3 76 0b 4c 89 f2 [18695.823912] RIP [] radeon_fence_process+0x8e/0x160 [radeon] [18695.825527] RSP [18695.827077] CR2: c900120b2118 [18695.835008] ---[ end trace 294711b28bfd3975 ]--- Only the GPU locked up, I could ssh in and reboot it. My system is Fedora 18/x86_64, with some upgraded components: Kernel 3.9+ (commit
[Bug 64471] Radeon HD6570 lockup in Brütal Legend
https://bugs.freedesktop.org/show_bug.cgi?id=64471 --- Comment #1 from Zolt?n B?sz?rm?nyi --- Created attachment 79166 --> https://bugs.freedesktop.org/attachment.cgi?id=79166=edit Lockup from "continue" -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130511/0e84c25e/attachment-0001.html>
[Bug 64471] New: Radeon HD6570 lockup in Brütal Legend
https://bugs.freedesktop.org/show_bug.cgi?id=64471 Priority: medium Bug ID: 64471 Assignee: dri-devel at lists.freedesktop.org Summary: Radeon HD6570 lockup in Br?tal Legend Severity: major Classification: Unclassified OS: Linux (All) Reporter: zboszor at pr.hu Hardware: x86-64 (AMD64) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Created attachment 79165 --> https://bugs.freedesktop.org/attachment.cgi?id=79165=edit Lockup from "new game" I tried Br?tal Legend on Fedora 18/x86_64, the game itself if i386. The system has these newer-than-Fedora18 components: kernel 3.9+ (commit 51a26ae7a14b85c99c9be470c2d28eeeba0f26a3) libdrm 2.4.44 from 2.4.44-2.fc20 SRPM from Koji recompiled on F18 llvm-3.3 from May 7, before branching to 3.3 was done mesa 9.2 from May 7, commit was around 03ef60681e61a52dee7fa3285618c313cf13f50c compiled into an RPM with float textures enabled: $ rpm -q mesa-libGL mesa-libGL-9.2-0.1.fc18.x86_64 mesa-libGL-9.2-0.1.fc18.i686 The game makes the Radeon chip lock up, reliably at the same point, which is when the game starts after the long cutscene. Attached are two dmesgs, showing the same lockup. The first occurred when I started a new game and watched through the cutscene. The second occurred when I tried to continue the auto-saved game. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130511/a30a6fbc/attachment.html>
[Bug 63520] r300g regression (RV380): Strange rendering of light sources in Penumbra (bisected)
https://bugs.freedesktop.org/show_bug.cgi?id=63520 --- Comment #16 from PJBrs --- To be clear-- with "trying different numbers for max_alu_instructions", I mean changing c->Base.max_alu_insts into a number (e.g., 15) in line 157 of the file src/gallium/drivers/r300/compiler/r300_fragprog_emit.c. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130511/104c03f5/attachment.html>
[Bug 63520] r300g regression (RV380): Strange rendering of light sources in Penumbra (bisected)
https://bugs.freedesktop.org/show_bug.cgi?id=63520 PJBrs changed: What|Removed |Added Attachment #79156|text/plain |image/png mime type|| -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130511/57814946/attachment.html>
[Bug 63520] r300g regression (RV380): Strange rendering of light sources in Penumbra (bisected)
https://bugs.freedesktop.org/show_bug.cgi?id=63520 --- Comment #15 from PJBrs --- Created attachment 79160 --> https://bugs.freedesktop.org/attachment.cgi?id=79160=edit Log RADEON_DEBUG=fp,vp, maxALU=20, smart renderer -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130511/8a6d1360/attachment.html>
[Bug 63520] r300g regression (RV380): Strange rendering of light sources in Penumbra (bisected)
https://bugs.freedesktop.org/show_bug.cgi?id=63520 --- Comment #14 from PJBrs --- Created attachment 79158 --> https://bugs.freedesktop.org/attachment.cgi?id=79158=edit Log RADEON_DEBUG=fp,vp, maxALU=20, old renderer -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130511/3a55f283/attachment.html>
[Bug 63520] r300g regression (RV380): Strange rendering of light sources in Penumbra (bisected)
https://bugs.freedesktop.org/show_bug.cgi?id=63520 --- Comment #13 from PJBrs --- Created attachment 79157 --> https://bugs.freedesktop.org/attachment.cgi?id=79157=edit Screenshot, maxALU=20, smart renderer -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130511/18dba643/attachment.html>
[Bug 63520] r300g regression (RV380): Strange rendering of light sources in Penumbra (bisected)
https://bugs.freedesktop.org/show_bug.cgi?id=63520 --- Comment #12 from PJBrs --- Created attachment 79156 --> https://bugs.freedesktop.org/attachment.cgi?id=79156=edit Screenshot, maxALU=20, old renderer -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130511/2a09c091/attachment-0001.html>
[Bug 63520] r300g regression (RV380): Strange rendering of light sources in Penumbra (bisected)
https://bugs.freedesktop.org/show_bug.cgi?id=63520 --- Comment #11 from PJBrs --- Created attachment 79155 --> https://bugs.freedesktop.org/attachment.cgi?id=79155=edit Log RADEON_DEBUG=fp,vp, maxALU=8, smart renderer -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130511/a99e8a66/attachment.html>
[Bug 63520] r300g regression (RV380): Strange rendering of light sources in Penumbra (bisected)
https://bugs.freedesktop.org/show_bug.cgi?id=63520 --- Comment #10 from PJBrs --- Created attachment 79154 --> https://bugs.freedesktop.org/attachment.cgi?id=79154=edit Log RADEON_DEBUG=fp,vp, maxALU=8, old renderer -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130511/f6aa924c/attachment.html>
[Bug 63520] r300g regression (RV380): Strange rendering of light sources in Penumbra (bisected)
https://bugs.freedesktop.org/show_bug.cgi?id=63520 --- Comment #9 from PJBrs --- Created attachment 79152 --> https://bugs.freedesktop.org/attachment.cgi?id=79152=edit Screenshot, maxALU=8, smart renderer -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130511/9703a2e9/attachment.html>
[Bug 63520] r300g regression (RV380): Strange rendering of light sources in Penumbra (bisected)
https://bugs.freedesktop.org/show_bug.cgi?id=63520 --- Comment #8 from PJBrs --- Created attachment 79150 --> https://bugs.freedesktop.org/attachment.cgi?id=79150=edit Screenshot, maxALU=8, old renderer -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130511/c0ef6b7e/attachment.html>
[Bug 63520] r300g regression (RV380): Strange rendering of light sources in Penumbra (bisected)
https://bugs.freedesktop.org/show_bug.cgi?id=63520 --- Comment #7 from PJBrs --- Tom Stellard suggested that I do a binary search for incorrectly rendered shaders. I first compared debug log differences between old and smart schedulers. The logs show that eight shader programs are compiled differently by the two schedulers (I assume that a shader program is identified by "pc=$number" in the log.) For each of these shader programs I've listed the number of fragment program instructions and the number of hardware program instruction, for both old and smart scheduler: #instructions: fp old: fp smart: hwp old:hwp smart: Shader program: pc=814 12 8 7 pc=925 24 19 19 pc=10 22 22 17 18 pc=11 9 8 4 4 pc=15 6 5 3 2 pc=17 26 26 18 18 pc=18 20 19 11 11 pc=19 7 6 3 3 fp=fragment program hwp=hardware program I then did a binary analysis by trying different numbers for max_alu_instructions. I started with 15. With max_alu=15, there are some differences in shading between old and smart schedulers. Same with max_alu=8. With lower max_alu (tested 4, 6 and 7), these differences disappear. I did not notice any other differences in rendering between old and smart schedulers for max_alu=<15. However, I did not yet see the bug that I initially noticed when I reported it, so I tested further with max_alu=20. With max_alu=20, the smart scheduler displays the lighting bug that I initially wanted to report. With max_alu=17 and max_alu=18, rendering is the same as with max_alu=15 for both old and smart schedulars. With max_alu=19, a new difference in rendering between old and smart schedulers is introduced. A final difference is introduced with max_alu=20, which shows the bug that I originally saw. So, in sum, at least three shader programs are rendered differently by the old and smart schedulers--the first difference appears with max_alu=8, the second with max_alu=19 and the third difference with max_alu=20. The first difference suggests that "pc=8" is rendered incorrectly, since it has 7 instructions in the smart scheduler. Apparently, it does not do anything with the old scheduler (which results in 8 instructions), but increasing max_alu does not change those rendering bits rendered incorrectly by the smart scheduler. The second difference is either caused by shader program "pc=17", which consist of 18 instructions in both schedulers, or by "pc=10" which consists of 17 instructions with the old scheduler and 18 instructions with the smart scheduler. It's hard to say which shader program is rendered incorrectly (if not both are), because, with the old scheduler, there are rendering differences between max_alu=17 and max_alu=18. As the smart renderer shows no differences between max_alu=17 and max_alu=18, these must be caused by "pc=10". The third incorrectly rendered shader program would be "pc=9", with 19 instructions. What would a good starting point for searching the bug be? I think comparing the compilations for pc=19 and pc=8, because those almost certainly are rendered incorrectly due to changes in the scheduler. I've added screenshots and logs insofar I thought was necessary. I have more available, but I don't want to clog this report. I hope that the filenames speak for themselves :-) Please let me know what else I can do. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130511/e6d50f12/attachment.html>
[PATCH] radeon: Allow disabling UVD
On Wed, 8 May 2013, Parag Warudkar wrote: > > > On Wed, 8 May 2013, Christian K?nig wrote: > > > If you want to hack a bit on it you could try commenting out the calls to > > "radeon_set_uvd_clocks" in radeon_uvd.c. That should give you the default > > clocks of 100Mhz, not enough for usable decoding, but on SUMO based UVD > > blocks > > a very failsafe default. Commenting out the two calls to radeon_set_uvd_clocks() did not make any difference - still fails to initialize. BTW, this is also an EFI install. Sounds like for some people BIOS mode works based on the bug report. Also confirming that the suspend/resume issue persists with the SUMO_uvd.bin firmware loaded even if the UVD init fails. It is only by removing the firmware I can get the machine to suspend reliably. Parag
Radeon GPU lockup with Brütal Legend
Hi, I just bought the Humble Bundle Double Fine Bundle and tried Brütal Legend. I got this when the second cutscene started and my Radeon HD6570 locked up. [18695.779736] radeon :01:00.0: GPU lockup CP stall for more than 1msec [18695.779745] radeon :01:00.0: GPU lockup (waiting for 0x001805f9 last fence id 0x001805f0) [18695.779759] [drm] Disabling audio support [18695.780874] radeon :01:00.0: Saved 631 dwords of commands on ring 0. [18695.780911] BUG: unable to handle kernel paging request at c900120b2118 [18695.781010] IP: [a009f41e] radeon_fence_process+0x8e/0x160 [radeon] [18695.781128] PGD 42e00f067 PUD 42e030067 PMD 421d91067 PTE 0 [18695.781213] Oops: [#1] SMP [18695.781272] Modules linked in: ip6table_filter(F) ip6_tables(F) ebtable_nat(F) ebtables(F) ipt_MASQUERADE(F) iptable_nat(F) nf_nat_ipv4(F) nf_nat(F) nf_conntrack_ipv4(F) nf_defrag_ipv4(F) xt_con ntrack(F) nf_conntrack(F) xt_CHECKSUM(F) iptable_mangle(F) fuse(F) be2iscsi(F) bnep(F) iscsi_boot_sysfs(F) bluetooth(F) bnx2i(F) cnic(F) uio(F) bridge(F) stp(F) llc(F) cxgb4i(F) cxgb4(F) cxgb3i(F) cxgb3(F) mdio(F) libcxgbi(F) ib_iser(F) rdma_cm(F) ib_addr(F) iw_cm(F) ib_cm(F) ib_sa(F) ib_mad(F) ib_core(F) iscsi_tcp(F) libiscsi_tcp(F) libiscsi(F) it87(F) hwmon_vid(F) scsi_transport_iscsi(F) s nd_hda_codec_hdmi(F) snd_hda_codec_realtek(F) snd_hda_intel(F) snd_hda_codec(F) snd_hwdep(F) snd_seq(F) snd_seq_device(F) snd_pcm(F) snd_page_alloc(F) snd_timer(F) r8169(F) edac_core(F) usblp(F) sp 5100_tco(F) snd(F) mii(F) [18695.782361] i2c_piix4(F) edac_mce_amd(F) soundcore(F) fam15h_power(F) k10temp(F) eeepc_wmi(F) asus_wmi(F) microcode(F) pcspkr(F) serio_raw(F) sparse_keymap(F) rfkill(F) video(F) nfsd(F) auth_rp cgss(F) nfs_acl(F) lockd(F) vhost_net(F) tun(F) macvtap(F) macvlan(F) kvm_amd(F) kvm(F) sunrpc(F) binfmt_misc(F) uinput(F) usb_storage(F) crc32c_intel(F) ghash_clmulni_intel(F) firewire_ohci(F) fir ewire_core(F) 3w_9xxx(F) crc_itu_t(F) mxm_wmi(F) radeon(F) i2c_algo_bit(F) drm_kms_helper(F) ttm(F) drm(F) i2c_core(F) wmi(F) [last unloaded: ipmi_msghandler] [18695.783094] CPU: 6 PID: 1107 Comm: Xorg Tainted: GF 3.9.0+ #1 [18695.783172] Hardware name: To be filled by O.E.M. To be filled by O.E.M./M5A99X EVO, BIOS 1604 10/16/2012 [18695.783281] task: 880421789770 ti: 88040049a000 task.ti: 88040049a000 [18695.783367] RIP: 0010:[a009f41e] [a009f41e] radeon_fence_process+0x8e/0x160 [radeon] [18695.783499] RSP: 0018:88040049bbc8 EFLAGS: 00010246 [18695.783561] RAX: c900120b2118 RBX: 0002 RCX: [18695.783642] RDX: 0041 RSI: RDI: 880425cde000 [18695.783724] RBP: 88040049bc28 R08: 880425cdedc0 R09: 880425cde208 [18695.783805] R10: R11: 0005 R12: 000c [18695.783887] R13: 880425cdee08 R14: 0002 R15: 880425cde000 [18695.783969] FS: 7fee008b2940() GS:88043ed8() knlGS:f7607780 [18695.784062] CS: 0010 DS: ES: CR0: 8005003b [18695.784153] CR2: c900120b2118 CR3: 0004229c3000 CR4: 000407e0 [18695.784238] DR0: DR1: DR2: [18695.784320] DR3: DR6: 0ff0 DR7: 0400 [18695.784401] Stack: [18695.784427] 8804221a3c48 a0122cb0 88042814fd80 88040049bc30 [18695.784526] 88040049bc18 813edd5e 880425cde000 880425cde000 [18695.784624] 0005 880425cdee38 88040049bcf0 88040049bdd0 [18695.784725] Call Trace: [18695.784769] [813edd5e] ? __dev_printk+0x5e/0x90 [18695.784859] [a00a0180] radeon_fence_count_emitted+0x20/0x70 [radeon] [18695.788569] [a00b65f8] radeon_ring_backup+0x58/0x150 [radeon] [18695.792332] [a0089e53] radeon_gpu_reset+0x93/0x230 [radeon] [18695.796254] [a00b49de] radeon_gem_handle_lockup.part.2+0xe/0x20 [radeon] [18695.800352] [a00b5348] radeon_gem_wait_idle_ioctl+0xc8/0xe0 [radeon] [18695.804731] [a001f493] drm_ioctl+0x4d3/0x570 [drm] [18695.806470] [81070f47] ? __set_task_blocked+0x37/0x80 [18695.808120] [a00b5280] ? radeon_gem_busy_ioctl+0x100/0x100 [radeon] [18695.809764] [8101b462] ? fpu_finit+0x22/0x40 [18695.811338] [8101b791] ? init_fpu+0x61/0xc0 [18695.812931] [811b07c7] do_vfs_ioctl+0x97/0x580 [18695.814507] [812980ea] ? inode_has_perm.isra.32.constprop.62+0x2a/0x30 [18695.816106] [81299717] ? file_has_perm+0x97/0xb0 [18695.817635] [811b0d41] SyS_ioctl+0x91/0xb0 [18695.819150] [8166d867] tracesys+0xdd/0xe2 [18695.820695] Code: 49 87 55 00 48 39 d0 48 89 c3 41 ba 01 00 00 00 73 46 41 80 bf a0 16 00 00 00 4d 8b b1 f8 0b 00 00 0f 84 8a 00 00 00 49 8b 40 10 8b 00 48 89 da 89 c0 48 21 ca 48 09 d0 48 39 c3 76 0b 4c 89 f2 [18695.823912] RIP
[Bug 63520] r300g regression (RV380): Strange rendering of light sources in Penumbra (bisected)
https://bugs.freedesktop.org/show_bug.cgi?id=63520 --- Comment #7 from PJBrs pj...@floorenpj.xs4all.nl --- Tom Stellard suggested that I do a binary search for incorrectly rendered shaders. I first compared debug log differences between old and smart schedulers. The logs show that eight shader programs are compiled differently by the two schedulers (I assume that a shader program is identified by pc=$number in the log.) For each of these shader programs I've listed the number of fragment program instructions and the number of hardware program instruction, for both old and smart scheduler: #instructions: fp old: fp smart: hwp old:hwp smart: Shader program: pc=814 12 8 7 pc=925 24 19 19 pc=10 22 22 17 18 pc=11 9 8 4 4 pc=15 6 5 3 2 pc=17 26 26 18 18 pc=18 20 19 11 11 pc=19 7 6 3 3 fp=fragment program hwp=hardware program I then did a binary analysis by trying different numbers for max_alu_instructions. I started with 15. With max_alu=15, there are some differences in shading between old and smart schedulers. Same with max_alu=8. With lower max_alu (tested 4, 6 and 7), these differences disappear. I did not notice any other differences in rendering between old and smart schedulers for max_alu=15. However, I did not yet see the bug that I initially noticed when I reported it, so I tested further with max_alu=20. With max_alu=20, the smart scheduler displays the lighting bug that I initially wanted to report. With max_alu=17 and max_alu=18, rendering is the same as with max_alu=15 for both old and smart schedulars. With max_alu=19, a new difference in rendering between old and smart schedulers is introduced. A final difference is introduced with max_alu=20, which shows the bug that I originally saw. So, in sum, at least three shader programs are rendered differently by the old and smart schedulers--the first difference appears with max_alu=8, the second with max_alu=19 and the third difference with max_alu=20. The first difference suggests that pc=8 is rendered incorrectly, since it has 7 instructions in the smart scheduler. Apparently, it does not do anything with the old scheduler (which results in 8 instructions), but increasing max_alu does not change those rendering bits rendered incorrectly by the smart scheduler. The second difference is either caused by shader program pc=17, which consist of 18 instructions in both schedulers, or by pc=10 which consists of 17 instructions with the old scheduler and 18 instructions with the smart scheduler. It's hard to say which shader program is rendered incorrectly (if not both are), because, with the old scheduler, there are rendering differences between max_alu=17 and max_alu=18. As the smart renderer shows no differences between max_alu=17 and max_alu=18, these must be caused by pc=10. The third incorrectly rendered shader program would be pc=9, with 19 instructions. What would a good starting point for searching the bug be? I think comparing the compilations for pc=19 and pc=8, because those almost certainly are rendered incorrectly due to changes in the scheduler. I've added screenshots and logs insofar I thought was necessary. I have more available, but I don't want to clog this report. I hope that the filenames speak for themselves :-) Please let me know what else I can do. -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 63520] r300g regression (RV380): Strange rendering of light sources in Penumbra (bisected)
https://bugs.freedesktop.org/show_bug.cgi?id=63520 --- Comment #8 from PJBrs pj...@floorenpj.xs4all.nl --- Created attachment 79150 -- https://bugs.freedesktop.org/attachment.cgi?id=79150action=edit Screenshot, maxALU=8, old renderer -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 63520] r300g regression (RV380): Strange rendering of light sources in Penumbra (bisected)
https://bugs.freedesktop.org/show_bug.cgi?id=63520 --- Comment #9 from PJBrs pj...@floorenpj.xs4all.nl --- Created attachment 79152 -- https://bugs.freedesktop.org/attachment.cgi?id=79152action=edit Screenshot, maxALU=8, smart renderer -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 63520] r300g regression (RV380): Strange rendering of light sources in Penumbra (bisected)
https://bugs.freedesktop.org/show_bug.cgi?id=63520 --- Comment #10 from PJBrs pj...@floorenpj.xs4all.nl --- Created attachment 79154 -- https://bugs.freedesktop.org/attachment.cgi?id=79154action=edit Log RADEON_DEBUG=fp,vp, maxALU=8, old renderer -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 63520] r300g regression (RV380): Strange rendering of light sources in Penumbra (bisected)
https://bugs.freedesktop.org/show_bug.cgi?id=63520 --- Comment #11 from PJBrs pj...@floorenpj.xs4all.nl --- Created attachment 79155 -- https://bugs.freedesktop.org/attachment.cgi?id=79155action=edit Log RADEON_DEBUG=fp,vp, maxALU=8, smart renderer -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 63520] r300g regression (RV380): Strange rendering of light sources in Penumbra (bisected)
https://bugs.freedesktop.org/show_bug.cgi?id=63520 --- Comment #12 from PJBrs pj...@floorenpj.xs4all.nl --- Created attachment 79156 -- https://bugs.freedesktop.org/attachment.cgi?id=79156action=edit Screenshot, maxALU=20, old renderer -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 63520] r300g regression (RV380): Strange rendering of light sources in Penumbra (bisected)
https://bugs.freedesktop.org/show_bug.cgi?id=63520 --- Comment #13 from PJBrs pj...@floorenpj.xs4all.nl --- Created attachment 79157 -- https://bugs.freedesktop.org/attachment.cgi?id=79157action=edit Screenshot, maxALU=20, smart renderer -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 63520] r300g regression (RV380): Strange rendering of light sources in Penumbra (bisected)
https://bugs.freedesktop.org/show_bug.cgi?id=63520 --- Comment #14 from PJBrs pj...@floorenpj.xs4all.nl --- Created attachment 79158 -- https://bugs.freedesktop.org/attachment.cgi?id=79158action=edit Log RADEON_DEBUG=fp,vp, maxALU=20, old renderer -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 63520] r300g regression (RV380): Strange rendering of light sources in Penumbra (bisected)
https://bugs.freedesktop.org/show_bug.cgi?id=63520 --- Comment #15 from PJBrs pj...@floorenpj.xs4all.nl --- Created attachment 79160 -- https://bugs.freedesktop.org/attachment.cgi?id=79160action=edit Log RADEON_DEBUG=fp,vp, maxALU=20, smart renderer -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 63520] r300g regression (RV380): Strange rendering of light sources in Penumbra (bisected)
https://bugs.freedesktop.org/show_bug.cgi?id=63520 PJBrs pj...@floorenpj.xs4all.nl changed: What|Removed |Added Attachment #79156|text/plain |image/png mime type|| -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 63520] r300g regression (RV380): Strange rendering of light sources in Penumbra (bisected)
https://bugs.freedesktop.org/show_bug.cgi?id=63520 --- Comment #16 from PJBrs pj...@floorenpj.xs4all.nl --- To be clear-- with trying different numbers for max_alu_instructions, I mean changing c-Base.max_alu_insts into a number (e.g., 15) in line 157 of the file src/gallium/drivers/r300/compiler/r300_fragprog_emit.c. -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 64471] New: Radeon HD6570 lockup in Brütal Legend
https://bugs.freedesktop.org/show_bug.cgi?id=64471 Priority: medium Bug ID: 64471 Assignee: dri-devel@lists.freedesktop.org Summary: Radeon HD6570 lockup in Brütal Legend Severity: major Classification: Unclassified OS: Linux (All) Reporter: zbos...@pr.hu Hardware: x86-64 (AMD64) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Created attachment 79165 -- https://bugs.freedesktop.org/attachment.cgi?id=79165action=edit Lockup from new game I tried Brütal Legend on Fedora 18/x86_64, the game itself if i386. The system has these newer-than-Fedora18 components: kernel 3.9+ (commit 51a26ae7a14b85c99c9be470c2d28eeeba0f26a3) libdrm 2.4.44 from 2.4.44-2.fc20 SRPM from Koji recompiled on F18 llvm-3.3 from May 7, before branching to 3.3 was done mesa 9.2 from May 7, commit was around 03ef60681e61a52dee7fa3285618c313cf13f50c compiled into an RPM with float textures enabled: $ rpm -q mesa-libGL mesa-libGL-9.2-0.1.fc18.x86_64 mesa-libGL-9.2-0.1.fc18.i686 The game makes the Radeon chip lock up, reliably at the same point, which is when the game starts after the long cutscene. Attached are two dmesgs, showing the same lockup. The first occurred when I started a new game and watched through the cutscene. The second occurred when I tried to continue the auto-saved game. -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 64471] Radeon HD6570 lockup in Brütal Legend
https://bugs.freedesktop.org/show_bug.cgi?id=64471 --- Comment #1 from Zoltán Böszörményi zbos...@pr.hu --- Created attachment 79166 -- https://bugs.freedesktop.org/attachment.cgi?id=79166action=edit Lockup from continue -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 64475] New: Slow work and low brightness in Euro Track Simulator II game with HD6850
https://bugs.freedesktop.org/show_bug.cgi?id=64475 Priority: medium Bug ID: 64475 Assignee: dri-devel@lists.freedesktop.org Summary: Slow work and low brightness in Euro Track Simulator II game with HD6850 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: commiethebeas...@gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/DRI/R600 Product: Mesa Created attachment 79172 -- https://bugs.freedesktop.org/attachment.cgi?id=79172action=edit Euro Truck Simulator screenshot I tried to run the game with STEAM_RUNTIME=1 R600_LLVM=0 R600_HYPERZ=0 steam Driver radeon Option SwapbuffersWait on Option ColorTiling off Option ColorTiling2D off Option EnablePageFlip on Option AccelMethod EXA and STEAM_RUNTIME=1 R600_LLVM=1 R600_HYPERZ=1 R600_DEBUG=sb steam Driver radeon Option SwapbuffersWait off Option ColorTiling on Option ColorTiling2D on Option EnablePageFlip off Option AccelMethod EXA options But all times the game runs slowly and with low brightness. In the mirrors is visible to normal brightness. Also I can put apitrace file here. direct rendering: Yes OpenGL renderer string: Gallium 0.4 on AMD BARTS OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.0 (git-5471e39) OpenGL core profile shading language version string: 1.40 Linux localhost 3.9.0-next-20130509 #1 SMP PREEMPT Thu May 9 12:49:14 MSK 2013 x86_64 AMD FX(tm)-8120 Eight-Core Processor AuthenticAMD GNU/Linux -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 64475] Slow work and low brightness in Euro Track Simulator II game with HD6850
https://bugs.freedesktop.org/show_bug.cgi?id=64475 commiethebeas...@gmail.com changed: What|Removed |Added Attachment #79172|text/plain |image/png mime type|| -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 64449] xorg hangs randomly with Radeon HD 7450A
https://bugs.freedesktop.org/show_bug.cgi?id=64449 Alex Deucher ag...@yahoo.com changed: What|Removed |Added Assignee|xorg-driver-...@lists.x.org |dri-devel@lists.freedesktop ||.org QA Contact|xorg-t...@lists.x.org | Product|xorg|Mesa Version|7.7 (2011) |unspecified Component|Driver/Radeon |Drivers/Gallium/r600 --- Comment #1 from Alex Deucher ag...@yahoo.com --- Please attach your dmesg output as well. Is this a hybrid system with both an integrated Intel GPU and the discrete AMD GPU? Does updating to mesa 9.1.2 or mesa from git help? -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 64471] Radeon HD6570 lockup in Brütal Legend
https://bugs.freedesktop.org/show_bug.cgi?id=64471 --- Comment #2 from Alex Deucher ag...@yahoo.com --- Does disabling hyperZ help? set env var R600_HYPERZ=0 -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
