[mythtv] [mythtv-commits] Ticket #6983: deadlock on readReadyLock and socket lock

David Asher asherml at gmail.com
Sat Sep 5 17:50:57 UTC 2009

On Sep 5, 2009, at 9:12 AM, MythTV wrote:

> #6983: deadlock on readReadyLock and socket lock
> ------------------------------ 
> +---------------------------------------------
> Reporter:  markspieth        |        Owner:  danielk
>     Type:  defect            |       Status:  assigned
> Priority:  major             |    Milestone:  0.22
> Component:  MythTV - General  |      Version:  head
> Severity:  high              |   Resolution:
>  Mlocked:  0                 |
> ------------------------------ 
> +---------------------------------------------
> Comment(by danielk):
> Mark, can you provide a backtrace of the process in deadlock + the
> mythbackend -v socket,network,extra log? If you still have the core  
> around
> and can't repro now the backtrace is more important.
> There is an existing report of mythweb deadlocking the backend, but in
> that report we were sending data on a dead socket so that was my first
> concern.
> I plan to set up mythweb again next week and investigate, but any  
> info I
> have before then will be useful.

If you have trouble reproducing (or just don't want to mess around  
with your systems) I can currently reproduce my hang EVERY time I  
delete a program from mythweb.  Any information or patches or tests  
you'd like I can provide.  Just ask.

It sure feels like a related problem.  I kept ending up in readReady  
when tracing around in the backtrace.



More information about the mythtv-dev mailing list