Message-ID: <438B3366.5070700@nortel.com>
Date: Mon, 28 Nov 2005 10:42:14 -0600
From: "Christopher Friesen" <cfriesen@nortel.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040115
MIME-Version: 1.0
To: mgross <mgross@linux.intel.com>
CC: "Randy.Dunlap" <rdunlap@xenotime.net>, vherva@vianova.fi, bunk@stusta.de,
       folkert@vanheusden.com, linux-kernel@vger.kernel.org
Subject: Re: capturing oopses
References: <20051122130754.GL32512@vanheusden.com> <20051126193358.GF22255@vianova.fi> <20051127204132.2b0d7406.rdunlap@xenotime.net> <200511280820.02473.mgross@linux.intel.com>
In-Reply-To: <200511280820.02473.mgross@linux.intel.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 730
Lines: 17

mgross wrote:

> You know some platforms that perserve the memory above some addresses across 
> warm boots.  For such platforms, one could reserve a buffer in that area can 
> copy the sys log buffer to it on panic along with a bit pattern that could be 
> searched for upon the next boot.

I've worked on a few blades that had this.  Serial console wasn't going 
to be available in the field, so being able to just dump debug 
information to persistent memory was really nice.

Chris
-
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/