From: "Sébastien Taylor" <sebastient@otii.com>
To: linux-mips@linux-mips.org
Subject: Problem registering interrupt
Date: Tue, 21 Dec 2004 10:55:56 -0700 [thread overview]
Message-ID: <9040F8C6-5379-11D9-944D-000393DBC6BE@otii.com> (raw)
Hello,
I am porting my driver from 2.4 to 2.6 and am having an issue with
interrupts, I've updated my interrupt handler to return irqreturn_t
instead of void and it looks like it should be ok, but on init, when I
call request_irq it blows up in my face (trace bellow).
Now, if I request_irq with SA_SHIRQ it does boot up fine, but when I
try to use the driver it blows up again. Now, I'm guessing that means
something else is requesting my irq number first which is why it works
with SA_SHIRQ but why would that cause a crash? Should it not just
return an error message?
Wasn't sure what code would be relevant so hopefully that explaination
helps,
Any help would be greatly appreciated.
CPU 0 Unable to handle kernel paging request at virtual address
00000004, epc =4
Oops in arch/mips/mm/fault.c::do_page_fault, line 166[#1]:
Cpu 0
$ 0 : 00000000 1000fc00 00000000 803382d8
$ 4 : 803382d8 80340000 00000001 804e92a8
$ 8 : 80340000 00000a35 80510000 80510000
$12 : 80510000 8113f074 8113f07c 0000ffff
$16 : 80367620 80367628 1000fc01 00000031
$20 : 805bef28 00000000 00000000 00000000
$24 : 00000000 00000078
$28 : 80570000 80571f20 00000000 801430c4
Hi : 000000a1
Lo : 47ad5a00
epc : 801430c8 setup_irq+0x148/0x224 Not tainted
ra : 801430c4 setup_irq+0x144/0x224
Status: 1000fc02 KERNEL EXL
Cause : 00808008
BadVA : 000000e1
PrId : 03030200
Process swapper (pid: 1, threadinfo=80570000, task=80554b48)
Stack : 805bef28 80340000 00000001 804e92a8 805bef28 80217188 00000000
00000000
00000031 803250e8 801433b4 80143368 00000000 80340000 00000001
804e92a8
00000000 80320000 80380000 00000000 00000000 00000000 8037a958
8037a56c
00000000 00000001 80808081 00000000 00000000 00000000 80382fec
00000000
80380000 80100518 00000000 00000000 00000000 00000000 00000000
00000000
...
Call Trace:
[<80217188>] mc2interrupt+0x0/0x368
[<801433b4>] request_irq+0xd0/0x12c
[<80143368>] request_irq+0x84/0x12c
[<80380000>] init+0x38/0xe0
[<8037a958>] mc2init+0x80/0x1d4
[<8037a56c>] tty_init+0x160/0x184
[<80380000>] init+0x38/0xe0
[<80100518>] init+0xbc/0x1f8
[<80104de0>] kernel_thread_helper+0x10/0x18
[<80104dd0>] kernel_thread_helper+0x0/0x18
Code: 0c049dad ae00000c 8e020004 <8c420004> 1040000a 00000000
3c048032 0c0
Kernel panic - not syncing: Attempted to kill init!
next reply other threads:[~2004-12-21 17:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-21 17:55 Sébastien Taylor [this message]
[not found] <41C947CC.20709@innova-card.com>
2004-12-22 10:19 ` Problem registering interrupt moreau francis
2004-12-22 10:44 ` Jan-Benedict Glaw
2004-12-22 10:44 ` Jan-Benedict Glaw
2005-01-06 22:19 ` Sébastien Taylor
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=9040F8C6-5379-11D9-944D-000393DBC6BE@otii.com \
--to=sebastient@otii.com \
--cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.