public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Meelis Roos <mroos@linux.ee>
Cc: Nigel Cunningham <ncunningham@cyclades.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Eric W.Biederman" <ebiederm@xmission.com>,
	Len Brown <len.brown@intel.com>
Subject: Re: reboot vs poweroff (was: Linux 2.6.13)
Date: Thu, 01 Sep 2005 14:32:35 +0200	[thread overview]
Message-ID: <4316F4E3.4030302@drzeus.cx> (raw)
In-Reply-To: <Pine.SOC.4.61.0509011030430.3232@math.ut.ee>

Meelis Roos wrote:
> 
> It's OK then - I'm not using any suspend and I had a problem that my
> machine powered down instead of reboot. The patch that went into 2.6.13
> after rc7 fixed it for me. So the current tree is OK for me and if it's
> OK for you too after suspend2 changes then this case can probably be
> closed.
> 

I'm still having problems with this patch. Both swsusp and swsusp2 are
affected. Perhaps the fix Nigel did needs to be done to swsusp aswell?

Bugzilla entry:

http://bugme.osdl.org/show_bug.cgi?id=4320

Rgds
Pierre

  reply	other threads:[~2005-09-01 12:33 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-29  0:17 Linux 2.6.13 Linus Torvalds
2005-08-29  0:43 ` Jesper Juhl
2005-08-29  3:05   ` Linus Torvalds
2005-08-29 10:57 ` Steven Rostedt
2005-08-29 12:17   ` Nigel Cunningham
2005-08-29 12:25     ` Jörn Engel
2005-08-29 12:28       ` Nigel Cunningham
2005-08-29 14:25     ` Antonino A. Daplas
2005-08-29 14:42       ` Steven Rostedt
2005-08-29 14:50       ` Linus Torvalds
2005-08-29 15:44         ` [PATCH] convert signal handling of NODEFER to act like other Unix boxes Steven Rostedt
2005-08-29 18:04         ` [PATCH] convert signal handling of NODEFER to act like other Unix boxes. [take2] Steven Rostedt
2005-08-29 12:19 ` Linux 2.6.13 Nigel Cunningham
2005-08-29 14:22   ` Roland Dreier
2005-09-01  6:24     ` reboot vs poweroff (was: Linux 2.6.13) Meelis Roos
2005-09-01  6:48       ` Nigel Cunningham
2005-09-01  7:33         ` Meelis Roos
2005-09-01 12:32           ` Pierre Ossman [this message]
2005-09-01 12:48             ` Nigel Cunningham
2005-09-01 15:15               ` Eric W. Biederman
2005-09-01 15:19                 ` reboot vs poweroff Pierre Ossman
2005-09-01 17:00                   ` Eric W. Biederman
2005-09-01 18:19                     ` Pierre Ossman
2005-09-01 18:23                       ` Eric W. Biederman
2005-09-01 21:11                         ` Nigel Cunningham
2005-09-02  4:46                           ` Eric W. Biederman
2005-09-01 20:22                     ` Pavel Machek
2005-09-02  4:26                       ` Eric W. Biederman
2005-09-01 21:09                 ` reboot vs poweroff (was: Linux 2.6.13) Nigel Cunningham
2005-08-29 18:23 ` Oops in 2.6.13 (was Linux 2.6.13 ) Masoud Sharbiani
2005-08-29 20:13   ` Lee Revell
2005-08-30  3:47     ` Masoud Sharbiani
2005-08-30 22:41 ` Linux 2.6.13 Henrik Persson
2005-09-01  2:29   ` Greg KH
2005-09-03  9:22     ` Henrik Persson
2005-08-31 12:42 ` Alexandre Buisse

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=4316F4E3.4030302@drzeus.cx \
    --to=drzeus-list@drzeus.cx \
    --cc=ebiederm@xmission.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mroos@linux.ee \
    --cc=ncunningham@cyclades.com \
    /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