All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Brower <ebrower@usa.net>
To: sparclinux@vger.kernel.org
Subject: Re: auto poweroff - keyboard dependency?
Date: Mon, 08 Mar 2004 00:58:22 +0000	[thread overview]
Message-ID: <404BC52E.60502@usa.net> (raw)

Janos Sziliczi wrote:

> Hi All,
> 
> I've compiled a 2.4.25 kernel.
> When I'd typed the 'halt' command as root, the Linux shutdowned and the
> machine turned off automatically (no 'power-off' needed on PROM prompt).

This tends to hit the list once every few weeks.

In both sparc and sparc64 the kernel will not power-off systems that are 
running with a serial console-- instead they are dropped to OBP (2.2.x 
did not act this way).  I believe Pete was going to remove this "safety 
measure" in sparc a while back but I don't believe it has been done.

If you are running a sparc kernel, remove the check for !serial_console

   if (auxio_power_register && !serial_console)

in arch/sparc/kernel/process.c.  In sparc64, remove the check

   if (!serial_console)

in arch/sparc64/kernel/power.c.

I have a sysctl patch for sparc that allows selection of power-off at 
halt for serial console systems.  Pete did not like this too much, but I 
believe it is a fair trade-off IFF anyone believes the safety measure 
should be preserved.  The sparc64 arch could benefit from the same.

If you aren't up to recompiling a kernel, depending upon version you 
might be able to type 'power-off' at OBP.  Some versions allow this, 
some require a keyboard with power button to be present.  Of coure, you 
could always reach over and flip the switch, too, if it is not miles away.

E



             reply	other threads:[~2004-03-08  0:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-08  0:58 Eric Brower [this message]
2004-03-08  1:44 ` auto poweroff - keyboard dependency? C.Newport

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=404BC52E.60502@usa.net \
    --to=ebrower@usa.net \
    --cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.