[mythtv] Ticket #7078: socket errors cause back-end to become unresponsive (trunk 21894)

David Asher asherml at gmail.com
Mon Sep 21 17:11:07 UTC 2009


On Sep 21, 2009, at 1:07 PM, MythTV wrote:

> #7078: socket errors cause back-end to become unresponsive (trunk  
> 21894)
> ------------------------------ 
> +---------------------------------------------
> Reporter:  databubble        |        Owner:  danielk
>     Type:  defect            |       Status:  infoneeded
> Priority:  major             |    Milestone:  0.22
> Component:  MythTV - General  |      Version:  head
> Severity:  medium            |   Resolution:
>  Mlocked:  0                 |
> ------------------------------ 
> +---------------------------------------------
>
> Comment(by danielk):
>
> databubble, your backtraces are still missing debugging info.
>
> davideshay, I do not see any evidence of a deadlock in that  
> backtrace. All
> threads appear to be in valid wait states.
>
> nickj-fox, please do not report "me too" -- it is not helpful. A  
> backtrace
> with debugging symbols that shows a deadlock would be helpful. (I  
> don't
> expect you to know if it displays a deadlock or not, just follow the
> TicketHowTo link on how to generate a full backtrace.)

Do the backtraces in #7046 look helpful?



More information about the mythtv-dev mailing list