<div class="gmail_quote">On Mon, Feb 9, 2009 at 1:27 PM, Bruce Taber <span dir="ltr"><<a href="mailto:b.taber@comcast.net">b.taber@comcast.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="Wj3C7c">Jelte Veldstra wrote:<br>
> This issue really drives me mad and I was wondering if others have<br>
> experienced the same.<br>
><br>
> I have built a dedicated backend based on CentOS 5 (with DVB support<br>
> from centos.plus kernels) and MythTV 0.21-fixes. It is currently fitted<br>
> with two Hauppauge Nova-S (budget) DVB-S adapters. Encrypted channels<br>
> are decrypted using open-sasc-ng and a subscription card in a phoenix<br>
> smartcard reader.<br>
><br>
> This setup works quite well but every now and then (~ 1 in 100<br>
> recordings) I have this setup hardlocking on me as a recording is<br>
> started. After restarting the system and looking into the logfiles there<br>
> is nothing that hints what happened that made it crash. It looks as if<br>
> the power plug was pulled as syslog shows nothing on the Linux level.<br>
> The backend log only shows the line that indicates a recording is<br>
> started and nothing since. The sasc-ng log shows no attempt of the<br>
> backend connecting to it for this recording. The system has had its<br>
> share of stress tests to rule out memory, power or overheating problems<br>
> and has shown no such issues.<br>
><br>
> As MythTV and sasc-ng run as non-privileged users it seems like<br>
> something is going on on kernel and driver level. This thought is<br>
> enforced as it only seems to happen with stv0299 based adapters (such as<br>
> the Nova-S). Having used a single Twinhan 1030A DVB-S adapter (dvb-bt8xx<br>
> based) for a while never failed on me. And when I mixed both types (I<br>
> really want a twin-tuner system) it would occasionally crash on the<br>
> Nova-S but never on the Twinhan.<br>
><br>
> So somehow it seems related to the hardware, but as I tried three<br>
> different stv0299 based tuners, it's not a faulty adapter is seems but<br>
> rather a driver issue. If I could find a second 1030A then I would try<br>
> that for sure, but I havent been able to find one, plus I'd really like<br>
> to understand what's going on here. Searching <a href="http://linuxtv.org" target="_blank">linuxtv.org</a><br>
</div></div>> <<a href="http://linuxtv.org" target="_blank">http://linuxtv.org</a>> mail archives doesn't provide answers on that.<br>
<div class="Ih2E3d">><br>
> Googling for it revealed some possible hints. One suggestion was that it<br>
> could be multirec in combination with open-sasc-ng. Others have found<br>
> that multirec not being 100% working with open-sasc-ng but had no<br>
> crashes. To rule is out I have disabled multirec, but still have had<br>
> crashes. Another suggestion was that a race condition could arrise<br>
> between software RAID5 code and the DVB subsystem (would explain why<br>
> there are no kernel messages during or after the crash). As I used soft<br>
> RAID5 I have since removed that configuration from my setup, but still<br>
> no luck.<br>
><br>
> So I have spent quite some time googling and trying out what I found<br>
> there, but no luck yet. I'm runnning out of ideas and wondered if other<br>
> MythTV users have had similar issues or found a pattern. So far I cannot<br>
> reproduce it and the only pattern so far is that it only happens at the<br>
> start of a recording (never during or outside recordings) and on stv0299<br>
> based adapters.<br>
><br>
> If you recognise this or have any pointers for me to try, please share.<br>
><br>
> Thanks in advance,<br>
><br>
><br>
> Jelte<br>
><br>
><br>
</div>> ------------------------------------------------------------------------<br>
<div class="Ih2E3d">><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" target="_blank">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br>
</div>My system suddenly started this same type of behavior. The problem was<br>
finally traced down to a faulty onboard Ethernet port. Disabling the<br>
Ethernet in the BIOS and installing a separate card eliminated the<br>
problem completely.<br>
<font color="#888888"><br>
Bruce<br>
</font><div><div></div><div class="Wj3C7c">_______________________________________________<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" target="_blank">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br>
</div></div></blockquote></div><br><br>Hello Bruce,<br>
<br>
Thanks for your input. What led you to this conclusion and what
Ethernet chip was the faulty one? My PCI slots are taken so I cannot
easily try it myself. Where there messages in logfiles that hinted
issues with the Ethernet port or was the Ethernet traffic poor? I have
already replaced this motherboard (for different reasons) and it now
has a different Ethernet chip. As far as I can tell it's working just
fine, but perhaps there are conflicts with certain chips.<br>
<br>
Regards,<br>
<br>
<br>
Jelte<br>
<br><br>