| From: Michael Carland <[EMAIL PROTECTED]> | I have an AMD64 machine running Debian sarge with 2.6.11.7, in 32 bit mode. | It's sole purpose is to run mythbackend (.18). It has a single PVR-500MCE with | ivtv 0.3.6e. I have a second PVR-500 I'd like to add, but am trying to resolve | this problem first. One possible problem is my MB has a VIA chipset. It is an | MSI K8T Neo2-F (I was looking for AMD64 with a good number of PCI). | | The problem is it reboots spontaneously. There is nothing in the logs, I even | had the kernel use ttyS0 as the console, and had another machine capture the | output.
[Note: I'm not an expert, I'm just thinking out loud.] Sounds like you are doing all you can. The serial console is a good thing to try. The fact that it is AMD64 is probably not a problem because you are using it in 32-bit mode. Have you tried it in 64-bit mode? I would not expect it to behave better, but it *might* behave differently. Of course that experiment requires a new installation and probably isn't worth the effort. | Still nothing interesting. It seems to happen more frequently if the | machine is busier. I haven't seen a reboot when it records a single program | at a time, for weeks on end. But if I am viewing something prerecorded (over | NFS) while it is recording, it is very likely I will get a reboot within 30 | minutes. I don't remember any reboots when I just view prerecorded video while | it is not recording. Since the playback isn't involving the PVR card, one kind of bad interaction is ruled out. Perhaps others can be eliminated by experiments. Can you crash the system by playback over NFS while not recording? Can you crash the system by playback from a local file while recording? Can you crash the system with other (non-NFS) network load while recording? | From: Robert Nelson <[EMAIL PROTECTED]> | I've been running into a similar problem using a 64 bit distro of FC3 | with an ASUS K8N-Pro board. Note: this is a board with an nVidia chipset, not Via. | Although similar, I don't have a complete | system reboot, mythfrontend just crashes. I was able to remedy the | problem by forcing the backend to access the full out IP instead of | doing a loopback on the ethernet card with 127.0.0.1. That remedied | my problem, you could alwasy try that and see, its simple. Just | disablet he loopback. Wow. 127.0.0.1 should not involve any networking hardware at all. I don't think that using the IP address of a real card probably causes the real card to be used either. I'm pretty sure that the network stack knows not to use the hardware to talk to itself. So using the real IP address of a real card should make no *hardware* difference. This is a fascinating observation, but I don't immediately see where it leads. ------------------------------------------------------- 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
