From: Hans de Goede <hdegoede@redhat.com>
To: Pablo Baena <pbaena@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: Possible bug on libv4l read() emulation
Date: Fri, 16 Oct 2009 19:42:58 +0200 [thread overview]
Message-ID: <4AD8B0A2.1090207@redhat.com> (raw)
In-Reply-To: <36be2c7a0910151500k847735dub3e1a8547f913e8c@mail.gmail.com>
Hi,
On 10/16/2009 12:00 AM, Pablo Baena wrote:
> I have a program where I use libv4l's read() emulation for simplicity.
> But with most v4l2 webcams I've tried, I get kernel panics.
>
> I have pics of the message if anyone cares to see them, I don't want
> to flood the mailing list.
>
> Basically, the names I see in the kernel panic from a uvcvideo card is:
>
> uvc_queue_next_buffer
> __bad_area_no_semaphore
> do_page_fault
>
> And a lot more.
>
A panic should never happen, no matter what libv4l does (as libv4l is 100%
userspace). Please submit a bug report with as much detail as possible to the
driver author.
Regards,
Hans
next prev parent reply other threads:[~2009-10-16 17:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 22:00 Possible bug on libv4l read() emulation Pablo Baena
2009-10-16 17:42 ` Hans de Goede [this message]
2009-10-16 18:23 ` Pablo Baena
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=4AD8B0A2.1090207@redhat.com \
--to=hdegoede@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=pbaena@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox