Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1647679 > unrolled thread

Re: [PowerPC][next-20170324][kselftest] kernel Oops when running tm/tm-signal-context-chk-vsx

Started byAbdul Haleem <abdhalee@linux.vnet.ibm.com>
First post2017-05-23 08:40 +0200
Last post2017-05-25 13:50 +0200
Articles 4 — 3 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PowerPC][next-20170324][kselftest] kernel Oops when running  tm/tm-signal-context-chk-vsx Abdul Haleem <abdhalee@linux.vnet.ibm.com> - 2017-05-23 08:40 +0200
    Re: [PowerPC][next-20170324][kselftest] kernel Oops when running tm/tm-signal-context-chk-vsx Michael Ellerman <mpe@ellerman.id.au> - 2017-05-24 14:00 +0200
      Re: [PowerPC][next-20170324][kselftest] kernel Oops when running  tm/tm-signal-context-chk-vsx Abdul Haleem <abdhalee@linux.vnet.ibm.com> - 2017-05-25 13:00 +0200
        Re: [PowerPC][next-20170324][kselftest] kernel Oops when running tm/tm-signal-context-chk-vsx Denis Kirjanov <kda@linux-powerpc.org> - 2017-05-25 13:50 +0200

#1647679 — Re: [PowerPC][next-20170324][kselftest] kernel Oops when running tm/tm-signal-context-chk-vsx

FromAbdul Haleem <abdhalee@linux.vnet.ibm.com>
Date2017-05-23 08:40 +0200
SubjectRe: [PowerPC][next-20170324][kselftest] kernel Oops when running tm/tm-signal-context-chk-vsx
Message-ID<tKbE6-7Qs-19@gated-at.bofh.it>
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

[toc] | [next] | [standalone]


#1649525 — Re: [PowerPC][next-20170324][kselftest] kernel Oops when running tm/tm-signal-context-chk-vsx

FromMichael Ellerman <mpe@ellerman.id.au>
Date2017-05-24 14:00 +0200
SubjectRe: [PowerPC][next-20170324][kselftest] kernel Oops when running tm/tm-signal-context-chk-vsx
Message-ID<tKD7j-1Uh-3@gated-at.bofh.it>
In reply to#1647679
Abdul Haleem <abdhalee@linux.vnet.ibm.com> writes:
> Hi Cyril,
>
> I see a similar trace, but with 'tm-signal-stack' test for mainline
> kernel 4.12.0-rc1 on PowerVM LPAR.

I can't reproduce this here.

Can you please retest on rc2.

Also please include the exact version of the test (it prints it), and
what toolchain you built it with.

cheers

[toc] | [prev] | [next] | [standalone]


#1650367

FromAbdul Haleem <abdhalee@linux.vnet.ibm.com>
Date2017-05-25 13:00 +0200
Message-ID<tKYEO-77g-5@gated-at.bofh.it>
In reply to#1649525
On Wed, 2017-05-24 at 21:50 +1000, Michael Ellerman wrote:
> Abdul Haleem <abdhalee@linux.vnet.ibm.com> writes:
> > Hi Cyril,
> >
> > I see a similar trace, but with 'tm-signal-stack' test for mainline
> > kernel 4.12.0-rc1 on PowerVM LPAR.
> 
> I can't reproduce this here.
It is not reproducible all the times.
> 
> Can you please retest on rc2.

With rc2, I see a similar call trace for the test
'tm_signal_context_chk_fpu'

I tried running tm-signal-stack alone, but no luck.
> 
> Also please include the exact version of the test (it prints it), and
> what toolchain you built it with.

test: tm_signal_context_chk_fpu
tags: git_version:v4.12-rc2-62-g2426125
success: tm_signal_context_chk_fpu

toolchain : gcc version 5.2.1


