From: Guenter Roeck <linux@roeck-us.net>
To: John David Anglin <dave.anglin@bell.net>
Cc: jejb@parisc-linux.org, Helge Deller <deller@gmx.de>,
linux-parisc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] parisc: Remove PTE load and fault check from L2_ptep macro
Date: Wed, 26 Sep 2018 06:29:55 -0700 [thread overview]
Message-ID: <4ac3d6fe-ef61-546d-e9fa-c8189edd288a@roeck-us.net> (raw)
In-Reply-To: <dcb9250d-f811-90be-2c5a-4d15cb29b474@bell.net>
On 09/26/2018 05:09 AM, John David Anglin wrote:
> Hi,
>
> On 2018-09-25 11:21 PM, Guenter Roeck wrote:
>> This patch causes my parisc qemu tests to fail.
>> Unfortunately I don't have any useful log output; the failure
>> is silent. Reverting the patch fixes the problem.
> Can you be more specific on how to run these tests?
>
> Dave
>
Sorry. Please see
https://github.com/groeck/linux-build-test/tree/master/rootfs/parisc
My tests enable a number of device and debug options on top of defconfig.
Those are not necessary, though. The problem can be reproduced with defconfig.
With the initrd available from there, and with an image built using 'defconfig',
run
qemu-system-hppa \
-kernel vmlinux -no-reboot \
-initrd rootfs.cpio.gz \
-append 'rdinit=/sbin/init console=ttyS0,115200' \
-nographic -monitor null
I tested with qemu 2.12 and 3.0. Using "arch/parisc/boot/bzImage" as kernel
image does not make a difference.
Note: The initrd auto-reboots. To avoid that, add "noreboot" as additional
command line option.
Hope this helps,
Guenter
prev parent reply other threads:[~2018-09-26 13:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 3:21 [PATCH] parisc: Remove PTE load and fault check from L2_ptep macro Guenter Roeck
2018-09-26 12:09 ` John David Anglin
2018-09-26 13:29 ` Guenter Roeck [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=4ac3d6fe-ef61-546d-e9fa-c8189edd288a@roeck-us.net \
--to=linux@roeck-us.net \
--cc=dave.anglin@bell.net \
--cc=deller@gmx.de \
--cc=jejb@parisc-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.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