[mythtv] Ticket #7078: socket errors cause back-end to become unresponsive (trunk 21894)
danielk at cuymedia.net
Mon Sep 21 17:34:22 UTC 2009
On Mon, 2009-09-21 at 13:11 -0400, David Asher wrote:
> On Sep 21, 2009, at 1:07 PM, MythTV wrote:
> > #7078: socket errors cause back-end to become unresponsive (trunk
> > 21894)
> Do the backtraces in #7046 look helpful?
Yes, I replied separately in that ticket. I'm not convinced both
tickets are for the same problem after looking at the backtraces.
#7046 appears to have a logical cause while #7078 is still a complete
mystery. The first couple back traces in #7078 are difficult to parse
due to the lack of debugging info, while David Shay's backtrace does
not seem to have any deadlocks, much less socket related ones. David
S.'s problem may in fact be something different from what databubble
is experiencing. David S. may be trying to run a master backend on an
ION which just does not have the grunt necessary to handle it.
I believe the extra debugging I added to the socket code is making
anything that causes the backend to either run slowly or deadlock
to look like a socket problem.
More information about the mythtv-dev