From: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
To: Venkat Rao B <vrbagal1@linux.vnet.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Cc: sachinp <sachinp@linux.vnet.ibm.com>,
Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [powerpc/powervmc]kernel BUG at arch/powerpc/mm/pgtable-book3s64.c:414!
Date: Mon, 18 Jun 2018 08:45:55 +0530 [thread overview]
Message-ID: <384d55cf-f2e0-f1be-fb17-587d2f189da7@linux.ibm.com> (raw)
In-Reply-To: <4d3ad051-2423-3570-7ef6-90f47a83f157@linux.vnet.ibm.com>
On 06/17/2018 01:22 PM, Venkat Rao B wrote:
>
>
> On Friday 15 June 2018 07:14 PM, Michael Ellerman wrote:
>> vrbagal1 <vrbagal1@linux.vnet.ibm.com> writes:
>>
>>> Hi,
>>>
>>> Observing kernel bug followed by kernel oops and system reboots, while
>>> running kselftest on Power8 LPAR.
>>>
>>> Machine Details: Power8 LPAR
>>> Git Tree:
>>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>>> Commit ID: f5b7769eb0400ec5217a47e41148a9f816ca1f9f
>>> Kernel version: 4.17.0-autotest
>>> GCC version: (gcc version 6.3.1 20161221 (Red Hat 6.3.1-1) (GCC))
>>>
>>
>> This is fixed by your patch Aneesh?
>>
>> http://patchwork.ozlabs.org/patch/929325/
>
> Yes, this patch fixes the issue.
>
I missed adding Reported-by:Venkat Rao B <vrbagal1@linux.vnet.ibm.com>
and Tested-by:Venkat Rao B <vrbagal1@linux.vnet.ibm.com>
Michael,
Can you add that when applying the patch?
-aneesh
prev parent reply other threads:[~2018-06-18 3:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 6:24 [powerpc/powervmc]kernel BUG at arch/powerpc/mm/pgtable-book3s64.c:414! vrbagal1
2018-06-15 13:44 ` Michael Ellerman
2018-06-17 7:52 ` Venkat Rao B
2018-06-18 3:15 ` Aneesh Kumar K.V [this message]
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=384d55cf-f2e0-f1be-fb17-587d2f189da7@linux.ibm.com \
--to=aneesh.kumar@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=sachinp@linux.vnet.ibm.com \
--cc=vrbagal1@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).