No, it's not mythtv. It's my own app. But I'm now wondering if maybe these messages occur when my application hits a point where it has to pause (e.g., waiting for another resource). I'll look into it. I thought my threads were smarter than that, but I may have overlooked something.
I'll get the branch build to fix the verbose logging. Thanks. Rich -- Rich Kadel Appeligo, Inc. (858) 433-1747 www.appeligo.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hans Verkuil Sent: Friday, February 23, 2007 11:44 PM To: Discussion list for development of the IVTV driver Subject: Re: [ivtv-devel] System (practically) non-responsive after several hours...no clues On Saturday 24 February 2007 08:27, Rich Kadel wrote: > So far it is working. I had trouble reusing the CentOS 4.3 (upgraded > to kernel 2.6.18) from when I was using the AMD Opteron and VIA > chipset. I'm not sure it was board related, but it was too hard to > figure out, so I reloaded the OS from scratch. Just got it up and > running again with SMP (I forgot to check if I did or didn't have HT > enabled). So far so good, except I'm occasionally getting those huge > logs about VBI and/or MPEG stream buffers full. > > Hans - A few days ago, you said you fixed it so it wouldn't generate > so many redundant log messages. Is the trunk still where I need to > go to get that fix? No, you need to get it from the 0.10 branch: http://ivtvdriver.org/viewcvs/ivtv/branches/0.10.tar.gz?view=tar The trunk contains my conversion work to get the driver into the kernel, that's not usable for now. BTW, I'm still not sure why you get those buffer full messages. You're not using MythTV, are you? That application has known issues with ivtv and mysql being handled in the same thread, sometimes causing long delays between two successive read()s from the video device. (Does anyone know what the status is of this MythTV bug?) Regards, Hans > > Thanks, > Rich > > -- > > Rich Kadel > Appeligo, Inc. > (858) 433-1747 > www.appeligo.com > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Stanley Merkx > Sent: Friday, February 23, 2007 12:50 PM > To: Discussion list for development of the IVTV driver > Subject: Re: [ivtv-devel] System (practically) non-responsive after > several hours...no clues > > > Replying to my own post to add more detail: > > According to the manual mine is a 945PL Neo (MS-7236). Cannot reboot > now to have a look at the BIOS (doing 2 recordings and a playback at > the moment ;-)). > > So it is probably not exactly the same board, but very similar. > > Good luck, hope your board is just as good for you as mine is for > me... > > Regards, > Stanley. > > >> The real test would be if all 4 PVR 500's will work (stable) with > >> a new motherboard, and I don't have a motherboard in my desktop > >> machine with 4 PCI > >> slots. On a whim, I've crossed my fingers and purchased a new MSI > >> 945P_Neo3-F and Intel Core 2 Duo 6600E (and 2Gigs DDR2) to replace > >> the ASUS > >> board and Opteron. Maybe this will do the trick. I'm recompiling > >> the kernel to include SMP. Let me know if anything here sounds > >> like a bad idea. > > > > This sounds very much like the same board I'm using. I'm at work > > now, so I can't check, but it is an MSI with an Intel 945 chipset > > and 4 PCI slots. > > > > I had some trouble getting the on-board SATA controller to work in > > native mode. Turned out I needed to add 3 modules to my initrd: > > ata_piix, libata and scsi_mod. Without these I could only boot with > > the controller in PATA legacy mode which was incredibly slow: RAID1 > > rebuild of 40GB took 22 hours with a load of ~25. Performance was > > so bad I almost brought the board back. > > > > Now it's working incredibly reliable with a dual core D805 and 2 > > PVR-350's and a Promise PATA controller (doing software RAID5) on > > the PCI bus. > > > > Stanley. > > > >> -- > >> > >> Rich Kadel > >> Appeligo, Inc. > >> (858) 433-1747 > >> www.appeligo.com > >> > >> > >> -----Original Message----- > >> From: [EMAIL PROTECTED] > >> [mailto:[EMAIL PROTECTED] On Behalf Of Brad > >> Barnett Sent: Wednesday, February 21, 2007 7:54 PM > >> To: Discussion list for development of the IVTV driver > >> Subject: Re: [ivtv-devel] System (practically) non-responsive > >> after several > >> hours...no clues > >> > >> On Wed, 21 Feb 2007 19:28:53 -0800 > >> > >> "Rich Kadel" <[EMAIL PROTECTED]> wrote: > >>> I may have to do that, but I'll have to swap out the CPU as well > >>> (and maybe memory). Could be pricey, but I need the stability. > >>> If that's what it takes. > >>> > >>> Any recommendations on an Intel motherboard, chipset, CPU > >>> combination that supports 4 PCI slots? PVR-500 requires 3.3 volt > >>> support, as I recall. > >> > >> You couldn't swap that box with your desktop, for example, for a > >> few days? > >> Anything to debug... > >> > >>> -- > >>> > >>> Rich Kadel > >>> Appeligo, Inc. > >>> (858) 433-1747 > >>> www.appeligo.com > >>> > >>> > >>> -----Original Message----- > >>> From: [EMAIL PROTECTED] > >>> [mailto:[EMAIL PROTECTED] On Behalf Of Brad > >>> Barnett Sent: Wednesday, February 21, 2007 4:13 PM > >>> To: Discussion list for development of the IVTV driver > >>> Subject: Re: [ivtv-devel] System (practically) non-responsive > >>> after several hours...no clues > >>> > >>> > >>> > >>> DMA issues should only occur when the card is actually in use. > >>> However, > >>> I want to warn you, I had DMA issues with merely one PVR-500 and > >>> a PVR-350! > >>> > >>> I had these problems with three different VIA chipsets, and they > >>> utterly > >>> vanished when I moved to an Intel chipset. VIA forums are rife > >>> with complaints about said chips. > >>> > >>> With a box that has 4 tuner cards in it, trying a different > >>> motherboard shouldn't be an issue. A swap out should take 10-15 > >>> minutes.... > >>> > >>> On Wed, 21 Feb 2007 15:50:45 -0800 > >>> "Rich Kadel" <[EMAIL PROTECTED]> wrote: > >> > >> _______________________________________________ > >> ivtv-devel mailing list > >> ivtv-devel@ivtvdriver.org > >> http://ivtvdriver.org/mailman/listinfo/ivtv-devel > > > > _______________________________________________ > > ivtv-devel mailing list > > ivtv-devel@ivtvdriver.org > > http://ivtvdriver.org/mailman/listinfo/ivtv-devel > > _______________________________________________ > ivtv-devel mailing list > ivtv-devel@ivtvdriver.org > http://ivtvdriver.org/mailman/listinfo/ivtv-devel > > > _______________________________________________ > ivtv-devel mailing list > ivtv-devel@ivtvdriver.org > http://ivtvdriver.org/mailman/listinfo/ivtv-devel _______________________________________________ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel _______________________________________________ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
