[mythtv-commits] Ticket #4234: mythbackend using 1100% of cpu in deadlock
MythTV
mythtv at cvs.mythtv.org
Wed Dec 5 14:17:25 UTC 2007
#4234: mythbackend using 1100% of cpu in deadlock
-------------------------------+--------------------------------------------
Reporter: johnsonn at matc.edu | Owner: nigel
Type: defect | Status: assigned
Priority: blocker | Milestone: 0.21
Component: mythtv | Version: head
Severity: high | Resolution:
Mlocked: 0 |
-------------------------------+--------------------------------------------
Comment(by johnsonn at matc.edu):
Why is there not more diagnostic data available for UPNP so people can
help diagnose problems?? For "-v upnp" supposing to be verbose, it is
not. I can not tell if UPNP found any of my UPNP compatible devices, nor
can I tell why they are not working. In my humble opinion "-v upnp"
should report on every send and receive command sent over the network. If
a device does not work the log should say I sent out this request and was
expecting this response, but I got <raw packet dump here(in ascii and
hex)> Then we can manual interpet the response data and build a patch
much easier. Also I believe there should be a GUI entry for UPNP under
settings or something that lists all detected devices and there status.
If a device is broken it should say something like "broken at phase 2" or
"devices response fails at phase 1". Maybe a section where we can assist
the decoding process by telling mythtv at what offset to find the data it
is expecting. I would be willing to apply patches, and report results.
--
Ticket URL: <http://svn.mythtv.org/trac/ticket/4234#comment:26>
MythTV <http://svn.mythtv.org/trac>
MythTV
More information about the mythtv-commits
mailing list