[mythtv-users] Backend consolidation, aborted...
ctmythtv at pacbell.net
Sat Jul 17 06:28:08 UTC 2010
David Brieck Jr. wrote:
> On Fri, Jul 16, 2010 at 8:48 AM, John Drescher <drescherjm at gmail.com> wrote:
>> On Thu, Jul 15, 2010 at 10:03 AM, Kevin Kuphal <kkuphal at gmail.com> wrote:
>>> On Wed, Jul 14, 2010 at 11:49 PM, Clay <ctmythtv at pacbell.net> wrote:
>>>> After a complete, clean, reinstall, same result.
>>>> I verified both pvr-150s are working, and recording.
>>>> 15 minutes into recording the pvr-150s shit the bed.
>>>> [ 52.469557] CPU0 attaching NULL sched-domain.
>>>> [ 60.108026] eth0: no IPv6 routers present
>>>> [ 64.977018] CPU0 attaching NULL sched-domain.
>>>> [ 64.977071] CPU0 attaching NULL sched-domain.
>>>> [ 1952.196010] ivtv0: DMA TIMEOUT 00000001 0
>>>> [ 1955.412011] ivtv0: DMA TIMEOUT 00000001 0
>>>> [ 1958.348011] ivtv0: DMA TIMEOUT 00000001 0
>>>> [ 1961.316015] ivtv0: DMA TIMEOUT 00000001 0
>>>> [ 1964.256010] ivtv0: DMA TIMEOUT 00000001 0
>>>> [ 1967.224031] ivtv0: DMA TIMEOUT 00000001 0
>>>> [ 1970.160014] ivtv0: DMA TIMEOUT 00000001 0
>>>> [ 1973.096009] ivtv0: DMA TIMEOUT 00000001 0
>>>> I'm putting them back in the old slave b/e to see if they work there.
>>>> If not, it's back to 0.21.
>>> This most certainly appears to be a kernel/driver issue for ivtv. In your
>>> reinstallation, etc. have you changed kernels/drivers from your previously
>>> working config? I would focus your energies there and not so much with the
>>> myth software which only relies on those ivtv drivers to provide it data.
>> I have seen this a long long time ago. Are you using an ancient kernel
>> like 2.6.18?
> He's on 10.04 which runs 2.6.32-23.
> If it helps, I had this problem myself with two PVR-250s. The backend
> would lockup completely randomly every 5-45 days. My solution was to
> setup another backend just for the PVRs so that when they crashed and
> I wasn't home at least my family could still use the system to view
> recordings and videos. I used to use 3 PVR-250s, but dropping down to
> two seemed to help it crash less often.
> That box has since gotten a fresh install of 10.04 and I'm patiently
> waiting to see if it crashes again. I personally thought it was due to
> an IDE hard drive not playing nice with the motherboard and it's
> firmware so during the upgrade a threw in a SATA drive just in case
> that was the original problem. The SATA drive has already fixed one of
> the issues I was having which was that after POST it would take about
> 15 seconds to load up the grub menu and another 15 seconds to start
> booting once a selection was made.
My PVR-150s were flawless in the old mbe/fe for over four years.
I'm hoping this malfunction is due to antique hardware.
This MB I tried for the new master BE is circa 1997.
It was perfect for a backend. 6 PCi slots... room for 4 cards and a SATA
adapter. Cool running P4 Northwood chip. A gig of 1066 Rambus RIMM.
While it was running it commflagged as fast as any of my newer boxes
Now I got nothing...
The DVB cards stopped working in the P4 box. They worked perfectly until
I yanked the PVRs.
Myth can't access the PVR-150s now that they're back in the same box
they came out of. The cards are fine. I can cat recordings off them.
Myth thinks they're in use.
I'm gathering up some new bits tomorrow to build a new box and start the
process all over again.
I can't believe I've been a friggin week trying to sort this mess out.
More information about the mythtv-users