public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Will <nico@youplala.net>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] Nova-T 500 issues - losing one tuner
Date: Tue, 11 Mar 2008 11:20:01 +0000	[thread overview]
Message-ID: <1205234401.7463.10.camel@acropora> (raw)
In-Reply-To: <20080311110707.GA15085@mythbackend.home.ivor.org>


On Tue, 2008-03-11 at 11:07 +0000, ivor@ivor.org wrote:
> Not sure if this helps or adds that much to the discussion... (I think
> this was concluded before)
> But I finally switched back to kernel 2.6.22.19 on March 5th (with
> current v4l-dvb code) and haven't had any problems with the Nova-t 500
> since. Running mythtv with EIT scanning enabled.
> 
> Looking in the kernel log I see a single mt2060 read failed message on
> March 6th and 9th and a single mt2060 write failed on March 8th. These
> events didn't cause any problems or cause the tuner or mythtv to fail
> though.

ah. 

So this begs the question:

What changed between 2.6.22 and 2.6.24? huh... funny, heh?

So, if 2.6.24 is finger pointed, I'm interested in a solution, as I have
a planned upgrade to it in about a month's time.

Nico




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

  reply	other threads:[~2008-03-11 11:20 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-11 11:07 [linux-dvb] Nova-T 500 issues - losing one tuner ivor
2008-03-11 11:20 ` Nicolas Will [this message]
2008-03-11 15:55   ` Patrik Hansson
2008-03-13 11:39     ` Ivor Hewitt
2008-03-11 22:03 ` Philip Pemberton
2008-03-11 22:10   ` Nicolas Will
     [not found]     ` <b04e7ceb0803111537o50b6478ep867d9c26f79b299a@mail.gmail.com>
2008-03-11 22:37       ` Luis Cidoncha
2008-03-12 17:01         ` Ben Firshman
2008-03-12 17:56           ` Patrik Hansson
2008-03-15 21:28     ` Philip Pemberton
2008-03-15 23:00       ` Sid Boyce
2008-03-16  0:22         ` Philip Pemberton
2008-03-12 19:40 ` Henrik Beckman
2008-03-12 19:48   ` Patrik Hansson
     [not found]   ` <8ad9209c0803121248u24f0621es9877b3c827c4e932@mail.gmail.com>
2008-03-13 13:53     ` Henrik Beckman
  -- strict thread matches above, loose matches on Subject: below --
2008-03-14 16:41 Ivor Hewitt
2008-03-15 18:38 ` Patrik Hansson
2008-03-15 19:42   ` Ivor Hewitt
2008-03-15 20:22     ` Nicolas Will
2008-03-15 21:42     ` Patrik Hansson
2008-03-16  9:40       ` Patrik Hansson
2008-03-16 13:04         ` Patrik Hansson
2008-03-19  9:18     ` Luis Cidoncha
2008-03-05 20:49 Shaun
2008-02-06 10:43 Christophe Boyanique
2008-02-06 19:29 ` Nicolas Will
2008-02-06 19:56   ` Nicolas Will
2008-02-06 20:34     ` Jonas Anden
2008-02-07 15:12       ` Christophe Boyanique
2008-02-07 16:51         ` Jonas Anden
2008-02-10 15:43           ` Patrik Hansson
2008-02-26 19:18             ` Philip Pemberton
2008-02-26 19:37               ` Patrik Hansson
2008-02-27 19:38                 ` Patrik Hansson
2008-02-28 19:11                   ` Philip Pemberton
2008-02-28 19:43                     ` Nicolas Will
2008-03-02 19:04                       ` Philip Pemberton
2008-02-28 20:10                     ` Dominique P.
2008-02-29  7:22                       ` Patrik Hansson
2008-02-29 21:31                     ` Philip Pemberton
2008-03-01  7:23                       ` Nicolas Will
2008-03-02  8:09                         ` Philip Pemberton
2008-03-02 12:19                           ` Patrik Hansson
2008-03-02 13:20                             ` Philip Pemberton
2008-03-02 14:09                             ` Philip Pemberton
2008-03-02 17:31                               ` Nicolas Will
2008-03-02 18:19                                 ` Philip Pemberton
2008-03-02 21:49                                   ` Philip Pemberton
2008-03-02 23:02                                     ` Nicolas Will
2008-03-02 23:07                                     ` Darren Salt
2008-03-03  0:18                                       ` Nicolas Will
2008-03-03 22:00                                         ` Philip Pemberton
2008-03-02 23:03                                   ` Darren Salt
2008-03-03  7:06                                     ` Philip Pemberton
2008-03-04 23:03               ` Ben Firshman
2008-03-12 20:34                 ` Patrik Hansson
2008-03-12 20:38                   ` Patrik Hansson
2008-04-05 11:34                     ` Patrik Hansson
2008-04-08 14:23                       ` daniel åkerud
2008-04-08 16:25                         ` Patrik Hansson
2008-04-09 12:35                           ` daniel åkerud
     [not found]                       ` <b04e7ceb0804120733t5d87eb1bh2dc88f57f1949afd@mail.gmail.com>
2008-04-12 14:33                         ` Luis Cidoncha
2008-02-25 19:25 ` Christophe Boyanique
2008-02-25 21:34   ` Ben Firshman
2008-02-25 22:14     ` Christophe Boyanique
2008-02-26  7:12   ` Philip Pemberton
     [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       ` 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

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=1205234401.7463.10.camel@acropora \
    --to=nico@youplala.net \
    --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