<div class="gmail_quote">On Tue, Jun 3, 2008 at 10:10 PM, Brian Foddy <<a href="mailto:bfoddy@visi.com">bfoddy@visi.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div>I'd guess its some kernel deadlock with a device driver. What tuner card<br>is (are) running during the process. If the machine is really busy, and<br>you have some of the kernel preempt settings on, and there is a bug<br>
in the driver, it could cause a hard crash.<br></div></div></blockquote>
<div> </div>
<div>I am using a pchdtv HD-3000 tuner using DVB. If that was the case should it spit something out in the syslog? Maybe there's a setting somewhere I can flip to increase verbosity when logging...?</div>
<div> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div><span id=""></span><br>What type of computer? Multi-core, dual CPU? Using SMP kernel?<br>These can cause driver bugs more readily. If its an SMP instance,<br>try your test with SMP disabled (there is a kernel param that will do this).<br>
</div></div></blockquote>
<div> </div>
<div>It's an AMD X2 4200+ cpu, with SMP enabled in the kernel. I'm using a custom built kernel so I'd have to recompile it without SMP enabled but that's something to try, it has been working fine for at least a year with this processor. I previously had a AMD 3200+ single core and it worked for like three years with this processor.</div>
<div> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div><span id=""></span><br>The commercial scan itself is probably (haven't looked at code, but<br>I can't imagine) doing anything other than standard file I/O using<br>normal calls, so root or not, I don't see it the problem. But if it<br>
keeps the system busy, it could cause other faults to show up.<br><br>In general, hard lock ups / crashes are due to faulty / buggy device drivers<br>or hardware failures.<br></div></div></blockquote>
<div> </div>
<div>Yeah, your arguement seems sound. So far the machine has been running for 2.5 days without a crash after removing the "start commercial detection as soon as recording starts" option. Maybe it is just that I'm spreading out the file I/O calls so they aren't on top of one another.</div>
</div>