From: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
To: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Madhavan Srinivasan <maddy@linux.ibm.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [mainline] powerpc/TM: Unexpected TM Bad Thing during core dump on POWER9 (7.1‑rc1)
Date: Tue, 28 Apr 2026 17:48:50 +0530 [thread overview]
Message-ID: <364996ce-aba2-4213-8d20-7dd481b43fe6@linux.ibm.com> (raw)
Greetings!!
IBM CI has reported a kernel crash while running
selftests/powerpc/signal on a POWER9 pSeries system.
I attempted to reproduce this issue manually, but was not successful so far.
Below are the details of the crash as reported by CI.
Crash Details:
[ 9798.880148] Unexpected TM Bad Thing exception at c00000000000dbac
(msr 0x8000000302a03031) tm_scratch=800000010280b033
[ 9798.880160] Oops: Unrecoverable exception, sig: 6 [#1]
[ 9798.880165] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=8192 NUMA pSeries
[ 9798.880173] Modules linked in: nvram(E) rpadlpar_io(E) rpaphp(E) ...
[ 9798.880233] CPU: 8 UID: 0 PID: 1039530 Comm: sigfuz
Tainted: G E 7.1.0-rc1 #1 PREEMPT
[ 9798.880245] Hardware name: IBM,8375-42A POWER9 (architected)
hv:phyp pSeries
[ 9798.880251] NIP: c00000000000dbac LR: 0000000010001e58
[ 9798.880262] MSR: 8000000302a03031 <SF,VEC,VSX,FP,ME,IR,DR,LE,TM[SE]>
Call Trace:
NIP [c00000000000dbac] interrupt_return_srr_kernel+0x15c/0x18c
Call Trace:
tm_reclaim_thread
flush_tmregs_to_thread
vsr_get
regset_get_alloc
fill_thread_core_info.isra.0
fill_note_info
elf_core_dump
coredump_write
do_coredump
vfs_coredump
get_signal
do_signal
do_notify_resume
interrupt_exit_user_prepare_main
interrupt_exit_user_prepare
interrupt_return_srr_user
Please let me know if further details are required.
If you happen to fix this issue, please add below tag.
Reported-by: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
Regards,
Venkat.
reply other threads:[~2026-04-28 12:19 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=364996ce-aba2-4213-8d20-7dd481b43fe6@linux.ibm.com \
--to=venkat88@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@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