Mailing List archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[linux-dvb] Re: Replay problems



Klaus Schmidinger wrote:
....
> > 1.  cDvbApi::SetPid issues an error message for
> >     the DMX_SET_PES_FILTER ioctl:
> >     Jun 17 16:39:20 vdr vdr[18454]: ERROR (dvbapi.c,2052): Device or resource busy
> 
> See my other posting on how to avoid this.

I do not have teletext PIDs in my channels.conf.
I will still make the change you suggested in the other
posting and see what happens.


> > 2.  During every recording I am getting "read incomplete section" errors.
> 
> Strange... I don't get these here (when recording). I only get them when the EPG
> scanner is active and the infamous "outcommand error 1" occurs.

I double-checked. My EPG-scanner is definitely inactive.
As you see from the log I posted, vdr only switched to the "CurrentChannel"
on startup and to the recording channel when starting the recording.


> > 4.  The driver tries to vfree a bad address.
> 
> I've also had these lately. Looks like this happens with encrypted channels
> only. 

I do not have a CAM and I do not have any encrypted channels in 
my channels.conf. Still I have 172 of these messages in my log
between midnight and now. 30 different addresses are listed in
these messages:

# fgrep 'vdr kernel: Trying to vfree() bad address' messages| sort -u -t'(' +2.0
Jun 17 10:10:50 vdr kernel: Trying to vfree() bad address (0000000f)
Jun 17 09:11:17 vdr kernel: Trying to vfree() bad address (00000038)
Jun 17 09:59:03 vdr kernel: Trying to vfree() bad address (00000210)
Jun 17 15:37:37 vdr kernel: Trying to vfree() bad address (00003a6e)
Jun 17 09:21:36 vdr kernel: Trying to vfree() bad address (0000c03f)
Jun 17 09:37:09 vdr kernel: Trying to vfree() bad address (00400008)
Jun 17 17:02:59 vdr kernel: Trying to vfree() bad address (00fb14fc)
Jun 17 10:17:24 vdr kernel: Trying to vfree() bad address (01b13cb0)
Jun 17 15:24:58 vdr kernel: Trying to vfree() bad address (01d1ff28)
Jun 17 09:26:48 vdr kernel: Trying to vfree() bad address (028890b5)
Jun 17 16:28:09 vdr kernel: Trying to vfree() bad address (02d0002c)
Jun 17 09:43:28 vdr kernel: Trying to vfree() bad address (03900020)
Jun 17 10:03:49 vdr kernel: Trying to vfree() bad address (049a0198)
Jun 17 10:16:13 vdr kernel: Trying to vfree() bad address (06068fff)
Jun 17 09:34:28 vdr kernel: Trying to vfree() bad address (085c431c)
Jun 17 16:32:36 vdr kernel: Trying to vfree() bad address (09688849)
Jun 17 10:02:36 vdr kernel: Trying to vfree() bad address (15eaa312)
Jun 17 14:10:33 vdr kernel: Trying to vfree() bad address (49680868)
Jun 17 15:10:51 vdr kernel: Trying to vfree() bad address (496a1249)
Jun 17 16:30:17 vdr kernel: Trying to vfree() bad address (5c468bf2)
Jun 17 15:04:58 vdr kernel: Trying to vfree() bad address (70478167)
Jun 17 00:27:11 vdr kernel: Trying to vfree() bad address (780000c0)
Jun 17 10:19:04 vdr kernel: Trying to vfree() bad address (8ae100c0)
Jun 17 09:43:28 vdr kernel: Trying to vfree() bad address (a2cfa001)
Jun 17 09:18:24 vdr kernel: Trying to vfree() bad address (d568f7b5)
Jun 17 15:28:40 vdr kernel: Trying to vfree() bad address (ee00866e)
Jun 17 09:16:43 vdr kernel: Trying to vfree() bad address (f0bc01b0)
Jun 17 15:09:16 vdr kernel: Trying to vfree() bad address (f0bc3f1e)
Jun 17 08:57:13 vdr kernel: Trying to vfree() bad address (f456c48f)
Jun 17 11:56:35 vdr kernel: Trying to vfree() bad address (fff7381c)

Ralph, is this harmless or does it indicate a driver bug?


Carsten.


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



Home | Main Index | Thread Index