public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonas Anden <jonas@anden.nu>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] [PATCH] Nova-T 500 issues - losing one tuner
Date: Mon, 04 Feb 2008 19:51:22 +0100	[thread overview]
Message-ID: <1202151082.9955.1.camel@anden.nu> (raw)
In-Reply-To: <1202149689.6981.10.camel@anden.nu>

Hmm... typical, isn't it? Just about ten minutes after I've sent out the
patch, the second tuner died again. It appears this is *not* enough to
fix the issue. Please discard the previous mail.

  // J

On Mon, 2008-02-04 at 19:28 +0100, Jonas Anden wrote:
> Hi all, 
> 
> > I have a hunch about this problem...
> ...
> > This, ... leads me to believe that this is timer-induced. Something
> > can't keep up. Adding debugging makes the operations slightly slower
> > (the module needs to do additional IO to speak to syslogd), and this
> > delay seems to be enough to keep it operational.
> 
> Attached is an extremely simple patch which seems to resolve the issue
> for me. Before turning streaming on/off, I have inserted a tiny delay or
> 10 ms-
> 
> Just using 'debug=1' wasn't enough to keep tuner 2 from dying. I set it
> up yesterday morning with debug=1, and when I got back home in the
> evening the second tuner was dead again. I then made the attached patch
> and the system has been stable since then (~24 hrs).
> 
> I also made a slight change by removing a "| 0x00" from the code. It
> performs absolutely nothing (and is probably removed by the compiler in
> optimization) but confuse when reading the code, imho... Patrick, if you
> really want it there I can recreate the patch with the or statement
> back ;)
> 
> Feel free to try it out.
> 
>   // J
> _______________________________________________
> linux-dvb mailing list
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

      reply	other threads:[~2008-02-04 18:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BC723861-F3E2-4B1C-BA54-D74B8960579A@firshman.co.uk>
     [not found] ` <47A38A25.2030804@firshman.co.uk>
     [not found]   ` <1201902231.935.12.camel@youkaida>
     [not found]     ` <200802021020.20298.shaun@saintsi.co.uk>
2008-02-03  9:39       ` [linux-dvb] Nova-T 500 issues - losing one tuner Jonas Anden
2008-02-03 11:37         ` Shaun
2008-02-03 21:38           ` Nicolas Will
2008-02-04 19:24             ` Shaun
2008-02-03 12:27         ` Ben Firshman
2008-02-03 21:36         ` Nicolas Will
2008-02-04 18:28         ` [linux-dvb] [PATCH] " Jonas Anden
2008-02-04 18:51           ` Jonas Anden [this message]

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=1202151082.9955.1.camel@anden.nu \
    --to=jonas@anden.nu \
    --cc=linux-dvb@linuxtv.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