All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antti Palosaari <crope@iki.fi>
To: Marx <acc.for.news@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: ITE9135 on AMD SB700 - ehci_hcd bug
Date: Wed, 03 Oct 2012 15:16:05 +0300	[thread overview]
Message-ID: <506C2C85.5090108@iki.fi> (raw)
In-Reply-To: <f5itj9-4o9.ln1@wuwek.kopernik.gliwice.pl>

On 10/03/2012 01:55 PM, Marx wrote:
> On 23.09.2012 18:22, Antti Palosaari wrote:
>> On 09/16/2012 05:23 PM, Antti Palosaari wrote:
>>> On 09/12/2012 09:32 AM, Marx wrote:
>>>> Hello
>>>> I'm trying to use dual DVB-T tuner based on ITE9135 tuner. I use Debian
>>>> kernel 3.5-trunk-686-pae. My motherboard is AsRock E350M1 (no USB3
>>>> ports).
>>>> Tuner is detected ok, see log at the end of post.
>>>>
>>>> When I try to scan channels, bug happens:
>>>> Sep 11 17:16:31 wuwek kernel: [ 209.291329] ehci_hcd 0000:00:13.2:
>>>> force halt; handshake f821a024 00004000 00000000 -> -110
>>>> Sep 11 17:16:31 wuwek kernel: [ 209.291401] ehci_hcd 0000:00:13.2: HC
>>>> died; cleaning up
>>>> Sep 11 17:16:31 wuwek kernel: [ 209.291606] usb 2-3: USB disconnect,
>>>> device number 2
>>>> Sep 11 17:16:41 wuwek kernel: [ 219.312848] dvb-usb: error while
>>>> stopping stream.
>>>> Sep 11 17:16:41 wuwek kernel: [ 219.320585] dvb-usb: ITE 9135(9006)
>>>> Generic successfully deinitialized and disconnected.
>>>>
>>>> After trying many ways I've read about problems with ehci on SB700
>>>> based
>>>> boards and switched off ehci via command
>>>> sh -c 'echo -n "0000:00:13.2" > unbind'
>>>> and now ehci bug doesn't happen. Of course I can see only one tuner and
>>>> in slower USB mode (see log at the end). But now I can scan succesfully
>>>> without any errors.
>>>>
>>>> Of course it isn't acceptable fix for my problem. Drivers for ITE9135
>>>> seems ok, but there is a problem with ehci_hcd on my motherboard.
>>>> I would like to know what can I do to fix my problem.
>>>
>>> I am quite sure dvb_usb_v2 fixes that. Test latest tree.
>>>
>>> Antti
>>>
>>
>> Test results please?
>
> I've replaced motherboard (no AMD chipset) and this problem disappeared.
> Unfortunatelly there were some problem with newsgate on gmane and I
> didn't receive your reply on time. Now I don't have this motherboard,
> but I can confirm ITE9135 drivers now works ok, so this problem was with
> USB driver.

I have also AMD SB700 USB bridge and saw these errors. I suspect it race 
condition in DVB USB which happens in certain situation / combinations. 
I added one mutex to DVB USB v2 due to that...

> Now I have some small problem with ITE9135 driver. I use dual tuner.
> When I restart computer while the card is connected then disconnect and
> connect card again, I have four devices in /dev/dvb instead of two.
> Is it known bug and is fixed or I should attach some logs?
> Marx

New for me. It could be ITE9135 driver bug or DVB USB bug. I have to 
test it.

regards
Antti

-- 
http://palosaari.fi/

      reply	other threads:[~2012-10-03 12:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-12  6:32 ITE9135 on AMD SB700 - ehci_hcd bug Marx
2012-09-13 21:01 ` Malcolm Priestley
2012-09-16 14:23 ` Antti Palosaari
2012-09-23 16:22   ` Antti Palosaari
2012-10-03 10:55     ` Marx
2012-10-03 12:16       ` Antti Palosaari [this message]

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=506C2C85.5090108@iki.fi \
    --to=crope@iki.fi \
    --cc=acc.for.news@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 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.