Okay, I have completed the first test. I exited X by moving to runlevel 3 like this $ sudo telinit 3 Then: $ sudo ivtvfbctl /dev/fb1 -globalalpha -nolocalalpha -alpha 0 Then: $ sudo dd if=file.mpg of=/dev/video16 bs=64k
This was with a 2.5 hour long movie. It plays to completion with no freeze so DMA with decoder seems to work fine in this environment. I don't think the other tests will gain me much since I was getting freeze of playback in mythtv without any other access happening, no recording goin on and not display of any program info from myth, just straight playback with nothing else going on would result in a freeze always in less than 20 minutes. So it would appear that maybe some other process might influence the robustness of the dma transfers. I will probably move straight to a plain vanilla i386 kernel and see if that helps I have plenty of MIPs for a single tuner! If you have any other ideas I would like to hear them. Steve -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of John Harvey Sent: Monday, November 14, 2005 11:50 PM To: 'Discussion list for development of the IVTV driver' Subject: RE: [ivtv-devel] ivtv framebuffer is broken with PVR350 One way to stop X running on the 350 would be to edit the Xorg.conf file and remove the 350 section temporarily. John > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:ivtv-devel- > [EMAIL PROTECTED] On Behalf Of Steve & Laurie Sanders > Sent: 15 November 2005 02:30 > To: Discussion list for development of the IVTV driver > Subject: RE: [ivtv-devel] ivtv framebuffer is broken with PVR350 > > John, > > Thanks for the detailed trouble shooting outline. Quickly the answer to > your > 2 questions. > 1) no i did not yet try a non smp kernel. i have to inventory all of the > other modules i need to recompile and it might take me a while. > 2) i am currently running mythtv svn 7738. > > I am running on FC3 system and loading ivtv during initrd. I know what i > need edit to boot my system without loading ivtv drivers but i currently > boot into kde desktop and i don't know how to undo that to perform the > experiments below but as soon as i find out how to do that i will perform > all the experiments you defined. > > thanks again. (if you can tell me how to keep x from starting and > launching > kde i will give double thanx!) > > Steve > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of John Harvey > Sent: Monday, November 14, 2005 1:24 PM > To: 'Discussion list for development of the IVTV driver' > Subject: RE: [ivtv-devel] ivtv framebuffer is broken with PVR350 > > > Apologies if you've already done some of this but the thread is getting > long > and there are various different problems in here. > > Things to try > 1) Have you tried a non SMP kernel as Hans suggested yet? > 2) I believe you are using Myth. If so which version? > > These errors appear to be mpeg decoder errors and nothing to do with the > framebuffer. > It would appear that the request to the firmware for information about the > next dma needed is getting the information wrong. Working out why this is > happening won't be easy. > The 350 has 3 users of the DMA engine. > > Encoder > Decoder > FrameBuffer > > The FrameBuffer normally doesn't do anything during playback unless either > an application talks to the X server or myth displays some information > (EPG > or Stop/pause information). > > Only one of these should use the DMA engine at anyone time. > The 1st thing to work out is which parts are being used when the system > goes > wrong. > > dd if=file.mpg of=/dev/video16 bs=64k > > will cause a file to be played by the decoder. > > 1st I would ensure this is stable. > Load ivtv & ivtv-fb but don't run X. > Make sure the global alpha is set to 0 > > ivtvfbctl /dev/fb0 -globalalpha -nolocalalpha -alpha 0 > > And then leave the dd command running in a loop over night. > > If this is ok then try recording & playing back at the same time by adding > > Dd if=/dev/video0 of=file1.mpg bs=64k count=10000 > > Again in a loop. > > If this works try playback and framebuffer updates > > ivtvfbctl /dev/fb0 -prepdma > > at the same time as the playback > > and then at the same time as playback and recording. > > All of these should probably be left running for an hour unless you hit a > problem earlier. > > One of these "should" lead to a problem without any real application or X > running and when we understand what situation causes the problem we will > be > in a better position to start trying to work out what the cause is. > > It is of course possible this won't show anything but I think it would be > useful to start with trying the above to see if it shows anything. > > John > > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:ivtv-devel- > > [EMAIL PROTECTED] On Behalf Of Steve & Laurie Sanders > > Sent: 13 November 2005 23:40 > > To: Discussion list for development of the IVTV driver > > Subject: RE: [ivtv-devel] ivtv framebuffer is broken with PVR350 > > > > John, > > > > I already posted that going back to 0.8.0 did not make any difference. I > > agree completly that it has to be a hardware or driver problem. $64M > > question, which driver? The hardware involved is a good genuine intel mb > > with integrated AGP video an network with 82865/82801EB chip set, 1G of > > ram, > > 3G P4 multithreading processor, and a PVR350. pretty solid hardware > > platform. > > > > Do you have any suggestions on how to hunt this bug down an kill it. I > > think > > hardware is stable. > > > > Steve > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] Behalf Of John Harvey > > Sent: Sunday, November 13, 2005 12:11 PM > > To: 'Discussion list for development of the IVTV driver' > > Subject: RE: [ivtv-devel] ivtv framebuffer is broken with PVR350 > > > > > > The frame buffer code in 0.8 is the same as in the latest. In fact going > > back to about 0.6 it hasn't really changed so I am not convinced about > > claims that 0.8 work and 0.10 is broken. > > The Xv code is the main difference so it is possible that something has > > changed there but again it is likely to be a driver/hardware issue. > > > > John > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] [mailto:ivtv-devel- > > > [EMAIL PROTECTED] On Behalf Of Steve & Laurie Sanders > > > Sent: 13 November 2005 19:19 > > > To: Discussion list for development of the IVTV driver > > > Subject: RE: [ivtv-devel] ivtv framebuffer is broken with PVR350 > > > > > > Never mind, 0.8.0 just froze too. No improvement for me. generated > this > > in > > > messages: > > > Nov 13 11:07:56 mediacenter kernel: ivtv0 warning: DEC: Decoder wants > > > 0x00010000 bytes, bad memory location 0x00010000. > > > Nov 13 11:07:59 mediacenter last message repeated 1847 times > > > Nov 13 11:08:07 mediacenter kernel: ivtv0 warning: DEC: Decoder > Invalid > > > type > > > 0x061c8202? > > > Nov 13 11:08:07 mediacenter last message repeated 4764 times > > > Nov 13 11:08:12 mediacenter kernel: ivtv0 warning: DEC: Decoder > Invalid > > > type > > > 0x02000000? > > > > > > > _______________________________________________ > ivtv-devel mailing list > [email protected] > http://ivtvdriver.org/mailman/listinfo/ivtv-devel > > > _______________________________________________ > ivtv-devel mailing list > [email protected] > http://ivtvdriver.org/mailman/listinfo/ivtv-devel _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
