All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jyri Sarha <jsarha@ti.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	Tero Kristo <t-kristo@ti.com>,
	Tomi Valkeinen <tomi.valkeinen@ti.com>,
	Peter Ujfalusi <peter.ujfalusi@ti.com>,
	Nishanth Menon <nm@ti.com>
Subject: Re: OMAP 4430 SDP: rather sick with recent kernels
Date: Wed, 17 Dec 2014 23:08:06 +0200	[thread overview]
Message-ID: <5491F0B6.4090904@ti.com> (raw)
In-Reply-To: <20141217185155.GI11502@n2100.arm.linux.org.uk>

On 12/17/2014 08:51 PM, Russell King - ARM Linux wrote:
> On Wed, Dec 17, 2014 at 09:23:33AM -0800, Tony Lindgren wrote:
>> Hi,
>>
>> * Russell King - ARM Linux <linux@arm.linux.org.uk> [141217 01:55]:
>>> Tony,
>>>
>>> As the IOMMU stuff was merged last night, which removed a really quite
>>> horrid conflict resolution, I updated my nightly build tree from its
>>> previous state last Thursday.
>>>
>>> Now, SDP4430 seems to be really quite broken.
>>
>> Sigh, things are just break left and right every merge window :(
>
> Some of these things were present before the merge window, so they're
> less of a concern.  The biggest problem though is the ABE ASoC stuff
> exploding, which prevents my test system getting anywhere near mounting
> its rootfs.
>
> It's fine in the "combined" case, because we end up totally dead as
> far as serial console goes, but the "omap4430" kernel boot test never
> ends because the kernel doesn't stop spewing "rcu_sched stall" messages.
>

I tried booting my 4460 Panda - which is the closest thing to 4430SDP 
that I've got - on next-20141217, but I could not get it to the point 
where the omap-abe-twl6040 probed. It probably is the problem you are 
talking about as the hang does not happen if I disable ASoC ABE all 
together, right?

I'll take a deeper look at it tomorrow, as Peter is not working ATM.

Best regards,
Jyri

WARNING: multiple messages have this Message-ID (diff)
From: jsarha@ti.com (Jyri Sarha)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP 4430 SDP: rather sick with recent kernels
Date: Wed, 17 Dec 2014 23:08:06 +0200	[thread overview]
Message-ID: <5491F0B6.4090904@ti.com> (raw)
In-Reply-To: <20141217185155.GI11502@n2100.arm.linux.org.uk>

On 12/17/2014 08:51 PM, Russell King - ARM Linux wrote:
> On Wed, Dec 17, 2014 at 09:23:33AM -0800, Tony Lindgren wrote:
>> Hi,
>>
>> * Russell King - ARM Linux <linux@arm.linux.org.uk> [141217 01:55]:
>>> Tony,
>>>
>>> As the IOMMU stuff was merged last night, which removed a really quite
>>> horrid conflict resolution, I updated my nightly build tree from its
>>> previous state last Thursday.
>>>
>>> Now, SDP4430 seems to be really quite broken.
>>
>> Sigh, things are just break left and right every merge window :(
>
> Some of these things were present before the merge window, so they're
> less of a concern.  The biggest problem though is the ABE ASoC stuff
> exploding, which prevents my test system getting anywhere near mounting
> its rootfs.
>
> It's fine in the "combined" case, because we end up totally dead as
> far as serial console goes, but the "omap4430" kernel boot test never
> ends because the kernel doesn't stop spewing "rcu_sched stall" messages.
>

I tried booting my 4460 Panda - which is the closest thing to 4430SDP 
that I've got - on next-20141217, but I could not get it to the point 
where the omap-abe-twl6040 probed. It probably is the problem you are 
talking about as the hang does not happen if I disable ASoC ABE all 
together, right?

I'll take a deeper look at it tomorrow, as Peter is not working ATM.

Best regards,
Jyri

  parent reply	other threads:[~2014-12-17 21:08 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-17  9:52 OMAP 4430 SDP: rather sick with recent kernels Russell King - ARM Linux
2014-12-17  9:52 ` Russell King - ARM Linux
2014-12-17 17:23 ` Tony Lindgren
2014-12-17 17:23   ` Tony Lindgren
2014-12-17 17:33   ` Nishanth Menon
2014-12-17 17:33     ` Nishanth Menon
2014-12-17 17:34     ` Tony Lindgren
2014-12-17 17:34       ` Tony Lindgren
2014-12-17 18:51   ` Russell King - ARM Linux
2014-12-17 18:51     ` Russell King - ARM Linux
2014-12-17 19:09     ` Tony Lindgren
2014-12-17 19:09       ` Tony Lindgren
2014-12-17 20:44       ` Tony Lindgren
2014-12-17 20:44         ` Tony Lindgren
2014-12-17 21:08     ` Jyri Sarha [this message]
2014-12-17 21:08       ` Jyri Sarha
2014-12-18 10:16       ` Russell King - ARM Linux
2014-12-18 10:16         ` Russell King - ARM Linux
2014-12-18 11:48         ` Peter Rosin
2014-12-18 11:48           ` Peter Rosin
2014-12-18 13:12           ` Jyri Sarha
2014-12-18 13:12             ` Jyri Sarha
2014-12-18 11:49         ` Mark Brown
2014-12-18 11:49           ` Mark Brown
2014-12-31 14:00           ` Peter Ujfalusi
2014-12-31 14:00             ` Peter Ujfalusi
2014-12-31 18:52             ` Mark Brown
2014-12-31 18:52               ` Mark Brown
2014-12-18 16:41   ` Tony Lindgren
2014-12-18 16:41     ` Tony Lindgren
2014-12-31 12:59     ` Peter Ujfalusi
2014-12-31 12:59       ` Peter Ujfalusi
2015-01-14 17:51 ` Russell King - ARM Linux
2015-01-14 17:51   ` Russell King - ARM Linux
2015-01-14 19:09   ` Tony Lindgren
2015-01-14 19:09     ` Tony Lindgren
2015-01-14 22:27     ` Tony Lindgren
2015-01-14 22:27       ` Tony Lindgren
2015-01-14 23:10     ` Russell King - ARM Linux
2015-01-14 23:10       ` Russell King - ARM Linux
2015-01-15 10:48       ` Russell King - ARM Linux
2015-01-15 10:48         ` Russell King - ARM Linux

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=5491F0B6.4090904@ti.com \
    --to=jsarha@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=nm@ti.com \
    --cc=peter.ujfalusi@ti.com \
    --cc=t-kristo@ti.com \
    --cc=tomi.valkeinen@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 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.