linux-kernel - Recent intel Cedarview motherboards: does not poweroff

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <4F8B1F64.9030502@msgid.tls.msk.ru>
Date:	Sun, 15 Apr 2012 23:20:04 +0400
From:	Michael Tokarev <mjt@....msk.ru>
To:	Linux-kernel <linux-kernel@...r.kernel.org>
CC:	linux-acpi@...r.kernel.org
Subject: Recent intel Cedarview motherboards: does not poweroff

Hello.

Intel produced a set of very nice mini-ITX boards with new Cedarview
Atom CPUs onboard -- D2500CC, D2700MUD, D2800MT etc.  Apparently
all of these boards have issues powering off from linux.

Here's the last few lines left on the screen when the system should
turn the power off:

ACPI: Preparing to enter system sleep state S5
ACPI Error (psargs-8359): [\_SB_.PCI0.LPCB.TPM_.PTS_] Namespace lookup failure, AE_NOT_FOUND
ACPI Error (psparse-8537): Method parse/execution failed [\_PTS] (Node f703c504), AE_NOT_FOUND
Disabling non-boot CPUs ...
CPU1 is now offline
SNP alternatives: switching to UP code
Power down.
_

The cursor is blinking, and power staus on.

Is there anything can be done with this?

Thanks!

Besides, these boards have a bios bug which is kinda difficult to work
around if you don't know how.  Even with latest BIOS, the beasts don't
REboot if the active partition is something not FAT/NTFS -- eg, any linux
native filesystem.  It boots fine after power on, but on reboot, instead
of displaying bootloader prompt, the screen becomes blank with cursor
blinking at the upper left corner, and after about 30..40 seconds staying
in this state and not reacting to Ctrl+Alt+Del, the system reboots, ad
infinitum.  One can powercycle the motherboard and it will boot again
(just once again), or it is possible to enter bios settings and save
settings (without changing anything) -- this way it will also boot, but
also just once.  The workaround is to create a small fat16 /boot partition...

Maybe this information will save quite some time and frustration to
someone... ;)

/mjt
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/