Opened 7 years ago

Closed 7 months ago

#12234 closed Bug Report - Hang/Deadlock (Unverified)

often fails to capture video, DVBSky S950C, file too small, offset>181

Reported by: Peter.Bienstman@… Owned by:
Priority: minor Milestone: unknown
Component: MythTV - General Version: 0.27-fixes
Severity: high Keywords:
Cc: Ticket locked: no


Often I fail to get live video or a successful recording using mythtv. However, when I start kaffeine afterwards and tune to that channel, I get video without problems. Subsequently starting mythtv again allows me to play that channel, as well as switch to different channels, so I assume mythtv does not correctly initialize my tuner.

I run mythbuntu 14.04.1 and have a DVBSky S950C PCIe, using the latest firmware and 140619 driver provided by DVBSky. I have a XBMC Windows frontend, although for the failed recording this should be irrelevant.

dmesg | grep dvb

[ 11.000016] cx23885_dvb_register() allocating 1 frontend(s) [ 11.000019] cx23885[0]: cx23885 based dvb card [ 11.296398] m88ds3103_load_firmware: Waiting for firmware upload (dvb-fe-ds3103.fw)... [ 12.532031] Registered IR keymap rc-dvbsky [ 20.009008] dvb_ca adapter 0: DVB CAM detected and initialised successfully

There are some errors being reported in dmesg ( like [128.828029] cx23885_wakeup: 17 buffers handled (should be 1) ) but they are probably red herrings since they also occur after a cold boot and and successful video playback.

I have tried turning off EIT collection. This reduces the frequency of the problem, but does not eliminate it.

The attached log file (-v channel, dvbcam, eit) seems to indicate that tuning is successful, but still a videostream cannot be started.

Attachments (1)

mythbackend.log (56.6 KB) - added by Peter.Bienstman@… 7 years ago.

Download all attachments as: .zip

Change History (2)

Changed 7 years ago by Peter.Bienstman@…

Attachment: mythbackend.log added

comment:1 Changed 7 months ago by Stuart Auchterlonie

Resolution: Unverified
Status: newclosed

Closing all old tickets in trac.

If your issue still persists, please open an issue in Github

and reference the existing trac ticket.

Note: See TracTickets for help on using tickets.