From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750750AbVKKN3R (ORCPT ); Fri, 11 Nov 2005 08:29:17 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750749AbVKKN3R (ORCPT ); Fri, 11 Nov 2005 08:29:17 -0500 Received: from 219-75-232-131.eonet.ne.jp ([219.75.232.131]:45840 "HELO viper2.netfort.gr.jp") by vger.kernel.org with SMTP id S1750744AbVKKN3Q (ORCPT ); Fri, 11 Nov 2005 08:29:16 -0500 Date: Fri, 11 Nov 2005 22:29:15 +0900 Message-ID: <87ek5nb9ec.dancerj%dancer@netfort.gr.jp> From: Junichi Uekawa To: Michael Krufky Cc: Junichi Uekawa , linux-kernel@vger.kernel.org, video4linux-list@redhat.com, debian-amd64@lists.debian.org Subject: Re: [x86_64] 2.6.14-git13 mplayer fails with "v4l2: ioctl queue buffer failed: Bad address" (2 Nov 2005, 11 Nov 2005) In-Reply-To: <87y83vl780.dancerj%dancer@netfort.gr.jp> References: <87fyqeicge.dancerj%dancer@netfort.gr.jp> <87wtjg5gh2.dancerj%dancer@netfort.gr.jp> <4373D087.5050908@linuxtv.org> <87psp859sd.dancerj%dancer@netfort.gr.jp> <43740F06.6030504@m1k.net> <87y83vl780.dancerj%dancer@netfort.gr.jp> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/21.4 (x86_64-pc-linux-gnu) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi, > > 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 That was wrong; I re-tested it and it looks like 6e9d6b8ee4e0c37d3952256e6472c57490d6780d was a bad one. 2.6.14 (741b2252a5e14d6c60a913c77a6099abe73a854a) is functional. $ git-bisect start $ git-bisect bad 6e9d6b8ee4e0c37d3952256e6472c57490d6780d $ git-bisect good 741b2252a5e14d6c60a913c77a6099abe73a854a Bisecting: 721 revisions left to test after this regards, junichi