linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Peter Kümmel" <syntheticpp@gmx.net>
To: balbi@ti.com, Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: Tony Lindgren <tony@atomide.com>,
	linux-omap@vger.kernel.org, Pavel Machek <pavel@ucw.cz>,
	Russell King <rmk+kernel@arm.linux.org.uk>,
	Santosh Shilimkar <ssantosh@kernel.org>
Subject: Re: 3.18.1->3.19-rc2: In-band Error seen by MPU
Date: Tue, 06 Jan 2015 12:25:12 +0100	[thread overview]
Message-ID: <54ABC618.8070906@gmx.net> (raw)
In-Reply-To: <20150105154313.GA19336@saruman>



Am 05.01.2015 um 16:43 schrieb Felipe Balbi:

>
> Just booted AM335x with CONFIG_PREEMPT and haven't seen any problem.
> Perhaps this is something related to another OMAP3-only driver ? Perhaps
> HSI/SSI ?
>
> cheers
>

I see a ssi error directly before the IN-Band error:

[    0.339935] platform 48058000.ssi-controller: Cannot lookup hwmod 'ssi'
[    0.346893] In-band Error seen by MPU  at address 0
[    0.346923] ------------[ cut here ]------------

Peter

  parent reply	other threads:[~2015-01-06 11:26 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-01 18:12 3.18.1->3.19-rc2: In-band Error seen by MPU Peter Kümmel
2015-01-01 18:20 ` Aaro Koskinen
2015-01-02 16:19   ` Tony Lindgren
2015-01-02 18:31     ` Peter Kümmel
2015-01-02 20:19       ` Aaro Koskinen
2015-01-02 20:40         ` Tony Lindgren
2015-01-02 22:34           ` Aaro Koskinen
2015-01-03  0:02             ` Tony Lindgren
2015-01-03 11:24               ` Peter Kümmel
2015-01-03 12:16               ` Aaro Koskinen
2015-01-05 15:43                 ` Felipe Balbi
2015-01-05 23:16                   ` Aaro Koskinen
2015-01-06  0:12                     ` Tony Lindgren
2015-01-06  2:02                       ` Felipe Balbi
2015-01-06  2:01                     ` Felipe Balbi
2015-01-06 12:38                       ` Aaro Koskinen
2015-01-06 16:51                         ` [PATCH] irqchip: omap-intc: fix legacy DMA regression Felipe Balbi
2015-01-06 17:48                           ` Aaro Koskinen
2015-01-06 17:52                             ` Tony Lindgren
2015-01-06 18:05                           ` Russell King - ARM Linux
2015-01-06 18:24                             ` Aaro Koskinen
2015-01-06 18:30                             ` Tony Lindgren
2015-01-06 20:38                           ` [PATCH v2] " Felipe Balbi
2015-01-07  3:00                             ` Jason Cooper
2015-01-19 18:34                               ` Tony Lindgren
2015-01-07 11:12                           ` [PATCH] " Peter Kümmel
2015-01-06 11:25                   ` Peter Kümmel [this message]
2015-01-06 11:52                     ` 3.18.1->3.19-rc2: In-band Error seen by MPU Sebastian Reichel
2015-01-06 12:47                       ` Aaro Koskinen
2015-01-06 13:47                         ` Peter Kümmel
2015-01-06 13:04                       ` Peter Kümmel

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=54ABC618.8070906@gmx.net \
    --to=syntheticpp@gmx.net \
    --cc=aaro.koskinen@iki.fi \
    --cc=balbi@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rmk+kernel@arm.linux.org.uk \
    --cc=ssantosh@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).