From owner-freebsd-questions@FreeBSD.ORG Thu May 28 05:43:12 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AA446106566C for ; Thu, 28 May 2009 05:43:12 +0000 (UTC) (envelope-from mel.flynn+fbsd.questions@mailing.thruhere.net) Received: from mailhub.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id 7A6F58FC17 for ; Thu, 28 May 2009 05:43:12 +0000 (UTC) (envelope-from mel.flynn+fbsd.questions@mailing.thruhere.net) Received: from sarevok.dnr.servegame.org (mailhub.lan.rachie.is-a-geek.net [192.168.2.11]) by mailhub.rachie.is-a-geek.net (Postfix) with ESMTP id 32D6B7E837; Wed, 27 May 2009 21:43:11 -0800 (AKDT) From: Mel Flynn To: freebsd-questions@freebsd.org Date: Thu, 28 May 2009 07:43:09 +0200 User-Agent: KMail/1.11.3 (FreeBSD/8.0-CURRENT; KDE/4.2.3; i386; ; ) References: <200905271943.56052.gnemmi@gmail.com> In-Reply-To: <200905271943.56052.gnemmi@gmail.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905280743.09479.mel.flynn+fbsd.questions@mailing.thruhere.net> Cc: Gonzalo Nemmi Subject: Re: Help logging kernel messages after failed resume X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 05:43:12 -0000 On Thursday 28 May 2009 00:43:56 Gonzalo Nemmi wrote: > Note: I can ssh into the notebook, then "su -" and issue "acpiconf -s > 3", but I can't get the notebook to WOL .. so .. I have to press the > power button on the notebook to get it to resume and as a consecuence, > those messages are sent to stdout (notebook screen) and I can't get > them on the ssh client. SCRIPT(1) it's not a solution either .. because > ad4 never gets back to life .. so script can't record a thing after it > went into suspend :( > > Any help will be greatly appreciated. Just to debug this issue, make /var/log and /var/run memory disks. /var/run too cause of the socket that syslog uses. That at least will give you the ability to manually transcribe the logs in worst case, best case being to save them to an USB stick you plug in after resume or copy of the network if bge ever comes back up. -- Mel