RE: Problem with MPC8536 and external IRQs when using a loadable kernel module
On Thu, 2010-12-09 at 17:20 -0800, Mark Pearson wrote: Magical - thank you very very much. The patch fixes the problem Really appreciate the quick response - and I would never have found that in a million years. No worries. Looks like someone should send 78e2e68a2b to the stable crew. FSL guys? I think it has already been sent to the sta...@kernel.org. Not sure if it has been included though. - Leo ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: Problem with MPC8536 and external IRQs when using a loadable kernel module
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 signature.asc Description: This is a digitally signed message part ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
RE: Problem with MPC8536 and external IRQs when using a loadable kernel module
Magical - thank you very very much. The patch fixes the problem Really appreciate the quick response - and I would never have found that in a million years. Mark -Original Message- From: Michael Ellerman [mailto:mich...@ellerman.id.au] Sent: Thursday, December 09, 2010 6:33 PM To: Mark Pearson Cc: linuxppc-dev@lists.ozlabs.org Subject: Re: Problem with MPC8536 and external IRQs when using a loadable kernel module 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 Confidentiality Notice: This message and any attachments may contain privileged and confidential information. If you have reason to believe that you are not the intended recipient or a person responsible for delivering this information to an intended recipient, you are hereby notified that any review, dissemination, distribution, or copying of this message is strictly prohibited. Please contact the sender immediately by reply mail and destroy all copies of the original message. ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
RE: Problem with MPC8536 and external IRQs when using a loadable kernel module
On Thu, 2010-12-09 at 17:20 -0800, Mark Pearson wrote: Magical - thank you very very much. The patch fixes the problem Really appreciate the quick response - and I would never have found that in a million years. No worries. Looks like someone should send 78e2e68a2b to the stable crew. FSL guys? cheers signature.asc Description: This is a digitally signed message part ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
