Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: "Francisco Beltrán Millalén" <fbeltranmillalen@gmail.com>
To: qchcio@gmail.com
Cc: amd-gfx@lists.freedesktop.org, alexander.deucher@amd.com,
	christian.koenig@amd.com, dev@deq.rocks, me@freddy.us,
	stable@vger.kernel.org
Subject: Re: [PATCH v3 3/3] drm/amdgpu: reset VI ASIC on Apple boards with VRAM at 0
Date: Fri, 16 Oct 2026 21:09:04 -0300	[thread overview]
Message-ID: <20261017000904.8663-1-fbeltranmillalen@gmail.com> (raw)
In-Reply-To: <20261015181837.41690-4-qchcio@gmail.com>

Hi Maciej,

Thanks for the patch.

I applied patch 3 to the 6.18.49 kernel I use on my MacBookPro14,3
(Radeon Pro 555, 1002:67ef, subsystem 106b:017a, rev c7).  The kernel
also carries my unrelated PCI and ACPI patches for this machine.

After a cold boot, amdgpu logs "PCI CONFIG reset" and "GPU posting
now..." while it loads, and VRAM ends up at 0xF400000000.
MC_VM_FB_LOCATION reads 0xf47ff400 through debugfs.  In my tests in
September, a kernel without the reset left VRAM at 0 after a cold boot.

I then suspended to RAM three times with rtcwake.  After each resume
MC_VM_FB_LOCATION was still 0xf47ff400, the screen came back, and the
kernel log showed no VM faults, ring timeouts or GPU recovery.  After
the last one I ran glxgears for a minute and the gfx ring kept going.

I also closed the lid for about ten minutes.  After opening it the
screen came back, MC_VM_FB_LOCATION was 0xf47ff400, and glxgears ran
for a minute without errors.

Before that I had also tried it after a warm reboot, with four rtcwake
cycles and one 45-minute suspend from the idle timer.  After each of
those MC_VM_FB_LOCATION was 0xf47ff400 and the log showed no GPU
errors.

Finally, I reloaded amdgpu after a suspend, twice, with modprobe -r
and modprobe.  Each time amdgpu logged "PCI CONFIG reset" and "GPU
posting now..." during the reload, VRAM was at 0xF400000000 and
MC_VM_FB_LOCATION read 0xf47ff400.  VRAM is no longer at 0 by then, so
I think the reset came from the existing SMC check: with amdgpu
unloaded, SMC_SYSCON_CLOCK_CNTL_0 read 0x01000000 and SMC_PC_C was
about 0x205xx and changing (read through the MMIO BAR).  After the
second reload I logged in again and ran glxgears for a minute without
errors.

Tested-by: Francisco Beltrán Millalén <fbeltranmillalen@gmail.com> # MacBookPro14,3

Thanks again,
Francisco

  reply	other threads:[~2026-10-17  0:09 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
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 [this message]
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=20261017000904.8663-1-fbeltranmillalen@gmail.com \
    --to=fbeltranmillalen@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=dev@deq.rocks \
    --cc=me@freddy.us \
    --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