[mythtv-commits] Ticket #9885: Deadlock on slave backend disconnect
MythTV
noreply at mythtv.org
Thu Jun 30 10:24:16 UTC 2011
#9885: Deadlock on slave backend disconnect
-------------------------------------+-------------------------------------
Reporter: Ian Dall <ian@…> | Type: Bug Report -
Status: new | General
Milestone: unknown | Priority: major
Version: Trunk Head | Component: MythTV - General
Keywords: | Severity: medium
| Ticket locked: 0
-------------------------------------+-------------------------------------
I have a setup with a master BE, 2 slave BEs and 1 - 3 frontends. I am
running code compiled from git (v0.25pre-2145-gf199a84-dirty).
The behaviour is that nothing works and one slave is dead and the master
backend is deadlocked. FE's don't work and accessing the status port with
a browser times-out.
The slave death is accompanied by kernel syslog messages like:
kernel: [371375.689820] mythbackend: page allocation failure. order:0,
mode:0x20
Maybe the slave death is due to a kernel bug, BUT the master should not
deadlock!
The attached backtrace shows that master Thread 16 is trying, in
SlaveDisconnected to get a shedlock, when shedlock is already held by
Scheduler::run further up the stack.
I saw exactly the same problem with an older version: 0.24-7.fc14
(464fa28373) but went to git head in the hope that this had been fixed :-(
I notice other deadlock tickets (esp #9745), but none seem to have quite
the same description, and the version I am running has the #9745 fix
included.
--
Ticket URL: <http://code.mythtv.org/trac/ticket/9885>
MythTV <http://code.mythtv.org/trac>
MythTV Media Center
More information about the mythtv-commits
mailing list