From owner-freebsd-current@FreeBSD.ORG Fri Mar 13 13:18:03 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 38453FEB for ; Fri, 13 Mar 2015 13:18:03 +0000 (UTC) Received: from sh4-5.1blu.de (sh4-5.1blu.de [178.254.11.41]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F0317781 for ; Fri, 13 Mar 2015 13:18:02 +0000 (UTC) Received: from ftp51246-2575596 by sh4-5.1blu.de with local (Exim 4.76) (envelope-from ) id 1YWPEV-0001FX-RK for freebsd-current@freebsd.org; Fri, 13 Mar 2015 14:02:31 +0100 Date: Fri, 13 Mar 2015 14:02:31 +0100 From: Matthias Apitz To: freebsd-current@freebsd.org Subject: Acer C720 random complete power-off Message-ID: <20150313130231.GA26391@sh4-5.1blu.de> Reply-To: Matthias Apitz MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD 7.0-RELEASE (i386) User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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: Fri, 13 Mar 2015 13:18:03 -0000 Hello, I run HEAD i386 on an Acer C720 netbook (the so called Cromebook), which works pretty much fine and very fast. The device is used on a daily basis with 18++ hours uptime a day. >From time to time (since January exactly 5 times) I faced a complete randomly power-off of the device. Please, do not think in the usual suspects of CPU heat or power drain. I monitor in a file every time the exact device situation, which is here: http://www.unixarea.de/c720-crashes.html In /var/log/messages are no indications, and if the system would have written something in its last second, it is perhaps rolled back by the fsck on reboot. What I wanted to ask here: Is there any way to read any information out of local memory buffers when the system comes up again or any other way to understand what could cause this problem. I have to admit, that until now I was never present with my eyes when it happened, I was always somehow a way from the display (running KDE4), and when I returned to it, I found it black. Thanks in advance. matthias -- Matthias Apitz | /"\ ASCII Ribbon Campaign: E-mail: guru@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X - No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards | en.wikipedia.org/wiki/ASCII_Ribbon_Campaign