[mythtv-commits] Ticket #8199: backend lockup on recording expiry

MythTV mythtv at cvs.mythtv.org
Tue Jun 1 12:13:51 UTC 2010

#8199: backend lockup on recording expiry
 Reporter:  michael_zanetti@…        |        Owner:  danielk       
     Type:  defect                   |       Status:  infoneeded_new
 Priority:  trivial                  |    Milestone:  unknown       
Component:  MythTV - Recording       |      Version:  0.23-fixes    
 Severity:  medium                   |   Resolution:                
  Mlocked:  0                        |  

Comment(by dude71@…):

 No one else reporting anything similar ? Michael_zanetti's post sounds
 pretty similar to me. What i still don't understand is how a bad disk
 controller only effects the mythbackend process (we are talking RAID-0 2x
 7200 sata disks here; not really slow either). I can SSH the backend just
 fine right after this "lockup" and after restarting the backend process it
 works normal again so I would exclude network dropping packets as well. I
 don't use a firewall internally so i'll exclude that as well.

 I would say that nothing you mention here or what I could think of would
 justify any service from getting into an undefined state (not serving
 recordings or streaming livetv in this case). It's only the mythbackend
 process that doesn't work as it should the rest of the machine is
 completely responsive. No errors in syslog/dmesg. Bad RAM stick would show
 up earlier I guess.. but I'll check that when I've the opportunity.

 I understand that it's hard to debug this without a logfile/backtrace. If
 this problem shows up again I'll try to post one. The line  "~MythContext
 waiting for threads to exit."  that Michael_zanetti reports I also have
 seen. Apart from that nothing special in the mythtv-backend.log.


Ticket URL: <http://svn.mythtv.org/trac/ticket/8199#comment:15>
MythTV <http://www.mythtv.org/>

More information about the mythtv-commits mailing list