Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754862AbYL2NZ0 (ORCPT ); Mon, 29 Dec 2008 08:25:26 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752721AbYL2NZP (ORCPT ); Mon, 29 Dec 2008 08:25:15 -0500 Received: from pih-relay06.plus.net ([212.159.14.19]:58076 "EHLO pih-relay06.plus.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752661AbYL2NZO (ORCPT ); Mon, 29 Dec 2008 08:25:14 -0500 X-Greylist: delayed 1519 seconds by postgrey-1.27 at vger.kernel.org; Mon, 29 Dec 2008 08:25:14 EST Message-ID: <4958C9CD.5050003@yahoo.com> Date: Mon, 29 Dec 2008 12:59:57 +0000 From: Sitsofe Wheeler User-Agent: Thunderbird 2.0.0.18 (Macintosh/20081105) MIME-Version: 1.0 To: for.poige+linux@gmail.com CC: Willy Tarreau , linux-kernel@vger.kernel.org Subject: Re: > I even didn't have a backtrace. References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Plusnet-Relay: dcbf12887fb17869f7f24121bf3b4486 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 625 Lines: 13 Igor Podlesny wrote: > Similar, but no exactly. I just thought that unlikely BIOS erases > memory content during "fast checks", so kernel diagnostic could be My understanding is that the only part of the BIOS that doesn't get cleared over a reboot (the hardware clock) is already being abused for suspend tracing - http://mjmwired.net/kernel/Documentation/power/s2ram.txt . -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/