[linux-dvb] Mantis 2033 still not working with CAM inserted

[linux-dvb] Mantis 2033 still not working with CAM inserted

[Ruediger Dohmhardt]

[-- Attachment #1: Type: text/plain, Size: 515 bytes --]

Dear Manu,

the code from

http://jusst.de/hg/mantis (10.5.08)

now works fine for the 2033 without the CAM (here Alphacrypt Light) 
inserted.

When I insert the CAM, audio and video stop. I need to remove the CAM 
and  I must  reload the module with
 
    modprobe -r mantis
 
followed by

    modprobe mantis

Could you please look into the attached /var/log/messages file.
Maybe it could provide a hint, what's still wrong.

The verbose level is set to 3 (options mantis verbose=3)


Thanks

Ciao Ruediger D.




[-- Attachment #2: messages.gz --]
[-- Type: application/x-gzip, Size: 26072 bytes --]

[-- Attachment #3: Type: text/plain, Size: 150 bytes --]

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Mantis 2033 still not working with CAM inserted

[Manu Abraham]

Ruediger Dohmhardt wrote:
> Dear Manu,
> 
> the code from
> 
> http://jusst.de/hg/mantis (10.5.08)
> 
> now works fine for the 2033 without the CAM (here Alphacrypt Light)
> inserted.
> 
> When I insert the CAM, audio and video stop. I need to remove the CAM
> and  I must  reload the module with
> 
>    modprobe -r mantis
> 
> followed by
> 
>    modprobe mantis
> 
> Could you please look into the attached /var/log/messages file.
> Maybe it could provide a hint, what's still wrong.
> 
> The verbose level is set to 3 (options mantis verbose=3)


Applied some changes, couldn't test the changes while being away, but
only build tests. Please do test again, also feel free to play with the
individual changesets as to check for various stage tests.

Regards,
Manu


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] CAM of Mantis 2033 still not working

[Ruediger Dohmhardt]

Manu Abraham schrieb:
> Ruediger Dohmhardt wrote:
>   
>> Dear Manu,
>>
>> the code from
>>
>> http://jusst.de/hg/mantis (10.5.08)
>>
>> now works fine for the 2033 without the CAM (here Alphacrypt Light)
>> inserted.
>>
>> When I insert the CAM, audio and video stop. I need to remove the CAM
>> and  I must  reload the module with
>>
>>    modprobe -r mantis
>>
>> followed by
>>
>>    modprobe mantis
>>
>> Could you please look into the attached /var/log/messages file.
>> Maybe it could provide a hint, what's still wrong.
>>
>> The verbose level is set to 3 (options mantis verbose=3)
>>     
>
>
> Applied some changes, couldn't test the changes while being away, but
> only build tests. Please do test again, also feel free to play with the
> individual changesets as to check for various stage tests.
>   
Dear Manu,

all changesets from Saturday night did not recognize the CAM.
I could, though, keep the Alphacrypt-Light plugged, but vdr-1.4.7 
provided only TV from the unencrypted channels.
vdr's CAM menu could not access the CAM.

changeset 7325b14e79e460fc (Monday evening):
Unencrypted channels: ok:
When I zap to an encrypted one, the drive hangs as shown below.
Then I need to reboot the machine, because
   
    modprobe -r mantis
 
could not really unload the module.

----------------------------------------------------------------------------------------------------------------------------------------------------

May 20 08:57:08 linux-sh8m kernel: mantis start feed & dma
May 20 08:57:08 linux-sh8m vdr: [5682] KBD remote control thread started 
(pid=5662, tid=5682)
May 20 08:57:08 linux-sh8m vdr: [5683] transfer thread started 
(pid=5662, tid=5683)
May 20 08:57:08 linux-sh8m vdr: [5684] receiver on device 1 thread 
started (pid=5662, tid=5684)
May 20 08:57:08 linux-sh8m vdr: [5686] TS buffer on device 1 thread 
started (pid=5662, tid=5686)
May 20 08:57:08 linux-sh8m vdr: [5683] [xine..put] Detected video size 
720x576
May 20 08:57:09 linux-sh8m vdr: [5683] setting audio track to 1 (0)
May 20 08:57:12 linux-sh8m vdr: [5681] [xine..put] Client 0 connected: 
127.0.0.1:3484
May 20 08:57:12 linux-sh8m vdr: [5681] [xine..put] cxSocket: 
setsockopt(SO_SNDBUF): got 262142 bytes
May 20 08:57:12 linux-sh8m vdr: [5681] [xine..put] Trying PIPE 
connection ...
May 20 08:57:12 linux-sh8m vdr: [5681] creating directory 
/video/plugins/xineliboutput/pipes.5662
May 20 08:57:12 linux-sh8m vdr: [5681] removing 
/video/plugins/xineliboutput/pipes.5662
May 20 08:57:12 linux-sh8m vdr: [5681] [xine..put] cBackgroundWriterI 
initialized (buffer 512 kb)
May 20 08:57:12 linux-sh8m vdr: [5681] [xine..put] cTcpWriter 
initialized (buffer 512 kb)
May 20 08:57:12 linux-sh8m vdr: [5681] [xine..put] Pipe open
May 20 08:57:19 linux-sh8m vdr: [5679] changing pids of channel 58 from 
701+701:702:204 to 901+901:902:204
/*
* switching to encrypted channel
*/
May 20 08:57:39 linux-sh8m vdr: [5678] frontend 0 lost lock on channel 
1, tp 113
May 20 08:57:41 linux-sh8m vdr: [5678] frontend 0 timed out while tuning 
to channel 1, tp 113
May 20 08:58:07 linux-sh8m vdr: [5662] switching to channel 3
May 20 08:58:07 linux-sh8m vdr: [5683] transfer thread ended (pid=5662, 
tid=5683)
May 20 08:58:07 linux-sh8m vdr: [5686] TS buffer on device 1 thread 
ended (pid=5662, tid=5686)
May 20 08:58:07 linux-sh8m vdr: [5684] buffer stats: 113552 (5%) used
May 20 08:58:07 linux-sh8m vdr: [5684] receiver on device 1 thread ended 
(pid=5662, tid=5684)
May 20 08:58:07 linux-sh8m vdr: [5662] cTS2PES got 1 TS errors, 1 TS 
continuity errors
May 20 08:58:07 linux-sh8m vdr: [5662] cTS2PES got 1 TS errors, 1 TS 
continuity errors
May 20 08:58:07 linux-sh8m vdr: [5662] buffer stats: 205484 (9%) used
May 20 08:58:07 linux-sh8m vdr: [5723] transfer thread started 
(pid=5662, tid=5723)
May 20 08:58:07 linux-sh8m vdr: [5724] receiver on device 1 thread 
started (pid=5662, tid=5724)
May 20 08:58:07 linux-sh8m vdr: [5725] TS buffer on device 1 thread 
started (pid=5662, tid=5725)
May 20 08:58:16 linux-sh8m vdr: [5678] frontend 0 timed out while tuning 
to channel 3, tp 121
May 20 08:58:23 linux-sh8m vdr: [5662] switching to channel 2
May 20 08:58:23 linux-sh8m vdr: [5723] transfer thread ended (pid=5662, 
tid=5723)
May 20 08:58:23 linux-sh8m kernel: mantis stop feed and dma
May 20 08:58:23 linux-sh8m vdr: [5725] TS buffer on device 1 thread 
ended (pid=5662, tid=5725)
May 20 08:58:23 linux-sh8m vdr: [5724] buffer stats: 0 (0%) used
May 20 08:58:23 linux-sh8m vdr: [5724] receiver on device 1 thread ended 
(pid=5662, tid=5724)
May 20 08:58:23 linux-sh8m vdr: [5662] buffer stats: 0 (0%) used
May 20 08:58:23 linux-sh8m kernel: mantis start feed & dma
May 20 08:58:23 linux-sh8m vdr: [5726] transfer thread started 
(pid=5662, tid=5726)
May 20 08:58:23 linux-sh8m vdr: [5727] receiver on device 1 thread 
started (pid=5662, tid=5727)
May 20 08:58:23 linux-sh8m vdr: [5728] TS buffer on device 1 thread 
started (pid=5662, tid=5728)
/*
* Switching back to unencrypted channel
*7
May 20 08:58:26 linux-sh8m kernel: mantis_ack_wait (0): Slave RACK Fail !
May 20 08:58:26 linux-sh8m kernel: DVB: TDA10021(0): _tda10021_writereg, 
writereg error (reg == 0x0c, val == 0x1e, ret == -121)
May 20 08:58:28 linux-sh8m kernel: APIC error on CPU0: 40(40)
May 20 08:58:29 linux-sh8m kernel: mantis_ack_wait (0): Slave RACK Fail !
May 20 08:58:29 linux-sh8m kernel: DVB: TDA10021(0): _tda10021_writereg, 
writereg error (reg == 0x0d, val == 0x86, ret == -121)
May 20 08:58:32 linux-sh8m kernel: mantis_ack_wait (0): Slave RACK Fail !
May 20 08:58:32 linux-sh8m kernel: DVB: TDA10021(0): _tda10021_writereg, 
writereg error (reg == 0x0e, val == 0x43, ret == -121)
May 20 08:58:35 linux-sh8m kernel: mantis_ack_wait (0): Slave RACK Fail !
May 20 08:58:35 linux-sh8m kernel: DVB: TDA10021(0): _tda10021_writereg, 
writereg error (reg == 0x34, val == 0x22, ret == -121)
May 20 08:58:38 linux-sh8m kernel: mantis_ack_wait (0): Slave RACK Fail !
May 20 08:58:38 linux-sh8m kernel: DVB: TDA10021(0): _tda10021_writereg, 
writereg error (reg == 0x01, val == 0x6a, ret == -121)
May 20 08:58:41 linux-sh8m kernel: mantis_ack_wait (0): Slave RACK Fail !
May 20 08:58:41 linux-sh8m kernel: DVB: TDA10021(0): _tda10021_writereg, 
writereg error (reg == 0x05, val == 0x46, ret == -121)
May 20 08:58:44 linux-sh8m vdr: [5681] [xine..put] Closing connection 0
May 20 08:58:44 linux-sh8m kernel: mantis_ack_wait (0): Slave RACK Fail !
May 20 08:58:44 linux-sh8m kernel: DVB: TDA10021(0): _tda10021_writereg, 
writereg error (reg == 0x08, val == 0x43, ret == -121)
May 20 08:58:47 linux-sh8m kernel: mantis_ack_wait (0): Slave RACK Fail !
May 20 08:58:47 linux-sh8m kernel: DVB: TDA10021(0): _tda10021_writereg, 
writereg error (reg == 0x09, val == 0x6a, ret == -121)
May 20 08:58:50 linux-sh8m kernel: mantis_ack_wait (0): Slave RACK Fail !
May 20 08:58:50 linux-sh8m kernel: DVB: TDA10021(0): _tda10021_writereg, 
writereg error (reg == 0x00, val == 0x6a, ret == -121)
May 20 08:58:53 linux-sh8m kernel: mantis_ack_wait (0): Slave RACK Fail !
May 20 08:58:53 linux-sh8m kernel: DVB: TDA10021(0): _tda10021_writereg, 
writereg error (reg == 0x00, val == 0x6b, ret == -121)




Ciao Ruediger


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] CAM of Mantis 2033 still not working

[Manu Abraham]

Ruediger Dohmhardt wrote:
> Manu Abraham schrieb:
>> Ruediger Dohmhardt wrote:
>>  
>>> Dear Manu,
>>>
>>> the code from
>>>
>>> http://jusst.de/hg/mantis (10.5.08)
>>>
>>> now works fine for the 2033 without the CAM (here Alphacrypt Light)
>>> inserted.
>>>
>>> When I insert the CAM, audio and video stop. I need to remove the CAM
>>> and  I must  reload the module with
>>>
>>>    modprobe -r mantis
>>>
>>> followed by
>>>
>>>    modprobe mantis
>>>
>>> Could you please look into the attached /var/log/messages file.
>>> Maybe it could provide a hint, what's still wrong.
>>>
>>> The verbose level is set to 3 (options mantis verbose=3)
>>>     
>>
>>
>> Applied some changes, couldn't test the changes while being away, but
>> only build tests. Please do test again, also feel free to play with the
>> individual changesets as to check for various stage tests.
>>   
> Dear Manu,
> 
> all changesets from Saturday night did not recognize the CAM.
> I could, though, keep the Alphacrypt-Light plugged, but vdr-1.4.7
> provided only TV from the unencrypted channels.
> vdr's CAM menu could not access the CAM.
> 
> changeset 7325b14e79e460fc (Monday evening):
> Unencrypted channels: ok:
> When I zap to an encrypted one, the drive hangs as shown below.
> Then I need to reboot the machine, because
>      modprobe -r mantis
> 
> could not really unload the module.


Can you please test again ?

Regards,
Manu

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] CAM of Mantis 2033 still not working

[Joakim Berglund]

Citerar Manu Abraham <abraham.manu@gmail.com>:

> Ruediger Dohmhardt wrote:
>> Manu Abraham schrieb:
>>> Ruediger Dohmhardt wrote:
>>>
...
>> changeset 7325b14e79e460fc (Monday evening):
>> Unencrypted channels: ok:
>> When I zap to an encrypted one, the drive hangs as shown below.
>> Then I need to reboot the machine, because
>>      modprobe -r mantis
>>
>> could not really unload the module.
>
>
> Can you please test again ?
>

Exactly the same problem on an 2040.
Checked before and after todays patch.

-----------------------------

[ 1320.629931] found a VP-2040 PCI DVB-C device on (01:09.0),
[ 1320.629932]     Mantis Rev 1 [153b:1178], irq: 17, latency: 64
[ 1320.629935]     memory: 0xfd0ff000, mmio: 0xffffc200006ba000
[ 1320.630623]         mantis_i2c_write: Address=[0x50] <W>[ 08 ]
[ 1320.630857]         mantis_i2c_read:  Address=[0x50] <R>[ 00 08 ca  
1c 72 73 ]
[ 1320.631702]     MAC Address=[00:08:ca:1c:72:73]
[ 1320.631731] mantis_alloc_buffers (0): DMA=0x1a20000  
cpu=0xffff810001a20000 size=65536
[ 1320.631737] mantis_alloc_buffers (0): RISC=0x2c8a0000  
cpu=0xffff81002c8a0000 size=1000
[ 1320.632651] DVB: registering new adapter (Mantis dvb adapter)
[ 1320.840918] mantis_frontend_init (0): Probing for CU1216 (DVB-C)
[ 1320.840925]         mantis_i2c_write: Address=[0x50] <W>[ ff ]
[ 1320.841068]         mantis_i2c_read:  Address=[0x50] <R>[ 3b ]
[ 1320.841212]         mantis_i2c_write: Address=[0x0c] <W>[ 00 33 ]
[ 1320.841495]         mantis_i2c_write: Address=[0x0c] <W>[ 1a ]
[ 1320.841637]         mantis_i2c_read:  Address=[0x0c] <R>[ 7d ]
[ 1320.841779] mantis_frontend_init (0): found Philips CU1216 DVB-C  
frontend (TDA10023) @ 0x0c
[ 1320.841782] mantis_frontend_init (0): Mantis DVB-C Philips CU1216  
frontend attach success
[ 1320.841786] DVB: registering frontend 0 (Philips TDA10023 DVB-C)...
[ 1320.841830] mantis_ca_init (0): Registering EN50221 device
[ 1320.842645] mantis_ca_init (0): Registered EN50221 device
[ 1320.842654] mantis_hif_init (0): Adapter(0) Initializing Mantis  
Host Interface
[ 1323.448980] dvb_ca adapter 0: DVB CAM detected and initialised successfully
[ 1344.901122]         mantis_i2c_write: Address=[0x0c] <W>[ 2a  
<3>mantis_ack_wait (0): Slave RACK Fail !
[ 1347.303023] DVB: TDA10023(0): tda10023_writereg, writereg error  
(reg == 0x2a, val == 0x02, ret == -121)
[ 1347.344417]         mantis_i2c_write: Address=[0x0c] <W>[ 2a  
<3>mantis_ack_wait (0): Slave RACK Fail !
[ 1349.745797] DVB: TDA10023(0): tda10023_writereg, writereg error  
(reg == 0x2a, val == 0x03, ret == -121)
[ 1349.787189]         mantis_i2c_write: Address=[0x0c] <W>[ 28  
<3>mantis_ack_wait (0): Slave RACK Fail !
[ 1352.188567] DVB: TDA10023(0): tda10023_writereg, writereg error  
(reg == 0x28, val == 0x07, ret == -121)
[ 1352.188572]         mantis_i2c_write: Address=[0x0c] <W>[ 29  
<3>mantis_ack_wait (0): Slave RACK Fail !
[ 1354.589796] DVB: TDA10023(0): tda10023_writereg, writereg error  
(reg == 0x29, val == 0xc0, ret == -121)
[ 1354.589800]         mantis_i2c_write: Address=[0x0c] <W>[ 00  
<3>mantis_ack_wait (0): Slave RACK Fail !
[ 1356.991028] DVB: TDA10023(0): tda10023_writereg, writereg error  
(reg == 0x00, val == 0x23, ret == -121)
[ 1356.991032]         mantis_i2c_write: Address=[0x0c] <W>[ 2a  
<3>mantis_ack_wait (0): Slave RACK Fail !
[ 1359.392261] DVB: TDA10023(0): tda10023_writereg, writereg error  
(reg == 0x2a, val == 0x08, ret == -121)
[ 1359.433657]         mantis_i2c_write: Address=[0x0c] <W>[ 1f  
<3>mantis_ack_wait (0): Slave RACK Fail !
[ 1361.835031] DVB: TDA10023(0): tda10023_writereg, writereg error  
(reg == 0x1f, val == 0x00, ret == -121)
[ 1361.876428]         mantis_i2c_write: Address=[0x0c] <W>[ e6  
<3>mantis_ack_wait (0): Slave RACK Fail !
[ 1364.277802] DVB: TDA10023: tda10023_readreg: readreg error (ret == -121)
[ 1364.277806]         mantis_i2c_write: Address=[0x0c] <W>[ e6  
<3>mantis_ack_wait (0): Slave RACK Fail !
[ 1366.679040] DVB: TDA10023(0): tda10023_writereg, writereg error  
(reg == 0xe6, val == 0x04, ret == -121)
[ 1366.679044]         mantis_i2c_write: Address=[0x0c] <W>[ 10


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] CAM of Mantis 2033 still not working

[Ruediger Dohmhardt]

Hi Manu,

the changeset 7344 3ae5e8d85a55 crashes after doing "modprobe mantis" 
and the computer hangs.
I could still log in from remote, doing an "init 6", but the machine did 
not reboot anymore. So I had to push the "Reset".

Below is /var/log/messges


May 23 23:10:51 linux-sh8m kernel: ACPI: PCI Interrupt 0000:02:01.0[A] 
-> GSI 21 (level, low) -> IRQ 21
May 23 23:10:51 linux-sh8m kernel: irq: 21, latency: 64
May 23 23:10:51 linux-sh8m kernel:  memory: 0xdfeff000, mmio: 
0xffffc200006f6000
May 23 23:10:51 linux-sh8m kernel: found a VP-2033 PCI DVB-C device on 
(02:01.0),
May 23 23:10:51 linux-sh8m kernel:     Mantis Rev 1 [1822:0008], irq: 
21, latency: 64
May 23 23:10:51 linux-sh8m kernel:     memory: 0xdfeff000, mmio: 
0xffffc200006f6000
May 23 23:10:51 linux-sh8m kernel:     MAC Address=[00:08:ca:19:e9:b6]
May 23 23:10:51 linux-sh8m kernel: mantis_alloc_buffers (0): 
DMA=0x69b90000 cpu=0xffff810069b90000 size=65536
May 23 23:10:51 linux-sh8m kernel: mantis_alloc_buffers (0): 
RISC=0x5afe0000 cpu=0xffff81005afe0000 size=1000
May 23 23:10:51 linux-sh8m kernel: DVB: registering new adapter (Mantis 
dvb adapter)
May 23 23:10:52 linux-sh8m kernel: mantis_frontend_init (0): Probing for 
CU1216 (DVB-C)
May 23 23:10:52 linux-sh8m kernel: TDA10021: i2c-addr = 0x0c, id = 0x7c
May 23 23:10:52 linux-sh8m kernel: mantis_frontend_init (0): found 
Philips CU1216 DVB-C frontend (TDA10021) @ 0x0c
May 23 23:10:52 linux-sh8m kernel: mantis_frontend_init (0): Mantis 
DVB-C Philips CU1216 frontend attach success
May 23 23:10:52 linux-sh8m kernel: DVB: registering frontend 0 (Philips 
TDA10021 DVB-C)...
May 23 23:10:52 linux-sh8m kernel: mantis_ca_init (0): Registering 
EN50221 device
May 23 23:10:52 linux-sh8m kernel: mantis_ca_init (0): Registered 
EN50221 device
May 23 23:10:52 linux-sh8m kernel: Unable to handle kernel NULL pointer 
dereference at 0000000000000000 RIP:
May 23 23:10:52 linux-sh8m kernel:  [<ffffffff80223de6>] 
__wake_up_common+0x26/0x70
May 23 23:10:52 linux-sh8m kernel: PGD 5c0b4067 PUD 5c1e6067 PMD 0
May 23 23:10:52 linux-sh8m kernel: Oops: 0000 [1] PREEMPT
May 23 23:10:52 linux-sh8m kernel: CPU 0
May 23 23:10:52 linux-sh8m kernel: Modules linked in: mantis ip6t_LOG 
nf_conntrack_ipv6 xt_pkttype ipt_LOG xt_limit
 kqemu(P) af_packet cpufreq_conservative cpufreq_ondemand 
cpufreq_performance cpufreq_powersave thermal fan evdev b
utton battery ac isofs nls_iso8859_1 nls_cp437 vfat fat nls_utf8 ntfs 
loop md_mod dm_mod ip6t_REJECT xt_tcpudp ipt_
REJECT xt_state iptable_mangle iptable_nat nf_nat iptable_filter 
ip6table_mangle nf_conntrack_ipv4 nf_conntrack nfn
etlink ip_tables ip6table_filter ip6_tables x_tables ipv6 vboxdrv rtc 
w83627hf hwmon_vid powernow_k8 freq_table pro
cessor lirc_mceusb2(F) usbhid lirc_dev lnbp21 mb86a16 nvidia(P) stb6100 
snd_ice1724 tda10021 snd_ice17xx_ak4xxx ide
_cd snd_ac97_codec ac97_bus cdrom snd_ak4114 ohci1394 tda10023 stb0899 
snd_pcm snd_timer snd_page_alloc snd_pt2258
snd_i2c snd_ak4xxx_adda snd_mpu401_uart snd_rawmidi snd_seq_device 
ieee1394 8139too snd soundcore stv0299 dvb_core
k8temp ehci_hcd ohci_hcd i2c_piix4 usbcore lp bttv ir_common 
compat_ioctl32 videodev v4l1_compat i2c_algo_bit v
May 23 23:10:52 linux-sh8m kernel: 4l2_common videobuf_dma_sg 
videobuf_core btcx_risc tveeprom i2c_core sg
May 23 23:10:52 linux-sh8m kernel: Pid: 4, comm: events/0 Tainted: 
PF      2.6.22.19 #6
May 23 23:10:52 linux-sh8m kernel: RIP: 0010:[<ffffffff80223de6>]  
[<ffffffff80223de6>] __wake_up_common+0x26/0x70
May 23 23:10:52 linux-sh8m kernel: RSP: 0000:ffff810037c8be50  EFLAGS: 
00010017
May 23 23:10:52 linux-sh8m kernel: RAX: 0000000000000000 RBX: 
0000000000000286 RCX: 0000000000000000
May 23 23:10:52 linux-sh8m kernel: RDX: 0000000000000001 RSI: 
0000000000000003 RDI: ffff810073af07d8
May 23 23:10:52 linux-sh8m kernel: RBP: ffff810037c8be80 R08: 
0000000000000000 R09: 00000000ffffffff
May 23 23:10:52 linux-sh8m kernel: R10: 0000000000000000 R11: 
0000000000000000 R12: ffff810037ff7fc0
May 23 23:10:52 linux-sh8m kernel: R13: ffff810073af07d8 R14: 
0000000000000001 R15: 0000000000000000
May 23 23:10:52 linux-sh8m kernel: FS:  00002ada904de6f0(0000) 
GS:ffffffff80604000(0000) knlGS:0000000000000000
May 23 23:10:52 linux-sh8m kernel: CS:  0010 DS: 0018 ES: 0018 CR0: 
000000008005003b
May 23 23:10:52 linux-sh8m kernel: CR2: 0000000000000000 CR3: 
0000000059e78000 CR4: 00000000000006e0
May 23 23:10:52 linux-sh8m kernel: Process events/0 (pid: 4, threadinfo 
ffff810037c8a000, task ffff810037c80040)
May 23 23:10:52 linux-sh8m kernel: Stack:  0000000300000000 
0000000000000286 ffff810037ff7fc0 ffffffff88db46e0
May 23 23:10:52 linux-sh8m kernel:  0000000000000000 0000000000000000 
ffff810037c8bea0 ffffffff80225865
May 23 23:10:52 linux-sh8m kernel:  ffff810073af07b0 ffff810073af07b8 
ffff810073af07b0 ffffffff8023aff7
May 23 23:10:52 linux-sh8m kernel: Call Trace:
May 23 23:10:52 linux-sh8m kernel:  [<ffffffff88db46e0>] 
:mantis:mantis_hifevm_work+0x0/0x300
May 23 23:10:52 linux-sh8m kernel:  [<ffffffff80225865>] __wake_up+0x25/0x60
May 23 23:10:52 linux-sh8m kernel:  [<ffffffff8023aff7>] 
run_workqueue+0xb7/0x1a0
May 23 23:10:52 linux-sh8m kernel:  [<ffffffff8023b6f0>] 
worker_thread+0x0/0x130
May 23 23:10:52 linux-sh8m kernel:  [<ffffffff8023b6f0>] 
worker_thread+0x0/0x130
May 23 23:10:52 linux-sh8m kernel:  [<ffffffff8023b7b3>] 
worker_thread+0xc3/0x130
May 23 23:10:52 linux-sh8m kernel:  [<ffffffff8023f150>] 
autoremove_wake_function+0x0/0x30
May 23 23:10:52 linux-sh8m kernel:  [<ffffffff8023b6f0>] 
worker_thread+0x0/0x130
May 23 23:10:52 linux-sh8m kernel:  [<ffffffff8023eceb>] kthread+0x4b/0x80
May 23 23:10:52 linux-sh8m kernel:  [<ffffffff8020a3c8>] child_rip+0xa/0x12
May 23 23:10:52 linux-sh8m kernel:  [<ffffffff8023eca0>] kthread+0x0/0x80
May 23 23:10:52 linux-sh8m kernel:  [<ffffffff8020a3be>] child_rip+0x0/0x12
May 23 23:10:52 linux-sh8m kernel:
May 23 23:10:52 linux-sh8m kernel:
May 23 23:10:52 linux-sh8m kernel: Code: 48 8b 18 75 08 eb 34 0f 1f 00 
48 89 d3 48 8d 78 e8 44 8b 60
May 23 23:10:52 linux-sh8m kernel: RIP  [<ffffffff80223de6>] 
__wake_up_common+0x26/0x70
May 23 23:10:52 linux-sh8m kernel:  RSP <ffff810037c8be50>
May 23 23:10:52 linux-sh8m kernel: CR2: 0000000000000000
May 23 23:10:52 linux-sh8m kernel: note: events/0[4] exited with 
preempt_count 1
May 23 23:10:52 linux-sh8m kernel: mantis_hif_init (0): Adapter(0) 
Initializing Mantis Host Interface




_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] CAM of Mantis 2033 still not working

[Ruediger Dohmhardt]

I just tried the changeset from today (7348 0b04be0c088a)

My machine still crashes, when inserting "mantis.ko"

The last running changeset (of course without CAM functionality) for me is:

7328 - d371e22416dd   from   21. Mai .08

Am I the only one, who uses 2.6.22.19  (64bit)?
Shall I switch the kernel version?
 
Ciao Ruediger D.



_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] CAM of Mantis 2033 still not working

[Bas v.d. Wiel]

Hi,
I'm running 2.6.24-16 64-bit, and I get a whole stream of errors 
(writing to registers fails) from the frontend whether or not the cam is 
inserted. I don't get any hard crashes anymore when I insert the CAM, 
but there's still my previous problem of not being able to find any 
signal/channels whatsoever using w_scan and a constant stream of 'tuning 
failure' from dvb-scan. Femon also shows everything as zero values, 
except the snr ration which is completely maxed out.

Bas

Ruediger Dohmhardt wrote:
> I just tried the changeset from today (7348 0b04be0c088a)
>
> My machine still crashes, when inserting "mantis.ko"
>
> The last running changeset (of course without CAM functionality) for me is:
>
> 7328 - d371e22416dd   from   21. Mai .08
>
> Am I the only one, who uses 2.6.22.19  (64bit)?
> Shall I switch the kernel version?
>  
> Ciao Ruediger D.
>
>
>
> _______________________________________________
> linux-dvb mailing list
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>
>   


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] CAM of Mantis 2033 still not working

[Manu Abraham]

Bas v.d. Wiel wrote:
> Hi,
> I'm running 2.6.24-16 64-bit, and I get a whole stream of errors 
> (writing to registers fails) from the frontend whether or not the cam is 
> inserted. I don't get any hard crashes anymore when I insert the CAM, 
> but there's still my previous problem of not being able to find any 
> signal/channels whatsoever using w_scan and a constant stream of 'tuning 
> failure' from dvb-scan. Femon also shows everything as zero values, 
> except the snr ration which is completely maxed out.
> 

Do you have the LOCK failure problem only when the CAM is inserted ?

Regards,
Manu

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] CAM of Mantis 2033 still not working

[Bas v.d. Wiel]

On Sat, 31 May 2008 00:10:22 +0400, Manu Abraham <abraham.manu@gmail.com>
wrote:
> Bas v.d. Wiel wrote:
>> Hi,
>> I'm running 2.6.24-16 64-bit, and I get a whole stream of errors
>> (writing to registers fails) from the frontend whether or not the cam is
>> inserted. I don't get any hard crashes anymore when I insert the CAM,
>> but there's still my previous problem of not being able to find any
>> signal/channels whatsoever using w_scan and a constant stream of 'tuning
>> failure' from dvb-scan. Femon also shows everything as zero values,
>> except the snr ration which is completely maxed out.
>>
> 
> Do you have the LOCK failure problem only when the CAM is inserted ?
> 
> Regards,
> Manu

Hi Manu,
The failures occur regardless of what I do. Whether or not the CAM is
inserted makes no difference at all. I tried it with different Linux
versions (Debian, Mythbuntu, Mythdora) in 32 bit and 64 bit versions. With
the current version of the driver my PC won't unload the mantis module
anymore and therefore refuses to even shut down properly. I'll post a dmesg
output later today. I've been tracking your driver for I guess a little
over a month now. The hard errors and crashes only started to occur after
functionality for the CAM was introduced. Before that the mantis module
loaded properly, it just didn't seem to do anything at all except just sit
there. Using Windows it works fine. A few days ago I posted all the
information I could find about my hardware (simply by looking at it) on the
list.

Regards,
Bas


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] CAM of Mantis 2033 still not working

[Ruediger Dohmhardt]

[-- Attachment #1: Type: text/html, Size: 9618 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] CAM of Mantis 2033 still not working

[Yves Gölz]

Hi,

I had same problem with kernel 2.6.24-19 on mythbuntu 8.04.
So I tried the trick and removed the CAM, and the patch 0b04be0c088a 
from Mantis works. But I have still the problem when the CAM is insert.


Regards
Yves

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb