From: Helmut Toplitzer <pvrusb2@toplitzer.net>
To: Rene Herman <rene.herman@keyaccess.nl>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
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: Fri, 20 Jan 2006 16:44:19 +0100 [thread overview]
Message-ID: <200601201644.19916.pvrusb2@toplitzer.net> (raw)
In-Reply-To: <43D0FD98.4080406@keyaccess.nl>
> experiencing the same problem after all. I feel so alone again...
However, at least temperatur goes slightly up (2K) wenn i load ehci-hcd
and I can confirm the ASYNC problem:
bus pci, device 0000:00:10.3 (driver 10 Dec 2004)
EHCI Host Controller
EHCI 1.00, hcd state 1
ownership 01000001 linux
SMI sts/enable 0xe0080000
structural params 0x00003206
capability params 0x00006872
status 0008 FLR
command 010009 (park)=0 ithresh=1 period=256 RUN
intrenable 37 IAA FATAL PCD ERR INT
uframe 0bb4
port 1 status 001000 POWER sig=se0
port 2 status 001000 POWER sig=se0
port 3 status 001000 POWER sig=se0
port 4 status 001005 POWER sig=se0 PE CONNECT
port 5 status 001000 POWER sig=se0
port 6 status 001000 POWER sig=se0
irq normal 963 err 0 reclaim 452 (lost 17)
complete 964 unlink 0
bus pci, device 0000:00:10.3 (driver 10 Dec 2004)
EHCI Host Controller
EHCI 1.00, hcd state 1
ownership 01000001 linux
SMI sts/enable 0xe0080000
structural params 0x00003206
capability params 0x00006872
status a008 Async Recl FLR
command 010009 (park)=0 ithresh=1 period=256 RUN
intrenable 37 IAA FATAL PCD ERR INT
uframe 3851
port 1 status 001000 POWER sig=se0
port 2 status 001000 POWER sig=se0
port 3 status 001000 POWER sig=se0
port 4 status 001005 POWER sig=se0 PE CONNECT
port 5 status 001000 POWER sig=se0
port 6 status 001000 POWER sig=se0
irq normal 963 err 0 reclaim 452 (lost 17)
complete 964 unlink 0
So there at least some similarities.
Helmut
--
My GNUpg fingerprint http://www.gnupg.org
4563 F4FB 0B7E 8698 53CD 00E9 E319 35BD 6A91 1656
next prev parent reply other threads:[~2006-01-20 15:44 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 ` [linux-usb-devel] " Rene Herman
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 [this message]
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=200601201644.19916.pvrusb2@toplitzer.net \
--to=pvrusb2@toplitzer.net \
--cc=bzolnier@gmail.com \
--cc=dbrownell@users.sourceforge.net \
--cc=linux-ide@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=rene.herman@keyaccess.nl \
--cc=stern@rowland.harvard.edu \
/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).