public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
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 16:08:44 +0100	[thread overview]
Message-ID: <1241104124.5168.46.camel@acropora> (raw)
In-Reply-To: <20090430135641.91441beqhfo80o4k@www.stud.uni-hannover.de>

On Thu, 2009-04-30 at 13:56 +0200, Soeren.Moch@stud.uni-hannover.de
wrote:
> > Apr 29 22:42:41 favia kernel: [   72.272045] ehci_hcd
> 0000:07:01.2:  
> > force halt; handhake ffffc20000666814 00004000 00000000 -> -110
> > [...]
> > 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)
> 
> I had the same "ehci_hcd force halt" error when I was debugging the
> Nova-TD dual-stream-switchon-problem:
> http://www.mail-archive.com/linux-media@vger.kernel.org/msg04643.html
> 
> Reducing the urb count to 1 (as included in the patch) solved the
> "ehci_hcd force halt" issue for me.

I mention that the URB part is a quick hack.

You were asking for opinions on that, and apparently did not get any
feedback.

Time for another call?

Nico


  reply	other threads:[~2009-04-30 15:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-30 11:56 Nova-T 500 does not survive reboot Soeren.Moch
2009-04-30 15:08 ` Nicolas Will [this message]
2009-04-30 17:27   ` Nicolas Will
  -- strict thread matches above, loose matches on Subject: below --
2009-05-22 13:30 Soeren Moch
2009-05-24 12:43 ` Nicolas Will
2009-04-30  5:15 Nicolas Will
2009-04-30 10:16 ` Eduard Huguet
2009-04-30 10:47   ` Nicolas Will
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

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=1241104124.5168.46.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