Opened 14 years ago

Closed 14 years ago

#1533 closed defect (invalid)

Post 0.19 patches crash system when playing livetv/recordings on PVR350 TV-Out

Reported by: luud.heck@… Owned by: Isaac Richards
Priority: blocker Milestone: unknown
Component: mythtv Version: head
Severity: high Keywords:
Cc: Ticket locked: no

Description

I noticed that somewhere in the post 0.19 release patches something changed causing my system to mess up the PCI irq kernel subsystem.

I'm running gentoo and when I upgraded from the (now no longer available) mythtv-0.19-r1 ebuild to the mythtv-0.19_p9163-r1 ebuild playing any video on the PVR350 TV-Out would first result in terrible sound (choppy and hissy). Pausing and continuing would fix the sound problem, but resulted in crashing the IRQ subsystem resulting in my network card no longer working.

So I cloned the mythtv-0.19_p9163-r1 to remove the post 0.19 patches and now the system is stable again. Attached is the ebuild I created for reference. It contains the location of the patches file used in the mythtv-0.19_p9163-r1 ebuild. It seems to me this relates to the revision 9163.

System details: Abit BH6 motherboard Celeron 700 PVR350 (PCI slot 1) PVR500 (PCI slot 2) HPT360 ATA-100 (PCI slot 3) Creative SB128 (PCI slot 4) 3com 3c905 (PCI slot 5)

Having the PVR cards first in the system is important otherwise the ivtv system is unstable. With mythv 0.19, this system is very stable, I've had it running for about 11 days.

Note that recording is no problem, but playback of recordings or livetv is bad. Playback on a remote frontend on an X server is also no problem (just to a PC screen that is).

Attachments (1)

mythtv-0.19-r2.ebuild (7.9 KB) - added by luud.heck@… 14 years ago.
Gentoo ebuild for mythtv-0.19

Download all attachments as: .zip

Change History (2)

Changed 14 years ago by luud.heck@…

Attachment: mythtv-0.19-r2.ebuild added

Gentoo ebuild for mythtv-0.19

comment:1 Changed 14 years ago by anonymous

Resolution: invalid
Status: newclosed

when the system locks up it is either a hardware problem or a kernel/driver problem.

If you would like to know why MythTV is triggering the problem so the ivtv people will help you, you should find the destabilizing changeset.

Note: See TracTickets for help on using tickets.