From: Paul Menzel <paulepanter@users.sourceforge.net>
To: grub-devel@gnu.org
Subject: `halt` doesn’t work on Lenovo T60 with coreboot and GRUB payload
Date: Sat, 15 Apr 2017 18:32:53 +0200 [thread overview]
Message-ID: <1492273973.2222.113.camel@users.sourceforge.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1387 bytes --]
Dear GRUB folks,
On a Lenovo T60 with coreboot and the GRUB payload, version 2.02-rc1,
entering `halt` in the GRUB command line, nothing happens. The cursor
goes one line below, and everything stays that way. After that, the
system can only be powered off by pressing the power button for ten
seconds.
Setting `debug=all` before that – `debug=halt` didn’t work – the last
lines are below.
```
[…]
commands/acpihalt.c:107: data type = 0x12
commands/acpihalt.c:241: Opcode 0x8
commands/acpihalt.c:242: Tell 2dbd
commands/acpihalt.c:107: data type = 0x12
commands/acpihalt.c:241: Opcode 0x8
commands/acpihalt.c:242: Tell 2dcd
commands/acpihalt.c:269: S5 found
commands/acpihalt.c:444: SLP_TYP = 7, port = 0x504
```
I would have expected at least the monitor to go dark, and maybe also
the system to power off as there is no specific command `poweroff`
[1].
> The command halts the computer. If the --no-apm option is specified,
> no APM BIOS call is performed. Otherwise, the computer is shut down
> using APM.
I heard, that SysV implemented `halt` “incorrectly”, so that it also
powered off the system. Only `halt -p` or `poweroff` was supposed to
that. so I don’t know, how GRUB’s implementation of `halt` is supposed
to work.
Kind regards,
Paul
[1] https://www.gnu.org/software/grub/manual/html_node/halt.html#halt
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next reply other threads:[~2017-04-15 16:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-15 16:32 Paul Menzel [this message]
2017-04-15 16:52 ` `halt` doesn’t work on Lenovo T60 with coreboot and GRUB payload Andrei Borzenkov
2017-04-16 19:34 ` Paul Menzel
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=1492273973.2222.113.camel@users.sourceforge.net \
--to=paulepanter@users.sourceforge.net \
--cc=grub-devel@gnu.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;
as well as URLs for NNTP newsgroup(s).