[VU+ Duo2] Not switching channel for recording

[lincsat]

I think I've found another bug. On a Duo2 with 2x Sat and 1x Cable tuner. Usually, when watching cable and a recording on a different cable channel is due to start, the box changes channel to record, this is the expected behaviour.

If there is a recording in progress from one of the Sat tuners at the time, then the channel doesn't change, recording doesn't start and the spinner displays making the box unresponsive needing a hard reboot

I've not tried with a previous ViX, only with Blackhole, which does work as expected, so unlikely to be a Vu+ driver issue

 

[timofee]

Duo2 with Apollo image works ok.

Suggest you try the latest Apollo image; if you still get same problem you know your problem is not image related.

 

[abu baniaz]

@Lincsat, Please attach debug logs next time it happens.

 

[lincsat]

It has happened again tonight when trying to record "Critical", I've attached the full log. The relevant section is at the end of the full log and highlighted here:

[TIMER] activating state 1
[TIMER] Found enough free space to record
[TIMER] Filename calculated as: '/media/hdd/movie/20150512 2058 -  - Critical'
recording service: <enigma.eServiceReference; proxy of <Swig Object of type 'eServiceReference *' at 0x5ddd0170> >
<192162.757705> [eDVBResourceManager] allocate channel.. 001a:f020
<192162.759120> [eDVBResourceManager] available channel.. 0019:f020
<192162.760419> [eDVBResourceManager] available channel.. 0802:0002
<192162.761770> allocate Channel: res -6
<192162.763117> eDVBServiceRecord: RECORD service event 0
[TIMER] 'prepare' failed: error -6
[TIMER] backoff: retry in 5 seconds
<192162.775614> eDVBServiceRecord: stop recording!
<192162.776868> eDVBServiceRecord: (was not recording)
[Trashcan] Recording in progress 1
[TIMER] prepare failed
[TIMER] zap without asking
[SKIN] processing screen MessageBoxSimple:
[SKIN] processing screen MessageBoxSimple_summary:
[TIMER] ok, zapped away
<192166.298613> [gRC] main thread is non-idle! display spinner!

View attachment Enigma2-10-05-2015_15-41-23.log

 

[rossi2000]

[TIMER] Filename calculated as: '/media/hdd/movie/20150512 2058 - - Critical'
timer was created via AUTOTIMER
check the auto timer channel
make sure it is still valid
it could have moved REF’s
since that AT was created

 

[lincsat]

All looks OK, showing as Sky1 HD. The other recording was set with Autotimer as well. It has also crashed when a manually set timer activated, didn't have the logging setup for that though.

 

[abu baniaz]

What are your sat tuners configured as please? Can you also post the section of settings file taht relates to tunerr config.

Please double check if this is correct way to reproduce:
Start recording on satellite.
Schedule recording on cable a few minutes ahead. (Does not matter if autotimer or manual)
Watch another cable channel. Should lock up at recording time.

Q. Cable channels being watched/recorded. Were they on same TP?

 

[judge]

All looks OK, showing as Sky1 HD.

Sky1 HD doesn't currently work on any E2 box. [EDIT] maybe it does on cable?

The other recording was set with Autotimer as well. It has also crashed when a manually set timer activated, didn't have the logging setup for that though.

Shouldn't cause a crash though. Crash logs don't need to be enabled by default, debug logs do. Both handy in tracking down issues.

 

[abu baniaz]

Currently testing this on my TM 3T Combo. 2 tuners as single/28.2, third tuner in cable mode.

Recording BBC 1 HD on sat. 30 minute manual recording.
Scheduled a recording on BBC3 cable at 00:30.
Watching BBC 2 on cable. It is on a different TP, so can't record in the background.

 

[abu baniaz]

At 00:27, channel zapped to enable recording. I'll try on the LX3.

 

[abu baniaz]

Repeated on LX3, slightly different tuner config. Nonetheless, a recording was active on satellite. Scheduled a recording from a bouquet created by Lraizer's cable plugin this time whilst watching another cable channel. Still fine.

I note that there is another thread with timer related issue for a Duo2.