public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean-Francois Moine <moinejf@free.fr>
To: David Ellingsworth <david@identd.dyndns.org>
Cc: Hans de Goede <hdegoede@redhat.com>,
	Mariusz Kozlowski <m.kozlowski@tuxland.pl>,
	video4linux-list@redhat.com
Subject: Re: [v4l-dvb-maintainer] [BUG] zc3xx oopses on unplug: unable to handle kernel paging request
Date: Thu, 20 Nov 2008 20:03:51 +0100	[thread overview]
Message-ID: <1227207831.1708.58.camel@localhost> (raw)
In-Reply-To: <30353c3d0811201057o2244ca80of033e3bead96c779@mail.gmail.com>

On Thu, 2008-11-20 at 13:57 -0500, David Ellingsworth wrote:
> I'm not entirely sure what's going on in the gspca driver. It seems as
> though the module count is wrong. Unfortunately, I don't have a camera

No, the module count is correct, the problem is that it is incremented /
decremented by 2 at each open / close. Don't you have the same behaviour
with stk-webcam?

> which uses this driver so it's a little hard for me to do any
> debugging with it at this time. Technically though, freeing the
> gspca_dev in the release callback of the video_device struct should be
> possible and that is how it was intended to be used. The stk-webcam
> driver has no issues using it this way either.

I looked at your code, and the only difference I see is that I
increment / decrement explicitly the subdriver module count (OK, step 1
- this module is not the main driver which has the file operations and
the problem!).

Did you activate the slab debug and check the disconnect while
streaming?

Regards.

-- 
Ken ar c'hentañ |             ** Breizh ha Linux atav! **
Jef             |               http://moinejf.free.fr/


--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

  reply	other threads:[~2008-11-20 19:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200811151218.45664.m.kozlowski@tuxland.pl>
2008-11-15 18:48 ` [BUG] zc3xx oopses on unplug: unable to handle kernel paging request Jean-Francois Moine
     [not found]   ` <200811162224.47885.m.kozlowski@tuxland.pl>
2008-11-18 18:57     ` Jean-Francois Moine
     [not found]       ` <200811182219.38925.m.kozlowski@tuxland.pl>
2008-11-19 10:32         ` Jean-Francois Moine
2008-11-19 13:52           ` David Ellingsworth
     [not found]             ` <492439AE.1070903@redhat.com>
2008-11-19 20:20               ` [v4l-dvb-maintainer] " Jean-Francois Moine
     [not found]               ` <200811192256.09361.m.kozlowski@tuxland.pl>
2008-11-20 18:19                 ` Jean-Francois Moine
2008-11-20 18:57                   ` David Ellingsworth
2008-11-20 19:03                     ` Jean-Francois Moine [this message]
2008-11-21  0:24                       ` leandro Costantino
2008-11-21 14:54                       ` David Ellingsworth
2008-11-21 15:03                         ` David Ellingsworth
2008-11-22 12:41                 ` Jean-Francois Moine
     [not found]                   ` <200811221421.50818.m.kozlowski@tuxland.pl>
2008-11-23 17:43                     ` Jean-Francois Moine

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=1227207831.1708.58.camel@localhost \
    --to=moinejf@free.fr \
    --cc=david@identd.dyndns.org \
    --cc=hdegoede@redhat.com \
    --cc=m.kozlowski@tuxland.pl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox