VU+Solo -> Kernel panic with Cccam and latest images (VTI4.1, BH 1.7)

**fced** · 26-02-2012, 07:16 PM

Hello,
I experiment kernels panic on my VU+Solo (original one (return to love auth ok)) when Cccam is installed and running...
Peoples on VU+support.com have said to me it's a drivers problems wich is uncompatible with CCcam, and wich cause the kernel panics ... So i tried with Oscam, and no kernel panic...
This problem happen with VTI 4.1 (4.0 is ok), Blackhole 1.6.7 and up, ViX-2.3.204... i think it's images

May be uninstall the driver wich cause problem and replace it with an older one... but i'm unable to identify wich driver is causing kernel panic...

Any help to identify the driver wich cause panic, or the problem himself please ? any idea ?

here is the part of the log when kernel panic occur :

Code:

hdd IDLE!
[IDLE] 3263.99992609 60 True
[EPGC] start cleanloop
[EPGC] stop cleanloop
[EPGC] 1268267 bytes for cache used
It's now  Thu Feb 23 16:28:15 2012
next real activation is Thu Feb 23 17:24:40 2012
[timer.py] next activation: 1330014595 (in 99995 ms)
nr_read 241 nr_write 10
sum 251 prev_sum 251
hdd IDLE!
[IDLE] 3269.99993515 60 True
nr_read 241 nr_write 10
sum 251 prev_sum 251
hdd IDLE!
[IDLE] 3275.99993515 60 True
CPU 0 Unable to handle kernel paging request at virtual address 00000008, epc == 802780ac, ra == 80279db4
Oops[#1]:
Cpu 0
$ 0   : 00000000 00000000 00000000 00000000
$ 4   : 80605d70 806057cc 00000000 00000d46
$ 8   : 00000001 00000000 00000001 00000000
$12   : 00000005 000003ff 80600000 805066fc
$16   : 80605d70 86469a30 00000000 80605d70
$20   : fffffffc 806057d0 fffffffe 806057cc
$24   : 00000001 8002305c                  
$28   : 86464000 86465b88 3b9aca00 80279db4
Hi    : 00000317
Lo    : 38148500
epc   : 802780ac rb_insert_color+0x54/0x1d0
    Tainted: P           
ra    : 80279db4 timerqueue_add+0x88/0x134
Status: 11000402    KERNEL EXL 
Cause : 00800008
BadVA : 00000008
PrId  : 0101954c (Brcm4380)
Modules linked in: brcmfb dvb_bcm7325(P) procmk
Process CCcam2_3_0 (pid: 741, threadinfo=86464000, task=84c0f728, tls=739fc930)
Stack : 80680000 800564e0 00000001 80279cd8 84c0f87c 80605d70 806057cc 86465c20
        80605790 00000003 806057d0 80600000 00000001 80279db4 86465c20 80605790
        00000003 806057d0 80605d70 806057c0 86465c20 80048e24 86465c20 00000000
        00000001 00000068 80600000 80605790 86465c18 80049c10 84c0f728 ffffffff
        84c0f728 ffffffff 804fedac 86626400 0f7f7b3c 00000d46 0f7f7b3c 00000d46
        ...
Call Trace:
[<802780ac>] rb_insert_color+0x54/0x1d0
[<80279db4>] timerqueue_add+0x88/0x134
[<80048e24>] __run_hrtimer+0x9c/0x110
[<80049c10>] hrtimer_interrupt+0x164/0x4b0
[<8000b6a4>] c0_compare_interrupt+0x3c/0x64
[<80060844>] handle_irq_event_percpu+0x5c/0x280
[<800634ac>] handle_percpu_irq+0x58/0x8c
[<80060408>] generic_handle_irq+0x44/0x64
[<80005818>] do_IRQ+0x18/0x24
[<8000225c>] plat_irq_dispatch+0xbc/0x1e0
[<80003f6c>] ret_from_irq+0x0/0x4
[<8027e1fc>] __copy_user+0x38/0x2bc
[<c07025e8>] sc_dev_ioctl+0x204/0x448 [dvb_bcm7325]


Code: 30430001  14600016  00549024 <8e500008> 12110032  00000000  12000020  00000000  8e030000 
---[ end trace a0b5fc5d59378cd2 ]---
Kernel panic - not syncing: Fatal exception in interrupt
Rebooting in 180 seconds..