public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "Andrew Morton" <akpm@osdl.org>,
	linux-pm@osdl.org,
	"Martin MOKREJŠ" <mmokrejs@ribosome.natur.cuni.cz>,
	john@illhostit.com, sjordet@gmail.com, fastboot@lists.osdl.org,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Zlatko Calusic" <zlatko.calusic@iskon.hr>,
	"Linus Torvalds" <torvalds@osdl.org>,
	"José Luis Domingo López" <jdomingo@24x7linux.com>,
	ncunningham@cyclades.com, linux-kernel@24x7linux.com
Subject: Re: FYI: device_suspend(...) in kernel_power_off().
Date: Wed, 10 Aug 2005 15:08:03 +0200	[thread overview]
Message-ID: <20050810130803.GA2004@elf.ucw.cz> (raw)
In-Reply-To: <m1pssnvx84.fsf@ebiederm.dsl.xmission.com>

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

Hi!

> >> > Code is not ready now => it can never be fixed? Thats quite a strange
> >> > conclusion to make.
> >> 
> >> It seems there is an fundamental incompatibility with ACPI power off.
> >> As best as I can tell the normal case of device_suspend(PMSG_SUSPEND)
> >> works reasonably well in 2.6.x.
> >
> > Powerdown is going to have the same problems as the powerdown at the
> > end of suspend-to-disk. Can you ask people reporting broken shutdown
> > to try suspend-to-disk?
> 
> Everyone I know of who is affected has been copied on this thread.
> However your request is just nonsense.  There is a device_resume in
> the code before we get to the device_shutdown so there should be no
> effect at all.  Are we looking at the same kernel?

Sorry, my fault. kernel/power/disk.c:power_down(): it calls
device_shutdown even in PM_DISK_PLATFORM case. I thought it would do
device_suspend() to enable drivers doing something more clever.

So only missing piece of puzzle seems to be making sure disks are
properly spinned down in device_shutdown... and even that seems to be
there, not sure why it was broken before.
								Pavel
-- 
if you have sharp zaurus hardware you don't need... you know my address

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



      parent reply	other threads:[~2005-08-10 13:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m1mzo9eb8q.fsf@ebiederm.dsl.xmission.com>
     [not found] ` <m1iryxeb4t.fsf@ebiederm.dsl.xmission.com>
2005-07-26 17:54   ` [PATCH 1/23] Add missing device_suspsend(PMSG_FREEZE) calls Nigel Cunningham
2005-07-28  1:12     ` Eric W. Biederman
2005-07-28  2:21       ` david-b
2005-07-28  2:44       ` Shaohua Li
     [not found] ` <20050727025923.7baa38c9.akpm@osdl.org>
     [not found]   ` <m1k6jc9sdr.fsf@ebiederm.dsl.xmission.com>
     [not found]     ` <20050727104123.7938477a.akpm@osdl.org>
     [not found]       ` <m18xzs9ktc.fsf@ebiederm.dsl.xmission.com>
     [not found]         ` <20050727224711.GA6671@elf.ucw.cz>
     [not found]           ` <20050727155118.6d67d48e.akpm@osdl.org>
     [not found]             ` <20050727225442.GD6529@elf.ucw.cz>
     [not found]               ` <1123125850.948.9.camel@localhost>
     [not found]                 ` <20050804214520.GF1780@elf.ucw.cz>
     [not found]                   ` <m1ackah4r3.fsf@ebiederm.dsl.xmission.com>
     [not found]                     ` <20050725161548.274d3d67.akpm@osdl.org>
     [not found]                       ` <dnpst4v5px.fsf@magla.zg.iskon.hr>
     [not found]                         ` <m1oe8o9stl.fsf@ebiederm.dsl.xmission.com>
     [not found]                           ` <dny87s6oe9.fsf@magla.zg.iskon.hr>
     [not found]                             ` <m1r7dk82a4.fsf@ebiederm.dsl.xmission.com>
     [not found]                               ` <42E8439E.9030103@ribosome.natur.cuni.cz>
     [not found]                                 ` <20050727193911.2cb4df88.akpm@osdl.org>
     [not found]                                   ` <42F121CD.5070903@ribosome.natur.cuni.cz>
     [not found]                                     ` <20050803200514.3ddb8195.akpm@osdl.org>
     [not found]                                       ` <20050805140837.GA5556@localhost>
     [not found]                                         ` <42F52AC5.1060109@ribosome.natur.cuni.cz>
     [not found]                                         ` <1123193791.9025.77.camel@localhost>
2005-08-07 12:48                                           ` FYI: device_suspend(...) in kernel_power_off() Eric W. Biederman
2005-08-07 19:02                                             ` Pavel Machek
2005-08-07 19:46                                               ` Eric W. Biederman
2005-08-07 21:11                                                 ` Pavel Machek
2005-08-09 17:25                                                   ` Eric W. Biederman
2005-08-09 21:29                                                     ` Nigel Cunningham
2005-08-10 13:08                                                     ` Pavel Machek [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=20050810130803.GA2004@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=akpm@osdl.org \
    --cc=ebiederm@xmission.com \
    --cc=fastboot@lists.osdl.org \
    --cc=jdomingo@24x7linux.com \
    --cc=john@illhostit.com \
    --cc=linux-kernel@24x7linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@osdl.org \
    --cc=mmokrejs@ribosome.natur.cuni.cz \
    --cc=ncunningham@cyclades.com \
    --cc=sjordet@gmail.com \
    --cc=torvalds@osdl.org \
    --cc=zlatko.calusic@iskon.hr \
    /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