From: Mikhail Novosyolov <m.novosyolov@rosalinux.ru>
To: regressions@lists.linux.dev, stable@vger.kernel.org
Cc: "Бетхер Александр" <a.betkher@rosalinux.ru>,
i.gaptrakhmanov@rosalinux.ru
Subject: [REGRESSION] Serious regression on 6.1.x-stable caused by "bounds: support non-power-of-two CONFIG_NR_CPUS"
Date: Mon, 29 Apr 2024 04:35:04 +0300 [thread overview]
Message-ID: <1e5355c9-7444-031d-59bc-52535f773755@rosalinux.ru> (raw)
Hello, colleagues.
Commit f2d5dcb48f7ba9e3ff249d58fc1fa963d374e66a "bounds: support non-power-of-two CONFIG_NR_CPUS" (https://github.com/torvalds/linux/commit/f2d5dcb48f7ba9e3ff249d58fc1fa963d374e66a) was backported to 6.1.x-stable (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=428ca0000f0abd5c99354c52a36becf2b815ca21), but causes a serious regression on quite a lot of hardware with AMD GPUs, kernel panics.
It was backported to 6.1.84, 6.1.84 has problems, 6.1.83 does not, the newest 6.1.88 still has this problem.
The problem is described here: https://gitlab.freedesktop.org/drm/amd/-/issues/3347
#regzbot introduced: 428ca0000f0abd5c99354c52a36becf2b815ca21
reply other threads:[~2024-04-29 1:35 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=1e5355c9-7444-031d-59bc-52535f773755@rosalinux.ru \
--to=m.novosyolov@rosalinux.ru \
--cc=a.betkher@rosalinux.ru \
--cc=i.gaptrakhmanov@rosalinux.ru \
--cc=regressions@lists.linux.dev \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).