From: "Михаил Новоселов" <m.novosyolov@rosalinux.ru>
To: Matthew Wilcox <willy@infradead.org>
Cc: riel@surriel.com, mgorman@techsingularity.net,
peterz@infradead.org, mingo@kernel.org,
akpm@linux-foundation.org, stable@vger.kernel.org,
sashal@kernel.org, "Бетхер Александр" <a.betkher@rosalinux.ru>,
"i gaptrakhmanov" <i.gaptrakhmanov@rosalinux.ru>
Subject: Re: Serious regression on 6.1.x-stable caused by "bounds: support non-power-of-two CONFIG_NR_CPUS"
Date: Mon, 29 Apr 2024 07:07:39 +0300 (MSK) [thread overview]
Message-ID: <134159708.2271149.1714363659210.JavaMail.zimbra@rosalinux.ru> (raw)
In-Reply-To: <Zi8MXbT9Ajbv74wK@casper.infradead.org>
(Resending in plain text, sorry for accodently sending in HTML)
----- Исходное сообщение -----
> От: "Matthew Wilcox" <willy@infradead.org>
> Кому: "Михаил Новоселов" <m.novosyolov@rosalinux.ru>
> Копия: riel@surriel.com, mgorman@techsingularity.net, peterz@infradead.org, mingo@kernel.org, akpm@linux-foundation.org,
> stable@vger.kernel.org, sashal@kernel.org, "Бетхер Александр" <a.betkher@rosalinux.ru>, "i gaptrakhmanov"
> <i.gaptrakhmanov@rosalinux.ru>
> Отправленные: Понедельник, 29 Апрель 2024 г 5:56:29
> Тема: Re: Serious regression on 6.1.x-stable caused by "bounds: support non-power-of-two CONFIG_NR_CPUS"
> On Sun, Apr 28, 2024 at 05:58:08PM +0300, Mikhail Novosyolov wrote:
>> 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.
>
> Does v6.8.3 (which contains cf778fff03be) have this problem?
> How about current Linus master?
6.1.88 - has problem
6.6.27 - does not have problem
6.9-rc from commit efdfbbc4dcc8f98754056971f88af0f7ff906144 https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git - does not have problem
6.8.3 was not tested, but we can test it if needed.
>
> What kernel config were you using? I don't see that info on
> https://linux-hardware.org/?probe=9c92ac1222
> (maybe my tired eyes can't see it)
Kernel config for 6.1: https://abf.io/import/kernel-6.1/blob/bcb3e9611f/kernel-x86_64.config
For 6.6: https://abf.io/import/kernel-6.6/blob/7404a4d3d5/kernel-x86_64.config
6.9-rc was built with copypastied config from 6.6 (https://abf.io/build_lists/5028240)
next prev parent reply other threads:[~2024-04-29 4:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-28 14:58 Serious regression on 6.1.x-stable caused by "bounds: support non-power-of-two CONFIG_NR_CPUS" Mikhail Novosyolov
2024-04-29 2:56 ` Matthew Wilcox
2024-04-29 4:07 ` Михаил Новоселов [this message]
2024-04-29 12:17 ` Matthew Wilcox
2024-04-29 13:37 ` Ильфат Гаптрахманов
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=134159708.2271149.1714363659210.JavaMail.zimbra@rosalinux.ru \
--to=m.novosyolov@rosalinux.ru \
--cc=a.betkher@rosalinux.ru \
--cc=akpm@linux-foundation.org \
--cc=i.gaptrakhmanov@rosalinux.ru \
--cc=mgorman@techsingularity.net \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=riel@surriel.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=willy@infradead.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