linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Zyngier <marc.zyngier@arm.com>
To: Guenter Roeck <linux@roeck-us.net>
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 16:31:03 +0100	[thread overview]
Message-ID: <20150831163103.2e13b301@arm.com> (raw)
In-Reply-To: <20150831141736.GA19616@roeck-us.net>

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...

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny.

  parent reply	other threads:[~2015-08-31 15:31 UTC|newest]

Thread overview: 14+ 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 [this message]
2015-08-31 15:47     ` Guenter Roeck
2015-08-31 16:18       ` Marc Zyngier
2015-08-31 16:40         ` Guenter Roeck
2015-08-31 17:09           ` 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: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=20150831163103.2e13b301@arm.com \
    --to=marc.zyngier@arm.com \
    --cc=ast@plumgrid.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --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 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).