[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241226103216.GA29340@pc21.mareichelt.com>
Date: Thu, 26 Dec 2024 11:32:16 +0100
From: Markus Reichelt <lkt+2023@...eichelt.com>
To: stable@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: volkerdi@...ckware.com
Subject: Re: [PATCH 6.12 000/160] 6.12.7-rc1 review
* Greg Kroah-Hartman <gregkh@...uxfoundation.org> wrote:
> This is the start of the stable review cycle for the 6.12.7 release.
> There are 160 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 Fri, 27 Dec 2024 15:53:30 +0000.
> Anything received after that time might be too late.
Hi Greg
6.12.7-rc1 compiles, boots and runs here on x86_64
(AMD Ryzen 5 PRO 4650G, Slackware64-15.0)
Nitpicking: On Slackware64-current (Tue Dec 24 19:32:08 UTC 2024)
I notice the following info in dmesg on an AMD Ryzen 5 7520U lappy
with kernel-firmware-20240904_87cae27 popping up within some minutes
after booting, no negative system impact noticed; tho, once the event
is logged, it seems to show up more frequent even in idle usage.
Dec 26 11:09:22 karrde kernel: rtw_8821ce 0000:02:00.0: unhandled firmware c2h interrupt
Dec 26 11:10:11 karrde last message buffered 3 times
Dec 26 11:12:14 karrde last message buffered 12 times
Dec 26 11:21:19 karrde last message buffered 41 times
Bluetooth is enabled. This happens on both 6.12.7-rc1 and 6.12.6 (probably affects earlier 6.12.X kernels too), I can't bisect.
Pat, what about a more recent kernel-firmware package to test? :)
Tested-by: Markus Reichelt <lkt+2023@...eichelt.com>
Powered by blists - more mailing lists