Announcement

Collapse
No announcement yet.

More Radeon & AMDGPU Fixes Line-Up For Linux 4.10

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

  • #21
    Originally posted by netkas View Post
    tried 4.9.5 kernel

    with radeon - same patch, same behaviour


    with amdgpu:
    the log - http://pastebin.com/NiTiWAYi
    the patch - http://rgho.st/68s7Zq9V9

    system doesn't freeze.

    but everything is green.

    in console, black became green, white is still white.
    Xorg - everything is greenish, I can see colors - red, blue, green (in glxgear), but the darker the color the more greenish it is. the brighter the color the more magentish it is.
    Are you meanwhile in contact with AMD and/or Mesa developers about the side-effects of your fix?

    I don't know anything about this, so I can only contribute an un-educated guess: perhaps something else needs to be done when the second VBIOS is recognized, like allocating a second color translation table, and without that the two monitors "share" some data structures that are not designed to be shared.

    Comment


    • #22
      Thanks for fixing it Alex!

      some update: it's greenish only on hdmi, it's ok on DP

      Comment


      • #23
        Originally posted by debianxfce View Post

        It is fixed:
        https://cgit.freedesktop.org/~agd5f/...1047fc08e6a5a9
        This proves that amd reacts fast and end users, use the wip kernel.
        Thanks for letting us know! I suppose this works on standard builds once admgpu supports Tahiti cards by default ?!

        Comment


        • #24
          Made a long test, after about 30 minutes the screen went black and system freezed (amdgpu, 4.11-wip)
          any idea how I can retrive some logs in such situation?

          Comment


          • #25
            it doesn't happen when I use nomodeset kernel option.
            it doesn't happen when I run Unigine Valley.

            Comment


            • #26
              I meant the issue doesn't happen when amdgpu is not used, so the issue is in amdgpu.

              Comment


              • #27
                Hello
                I was able to get a log from this strange crash, in fact it's only driver crash, not whole system:

                Code:
                [ 1577.221542] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: id=0018
                [ 1577.221551] pcieport 0000:00:03.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, id=0018(Requester ID)
                [ 1577.221556] pcieport 0000:00:03.0:   device [8086:0e08] error status/mask=00004000/00000000
                [ 1577.221559] pcieport 0000:00:03.0:    [14] Completion Timeout     (First)
                [ 1577.221564] pcieport 0000:00:03.0: broadcast error_detected message
                [ 1577.221566] pcieport 0000:00:03.0: AER: Device recovery failed
                [ 1577.239031] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: id=0018
                [ 1577.239043] pcieport 0000:00:03.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, id=0018(Requester ID)
                [ 1577.239052] pcieport 0000:00:03.0:   device [8086:0e08] error status/mask=00004000/00000000
                [ 1577.239076] pcieport 0000:00:03.0:    [14] Completion Timeout     (First)
                [ 1577.239088] pcieport 0000:00:03.0: broadcast error_detected message
                [ 1577.239091] pcieport 0000:00:03.0: AER: Device recovery failed
                [ 1577.255393] pciehp 0000:00:03.0:pcie004: Slot(5-3): Link Down
                [ 1577.255439] pcieport 0000:00:03.0: AER: Multiple Uncorrected (Fatal) error received: id=0018
                [ 1577.255451] pcieport 0000:00:03.0: PCIe Bus Error: severity=Uncorrected (Fatal), type=Transaction Layer, id=0018(Requester ID)
                [ 1577.255456] pcieport 0000:00:03.0:   device [8086:0e08] error status/mask=00004020/00000000
                [ 1577.255460] pcieport 0000:00:03.0:    [ 5] Surprise Down Error   
                [ 1577.255465] pcieport 0000:00:03.0:    [14] Completion Timeout     (First)
                [ 1577.255472] pcieport 0000:00:03.0: broadcast error_detected message
                [ 1577.255475] amdgpu 0000:06:00.0: device has no AER-aware driver
                [ 1577.255478] snd_hda_intel 0000:06:00.1: device has no AER-aware driver
                [ 1577.288954] pciehp 0000:00:03.0:pcie004: Slot(5-3): Link Up
                [ 1577.288969] pciehp 0000:00:03.0:pcie004: Slot(5-3): Link Up event queued; currently getting powered off
                [ 1582.683884] [drm:atom_op_jump [amdgpu]] *ERROR* atombios stuck in loop for more than 5secs aborting
                [ 1582.683909] [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing D17E (len 62, WS 0, PS 0) @ 0xD19A
                [ 1582.683935] pcieport 0000:00:03.0: Root Port link has been reset
                [ 1582.683940] pcieport 0000:00:03.0: AER: Device recovery failed
                pcieport 0000:00:03.0 is pci bridge behind master card (with outputs)

                Code:
                 \-[0000:00]-+-00.0  Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 DMI2
                             +-02.0-[02]--+-00.0  Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT [Radeon R7 370 / R9 270X/370 OEM]
                             |            \-00.1  Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series]
                             +-03.0-[06]--+-00.0  Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT [Radeon R7 370 / R9 270X/370 OEM]
                             |            \-00.1  Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series]

                Comment

                Working...
                X