From: David Brownell <david-b@pacbell.net>
To: "Rafael J. Wysocki" <rjw@sisk.pl>, Jan De Luyck <lkml@kcore.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] Re: [2.6.9-rc3] suspend-to-disk oddities
Date: Mon, 4 Oct 2004 08:04:04 -0700 [thread overview]
Message-ID: <200410040804.04382.david-b@pacbell.net> (raw)
In-Reply-To: <200410041456.27350.rjw@sisk.pl>
On Monday 04 October 2004 5:56 am, Rafael J. Wysocki wrote:
> On Monday 04 of October 2004 14:22, Jan De Luyck wrote:
> >
> > UHCI. I just did a test-suspend-resume, currently plugged
> > USB devices don't work, but it does show up in the devices
> > file. It also responds to replugging.... I don't get it.
> > I had no response whatsoever earlier. ...
>
> Have you tried booting with pci=routeirq? It may help.
I've seen strangeness on the resume path too, with devices
not responding but still being known to the kernel. What I
found odd was that I know the OHCI hardware was reinitialized
correctly, and it was just khubd that wasn't responding. So
it wouldn't even respond to unplug/replug. And this is with
known-OK IRQ settings (driver did get IRQs after resume).
There's some other stuff misbehaving still. I'm hoping to see
the simpler stuff work first -- standby and STR behaving, wakeup
by USB keyboards not ACPI power buttons -- and at that point
the remaining problems will be specific to STD. There are
enough wierd BIOS and power states with STD that making
that work first is very likely to bork the other stuff.
- Dave
prev parent reply other threads:[~2004-10-04 15:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-04 9:07 [2.6.9-rc3] suspend-to-disk oddities Jan De Luyck
2004-10-04 11:31 ` Oliver Neukum
2004-10-04 11:59 ` Jan De Luyck
2004-10-04 12:06 ` Oliver Neukum
2004-10-04 12:22 ` Jan De Luyck
2004-10-04 12:56 ` Rafael J. Wysocki
2004-10-04 15:04 ` David Brownell [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=200410040804.04382.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@kcore.org \
--cc=rjw@sisk.pl \
/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