From: Kevin Hilman <khilman@linaro.org>
To: Nishanth Menon <nm@ti.com>
Cc: kernel-build-reports@lists.linaro.org,
"linaro-kernel@lists.linaro.org" <linaro-kernel@lists.linaro.org>,
linux-omap <linux-omap@vger.kernel.org>,
Tony Lindgren <tony@atomide.com>
Subject: Re: next boot: 36 pass, 3 fail (next-20140210)
Date: Mon, 10 Feb 2014 08:44:03 -0800 [thread overview]
Message-ID: <7hwqh2apf0.fsf@paris.lan> (raw)
In-Reply-To: <52F8FF98.1090408@ti.com> (Nishanth Menon's message of "Mon, 10 Feb 2014 10:34:32 -0600")
Nishanth Menon <nm@ti.com> writes:
> On 02/10/2014 10:33 AM, Kevin Hilman wrote:
>> +linux-omap list
>>
>> On Mon, Feb 10, 2014 at 7:58 AM, Kevin's boot bot <khilman@linaro.org> wrote:
>>> Automated DT boot report for various ARM defconfigs.
>>>
>>>
>>> Tree/Branch: next
>>> Git describe: next-20140210
>>> Failed boot tests (console logs at the end)
>>> ===========================================
>>> omap3-beagle-xm: FAIL: multi_v7_defconfig
>>> omap3-tobi: FAIL: multi_v7_defconfig
>>> omap4-panda-es: FAIL: multi_v7_defconfig
>>
>> These are all new OMAP failures, and appear to be an EHCI panic during
>> boot. Note that omap2plus_defconfig boots fine on all these boards,
>> this failure is only for multi_v7_defconfig.
>>
>> Not sure if anyone else has seen this yet.
>
> yep - reported and being looked here:
> http://marc.info/?t=139204803900004&r=1&w=2
Great, thanks.
Kevin
prev parent reply other threads:[~2014-02-10 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52f8f712.626d440a.6fab.5ae1@mx.google.com>
2014-02-10 16:33 ` next boot: 36 pass, 3 fail (next-20140210) Kevin Hilman
2014-02-10 16:34 ` Nishanth Menon
2014-02-10 16:44 ` Kevin Hilman [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=7hwqh2apf0.fsf@paris.lan \
--to=khilman@linaro.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=tony@atomide.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