Re: av7110 error reporting

2010-01-06 Thread Johan

Oliver Endriss wrote:

Hi,

Johan wrote:
  

I need some guidance on error messages..

T
[ 7678.312025] dvb-ttpci: StartHWFilter error  buf 0b07 0010 0803 b96a  
ret 0  handle 


These start as soon as I view or record a channel, and obviously fills 
up the log quickly.


I believe the code that generates these messages is at the bottom of 
this message (part of av7110.c). This code was introduced in 2005 to 
improve error reporting.



True.

  
Currently I run today's v4l-dvb (using a hg update), and kernel 
2.6.31-16. (Ubuntu), however the issue occurred in older combinations as 
well (over a year ago), so it is not introduced by the last kernels or 
DVB driverset.


The message seems to be triggered by the variable handle being larger 
then 32. On my system it always reports .



Handle ==  means that the av7110 was not able to create a new filter
entry. This will happen if there are already 32 active filters.

Does it happen for all channels, or only for a specific one?
If the latter is true: Which channel is causing the problem?
Does it have a large number of audio pids?

  
Am I looking at faulty hardware, or can I resolve this issue more 
elegant than just disabling the fault report?

(keep in mind that I do not have a programming/coding background)



You may disable the warning, but be warned that some parts of the data
will not be recorded due to missing filter entries...

Oliver

  
Think I know why this is happening. Using Mplayer I see that dvb-ttpci 
is used by about 4-5 processes. No errors.
Using mythtv 0.22 lsmod reports dvb-ttpci being used by 31 processes. 
Errors.


My idea is that mythtv's multirec feature is causing this, even though I 
have not enabled any virtual tuner.
My card, an unmodified Nexus-s (from 1998) may not support multirec due 
to its hardware design. (took me quite a bit of googling to make this 
assumption).


So, if my assumption is correct, the error is with Mythtv, where it is 
assumed that my card is multirec capable. (and how would Mythtv know, 
since the driver is the same ?)


I have now bought an HVR4000, so I have time to mod the Nexus. (and dig 
out my reading glasses to find the pins)


Johan



--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: av7110 error reporting

2010-01-05 Thread Oliver Endriss
Hi,

Johan wrote:
 I need some guidance on error messages..
 
 The machine receives these messages in the systemlog (dmesg)
 
 [ 7673.168026] dvb-ttpci: StartHWFilter error  buf 0b07 0010 07e9 b96a  
 ret 0  handle 
 [ 7674.192025] dvb-ttpci: StartHWFilter error  buf 0b07 0010 07ee b96a  
 ret 0  handle 
 [ 7675.224025] dvb-ttpci: StartHWFilter error  buf 0b07 0010 07f3 b96a  
 ret 0  handle 
 [ 7676.248128] dvb-ttpci: StartHWFilter error  buf 0b07 0010 07f9 b96a  
 ret 0  handle 
 [ 7677.280026] dvb-ttpci: StartHWFilter error  buf 0b07 0010 07fd b96a  
 ret 0  handle 
 [ 7678.312025] dvb-ttpci: StartHWFilter error  buf 0b07 0010 0803 b96a  
 ret 0  handle 
 
 These start as soon as I view or record a channel, and obviously fills 
 up the log quickly.
 
 I believe the code that generates these messages is at the bottom of 
 this message (part of av7110.c). This code was introduced in 2005 to 
 improve error reporting.

True.

 Currently I run today's v4l-dvb (using a hg update), and kernel 
 2.6.31-16. (Ubuntu), however the issue occurred in older combinations as 
 well (over a year ago), so it is not introduced by the last kernels or 
 DVB driverset.

 The message seems to be triggered by the variable handle being larger 
 then 32. On my system it always reports .

Handle ==  means that the av7110 was not able to create a new filter
entry. This will happen if there are already 32 active filters.

Does it happen for all channels, or only for a specific one?
If the latter is true: Which channel is causing the problem?
Does it have a large number of audio pids?

 Am I looking at faulty hardware, or can I resolve this issue more 
 elegant than just disabling the fault report?
 (keep in mind that I do not have a programming/coding background)

