Opened 15 years ago
Closed 15 years ago
#6727 closed defect (wontfix)
MythTV randomly fails to record
| Reported by: | Owned by: | Shane Shrybman | |
|---|---|---|---|
| Priority: | major | Milestone: | 0.22 |
| Component: | MythTV - Recording | Version: | 0.21-fixes |
| Severity: | medium | Keywords: | random recording fail tuning |
| Cc: | Ticket locked: | no |
Description
MythTV randomly fails to record shows.
What I've done/tried:
- Made sure I have plenty of diskspace left, and propper access rights to the recordingfolder
- Made sure the channel is "tune-able" - by tuning into the channel using LiveTV.
- Tried updating my DVB-C drivers
- Updated MythTV to the latest -fixes release (20887)
My setup:
Two TT-1501C DVB-C Cards.
Raid'ed storage folder
MythTV 0.21-fixes rev. 20887
I could expect my QAM of being a tad to slow to decode - right after the tuning... But I havent been able to verify that (And honestly, I don't know how to verify it!)
As a workaround I guess MythTV could retry to start the recording, if it for some reason fails.
I see MythTV KNOWS the recording went wrong, since it's saying: "Deleting stale pending recording"
I've attached a log where it failed to record the show "Top Gear"
Attachments (5)
Change History (12)
Changed 15 years ago by
| Attachment: | mythtv-fail-to-record.txt added |
|---|
comment:1 Changed 15 years ago by
| Milestone: | 0.21.1 → unknown |
|---|
Changed 15 years ago by
| Attachment: | mytht-fail-record-docter-who.txt added |
|---|
MythTV only recording two minutes of a show, then aborting.
comment:2 Changed 15 years ago by
This time MythTV just recorded two minutes of the show, and then aborted :(
(attachment: mytht-fail-record-docter-who.txt)
comment:3 Changed 15 years ago by
| Milestone: | unknown → 0.22 |
|---|---|
| Status: | new → infoneeded_new |
Have you recently updated the kernel? Specifically which kernel are you currently using?
A number of us have seen a similar bug, but until now we haven't be able to rule out a recent bug in 0.22 because we'd had no 0.21 reports. However every single report of that issue seems to follow a kernel upgrade.
comment:4 Changed 15 years ago by
I haven't upgraded my kernel since April 2009. I'm still using 2.6.28 - with a V4L snapshot from Jul 13 2009(I have tried upgrading/downgrading the V4L snapshot - but that didn't make any difference).
Changed 15 years ago by
| Attachment: | mythtv-fail.record-ncis.txt added |
|---|
Yeat another failed recording. This time the show "Navy CIS"
Changed 15 years ago by
| Attachment: | mythtv-fail-record-top-gear.txt added |
|---|
Yeat another failed recording. This time the show "Top Gear"
comment:5 Changed 15 years ago by
| Component: | MythTV - General → MythTV - Recording |
|---|---|
| Owner: | changed from Isaac Richards to danielk |
| Status: | infoneeded_new → new |
IMHO this is a driver problem, the use of updated snapshots bring it inline with what's in the 2.6.29 kernel where this error first appeared. The logs from 0.21 don't say anything useful, trunk logs are better since we actually started looking for the errors. We may work around this in 0.22, but whatever fixes we come up with are unlikely to be backported to 0.21.
comment:6 Changed 15 years ago by
| Owner: | changed from danielk to Shane Shrybman |
|---|---|
| Status: | new → assigned |
comment:7 Changed 15 years ago by
| Resolution: | → wontfix |
|---|---|
| Status: | assigned → closed |
Thanks for your report.
Unfortunately the 0.21-fixes branch is transitioning into the unsupported state as we try and make a push for the 0.22 release.
Most active developers have upgraded to what will become the 0.22 release and are not actively working on 0.21 anymore.
So I am going to close this ticket for now, but please do re-open if you experience the same issues with 0.22.
log file of MythTV failing to record a show