Thanks for your reply. Yes, our driver is programmed to share irqs.
SA_SHIRQ is used.
Dinesh
black hole wrote:
Hello,
On 10/31/06, *Dinesh* <dbhat@xxxxxxxxx <mailto:dbhat@xxxxxxxxx>> wrote:
Hello,
I have a problem with irqs.
As soon our DVB card shares its IRQ with another device (in our case
it's eth2), dmesg says this :
irq 12: nobody cared!
[<c0107c6a>]
[<c0107d50>]
[<c0107f60>]
[<c0105f20>]
[<c011992e>]
[<c01199b7>]
[<c0107f45>]
[<c0105f20>]
[<c01083de>]
[<d081d7c0>]
[<c0108020>]
[<d081da23>]
[<d081d7c0>]
[<d081e80c>]
[<c0211d15>]
[<c0213183>]
[<c024c26a>]
[<c024e576>]
[<c0209439>]
[<c01590d9>]
[<c0105db3>]
handlers:
[<d081d7c0>]
Disabling IRQ #12
cat /proc/interrupts show this:
CPU0
0: 96124 XT-PIC timer
2: 0 XT-PIC cascade
3: 2 XT-PIC serial
4: 6012 XT-PIC serial
5: 63 XT-PIC eth1
8: 0 XT-PIC rtc
10: 350 XT-PIC eth0
12: 300000 XT-PIC eth2, DVB Master Q/i
14: 1235 XT-PIC ide0
NMI: 0
ERR: 0
We tried to change kernel versions, from 2.6.9 to 2.6.18, to change e100
drivers, but it won't fix the issue.
Does anyone have any idea or solutions? I used noirqdebug, irqpoll,
noacpi options already but in vain.
Can anyone guide me in the right direction please?
Thanks,
Dinesh
Is your driver programmed to be able to share interrupts?
(I guess the eth2 driver in use is programmed that way).
BlackHole
--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive: http://mail.nl.linux.org/kernelnewbies/
FAQ: http://kernelnewbies.org/faq/
