From: Andy Walls <awalls@radix.net>
To: Brandon Jenkins <bcjenkins@tvwhere.com>
Cc: Waffle Head <narflex@gmail.com>,
video4linux-list@redhat.com, ivtv-devel@ivtvdriver.org
Subject: Re: CX18 Oops
Date: Sat, 23 Aug 2008 17:44:20 -0400 [thread overview]
Message-ID: <1219527860.11451.2.camel@morgan.walls.org> (raw)
In-Reply-To: <de8cad4d0808181017q1c2467c2g74973deb1c70db97@mail.gmail.com>
On Mon, 2008-08-18 at 13:17 -0400, Brandon Jenkins wrote:
> On Mon, Aug 18, 2008 at 6:35 AM, Brandon Jenkins <bcjenkins@tvwhere.com> wrote:
> > On Sat, Aug 16, 2008 at 10:13 PM, Andy Walls <awalls@radix.net> wrote:
> >> On Mon, 2008-08-11 at 17:33 -0400, Brandon Jenkins wrote:
> >>> On Fri, Aug 8, 2008 at 10:18 AM, Andy Walls <awalls@radix.net> wrote:
> Andy,
>
> I also seeing these messages in dmesg:
>
> [65288.817420] cx18-0: Cannot find buffer 58 for stream TS
> [65288.817440] cx18-0: Could not find buf 58 for stream TS
> [65840.130797] cx18-0: Cannot find buffer 17 for stream TS
> [65840.130797] cx18-0: Could not find buf 17 for stream TS
> [65861.882721] cx18-0: Cannot find buffer 48 for stream TS
> [65861.882741] cx18-0: Could not find buf 48 for stream TS
> [66151.627392] cx18-0: Cannot find buffer 107 for stream encoder MPEG
> [66151.627392] cx18-0: Could not find buf 107 for stream encoder MPEG
> [67632.953680] cx18-0: Cannot find buffer 99 for stream encoder MPEG
> [67632.953680] cx18-0: Could not find buf 99 for stream encoder MPEG
> [67795.527911] cx18-0: Cannot find buffer 106 for stream encoder MPEG
> [67795.527911] cx18-0: Could not find buf 106 for stream encoder MPEG
>
> Brandon
Brandon,
There is now a fix for this bug as well in my v4l-dvb repo.
Regards,
Andy
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2008-08-23 21:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 1:04 CX18 Oops Brandon Jenkins
2008-08-06 1:29 ` Andy Walls
2008-08-06 10:57 ` Brandon Jenkins
2008-08-07 0:55 ` Andy Walls
2008-08-07 10:16 ` Brandon Jenkins
2008-08-07 13:36 ` Brandon Jenkins
2008-08-08 0:46 ` Andy Walls
2008-08-08 14:18 ` Andy Walls
2008-08-08 14:35 ` Hans Verkuil
2008-08-08 14:44 ` Andy Walls
2008-08-09 17:43 ` Brandon Jenkins
2008-08-11 21:33 ` Brandon Jenkins
2008-08-17 2:13 ` Andy Walls
2008-08-17 9:41 ` Hans Verkuil
2008-08-17 19:12 ` Andy Walls
2008-08-17 20:01 ` Hans Verkuil
2008-08-18 2:53 ` Andy Walls
2008-08-18 10:35 ` Brandon Jenkins
2008-08-18 17:17 ` Brandon Jenkins
2008-08-19 0:34 ` Andy Walls
2008-08-23 21:44 ` Andy Walls [this message]
2008-08-25 19:14 ` Brandon Jenkins
2008-08-18 23:52 ` Andy Walls
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=1219527860.11451.2.camel@morgan.walls.org \
--to=awalls@radix.net \
--cc=bcjenkins@tvwhere.com \
--cc=ivtv-devel@ivtvdriver.org \
--cc=narflex@gmail.com \
--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.