public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: linux-kernel@vger.kernel.org
Cc: David Brownell <david-b@pacbell.net>,
	linux-usb-devel@lists.sourceforge.net,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [linux-usb-devel] 2.6.10-rc1-mm4: USB storage not working on AMD64
Date: Wed, 10 Nov 2004 15:57:51 +0100	[thread overview]
Message-ID: <200411101557.51057.rjw@sisk.pl> (raw)
In-Reply-To: <200411100558.45934.david-b@pacbell.net>

On Wednesday 10 of November 2004 14:58, David Brownell wrote:
> On Wednesday 10 November 2004 02:54, Rafael J. Wysocki wrote:
> > Hi,
> > 
> > There seems to be a problem in 2.6.10-rc1-mm4 with either USB storage (eg 
a 
> > pendrive) or hotplug on AMD64 (NForce3 chipset, ohci-hcd, SuSE 9.1).
> > Namely,  
> > if a USB pendrive is inserted into a socket, the kernel does not even 
detect 
> > it.  Here's what appears in dmesg after it's inserted:
> > 
> > ohci_hcd 0000:00:02.0: wakeup
> > 
> > Other USB devices (eg a mouse) seem to work normally.
> 
> I recently posted several USB PM fixes that make things work better
> in my testing, and it sounds like they'd probably help here too.

Are they available as stand-alone patches?  I'd like to test ...

Greets,
RJW

-- 
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
		-- Lewis Carroll "Alice's Adventures in Wonderland"

  reply	other threads:[~2004-11-10 15:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-10 10:54 2.6.10-rc1-mm4: USB storage not working on AMD64 Rafael J. Wysocki
2004-11-10 13:58 ` [linux-usb-devel] " David Brownell
2004-11-10 14:57   ` Rafael J. Wysocki [this message]
2004-11-10 15:36     ` David Brownell
2004-11-10 23:42       ` Rafael J. Wysocki
2004-11-10 15:52         ` David Brownell

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=200411101557.51057.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=akpm@osdl.org \
    --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