public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
To: linux-pm-qjLDD68F18O7TbgM5vRIOg@public.gmane.org
Cc: Arioch <the_Arioch-SYPjacQAEmk@public.gmane.org>,
	Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
Subject: Re: potential pitfall? changing configuration while PC in hibernate
Date: Mon, 21 Mar 2005 10:22:37 -0800	[thread overview]
Message-ID: <200503211022.38068.david-b@pacbell.net> (raw)
In-Reply-To: <20050321095229.GA28507-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 706 bytes --]

On Monday 21 March 2005 1:52 am, Pavel Machek wrote:
> On Po 21-03-05 11:02:04, Arioch wrote:
> > 
> > I wonder, if hardware configuration asked for changes when resuming from 
> > hibernate ?
> 
> Current position is "don't do this". You *will* be able to recover by
> passing noresume, but if you change hw configuration, it may crash&burn.

That may be Pavel's position, but USB-wise we absolutely consider
it a bug if Linux misbehaves in the face of routine actions like
unplugging a device during suspend (or plugging in a new one).
Regardless of "noresume" etc.

I'd say that's true for all hotpluggable busses, in fact, but I
rarely submit patches for non-USB ones like PCMCIA or CardBus.

- Dave



[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  parent reply	other threads:[~2005-03-21 18:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-21  8:02 potential pitfall? changing configuration while PC in hibernate Arioch
2005-03-21  9:52 ` Pavel Machek
     [not found]   ` <20050321095229.GA28507-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-03-21 10:49     ` Arioch
2005-03-21 18:22     ` David Brownell [this message]
2005-03-21 15:29 ` Alan Stern

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=200503211022.38068.david-b@pacbell.net \
    --to=david-b-ybekhbn/0ldr7s880joybq@public.gmane.org \
    --cc=linux-pm-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=pavel-+ZI9xUNit7I@public.gmane.org \
    --cc=the_Arioch-SYPjacQAEmk@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox