From: Rob Landley <rob@landley.net>
To: Brad Campbell <brad@wasp.net.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Process in D state with USB and swsuspsp
Date: Sun, 27 Jun 2004 03:50:46 -0500 [thread overview]
Message-ID: <200406270350.46641.rob@landley.net> (raw)
In-Reply-To: <40DE5BC0.7080206@wasp.net.au>
On Sunday 27 June 2004 00:31, Brad Campbell wrote:
> Rob Landley wrote:
> > As I said, I realise that unplugging even a USB adapter with the machine
> > is suspended is Not A Good Thing. But it's likely to be a common thing
> > among people who can't figure out after the fact "oh yeah, that's what's
> > going wrong"...
>
> Most of us that use swsusp regularly have our pre-suspend script unload usb
> before suspend to prevent exactly this sort of behaviour.
> I also unload PCMCIA.
>
> If there is something using these devices that prevents unloading, then my
> script notifies me that I'm doing something I need to stop before I
> suspend. Can't remember the last time that happened though.
>
> Check out the swsusp-devel list for further info.
Yeah, I could, I just don't use USB enough. My suspend script is now stripped
down to the point where the only thing I do is run dhclient afterwards (and
that's mostly because it seems to be too stupid to notice the timeout's
elapsed. Persumably it should have some kind of trigger if the wireless
access point toggles...)
It's just that a hot-pluggable bus, it should be possible to convince the
thing to reprobe all devices on a bus reset. Oh well.
Maybe a todo item for 2.7...
Rob
--
www.linucon.org: Linux Expo and Science Fiction Convention
October 8-10, 2004 in Austin Texas. (I'm the con chair.)
next prev parent reply other threads:[~2004-06-27 8:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-27 1:34 Process in D state with USB and swsuspsp Rob Landley
2004-06-27 5:31 ` Brad Campbell
2004-06-27 8:50 ` Rob Landley [this message]
2004-06-27 13:22 ` Oliver Neukum
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=200406270350.46641.rob@landley.net \
--to=rob@landley.net \
--cc=brad@wasp.net.au \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.