From: Michael Ellerman <michael@ellerman.id.au>
To: Mark Pearson <Mark.Pearson@bladenetwork.net>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Problem with MPC8536 and external IRQs when using a loadable kernel module
Date: Fri, 10 Dec 2010 10:33:14 +1100 [thread overview]
Message-ID: <1291937594.3523.20.camel@concordia> (raw)
In-Reply-To: <11BA25866A2E3A45A797B469B2344B3901554D3D@blademail.bladenetwork.net>
[-- Attachment #1: Type: text/plain, Size: 854 bytes --]
On Thu, 2010-12-09 at 12:45 -0800, Mark Pearson wrote:
> I have a curious problem. This is on a MPC8636 based platform with
> 36-bit address space (that may or may not be important).
>
>
>
> I have a very simple driver that registers for one of the external
> IRQs with a trivial interrupt handler. It works great when built in as
> part of the kernel.
>
>
>
> However, if I make it a loadable module I get the crash shown below
> (blade_irq is my IRQ handler).
>
>
>
> -----Console capture ----------------------------------------
>
> Unable to handle kernel paging request for instruction fetch
^^^^^^^^^^^^^^^^^
Your interrupt handler isn't mapped executable? Something wrong with
module loading?
Do you need 78e2e68a2b79f394b7cd61e07987a8a89af907f7 ?
cheers
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-12-09 23:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 20:45 Problem with MPC8536 and external IRQs when using a loadable kernel module Mark Pearson
2010-12-09 23:33 ` Michael Ellerman [this message]
2010-12-10 1:20 ` Mark Pearson
2010-12-10 3:07 ` Michael Ellerman
2010-12-10 8:03 ` Li Yang-R58472
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=1291937594.3523.20.camel@concordia \
--to=michael@ellerman.id.au \
--cc=Mark.Pearson@bladenetwork.net \
--cc=linuxppc-dev@lists.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