From: David Brownell <david-b@pacbell.net>
To: "Nathan Becker" <nathanbecker@gmail.com>
Cc: 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: Sat, 6 May 2006 12:32:51 -0700 [thread overview]
Message-ID: <200605061232.52303.david-b@pacbell.net> (raw)
In-Reply-To: <2151339d0605042246n1e40a496l8af646218edc781e@mail.gmail.com>
On Thursday 04 May 2006 10:46 pm, Nathan Becker wrote:
> Yes, GART_IOMMU is already turned on. Do you want me to send more
> detailed debugging messages?
And when you tell the kernel to only use 2 GB, it works again right?
Just trying to rule out hardware or hardware-init bugs.
Maybe you could change both dma masks to be 31 bits and then force the
IOMMU active, so it gives out addresses below 2GB. You should be able
to make it so that the EHCI controller never sees addresss with the
high bit set, making your 4 GB config act like a 2 GB one (via IOMMU).
Which one hopes means "working" ... it'd be good to know a workaround!
This isn't neceessarily a variant of that known NForce silicon bug, but you
could help confirm that by changing the "3strikes" message so it prints
out urb->transfer_dma ... and maybe make qh_completions() dump the dma
addresses of the qh and qtd too (iff urb->status becomes -EPROTO).
next prev parent reply other threads:[~2006-05-06 19:32 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
2006-05-05 5:46 ` Nathan Becker
2006-05-06 19:32 ` David Brownell [this message]
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=200605061232.52303.david-b@pacbell.net \
--to=david-b@pacbell.net \
--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