mirror of https://lore.kernel.org/lkml/
 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,
	Pavel Machek <pavel@suse.cz>
Subject: Re: [linux-usb-devel] 2.6.9-rc3: USB OHCI failure on suspend on AMD64
Date: Fri, 1 Oct 2004 10:02:20 +0200	[thread overview]
Message-ID: <200410011002.20517.rjw@sisk.pl> (raw)
In-Reply-To: <200409301458.01099.david-b@pacbell.net>

On Thursday 30 of September 2004 23:58, David Brownell wrote:
> On Thursday 30 September 2004 1:51 pm, Rafael J. Wysocki wrote:
> > Hi,
> > 
> > It seems there's a problem with USB OHCI driver that causes these traces 
to 
> > appear on suspend on an AMD64-based box:
> 
> Not all parts of power management integrate well yet with each other,
> though it's acting better.  Plus there are some OHCI updates in the USB
> patches (you'll have those in the MM tree) that help address some of
> the more perverse ways that suspend-to-disk kicks USB around, and
> a few similar usbcore changes that need re-integration with the RC3
> swsusp/pmdisk updates.
> 
> Keep using the "rmmod" workaround for now.  And don't combine
> CONFIG_USB_SUSPEND with suspend-to-{disk,ram} unless you're
> feeling like debugging the results.

I'm doing just this.  And reporting. ;-)

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-10-01  7:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-30 20:51 Rafael J. Wysocki
2004-09-30 21:11 ` Pavel Machek
2004-09-30 21:58 ` [linux-usb-devel] " David Brownell
2004-10-01  8:02   ` Rafael J. Wysocki [this message]

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=200410011002.20517.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=pavel@suse.cz \
    /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

Powered by JetHome