From owner-freebsd-acpi@FreeBSD.ORG Thu May 22 10:30:26 2008 Return-Path: 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 768B3106564A for ; Thu, 22 May 2008 10:30:26 +0000 (UTC) (envelope-from vova@sw.ru) Received: from relay.sw.ru (mailhub.sw.ru [195.214.232.25]) by mx1.freebsd.org (Postfix) with ESMTP id E68E18FC2A for ; Thu, 22 May 2008 10:30:24 +0000 (UTC) (envelope-from vova@sw.ru) Received: from vbook.fbsd.ru ([10.30.1.111]) (authenticated bits=0) by relay.sw.ru (8.13.4/8.13.4) with ESMTP id m4MAUD9X021296 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 22 May 2008 14:30:19 +0400 (MSD) Received: from vova by vbook.fbsd.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Jz83p-0001Ib-Kg; Thu, 22 May 2008 14:30:13 +0400 From: Vladimir Grebenschikov To: Takanori Watanabe In-Reply-To: <200805220339.m4M3dF2q033762@sana.init-main.com> References: <200805220339.m4M3dF2q033762@sana.init-main.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: SWsoft Date: Thu, 22 May 2008 14:30:13 +0400 Message-Id: <1211452213.2647.1.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.22.1 FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov Cc: freebsd-acpi@freebsd.org Subject: Re: SMP suspend/resume. X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vova@fbsd.ru List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 May 2008 10:30:26 -0000 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. -- Vladimir B. Grebenschikov vova@fbsd.ru