All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tomasz Moń" <desowin@gmail.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: "Deucher, Alexander" <alexander.deucher@amd.com>,
	amd-gfx list <amd-gfx@lists.freedesktop.org>
Subject: Re: Waiting for fences timed out on MacBook Pro 2019
Date: Tue, 13 Jul 2021 09:00:30 +0200	[thread overview]
Message-ID: <CAOHtt38Eg0jn13DsX85Y3782dzxppwXbNH-KOrGfd8Pkvd51uw@mail.gmail.com> (raw)
In-Reply-To: <CADnq5_Mx3oR6SGSz9R3muVrv4zLhYJt8Zf=uDnNx9p6mXfbGUA@mail.gmail.com>

On Mon, Jul 12, 2021 at 8:35 PM Alex Deucher <alexdeucher@gmail.com> wrote:
> On Mon, Jul 12, 2021 at 5:57 AM Tomasz Moń <desowin@gmail.com> wrote:
> > I am having trouble getting Linux to run on MacBook Pro 2019 with
> > Radeon Pro Vega 20 4 GB. Basically as soon as graphical user interface
> > starts, the whole system freezes. This happens with every Linux kernel
> > version I have tried over the last few months, including 5.13.
>
> If this is a regression, can you bisect?

I cannot find any working kernel version. There are some differences
between what happens after the failure, but it all seem to start with
ring gfx timeout.

Below is log with 5.6.6. Is there any point in trying even older
kernels than 5.6.6?

