Ticket #9885 (closed Bug Report - General: Fixed)
Opened 2 years ago
Last modified 22 months ago
Deadlock on slave backend disconnect
|Reported by:||Ian Dall <ian@…>||Owned by:||danielk|
|Component:||MythTV - General||Version:||Master Head|
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 :-(
comment:1 Changed 2 years ago by Jonatan <mythtv@…>
comment:2 Changed 23 months ago by Ian Dall <ian@…>
comment:3 Changed 23 months ago by Ian Dall <ian@…>
comment:4 Changed 23 months ago by danielk
comment:5 Changed 23 months ago by Github
comment:6 Changed 23 months ago by danielk
- Owner set to danielk
- Status changed from new to assigned
- Milestone changed from unknown to 0.25
comment:7 Changed 22 months ago by danielk
- Status changed from assigned to closed
- Resolution set to Fixed