From: "Nathan Becker" <nathanbecker@gmail.com>
To: "David Brownell" <david-b@pacbell.net>
Cc: linux-usb-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] Re: USB 2.0 ehci failure with large amount of RAM (4GB) on x86_64
Date: Sat, 13 May 2006 10:17:31 -0700 [thread overview]
Message-ID: <2151339d0605131017v6fdda8edt334f43fb62e3f253@mail.gmail.com> (raw)
In-Reply-To: <200605122132.41410.david-b@pacbell.net>
Thanks for the patch. However, did you not get my very last message?
Checking back through my mail logs, I think it might not have been
delivered.
After claiming that the dma mask fixed the problem, I quickly
discovered that the dma was not what did it. Thus the patch you sent
does not work.
But, here is what does: If I rmmod ehci_hcd and then modprobe
ehci_hcd, it works, and I get full USB 2.0 speed. There must be
something happening in the clean-up code of the the ehci_hcd that
fixes whatever conflict I'm having. When I originally made that patch
and then reloaded the ehci_hcd module to test it, I mistakenly thought
that it was the patch that was fixing the problem. I should have
tested more thoroughly before sending the e-mail, but I got very
excited. Sorry about that. After several days of using the
rmmod/modprobe workaround, I do feel confident that it is a legitimate
fix.
next prev parent reply other threads:[~2006-05-13 17:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2151339d0605032148n5d6936ay31ab017fbabc65b3@mail.gmail.com>
2006-05-04 4:52 ` Nathan Becker
2006-05-04 5:27 ` Greg KH
2006-05-04 7:49 ` Andi Kleen
2006-05-05 0:12 ` Nathan Becker
2006-05-05 2:22 ` David Brownell
2006-05-05 5:46 ` Nathan Becker
2006-05-06 19:32 ` David Brownell
2006-05-06 20:34 ` Nathan Becker
2006-05-10 5:37 ` Nathan Becker
2006-05-10 17:04 ` Nathan Becker
2006-05-13 4:32 ` [linux-usb-devel] " David Brownell
2006-05-13 17:17 ` Nathan Becker [this message]
2006-05-16 17:29 ` Pete Zaitcev
2006-05-20 18:03 ` Will Dyson
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=2151339d0605131017v6fdda8edt334f43fb62e3f253@mail.gmail.com \
--to=nathanbecker@gmail.com \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.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
all inboxes | Powered by JetHome®