[Bug 35452] New: [RADEON:KMS:RS780:R600G] Graphical Glitches when running games under wine

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sat Mar 19 14:25:27 PDT 2011


https://bugs.freedesktop.org/show_bug.cgi?id=35452

           Summary: [RADEON:KMS:RS780:R600G] Graphical Glitches when
                    running games under wine
           Product: xorg
           Version: git
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/Radeon
        AssignedTo: xorg-driver-ati at lists.x.org
        ReportedBy: mike at fireburn.co.uk
         QAContact: xorg-team at lists.x.org


Created an attachment (id=44620)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=44620)
dmesg of card initialisation 

When I run Warcraft 3 under wine on my 64bit system the screen shows some
corruption then displays the start screen whilst flashing in and out and the
game complains there is no audio hardware

The A/V is outputted via HDMI and sound and glxgears (32bit and 64bit) run
without issue at about 300fps when vblank_mode=0

Using the keyboard I can close the game but the visual glitches continue to the
desktop (I run kwin)

the lspci -nn output for the device is

01:05.0 VGA compatible controller [0300]: ATI Technologies Inc M880G [Mobility
Radeon HD 4200] [1002:9712]

I compiled the 32bit libdrm and mesa libraries myself from the latest git to
make sure the issue hasn't already been fixed and I've also tried the latest
kernel 2.6.39-rc0 too.

With the classic r600 driver the game doesn't even start I have to ssh in to
kill it and there are no graphical errors after

I'll attach dmesg initialisation of the card 

The errors show as this:

[drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -35!
radeon 0000:01:05.0: GPU lockup CP stall for more than 10040msec
[drm] Disabling audio support
radeon 0000:01:05.0: GPU softreset 
radeon 0000:01:05.0:   R_008010_GRBM_STATUS=0xB2333030
radeon 0000:01:05.0:   R_008014_GRBM_STATUS2=0x00000003
radeon 0000:01:05.0:   R_000E50_SRBM_STATUS=0x20000040
radeon 0000:01:05.0:   R_008020_GRBM_SOFT_RESET=0x00007FEE
radeon 0000:01:05.0: R_008020_GRBM_SOFT_RESET=0x00000001
radeon 0000:01:05.0:   R_008010_GRBM_STATUS=0xA0003030
radeon 0000:01:05.0:   R_008014_GRBM_STATUS2=0x00000003
radeon 0000:01:05.0:   R_000E50_SRBM_STATUS=0x20008040
radeon 0000:01:05.0: GPU reset succeed
radeon 0000:01:05.0: WB enabled
[drm] ring test succeeded in 0 usecs
[drm] ib test succeeded in 1 usecs
[drm] Enabling audio support
[drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -35!
radeon 0000:01:05.0: GPU lockup CP stall for more than 10040msec
[drm] Disabling audio support
radeon 0000:01:05.0: GPU softreset 
radeon 0000:01:05.0:   R_008010_GRBM_STATUS=0xB2333030
radeon 0000:01:05.0:   R_008014_GRBM_STATUS2=0x00000003
radeon 0000:01:05.0:   R_000E50_SRBM_STATUS=0x20000040
radeon 0000:01:05.0:   R_008020_GRBM_SOFT_RESET=0x00007FEE
radeon 0000:01:05.0: R_008020_GRBM_SOFT_RESET=0x00000001
radeon 0000:01:05.0:   R_008010_GRBM_STATUS=0xA0003030
radeon 0000:01:05.0:   R_008014_GRBM_STATUS2=0x00000003
radeon 0000:01:05.0:   R_000E50_SRBM_STATUS=0x20008040
radeon 0000:01:05.0: GPU reset succeed
radeon 0000:01:05.0: WB enabled
[drm] ring test succeeded in 0 usecs
[drm] ib test succeeded in 1 usecs
[drm] Enabling audio support


Using the old kernel and user space I used to get errors about invalid command
streams too

Mar 19 20:29:33 quark kernel: [drm:radeon_cs_ioctl] *ERROR* Failed to parse
relocation -35!
Mar 19 20:29:33 quark kernel: radeon 0000:01:05.0: texture bo too small (1920
1080 26 0 -> 8294400 have 1720320)
Mar 19 20:29:33 quark kernel: radeon 0000:01:05.0: alignments 1920 1 1 1
Mar 19 20:29:33 quark kernel: [drm:radeon_cs_ioctl] *ERROR* Invalid command
stream !


Please let me know if there is any extra messages you require, or reruns with
debugging turned on

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the xorg-driver-ati mailing list