Are there any DMA messages in your log files? I fought with this for awhile... I ended up putting a NVidia 5200 in my box and ditching the 350's TV-Out.
In my case, it worked way back in FC1 and an older ivtv version - I also recall that ivtvdev was different back then. mjc --- Maverick <[EMAIL PROTECTED]> wrote: > Wow! There is actually someone else out there with this problem! ;) I > started thinking it was just me and my friend being the only two in > the world for a sec. > > Anyway, yes, I'm running an older Dell GX110 which is a P3-667 or > something. My friends is not a dell, just a Celeron 533. So yeah, I > believe it could be dma on the slow machines, but the thing is, if we > run X on the monitor, and just use the PVR-350 for recording/playback, > it works perfectly. That fact alone leeds us to believe the problem is > the X ivtv fb driver and a possiable incompatability with new cards > (350's w/ Tuner = 47). Unfontunatly, I have no idea how to > test/confirm/debug that thought. I certainly think we're not the only > one's using low end machines and PVR-350's, in fact, that's why I > bought the '350, so I can use a low end processer. > > As for disabling DMA, I did an hdparm -d0 /dev/hda, and that causes > mythbackend to take 80-90% cpu, thus making the box useless. So > although we may know it's a DMA bus deadlock or whatever, I don't > think not using DMA is the right fix. > > I'd put the money into a new machine, or even replace my main computer > and use it's 1.2Ghz AMD board, but if the problem still continues on > new hardware... well... then what? > > Thanks for your reply, at least I know I'm not crazy. Maybe the real > test would be to borrow/buy an older PVR-350 from someone and see if > the problem exists. I'd also willing work with a developer on fixing > it.. ;) > > -Kenneth > > On Sat, 12 Feb 2005 21:03:48 -0500, Brent Kilgore > <[EMAIL PROTECTED]> wrote: > > Whoh. .. Are you me? I'm sure I typed this a while back. Now, let me > > read rest of your post to make sure. I always wondered what I did while > > I slept :) j/k > > > > Ok, didn't notice if you mentioned it but I'm assuming you are running > > on a low-endish computer. Possible an old dell dimension? > > > > I had 2 big problems. First off, every once in a while usually when the > > MPEG stream got interrupted the adaptor would blow up. Video out stops > > and the syslogs are flooded with crap. This turned out to be faulty > > hardware. After a couple of false starts with Hauppauge they were happy > > (?) enough to cross ship the card. > > > > Second, was the freezing problem EXACTLY how you described it. Except > > that if I waited to long sometimes I could flood ping it back into > > reality. Took a few minutes but better than a hard lock. My fix for > > this was... DISABLE DMA on the hard drive. That's right DISABLE.I did > > that and everything was smooooth and perfect. Apparently on my > > motherboard the bus controller(?) was setting up a DMA deadlock > > situation or something. It hit me in the middle of the night. DEADLOCK > > ... therefore eliminate one of the parties. The DMA on the PVR was > > impossible to remove so I killed it on the HD. I went from .2% usage to > > 20% usage but that's ok. It's still responsive. In fact I burnt a DVD > > while watching live TV with only a couple of stutters. > > > > I've got a 120G hd in the mail scheduled to be here tomorrow. I hope I > > can make it work. > > > > I hope I wasn't too incoherent. My brain is currently trying to figure > > out the easiest way to clone my hard drive to another 20g ( not > > identical geometry :( ) to backup my 4 months of hard work. > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of Maverick > > Sent: Saturday, February 12, 2005 6:31 AM > > To: [email protected] > > Subject: [ivtv-devel] Lockup / System freeze w/ new PVR-350 > > > > Hello, > > > > Hope I'm on the right list for this... > > > > I'm trying to debug a problem with new PVR-350's. Both a friend of > > mine and I bought them, built similar (but not same) boxes, and have > > debian (KnoppMyth), and in my case, I'm now on Kernel 2.6.10 + ivtv > > 0.3.2d. I've tried both 0.2latest and 0.3 ivtv versions, every > > firmware version I could get ahold of, every trick I can think of to > > no avail, so I figured it was time to ask the pros. > > > > Our problem is, no matter what ivtv driver we try, or what config > > options, etc, the boxes lock up spontaneously. The only "temporary" > > resolution we've been able to make work is to run X (mythfrontend) on > > a monitor, but still use ivtv to record/playback TV. So, it makes us > > assume that the lockup/pause/freeze issue has to do with ivtv_fb more > > than anything else. I've also experienced issues where it will > > unfreeze after about 10 seconds, only to freeze moments later. > > Another way to make it lock up is actually playback a recording, and > > either wait about 2-15 minutes, or ff/rew a couple times. Does the > > same thing, and if I'm not mistaken, that doesn't even use ivtv_fb... > > > > Another oddity is, if I'm SSH'd into the box, sitting at the shell, I > > can hit enter right after it freezes to unlock it. If I wait too long > > though, the whole box seems to lock up and my SSH will drop. Can't > > reconnect, can't anything, have to power cycle. Obviously, this > > situation makes it rather impossible to use the boxes on just a TV > > alone. Is anyone familiar with this issue, and or know a way to fix > > it? > > > > I thought maybe it has something to do with IRQ/DMA stuff, and I saw > > another post asking about that, but no conclusive answers. :( Is it > > possiable the bus is being flooded with too much I/O? > > > > We also thought maybe it has some weirdness w/ the kernel's > > framebuffer and ivtv's framebuffer conflicting somehow, I even tried > > compiling my kernel without the console framebuffer, but that just > > seemed to break everything. > > > > Lastly, upgrading from ivtv 0.2 latest to 0.3.2d, now the tuner tunes > > nothing but static, but I'm way less worried about that since it locks > > up so much. > > > > Here's my dmesg stuff if it helps: > > > > Linux video capture interface: v1.00 > > ivtv: ==================== START INIT IVTV ==================== > > ivtv: version 0.3.2 (d) loading > > ivtv: Linux version: 2.6.10-20050210 SMP preempt 386 gcc-3.3 > > ivtv: In case of problems please include the debug info > > ivtv: between the START INIT IVTV and END INIT IVTV lines when > > ivtv: mailing the ivtv-devel mailinglist. > > ivtv: Autodetected WinTV PVR 350 card > > ivtv: Found an iTVC15 based chip > > PCI: Found IRQ 10 for device 0000:01:08.0 > > PCI: Sharing IRQ 10 with 0000:00:1f.3 > > PCI: Sharing IRQ 10 with 0000:00:1f.5 > > ivtv: XXX PCI device: 0x7124 vendor: 0x8086 > > tveeprom: Hauppauge: model = 48132, rev = K268, serial# = 2913978 > > tveeprom: tuner = LG TAPE H001F MK3 (idx = 68, type = 47) > > tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000) > > tveeprom: audio_processor = MSP3440 (type = 11) > > ivtv: i2c attach [client=tveeprom[0],ok] > > ivtv: Tuner Type 47, Tuner formats 0x00001000, Radio: yes, Model > > 0x00ad2598, Rev > > ision 0x00000001 > > ivtv: NTSC tuner detected > > ivtv: Radio detected > > tuner: Ignoring new-style parameters in presence of obsolete ones > > tuner: chip found at addr 0xc2 i2c-bus ivtv i2c driver #0 > > ivtv: i2c attach [client=(tuner unset),ok] > > saa7115: starting probe for adapter ivtv i2c driver #0 (0x10005) > > saa7115: detecting saa7115 client on address 0x42 > > saa7115: writing init values > > ivtv: i2c attach [client=saa7115[0],ok] > > saa7115: status: (1E) 0x48, (1F) 0xc0 > > saa7127: Ignoring new-style parameters in presence of obsolete ones > > saa7127: video encoder driver version V 0.3 loaded > > saa7127: detecting saa7127 client on address 0x88 > > saa7127: Selecting NTSC video Standard > > saa7127: Selecting S-Video+Composite > > saa7127: Turn WSS off > > saa7127: Widescreen Mode 4:3 Full Format > > saa7127: Selecting Normal Encoder Input > > saa7127: Enable Video Output > > ivtv: i2c attach [client=saa7127[0],ok] > > msp34xx: ivtv version > > msp34xx: init: chip=MSP3448W-A2, has NICAM support, simple (D) mode, > > simpler (G) > > no-thread mode > > msp34xx: $Id$ compiled on: Feb 12 2005 00:28:45 > > ivtv: i2c attach [client=MSP3448W-A2,ok] > > ivtv: Encoder revision: 0x02040011 > > ivtv: Decoder revision: 0x02020023 > > ivtv: Configuring WinTV PVR 350 card with 10 streams > > ivtv: Create DMA stream 0 using 256 16384 byte buffers 4194304 kbytes > > total > > ivtv: Registered v4l2 device, streamtype 0 minor 0 > > ivtv: Create DMA stream 1 > > ivtv: Registered v4l2 device, streamtype 1 minor 32 > > ivtv: Create stream 2 using 40 52224 byte buffers 2097152 kbytes total > > ivtv: Registered v4l2 device, streamtype 2 minor 224 > > ivtv: Create DMA stream 3 using 455 4608 byte buffers 2097152 kbytes > > total > > ivtv: Registered v4l2 device, streamtype 3 minor 24 > > ivtv: Create stream 4 > > ivtv: Registered v4l2 device, streamtype 4 minor 64 > > ivtv: Create DMA stream 5 using 16 65536 byte buffers 1048576 kbytes > > total > > ivtv: Registered v4l2 device, streamtype 5 minor 16 > > ivtv: Create stream 6 using 1024 2048 byte buffers 262144 kbytes total > > ivtv: Registered v4l2 device, streamtype 6 minor 228 > > ivtv: Create stream 7 > > ivtv: Registered v4l2 device, streamtype 7 minor 232 > > ivtv: Create DMA stream 8 using 6 103680 byte buffers 622080 kbytes > > total > > ivtv: Registered v4l2 device, streamtype 8 minor 48 > > ivtv: Create DMA stream 9 using 32 65536 byte buffers 2097152 kbytes > > total > > ivtv: Setting Tuner 47 > > tuner: type set to 47 (NoTuner) by ivtv i2c driver #0 > > saa7115: decoder set input (4) > > saa7115: now setting Composite input > > ivtv: Setting audio matrix to input 3, output 1 > > ivtv: Switching standard to NTSC. > > ivtv: ivtv_enc_thread: pid = 2027, itv = 0xd0b0c2a0 > > ivtv: ivtv_dec_thread: pid = 2028, itv = 0xd0b0c2a0 > > saa7115: decoder set norm NTSC > > saa7115: set audio: 0x01 > === message truncated === ===== Michael J. Carter | QOTD: "If you keep an open mind people [EMAIL PROTECTED] | will throw a lot of garbage in it." __________________________________ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ ivtv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
