From: Sean <knife@toaster.net>
To: bugzilla-daemon@bugzilla.kernel.org
Cc: moinejf@free.fr, Alan Stern <stern@rowland.harvard.edu>,
linux-media@vger.kernel.org, USB list <linux-usb@vger.kernel.org>
Subject: Re: [Bug 14564] capture-example sleeping function called from invalid context at arch/x86/mm/fault.c
Date: Mon, 04 Jan 2010 18:31:52 -0800 [thread overview]
Message-ID: <4B42A498.10801@toaster.net> (raw)
In-Reply-To: <201001030702.o0372phV004707@demeter.kernel.org>
bugzilla-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=14564
>
>
> Jean-Francois Moine <moinejf@free.fr> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |moinejf@free.fr
>
>
>
>
> --- Comment #22 from Jean-Francois Moine <moinejf@free.fr> 2010-01-03 07:02:45 ---
> Hello Sean,
>
> Sorry to be a bit late. Looking at the dmesg, I found that the gspca version
> was 2.7.0. May you upgrade your linux media stuff from LinuxTv.org and check if
> this problem still occurs?
>
> Jef
>
Jef,
I upgraded to the latest v4l-dvb from http://linuxtv.org/hg/v4l-dvb,
made the kernel modules, made the v4l libraries, and recompiled
capture-example.c. Gspca now shows 2.8.0. The error still persists. Alan
Stern's latest patch to ohci-q.c traps the error. I think it is an issue
with the cpu or usb controller on the Vortex86SX SoC.
Sean
next parent reply other threads:[~2010-01-05 2:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-14564-16732@http.bugzilla.kernel.org/>
[not found] ` <201001030702.o0372phV004707@demeter.kernel.org>
2010-01-05 2:31 ` Sean [this message]
2010-01-05 2:45 ` [Bug 14564] capture-example sleeping function called from invalid context at arch/x86/mm/fault.c Alan Stern
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=4B42A498.10801@toaster.net \
--to=knife@toaster.net \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=moinejf@free.fr \
--cc=stern@rowland.harvard.edu \
/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