From: Richard Lemieux <rlemieu@cooptel.qc.ca>
To: Andy Walls <awalls@radix.net>
Cc: Devin Heitmueller <dheitmueller@kernellabs.com>,
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: Sat, 13 Feb 2010 08:40:32 -0500 [thread overview]
Message-ID: <4B76ABD0.8050002@cooptel.qc.ca> (raw)
In-Reply-To: <1266023937.3062.17.camel@palomino.walls.org>
Hi,
I was in the process of setting up my machine so I can run any of
the tests you might ask for. First I needed a fully tested backup partition,
and then I needed to bring udev up to date. But I see that the problem
is pretty much resolved right now. As Devin said earlier I doubt I can ever
reproduce this event. Thanks very much for everything you do for the Linux
community.
Richard
Andy Walls wrote:
> Yes. But it will take me a while. I don't have a git tree, because I
> don't have high bandwidth internet yet. (The cable company's been
> delayed in laying cable to my home due to repeated snowstorms.)
>
> I just didn't want the problem to fall through the cracks. I'll submit
> something to bugzilla for now. If a user complains of this rare Ooops
> when loading firmware, the current workaround is to lengthen the timeout
> via sysfs.
>
> Regards,
> Andy
next prev parent reply other threads:[~2010-02-13 13:40 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
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 [this message]
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=4B76ABD0.8050002@cooptel.qc.ca \
--to=rlemieu@cooptel.qc.ca \
--cc=awalls@radix.net \
--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