[mythtv-users] A post about no problem, but still wondering ...

[R. G. Newbury]

On 11/04/14 09:30 PM, Saul A. Peebsen wrote:
> On Fri, 11 Apr 2014 16:28:46 +1200
> Stephen Worthington <stephen_agent at jsw.gen.nz> wrote:
>
>> On Thu, 10 Apr 2014 14:32:44 -0500, you wrote:
>>
>>> I had a crashing BE which crashed almost every time HVR2250 was
>>> accessed first time. Once it was working it kept working. It was so
>>> bad I enabled hardware watchdog support in my kernel to have this
>>> box reset automatically (headless box in a closet).
>>> I was thinking the motherboard is bad, so I replaced it. No cigar.
>>> Until I added 2 GiB of RAM to make it 4 GiB total ... not a single
>>> crash after that.
>>> Is there an explanation to this?
>>
>> Is it by chance a 32-bit system?
>
> Nope, 64. And it is not the memory, when I replaced the motherboard it
> came with new RAM.

Your old motherboard may have been the inadvertent source of the 
problem. I also have an HVR2250. It uses 3 modules, which have to be 
loaded in the correct order. Otherwise the card will not work. But I 
have never had the BE crash! The problem appears to be that there can be 
race condition where one module starts to load, and another starts to 
load before the first has finished loading and stabilized.
Hilarity ensues...</sarc>


I ended up adding the following lines to /etc/rc.d/rc.local

systemctl stop mythbackend.service
modprobe -r tda18271
modprobe -r s5h1411
modprobe -r saa7164
modprobe -r s5h1411
modprobe -r tda18271
modprobe -r s5h1411
echo "  Ignore 'FATAL error' messages above if next line is 'No output...' "
lsmod | grep tad18271
lsmod | grep s5h1411
lsmod | grep saa7164
echo "  No output means modules were properly unloaded"

modprobe  tda18271
modprobe  s5h1411
modprobe  saa7164
echo "  Modules re-loaded in proper order"
systemctl start mythbackend.service

Sounds like you are lucky. Your new motherboard +/- card combo +/- your 
distro don't have that problem!

-- 
              R. Geoffrey Newbury