Well that makes sense. The reason I was asking was I just added a new hard drive to my frontend/backend box and then started to have a problem with it freezing regularly. I think it was a temperature issue as the machine didn't have very good ventilation where it was located. I didn't really think about voltages. What I ended up doing was setting up a dedicated storage/mysql machine in another room and making that one just a frontend/backend over the network (I wanted to move the backend portion too but the encoder card has to stay in it because I don't have a cable outlet anywhere else and I already have too many cables running around our place so another would probably be too much for my wife :-))
<br><br>Thanks<br><br><div><span class="gmail_quote">On 11/10/06, <b class="gmail_sendername">Jon Vanderwoude</b> <<a href="mailto:jvanderw@gmail.com">jvanderw@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I installed Sensord, set it up to log the voltages ever 5 minutes or<br>so, checked the logs right around the time it crashed, the 3.3v rail<br>was always out of spec (3.10 ish... )<br><br>looked up the buffer chip that is on the PVR250, checked out the white
<br>paper it runs off 3.3V's<br><br>I hooked up the volt meter in side the case just to make sure that the<br>sensor on the motherboard was accurate (because I'm cheap and don't<br>want to buy a new psu with out good reason) and sure enough it was
<br>dropping below 3.1 (memory chip specs say it should work down to 3.0,<br>but the reality seems to be different... or there is something in<br>series with the chip in the board that pulls off some extra<br>voltage...)<br>
<br>replaced it no problem with it for a week now, when before I couldn't<br>make it two hours with out it stopping, and less if I was watching tv<br>while recording. I let it run watching tv on a remote front end over<br>
night with no issues (while encoding previous recordings just to<br>stress test)<br><br>On 11/9/06, David Leinbach <<a href="mailto:dleinbac@gmail.com">dleinbac@gmail.com</a>> wrote:<br>> Out of curiosity, how did you determine that this was the problem?
<br>><br>><br>> On 11/9/06, Jon Vanderwoude <<a href="mailto:jvanderw@gmail.com">jvanderw@gmail.com</a> > wrote:<br>> ><br>> > On 10/13/06, Nick <<a href="mailto:knowledgejunkie@gmail.com">knowledgejunkie@gmail.com
</a> > wrote:<br>> > > On 12/10/06, McNally <<a href="mailto:mcnallychris@pobox.com">mcnallychris@pobox.com</a>> wrote:<br>> > > > Hi,<br>> > > ><br>> > > > I'm using mythtv
0.20. When I watch recording in progress, such as a<br>> > > > baseball game, I begin watching about 40 minutes after the start, fast<br>> > > > forward through commercials and other junk, and find that the actual
<br>> > > > recording seems to have stopped soon after i started watching. This<br>> has<br>> > > > happened twice already to me. I see from the logs that there seems to<br>> be<br>> > > > a DMA error and it may be IVTV related. Other recordings have ended
<br>> much<br>> > > > sooner than scheduled and there is an error in the Myth log.<br>> > > ><br>> > > > I am using an ASUS A8N-VM CSM mainboard with an AMD Sempron which has<br>> > > > NVIDIA nforce and gforce chipsets. The backend and frontend are the
<br>> same<br>> > > > box. I am using ext3. The CPU from top is around 90% when watching<br>> > > > recordings. I have sections of the logs below. Thanks in advance.<br>> > > ><br>> > > > ivtv version
<br>> > > > ivtv: version 0.7.0 (tagged release) loading<br>> > > > ivtv: Linux version: 2.6.17-1.2142_FC4 mod_unload 686 REGPARM<br>> 4KSTACKS<br>> > > > gcc-4.0<br>> > >
<br>> > > Try upgrading to ivtv 0.7.1 which has a fix for DMA problems like this<br>> > > - from the ivtv changelog:<br>> > ><br>> > > IVTV changes:<br>> > ><br>> > >
0.7.1 stable release<br>> > > - Add getopt support to test/vbi. Add new timeout option.<br>> > > - Fix South African broadcast frequency table.<br>> > > - Detect and workaround DMA offsets that can be introduced by
<br>> > > a DMA error.<br>> > > - Sliced VBI always uses PIO, never DMA.<br>> > ><br>> > ><br>> > > Nick<br>> ><br>> ><br>> > I was having this issue even after installing the new firmware, turns
<br>> > out the 3.3v line on my power supply was bad and the memory chip on<br>> > the PVR-250 wasn't getting the juice it needed to keep it going,<br>> > replacing the power supply resolved the issue.<br>
> > _______________________________________________<br>> > mythtv-users mailing list<br>> > <a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>> > <a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br>> ><br>><br>><br>> _______________________________________________<br>> mythtv-users mailing list<br>> <a href="mailto:mythtv-users@mythtv.org">
mythtv-users@mythtv.org</a><br>> <a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br>><br>><br>><br>_______________________________________________
<br>mythtv-users mailing list<br><a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br><a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
</a><br></blockquote></div><br>