public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: "Toralf Förster" <toralf.foerster@gmx.de>,
	ibm-acpi-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, "Pavel Machek" <pavel@ucw.cz>
Subject: Re: [ibm-acpi-devel] suspend/hibernation regression between 2.6.19 and 2.6.20 w/ Thinkpad T41
Date: Wed, 8 Aug 2007 22:24:38 +0200	[thread overview]
Message-ID: <200708082224.39337.rjw@sisk.pl> (raw)
In-Reply-To: <20070808144854.GB9587@khazad-dum.debian.net>

On Wednesday, 8 August 2007 16:48, Henrique de Moraes Holschuh wrote:
> On Wed, 08 Aug 2007, Rafael J. Wysocki wrote:
> > > I wish we loaded the kernel just once, maybe from the boot loader.
> > 
> > Well, that's not so easy.  That will work for the bare image, but if we want it
> > to be compressed and/or encrypted, then the boot loader will need to
> > contain all of the necessary code.
> 
> Doing things right always have an associated cost, or we'd be doing it right
> since day one...
> 
> > I may be doable by using a special boot kernel with ACPI disabled and only
> > as many drivers as required to load the image, but that will make it more
> > difficult to set up and to recover from errors.
> 
> Better than the walking bomb we have now.  When waking from suspend-to-disk,
> we should not overwrite ANY non-kernel data which has ties to external
> systems (the hardware, the firmware).  Instead, we should re-init everything
> (re-init hardware to make sure we know in which state it is, re-init
> ourselves, to make sure we match the firmware and hardware state), as if we
> were booting a cold system in the first place.

Yes, we've already had an agreement about that on linux-pm, now the problem is
to implement it and not to break things in the process ...


-- 
"Premature optimization is the root of all evil." - Donald Knuth

      reply	other threads:[~2007-08-08 20:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-05 17:02 suspend/hibernation regression between 2.6.19 and 2.6.20 w/ Thinkpad T41 Toralf Förster
2007-08-05 20:11 ` Henrique de Moraes Holschuh
2007-08-05 22:29 ` Pavel Machek
2007-08-06  9:36   ` Toralf Förster
2007-08-06 14:36     ` Henrique de Moraes Holschuh
2007-08-06 14:56       ` Rafael J. Wysocki
2007-08-06 15:03         ` Henrique de Moraes Holschuh
2007-08-06 19:13       ` Toralf Förster
2007-08-07  0:21         ` [ibm-acpi-devel] " Henrique de Moraes Holschuh
2007-08-07 13:21           ` Toralf Förster
2007-08-07 15:38             ` Rafael J. Wysocki
2007-08-08  9:22               ` Toralf Förster
2007-08-08 12:04                 ` Henrique de Moraes Holschuh
2007-08-08 12:42                   ` Rafael J. Wysocki
2007-08-08 14:48                     ` Henrique de Moraes Holschuh
2007-08-08 20:24                       ` 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=200708082224.39337.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=hmh@hmh.eng.br \
    --cc=ibm-acpi-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=toralf.foerster@gmx.de \
    /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