From: Christian Heusel <christian@heusel.eu>
To: Luna Jernberg <droidbittin@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net,
rwarsow@gmx.de, conor@kernel.org, hargar@microsoft.com,
broonie@kernel.org,
Mario Limonciello <mario.limonciello@amd.com>,
Alex Deucher <alexander.deucher@amd.com>,
Ray Wu <ray.wu@amd.com>, Wayne Lin <Wayne.Lin@amd.com>
Subject: Re: [PATCH 6.14 000/197] 6.14.7-rc1 review
Date: Thu, 15 May 2025 14:40:21 +0200 [thread overview]
Message-ID: <f727a009-a896-4eb5-8b1c-03417d48e545@heusel.eu> (raw)
In-Reply-To: <CADo9pHgq2jzeVO4PFW6ObBj2bT9FSWcJUC5fRA9kVjMVah0J0g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2786 bytes --]
On 25/05/15 02:34PM, Luna Jernberg wrote:
> Same problem in rc2 just tested
Yes the fix is still on the way to mainline (see the mail from Mario
pointing to the patches posted to amd-gfx), but given that it's just
some log entries that stop again and nothing serious it should not be of
much issue.
Cheers,
Chris
> Den tis 13 maj 2025 kl 07:26 skrev Christian Heusel <christian@heusel.eu>:
> >
> > On 25/05/12 07:37PM, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 6.14.7 release.
> > > There are 197 patches in this series, all will be posted as a response
> > > to this one. If anyone has any issues with these being applied, please
> > > let me know.
> > >
> > > Responses should be made by Wed, 14 May 2025 17:19:58 +0000.
> > > Anything received after that time might be too late.
> >
> > Hello everyone,
> >
> > I have noticed that the following commit produces a whole bunch of lines
> > in my journal, which looks like an error for me:
> >
> > > Wayne Lin <Wayne.Lin@amd.com>
> > > drm/amd/display: Fix wrong handling for AUX_DEFER case
> >
> > amdgpu 0000:04:00.0: amdgpu: [drm] amdgpu: AUX reply command not ACK: 0x01.
> > amdgpu 0000:04:00.0: amdgpu: [drm] amdgpu: AUX partially written
> > amdgpu 0000:04:00.0: amdgpu: [drm] amdgpu: AUX reply command not ACK: 0x01.
> > amdgpu 0000:04:00.0: amdgpu: [drm] amdgpu: AUX partially written
> > amdgpu 0000:04:00.0: amdgpu: [drm] amdgpu: AUX reply command not ACK: 0x01.
> > amdgpu 0000:04:00.0: amdgpu: [drm] amdgpu: AUX partially written
> > amdgpu 0000:04:00.0: amdgpu: [drm] amdgpu: AUX reply command not ACK: 0x01.
> > amdgpu 0000:04:00.0: amdgpu: [drm] amdgpu: AUX partially written
> > amdgpu 0000:04:00.0: amdgpu: [drm] amdgpu: AUX reply command not ACK: 0x01.
> > amdgpu 0000:04:00.0: amdgpu: [drm] amdgpu: AUX partially written
> > amdgpu 0000:04:00.0: amdgpu: [drm] amdgpu: AUX reply command not ACK: 0x01.
> > amdgpu 0000:04:00.0: amdgpu: [drm] amdgpu: AUX partially written
> > amdgpu 0000:04:00.0: amdgpu: [drm] amdgpu: AUX reply command not ACK: 0x01.
> > amdgpu 0000:04:00.0: amdgpu: [drm] amdgpu: AUX partially written
> > amdgpu 0000:04:00.0: amdgpu: [drm] amdgpu: AUX reply command not ACK: 0x01.
> > amdgpu 0000:04:00.0: amdgpu: [drm] amdgpu: AUX partially written
> >
> > this does not seem to be serious, i.e. the system otherwise works as
> > intended but it's still noteworthy. Is there a dependency commit missing
> > maybe? From the code it looks like it was meant to be this way 🤔
> >
> > You can find a full journal here, with the logspammed parts in
> > highlight:
> > https://gist.github.com/christian-heusel/e8418bbdca097871489a31d79ed166d6#file-dmesg-log-L854-L981
> >
> > Cheers,
> > Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-05-15 12:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 17:37 Greg Kroah-Hartman
2025-05-12 19:30 ` Pavel Machek
2025-05-12 20:56 ` Jon Hunter
2025-05-13 0:26 ` Christian Heusel
2025-05-13 6:24 ` Luna Jernberg
2025-05-13 13:07 ` Mario Limonciello
2025-05-15 12:34 ` Luna Jernberg
2025-05-15 12:40 ` Christian Heusel [this message]
2025-05-13 9:41 ` Ron Economos
2025-05-13 9:45 ` Mark Brown
2025-05-13 10:40 ` Naresh Kamboju
2025-05-13 13:29 ` Naresh Kamboju
2025-05-14 9:53 ` Greg Kroah-Hartman
2025-05-13 11:38 ` Takeshi Ogasawara
2025-05-13 12:54 ` Florian Fainelli
2025-05-13 14:58 ` Markus Reichelt
2025-05-13 17:27 ` Peter Schneider
2025-05-13 17:30 ` Shuah Khan
2025-05-14 7:50 ` Christian Heusel
2025-05-14 11:49 ` Shung-Hsi Yu
2025-05-15 4:17 ` Pawan Gupta
2025-05-15 12:04 ` Shung-Hsi Yu
2025-05-14 16:45 ` Hardik Garg
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=f727a009-a896-4eb5-8b1c-03417d48e545@heusel.eu \
--to=christian@heusel.eu \
--cc=Wayne.Lin@amd.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.deucher@amd.com \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=droidbittin@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@microsoft.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=mario.limonciello@amd.com \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=ray.wu@amd.com \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®