On Fri, Jun 12, 2009 at 1:11 PM, Ken Mink <[email protected]>wrote:

> This sounds almost exactly like the reboot issue I've been having. I'm
> using a AMD processor, but the motherboard is VIA chipsets. I am running
> CentOS. The kernel reports itself as 2.6.18, but there a lot of
> backporting in it.
>
> I am going to start compiling vanilla kernels and see if I can find one
> where the PVR-500 is stable. I'm starting with 2.6.25 and working
> backwards.
>
> I am not willing to bet on my success. My issue could easily be a
> hardware problem. My gut says it's not, though.
>
> Jeroen Roos wrote:
> > Hello all,
> >
> > I have a PVR-500 card on a Via Epia EN15000 board. I am running Gentoo
> > Linux on it for MyhthTV. Ever since upgrading from kernel 2.6.22, I have
> > been having reboots on my system whenever it tries recording something.
> > Because I have had some issues with the SATA drivers on it previously, I
> >  have always suspected that to be the problem, however, after some more
> > research I am now pretty sure that the IVTV driver is the culprit.
> >
> > When using kernel 2.6.22 (with Gentoo patches) everything works fine. I
> > have tried many different kernels after that, and with all the system
> > eventually reboots. The current I have running is the vanilla 2.6.29.4
> > kernel, still the same problem.
> >
> > I can easily reproduce the problem by running:
> >
> > dd if=/dev/video0 of=/dev/null bs=64k count=10000
> >
> > usually it reboots before it reaches 5000 blocks, sometimes it takes a
> > little longer, but eventually the system reboots.
> >
> > I think that I rule out all other components of the system by copying to
> > /dev/null.
> >
> > Any video recorded with the card is good (that is, when it's not sent to
> > /dev/null :-) )
> >
> > I have checked http://www.ivtvdriver.org/index.php/Howto and everything
> > seems to be installed as it should be, after that I checked
> > http://www.ivtvdriver.org/index.php/Troubleshooting, but that does not
> > seem to mention anything that is describing my situation.
> >
> > I have tried setting debug to 127, but I don't see anything that looks
> > like an error, it also doesn't display anything just before crashing.
> >
> > the dmesg | tac ... etc script on the "how to ask for help" page does
> > not give any output, so I'll just include dmesg | grep ivtv...
> >
> > I think I am using the in-kernel version of ivtv, but I am not 100%
> > sure, how do I check?
>

I can't say definitively how to check but I was using the in-kernel version
for 2.6.26 (debian lenny) and got the following in my dmesg:
ivtv: Start initialization, version 1.4.1
Which is newer than the one you reported below.

>
> > I have run out of options on what to try next, any ideas?
>

How about building the latest ivtv?  http://ivtvdriver.org/index.php/Howto

>
> >
> >
> > Thanks,
> > Jeroen
> >
> >
> > video ~ # dmesg | grep ivtv
> > ivtv: Start initialization, version 1.4.0
> > ivtv0: Initializing card 0
> > ivtv0: Autodetected Hauppauge card (cx23416 based)
> > ivtv 0000:04:08.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
> > ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
> > ivtv0: Autodetected WinTV PVR 500 (unit #1)
> > cx25840 1-0044: cx25843-24 found @ 0x88 (ivtv i2c driver #0)
> > tuner 1-0060: chip found @ 0xc0 (ivtv i2c driver #0)
> > tuner 1-0043: chip found @ 0x86 (ivtv i2c driver #0)
> > tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
> > wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0)
> > IRQ 17/ivtv0: IRQF_DISABLED is not guaranteed on shared IRQs
> > ivtv0: Registered device video0 for encoder MPG (4096 kB)
> > ivtv0: Registered device video32 for encoder YUV (2048 kB)
> > ivtv0: Registered device vbi0 for encoder VBI (1024 kB)
> > ivtv0: Registered device video24 for encoder PCM (320 kB)
> > ivtv0: Registered device radio0 for encoder radio
> > ivtv0: Initialized card: WinTV PVR 500 (unit #1)
> > ivtv1: Initializing card 1
> > ivtv1: Autodetected Hauppauge card (cx23416 based)
> > ivtv 0000:04:09.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
> > ivtv1: Unreasonably low latency timer, setting to 64 (was 32)
> > ivtv1: Correcting tveeprom data: no radio present on second unit
> > ivtv1: Autodetected WinTV PVR 500 (unit #2)
> > cx25840 2-0044: cx25843-24 found @ 0x88 (ivtv i2c driver #1)
> > tuner 2-0043: chip found @ 0x86 (ivtv i2c driver #1)
> > tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #1)
> > wm8775 2-001b: chip found @ 0x36 (ivtv i2c driver #1)
> > IRQ 18/ivtv1: IRQF_DISABLED is not guaranteed on shared IRQs
> > ivtv1: Registered device video1 for encoder MPG (4096 kB)
> > ivtv1: Registered device video33 for encoder YUV (2048 kB)
> > ivtv1: Registered device vbi1 for encoder VBI (1024 kB)
> > ivtv1: Registered device video25 for encoder PCM (320 kB)
> > ivtv1: Initialized card: WinTV PVR 500 (unit #2)
> > ivtv: End initialization
> > ivtv 0000:04:08.0: firmware: requesting v4l-cx2341x-enc.fw
> > ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
> > ivtv0: Encoder revision: 0x02060039
> > ivtv 0000:04:09.0: firmware: requesting v4l-cx2341x-enc.fw
> > ivtv1: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
> > ivtv1: Encoder revision: 0x02060039
> >
> > video ~ # lspci | grep video
> > 04:08.0 Multimedia video controller: Internext Compression Inc iTVC16
> > (CX23416) MPEG-2 Encoder (rev 01)
> > 04:09.0 Multimedia video controller: Internext Compression Inc iTVC16
> > (CX23416) MPEG-2 Encoder (rev 01)
> >
> > video ~ # uname -a
> > Linux video 2.6.29.4 #1 SMP Wed Jun 10 20:58:40 CEST 2009 i686 VIA
> > Esther processor 1500MHz CentaurHauls GNU/Linux
> >
> > _______________________________________________
> > ivtv-users mailing list
> > [email protected]
> > http://ivtvdriver.org/mailman/listinfo/ivtv-users
>
>
> --
> "They that can give up essential liberty to obtain a little temporary
> safety deserve neither liberty nor safety."--Benjamin Franklin
> " 'Necessity' is the plea for every infringement of human liberty; it
> is the argument of tyrants; it is the creed of slaves."--William Pitt
>
> _______________________________________________
> ivtv-users mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Reply via email to