From: Michael Ellerman <mpe@ellerman.id.au>
To: Sachin Sant <sachinp@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org, linux-next@vger.kernel.org
Subject: Re: [next-20190530] Boot failure on PowerPC
Date: Fri, 31 May 2019 23:52:21 +1000 [thread overview]
Message-ID: <87h89aohnu.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <79EEB945-661A-41AD-8B26-2FD3B3F84697@linux.vnet.ibm.com>
Sachin Sant <sachinp@linux.vnet.ibm.com> writes:
> Latest next fails to boot with a kernel panic on POWER9.
>
> [ 33.689332] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: write_irq_affinity.isra.5+0x15c/0x160
> [ 33.689346] CPU: 35 PID: 4907 Comm: irqbalance Not tainted 5.2.0-rc2-next-20190530-autotest-autotest #1
> [ 33.689352] Call Trace:
> [ 33.689356] [c0000018d974bab0] [c000000000b5328c] dump_stack+0xb0/0xf4 (unreliable)
> [ 33.689364] [c0000018d974baf0] [c000000000120694] panic+0x16c/0x408
> [ 33.689370] [c0000018d974bb80] [c00000000012010c] __stack_chk_fail+0x2c/0x30
> [ 33.689376] [c0000018d974bbe0] [c0000000001b859c] write_irq_affinity.isra.5+0x15c/0x160
> [ 33.689383] [c0000018d974bd30] [c0000000004d6f30] proc_reg_write+0x90/0x110
> [ 33.689388] [c0000018d974bd60] [c00000000041453c] __vfs_write+0x3c/0x70
> [ 33.689394] [c0000018d974bd80] [c000000000418650] vfs_write+0xd0/0x250
> [ 33.689399] [c0000018d974bdd0] [c000000000418a2c] ksys_write+0x7c/0x130
> [ 33.689405] [c0000018d974be20] [c00000000000b688] system_call+0x5c/0x70
>
> Machine boots till login prompt and then panics few seconds later.
>
> Last known next build was May 24th. Will attempt few builds till May 30 to
> narrow down this problem.
My CI was fine with next-20190529 (9a15d2e3fd03e3).
cheers
next prev parent reply other threads:[~2019-05-31 13:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 13:00 [next-20190530] Boot failure on PowerPC Sachin Sant
2019-05-31 13:52 ` Michael Ellerman [this message]
2019-05-31 18:13 ` Dexuan-Linux Cui
2019-06-03 3:11 ` Sachin Sant
2019-06-03 3:23 ` Lili Deng (Wicresoft North America Ltd)
2019-06-03 7:15 ` Lili Deng (Wicresoft North America Ltd)
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=87h89aohnu.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=linux-next@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).