From: Kumar Gala <galak@kernel.crashing.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc/ipic: unmask all interrupt sources
Date: Thu, 6 Aug 2009 21:26:48 -0500 [thread overview]
Message-ID: <7AF37DF7-6BC8-4CAD-911C-8EC93B0CB199@kernel.crashing.org> (raw)
In-Reply-To: <20090805194112.GA18204@www.tglx.de>
On Aug 5, 2009, at 2:41 PM, Sebastian Andrzej Siewior wrote:
> in case the interrupt controller was used in an earlier life then it
> is
> possible it is that some of its sources were used and are still
> unmask.
> If the (unmasked) device is active and is creating interrupts (or one
> interrupts was pending since the interrupts were disabled) then the
> boot
> process "ends" very soon. Once external interrupts are enabled, we
> land in
> -> do_IRQ
> -> call ppc_md.get_irq()
> -> ipic_read() gets the source number
> -> irq_linear_revmap(source)
> -> revmap[source] == NO_IRQ
> -> irq_find_mapping(source) returns NO_IRQ because no source
> is registered
> -> source is NO_IRQ, ppc_spurious_interrupts gets incremented, no
> further action.
>
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> ---
> This solves my kexec problem I had earlier. I could disable the device
> in ->shutdown path but the device in question could been used in the
> boot loader. Usually one gets the "nobody cared" message for unhandled
> interrupts but in this (rare) case nothing happens and box stands
> still.
>
> arch/powerpc/sysdev/ipic.c | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
applied to next
- k
prev parent reply other threads:[~2009-08-07 2:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 19:41 [PATCH] powerpc/ipic: unmask all interrupt sources Sebastian Andrzej Siewior
2009-08-05 20:04 ` Kumar Gala
2009-08-05 21:29 ` Sebastian Andrzej Siewior
2009-08-07 2:26 ` Kumar Gala [this message]
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=7AF37DF7-6BC8-4CAD-911C-8EC93B0CB199@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=bigeasy@linutronix.de \
--cc=linuxppc-dev@ozlabs.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