From owner-freebsd-acpi@FreeBSD.ORG  Thu May 22 14:21:17 2008
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
Delivered-To: freebsd-acpi@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id D83791065684
	for <freebsd-acpi@freebsd.org>; Thu, 22 May 2008 14:21:17 +0000 (UTC)
	(envelope-from takawata@init-main.com)
Received: from sana.init-main.com (unknown [IPv6:2001:240:28::1])
	by mx1.freebsd.org (Postfix) with ESMTP id 83C098FC1B
	for <freebsd-acpi@freebsd.org>; Thu, 22 May 2008 14:21:17 +0000 (UTC)
	(envelope-from takawata@init-main.com)
Received: from ns.init-main.com (localhost [127.0.0.1])
	by sana.init-main.com (8.14.1/8.13.8) with ESMTP id m4MDxRs9042493;
	Thu, 22 May 2008 22:59:28 +0900 (JST)
	(envelope-from takawata@ns.init-main.com)
Message-Id: <200805221359.m4MDxRs9042493@sana.init-main.com>
To: vova@fbsd.ru
In-reply-to: Your message of "Thu, 22 May 2008 14:30:13 +0400."
	<1211452213.2647.1.camel@localhost>
Date: Thu, 22 May 2008 22:59:27 +0900
From: Takanori Watanabe <takawata@init-main.com>
Cc: freebsd-acpi@freebsd.org
Subject: Re: SMP suspend/resume.
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
	<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
	<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 22 May 2008 14:21:17 -0000

In message <1211452213.2647.1.camel@localhost>, Vladimir Grebenschikov wrote:
>On Thu, 2008-05-22 at 12:39 +0900, Takanori Watanabe wrote:
>
>> >But RELENG_7 (without patch) normally enters to S3, but failed to wake.
>> 
>> I tested it on sched_ule. So I know littele about sched_4bsd.
>> The message may caused on forward_wakeup on sched_4bsd, so
>> how about kern.sched.ipiwakeup.forward_wakeup set to 0.
>
>Just test it on SCHED_ULE.
>Now it does not write anything on console, just turn off console and
>hardlock.
>No actual enter to sleep (I assume that by indication lamps).
>
>I've booted as 'boot -sv' and tried to go to sleep from single-user
>mode.

In RELENG_7, some more patch should be merged from HEAD, so that 
preserver identity mapping. 
BTW, did you make sure UP kernel successfully suspend and resume 
on your machine?