From: ynorov@caviumnetworks.com (Yury Norov)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM64: kernel panics in DABT in sys_msync path
Date: Mon, 25 Sep 2017 22:04:26 +0300 [thread overview]
Message-ID: <20170925190426.6prpcfn7lly26clm@yury-thinkpad> (raw)
In-Reply-To: <20170925140240.vl5mvbce5lb37dxe@yury-thinkpad>
On Mon, Sep 25, 2017 at 05:02:40PM +0300, Yury Norov wrote:
> Hi Will,
>
> > > The bug is reproducible for ilp32 and lp64 binaries. For kernel 4.12
> > > and for all kernels if '-smp 1' is passed to qemu, everything works
> > > fine. If no ideas, I think I'm able bisect it.
> >
> > I tried to reproduce this on hardware, but failed to do so. Our nightly
> > tests are also coming back fine for rwtest03. I just built Qemu v2.10.0
> > and that also passes the test with -smp 4 for me, so I'm a bit stuck.
>
> I also see the test passed sometimes. I run it in endless cycle and
> leave for a while. 5-10 iterations are usually enough.
>
> > Could you share:
> >
> > * Your kernel .config
> > * Your QEMU command line
> > * Details of your userspace
>
> Qemu configure command:
> ./configure --target-list=aarch64-softmmu --enable-fdt --enable-vhost-net --enable-kvm
>
> And run command:
> /home/yury/work/qemu-2.10.0/aarch64-softmmu/qemu-system-aarch64 \
> -machine virtualization=true -machine gic-version=3 \
> -machine virt -cpu cortex-a57 -nographic -smp 4 -m 1024 \
> -global virtio-blk-device.scsi=off -device virtio-scsi-device,id=scsi \
> -drive file=img/ubuntu-core-14.04.1-core-arm64.img,id=coreimg,cache=unsafe,if=none -device scsi-hd,drive=coreimg \
> -kernel /home/yury/work/linux/arch/arm64/boot/Image \
> --append "console=ttyAMA0 root=/dev/sda" \
> -initrd initrd.img-3.13.0-62-generic \
> $NETWORK \
> -redir tcp:2222::22 \
> -s \
> $@
>
> My userspace is Ubuntu 14. I build lp64 tests with default Ubuntu
> toolchain, and ilp32 tests with Linaro cross-toolchain.
>
> The config is attached, and the branch is vanilla 4.13 kernel, or this
> one:
> https://github.com/norov/linux/tree/ilp32-4.13
>
> Later today I will share the whole qemu environment I use.
https://drive.google.com/file/d/0B07VUB3kjLD8Mm5XN21qTTBfbnc/view
> Yury
next prev parent reply other threads:[~2017-09-25 19:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-24 21:36 ARM64: kernel panics in DABT in sys_msync path Yury Norov
2017-09-25 10:53 ` Will Deacon
2017-09-25 14:02 ` Yury Norov
2017-09-25 19:04 ` Yury Norov [this message]
2017-09-25 20:52 ` Ruigrok, Richard
[not found] ` <a3b714ae-97a5-8458-9bf7-140eeeebc4b9@codeaurora.org>
2017-09-26 10:23 ` Will Deacon
2017-09-26 11:54 ` Yury Norov
2017-09-26 14:23 ` Ruigrok, Richard
2017-09-26 17:31 ` Will Deacon
2017-09-27 15:50 ` Will Deacon
2017-09-27 18:00 ` Richard Ruigrok
2017-09-28 3:31 ` Richard Ruigrok
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=20170925190426.6prpcfn7lly26clm@yury-thinkpad \
--to=ynorov@caviumnetworks.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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