From: Rob Landley <landley@trommello.org>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Jurriaan <thunder7@xs4all.nl>,
Linux-Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Any hope of fixing shutdown power off for SMP?
Date: Mon, 21 Oct 2002 14:15:03 -0500 [thread overview]
Message-ID: <200210211415.03206.landley@trommello.org> (raw)
In-Reply-To: <Pine.LNX.3.96.1021021163731.4564A-100000@gatekeeper.tmr.com>
On Monday 21 October 2002 15:41, Bill Davidsen wrote:
> On Sun, 20 Oct 2002, Rob Landley wrote:
> > On Sunday 20 October 2002 21:45, Bill Davidsen wrote:
> > > On Sun, 20 Oct 2002, Jurriaan wrote:
> > > > 2.5.43 will power down my smp VP6 board if I replace the BUG() calls
> > > > in arch/i386/kernel/apm.c with warnings. Somehow, the kernel doesn't
> > > > succesfully schedule itself to run on CPU 0. However, for my bios
> > > > that isn't needed.
> > >
> > > Are you using the real-mode call? Perhaps I should try NOT doing that,
> > > and see if it solves the problem. That used to be the solution, but
> > > things change.
> >
> > None of my systems will power down on UP if I enable the "local apic
> > support on uniprocessors" option.
> >
> > Something about the APIC code prevents the power down from occuring. The
> > symptoms are as you describe: the drives spin down, and the power goes
> > off immediately if you press the button (instead of having to hold it
> > down), but the power doesn't go off by itself.
> >
> > Works fine if I compile without local APIC support.
>
> Hum, and you can quote me on that. I don't have that particular problem at
> all, my problem is only with SMP.
SMP machines have the APIC enabled by default. Hence the problem sounds like
it's (at least being triggered by) the APIC code.
> Anyway, my kernels are SMP, and if I boot "nosmp" they work fine with
> every APIC in sight enabled. This may or may not be the same problem, you
> could build an SMP kernel and boot it "nosmp" with APIC on and see what
> that does (if you're curious).
Dunno. The boxen I currently manage are UP (cheaper that way), so I don't
actually need the APIC, so I switched it off and life went on. Alan Cox
seems to be of the opinion that bios bugs are involved, which should come as
no surprise. :)
Rob
prev parent reply other threads:[~2002-10-22 0:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-19 19:40 Bill Davidsen
2002-10-20 5:37 ` Jurriaan
2002-10-20 23:51 ` J.A. Magallon
2002-10-21 0:52 ` Bill Davidsen
2002-10-21 1:03 ` J.A. Magallon
2002-10-21 2:40 ` Bill Davidsen
2002-10-21 2:45 ` Bill Davidsen
2002-10-21 1:58 ` Rob Landley
2002-10-21 11:32 ` Alan Cox
2002-10-21 20:41 ` Bill Davidsen
2002-10-21 19:15 ` Rob Landley [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=200210211415.03206.landley@trommello.org \
--to=landley@trommello.org \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thunder7@xs4all.nl \
/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®