From: Abdul Haleem <abdhalee@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Cyril Bur <cyrilbur@gmail.com>
Subject: Re: [PowerPC][next-20170324][kselftest] kernel Oops when running tm/tm-signal-context-chk-vsx
Date: Mon, 03 Apr 2017 14:33:51 +0530 [thread overview]
Message-ID: <1491210231.7788.12.camel@abdul.in.ibm.com> (raw)
In-Reply-To: <1491209923.7788.9.camel@abdul.in.ibm.com>
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>
--
Regard's
Abdul Haleem
IBM Linux Technology Centre
next prev parent reply other threads:[~2017-04-03 9:04 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 [this message]
2017-05-23 6:33 ` Abdul Haleem
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=1491210231.7788.12.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=mpe@ellerman.id.au \
--cc=sfr@canb.auug.org.au \
/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).