You may disable the warning, but be warned that some parts of the data
will not be recorded due to missing filter entries...

Oliver

-- 

VDR Remote Plugin 0.4.0: http://www.escape-edv.de/endriss/vdr/
4 MByte Mod: http://www.escape-edv.de/endriss/dvb-mem-mod/
Full-TS Mod: http://www.escape-edv.de/endriss/dvb-full-ts-mod/

--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


av7110 error reporting

2009-12-30 Thread Johan

I need some guidance on error messages..

The machine receives these messages in the systemlog (dmesg)

[ 7673.168026] dvb-ttpci: StartHWFilter error  buf 0b07 0010 07e9 b96a  
ret 0  handle 
[ 7674.192025] dvb-ttpci: StartHWFilter error  buf 0b07 0010 07ee b96a  
ret 0  handle 
[ 7675.224025] dvb-ttpci: StartHWFilter error  buf 0b07 0010 07f3 b96a  
ret 0  handle 
[ 7676.248128] dvb-ttpci: StartHWFilter error  buf 0b07 0010 07f9 b96a  
ret 0  handle 
[ 7677.280026] dvb-ttpci: StartHWFilter error  buf 0b07 0010 07fd b96a  
ret 0  handle 
[ 7678.312025] dvb-ttpci: StartHWFilter error  buf 0b07 0010 0803 b96a  
ret 0  handle 


These start as soon as I view or record a channel, and obviously fills 
up the log quickly.


I believe the code that generates these messages is at the bottom of 
this message (part of av7110.c). This code was introduced in 2005 to 
improve error reporting.


Currently I run today's v4l-dvb (using a hg update), and kernel 
2.6.31-16. (Ubuntu), however the issue occurred in older combinations as 
well (over a year ago), so it is not introduced by the last kernels or 
DVB driverset.


The message seems to be triggered by the variable handle being larger 
then 32. On my system it always reports .


Am I looking at faulty hardware, or can I resolve this issue more 
elegant than just disabling the fault report?

(keep in mind that I do not have a programming/coding background)



Johan



start of code---
static int StartHWFilter(struct dvb_demux_filter *dvbdmxfilter)
{
   struct dvb_demux_feed *dvbdmxfeed = dvbdmxfilter-feed;
   struct av7110 *av7110 = dvbdmxfeed-demux-priv;
   u16 buf[20];
   int ret, i;
   u16 handle;
//u16 mode = 0x0320;
   u16 mode = 0xb96a;

   dprintk(4, %p\n, av7110);

   if (av7110-full_ts)
   return 0;

   if (dvbdmxfilter-type == DMX_TYPE_SEC) {
   if (hw_sections) {
   buf[4] = (dvbdmxfilter-filter.filter_value[0]  8) |
   dvbdmxfilter-maskandmode[0];
   for (i = 3; i  18; i++)
   buf[i + 4 - 2] =
   (dvbdmxfilter-filter.filter_value[i]  8) |
   dvbdmxfilter-maskandmode[i];
   mode = 4;
   }
   } else if ((dvbdmxfeed-ts_type  TS_PACKET) 
  !(dvbdmxfeed-ts_type  TS_PAYLOAD_ONLY)) {
   av7110_p2t_init(av7110-p2t_filter[dvbdmxfilter-index], 
dvbdmxfeed);

   }

   buf[0] = (COMTYPE_PID_FILTER  8) + AddPIDFilter;
   buf[1] = 16;
   buf[2] = dvbdmxfeed-pid;
   buf[3] = mode;

   ret = av7110_fw_request(av7110, buf, 20, handle, 1);
   if (ret != 0 || handle = 32) {
   printk(dvb-ttpci: %s error  buf %04x %04x %04x %04x  
   ret %d  handle %04x\n,
   __func__, buf[0], buf[1], buf[2], buf[3],
   ret, handle);
   dvbdmxfilter-hw_handle = 0x;
   if (!ret)
   ret = -1;
   return ret;
   }

   av7110-handle2filter[handle] = dvbdmxfilter;
   dvbdmxfilter-hw_handle = handle;

   return ret;
}

--end of code
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html