From owner-freebsd-current@FreeBSD.ORG Tue Jul 7 13:07:54 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5CCF7106564A for ; Tue, 7 Jul 2009 13:07:54 +0000 (UTC) (envelope-from aragon@phat.za.net) Received: from mail.geek.sh (decoder.geek.sh [196.36.198.81]) by mx1.freebsd.org (Postfix) with ESMTP id EDB468FC13 for ; Tue, 7 Jul 2009 13:07:53 +0000 (UTC) (envelope-from aragon@phat.za.net) Received: from igor.geek.sh (unknown [196.209.244.147]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.geek.sh (Postfix) with ESMTPSA id 03CAC39815; Tue, 7 Jul 2009 15:07:51 +0200 (SAST) Message-ID: <4A5348A4.60401@phat.za.net> Date: Tue, 07 Jul 2009 15:07:48 +0200 From: Aragon Gouveia User-Agent: Thunderbird 2.0.0.21 (X11/20090331) MIME-Version: 1.0 To: Gonzalo Nemmi References: <19e9a5dc0907062310s6de64529uc1fb544d0b357829@mail.gmail.com> In-Reply-To: <19e9a5dc0907062310s6de64529uc1fb544d0b357829@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Can't get resume to work on -BETA1/-CURRENT-200906, help needed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jul 2009 13:07:54 -0000 Hi, Gonzalo Nemmi wrote: > log in > acpiconf -s 3 > suspend works > opened the lid and the screen doesn't come back (backlight never gets back) > hard reset > login again and checked /var/log/messages .. this is what I found: I have problems with suspend too, on AMD64. Basically it works and my systems comes back up, but some devices are hosed afterwards. My bge network interface is one. I get precisely the same PHY timeout errors you're getting after a suspend. The iwn network driver screams the following if I try use it after a suspend: > Jul 7 14:53:17 fuzz kernel: iwn0: iwn_mem_lock: could not lock memory > Jul 7 14:53:17 fuzz last message repeated 7 times > Jul 7 14:53:17 fuzz kernel: iwn0: iwn_transfer_microcode: could not load boot firmware > Jul 7 14:53:17 fuzz kernel: iwn0: iwn_transfer_firmware: could not load boot firmware, error 60 > Jul 7 14:53:17 fuzz kernel: iwn0: iwn_init_locked: could not load firmware, error 60 USB ports resume sometimes, sometimes not: > Jul 7 14:58:44 fuzz kernel: usbus2: port reset timeout > Jul 7 14:58:44 fuzz kernel: uhub_reattach_port:369: port 1 reset failed, error=USB_ERR_TIMEOUT > Jul 7 14:58:44 fuzz kernel: uhub_reattach_port:456: device problem (USB_ERR_TIMEOUT), disabling port 1 > Jul 7 14:58:44 fuzz kernel: usbus6: port reset timeout > Jul 7 14:58:44 fuzz kernel: uhub_reattach_port:369: port 5 reset failed, error=USB_ERR_TIMEOUT > Jul 7 14:58:44 fuzz kernel: uhub_reattach_port:456: device problem (USB_ERR_TIMEOUT), disabling port 5 > Jul 7 14:58:55 fuzz kernel: uhci_interrupt: resume detect > Jul 7 14:58:55 fuzz kernel: ugen6.2: at usbus6 (disconnected) > Jul 7 14:58:55 fuzz kernel: ugen5.2: at usbus5 (disconnected) > Jul 7 14:58:56 fuzz kernel: usbus6: port reset timeout > Jul 7 14:58:56 fuzz kernel: uhub_reattach_port:369: port 6 reset failed, error=USB_ERR_TIMEOUT > Jul 7 14:58:56 fuzz kernel: uhub_reattach_port:456: device problem (USB_ERR_TIMEOUT), disabling port 6 And I just noticed this message: > Jul 7 14:53:36 fuzz kernel: calcru: runtime went backwards from 18237633 usec to 9377885 usec for pid 10 (idle) Unloading modules from the kernel prior to suspending doesn't seem to work either. On the upside, FreeBSD 8.0 boots rather quickly! :) Regards, Aragon