mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Nathan Becker" <nathanbecker@gmail.com>
To: "David Brownell" <david-b@pacbell.net>
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: Wed, 10 May 2006 10:04:59 -0700	[thread overview]
Message-ID: <2151339d0605101004l4a2153d4h40ec7db907ae5d43@mail.gmail.com> (raw)
In-Reply-To: <2151339d0605092237m4ef4e835k16b8c779f6ad7046@mail.gmail.com>

In my last message I sent a patch that I thought fixed the problem.

I made a mistake in my testing.  It turns out that my patch doesn't
have an effect on this problem.  What I discovered was a workaround: 
If I rmmod ehci-hcd and then modprobe it back in, usb 2.0 it works. 
That's what I did when I tested my patched version, so I mistakenly
thought it was my patch that fixed it.

So it seems that there is something that happens when the ehci-hcd
shuts down that helps initialize it to work properly.  What could it
be?

  reply	other threads:[~2006-05-10 17:05 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 ` 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 [this message]
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=2151339d0605101004l4a2153d4h40ec7db907ae5d43@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®