From: Junichi Uekawa <dancer@netfort.gr.jp>
To: Michael Krufky <mkrufky@m1k.net>
Cc: Junichi Uekawa <dancer@netfort.gr.jp>,
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)
Date: Fri, 11 Nov 2005 22:29:15 +0900 [thread overview]
Message-ID: <87ek5nb9ec.dancerj%dancer@netfort.gr.jp> (raw)
In-Reply-To: <87y83vl780.dancerj%dancer@netfort.gr.jp>
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
next prev parent reply other threads:[~2005-11-11 13:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-03 4:26 mencoder fails with Linux kernel from linus's git tree (2 Nov 2005) Junichi Uekawa
2005-11-10 21:40 ` [x86_64] 2.6.14-git13 mplayer fails with "v4l2: ioctl queue buffer failed: Bad address" (2 Nov 2005, 11 " Junichi Uekawa
2005-11-10 22:58 ` Mike Krufky
2005-11-11 0:05 ` Junichi Uekawa
2005-11-11 3:24 ` Michael Krufky
2005-11-11 12:06 ` Junichi Uekawa
2005-11-11 13:11 ` Michael Krufky
2005-11-11 13:29 ` Junichi Uekawa [this message]
2005-11-11 14:06 ` Hugh Dickins
2005-11-12 22:22 ` Nickolay V. Shmyrev
2005-11-13 2:54 ` Matti Aarnio
2005-11-13 4:24 ` Junichi Uekawa
2005-11-16 12:50 ` Nickolay V. Shmyrev
2005-11-16 17:47 ` Hugh Dickins
2005-12-01 0:09 ` Junichi Uekawa
2005-11-17 0:07 ` Junichi Uekawa
2005-11-11 14:21 ` Junichi Uekawa
2005-11-12 21:11 ` Ricardo Cerqueira
[not found] ` <87mzj4uoys.dancerj%dancer@netfort.gr.jp>
2005-12-19 23:10 ` [x86_64] linux 2.6.15-rc6 mplayer fails to record ALSA audio Junichi Uekawa
2006-01-14 7:33 ` Junichi Uekawa
2006-01-19 23:11 ` [x86_64] bttv: linux 2.6.16-rc1 mplayer fails to record ALSA audio and fails tune TV Junichi Uekawa
2006-02-02 9:13 ` Junichi Uekawa
2006-02-02 13:53 ` Manu Abraham
2006-02-02 23:04 ` Junichi Uekawa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ek5nb9ec.dancerj%dancer@netfort.gr.jp \
--to=dancer@netfort.gr.jp \
--cc=debian-amd64@lists.debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkrufky@m1k.net \
--cc=video4linux-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.