public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Markus Reichelt <lkt+2023@mareichelt.com>
To: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: volkerdi@slackware.com
Subject: Re: [PATCH 6.12 000/160] 6.12.7-rc1 review
Date: Thu, 26 Dec 2024 11:32:16 +0100	[thread overview]
Message-ID: <20241226103216.GA29340@pc21.mareichelt.com> (raw)
In-Reply-To: <20241223155408.598780301@linuxfoundation.org>

* Greg Kroah-Hartman <gregkh@linuxfoundation.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@mareichelt.com>

  parent reply	other threads:[~2024-12-26 10:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-23 15:56 [PATCH 6.12 000/160] 6.12.7-rc1 review Greg Kroah-Hartman
2024-12-23 21:16 ` SeongJae Park
2024-12-23 22:39 ` Shuah Khan
2024-12-23 23:23 ` Takeshi Ogasawara
2024-12-24  8:42 ` Harshit Mogalapalli
2024-12-24 10:16 ` Ron Economos
2024-12-24 12:18 ` Peter Schneider
2024-12-24 12:25 ` Luna Jernberg
2024-12-24 13:26 ` Jon Hunter
2024-12-24 19:12 ` Naresh Kamboju
2024-12-26 13:41   ` Marc Zyngier
2024-12-27 13:04     ` Greg Kroah-Hartman
2024-12-27 13:23       ` Marc Zyngier
2024-12-27 13:34         ` Greg Kroah-Hartman
2024-12-27 13:43           ` Marc Zyngier
2024-12-27 13:49             ` Greg Kroah-Hartman
2024-12-27 17:27         ` Guenter Roeck
2024-12-24 21:36 ` Justin Forbes
2024-12-26 10:08 ` Muhammad Usama Anjum
2024-12-26 10:32 ` Markus Reichelt [this message]
2024-12-26 17:17 ` Florian Fainelli
2024-12-26 19:35 ` [PATCH 6.12] " Hardik Garg
2024-12-26 20:21 ` [PATCH 6.12 000/160] " Pavel Machek

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=20241226103216.GA29340@pc21.mareichelt.com \
    --to=lkt+2023@mareichelt.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=volkerdi@slackware.com \
    /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