[vdr] Re: Two DVB-T cards

["Adrian P Challinor" <adrian.challinor@osiris.co.uk>]

Well, thank you. At least it doesn't reboot now! 

But I have a problem with conflicting IRQ's. Both my TechnoTrend DVB-T
Premium card and the Nebula DVB-T budget card seem to get mapped to IRQ 21. 
When I load the Nebula drivers, I get lots of messages: 

Apr 18 14:23:56 vdr kernel: bt878(0): irq FBUS risc_pc=186ef008(0): irq FBUS
risc_pc=186ef000
Apr 18 14:23:56 vdr kernel: bt878(0): irq FBUS risc_pc=186ef000
Apr 18 14:23:56 vdr last message repeated 3343 times

Then a call trace... 

Apr 18 14:23:56 vdr kernel: irq 21: nobody cared!
Apr 18 14:23:56 vdr kernel: Call Trace:
Apr 18 14:23:56 vdr kernel:  [__report_bad_irq+35/128]
__report_bad_irq+0x23/0x80
Apr 18 14:23:56 vdr kernel:  [<c010d543>] __report_bad_irq+0x23/0x80
Apr 18 14:23:56 vdr kernel:  [note_interrupt+120/160]
note_interrupt+0x78/0xa0
Apr 18 14:23:56 vdr kernel:  [<c010d638>] note_interrupt+0x78/0xa0
Apr 18 14:23:56 vdr kernel:  [do_IRQ+217/256] do_IRQ+0xd9/0x100
Apr 18 14:23:56 vdr kernel:  [<c010d839>] do_IRQ+0xd9/0x100
Apr 18 14:23:56 vdr kernel:  [common_interrupt+24/32]
common_interrupt+0x18/0x20
Apr 18 14:23:56 vdr kernel:  [<c010bf28>] common_interrupt+0x18/0x20
Apr 18 14:23:56 vdr kernel:  [schedule+0/1568] schedule+0x0/0x620
Apr 18 14:23:56 vdr kernel:  [<c011f720>] schedule+0x0/0x620
Apr 18 14:23:56 vdr kernel:  [schedule_timeout+160/176]
schedule_timeout+0xa0/0xb0
Apr 18 14:23:56 vdr kernel:  [<c012a210>] schedule_timeout+0xa0/0xb0
Apr 18 14:23:56 vdr kernel:  [sock_ioctl+362/608] sock_poll+0x1a/0x20
Apr 18 14:23:56 vdr kernel:  [<c02d897a>] sock_poll+0x1a/0x20
Apr 18 14:23:56 vdr kernel:  [do_select+678/736] do_select+0x2a6/0x2e0
Apr 18 14:23:56 vdr kernel:  [<c0164326>] do_select+0x2a6/0x2e0
Apr 18 14:23:56 vdr kernel:  [__pollwait+0/176] __pollwait+0x0/0xb0
Apr 18 14:23:56 vdr kernel:  [<c0163ef0>] __pollwait+0x0/0xb0
Apr 18 14:23:56 vdr kernel:  [sys_select+720/1184] sys_select+0x2d0/0x4a0
Apr 18 14:23:56 vdr kernel:  [<c0164660>] sys_select+0x2d0/0x4a0
Apr 18 14:23:56 vdr kernel:  [sysenter_past_esp+82/121]
sysenter_past_esp+0x52/0x79
Apr 18 14:23:56 vdr kernel:  [<c010afa9>] sysenter_past_esp+0x52/0x79
Apr 18 14:23:56 vdr kernel:
Apr 18 14:23:56 vdr kernel: handlers:
Apr 18 14:23:56 vdr kernel: [__crc_deactivate_super+1048185/4975358]
(__crc_bttv_get_gpio_queue+0xd0c1c01/0xd0c859b [btt
v])
Apr 18 14:23:56 vdr kernel: [<e09c7140>]
(__crc_bttv_get_gpio_queue+0xd0c1c01/0xd0c859b [bttv])
Apr 18 14:23:56 vdr kernel: [__crc_deactivate_super+2044297/4975358]
(__crc_bt878_num+0xadae661/0xadaed6d [bt878])
Apr 18 14:23:56 vdr kernel: Disabling IRQ #21

After this, the TechnoTrend card will tune, but not the Nebula. 

Adrian


> -----Original Message-----
> From: vdr-bounce@linuxtv.org [mailto:vdr-bounce@linuxtv.org] On Behalf Of
> Michal Dobrzynski
> Sent: Sunday, April 18, 2004 4:04 AM
> To: vdr@linuxtv.org
> Subject: [vdr] Re: Two DVB-T cards
> 
> Do you mean it crashes or just reboots suddenly?
> 
> If it's a sudden reboot make sure you don't have any watchdog timers
> enabled in your kernel. I had the same problem and it didn't matter
> what I did the machine just rebooted a couple of minutes after
> starting. I disabled the watchdog in the kernel config, recompiled and
> the problem went away.
> 
> Regards,
> Michal
> 



-- 
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe vdr" as subject.