From: Rene Herman <rene.herman@keyaccess.nl>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Helmut Toplitzer <pvrusb2@toplitzer.net>,
linux-ide@vger.kernel.org, dbrownell@users.sourceforge.net,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [linux-usb-devel] Re: BUG?: VIA IDE transfer-rate problem
Date: Tue, 17 Jan 2006 15:19:47 +0100 [thread overview]
Message-ID: <43CCFD03.2060605@keyaccess.nl> (raw)
In-Reply-To: <58cb370e0601170517v6fe68992ma5bdc67d5eb1e6f1@mail.gmail.com>
Bartlomiej Zolnierkiewicz wrote:
> On 1/13/06, Helmut Toplitzer <pvrusb2@toplitzer.net> wrote:
>> I've got a question about a small experiment I made:
>> I tried to find out the transfer-rate of my hd by useing
>> hdparm -t /dev/hda
>> and got changing transferrates starting from
>>
>> 37MB/s with CPU not utilized
>> 55MB/s with CPU 100% utilized
[ ... ]
>> 22MB/s with ehci-hcd loaded and a device already initilized
>> 55MB/s with ehci-hcd loaded and CPU 100% utilized
>> (see log1/log2)
>
> As discussed in this thread:
> http://marc.theaimsgroup.com/?l=linux-kernel&m=111765523627674&w=2
>
> It seems that the problem is caused by flakey USB chipset
> thus IDE folks cannot do much about it, sorry.
Indeed. It seems VIA EHCI controllers are quite simply terminally
broken. And Helmut is also seeing problems with a soundcard.
Helmut, I believe it would be better if you could try the first of these
tests without the VIA USB2 controller even plugged in and then see if
you still get that effect.
(Bartlomiej, note by the way that in my case it's not a VIA southbridge
but an AMD756, although I believe that might be quite similar to old VIA
southbridges in so far as that VIA looked at that one)
>> So it looks like CPU/USB/IDE is in some interaction. Any
>> ideas what to do against this. My current kernel is
>> 2.6.15
As said, if you can be bothered, taking the VIA EHCI controller out of
the picture would be interesting. Personally, I only experience the
throughput drop with ehci-loaded and in use or used, fixed by unloading
ehci-hcd so I can't test more than that, but I wouldn't be terribly
surprised if completely taking out the USB controller would solve other
problems as well. As clear by now, that chip is doing some _very_
strange things to the bus.
Rene.
next prev parent reply other threads:[~2006-01-17 14:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-13 18:09 BUG?: VIA IDE transfer-rate problem Helmut Toplitzer
2006-01-13 18:10 ` Helmut Toplitzer
2006-01-16 17:49 ` Helmut Toplitzer
2006-01-17 9:55 ` Gentoopower
2006-01-17 10:22 ` Helmut Toplitzer
2006-01-17 13:17 ` Bartlomiej Zolnierkiewicz
2006-01-17 14:19 ` Rene Herman [this message]
2006-01-17 16:03 ` Helmut Toplitzer
2006-01-18 10:27 ` Bartlomiej Zolnierkiewicz
2006-01-18 14:36 ` Helmut Toplitzer
2006-01-18 15:54 ` [linux-usb-devel] " David Brownell
2006-01-18 16:13 ` Bartlomiej Zolnierkiewicz
2006-01-18 23:41 ` Helmut Toplitzer
2006-01-19 1:05 ` [linux-usb-devel] " Alan Cox
2006-01-19 7:21 ` Helmut Toplitzer
2006-01-19 11:51 ` Erik Slagter
2006-01-19 12:19 ` Bartlomiej Zolnierkiewicz
2006-01-19 13:31 ` Helmut Toplitzer
2006-01-19 19:59 ` Helmut Toplitzer
2006-01-19 21:29 ` [linux-usb-devel] " Alan Stern
2006-01-20 11:27 ` Helmut Toplitzer
2006-01-20 15:11 ` Rene Herman
2006-01-20 15:44 ` Helmut Toplitzer
2006-01-22 17:16 ` Rene Herman
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=43CCFD03.2060605@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=bzolnier@gmail.com \
--cc=dbrownell@users.sourceforge.net \
--cc=linux-ide@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=pvrusb2@toplitzer.net \
/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;
as well as URLs for NNTP newsgroup(s).