From: Ian Molton <ian.molton@codethink.co.uk>
To: linux-sh@vger.kernel.org
Subject: EMEV2: debugging a Strange IRQ issue on SMP
Date: Mon, 22 Jul 2013 17:15:36 +0000 [thread overview]
Message-ID: <51ED68B8.3070302@codethink.co.uk> (raw)
Hi guys,
I'm currently attempting to debug strange interrupt handling behaviour
on EMEV2.
I and Ben Dooks undertook a port of much of the EMEV2 (mach-emxx) to
2.6.39 a couple of weeks ago, and I recall having dealt with similar
problems before, although they went away with some patches that fixed
the pl310 cache controller behaviour.
We are now working on mainline (3.10+) and are seeing what appears to be
the same problem -
IRQs are arriving, usually, but it seems that under some unknown
circumstances, the interrupts from the STI timer stop arriving when in
SMP mode.
They often dont stop immediately but work briefly, and then stop
somewhat randomly, usually causing driver probes to hang during an
msleep() or such.
I've compared the SCU and GIC (distributor and CPU) registers between
the working (2.6.39) kernel, and the non-working mainline effort, and
not found any real differences, other than some oddities in undocumented
(and possibly irrelevant?) registers. All the documented registers
contain sane, and substantially identical looking values.
the SCU is enabled, and both CPUs are set to coherent.
the problem occurs despite the L2 cache being completely disabled.
**the problem goes away when booting with nosmp**
Older kernels required the GIC to be mapped in a "Strongly ordered"
region, however emulating this behaviour in mainline does not appear to
help.
Older kernels only exhibited this issue with L2 enabled.
I'm wondering if this is some strange IRQ routing issue, but its eluding
me at present.
Has anyone seem odd IRQ bahaviour on SMP setups before?
next reply other threads:[~2013-07-22 17:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 17:15 Ian Molton [this message]
2013-07-23 10:53 ` EMEV2: debugging a Strange IRQ issue on SMP Ian Molton
2013-07-23 12:34 ` Ian Molton
2013-07-24 3:23 ` Magnus Damm
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=51ED68B8.3070302@codethink.co.uk \
--to=ian.molton@codethink.co.uk \
--cc=linux-sh@vger.kernel.org \
/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).