public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: uTaR <utar101@gmail.com>
To: linux-media@vger.kernel.org
Subject: Hauppauge NOVA-T 500 falls over after warm reboot
Date: Tue, 03 Mar 2009 19:45:03 +0000	[thread overview]
Message-ID: <49AD88BF.30507@gmail.com> (raw)


Just thought I would report some unusual behaviour I am seeing on my
Nova-T 500.  Basically the card works fine with a cold boot but falls
over rapidly after a warm reboot.

This started after I compiled the latest v4l source tree (as at 22 Feb
09) due to me adding a Tevii S650 to my system.  At first I thought it
was the Tevii which was causing the problem but testing showed the Nova
falls over irrespective of if the Tevii is attached.

I'm running Ubuntu with 2.6.27-11 and I never had this issue with v4l
running "out of the box."

Sample of the log after the Nova falls over follows:

[  117.920002] ehci_hcd 0000:05:00.2: force halt; handhake f88f4c14
00004000 00000000 -> -110
[  129.412342] mt2060 I2C write failed
[  132.412253] mt2060 I2C write failed
[  133.713596] mt2060 I2C write failed
[  136.712264] mt2060 I2C write failed
[  138.004603] mt2060 I2C write failed
[  141.004564] mt2060 I2C write failed
[  147.177361] mt2060 I2C write failed
[  150.176124] mt2060 I2C write failed
[  171.026988] mt2060 I2C write failed
[  171.041701] mt2060 I2C write failed (len=2)
[  171.041824] mt2060 I2C write failed (len=6)
[  171.041922] mt2060 I2C read failed

             reply	other threads:[~2009-03-03 19:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-03 19:45 uTaR [this message]
2009-03-03 20:29 ` Hauppauge NOVA-T 500 falls over after warm reboot Eduard Huguet
2009-03-03 21:08   ` uTaR
2009-03-04  8:26     ` Eduard Huguet
2009-03-05 19:57       ` utar
2009-03-05 20:43         ` Eduard Huguet

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=49AD88BF.30507@gmail.com \
    --to=utar101@gmail.com \
    --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