mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Andrew Morton <akpm@digeo.com>, linux-kernel@vger.kernel.org
Subject: Re: bug on shutdown from 68-mm4 (machine_power_off returning causes problems)
Date: 12 May 2003 07:37:55 -0600	[thread overview]
Message-ID: <m11xz45lqk.fsf@frodo.biederman.org> (raw)
In-Reply-To: <19660000.1052710226@[10.10.2.4]>

"Martin J. Bligh" <mbligh@aracnet.com> writes:

> >> Yup, backing out kexec fixes it.
> > 
> > 
> > Ok.  Thinking it through the differences is that I have machine_power_off
> > call stop_apics (which is roughly equivalent to the old smp_send_stop).
> 
> Mmmm. Not sure NUMA-Q will like disconnect_bsp_APIC() much, but I guess
> that's my problem, not yours ;-) I can't do init 6 at the moment, so I'm
> walking on thin ice as is ... if I have to fix a couple of things up for
> NUMA-Q, that's no problem.

Ah ok.  This could explain some of your problems with kexec if you
can't even reboot the box....
 
> > In the kexec patch that does 2 things.
> > 1) It shuts down the secondary cpus, and returns the bootstrap cpu to
> >    virtual wire mode. 
> > 2) It calls set_cpus_allowed to force the reboot to be on the primary
> >    cpu.
> > 
> > After returning from machine_power_off. We run into a problem
> > in flush_tlb_mm.  Because we have a cpu disabled, that is still part
> > of the mm's vm mask.
> 
> OK ... I presume that's just because you shut down the secondaries then.
> If so ... shouldn't it remove them from the relevant vm mask when it
> offlines them? (probably not your code, but still)

Right.  The code is more about shutting down the secondaries then off
lining them.  In a general purpose scenario I expect more would need
to happen.

> > Does anyone know why machine_halt, and machine_power_off return?
> 
> Nope, thats ... odd ;-)

That is what I thought.

I have sent the fixed patches to Andrew and CC'd the list so we will
see what develops.

Eric


  reply	other threads:[~2003-05-12 13:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-11  3:25 bug on shutdown from 68-mm4 Martin J. Bligh
2003-05-11  5:44 ` Andrew Morton
2003-05-11  3:36   ` Martin J. Bligh
2003-05-11  6:11     ` Andrew Morton
2003-05-11 14:47       ` Martin J. Bligh
2003-05-11 18:37         ` bug on shutdown from 68-mm4 (machine_power_off returning causes problems) Eric W. Biederman
2003-05-12  3:30           ` Martin J. Bligh
2003-05-12 13:37             ` Eric W. Biederman [this message]
2003-05-12 12:43               ` Martin J. Bligh
2003-05-13  9:35                 ` Eric W. Biederman
2003-05-14 17:27                 ` Eric W. Biederman

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=m11xz45lqk.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.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

Powered by JetHome