From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: "Greg KH" <gregkh@suse.de>, "Frans Pop" <elendil@planet.nl>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [2.6.25-rc1] System no longer powers off after shutdown
Date: Thu, 14 Feb 2008 16:06:19 -0800 [thread overview]
Message-ID: <86802c440802141606m3f44c786tb9ec4e684c71550a@mail.gmail.com> (raw)
In-Reply-To: <20080214234832.GA14363@elte.hu>
On Thu, Feb 14, 2008 at 3:48 PM, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Yinghai Lu <yhlu.kernel@gmail.com> wrote:
>
> > after disable cpufreq, i got
> >
> > ACPI: Preparing to enter system sleep state S5
> > Disabling non-boot CPUs ...
> > kvm: disabling virtualization on CPU1
> > CPU 1 is now offline
> > CPU1 is down
> > kvm: disabling virtualization on CPU2
> > CPU 2 is now offline
> > ================> hang here.
> >
> > but x86.git/mm could go through down all the cpus....
> >
> > interesting...
>
> i suspect some kobject related race, and i have the feeling this all is
> timing dependent.
>
> Andrew started seeing reboot hangs roughly around the time when the
> kobject changes went upstream. Given that x86.git had flux in that
> timeframe too i couldnt be sure what caused them.
>
> i have the fixlet below in x86.git but it didnt solve Andrew's problem
> so it's parking now at the end of the queue, with no clear purpose in
> life :-) If it would solve someone's problem it might be revitalized.
>
> Note: this does not fix any particular bug i know about, it's just a
> hack.
>
> Ingo
>
> ------------------------------>
> Subject: x86: highprio shutdown hack
> From: Ingo Molnar <mingo@elte.hu>
>
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> ---
> arch/x86/kernel/reboot.c | 16 ++++++++++++++--
> 1 file changed, 14 insertions(+), 2 deletions(-)
>
> Index: linux-x86.q/arch/x86/kernel/reboot.c
> ===================================================================
> --- linux-x86.q.orig/arch/x86/kernel/reboot.c
> +++ linux-x86.q/arch/x86/kernel/reboot.c
> @@ -396,8 +396,20 @@ static void native_machine_shutdown(void
> if (!cpu_isset(reboot_cpu_id, cpu_online_map))
> reboot_cpu_id = smp_processor_id();
>
> - /* Make certain I only run on the appropriate processor */
> - set_cpus_allowed(current, cpumask_of_cpu(reboot_cpu_id));
> + /*
> + * Make certain we only run on the appropriate processor,
> + * and with sufficient priority:
> + */
> + {
> + struct sched_param schedparm;
> + int ret;
> +
> + schedparm.sched_priority = 99;
> + ret = sched_setscheduler(current, SCHED_RR, &schedparm);
> + WARN_ON_ONCE(1);
so I got
------------[ cut here ]------------
WARNING: at arch/x86/kernel/reboot.c:409 native_machine_shutdown+0x5f/0xb4()
Modules linked in:
Pid: 7173, comm: reboot Not tainted 2.6.25-rc1-smp-00168-g458504f-dirty #33
Call Trace:
[<ffffffff802521d8>] warn_on_slowpath+0x64/0x8e
[<ffffffff802464c8>] enqueue_task+0x5c/0x7e
[<ffffffff8027765c>] rt_mutex_adjust_pi+0x28/0x94
[<ffffffff8024c075>] sched_setscheduler+0x304/0x33c
[<ffffffff80237feb>] native_machine_shutdown+0x5f/0xb4
[<ffffffff80237f6e>] native_machine_restart+0x2e/0x4c
[<ffffffff8026234b>] sys_reboot+0x140/0x1b2
[<ffffffff8029bbd2>] handle_mm_fault+0x380/0x705
[<ffffffff802cc311>] d_kill+0x50/0x7c
[<ffffffff8097d000>] do_page_fault+0x3bd/0x7c9
[<ffffffff804d58ae>] __up_read+0x27/0xb5
[<ffffffff8022432b>] system_call_after_swapgs+0x7b/0x80
---[ end trace eb0e49090acb42b5 ]---
next prev parent reply other threads:[~2008-02-15 0:06 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 15:23 [2.6.25-rc0 " Frans Pop
2008-02-12 20:39 ` [2.6.25-rc1] " Frans Pop
2008-02-12 20:56 ` Greg KH
2008-02-12 21:45 ` Frans Pop
2008-02-13 7:54 ` Andrew Morton
2008-02-13 8:23 ` Jeff Chua
2008-02-13 9:24 ` Frans Pop
2008-02-13 11:39 ` Frans Pop
2008-02-13 16:58 ` Greg KH
2008-02-13 18:55 ` Rafael J. Wysocki
2008-02-15 6:59 ` Greg KH
2008-02-15 8:52 ` Jeff Chua
2008-02-15 21:00 ` Greg KH
2008-02-13 19:28 ` Frans Pop
2008-02-14 23:38 ` Yinghai Lu
2008-02-14 23:48 ` Ingo Molnar
2008-02-15 0:06 ` Yinghai Lu [this message]
2008-02-15 2:14 ` Yinghai Lu
2008-02-15 3:45 ` Yinghai Lu
2008-02-15 6:52 ` Greg KH
2008-02-15 8:41 ` Yinghai Lu
2008-02-15 20:58 ` Greg KH
2008-02-15 6:57 ` Greg KH
2008-02-15 10:19 ` Frans Pop
2008-02-15 19:38 ` Yinghai Lu
2008-02-15 20:31 ` Yinghai Lu
2008-02-15 20:58 ` Greg KH
2008-02-15 20:58 ` Greg KH
2008-02-13 8:41 ` [2.6.25-rc1] jerky mouse cursor and randoooom key repeats Frans Pop
2008-02-15 23:58 ` Pavel Machek
2008-02-16 1:23 ` Gabriel C
2008-02-16 6:19 ` Mike Galbraith
2008-02-16 10:09 ` Gabriel C
2008-02-16 14:03 ` Mike Galbraith
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=86802c440802141606m3f44c786tb9ec4e684c71550a@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=elendil@planet.nl \
--cc=gregkh@suse.de \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®