From: Guenter Roeck <linux@roeck-us.net>
To: Marc Zyngier <marc.zyngier@arm.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
"pi-cheng.chen" <pi-cheng.chen@linaro.org>,
Alexei Starovoitov <ast@plumgrid.com>
Subject: Re: linux-next: Tree for Aug 31 (new arm, arm64, s390 failures)
Date: Mon, 31 Aug 2015 08:47:07 -0700 [thread overview]
Message-ID: <55E476FB.2040208@roeck-us.net> (raw)
In-Reply-To: <20150831163103.2e13b301@arm.com>
Hi Marc,
On 08/31/2015 08:31 AM, Marc Zyngier wrote:
> On Mon, 31 Aug 2015 07:17:36 -0700
> Guenter Roeck <linux@roeck-us.net> wrote:
>
> Hi Guenter,
>
>> Qemu test results:
>> total: 85 pass: 74 fail: 11
>> Failed tests:
>> arm:vexpress-a9:arm_vexpress_defconfig:vexpress-v2p-ca9
>> arm:vexpress-a15:arm_vexpress_defconfig:vexpress-v2p-ca15-tc1
>> arm:vexpress-a9:multi_v7_defconfig:vexpress-v2p-ca9
>> arm:vexpress-a15:multi_v7_defconfig:vexpress-v2p-ca15-tc1
>> arm:realview-pb-a8:arm_realview_pb_defconfig
>> arm:realview-eb:arm_realview_eb_defconfig
>> mips:fuloong2e_defconfig
>> xtensa:dc232b:lx60:xtensa_defconfig
>> xtensa:dc232b:kc705:xtensa_defconfig
>> xtensa:dc233c:ml605:generic_kc705_defconfig
>> xtensa:dc233c:kc705:generic_kc705_defconfi
>>
>> Notable new failures (since next-20150828) are the s390 build failures,
>> the arm64 build failure, and the arm qemu test failures.
>>
>
> [...]
>
>> The qemu arm tests all fail silently, meaning there is no console
>> output. Bisect points to 'irqchip/GIC: Convert to EOImode == 1'.
>> Bisect log attached.
>
> Could you give me a qemu command-line I can use to track this down?
> Real HW seems happy enough, from what I can see...
>
That is what I was most concerned about :-(. Unfortunately, it
affects many of the most widely used arm qemu emulations, so it
would be very desirable to get this fixed, either in the kernel
or in qemu.
See https://github.com/groeck/linux-build-test, specifically
https://github.com/groeck/linux-build-test/tree/master/rootfs/arm/.
run-qemu-arm.sh includes the various command lines and configurations.
Note that some of the tests require a patched version of qemu.
The tests failing above should all work with the latest published
version of qemu (2.4), though.
Please let me know if there is anything I can do to help tracking
this down.
Thanks,
Guenter
next prev parent reply other threads:[~2015-08-31 15:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 9:54 linux-next: Tree for Aug 31 Stephen Rothwell
2015-08-31 14:17 ` linux-next: Tree for Aug 31 (new arm, arm64, s390 failures) Guenter Roeck
2015-08-31 15:09 ` Alexei Starovoitov
2015-08-31 15:31 ` Marc Zyngier
2015-08-31 15:31 ` Marc Zyngier
2015-08-31 15:47 ` Guenter Roeck [this message]
2015-08-31 16:18 ` Marc Zyngier
2015-08-31 16:18 ` Marc Zyngier
2015-08-31 16:40 ` Guenter Roeck
2015-08-31 17:09 ` Marc Zyngier
2015-08-31 17:09 ` Marc Zyngier
2015-08-31 18:26 ` Marc Zyngier
2015-08-31 18:26 ` Marc Zyngier
2015-08-31 18:57 ` Guenter Roeck
2015-08-31 19:13 ` Marc Zyngier
2015-08-31 19:13 ` Marc Zyngier
2015-08-31 19:40 ` Guenter Roeck
2015-08-31 20:07 ` Mark Brown
2015-08-31 18:33 ` Guenter Roeck
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=55E476FB.2040208@roeck-us.net \
--to=linux@roeck-us.net \
--cc=ast@plumgrid.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=pi-cheng.chen@linaro.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.