From: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>
To: Jan Stancek <jstancek@redhat.com>
Cc: linuxppc-dev@lists.ozlabs.org, vdavydov@parallels.com,
benh@kernel.crashing.org, paulus@samba.org, mpe@ellerman.id.au,
anton@samba.org, nacc@linux.vnet.ibm.com,
gkurz@linux.vnet.ibm.com, grant.likely@linaro.org,
nikunj@linux.vnet.ibm.com, Steve Best <sbest@redhat.com>,
Gustavo Duarte <gduarte@redhat.com>,
Thomas Huth <thuth@redhat.com>
Subject: Re: [BUG] PowerNV crash with 4.4.0-rc8 at sched_init_numa (related to commit c118baf80256)
Date: Mon, 11 Jan 2016 18:41:48 +0530 [thread overview]
Message-ID: <5693AA14.8050203@linux.vnet.ibm.com> (raw)
In-Reply-To: <5693978F.2040507@linux.vnet.ibm.com>
On 01/11/2016 05:22 PM, Raghavendra K T wrote:
> On 01/10/2016 04:33 AM, Jan Stancek wrote:
>> Hi,
>>
>> I'm seeing bare metal ppc64le system crashing early during boot
>> with latest upstream kernel (4.4.0-rc8):
>>
>
> Jan,
> Do you mind sharing the .config you used for the kernel.
> Not able to reproduce with the one that I have :(
>
Never mind.. I enabled DEBUG_PER_CPU_MAPS.. to hit that..
/me goes back..
next prev parent reply other threads:[~2016-01-11 13:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1477405602.6296768.1452378871633.JavaMail.zimbra@redhat.com>
2016-01-09 23:03 ` [BUG] PowerNV crash with 4.4.0-rc8 at sched_init_numa (related to commit c118baf80256) Jan Stancek
2016-01-10 6:47 ` Raghavendra K T
2016-01-10 9:25 ` Jan Stancek
2016-01-11 11:52 ` Raghavendra K T
2016-01-11 13:11 ` Raghavendra K T [this message]
2016-01-15 13:43 ` Raghavendra K T
2016-01-15 14:18 ` Jan Stancek
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=5693AA14.8050203@linux.vnet.ibm.com \
--to=raghavendra.kt@linux.vnet.ibm.com \
--cc=anton@samba.org \
--cc=benh@kernel.crashing.org \
--cc=gduarte@redhat.com \
--cc=gkurz@linux.vnet.ibm.com \
--cc=grant.likely@linaro.org \
--cc=jstancek@redhat.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=nacc@linux.vnet.ibm.com \
--cc=nikunj@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--cc=sbest@redhat.com \
--cc=thuth@redhat.com \
--cc=vdavydov@parallels.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).