From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Hilman Subject: Re: OMAP baseline test results for v3.7-rc1 Date: Mon, 22 Oct 2012 13:43:34 -0700 Message-ID: <87hapmfdah.fsf@deeprootsystems.com> References: <20121019190358.GI1613@blackmetal.musicnaut.iki.fi> <20121019190136.GA4229@arwen.pp.htv.fi> <20121019193847.GJ1613@blackmetal.musicnaut.iki.fi> <87y5iyfmmo.fsf@deeprootsystems.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mail-pa0-f46.google.com ([209.85.220.46]:40337 "EHLO mail-pa0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754195Ab2JVUnI (ORCPT ); Mon, 22 Oct 2012 16:43:08 -0400 Received: by mail-pa0-f46.google.com with SMTP id hz1so2212447pad.19 for ; Mon, 22 Oct 2012 13:43:08 -0700 (PDT) In-Reply-To: <87y5iyfmmo.fsf@deeprootsystems.com> (Kevin Hilman's message of "Mon, 22 Oct 2012 10:21:51 -0700") Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Aaro Koskinen Cc: Felipe Balbi , Paul Walmsley , linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org Kevin Hilman writes: > Aaro Koskinen writes: > >> Hi, >> >> On Fri, Oct 19, 2012 at 10:01:36PM +0300, Felipe Balbi wrote: >>> On Fri, Oct 19, 2012 at 10:03:58PM +0300, Aaro Koskinen wrote: >>> > FYI, I saw I2C hangs also on Nokia N900 with v3.7-rc1 (omap_i2c >>> > omap_i2c.1: timeout waiting for bus ready). After several reboots they >>> > disappered (kernel binary was the same), and I have been unable to >>> > reproduce them since. >>> >>> any change you have those logs saved somewhere ? Want to see if it's the >>> same problem triggered by RTC. >> >> I did not save the logs, but now I tried again, I managed to reproduce >> it after couple boots. The log is below, and after that the there's also >> one from OK boot for comparison. >> >> In the error case, the boot never reaches userspace, just silently hangs >> (or maybe I just didn't wait enough long). > > Can you try to revert the threaded IRQ conversion to see if things get > to working again? commit 3b2f8f82dad7d1f79cdc8fc05bd1c94baf109bde Nevermind, Paul seems to have already isolated the problem on this one. Kevin