mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marc Dionne <marc.c.dionne@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: BUG during shutdown - bisected to commit e2912009
Date: Fri, 1 Jan 2010 19:27:38 -0500	[thread overview]
Message-ID: <6041d2001001011627o5c494df4v37c0c466df3d444c@mail.gmail.com> (raw)

I'm getting a BUG with current kernels from
kernel/time/clockevents.c:263 when halting the system - a restart
behaves normally.  I don't have a good camera handy at the moment to
capture the call stack on screen, but the call sequence is:

clockevents_notify
hrtimer_cpu_notify
notifier_call_chain
raw_notifier_call_chain
_cpu_down
disable_nonboot_cpus
kernel_power_off
sys_reboot

I bisected it down to commit e2912009: sched: Ensure set_task_cpu() is
never called on blocked tasks.  There were a few commits tested along
the way where I got a freeze (with the power still on) instead of a
BUG. Reverting that commit from the current kernel doesn't look
trivial, but the commit immediately preceding this one does halt fine.

Marc

             reply	other threads:[~2010-01-02  0:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-02  0:27 Marc Dionne [this message]
2010-01-02  0:42 ` Peter Zijlstra
2010-01-04 18:43   ` Marc Dionne
2010-01-05  2:56     ` Xiaotian Feng
2010-01-05  3:23       ` Marc Dionne
2010-01-05 10:18         ` Xiaotian Feng
2010-01-05 22:58           ` Marc Dionne
2010-01-06  9:42             ` Xiaotian Feng
2010-01-07  0:44               ` Marc Dionne
2010-01-07  2:51                 ` Xiaotian Feng
2010-01-07  3:07                   ` Marc Dionne
2010-01-07  3:20                     ` Marc Dionne
2010-01-07  3:24                       ` Xiaotian Feng

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=6041d2001001011627o5c494df4v37c0c466df3d444c@mail.gmail.com \
    --to=marc.c.dionne@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --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®