From: "Timur Kristóf" <timur.kristof@gmail.com>
To: qchcio@gmail.com, amd-gfx@lists.freedesktop.org
Cc: amd-gfx@lists.freedesktop.org,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
stable@vger.kernel.org, "Brad Drury" <drury.brad@gmail.com>
Subject: Re: [PATCH v2 1/3] drm/amdgpu: reset SI ASIC on MacBookPros with VRAM at 0
Date: Sun, 25 Oct 2026 18:14:35 +0100 [thread overview]
Message-ID: <oVwVffbwQ9mrJnRml_R8-Q@gmail.com> (raw)
In-Reply-To: <20261022073638.724414-1-drury.brad@gmail.com>
On 2026. október 22., csütörtök 9:36:38 közép-európai téli idő Brad Drury
wrote:
> One thing I noticed: on 2 of the 4 resumes, about a second after
> resume, vce_v1_0_stop() logged:
>
> amdgpu 0000:01:00.0: VCE busy: VCE_STATUS=0x2, SRBM_STATUS2=0x80
>
> VCE encode worked straight afterwards, so it doesn't seem to break
> anything.
The following patch should fix that:
"drm/amdgpu/vce1: Fix checking whether VCE1 is idle"
https://lists.freedesktop.org/archives/amd-gfx/2026-October/154367.html
Best regards,
Timur
next prev parent reply other threads:[~2026-10-25 17:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BN9PR12MB514681E5EDA768CB4497EACFF79D2@BN9PR12MB5146.namprd12.prod.outlook.com>
[not found] ` <20261015095713.20560-1-qchcio@gmail.com>
2026-10-15 9:57 ` [PATCH v2 1/3] drm/amdgpu: reset SI ASIC on MacBookPros with VRAM at 0 Maciej Kucharek
2026-10-22 7:36 ` Brad Drury
2026-10-25 17:14 ` Timur Kristóf [this message]
2026-10-15 9:57 ` [PATCH v2 2/3] drm/amdgpu: reset CIK ASIC on Apple boards " Maciej Kucharek
2026-10-15 9:57 ` [PATCH v2 3/3] drm/amdgpu: reset VI " Maciej Kucharek
2026-10-15 13:26 ` Alex Deucher
[not found] ` <20261015181837.41690-1-qchcio@gmail.com>
2026-10-15 18:18 ` [PATCH v3 1/3] drm/amdgpu: reset SI ASIC on MacBookPros " Maciej Kucharek
2026-10-15 18:18 ` [PATCH v3 2/3] drm/amdgpu: reset CIK ASIC on Apple boards " Maciej Kucharek
2026-10-25 17:14 ` Timur Kristóf
2026-10-15 18:18 ` [PATCH v3 3/3] drm/amdgpu: reset VI " Maciej Kucharek
2026-10-17 0:09 ` Francisco Beltrán Millalén
2026-10-15 19:01 ` [PATCH v2 " Alex Deucher
2026-10-17 14:26 ` Sergey Armodin
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=oVwVffbwQ9mrJnRml_R8-Q@gmail.com \
--to=timur.kristof@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=drury.brad@gmail.com \
--cc=qchcio@gmail.com \
--cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox