Re: [x86_64] 2.6.14-git13 mplayer fails with "v4l2: ioctl queue buffer failed: Bad address" (2 Nov 2005, 11 Nov 2005)

[Junichi Uekawa]

Hi,

> >>>$ mplayer  tv://1 -tv driver=v4l2
> >>>MPlayer dev-CVS--4.0.2 (C) 2000-2005 MPlayer Team
> >>>CPU: Advanced Micro Devices Athlon 64 Newcastle,Winchester,San Diego,Venice; Sempron Palermo (Family: 15, Stepping: 0)
> >>>Detected cache-line size is 64 bytes
> >>>CPUflags:  MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 1 SSE2: 1
> >>>Compiled for x86 CPU with extensions: MMX MMX2 3DNow 3DNowEx SSE SSE2
> >>>
> >>bttv currently only supports v4l1.  We are still in the process of 
> >>porting the bttv driver from v4l1 to v4l2. Nickolay is working on it.
> >>
> >Thanks for the info. It's strange since this is a regression
> >(pre 2.6.14 used to work. New code made it fail).
> >Do you mean there was a change that broke v4l2 support in bttv ?
> >Ever since Linux Kernel 2.6.3, I used v4l2 for recording (more
> >than one and a half years...)
> >  
> >
> v4l2 support could not have been broken, since it was never present.  
> You were going through a compat layer.... Maybe that's where the 
> regression is.

> One question -- At exactly what point does this break for you?  The git 
> commit key above was from today, but at what point did this LAST work 
> for you?  It would be really helpful if you can do a git bisection test, 
> so that we can isolate the trouble patch if in fact it is a regression.

df70b17f88a4d1d8545d3569a1f6d28c6004f9e4 2 Nov 2005 Nonfunctional bttv
d83c671fb7023f69a9582e622d01525054f23b66 1 Nov 2005 (fails to boot due to USB issues)
6e9d6b8ee4e0c37d3952256e6472c57490d6780d 27 Oct 2005 Functional bttv

 
> You might also like to join us in #v4l on irc.freenode.net ... Sometimes 
> it's much quicker to troubleshoot this stuff over irc instead of email.


joined, but currently rebooting sporadically to test 
different kernels.


regards,
	junichi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/