mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Marc Ballarin <Ballarin.Marc@gmx.de>,
	akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: Calling suspend() in halt/restart/shutdown -> not a good idea
Date: Tue, 2 Aug 2005 11:54:01 +0200	[thread overview]
Message-ID: <20050802095401.GB1442@elf.ucw.cz> (raw)
In-Reply-To: <1122926885.30257.4.camel@gaston>

Hi!

> > > Why are we calling driver suspend routines in these ? This is _not_ a
> > > good idea ! On various machines, the mecanisms for shutting down are
> > > quite different from suspend/resume, and current drivers have too many
> > > bugs to make that safe. I keep getting all sort of reports of machines
> > > not shutting down anymore.
> > 
> > For example, my Centrino laptop will restart instead of power down with
> > -mm kernels.
> > 
> > To "fix" this I can either:
> > - unplug power. Shutdown works when on battery power.
> > - attach an external USB hard disk => power down always works.
> > - remove device_suspend(PMSG_SUSPEND) => power down always works.-
> 
> Yes, this is just one of the gazillion setup that got broken by this
> change. Drivers already have a shutdown() callback anyway, and if we
> want to re-use the suspend one, then we need to define some sane
> parameter, not "fake" a system suspend.

I'd like to get rid of shutdown callback. Having two copies of code
(one in callback, one in suspend) is ugly.
								Pavel

-- 
teflon -- maybe it is a trademark, but it should not be.

  reply	other threads:[~2005-08-02  9:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-01 15:09 Benjamin Herrenschmidt
2005-08-01 18:37 ` Marc Ballarin
2005-08-01 20:08   ` Benjamin Herrenschmidt
2005-08-02  9:54     ` Pavel Machek [this message]
2005-08-03 11:40       ` Benjamin Herrenschmidt
2005-08-03 16:53         ` Kyle Moffett
2005-08-03 19:59           ` Benjamin Herrenschmidt
2005-08-04 20:56           ` Pavel Machek
2005-08-04 21:04         ` Pavel Machek
2005-08-02  9:53 ` Pavel Machek
2005-08-02 14:40   ` Eric W. Biederman
2005-08-02 14:45     ` Pavel Machek
2005-08-03 11:43       ` Benjamin Herrenschmidt
2005-08-03 11:43     ` Benjamin Herrenschmidt
2005-08-03 11:38   ` Benjamin Herrenschmidt
2005-08-04  2:27     ` Andrew Morton
2005-08-02 10:04 ` Pavel Machek
2005-08-03 11:41   ` Benjamin Herrenschmidt

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=20050802095401.GB1442@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=Ballarin.Marc@gmx.de \
    --cc=akpm@osdl.org \
    --cc=benh@kernel.crashing.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®