public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Lemieux <rlemieu@cooptel.qc.ca>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: linux-media@vger.kernel.org
Subject: Re: Driver crash on kernel 2.6.32.7. Interaction between cx8800 (DVB-S) and USB HVR Hauppauge 950q
Date: Tue, 09 Feb 2010 13:32:41 -0500	[thread overview]
Message-ID: <4B71AA49.5000708@cooptel.qc.ca> (raw)
In-Reply-To: <829197381002090742m1975641eta54b9169447b0436@mail.gmail.com>

Hi,

I tried something simple with three kernel versions:

2.6.30, 2.6.31, and 2.6.32.7.

But I can't reproduce the problem that way.

Just after booting I run alternatively

/opt/dvb-apps/bin/szap -a 0 -r "CCTV 4"
/opt/dvb-apps/bin/azap -a 1 -r "57.1"

and then I run them concurrently

and finally I disconnect the USB tuner and replug and retry the 'azap'

I did not get any crash yet.

So there is likely some other "environmental" condition that is relevant.

I will continue using 2.6.32.7.  Whenever I meet the problem I will
take note of the environment and try to reproduce the same environment with
other versions of the kernel.

Thanks

> 
> The only "major reorganization" in that time period I can think of is
> a couple of the files related to IR support were moved.
> 
> Further, the problem appears to be in the implementation of
> request_firmware() and doesn't look specific to any changes in the
> v4l-dvb tree.
> 
> All I can suggest at this point is you try to narrow down what release
> the breakage was introduced in, at which point we can take a look at
> what changed.
> 
> Devin
> 

  reply	other threads:[~2010-02-09 18:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-09  4:43 Driver crash on kernel 2.6.32.7. Interaction between cx8800 (DVB-S) and USB HVR Hauppauge 950q Richard Lemieux
2010-02-09  5:18 ` Devin Heitmueller
2010-02-09 13:44   ` Richard Lemieux
2010-02-09 15:42     ` Devin Heitmueller
2010-02-09 18:32       ` Richard Lemieux [this message]
2010-02-10  2:14 ` Andy Walls
2010-02-10  3:05   ` Richard Lemieux
2010-02-10  3:12     ` Devin Heitmueller
2010-02-10 14:24       ` Andy Walls
2010-02-10 15:34       ` Andy Walls
2010-02-12  4:11         ` Greg KH
2010-02-13  1:18           ` Andy Walls
2010-02-13 13:40             ` Richard Lemieux
2010-02-10  3:09   ` Devin Heitmueller

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=4B71AA49.5000708@cooptel.qc.ca \
    --to=rlemieu@cooptel.qc.ca \
    --cc=dheitmueller@kernellabs.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