linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Nicholas Piggin <npiggin@gmail.com>
To: vrbagal1 <vrbagal1@linux.vnet.ibm.com>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	linux-fsdevel@vger.kernel.org,
	sachinp <sachinp@linux.vnet.ibm.com>
Subject: Re: [powerpc/powervm]Oops: Kernel access of bad area, sig: 11 [#1] while running stress-ng
Date: Tue, 10 Jul 2018 18:07:25 +1000	[thread overview]
Message-ID: <20180710180708.6e0cd26b@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <8595a4f915a7344210a8cc7ad6923a2b@linux.vnet.ibm.com>

On Tue, 10 Jul 2018 11:58:40 +0530
vrbagal1 <vrbagal1@linux.vnet.ibm.com> wrote:

> Hi,
> 
> Observing kernel oops on Power9(ZZ) box, running on PowerVM, while 
> running stress-ng.
> 
> 
> Kernel: 4.18.0-rc4
> Machine: Power9 ZZ (PowerVM)
> Test: Stress-ng
> 
> Attached is .config file
> 
> Traces:
> 
>   [12251.245209] Oops: Kernel access of bad area, sig: 11 [#1]

Can you post the lines above this? Otherwise we don't know what address
it tried to access (without decoding the instructions and reconstructing
it from registers at least, which the XFS devs wouldn't be inclined to
do).

And I assume there is nothing else relevant to XFS in the dmesg before
this?

Thanks,
Nick

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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-10  6:28 [powerpc/powervm]Oops: Kernel access of bad area, sig: 11 [#1] while running stress-ng vrbagal1
2018-07-10  8:07 ` Nicholas Piggin [this message]
2018-07-10 10:11   ` vrbagal1
2018-07-10 13:42     ` Michael Ellerman
2018-07-19  6:17       ` vrbagal1
2018-07-19 13:33         ` Brian Foster
2018-07-20  6:02           ` vrbagal1

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=20180710180708.6e0cd26b@roar.ozlabs.ibm.com \
    --to=npiggin@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --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).