On Sunday 27 August 2006 18:31, Thomas Schmitz wrote:
> On Sunday 27 August 2006 18:21, Hans Verkuil wrote:
> > On Sunday 27 August 2006 18:14, Thomas Schmitz wrote:
> > > On Sunday 27 August 2006 17:55, Thomas Schmitz wrote:
> > > > On Sunday 27 August 2006 17:10, Hans Verkuil wrote:
> > > > > On Sunday 27 August 2006 16:04, Thomas Schmitz wrote:
> > > > > > Some bad news, the current 0.6 svn version panics on my
> > > > > > machine on load.
> > > > >
> > > > > And if you revert the last change, does it work again? This
> > > > > is clearly during early intialization and as far as I know I
> > > > > haven't touched that.
> > > >
> > > > I used  ivtv-0.6.3 (development revision 3341) before and it
> > > > worked nearly flawless - the only problem were the DMA errors
> > > > and corrupted video if I used the ondemand powersave module.
> > > >
> > > > I have just rebuild rev. 3341 and rev. 3405 again (just to make
> > > > sure that nothing I changed in my build environment since the
> > > > last time I build 3341 causes the problem) and the behavior is
> > > > the same. 3341 loads without problem and 3405 panics
> > > > reproduceable on load.
> > > >
> > > > I will try to narrow down which changeset between 3341 and 3405
> > > > introduced the problem.
> > >
> > > OK that was easy, there were far fewer changes than I expected
> > > between 3341 and 3405. 3374 (the last change before 3405) works
> > > without problems.
> >
> > Hmm, just a wild guess, but what happens if you delete all
> > GFP_DMA32 strings by a '0' in ivtv-queue.c? Would that fix the
> > problem?
>
> That solves the problem. rev. 3405 loads normally and I quick test
> with mythtv did not show any other problems.

Reverted this change. It should now work again. I clearly do not 
understand the behavior of GFP_DMA32 or I use it in the wrong spot. It 
sort of accidentally piggy-backed on the DMA fixed.

        Hans

_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

Reply via email to