[linux-dvb] Re: budget-ci CI interface testing

["Bernhard C. Schrenk" <tv@clemy.org>]

> > 2) If I unload the driver and load it again (tried budget-ci only and
also
> > all modules down to dvb-core). Initialisation of the CAM does not work
any
> > more. I can not retry the whole test cycle yet, because I can not reboot
> > the machine (due to another bug) remotely.
>
> I can't replicate this on my CAM. Does it do the same thing if you don't
have
> your subscription card in it?

I will test it as soon as I get physical access to the machine (on the
weekend).
I am working around this problem at the moment by disabling the error
handling in dvb_ca_en50221_set_configoption.

I have started testing with cam_set from libdvb.
I needed to set the readers member of dvbdev_ca to 1 in dvb_ca_en50221.c,
because cam_set reported device already in use.

The output of cam_set (with debug enabled):
Found 1CAM(s)
Resetting slot 0...ok.
Using /dev/dvb/adapter0/ca0
Found 1 slots
Module ready in slot 0
Creating connection: slot 0, tcid 1
--> 00 01 82 01 01
<-- 00 00 83 01 01 80 02
    .  .  .  .  .  .  .
ERROR: CAM: Read failed: slot 0, tcid 1

CAM: retrying to establish connection
ERROR: CAM: Read failed: slot 0, tcid 1

CAM: retrying to establish connection
ERROR: CAM: Read failed: slot 0, tcid 1

CAM: retrying to establish connection
ERROR: CAM: Read failed: slot 0, tcid 1

CAM: retrying to establish connection

---

The corresponding output of the kernel:
<deleted the log of the second initialisation initiated by cam_set>
Apr  9 12:51:27 videobox kernel: CAM supports FR IRQ
Apr  9 12:51:27 videobox kernel: dvb_ca: DVB CAM detected and initialised
successfully
Apr  9 12:51:27 videobox kernel: dvb_ca_en50221_io_do_ioctl
Apr  9 12:51:27 videobox kernel: dvb_ca_en50221_io_write
Apr  9 12:51:27 videobox kernel: dvb_ca_en50221_write_data
Apr  9 12:51:27 videobox kernel: dvb_ca_en50221_io_poll
Apr  9 12:51:27 videobox kernel: FR/DA IRQ slot:0
Apr  9 12:51:27 videobox kernel: dvb_ca_en50221_io_poll
Apr  9 12:51:27 videobox kernel: dvb_ca_en50221_read_data
Apr  9 12:51:27 videobox kernel: dvb_ca_en50221_read_data
Apr  9 12:51:27 videobox kernel: dvb_ca_en50221_io_poll
Apr  9 12:51:27 videobox kernel: dvb_ca_en50221_io_read
Apr  9 12:51:27 videobox kernel: dvb_ca_en50221_read_data
Apr  9 12:51:39 videobox last message repeated 1130 times
Apr  9 12:51:39 videobox kernel: dvb_ca_en50221_io_release

---

I do not know the protocol well enough, to see the problem, but I think it
has something todo with a tcid comparison in cam_set which is not fulfilled.
The second possible problem I see is that the dvb_ca_en50221_read_data
function is called 1130 times in 12 seconds, but no data is delivered to
cam_set after the 7 bytes.

I have also seen one time, that every io_poll returned with a time out, also
the one after the FR IRQ. And so cam_set never called read and returned
errors only. But I have no log of this and I have no access to the machine
anymore, because it crashed.

I started cam_set, killed it with CTRL+C somewhere between write and read
call and started it again. After this procedure the connection was lost.

I hope this will help a little bit, I will continue my tests after I have
reseted the machine today evening or tomorrow.

Regards,
Bernhard



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