linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Srikar Dronamraju <srikar@linux.ibm.com>
To: Erhard Furtner <erhard_f@mailbox.org>
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 14:19:13 +0530	[thread overview]
Message-ID: <aDV8iWe2nWX9JuvV@linux.ibm.com> (raw)
In-Reply-To: <20250526205537.2f1bccec@yea>

* Erhard Furtner <erhard_f@mailbox.org> [2025-05-26 20:55:37]:

Hi Erhard,

Thanks for reporting.

> 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?

> Modules linked in: md5 md5_ppc sha512_generic cmac cifs cifs_arc4 dns_resolver nls_ucs2_utils cifs_md4 zram af_packet cfg80211 rfkill evdev input_leds hid_generic usbhid hid radeon ctr xts cbc aes_generic libaes ofpart vmx_crypto powernv_flash gf128mul drm_suballoc_helper xhci_pci i2c_algo_bit mtd backlight drm_ttm_helper ttm drm_exec xhci_hcd ibmpowernv drm_display_helper opal_prd hwmon at24 regmap_i2c usbcore usb_common
> CPU: 12 UID: 250 PID: 44394 Comm: sh Tainted: G                T  6.14.8-gentoo-P9 #1
> Tainted: [T]=RANDSTRUCT
> Hardware name: T2P9D01 REV 1.01 POWER9 0x4e1202 opal:skiboot-bc106a0 PowerNV
> NIP:  c0000000000181c0 LR: c00000000001819c CTR: c00000000018fe50
> REGS: c00000008f603500 TRAP: 0700   Tainted: G                T   (6.14.8-gentoo-P9)
> MSR:  9000000002823032 <SF,HV,VEC,VSX,FP,ME,IR,DR,RI>  CR: 84042822  XER: 20040000
> CFAR: c000000000018110 IRQMASK: 3 
> GPR00: c000000000019fd0 c00000008f6037a0 c00000000115b100 9000000002803032 
> GPR04: c00000000bec0080 0000000000000000 c00000000213dec8 0000000004000000 
> GPR08: 0000000000002000 0000000000000001 0000000002002000 0000000000002000 
> GPR12: c00000000018ca30 c0000007ffff6800 0000000000000000 c00000003bd322c0 
> GPR16: 0000000000000003 00000000fff9cb3c 0000000001b42e30 0000000000000000 
> GPR20: 000000000072b0f0 0000000000000000 c000000002117c00 00000000007401c0 
> GPR24: c00000003bd32800 c00000000bec0e00 00000007fcabb000 c0000000020fd8b8 
> GPR28: c0000000010b0218 c00000003bd31a80 100000000080f032 c00000003bd31a80 
> NIP [c0000000000181c0] giveup_all+0x90/0x1d0
> LR [c00000000001819c] giveup_all+0x6c/0x1d0

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?

-- 
Thanks and Regards
Srikar Dronamraju


  reply	other threads:[~2025-05-27  8:49 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 [this message]
2025-05-27 18:47   ` Erhard Furtner
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=aDV8iWe2nWX9JuvV@linux.ibm.com \
    --to=srikar@linux.ibm.com \
    --cc=erhard_f@mailbox.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.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 NNTP newsgroup(s).