From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: "Scheuermann, Mail" <Scheuermann@barco.com>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: AW: AW: v4l2_buffer with PBO mapped memory
Date: Mon, 07 Apr 2014 01:37:28 +0200 [thread overview]
Message-ID: <12148246.7IO9AkCti4@avalon> (raw)
In-Reply-To: <67C778DDEF97AE4BA9DC4BA8ECFD811E1DB2EA13@KUUMEX11.barco.com>
Hi Thomas,
On Friday 04 April 2014 20:01:33 Scheuermann, Mail wrote:
> Hi Laurent,
>
> I've done the following:
>
> echo 3 >/sys/module/videobuf2_core/parameters/debug
>
> and found in /var/log/kern.log after starting my program:
>
> [239432.535077] vb2: Buffer 0, plane 0 offset 0x00000000
> [239432.535080] vb2: Buffer 1, plane 0 offset 0x001c2000
> [239432.535082] vb2: Buffer 2, plane 0 offset 0x00384000
> [239432.535083] vb2: Allocated 3 buffers, 1 plane(s) each
> [239432.535085] vb2: qbuf: userspace address for plane 0 changed,
> reacquiring memory
> [239432.535087] vb2: qbuf: failed acquiring userspace memory for plane 0
This confirms everything is working properly up to the point where videobuf2-
vmalloc fails to acquire the user pointer memory. The problem comes from
vb2_vmalloc_get_userptr() in drivers/media/v4l2-core/videobuf2-vmalloc.c.
Unfortunately that function lacks debugging. Are you familiar enough with
kernel programming to add printk statements there and see where it fails ?
> [239432.535088] vb2: qbuf: buffer preparation failed: -22
> [239432.535128] vb2: streamoff: not streaming
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-04-06 23:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 15:10 v4l2_buffer with PBO mapped memory Thomas Scheuermann
2014-04-02 19:23 ` Laurent Pinchart
2014-04-03 16:52 ` AW: " Scheuermann, Mail
2014-04-03 23:16 ` Laurent Pinchart
2014-04-04 20:01 ` AW: " Scheuermann, Mail
2014-04-06 23:37 ` Laurent Pinchart [this message]
2014-04-11 5:56 ` Thomas Scheuermann
2014-04-15 6:04 ` Thomas Scheuermann
2014-04-15 15:02 ` Hans Verkuil
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=12148246.7IO9AkCti4@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=Scheuermann@barco.com \
--cc=linux-media@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox