Announcement

Collapse
No announcement yet.

Radeon R600 Tiling Patches Are Ready

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Zephiris
    replied
    I'm getting similar errors as PuckPoltergeist with a 6950 2GB with 1440x900 screen resolution.
    Similarly, all of the git versions are up to date and patched.

    These kinds of errors are with ColorTiling+ColorTiling2D set to off in xorg.conf:
    Code:
    [   14.397349] radeon 0000:01:00.0: evergreen_cs_track_validate_texture:728 texture bo too small (layer size 5529600, offset 0, max layer 1, depth 1, bo size 5324800) (1536 900)
    [   14.397351] [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
    [   14.905432] radeon 0000:01:00.0: evergreen_cs_track_validate_cb:443 cb[0] bo too small (layer size 5554176, offset 0, max layer 1, bo size 5529600, slice 21695)
    [   14.905434] radeon 0000:01:00.0: evergreen_cs_track_validate_cb:447 problematic surf: (1536 904) (1 4 1 0 0 4 0)
    [   14.905435] radeon 0000:01:00.0: evergreen_packet3_check:1918 invalid cmd stream 462
    These are with either on:
    Code:
    [  142.928652] radeon 0000:01:00.0: evergreen_cs_track_validate_texture:728 texture bo too small (layer size 5529600, offset 0, max layer 1, depth 1, bo size 5324800) (1536 900)
    [  142.928654] [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
    [  143.169816] radeon 0000:01:00.0: evergreen_surface_value_conv_check:329 invalid array mode 5
    [  143.169818] radeon 0000:01:00.0: evergreen_packet3_check:1918 invalid cmd stream 462
    [  143.169819] [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
    [  143.235577] radeon 0000:01:00.0: evergreen_surface_value_conv_check:329 invalid array mode 5
    [  143.235578] radeon 0000:01:00.0: evergreen_packet3_check:1918 invalid cmd stream 819
    [  143.235580] [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
    It's impossible to get a working screen (for me) unless the DDX is reverted to a non-patched version.

    Leave a comment:


  • droste
    replied
    Originally posted by allquixotic View Post
    64-bit kernel, 32-bit wine supported by 32-bit libs (32-bit mesa, 32-bit libdrm) but a 64-bit Xorg server and 64-bit DDX.

    You guys who are having the problem should try another desktop manager to see if it's KDM
    Works here with kdm/kwin (everything 64bit)

    Leave a comment:


  • allquixotic
    replied
    Originally posted by pixo View Post
    OK done some more testing.
    The problem seems to be only in 32bit
    I get the:
    [ 738.794944] radeon 0000:01:00.0: evergreen_cs_track_validate_depth:608 depth read bo too small (layer size 33423360, offset 0, max layer 1, bo size 11059200)
    [ 738.794947] radeon 0000:01:00.0: evergreen_packet3_check:1889 invalid cmd stream
    [ 738.794949] [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !

    In 64bit everithing works fine.
    Also if I disable CollorTiling2D 32bit works fine.
    Maybe there is something wrong inbetween 32bit libdrm and 64bit kernel.

    allquixotic can you tell if you run ST:Online on 32bit system or 64bit multilib?
    64-bit kernel, 32-bit wine supported by 32-bit libs (32-bit mesa, 32-bit libdrm) but a 64-bit Xorg server and 64-bit DDX.

    You guys who are having the problem should try another desktop manager to see if it's KDM

    Leave a comment:


  • glisse
    replied
    Originally posted by PuckPoltergeist View Post
    As soon as I replace the radeon_drv.so with the patched one, the screen gets diagonal distorted and I get the command stream errors. I don't even need to activate the ColorTiling2D option.
    I've downloaded the patch again and applied on top of 36c190671081967bac6fff48aaf66d67b639a48c to be sure, nothing got lost there. It applied cleanly (one trailing whitespace warning but I don't think this was responsible).
    What's your screen resolution ?

    Leave a comment:


  • PuckPoltergeist
    replied
    As soon as I replace the radeon_drv.so with the patched one, the screen gets diagonal distorted and I get the command stream errors. I don't even need to activate the ColorTiling2D option.
    I've downloaded the patch again and applied on top of 36c190671081967bac6fff48aaf66d67b639a48c to be sure, nothing got lost there. It applied cleanly (one trailing whitespace warning but I don't think this was responsible).

    Leave a comment:


  • PuckPoltergeist
    replied
    Originally posted by glisse View Post
    I can only play the guess game here but you might also be lacking the proper ddx. Unless kdm is doing something very weird and hiting a codepath i haven't hit. Also Option ColorTiling is useless with patched ddx, only option ColorTiling2D matter for r600 and newer.
    Ok, but Option ColorTiling was the one that was needed to get a working X again. I had to take it off by force. Additionally I had a complete xserver crash with the patched ddx when tried to view a movie with mplayer2. At least I suspect the ddx was responsible. The log says:
    Code:
    Backtrace:
    [ 40622.687] 0: /usr/bin/X (xorg_backtrace+0x26) [0x56d1a6]
    [ 40622.687] 1: /usr/bin/X (0x400000+0x170f49) [0x570f49]
    [ 40622.687] 2: /lib64/libpthread.so.0 (0x7f3535823000+0x10ff0) [0x7f3535833ff0]
    [ 40622.687] 3: /usr/lib64/xorg/modules/drivers/radeon_drv.so (0x7f3532872000+0xb3d34) [0x7f3532925d34]
    [ 40622.687] 4: /usr/lib64/xorg/modules/drivers/radeon_drv.so (0x7f3532872000+0xcffec) [0x7f3532941fec]
    [ 40622.687] 5: /usr/lib64/xorg/modules/drivers/radeon_drv.so (0x7f3532872000+0x7e06e) [0x7f35328f006e]
    [ 40622.688] 6: /usr/bin/X (0x400000+0x8c38e) [0x48c38e]
    [ 40622.688] 7: /usr/lib64/xorg/modules/extensions/libextmod.so (0x7f3533823000+0xf55e) [0x7f353383255e]
    [ 40622.688] 8: /usr/bin/X (0x400000+0x37039) [0x437039]
    [ 40622.688] 9: /usr/bin/X (0x400000+0x2613a) [0x42613a]
    [ 40622.688] 10: /lib64/libc.so.6 (__libc_start_main+0xed) [0x7f35347503cd]
    [ 40622.688] 11: /usr/bin/X (0x400000+0x264bd) [0x4264bd]
    [ 40622.688] Segmentation fault at address 0x2b0
    [ 40622.688]*
    Fatal server error:
    [ 40622.688] Caught signal 11 (Segmentation fault). Server aborting
    [ 40622.688]*
    [ 40622.688]
    I will test some more.

    Leave a comment:


  • glisse
    replied
    Originally posted by PuckPoltergeist View Post
    I've removed mesa completely, started kdm, stopped kdm, reinstalled mesa, started kdm. Everytime the same behavior. As soon as I've enabled ColorTiling (not even ColorTiling2D) I got a garbled screen and dmesg showed the command stream errors. Something goes wrong on my HD5470. And I doubt it's because improper mesa.

    PS: I've found some other error messages in dmesg:
    Code:
    radeon 0000:01:00.0: evergreen_surface_check_1d:244 stencil height 581 invalid must be aligned with 8
    radeon 0000:01:00.0: evergreen_cs_track_validate_stencil:502 stencil invalid (0x000000af 0x000031ed 0x00000401 0x00002022)
    radeon 0000:01:00.0: evergreen_packet3_check:1918 invalid cmd stream 929
    [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
    I can only play the guess game here but you might also be lacking the proper ddx. Unless kdm is doing something very weird and hiting a codepath i haven't hit. Also Option ColorTiling is useless with patched ddx, only option ColorTiling2D matter for r600 and newer.

    Leave a comment:


  • pixo
    replied
    OK done some more testing.
    The problem seems to be only in 32bit
    I get the:
    [ 738.794944] radeon 0000:01:00.0: evergreen_cs_track_validate_depth:608 depth read bo too small (layer size 33423360, offset 0, max layer 1, bo size 11059200)
    [ 738.794947] radeon 0000:01:00.0: evergreen_packet3_check:1889 invalid cmd stream
    [ 738.794949] [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !

    In 64bit everithing works fine.
    Also if I disable CollorTiling2D 32bit works fine.
    Maybe there is something wrong inbetween 32bit libdrm and 64bit kernel.

    allquixotic can you tell if you run ST:Online on 32bit system or 64bit multilib?

    env:
    gentoo 64bit
    01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Turks [Radeon HD 6570]
    Linux Kriziak 3.3.0-rc2+ #1 SMP Sun Feb 5 19:26:01 CET 2012 x86_64 Intel(R) Core(TM) i3-2100 CPU @ 3.10GHz GenuineIntel GNU/Linux
    OpenGL vendor string: X.Org
    OpenGL renderer string: Gallium 0.4 on AMD TURKS
    OpenGL version string: 2.1 Mesa 8.0-devel (git-189e6c7)
    OpenGL shading language version string: 1.20

    Using lidbrm, libdrm-32bit, mesa and mesa-32bit from git master. Both mesas are patched.

    Leave a comment:


  • PuckPoltergeist
    replied
    I've removed mesa completely, started kdm, stopped kdm, reinstalled mesa, started kdm. Everytime the same behavior. As soon as I've enabled ColorTiling (not even ColorTiling2D) I got a garbled screen and dmesg showed the command stream errors. Something goes wrong on my HD5470. And I doubt it's because improper mesa.

    PS: I've found some other error messages in dmesg:
    Code:
    radeon 0000:01:00.0: evergreen_surface_check_1d:244 stencil height 581 invalid must be aligned with 8
    radeon 0000:01:00.0: evergreen_cs_track_validate_stencil:502 stencil invalid (0x000000af 0x000031ed 0x00000401 0x00002022)
    radeon 0000:01:00.0: evergreen_packet3_check:1918 invalid cmd stream 929
    [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
    Last edited by PuckPoltergeist; 06 February 2012, 01:26 PM.

    Leave a comment:


  • PuckPoltergeist
    replied
    Originally posted by glisse View Post
    Issue on your end, something is not using the proper mesa.
    Ok, where does the inproper mesa come from? I've only one version installed (system one) and this is patched with your patch and the build-patch for egl/gbm. It's build by portage with the patches applied on top of the latest git (mesa and ddx).

    PS: How does kdm interact with mesa? I thought it's ddx only at this point.

    Leave a comment:

Working...
X