From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nishanth Menon Subject: Re: next boot: 36 pass, 3 fail (next-20140210) Date: Mon, 10 Feb 2014 10:34:32 -0600 Message-ID: <52F8FF98.1090408@ti.com> References: <52f8f712.626d440a.6fab.5ae1@mx.google.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Return-path: Received: from comal.ext.ti.com ([198.47.26.152]:44942 "EHLO comal.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752111AbaBJQel (ORCPT ); Mon, 10 Feb 2014 11:34:41 -0500 In-Reply-To: Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Kevin Hilman , kernel-build-reports@lists.linaro.org, "linaro-kernel@lists.linaro.org" , linux-omap , Tony Lindgren 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 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 -- Regards, Nishanth Menon