From: David Brownell <david-b@pacbell.net>
To: Greg KH <greg@kroah.com>, Nathan Becker <nathanbecker@gmail.com>
Cc: ak@suse.de, linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net
Subject: Re: USB 2.0 ehci failure with large amount of RAM (4GB) on x86_64
Date: Thu, 4 May 2006 19:22:50 -0700 [thread overview]
Message-ID: <200605041922.52243.david-b@pacbell.net> (raw)
In-Reply-To: <20060504052751.GA23054@kroah.com>
> On Wed, May 03, 2006 at 09:52:11PM -0700, Nathan Becker wrote:
> > Hi,
> >
> > I recently added two more memory modules to my Gigabyte K8NXP-SLI
> > motherboard, bringing the total up to 4GB. I had 2GB previously and
> > things were running well with kernel 2.6.16.9 x86_64. The CPU is an
> > AMD 4800+ X2.
> >
> > After the upgrade, USB 2.0 stopped working...
There's an erratum in NF4 parts affecting certain EHCI accesses to
memory addresses over the 2GB mark, and you might be seeing this.
Presumably you're running with the GART IOMMU? If not, then turn
that on. Maybe even turn on IOMMU_DEBUG.
Another experiment might be taking the PCI_VENDOR_ID_NVIDIA case
in drivers/usb/host/ehci-pci.c and adding a call to dma_set_mask()
in addition to the existing call.
- Dave
next prev parent reply other threads:[~2006-05-05 2:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2151339d0605032148n5d6936ay31ab017fbabc65b3@mail.gmail.com>
2006-05-04 4:52 ` USB 2.0 ehci failure with large amount of RAM (4GB) on x86_64 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 [this message]
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
2006-05-16 17:29 ` Pete Zaitcev
2006-05-20 18:03 ` Will Dyson
2006-05-16 22:37 Biker
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=200605041922.52243.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=ak@suse.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=nathanbecker@gmail.com \
/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