From: Sean <knife@toaster.net>
To: linux-media@vger.kernel.org
Cc: Hans de Goede <hdegoede@redhat.com>
Subject: Re: capture-example.c crash on close_device()
Date: Wed, 12 Aug 2009 14:55:05 -0700 [thread overview]
Message-ID: <4A833A39.2000305@toaster.net> (raw)
In-Reply-To: <4A79E6A3.7050508@toaster.net>
Hans,
What do you think is causing this? pac207 driver.
Sean
Sean wrote:
> Hi,
>
> I have compiled kernel 2.6.30 from kernel.org, and I have also
> compiled capture-example.c from the mercurial depository. These work
> on laptop hardware, but on my DM&P e-box 2300SX (with vortex86 cpu),
> capture-example.c crashes the system. Complete lockup, no keyboard,
> etc. I turned on all debuging in gspca_main, i.e. options gspca_main
> debug=0x1FF. I also put print statements in capture-example.c in
> main() before each function call. Here is the output below. Has anyone
> had this problem?
>
> -------
> # capture-example -r
> <snip>
> gspca: packet [28] o:28644 l:126
> gspca: add t:2 l:126
> gspca: packet [31] o:31713 l:630
> pac207: SOF found, bytes to analyze: 630. Frame starts at byte #19
> gspca: add t:3 l:14
> gspca: frame complete len:26496 q:1 i:0 o:1
> gspca: add t:1 l:0
> gspca: add t:2 l:600
> gspca: poll
> gspca: read (202752)
> gspca: dqbuf
> gspca: frame wait q:1 i:0 o:0
> gspca: autogain: lum: 252, desired: 102, steps: 5
> gspca: dqbuf 1
> gspca: qbuf 1
> gspca: qbuf q:0 i:0 o:0
> .stop_capturing()
> uninit_device()
> close_device()
> gspca: capture-example close
> gspca: kill transfer
> gspca: isoc irq
> gspca: isoc irq
> gspca: isoc irq
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2009-08-12 21:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 20:08 capture-example.c crash on close_device() Sean
2009-08-12 21:55 ` Sean [this message]
2009-10-27 8:48 ` Sean
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=4A833A39.2000305@toaster.net \
--to=knife@toaster.net \
--cc=hdegoede@redhat.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 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.