All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jurgen Kramer <gtmkramer@xs4all.nl>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Raimonds Cicans <ray@apollo.lv>, linux-media@vger.kernel.org
Subject: Re: [REGRESSION] media: cx23885 broken by commit 453afdd "[media] cx23885: convert to vb2"
Date: Fri, 13 Feb 2015 17:29:13 +0100	[thread overview]
Message-ID: <1423844953.2887.7.camel@xs4all.nl> (raw)
In-Reply-To: <54DDC2B7.2080503@xs4all.nl>

Hi Hans,

On Fri, 2015-02-13 at 10:24 +0100, Hans Verkuil wrote:
> Jurgen, Raimond,
> 
> On 02/13/2015 10:12 AM, Hans Verkuil wrote:
> > Hi Jurgen,
> > 
> > On 02/04/2015 06:21 PM, Jurgen Kramer wrote:
> >> On Wed, 2015-02-04 at 17:19 +0100, Hans Verkuil wrote:
> >>> On 02/04/2015 05:06 PM, Jurgen Kramer wrote:
> >>>> Hi Hans,
> >>>>
> >>>> On Mon, 2015-02-02 at 10:36 +0100, Hans Verkuil wrote:
> >>>>> Raimonds and Jurgen,
> >>>>>
> >>>>> Can you both test with the following patch applied to the driver:
> >>>>
> >>>> Unfortunately the mpeg error is not (completely) gone:
> >>>
> >>> OK, I suspected that might be the case. Is the UNBALANCED warning
> >>> gone with my vb2 patch?
> > 
> >>> When you see this risc error, does anything
> >>> break (broken up video) or crash, or does it just keep on streaming?
> > 
> > Can you comment on this question?
> > 
> >>
> >> The UNBALANCED warnings have not reappeared (so far).
> > 
> > And they are still gone? If that's the case, then I'll merge the patch
> > fixing this for 3.20.
> > 
> > With respect to the risc error: the only reason I can think of is that it
> > is a race condition when the risc program is updated. I'll see if I can
> > spend some time on this today or on Monday. Can you give me an indication
> > how often you see this risc error message?
> 
> Can you both apply this patch and let me know what it says the next time you
> get a risc error message? I just realized that important information was never
> logged, so with luck this might help me pinpoint the problem.
I'll apply it tonight and will keep you posted.

Jurgen



  reply	other threads:[~2015-02-13 16:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-11  9:33 [REGRESSION] media: cx23885 broken by commit 453afdd "[media] cx23885: convert to vb2" Raimonds Cicans
2015-01-12 10:55 ` Hans Verkuil
2015-01-12 15:27   ` Raimonds Cicans
2015-01-13 16:07     ` Antti Palosaari
2015-01-29  7:33 ` Hans Verkuil
2015-01-29 11:51   ` Raimonds Cicans
2015-01-29 12:12     ` Hans Verkuil
2015-02-01 13:06       ` Raimonds Cicans
2015-02-02  9:36         ` Hans Verkuil
2015-02-02 14:43           ` Jurgen Kramer
2015-02-04 16:06           ` Jurgen Kramer
2015-02-04 16:19             ` Hans Verkuil
2015-02-04 17:21               ` Jurgen Kramer
2015-02-13  9:12                 ` Hans Verkuil
2015-02-13  9:24                   ` Hans Verkuil
2015-02-13 16:29                     ` Jurgen Kramer [this message]
2015-02-15  7:53                     ` Jurgen Kramer
2015-02-15 10:28                     ` Raimonds Cicans
2015-02-13 16:14                   ` Jurgen Kramer
2015-02-13 16:42                     ` Hans Verkuil
2015-02-13 17:20                       ` Jurgen Kramer
2015-02-04 19:53               ` Raimonds Cicans
2015-02-06 16:02                 ` Raimonds Cicans

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=1423844953.2887.7.camel@xs4all.nl \
    --to=gtmkramer@xs4all.nl \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=ray@apollo.lv \
    /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.