From: Michael Ellerman <michael@ellerman.id.au>
To: Frank Prepelica <Frank.Prepelica@ubidyne.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: AW: Kernel fault with simple UIO interrupt driver in 2.6.30.4
Date: Fri, 07 Aug 2009 00:15:40 +1000 [thread overview]
Message-ID: <1249568140.20200.19.camel@concordia> (raw)
In-Reply-To: <29DC34A6B43468409F5A371CFE34E849DFCA3D@ex01.ads.ubidyne.de>
[-- Attachment #1: Type: text/plain, Size: 1692 bytes --]
On Tue, 2009-08-04 at 09:23 +0200, Frank Prepelica wrote:
> Oh okay, I didnt think anybody would need it :)
> IRQ 20/IRQ3 Kernel Driver: IRQF_DISABLED is not guaranteed on shared IRQs
> Unable to handle kernel paging request for instruction fetch
> Faulting instruction address: 0x00000000
> Oops: Kernel access of bad area, sig: 11 [#1]
> MPC831x RDB
> Modules linked in:
> NIP: 00000000 LR: c004755c CTR: 00000000
> REGS: c7827d50 TRAP: 0400 Not tainted (2.6.30.4)
> MSR: 20001032 <ME,IR,DR> CR: 28000022 XER: 20000000
> TASK = c7828000[1] 'swapper' THREAD: c7826000
> GPR00: 00000002 c7827e00 c7828000 00000014 00000002 00000014 c73adb7c c06bb460
> GPR08: 00000000 00000000 00000014 00000000 00000000 00000000 07fff000 00000001
> GPR16: ffffffff 00000000 007fff00 07ff9794 00000000 00000000 007ffeb0 00000000
> GPR24: c73ad180 c02d70a4 c0574f28 00009032 00000014 00000000 c73adb40 c0574f08
> Call Trace:
> [c7827e00] [c00474e4] 0xc00474e4 (unreliable)
> [c7827e20] [c0047754] 0xc0047754
> [c7827e50] [c019c568] 0xc019c568
> [c7827e90] [c019c7f8] 0xc019c7f8
> [c7827ea0] [c0177a80] 0xc0177a80
> [c7827ec0] [c0177b94] 0xc0177b94
> [c7827ee0] [c01764d8] 0xc01764d8
> [c7827f10] [c0177590] 0xc0177590
> [c7827f20] [c017703c] 0xc017703c
> [c7827f40] [c0178080] 0xc0178080
> [c7827f60] [c0319884] 0xc0319884
> [c7827f70] [c00038dc] 0xc00038dc
> [c7827fe0] [c03037c0] 0xc03037c0
> [c7827ff0] [c0010778] 0xc0010778
It would be more useful with symbols :)
But, you can see that it's taking a 400, ie. faulting on instruction
fetch - which suggests your driver is causing the kernel to try and
execute at instruction 0x0 - why I'm not sure.
cheers
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-08-06 14:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 7:23 AW: Kernel fault with simple UIO interrupt driver in 2.6.30.4 Frank Prepelica
2009-08-06 14:15 ` Michael Ellerman [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-08-04 11:04 Frank Prepelica
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=1249568140.20200.19.camel@concordia \
--to=michael@ellerman.id.au \
--cc=Frank.Prepelica@ubidyne.com \
--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;
as well as URLs for NNTP newsgroup(s).