mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zbigniew Luszpinski <zbiggy@o2.pl>
To: linux-usb@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: PROBLEM: Nvidia OHCI chipset MCP78S (Geforce 8200) hangs on > 1Mbit transfers if noapic/acpi=noirq is missing
Date: Mon, 6 Jul 2009 23:40:56 +0200	[thread overview]
Message-ID: <200907062340.56308.zbiggy@o2.pl> (raw)
In-Reply-To: <200907060211.43377.zbiggy@o2.pl>

Hello,

with my ohci usb controller problem I came to conclusion that it hangs only 
during big transfers when ohci usb controller is unable to keep up with rest 
of the system. That is why it only hangs on fast bulk/iso transfers and not 
when slow usb keyboard or mouse is used.

After being inspired by this uhci usb bugfix (which is very similar to my 
problem but in my case Nvidia does not provide any driver for windows usb. 
Just use default windows one):
http://osdir.com/ml/linux.usb.user/2002-12/msg00112.html
So I modified ohci usb driver source code (ohci-q.c, ohci-hub.c) in similar 
way by adding mdelay(5); before most of ohci_writel(...) and ohci_readl(...). 
After recompilation and reboot I used ohci usb without noapic workaround for 
much longer time without hanging. However after this modification usb hangs
immediately after hotpluging other usb device so my ugly hack did not fix all
the issues. :(

I hope I find here someone who wrote or know Linux ohci driver so he/she knows 
how to slow down ohci bulk/iso IO operations without breaking hotplug.
It looks Linux ohci driver is more aggressive on ohci IO than windows one so 
making Linux less timing demanding would help my MCP78S keep working.

have a nice day,
Zbigniew Luszpinski


       reply	other threads:[~2009-07-06 21:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200907060122.26312.zbiggy@o2.pl>
     [not found] ` <200907060211.43377.zbiggy@o2.pl>
2009-07-06 21:40   ` Zbigniew Luszpinski [this message]
2009-07-07  1:50     ` Alan Stern

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=200907062340.56308.zbiggy@o2.pl \
    --to=zbiggy@o2.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@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

all inboxes | Powered by JetHome®