public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <lkml@rtr.ca>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	"Brown, Len" <len.brown@intel.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	simon.derr@bull.net, Alexey Starikovskiy <astarikovskiy@suse.de>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch 4/6] Fix SMP poweroff hangs
Date: Fri, 05 Oct 2007 09:46:11 -0400	[thread overview]
Message-ID: <47064023.7080703@rtr.ca> (raw)
In-Reply-To: <m1myuyv6qu.fsf@ebiederm.dsl.xmission.com>

Eric W. Biederman wrote:
> Mark Lord <lkml@rtr.ca> writes:
>> Comments?  Eric?
> 
> Sorry -EBUSY.
> 
> The trylock on call_lock is a recent thing (.22), added to keep panic
> from hanging.   It probably makes more sense to move bust_spinlocks(0)
> down a few lines in kernel/panic.c and to test oops_in_progress in
> smp_send_stop and make all screwy locking behavior depend on that.

I've seen this issue (to a much lessor extent) on 2.6.17 as well.
So if earlier kernels had the regular spin_lock() there (rather than trylock)
then this is still *an* issue, but not *the* issue.  And in my specific
case (only 2 CPUs), the trylock cannot be the problem here.
But with more cores it definitely could be an issue.

> As for not waiting until cpus are in their stop loop that looks easy
> enough to remedy.  I don't know if any of those is our culprit but
> it certainly looks worth cleaning up.  If you are interested in
> testing I will cook up a patch.

I suspect this one more, as there really are not many other possibilities.
One thing to try might be to just have the power_off() code do msleep(1000)
before the ACPI poweroff call.  That would give enough time for the other
core to "halt", and is easy enough to try for diagnosis purposes.

I'm off rock climbing for a week or so, but if you cook something up
in the meanwhile then I'll test it on return.

> I haven't had a chance yet to walk through the other possible x86
> sysdev devices to see if there are any other canidates.

Cheers!


      parent reply	other threads:[~2007-10-05 13:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200710010820.l918KApW006834@imap1.linux-foundation.org>
     [not found] ` <CFF307C98FEABE47A452B27C06B85BB603DA9AB8@hdsmsx411.amr.corp.intel.com>
     [not found]   ` <m1hclascwo.fsf@ebiederm.dsl.xmission.com>
     [not found]     ` <200710020048.38856.rjw@sisk.pl>
     [not found]       ` <m1myv2o13c.fsf@ebiederm.dsl.xmission.com>
     [not found]         ` <470198B1.2030003@rtr.ca>
     [not found]           ` <m1ve9pn8d1.fsf@ebiederm.dsl.xmission.com>
     [not found]             ` <470271EA.4040509@rtr.ca>
     [not found]               ` <m1ejgdif0f.fsf@ebiederm.dsl.xmission.com>
     [not found]                 ` <4702C902.7000504@rtr.ca>
2007-10-05 13:39                   ` [patch 4/6] Fix SMP poweroff hangs Mark Lord
     [not found]                   ` <4702CCFB.1010000@pobox.com>
2007-10-05 13:40                     ` Mark Lord
     [not found]                     ` <47052292.3090400@rtr.ca>
     [not found]                       ` <m1myuyv6qu.fsf@ebiederm.dsl.xmission.com>
2007-10-05 13:46                         ` Mark Lord [this message]

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=47064023.7080703@rtr.ca \
    --to=lkml@rtr.ca \
    --cc=akpm@linux-foundation.org \
    --cc=astarikovskiy@suse.de \
    --cc=ebiederm@xmission.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=simon.derr@bull.net \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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