Created attachment 51644 [details] dmesg output I'm seeing texture and screen corruption and massive lag when this game loads. I suspect, but aren't positive, that the textures being affected are DDS format. I have to kill the game via SSH and in some cases switch to another VT and back. Seems to happen with or without libdxtn. Tried to get a gdb trace but after killing Spring gdb says no trace available. Card: HD6870 (Evergreen?) Distro: Gentoo 64-bit Kernel: 3.0.4 (radeon DRI compiled in, KMS on, BARTS_*, BTC_*, AMD firmware) Mesa: 7.11 Xorg: 1.11 libdrm: 2.4.26 A sample of the dmesg output I get is: radeon 0000:07:00.0: vbo resource seems too big for the bo radeon 0000:07:00.0: vbo resource seems too big for the bo radeon 0000:07:00.0: vbo resource seems too big for the bo radeon 0000:07:00.0: vbo resource seems too big for the bo radeon 0000:07:00.0: vbo resource seems too big for the bo radeon 0000:07:00.0: vbo resource seems too big for the bo [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x7a [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! radeon 0000:07:00.0: GPU lockup CP stall for more than 10010msec ------------[ cut here ]------------ WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:267 0xffffffff81252dc5() Hardware name: System Product Name GPU lockup (waiting for 0x0067447C last fence id 0x0067447B) Modules linked in: ipv6 ecb md4 cifs snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss joydev hid_logitech ff_memless usbhid usb_storage snd_hda_codec_hdmi snd_hda_codec_via ohci_hcd xhci_hcd pcspkr sg snd_hda_intel snd_hda_codec snd_hwdep snd_pcm r8169 mii snd_timer ssb ehci_hcd processor button snd pcmcia usbcore i2c_piix4 snd_page_alloc thermal_sys pcmcia_core Pid: 11731, comm: spring Tainted: G W 3.0.4-gentoo #12 Call Trace: [<ffffffff810335bb>] 0xffffffff810335bb [<ffffffff81033667>] 0xffffffff81033667 [<ffffffff81252dc5>] 0xffffffff81252dc5 [<ffffffff8104a44b>] ? 0xffffffff8104a44b [<ffffffff81267a2f>] 0xffffffff81267a2f [<ffffffff81268def>] 0xffffffff81268def [<ffffffff810a45af>] ? 0xffffffff810a45af [<ffffffff81213ac6>] 0xffffffff81213ac6 [<ffffffff81268d5b>] ? 0xffffffff81268d5b [<ffffffff810209ff>] ? 0xffffffff810209ff [<ffffffff810ce3c7>] 0xffffffff810ce3c7 [<ffffffff810c1536>] ? 0xffffffff810c1536 [<ffffffff810ce448>] 0xffffffff810ce448 [<ffffffff813e2f7b>] 0xffffffff813e2f7b ---[ end trace 4ff6bd64a104cf66 ]--- radeon 0000:07:00.0: GPU softreset radeon 0000:07:00.0: GRBM_STATUS=0xA27338A0 radeon 0000:07:00.0: GRBM_STATUS_SE0=0x1C000007 radeon 0000:07:00.0: GRBM_STATUS_SE1=0x0C000007 radeon 0000:07:00.0: SRBM_STATUS=0x20000AC0 radeon 0000:07:00.0: GRBM_SOFT_RESET=0x00007F6B radeon 0000:07:00.0: GRBM_STATUS=0x00003828 radeon 0000:07:00.0: GRBM_STATUS_SE0=0x00000007 radeon 0000:07:00.0: GRBM_STATUS_SE1=0x00000007 radeon 0000:07:00.0: SRBM_STATUS=0x200000C0 radeon 0000:07:00.0: GPU reset succeed radeon 0000:07:00.0: WB enabled [drm] ring test succeeded in 2 usecs [drm] ib test succeeded in 3 usecs [drm] force priority to high [drm] force priority to high ---------- dmesg and screenshots attached. Not sure what else you need, let me know.
Created attachment 51645 [details] Screenshot
Created attachment 51646 [details] after a few seconds it looks like this
Probably a Mesa driver issue, please attach the output of glxinfo.
Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.