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 08:44:05 -0500 [thread overview]
Message-ID: <4B7166A5.8050402@cooptel.qc.ca> (raw)
In-Reply-To: <829197381002082118k346437b3y4dc2eb76d017f24f@mail.gmail.com>
Hi Devin,
I was previously running kernel vmlinux-2.6.29.5. I notice there was a major
reorganization of some of the media structure between 2.6.29 and 2.6.32.
Can you tell me at wich kernel version the change occured so I can start from there.
Richard
Devin Heitmueller wrote:
> On Mon, Feb 8, 2010 at 11:43 PM, Richard Lemieux <rlemieu@cooptel.qc.ca> wrote:
>> Hi,
>>
>> I got some driver crashes after upgrading to kernel 2.6.32.7. It seems that
>> activating either TBS8920 (DVB-S) and HVR950Q (ATSC) after the other one has
>> run (and is no longer in use by an application) triggers a driver crash.
>
> Hello Richard,
>
> Have you tried any other kernel version? For example, do you know
> that it works properly in 2.6.32.6?
>
> Can you bisect and see when the problem was introduced?
>
> Devin
>
next prev parent reply other threads:[~2010-02-09 13:44 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 [this message]
2010-02-09 15:42 ` Devin Heitmueller
2010-02-09 18:32 ` Richard Lemieux
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=4B7166A5.8050402@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