On Wed, Oct 01, 2008 at 01:33:20PM +0200, Sander Sweers wrote: > On Wed, Oct 1, 2008 at 05:11, Alan <[EMAIL PROTECTED]> wrote: > > So now I have a big fan pointed at the 350 but the playback (while > > recording 3 shows at once via the three cards) just bails out (for 2 of > > the three current recordings) and dmesg is full of: > > > > i2c_adapter i2c-0: sendbytes: error - bailout. > > ivtv2: DMA TIMEOUT 00000001 0 > > ivtv2: DMA TIMEOUT 00000001 0 > > ivtv2: DMA TIMEOUT 00000001 0 > > ivtv2: DMA TIMEOUT 00000001 0 > > i2c_adapter i2c-0: sendbytes: error - bailout. > > i2c_adapter i2c-0: sendbytes: error - bailout. > > ivtv2: DMA TIMEOUT 00000001 0 > > ivtv2: DMA TIMEOUT 00000001 0 > > This is not good and I suspect these come from a PVR-150, correct? The > PVR-150 has trouble with dma transfers which got worked around in > newer version of ivtv. But can still hapen in certain situations. > > > Any ideas? Or ways of testing heat maybe? > > Yes but this probabaly involves upgrading to a new version of ivtv. > Can you post the *complete* ivtv init so we know which version you are > on.
Sure thing.... ivtv is 1.1.0, but I notice that the xserver-xorg-video-ivtv package installed is .10.6, I found a debian version of xserver-xorg-video-ivtv_1.0.1-1_i386.deb which I'm considering upgrading to, if anyone things it'd do anything. Just before I rebooted to get the full init for you I noticed these in dmesg: ivtv0: All encoder MPG stream buffers are full. Dropping data. ivtv0: Cause: the application is not reading fast enough. IVTV0: All encoder VBI stream buffers are full. Dropping data. ivtv0: Cause: the application is not reading fast enough. Not sure if it's related or not.... Anyway, here's the output of dmesg | grep ivtv: ------------------------------------------------- [EMAIL PROTECTED]:~$ dmesg | grep -i ivtv ivtv: Start initialization, version 1.1.0 ivtv0: Initializing card #0 ivtv0: Autodetected Hauppauge card (cx23415 based) ivtv0: Unreasonably low latency timer, setting to 64 (was 32) tuner 2-0043: chip found @ 0x86 (ivtv i2c driver #0) tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #0) msp3400 2-0040: MSP4448G-B3 found @ 0x80 (ivtv i2c driver #0) saa7115 2-0021: saa7115 found (1f7115d0e100000) @ 0x42 (ivtv i2c driver #0) ivtv0: Autodetected Hauppauge WinTV PVR-350 saa7127 2-0044: saa7129 found @ 0x88 (ivtv i2c driver #0) 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: Registered device video16 for decoder MPG (1024 kB) ivtv0: Registered device vbi8 for decoder VBI (64 kB) ivtv0: Registered device vbi16 for decoder VOUT ivtv0: Registered device video48 for decoder YUV (1024 kB) ivtv0: Initialized card #0: Hauppauge WinTV PVR-350 ivtv1: Initializing card #1 ivtv1: Autodetected Hauppauge card (cx23416 based) ivtv1: Unreasonably low latency timer, setting to 64 (was 32) tuner 3-0043: chip found @ 0x86 (ivtv i2c driver #1) tuner 3-0061: chip found @ 0xc2 (ivtv i2c driver #1) ivtv1: Autodetected Hauppauge WinTV PVR-150 cx25840 3-0044: cx25843-24 found @ 0x88 (ivtv i2c driver #1) wm8775 3-001b: chip found @ 0x36 (ivtv i2c driver #1) 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: Registered device radio1 for encoder radio ivtv1: Initialized card #1: Hauppauge WinTV PVR-150 ivtv2: Initializing card #2 ivtv2: Autodetected Hauppauge card (cx23416 based) ivtv2: Unreasonably low latency timer, setting to 64 (was 32) tuner 4-0043: chip found @ 0x86 (ivtv i2c driver #2) tuner 4-0061: chip found @ 0xc2 (ivtv i2c driver #2) cx25840 4-0044: cx25843-24 found @ 0x88 (ivtv i2c driver #2) wm8775 4-001b: chip found @ 0x36 (ivtv i2c driver #2) ivtv2: Autodetected Hauppauge WinTV PVR-150 ivtv2: Registered device video2 for encoder MPG (4096 kB) ivtv2: Registered device video34 for encoder YUV (2048 kB) ivtv2: Registered device vbi2 for encoder VBI (1024 kB) ivtv2: Registered device video26 for encoder PCM (320 kB) ivtv2: Registered device radio2 for encoder radio ivtv2: Initialized card #2: Hauppauge WinTV PVR-150 ivtv: End initialization ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes) ivtv0: Loaded v4l-cx2341x-dec.fw firmware (262144 bytes) ivtv0: Encoder revision: 0x02060039 ivtv0: Decoder revision: 0x02020023 ivtv0: Loaded v4l-cx2341x-init.mpg firmware (155648 bytes) ivtvfb0: Framebuffer at 0xd5510000, mapped to 0xfa210000, size 1665k ivtvfb0: Framebuffer registered on ivtv card id 0 ivtv2: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes) ivtv2: Encoder revision: 0x02060039 ivtv1: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes) ivtv1: Encoder revision: 0x02060039 [EMAIL PROTECTED]:~$ ------------------------------------------------- Hardware setup is /dev/video0 = pvr-350 video1 and video2 are pvr-150s, the box is a knoppmyth system from last year about this time though no (or minimal) packages upgraded on it. I replaced the 350 card last week due to issues with it's tv tuner recording badly, and previously it had no issues like this (though that was before the addition of the 2x150 cards though). Alan -- Alan <[EMAIL PROTECTED]> - http://arcterex.net -------------------------------------------------------------------- "Beware of computer programmers that carry screwdrivers." -- Unknown _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
