Opened 9 years ago

Closed 9 years ago

#10050 closed Bug Report - Hang/Deadlock (Invalid)

Starting mythbackend doesn't initiliaze DVB cards correctly until mythbackend is restarted

Reported by: t-p@… Owned by:
Priority: minor Milestone: unknown
Component: MythTV - General Version: Master Head
Severity: medium Keywords:
Cc: Ticket locked: yes


I've noticed when using v0.25pre-3329-gbececaa-dirty that sometimes (maybe 75%) after rebooting my HTPC mythbackend cannot initialize DVB cards correctly until I restart mythbackend. Attached logs show "Opening DVB frontend device failed. eno: Bad address (14)" for both of my DVB cards. My setup used to work ok with approx month old trunk build until last weekend when I updated the system (same OS Fedora 13 with 2.6.34-9 kernel used with both builds).

However DVB cards are initialized correctly in the bootup because I can watch DVB channel using mplayer even though mythtv gives this error.

Attachments (2)

mythbackend.log (19.0 KB) - added by anonymous 9 years ago.
mythbackend log
mythbackend.txt (678 bytes) - added by anonymous 9 years ago.
mythbackend --version info

Download all attachments as: .zip

Change History (3)

Changed 9 years ago by anonymous

Attachment: mythbackend.log added

mythbackend log

Changed 9 years ago by anonymous

Attachment: mythbackend.txt added

mythbackend --version info

comment:1 Changed 9 years ago by robertm

Resolution: Invalid
Status: newclosed
Ticket locked: set

This isn't a mythbackend problem, it's a "your init script is starting the backend before it has initialized the DVB devices" problem. The devices *are* initialized at boot properly, but by the time you get to being able to use mplayer, your distro has long since started Mythbackend too early, a condition from which myth is not designed to recover.

Please start on the mythtv-users mailing list to get assistance in changing the order in which your distro starts services.

Note: See TracTickets for help on using tickets.