From: Jonas Anden <jonas@anden.nu>
To: Nicolas Will <nico@youplala.net>
Cc: linux-dvb <linux-dvb@linuxtv.org>
Subject: Re: [linux-dvb] Very quiet around Nova-T 500
Date: Tue, 19 Feb 2008 22:56:11 +0100 [thread overview]
Message-ID: <1203458171.8019.20.camel@anden.nu> (raw)
In-Reply-To: <1202762738.8087.8.camel@youkaida>
> > There is not a lot being said about the Nova-T 500 the last week.
> > Don´t know if that is a good (coders coding) or a bad (nothin
> > happening)
>
> Or coders busy on other code, or coders who ran out of ideas, or coders
> enjoying life, etc.
..or just waiting for the problem to reappear ;( The trouble with the
second tuner dying is tricky (for me) to isolate.
As a workaround, enabling full debug (debug=15) on the dvb_usb_dib0700
module has made my system rock solid. I turned on debugging to try to
isolate the issue, but with debugging enabled the problem does not
appear (at least not on my system).
I haven't really figured out *what* in the debug code is helping yet,
but I still suspect that this is timing-related and the debug code
simply slows things down a bit. Enabling debugging will put a whole lot
of "junk" in your system log files, but at least the second tuner wont
die on you. If you go this path, make sure your log rotation works as it
should -- my weekly rotated logs are up to 130 MB in size ;)
// J
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-02-19 21:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 20:07 [linux-dvb] Very quiet around Nova-T 500 Patrik Hansson
2008-02-11 20:45 ` Nicolas Will
2008-02-19 21:56 ` Jonas Anden [this message]
2008-02-19 22:48 ` Nicolas Will
2008-02-20 0:12 ` hermann pitton
2008-02-20 7:12 ` Nicolas Will
2008-02-20 15:14 ` hermann pitton
2008-02-25 17:00 ` Patrik Hansson
2008-02-20 7:38 ` Patrik Hansson
2008-02-20 9:25 ` Nicolas Will
2008-02-20 9:36 ` Jonas Anden
2008-02-20 9:43 ` Nicolas Will
2008-02-20 11:39 ` Patrik Hansson
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=1203458171.8019.20.camel@anden.nu \
--to=jonas@anden.nu \
--cc=linux-dvb@linuxtv.org \
--cc=nico@youplala.net \
/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