[HANG] Deadlock in MBE with 24-fixes

[Dave Badia <dbadia@…>]

Upgraded to the lastest 24-fixes a few weeks ago and have had some deadlocks on the master BE since. Been happening quite often lately, twice in 2 days. My MBE runs on it's own server, I have 2 other machines with slave BEs and FEs on them.

Haven't been able to determine what actions (recordings start/stop etc) are happening when it occurs as I'm always at work. Backtraces from the last 2 deadlocks are attached.

Only recent upgrade I can think of is moving to an SSD for the MBE OS and myth DB. Running on gentoo.

MBE version info: MythTV Version : v0.24.1-12-ge097ed1-dirty MythTV Branch : 241f Network Protocol : 63 Library API : 0.24.20110505-1 QT Version : 4.6.2 Options compiled in:

linux profile using_alsa using_oss using_backend using_bindings_perl using_bindings_python using_dvb using_frontend using_hdhomerun using_hdpvr using_iptv using_ivtv using_joystick_menu using_lirc using_mheg using_opengl_video using_opengl_vsync using_qtdbus using_qtwebkit using_v4l using_x11 using_xrandr using_xv using_bindings_perl using_bindings_python using_mythtranscode using_opengl using_vdpau using_ffmpeg_threads using_live using_mheg

[Dave Badia <dbadia@…>]

Had 2 more deadlocks occur in the past 2 days. One of them occurred after my hdpvr recording failed on a slave backend. Backtrace and mysql process list attached

[Dave Badia <dbadia@…>]

This hasn't occurred in the past few months. Think it was fixed by one of the deadlock patches in 24 fixes.

[sphery]

Closing at reporter's request. Thanks for reporting back.

[stuartm]

Milestone 0.24.2 deleted