From: Tony Lindgren <tony@atomide.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
Yingjoe Chen <yingjoe.chen@mediatek.com>,
Marc Zyngier <marc.zyngier@arm.com>,
Jason Cooper <jason@lakedaemon.net>, Felipe Balbi <balbi@ti.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Regression with legacy IRQ numbers caused by 9a1091ef0017
Date: Fri, 16 Jan 2015 08:21:20 -0800 [thread overview]
Message-ID: <20150116162119.GK18552@atomide.com> (raw)
In-Reply-To: <20150115171924.GV11502@n2100.arm.linux.org.uk>
* Russell King - ARM Linux <linux@arm.linux.org.uk> [150115 09:22]:
> On Thu, Jan 15, 2015 at 07:28:39AM -0800, Tony Lindgren wrote:
> > * Russell King - ARM Linux <linux@arm.linux.org.uk> [150115 02:53]:
> > > I don't think we've proven a link there. While you're right that it
> > > causes the wrong interrupt to be claimed, I have two kernels here,
> > > both claim the same interrupt, one which is multi-platform and issues
> > > that strange warning, and one which targets only OMAP4 which doesn't.
> > >
> > > There's something else going on which causes the bus errors which we
> > > haven't found.
> >
> > I think it gets triggered if you enable PREEMPT.
>
> That's something which we can try to prove... build running now with
> CONFIG_PREEMPT=y
Looks like you now have the omap_l3_noc error appear for sdp4430 in
your logs after enabling PREEMPT.
I guess that means case closed for this one?
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: Regression with legacy IRQ numbers caused by 9a1091ef0017
Date: Fri, 16 Jan 2015 08:21:20 -0800 [thread overview]
Message-ID: <20150116162119.GK18552@atomide.com> (raw)
In-Reply-To: <20150115171924.GV11502@n2100.arm.linux.org.uk>
* Russell King - ARM Linux <linux@arm.linux.org.uk> [150115 09:22]:
> On Thu, Jan 15, 2015 at 07:28:39AM -0800, Tony Lindgren wrote:
> > * Russell King - ARM Linux <linux@arm.linux.org.uk> [150115 02:53]:
> > > I don't think we've proven a link there. While you're right that it
> > > causes the wrong interrupt to be claimed, I have two kernels here,
> > > both claim the same interrupt, one which is multi-platform and issues
> > > that strange warning, and one which targets only OMAP4 which doesn't.
> > >
> > > There's something else going on which causes the bus errors which we
> > > haven't found.
> >
> > I think it gets triggered if you enable PREEMPT.
>
> That's something which we can try to prove... build running now with
> CONFIG_PREEMPT=y
Looks like you now have the omap_l3_noc error appear for sdp4430 in
your logs after enabling PREEMPT.
I guess that means case closed for this one?
Regards,
Tony
next prev parent reply other threads:[~2015-01-16 16:25 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 22:14 Regression with legacy IRQ numbers caused by 9a1091ef0017 Tony Lindgren
2015-01-14 22:14 ` Tony Lindgren
2015-01-15 10:50 ` Russell King - ARM Linux
2015-01-15 10:50 ` Russell King - ARM Linux
2015-01-15 15:28 ` Tony Lindgren
2015-01-15 15:28 ` Tony Lindgren
2015-01-15 17:19 ` Russell King - ARM Linux
2015-01-15 17:19 ` Russell King - ARM Linux
2015-01-16 16:21 ` Tony Lindgren [this message]
2015-01-16 16:21 ` Tony Lindgren
2015-01-16 16:30 ` Russell King - ARM Linux
2015-01-16 16:30 ` Russell King - ARM Linux
2015-01-16 16:41 ` Tony Lindgren
2015-01-16 16:41 ` Tony Lindgren
2015-01-16 16:46 ` Felipe Balbi
2015-01-16 16:46 ` Felipe Balbi
2015-01-16 17:22 ` Russell King - ARM Linux
2015-01-16 17:22 ` Russell King - ARM Linux
2015-01-16 17:29 ` Tony Lindgren
2015-01-16 17:29 ` Tony Lindgren
2015-01-16 22:52 ` Tony Lindgren
2015-01-16 22:52 ` Tony Lindgren
2015-01-16 22:57 ` Russell King - ARM Linux
2015-01-16 22:57 ` Russell King - ARM Linux
2015-01-16 22:57 ` Tony Lindgren
2015-01-16 22:57 ` Tony Lindgren
2015-01-15 13:42 ` Marc Zyngier
2015-01-15 13:42 ` Marc Zyngier
2015-01-15 14:27 ` Arnd Bergmann
2015-01-15 14:27 ` Arnd Bergmann
2015-01-15 14:43 ` Marc Zyngier
2015-01-15 14:43 ` Marc Zyngier
2015-01-15 15:37 ` Tony Lindgren
2015-01-15 15:37 ` Tony Lindgren
2015-01-16 16:56 ` Arnd Bergmann
2015-01-16 16:56 ` Arnd Bergmann
2015-01-16 17:23 ` Marc Zyngier
2015-01-16 17:23 ` Marc Zyngier
2015-01-17 0:48 ` Simon Horman
2015-01-17 0:48 ` Simon Horman
2015-01-15 16:37 ` Arnd Bergmann
2015-01-15 16:37 ` Arnd Bergmann
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=20150116162119.GK18552@atomide.com \
--to=tony@atomide.com \
--cc=balbi@ti.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=marc.zyngier@arm.com \
--cc=tglx@linutronix.de \
--cc=yingjoe.chen@mediatek.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.