Hello, On Wed, 2010-01-06 at 09:36 -0500, Devin Heitmueller wrote: > Just to be clear, this patch does *not* address the warm reboot > problem. I am continuing to work that issue, but there should be no > expectation that this patch allows the device to survive a warm > reboot. > That one would be cool. > It should address concerns people were seeing where the system load > would be between 0.50 and 1.0 just by having the device connected, and > *may* help in cases where you start to see mt2060 errors after several > hours of operation. hmmm... 32 days uptime, no mt2060 error from my NovaT500, outside of a failed read at startup. regarding the load, I'm not sure I am experiencing it, or it is shadowed by MythTV's frontend "idling" at 15% cpu... I'll stop the frontend during the night and look at the load in the morning. I may be able to provide a graph from munin, as I have multiple recordings, some concurrent, of the kids shows in the morning. If I have the load thing, I'll test the patch, otherwise I'll keep the WAF, and KAF, as I would not be a proper guinea pig anyway. Nico -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
