From: Nicolas Will <nico@youplala.net>
To: linux-media@vger.kernel.org
Subject: Re: Nova-T 500 does not survive reboot
Date: Thu, 30 Apr 2009 11:47:18 +0100 [thread overview]
Message-ID: <1241088438.5237.16.camel@acropora> (raw)
In-Reply-To: <loom.20090430T101124-541@post.gmane.org>
On Thu, 2009-04-30 at 10:16 +0000, Eduard Huguet wrote:
> Nicolas Will <nico <at> youplala.net> writes:
>
> >
> > Hello all,
> >
> > I am running an hg clone from a few days ago with firmware 1.20 on a
> > 64-bit Ubuntu Intrepid (2.6.27 kernel).
> >
> > I have noticed that for some time now the card/driver/firmware
> > combination does not like warm reboots.
> >
> > If I reboot the system and try to use any Nova-T 500 tuner, I
> > immediately get the mt2060 I2C errors.
> >
> > If I completely shut down the system, remove the power, then reboot, all
> > is fine.
> >
> > I have missed most of the linux-media traffic, I was still stuck on
> > linux-dvb. Have I missed some discussions about this?
> >
> > Thanks!
> >
> > Nico
> Hi, Nicholas
>
> I posted the very same thing 3 days ago:
> http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/4973
Argh, I missed it (I don't really like gmame's archiving... I will need
to get used to it).
I have the same :
Apr 29 22:42:41 favia kernel: [ 72.272045] ehci_hcd 0000:07:01.2: force halt; handhake ffffc20000666814 00004000 00000000 -> -110
then
Apr 29 22:43:02 favia kernel: [ 92.900094] mt2060 I2C write failed
Apr 29 22:43:02 favia kernel: [ 92.905830] mt2060 I2C write failed (len=2)
Apr 29 22:43:02 favia kernel: [ 92.905835] mt2060 I2C write failed (len=6)
Apr 29 22:43:02 favia kernel: [ 92.905838] mt2060 I2C read failed
Apr 29 22:43:02 favia kernel: [ 92.912552] mt2060 I2C read failed
Apr 29 22:43:02 favia kernel: [ 92.920572] mt2060 I2C read failed
Apr 29 22:43:02 favia kernel: [ 92.928552] mt2060 I2C read failed
Apr 29 22:43:02 favia kernel: [ 92.936554] mt2060 I2C read failed
Apr 29 22:43:02 favia kernel: [ 92.944552] mt2060 I2C read failed
...............
and at one point I get the following before I shut down
Apr 29 22:44:27 favia kernel: [ 177.818215] dvb-usb: could not submit URB no. 0 - get them all back
Apr 29 22:44:27 favia kernel: [ 177.818222] dvb-usb: error while enabling fifo.
>
>
> This is something that has been occuring lately, since some months ago. I don't
> know when exactly was this bug introduced, but it has been in HG for a couple of
> months at least. I can remenber that other guy posted about this issue some time
> ago, but I can't find the link.
I'm with that too. I was just really busy at the time to dig into it.
>
>
> And for what I see, Janne Grunau is also having problems with the card. See what
> he have just posted...:
> http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/4973
I saw that one too, it arrived as I subscribed to the proper list.
I'm not directly concerned now, but I will be facing this too when I
will want to upgrade my system to the current Ubuntu release.
Soooooo...
What can I/we do to help track/fix this?
I'm game for a bit of testing, within reason, though, at the system is
in production.
Do you know if the issue is the same with a Nova-TD stick? If it is,
then I could be able to use debugging as an excuse to buy one, and then
add 2 tuners to the system when all is done :o)
Nico
http://www.youplala.net/linux/home-theater-pc/
next prev parent reply other threads:[~2009-04-30 10:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 5:15 Nova-T 500 does not survive reboot Nicolas Will
2009-04-30 10:16 ` Eduard Huguet
2009-04-30 10:47 ` Nicolas Will [this message]
2009-04-30 10:51 ` Nicolas Will
2009-05-05 13:24 ` Eduard Huguet
[not found] ` <1241530356.5394.2.camel@acropora>
2009-05-05 13:42 ` Eduard Huguet
-- strict thread matches above, loose matches on Subject: below --
2009-04-30 11:56 Soeren.Moch
2009-04-30 15:08 ` Nicolas Will
2009-04-30 17:27 ` Nicolas Will
2009-05-22 13:30 Soeren Moch
2009-05-24 12:43 ` 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=1241088438.5237.16.camel@acropora \
--to=nico@youplala.net \
--cc=linux-media@vger.kernel.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