All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christophe LEROY <christophe.leroy@c-s.fr>
To: Abdul Haleem <abdhalee@linux.vnet.ibm.com>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Cc: sachinp <sachinp@linux.vnet.ibm.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	npiggin <npiggin@gmail.com>,
	linux-next <linux-next@vger.kernel.org>,
	manvanth <manvanth@linux.vnet.ibm.com>
Subject: Re: [BUG][linux-next][ppc] kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: __schedule+0x978/0xa80
Date: Fri, 12 Oct 2018 10:08:39 +0200	[thread overview]
Message-ID: <eef38553-779a-c7f5-500f-145dbf4b6a49@c-s.fr> (raw)
In-Reply-To: <1539330499.17569.33.camel@abdul.in.ibm.com>



Le 12/10/2018 à 09:48, Abdul Haleem a écrit :
> On Fri, 2018-10-12 at 13:15 +0530, Abdul Haleem wrote:
>> Greeting's
>>
>> Today's linux-next fails to boot on powerpc bare-metal with this error
>>
>> POWER8 performance monitor hardware support registered
>> rcu: Hierarchical SRCU implementation.
>> smp: Bringing up secondary CPUs ...
>> Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: __schedule+0x978/0xa80
>> CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.19.0-rc7-next-20181010-autotest-autotest #1
>> Call Trace:
>> [c000001fed5b3bf0] [c000000000a0ef3c] dump_stack+0xb0/0xf4 (unreliable)
>> [c000001fed5b3c30] [c0000000000f9d68] panic+0x140/0x308
>> [c000001fed5b3cc0] [c0000000000f9844] __stack_chk_fail+0x24/0x30
>> [c000001fed5b3d20] [c000000000a2c3a8] __schedule+0x978/0xa80
>> [c000001fed5b3e00] [c000000000a2c9b4] schedule_idle+0x34/0x60
>> [c000001fed5b3e30] [c00000000013d344] do_idle+0x224/0x3d0
>> [c000001fed5b3ec0] [c00000000013d6e0] cpu_startup_entry+0x30/0x50
>> [c000001fed5b3ef0] [c000000000047f34] start_secondary+0x4d4/0x520
>> [c000001fed5b3f90] [c00000000000b370] start_secondary_prolog+0x10/0x14
>> Rebooting in 10 seconds..
>>
>> Machine: Power 8 bare-metal
>> kernel version: 4.19.0-rc7-next-20181010
>> gcc version: 4.8.5 20150623
>> config attach
> 
> Attaching the kernel config file
> 

# Linux/powerpc 4.11.0-rc4 Kernel Configuration

This is not the correct config file. Can you send the .config ?

Christophe

  reply	other threads:[~2018-10-12  8:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-12  7:45 [BUG][linux-next][ppc] kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: __schedule+0x978/0xa80 Abdul Haleem
2018-10-12  7:45 ` Abdul Haleem
2018-10-12  7:48 ` Abdul Haleem
2018-10-12  8:08   ` Christophe LEROY [this message]
2018-10-12  9:02     ` Aneesh Kumar K.V
2018-10-12  9:20       ` Christophe LEROY
2018-10-12 12:06       ` Christophe LEROY
2018-10-12 10:31     ` Abdul Haleem
2018-10-12 10:31       ` Abdul Haleem
2018-10-12 10:36       ` Christophe LEROY
2018-10-12 10:36         ` Christophe LEROY
2018-10-12 13:23         ` Abdul Haleem
2018-10-12 13:23           ` Abdul Haleem
2018-10-13  9:47           ` Christophe LEROY
2018-10-13  9:47             ` Christophe LEROY

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=eef38553-779a-c7f5-500f-145dbf4b6a49@c-s.fr \
    --to=christophe.leroy@c-s.fr \
    --cc=abdhalee@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=manvanth@linux.vnet.ibm.com \
    --cc=npiggin@gmail.com \
    --cc=sachinp@linux.vnet.ibm.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.