latest trace:
[ 1953.024563] Bad kernel stack pointer 7fffe0a1ddc0 at c00000000000b660
[ 1953.024582] Oops: Bad kernel stack pointer, sig: 6 [#1]
[ 1953.024585] SMP NR_CPUS=2048 
[ 1953.024585] NUMA 
[ 1953.024587] pSeries
[ 1953.024590] Modules linked in: rtc_generic vmx_crypto pseries_rng
autofs4
[ 1953.024597] CPU: 14 PID: 27145 Comm: tm-signal-conte Not tainted
4.12.0-rc2-00062-g2426125-dirty #1
[ 1953.024601] task: c0000007699f8600 task.stack: c00000076a24c000
[ 1953.024603] NIP: c00000000000b660 LR: 0000000010001aac CTR:
0000000000000000
[ 1953.024608] REGS: c00000000ebdbd40 TRAP: 0700   Not tainted
(4.12.0-rc2-00062-g2426125-dirty)
[ 1953.024610] MSR: 8000000102a03031 <SF,VEC,VSX,FP,ME,IR,DR,LE,TM[E]>
[ 1953.024615]   CR: 42000822  XER: 00000000
[ 1953.024618] CFAR: c00000000000b5b4 SOFTE: 0 
               GPR00: 0000000000000025 00007fffe0a1ddc0 0000000010028200
0000000000000000 
               GPR04: 000000000000000a 0000000000000000 0000000000000000
0000000000000000 
               GPR08: 00000000000000f8 0000000000000000 0000000000000000
0000000000000000 
               GPR12: 0000000000000000 00007fff8878c440 ffffffffffffffff
fffffffffffffffe 
               GPR16: fffffffffffffffd fffffffffffffffc fffffffffffffffb
fffffffffffffffa 
               GPR20: fffffffffffffff9 fffffffffffffff8 fffffffffffffff7
fffffffffffffff6 
               GPR24: fffffffffffffff5 fffffffffffffff4 fffffffffffffff3
fffffffffffffff2 
               GPR28: fffffffffffffff1 fffffffffffffff0 ffffffffffffffef
ffffffffffffffee 
[ 1953.024652] NIP [c00000000000b660] fast_exception_return+0x90/0x98
[ 1953.024655] LR [0000000010001aac] 0x10001aac
[ 1953.024657] Call Trace:
[ 1953.024658] Instruction dump:
[ 1953.024661] 7c40e3a6 e9a100d8 7c7b03a6 e84101a0 7c4ff120 e8410170
7c5a03a6 e8010070 
[ 1953.024666] e8410080 e8610088 e8810090 e8210078 <4c000024> 48000000
e8610178 88ed02bb 
[ 1953.024671] ---[ end trace 3e1eeb3cfb1260c1 ]---

> 
> cheers
> 


-- 
Regard's

Abdul Haleem
IBM Linux Technology Centre

[toc] | [prev] | [next] | [standalone]


#1650426 — Re: [PowerPC][next-20170324][kselftest] kernel Oops when running tm/tm-signal-context-chk-vsx

FromDenis Kirjanov <kda@linux-powerpc.org>
Date2017-05-25 13:50 +0200
SubjectRe: [PowerPC][next-20170324][kselftest] kernel Oops when running tm/tm-signal-context-chk-vsx
Message-ID<tKZrd-7Fs-45@gated-at.bofh.it>
In reply to#1650367
[  283.516559] Kernel BUG at c00000000191c160 [verbose debug info unavailable]
[  283.516573] Unexpected TM Bad Thing exception at c00000000191c160
(msr 0x2a03030)
cpu 0x19: Vector: 700 (Program Check) at [c0000007d1a37920]
    pc: c00000000191c160: fast_exception_return+0xac/0xb4
    lr: c000000001925ed4: .arch_local_irq_restore.part.10+0x74/0xa0
    sp: c0000007d1a37ba0
   msr: 9000000302a03030
  current = 0xc0000007d094c000
  paca    = 0xc00000000fffd980	 softe: 0	 irq_happened: 0x01
    pid   = 7804, comm = tm-signal-conte
Linux version 4.12.0-rc2 (root@power.oil.ru) (gcc version 4.8.3
20140911 (Red Hat 4.8.3-9) (GCC) ) #31 SMP PREEMPT Thu May 25 07:22:54
EDT 2017
WARNING: exception is not recoverable, can't continue
enter ? for help
[link register   ] c000000001925ed4 .arch_local_irq_restore.part.10+0x74/0xa0
[c0000007d1a37ba0] c000000001925ea0
.arch_local_irq_restore.part.10+0x40/0xa0 (unreliable)
[c0000007d1a37c10] c000000001a565f0 .lock_acquire+0x100/0x340
[c0000007d1a37cf0] c000000001b8fb44 .__might_fault+0x74/0xb0
[c0000007d1a37d60] c00000000193cd60 .sys_rt_sigreturn+0x9e0/0xb70
[c0000007d1a37e30] c00000000191b9ec system_call+0x38/0xfc
--- Exception: c01 (System Call) at 0000000010001c38
SP (7fffddb2dd60) is in userspace

>
>
>
>

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web