From: Olaf Hering <olh@suse.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] properly stop devices before poweroff
Date: Mon, 1 Aug 2005 17:19:56 +0200 [thread overview]
Message-ID: <20050801151956.GA29448@suse.de> (raw)
In-Reply-To: <200506260105.j5Q15eBj021334@hera.kernel.org>
On Sun, Jun 26, Linux Kernel Mailing List wrote:
> tree e2de713c76ddb42b091305b88aa7ca4938081789
> parent 5ce47e59c9688d8480ae41100117d8188c191401
> author Pavel Machek <pavel@ucw.cz> Sun, 26 Jun 2005 04:55:11 -0700
> committer Linus Torvalds <torvalds@ppc970.osdl.org> Sun, 26 Jun 2005 06:24:33 -0700
>
> [PATCH] properly stop devices before poweroff
>
> Without this patch, Linux provokes emergency disk shutdowns and
> similar nastiness. It was in SuSE kernels for some time, IIRC.
>
> Signed-off-by: Pavel Machek <pavel@suse.cz>
> Signed-off-by: Andrew Morton <akpm@osdl.org>
> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
>
> include/linux/pm.h | 33 +++++++++++++++++++++------------
> kernel/sys.c | 3 +++
> 2 files changed, 24 insertions(+), 12 deletions(-)
> +++ b/kernel/sys.c
> @@ -405,6 +405,7 @@ asmlinkage long sys_reboot(int magic1, i
> case LINUX_REBOOT_CMD_HALT:
> notifier_call_chain(&reboot_notifier_list, SYS_HALT, NULL);
> system_state = SYSTEM_HALT;
> + device_suspend(PMSG_SUSPEND);
> device_shutdown();
> printk(KERN_EMERG "System halted.\n");
> machine_halt();
> @@ -415,6 +416,7 @@ asmlinkage long sys_reboot(int magic1, i
> case LINUX_REBOOT_CMD_POWER_OFF:
> notifier_call_chain(&reboot_notifier_list, SYS_POWER_OFF, NULL);
> system_state = SYSTEM_POWER_OFF;
> + device_suspend(PMSG_SUSPEND);
> device_shutdown();
> printk(KERN_EMERG "Power down.\n");
> machine_power_off();
This change for 'case LINUX_REBOOT_CMD_POWER_OFF' causes an endless hang
after 'halt -p' on my Macs with USB keyboard.
It went into rc1, but the hang in an usb device (1-1.3) shows up only
with rc3. Why is device_suspend() called anyway if the
system will go down anyway in a few milliseconds?
next parent reply other threads:[~2005-08-01 15:22 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200506260105.j5Q15eBj021334@hera.kernel.org>
2005-08-01 15:19 ` Olaf Hering [this message]
2005-08-01 16:10 ` [PATCH] remove device_suspend calls in sys_reboot path Olaf Hering
2005-08-01 19:37 ` Olaf Hering
2005-08-02 9:58 ` Pavel Machek
2005-07-27 21:14 [patch] properly stop devices before poweroff Luck, Tony
-- strict thread matches above, loose matches on Subject: below --
2005-07-26 19:02 Luck, Tony
2005-07-26 19:10 ` Andrew Morton
2005-07-27 0:14 ` tony.luck
2005-07-27 0:23 ` Andrew Morton
2005-07-27 7:40 ` Pavel Machek
2005-07-28 1:37 ` Kenji Kaneshige
2005-07-28 1:41 ` Andrew Morton
2005-04-21 15:02 tvrtko.ursulin
2005-04-21 11:30 tvrtko.ursulin
2005-04-21 11:38 ` Pavel Machek
2005-04-21 11:13 Pavel Machek
2005-04-29 13:18 ` Andrew Morton
2005-04-29 13:36 ` Zwane Mwaikambo
2005-04-30 9:47 ` Andrew Morton
2005-04-30 13:40 ` Pavel Machek
2005-05-01 19:09 ` Kenji Kaneshige
2005-05-01 19:57 ` Pavel Machek
2005-05-01 22:16 ` Adam Belay
2005-05-16 7:56 ` Andrew Morton
2005-05-19 12:43 ` Kenji Kaneshige
2005-05-01 22:24 ` Adam Belay
2005-05-01 23:16 ` Pavel Machek
2005-05-02 0:01 ` Adam Belay
2005-05-02 9:55 ` Pavel Machek
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=20050801151956.GA29448@suse.de \
--to=olh@suse.de \
--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