From owner-freebsd-acpi@FreeBSD.ORG Tue Jul 3 02:39:27 2012 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 10C40106564A for ; Tue, 3 Jul 2012 02:39:27 +0000 (UTC) (envelope-from sendtomatt@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id D56C28FC0C for ; Tue, 3 Jul 2012 02:39:26 +0000 (UTC) Received: by pbbro2 with SMTP id ro2so9216227pbb.13 for ; Mon, 02 Jul 2012 19:39:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=5IRGoMxkUzhTqGE+hmC4rrmk8sQvzjJrBijg28C7xpY=; b=ODMrS6Gt6Cgad6lk3JyWCr1wZY8Ptg2l1kesxvnJsEsnTlkKrS/63DKqGPbu5HZdds BAQ4fc86bJWQPJPHUCBKIOBg3nujy0/RalYG9WkPhIZu6x3+sHFUtguxfCLfnh00X1Rn iLxyHSs7eAK1id7yMxazeVhlZ8eYqf0/MGPTGtBm86qANOV8bzy1epSZUpBR7yGcqTIH krdo6nGtAZDWYJqrBiMZ1lWSrJ8NTMHoD+dFLLPF1vGshflCjgumwGVcR6ow8pTYDaUM CsUGRQ2B5UYaamCSmQTLYjoMKbav1Wqv1XJuqpU7buIiz752RUxvuZ2tiPkHQ3Umy8Yw DCkg== Received: by 10.68.213.7 with SMTP id no7mr2826637pbc.3.1341283166649; Mon, 02 Jul 2012 19:39:26 -0700 (PDT) Received: from flatline.local (70-36-223-239.dsl.dynamic.sonic.net. [70.36.223.239]) by mx.google.com with ESMTPS id ot4sm14378247pbb.65.2012.07.02.19.39.24 (version=SSLv3 cipher=OTHER); Mon, 02 Jul 2012 19:39:25 -0700 (PDT) Message-ID: <4FF25B3F.3040704@gmail.com> Date: Mon, 02 Jul 2012 19:38:55 -0700 From: matt User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120619 Thunderbird/13.0.1 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Gustau_P=E9rez_i_Querol?= References: <4FE99A6A.30809@entel.upc.edu> In-Reply-To: <4FE99A6A.30809@entel.upc.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-acpi@freebsd.org Subject: Re: Unable to resume amd64 machine X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jul 2012 02:39:27 -0000 On 06/26/12 04:18, Gustau Pérez i Querol wrote: > > Hi, > > it seems there was some problem when I posted this one. Sorry if it > shows two times in the mailing list. > > I've trying to suspend/resume an amd64 machine. The machine is a > fujitsu S710 laptop running: > > FreeBSD 10.0-CURRENT #4 r237339=e61ad3a-dirty: Sat Jun 23 > 17:12:58 CEST 2012 > > I did the tests in the following conditions: > > - No X loaded. Everything in console. The machine has an Intel video > card, but the i915kms wasn't there. > - When removing modules, I tried in single user mode. > > The behavior is basically the machine seems to suspend fine (I see > the power led blinking) but when resuming it freezes hard. I see the > disk spinning for a while and then it stops. I can't ssh to it, I > can't use the keyboard at all so I can issue no command at all. > > I've tried stripping down the kernel (everything is out except > if_ath, em and usb stack). No pccard, no sdhci, no sound, no cuse4bsd, > no usb hid devices (I'm using uhidd for hid devices), no acpi_video or > acpi_fujitsu there but the same result. > > I tried enabling debug.acpi.resume_beep=1. When doing this, the > laptop beeped like crazy. > > With sysctl debug.acpi.suspend_bounce=1, the suspend put the screen > blank, however the machine stayed alive. > > With acpi.reset_video I got no result. > > I tried using the serial console on the laptop. I saw the suspend > process taking down some usb devices. Resume showed nothing on the > serial console. > > Disabling devices in the BIOS (removing wifi, bluetooth, webcam, etc > ...) didn't bring me further. > > Thanks > > This could be similar to thinkpads, see my response to Honest Qiao's X201... Here's the short version: In single user, set hw.pci.do_power_resume=0 and hw.pci.do_power_suspend=0 Try suspend bounce (and if successful suspend) with suspend beep sysctl on. If that fails (either bounce or full suspend) try just hw.pci.do_power_resume=1 repeat test (bounce then full suspend) If that fails (either bounc or full suspend) try just hw.pci.do_power_suspend=1 repeat test (bounce then full suspend) I recommend testing laptop with SSH or some other screenless way of seeing if it resumed, as onboard graphics can be tricky these days. Matt Matt