From: Philip Pemberton <lists@philpem.me.uk>
To: Patrik Hansson <patrik@wintergatan.com>
Cc: linux-dvb <linux-dvb@linuxtv.org>
Subject: Re: [linux-dvb] Nova-T 500 issues - losing one tuner
Date: Thu, 28 Feb 2008 19:11:39 +0000 [thread overview]
Message-ID: <47C7076B.6060903@philpem.me.uk> (raw)
In-Reply-To: <8ad9209c0802271138o2e0c00d3o36ec16332d691953@mail.gmail.com>
Patrik Hansson wrote:
> 20:37:40 up 1 day, 8 min ...and counting, both tuners working fine.
>
> There are two:
> [14153.150380] mt2060 I2C read failed
> [18967.903269] mt2060 I2C read failed
> recorded in dmesg but nothing fatal.
philpem@dragon:~$ uptime
19:06:28 up 23:42, 3 users, load average: 1.19, 1.22, 1.18
And the log is full of this crap:
Feb 28 06:29:13 dragon syslogd 1.5.0#1ubuntu1: restart.
Feb 28 06:29:13 dragon kernel: [39865.332785] cx24123_readreg: reg=0x14
(error=-121)
Feb 28 06:29:13 dragon kernel: [39865.333946] cx24123_readreg: reg=0x20
(error=-121)
Feb 28 06:29:13 dragon kernel: [39865.432586] cx24123_readreg: reg=0x14
(error=-121)
Feb 28 06:29:13 dragon kernel: [39865.433733] cx24123_readreg: reg=0x20
(error=-121)
Feb 28 06:29:13 dragon kernel: [39865.532380] cx24123_readreg: reg=0x14
(error=-121)
Feb 28 06:29:13 dragon kernel: [39865.533473] cx24123_readreg: reg=0x20
(error=-121)
Feb 28 06:29:13 dragon kernel: [39865.632210] cx24123_readreg: reg=0x14
(error=-121)
Feb 28 06:29:13 dragon kernel: [39865.633301] cx24123_readreg: reg=0x20
(error=-121)
Feb 28 06:29:13 dragon kernel: [39865.731998] cx24123_readreg: reg=0x14
(error=-121)
Feb 28 06:29:13 dragon kernel: [39865.733092] cx24123_readreg: reg=0x20
(error=-121)
Feb 28 06:29:14 dragon kernel: [39865.831820] cx24123_readreg: reg=0x14
(error=-121)
Feb 28 06:29:14 dragon kernel: [39866.374256] mt2060 I2C write failed (len=2)
Feb 28 06:29:14 dragon kernel: [39866.374262] mt2060 I2C write failed (len=6)
Feb 28 06:29:14 dragon kernel: [39866.374264] mt2060 I2C read failed
Feb 28 06:29:14 dragon kernel: [39866.382298] mt2060 I2C read failed
Feb 28 06:29:14 dragon kernel: [39866.390210] mt2060 I2C read failed
Feb 28 06:29:14 dragon kernel: [39866.398195] mt2060 I2C read failed
Feb 28 06:29:14 dragon kernel: [39866.406181] mt2060 I2C read failed
Feb 28 06:29:14 dragon kernel: [39866.414175] mt2060 I2C read failed
Feb 28 06:29:14 dragon kernel: [39866.422213] mt2060 I2C read failed
Feb 28 06:29:14 dragon kernel: [39866.430162] mt2060 I2C read failed
And the tuner is utterly shot. It worked for most of one recording, then
promptly died.
*sigh*
Patrik, just out of curiosity, what kernel are you running?
I'm running 2.6.24-8-generic on Mythbuntu 8.04 alpha 2 and thinking about
downgrading to an earlier kernel.
--
Phil. | (\_/) This is Bunny. Copy and paste Bunny
lists@philpem.me.uk | (='.'=) into your signature to help him gain
http://www.philpem.me.uk/ | (")_(") world domination.
_______________________________________________
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-28 19:11 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 10:43 [linux-dvb] Nova-T 500 issues - losing one tuner 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 [this message]
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
-- 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-11 11:07 ivor
2008-03-11 11:20 ` Nicolas Will
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
2008-03-05 20:49 Shaun
[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=47C7076B.6060903@philpem.me.uk \
--to=lists@philpem.me.uk \
--cc=linux-dvb@linuxtv.org \
--cc=patrik@wintergatan.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.