On Jun 23, 2005, at 2:30 PM, Andrew Ziobro wrote:
If this is something you could try, I'd be interested to hear your
results. If you are also able to avoid reboots by not using NFS, I'll
dig deeper on that path.
I also had a problem with NFS and Myth. I changed NFS to use TCP
instead of UDP. I had a network card or router that would drop
packets. TCP allowed it to recover better.
Drew
Thanks, but I already use TCP for NFS, and all the other options
suggested in the Myth docs.
This looks to be something more sinister, as a simple dropped packet
might cause Myth to burp, but it shouldn't cause an NFS server to
reboot. I found someone else who had a problem with kernel NFS
rebooting their machine. The only thing that ended the rebooting was to
switch to user space NFS, and eventually a new motherboard. Seems a bit
drastic to me.
I'm going to keep NFS turned off for a while, make sure that solves the
problem, and then try and figure out a way to capture the error message
(if there even is one) before the thing reboots. Assuming this all goes
to plan, I'll take it to the kernel mailing list.
-Michael
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
ivtv-devel mailing list
ivtv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
