From: Erhard Furtner <erhard_f@mailbox.org>
To: Srikar Dronamraju <srikar@linux.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: WARNING: CPU: 12 PID: 44394 at arch/powerpc/kernel/process.c:437 giveup_all+0x90/0x1d0 (v6.14.8, Talos II)
Date: Tue, 27 May 2025 20:47:28 +0200 [thread overview]
Message-ID: <20250527204728.63d538f8@yea> (raw)
In-Reply-To: <aDV8iWe2nWX9JuvV@linux.ibm.com>
On Tue, 27 May 2025 14:19:13 +0530
Srikar Dronamraju <srikar@linux.ibm.com> wrote:
> > Getting these from time to time when I run the machine for longer periods building:
> >
> > [...]
> > ------------[ cut here ]------------
> > WARNING: CPU: 12 PID: 44394 at arch/powerpc/kernel/process.c:437 giveup_all+0x90/0x1d0
>
> Its a warning with says that the task's userspace MSR register has
> VSX set but not the VEC or FP.
>
> Were you building the kernel or were you building something else.
> Can you paste the command you attempted?
I was doing an 'emerge -e @world' in Gentoo Linux and probably building a kernel in another shell. Noticed it only in the logs on the next day so I can't tell exactly which command triggered the issue.
But I will pay closer attention from now on.
> If this is happening with only the recent kernel and working with a previous
> kernel, do you happen to know the previous kernel version.
> In which case, is there a possibility of doing a git bisect?
I think I have not seen this in v6.13, certainly not in v6.12.
As I get this only from time to time bisecting will be hard. For that purpose I have yet to find a way to trigger it more reliably. But I'll take your hints and try!
Regards,
Erhard
next prev parent reply other threads:[~2025-05-27 18:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 18:55 WARNING: CPU: 12 PID: 44394 at arch/powerpc/kernel/process.c:437 giveup_all+0x90/0x1d0 (v6.14.8, Talos II) Erhard Furtner
2025-05-27 8:49 ` Srikar Dronamraju
2025-05-27 18:47 ` Erhard Furtner [this message]
2025-05-29 5:11 ` Srikar Dronamraju
2025-06-01 9:59 ` Erhard Furtner
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=20250527204728.63d538f8@yea \
--to=erhard_f@mailbox.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=srikar@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).