[ 209.276886] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR*
Waiting for fences timed out!
[ 214.193336] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx
timeout, signaled seq=392, emitted seq=394
[ 214.193372] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process
information: process Xorg pid 16356 thread Xorg:cs0 pid 16357
[ 214.193375] amdgpu 0000:03:00.0: GPU reset begin!
[ 214.355019] amdgpu 0000:03:00.0: GPU mode1 reset
[ 214.876624] [drm] psp mode1 reset succeed
[ 214.983413] amdgpu 0000:03:00.0: GPU reset succeeded, trying to resume
[ 214.983490] [drm] PCIE GART of 512M enabled (table at 0x000000F401AEB000).
[ 214.983685] [drm] PSP is resuming...
[ 215.170727] [drm] reserve 0x400000 from 0xf4fe800000 for PSP TMR
[ 215.322638] [drm] kiq ring mec 2 pipe 1 q 0
[ 215.558174] [drm] DM_MST: starting TM on aconnector: 000000008b23e629 [id: 64]
[ 216.043545] [drm] UVD and UVD ENC initialized successfully.
[ 216.143888] [drm] VCE initialized successfully.
[ 216.143891] amdgpu 0000:03:00.0: ring gfx uses VM inv eng 0 on hub 0
[ 216.143892] amdgpu 0000:03:00.0: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[ 216.143892] amdgpu 0000:03:00.0: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[ 216.143893] amdgpu 0000:03:00.0: ring comp_1.2.0 uses VM inv eng 5 on hub 0
[ 216.143893] amdgpu 0000:03:00.0: ring comp_1.3.0 uses VM inv eng 6 on hub 0
[ 216.143894] amdgpu 0000:03:00.0: ring comp_1.0.1 uses VM inv eng 7 on hub 0
[ 216.143894] amdgpu 0000:03:00.0: ring comp_1.1.1 uses VM inv eng 8 on hub 0
[ 216.143895] amdgpu 0000:03:00.0: ring comp_1.2.1 uses VM inv eng 9 on hub 0
[ 216.143895] amdgpu 0000:03:00.0: ring comp_1.3.1 uses VM inv eng 10 on hub 0
[ 216.143896] amdgpu 0000:03:00.0: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
[ 216.143896] amdgpu 0000:03:00.0: ring sdma0 uses VM inv eng 0 on hub 1
[ 216.143897] amdgpu 0000:03:00.0: ring sdma1 uses VM inv eng 1 on hub 1
[ 216.143897] amdgpu 0000:03:00.0: ring uvd_0 uses VM inv eng 4 on hub 1
[ 216.143898] amdgpu 0000:03:00.0: ring uvd_enc_0.0 uses VM inv eng 5 on hub 1
[ 216.143898] amdgpu 0000:03:00.0: ring uvd_enc_0.1 uses VM inv eng 6 on hub 1
[ 216.143899] amdgpu 0000:03:00.0: ring vce0 uses VM inv eng 7 on hub 1
[ 216.143899] amdgpu 0000:03:00.0: ring vce1 uses VM inv eng 8 on hub 1
[ 216.143900] amdgpu 0000:03:00.0: ring vce2 uses VM inv eng 9 on hub 1
[ 216.146937] [drm] recover vram bo from shadow start
[ 216.147238] [drm] recover vram bo from shadow done
[ 216.147239] [drm] Skip scheduling IBs!
[ 216.147239] [drm] Skip scheduling IBs!
[ 216.147245] [drm] Skip scheduling IBs!
[ 216.147247] [drm] Skip scheduling IBs!
[ 216.147248] [drm] Skip scheduling IBs!
[ 216.147249] [drm] Skip scheduling IBs!
[ 216.147250] [drm] Skip scheduling IBs!
[ 216.147291] [drm] Skip scheduling IBs!
[ 216.147293] [drm] Skip scheduling IBs!
[ 216.147299] [drm] Skip scheduling IBs!
[ 216.147300] amdgpu 0000:03:00.0: GPU reset(2) succeeded!
[ 216.147304] [drm] Skip scheduling IBs!
[ 216.147305] [drm] Skip scheduling IBs!
[ 216.147306] [drm] Skip scheduling IBs!
[ 216.147307] [drm] Skip scheduling IBs!
[ 216.147328] [drm] Skip scheduling IBs!
[ 216.147330] [drm] Skip scheduling IBs!
[ 216.147331] [drm] Skip scheduling IBs!
[ 216.147331] [drm] Skip scheduling IBs!
[ 216.147332] [drm] Skip scheduling IBs!
[ 216.147334] [drm] Skip scheduling IBs!
[ 216.147334] [drm] Skip scheduling IBs!
[ 216.147336] [drm] Skip scheduling IBs!
[ 216.147337] [drm] Skip scheduling IBs!
[ 216.147338] [drm] Skip scheduling IBs!
[ 216.147339] [drm] Skip scheduling IBs!
[ 216.147339] [drm] Skip scheduling IBs!
[ 216.147340] [drm] Skip scheduling IBs!
[ 216.147341] [drm] Skip scheduling IBs!
[ 216.147342] [drm] Skip scheduling IBs!
[ 216.147343] [drm] Skip scheduling IBs!
[ 216.147344] [drm] Skip scheduling IBs!
[ 216.147345] [drm] Skip scheduling IBs!
[ 216.147346] [drm] Skip scheduling IBs!
[ 216.147347] [drm] Skip scheduling IBs!
[ 216.147348] [drm] Skip scheduling IBs!
[ 216.147349] [drm] Skip scheduling IBs!
[ 216.147349] [drm] Skip scheduling IBs!
[ 216.147350] [drm] Skip scheduling IBs!
[ 216.147352] [drm] Skip scheduling IBs!
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

  reply	other threads:[~2021-07-13  7:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-12  9:56 Waiting for fences timed out on MacBook Pro 2019 Tomasz Moń
2021-07-12 18:35 ` Alex Deucher
2021-07-13  7:00   ` Tomasz Moń [this message]
2022-02-06  8:17 ` Tomasz Moń
2022-03-26 17:37   ` Tomasz Moń

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAOHtt38Eg0jn13DsX85Y3782dzxppwXbNH-KOrGfd8Pkvd51uw@mail.gmail.com \
    --to=desowin@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=alexdeucher@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.