On 2/28/08, Dominique P. <[EMAIL PROTECTED]> wrote:
> Hi
>
> I have exactly the same problem, all seems fine on vdr until I start one
> recording that use the second timer , I got thousand of message like this
> one , it seems stg is not well loaded some time, I just have to shutdown vdr,
> I can see that device disconnect itself on dmesg and all is OK when starting
> vdr another time ...
>
> hope somebody have a solution for that
>
> Best regards
>
> kernel = 2.6.22.18-desktop586-1mdv on mandriva 2008.0
>
>
>
> Le Thursday 28 February 2008 20:11:39 Philip Pemberton, vous avez écrit :
> > 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.
> >
> > [EMAIL PROTECTED]:~$ 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.
>
>
> _______________________________________________
> linux-dvb mailing list
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>

1: I got a mailer-daemon reply saing that my ip was spamfiltred (I use
gmail?) when replying to what kernel i use.
My kernel is 2.6.22-14-generic

2: This morning I hade L__ on my second tuner.
some more mt2060 I2C read failed in dmesg.

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

Reply via email to