dvb-t tune failure crashes backend

Bug #495429 reported by Kev Walke on 2009-12-11
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MythTV
Won't Fix
Unknown
Mythbuntu
Won't Fix
High
Unassigned

Bug Description

My backend failed yesterday after the dvb-t tuner failed to tune according to the logs. I attach a backtrace as I had gdb attached to get information for an entirely separate bug

Kev Walke (kelvinelk) wrote :
MarcRandolph (mrand) wrote :

Howdy, and thank you for helping to improve Mythbuntu by submitting this ticket. Could you please confirm which version of Ubuntu / Mythbuntu, and which version of MythTV you are running (by executing mythbackend --version)?

Changed in mythbuntu:
importance: Undecided → High
status: New → Incomplete
Kev Walke (kelvinelk) wrote :

of course:) it is jaunty using 0.22 auto-builds from mythbuntu:

MythTV Version : 22957
MythTV Branch : branches/release-0-22-fixes
Network Protocol : 50
Library API : 0.22.20091023-1
QT Version : 4.5.0
Options compiled in:
 linux profile using_oss using_alsa using_pulse using_jack using_backend using_dvb using_firewire using_frontend using_glx_proc_addr_arb using_hdhomerun using_hdpvr using_iptv using_ivtv using_joystick_menu using_libfftw3 using_lirc using_mheg using_opengl_video using_opengl_vsync using_qtwebkit using_v4l using_x11 using_xrandr using_xv using_xvmc using_xvmc_vld using_xvmcw using_bindings_perl using_bindings_python using_opengl using_vdpau using_ffmpeg_threads using_libavc_5_3 using_live using_mheg

MarcRandolph (mrand) wrote :

Thank you for the quick response. I've forwarded this issue upstream - I hope that your backtrace info will help them get to the bottom of the issue. In the mean time, if you could attach your backend log, or at least, the part of it around this time frame, they may find that helpeful as well.

Changed in mythbuntu:
status: Incomplete → Triaged
Changed in mythtv:
status: Unknown → New
Kev Walke (kelvinelk) wrote :

no problem. mythbackend log attached.

Thank you. The program should never crash, so I consider the
backtrace and crash report valid. However, does the backtrace that
you captured result after the following log? If so, you may be able to
fix it by reconfiguring your capture card:

2009-12-10 16:01:28.607 DVBChan(25:/dev/dvb/adapter0/frontend0)
Warning: Opening DVB frontend device failed.
   eno: Device or resource busy (16)
2009-12-10 16:01:28.659 DVBChan(25:/dev/dvb/adapter0/frontend0)
Warning: Opening DVB frontend device failed.
   eno: Device or resource busy (16)
2009-12-10 16:01:28.711 DVBChan(25:/dev/dvb/adapter0/frontend0)
Warning: Opening DVB frontend device failed.
   eno: Device or resource busy (16)
2009-12-10 16:01:28.713 DVBChan(25:/dev/dvb/adapter0/frontend0) Error:
Failed to open DVB frontend device due to fatal error or too many
attempts.
2009-12-10 16:01:28.714 MythBackend, Error: No valid capture cards are
defined in the database.
   Perhaps you should re-read the installation instructions?
2009-12-10 16:01:28.719 New DB connection, total: 3
2009-12-10 16:01:28.731 Connected to database 'mythconverg' at host: mythtv
2009-12-10 16:01:28.748 MediaServer::HttpServer Create Error
2009-12-10 16:01:28.757 Enabled verbose msgs: important general
2009-12-10 16:01:28.764 AutoExpire: CalcParams(): Max required Free
Space: 0.0 GB w/freq: 15 min
2009-12-10 16:01:28.769 Failed to bind port 6543. Exiting.
2009-12-10 16:01:28.771 Backend exiting, MainServer initialization error.
Error in my_thread_global_end(): 1 threads didn't exit

Mario Limonciello (superm1) wrote :

That sounds like two backends running at the same time

On Fri, Dec 11, 2009 at 09:28, MarcRandolph <email address hidden> wrote:

> Thank you. The program should never crash, so I consider the
> backtrace and crash report valid. However, does the backtrace that
> you captured result after the following log? If so, you may be able to
> fix it by reconfiguring your capture card:
>
>
> 2009-12-10 16:01:28.607 DVBChan(25:/dev/dvb/adapter0/frontend0)
> Warning: Opening DVB frontend device failed.
> eno: Device or resource busy (16)
> 2009-12-10 16:01:28.659 DVBChan(25:/dev/dvb/adapter0/frontend0)
> Warning: Opening DVB frontend device failed.
> eno: Device or resource busy (16)
> 2009-12-10 16:01:28.711 DVBChan(25:/dev/dvb/adapter0/frontend0)
> Warning: Opening DVB frontend device failed.
> eno: Device or resource busy (16)
> 2009-12-10 16:01:28.713 DVBChan(25:/dev/dvb/adapter0/frontend0) Error:
> Failed to open DVB frontend device due to fatal error or too many
> attempts.
> 2009-12-10 16:01:28.714 MythBackend, Error: No valid capture cards are
> defined in the database.
> Perhaps you should re-read the installation
> instructions?
> 2009-12-10 16:01:28.719 New DB connection, total: 3
> 2009-12-10 16:01:28.731 Connected to database 'mythconverg' at host: mythtv
> 2009-12-10 16:01:28.748 MediaServer::HttpServer Create Error
> 2009-12-10 16:01:28.757 Enabled verbose msgs: important general
> 2009-12-10 16:01:28.764 AutoExpire: CalcParams(): Max required Free
> Space: 0.0 GB w/freq: 15 min
> 2009-12-10 16:01:28.769 Failed to bind port 6543. Exiting.
> 2009-12-10 16:01:28.771 Backend exiting, MainServer initialization error.
> Error in my_thread_global_end(): 1 threads didn't exit
>
> --
> dvb-t tune failure crashes backend
> https://bugs.launchpad.net/bugs/495429
> You received this bug notification because you are a member of Mythbuntu
> Developers, which is subscribed to Mythbuntu.
>

--
Mario Limonciello
<email address hidden>
Sent from Manchester, NH, United States

Kev Walke (kelvinelk) wrote :

Yes it was after. I don't understand how reconfiguring the capture card could clear things here? I haven't touched mythtv-setup in months.

Changed in mythtv:
status: New → Won't Fix
MarcRandolph (mrand) wrote :

Upstream has determined that this is either no longer occuring, or is so unlikely to occur that the effort to fix the bug is not worth it.

Changed in mythbuntu:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.