From: Sam Ravnborg <sam@ravnborg.org>
To: Nick Bowler <nbowler@draconx.ca>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
sparclinux@vger.kernel.org, Andreas Larsson <andreas@gaisler.com>,
Linux regressions mailing list <regressions@lists.linux.dev>
Subject: Re: PROBLEM: Only one CPU active on Ultra 60 since ~4.8 (regression)
Date: Sat, 30 Mar 2024 10:16:01 +0100 [thread overview]
Message-ID: <20240330091601.GA128565@ravnborg.org> (raw)
In-Reply-To: <a7c155ed-71fc-4ed9-a8c8-f98024b74651@draconx.ca>
On Fri, Mar 29, 2024 at 04:11:06PM -0400, Nick Bowler wrote:
> Hi Sam,
>
> On 2024-03-29 05:44, Sam Ravnborg wrote:
> > I took a look at this and may have a fix. Could you try the following
> > patch. It builds - but I have not tested it.
>
> With this patch applied on top of 6.9-rc1, both CPUs appear to come up:
>
> % cat /proc/cpuinfo
> [...]
> ncpus probed : 2
> ncpus active : 2
> [...]
> State:
> CPU0: online
> CPU2: online
Thanks, I will add a Tested-by: Nick Bowler <nbowler@draconx.ca>
and submit the patch properly along with a few other sparc64 related
fixes.
Sam
next prev parent reply other threads:[~2024-03-30 9:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADyTPEwt=ZNams+1bpMB1F9w_vUdPsGCt92DBQxxq_VtaLoTdw@mail.gmail.com>
2023-01-20 3:15 ` PROBLEM: Only one CPU active on Ultra 60 since ~4.8 (regression) Nick Bowler
2023-01-21 13:31 ` Linux kernel regression tracking (Thorsten Leemhuis)
2024-03-22 4:57 ` Nick Bowler
2024-03-28 19:36 ` Linux regression tracking (Thorsten Leemhuis)
2024-03-28 20:09 ` Linus Torvalds
2024-03-28 21:08 ` Nick Bowler
2024-03-29 9:44 ` Sam Ravnborg
2024-03-29 20:11 ` Nick Bowler
2024-03-30 9:16 ` Sam Ravnborg [this message]
2024-04-05 15:05 ` Andreas Larsson
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=20240330091601.GA128565@ravnborg.org \
--to=sam@ravnborg.org \
--cc=andreas@gaisler.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nbowler@draconx.ca \
--cc=regressions@lists.linux.dev \
--cc=sparclinux@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