From: Abdul Haleem <abdhalee@linux.vnet.ibm.com>
To: Cyril Bur <cyrilbur@gmail.com>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
sachinp <sachinp@linux.vnet.ibm.com>
Subject: Re: [PowerPC][next-20170324][kselftest] kernel Oops when running tm/tm-signal-context-chk-vsx
Date: Tue, 23 May 2017 12:03:19 +0530 [thread overview]
Message-ID: <1495521199.9020.13.camel@abdul.in.ibm.com> (raw)
In-Reply-To: <1491210231.7788.12.camel@abdul.in.ibm.com>
On Mon, 2017-04-03 at 14:33 +0530, Abdul Haleem wrote:
> On Mon, 2017-04-03 at 14:28 +0530, Abdul Haleem wrote:
> > On Tue, 2017-03-28 at 21:00 +1100, Michael Ellerman wrote:
> > > Abdul Haleem <abdhalee@linux.vnet.ibm.com> writes:
> > >
> > > > Hi,
> > > >
> > > > While running kernel self tests on ppc64, tm/tm-signal-context-chk-vsx
> > > > tests fails with Oops message.
> > > >
> > > > I was able to reproduce only twice out of 20 runs on next-20170324 only.
> > > > so it is difficult to bisect the commit causing the issue.
> > >
> > > Can you try mainline as of this commit:
> > >
> > > 605df8d674ac ("selftests/powerpc: Replace stxvx and lxvx with stxvd2x/lxvd2x")
> > >
> > > https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=605df8d674ac65e044a0bf4998b28c2f350b7f9e
> > >
> > > cheers
> > >
> >
> >
> > Trace is not reproducible on mainline with above commit.
> >
> > Cyril was able to reproduce it and is working on it.
> >
> >
> >
> >
> cc Cyril Bur <cyrilbur@gmail.com>
>
Hi Cyril,
I see a similar trace, but with 'tm-signal-stack' test for mainline
kernel 4.12.0-rc1 on PowerVM LPAR.
tm-signal-msr-r[7669]: bad frame in rt_sigreturn: 00007fffe8a6a6c0 nip
00007fff8335f094 lr 00007fff835104d8
tm-signal-stack[7675]: bad frame in setup_rt_frame: 0000000000000000 nip
0000000010000d44 lr 0000000010000d28
Bad kernel stack pointer 7fffd8b33530 at c00000000000b660
Oops: Bad kernel stack pointer, sig: 6 [#1]
SMP NR_CPUS=2048
NUMA
pSeries
Dumping ftrace buffer:
(ftrace buffer empty)
Modules linked in: vmx_crypto(E) pseries_rng(E) rtc_generic(E)
autofs4(E) [last unloaded: torture]
CPU: 8 PID: 8014 Comm: tm-signal-conte Tainted: G E
4.12.0-rc1-autotest #1
task: c0000007742ac000 task.stack: c000000773b84000
NIP: c00000000000b660 LR: 0000000010001af0 CTR: 0000000000000000
REGS: c00000000ec23d40 TRAP: 0700 Tainted: G E
(4.12.0-rc1-autotest)
MSR: 8000000102a03031 <SF,VEC,VSX,FP,ME,IR,DR,LE,TM[E]>
CR: 42000822 XER: 00000000
CFAR: c00000000000b5b4 SOFTE: 0
GPR00: 0000000000000025 00007fffd8b33530 0000000010028200
0000000000000000
GPR04: 000000000000000a 0000000010020010 0000000000000000
0000000000000000
GPR08: 00000000000000f8 0000000000000000 0000000000000000
0000000000000000
GPR12: 0000000000000000 00007fff8b6ac440 0000000000000000
0000000000000000
GPR16: 0000000000000000 0000000000000000 0000000000000000
0000000000000000
GPR20: 0000000000000000 0000000000000000 0000000000000000
0000000000000000
GPR24: 0000000000000000 0000000000000000 0000000000000000
00007fff8b69f948
GPR28: 0000000010020010 0000000010020304 0000000000001f4e
00000000000333ce
NIP [c00000000000b660] fast_exception_return+0x90/0x98
LR [0000000010001af0] 0x10001af0
Call Trace:
Instruction dump:
7c40e3a6 e9a100d8 7c7b03a6 e84101a0 7c4ff120 e8410170 7c5a03a6 e8010070
e8410080 e8610088 e8810090 e8210078 <4c000024> 48000000 e8610178
88ed02bb
---[ end trace a10b71ed348d921f ]---
--
Regard's
Abdul Haleem
IBM Linux Technology Centre
next prev parent reply other threads:[~2017-05-23 6:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 11:02 [PowerPC][next-20170324][kselftest] kernel Oops when running tm/tm-signal-context-chk-vsx Abdul Haleem
2017-03-28 10:00 ` Michael Ellerman
2017-04-03 8:58 ` Abdul Haleem
2017-04-03 9:03 ` Abdul Haleem
2017-05-23 6:33 ` Abdul Haleem [this message]
2017-05-24 11:50 ` Michael Ellerman
2017-05-25 10:53 ` Abdul Haleem
2017-05-25 11:47 ` Denis Kirjanov
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=1495521199.9020.13.camel@abdul.in.ibm.com \
--to=abdhalee@linux.vnet.ibm.com \
--cc=cyrilbur@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sachinp@linux.vnet.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).