Ticket #10884 (new Bug Report - General)
Opened 11 months ago
Last modified 7 months ago
LiveTV with HD Homerun Prime fails with max buffering
| Reported by: | monkeypet@… | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | unknown |
| Component: | MythTV - General | Version: | 0.25-fixes |
| Severity: | medium | Keywords: | |
| Cc: | Ticket locked: | no |
Description
My setup is a backend, fc17 with 0.25/fixes with HDHR Prime (3 tuners). Remote Frontend is ubuntu 12.04, running v0.25.1-56-g11d7795 on an intel mac mini.
When I start LiveTV, it stops after a few mins ranging from 5 mins to 15 mins, I get the message "max buffering...", mythfrontend usually crashes afterwards or is stuck. Then I have to restart the frontend. This occurs on any channel.
I have attached a log from the backend and frontend. Issue occurs at 2012-07-05 14:03 in the logfiles.
Please let me know what else I can provide or try. I am willing to help out.
Attachments
Change History
Changed 11 months ago by monkeypet@…
- Attachment mythbackend.20120704182810.7624.log.bz2 added
Changed 11 months ago by monkeypet@…
- Attachment mythfrontend.20120705140228.5946.log.1.bz2 added
Mythfrontend Logs.
comment:1 Changed 11 months ago by Monkey Pet <monkeypet@…>
Exact Error message "Video Frame Buffering Failed too many times".
comment:1 Changed 11 months ago by Monkey Pet <monkeypet@…>
Exact Error message "Video Frame Buffering Failed too many times".
Changed 11 months ago by Monkey Pet <monkeypet@…>
- Attachment mythfrontend.20120705183103.6527.log.bz2 added
Another frontend log. This one I tuned to one channel until the error occurred.
Changed 11 months ago by Monkey Pet <monkeypet@…>
- Attachment mythtv_backtrace.txt added
mythfrontend segfaults, version v0.25.1-56-g11d7795
comment:2 Changed 7 months ago by Monkey Pet <monkeypet@…>
This was caused by the HDHR Prime dropping off the network for a few secs during recordings. The workaround is to keep on pinging the HDHR Prime. I have a bug opened with silicon dust. Still mythfrontend should never segfault, but neither should the HDHR drop off the network. Also see bug 10414 where I found the workaround of pinging the HDHR Prime.
Backend Logs.