From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux kernel regressions list <regressions@lists.linux.dev>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Quick extra post-rc7 regression report due to the nearing 6.9 release
Date: Thu, 9 May 2024 19:27:41 +0200 [thread overview]
Message-ID: <4c7be436-8a5d-469f-b88e-bfe17bafb991@leemhuis.info> (raw)
Hi Linus, here is a short extra regression report for you mentioning
regressions that you might want to be aware of or could still be fixed,
but afaics are unlikely to get fixed:
* 1cb63d80fff6c4 ("Bluetooth: btusb: Add support Mediatek MT7920") on
some devices leads to firmware loading problems with older firmware
files[1]; the fix is in next for two weeks now[2], but the maintainer
missed that this is regression fix[3]:
[1] https://lore.kernel.org/lkml/20240401144424.1714-1-mike@fireburn.co.uk/
[2] 5e970bdf73e619 ("Bluetooth: btusb: Fix the patch for MT7920 the affected to MT7921")
[3] https://lore.kernel.org/lkml/CABBYNZK1QWNHpmXUyne1Vmqqvy7csmivL7q7N2Mu=2fmrUV4jg@mail.gmail.com/
* Gaha Bana reported that a AMD Ryzen 7840HS CPU stopped using the boost
frequencies; a fix is ready, but Rafael afaics only queued for 6.10[1]:
[1] https://lore.kernel.org/lkml/CAJZ5v0iqEj0bx72Rqn--srv8Y+ievjZx6W8_kJksPzPVTLLqxQ@mail.gmail.com/
* Some change caused boot lockups for Ben Greear[1]; a workaround is now
in next[2], but only queued for the next merge window:
[1] https://lore.kernel.org/lkml/30f757e3-73c5-5473-c1f8-328bab98fd7d@candelatech.com/
[2] https://lore.kernel.org/linux-wireless/20240430234212.2132958-1-greearb@candelatech.com/
[3] https://lore.kernel.org/linux-wireless/20240508120726.85A10C113CC@smtp.kernel.org/
* Lyude ran into a boot lockup on a AMD machine caused by the topology
changes from Thomas they are still trying to track down[1]; but this is
the only such report I'm aware of, so hopefully something pretty rare:
[1] https://lore.kernel.org/lkml/3d77cb89857ee43a9c31249f4eab7196013bc4b4.camel@redhat.com/
* Dan Moulding reported a nouveau regression three days ago, but no
reply from the developers yet:
[1] https://lore.kernel.org/stable/20240506182331.8076-1-dan@danm.net/
There are a few more regression, but those IMHO were not worth mentioning.
Ciao, Thorsten
reply other threads:[~2024-05-09 17:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4c7be436-8a5d-469f-b88e-bfe17bafb991@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).