public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.co.uk>
To: linux list <linux-kernel@vger.kernel.org>
Subject: Black box flight recorder for Linux
Date: Sat, 08 Apr 2006 12:12:56 +0100	[thread overview]
Message-ID: <44379AB8.6050808@superbug.co.uk> (raw)

Hi,

I have had an idea for a black box flight recorder type feature for 
Linux. Before I try to implement it, I just wish to ask here if anyone 
has already tried it, and whether the idea works or not.

Description for feature:
Stamp the dmesg output on RAM somewhere, so that after a reset (reset 
button pressed, not power off), the RAM can be read and details of 
oopses etc. can be read.

Now, the question I have is, if I write values to RAM, do any of those 
values survive a reset? If any did survive, one could use them to store 
oops output in. I am currently only interested in Intel CPU and AMD CPU 
based motherboards. If only some values survived, one could use some 
sort of redundant encoding so the good values could be recovered.

The main advantage of something like this would be for newer 
motherboards that are around now that don't have a serial port.

If no one has tried this, I will spend some time testing.

James




             reply	other threads:[~2006-04-08 11:13 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-08 11:12 James Courtier-Dutton [this message]
2006-04-08 13:41 ` Black box flight recorder for Linux Andi Kleen
2006-04-08 19:42   ` Guennadi Liakhovetski
2006-04-08 16:40 ` Lee Revell
2006-04-08 17:30 ` Matti Aarnio
2006-04-09 19:23 ` Krzysztof Halasa
2006-04-10 12:01   ` Andy Green
2006-04-10 19:24     ` Krzysztof Halasa
2006-04-19 10:47       ` Krzysztof Halasa
2006-04-19 20:20         ` [lm-sensors] " Rudolf Marek
2006-04-19 23:02           ` Krzysztof Halasa
2006-06-06 17:42     ` Krzysztof Halasa
2006-06-07  8:03       ` Jean Delvare
2006-06-07 10:18         ` Andy Green
2006-06-07 23:52           ` Krzysztof Halasa
2006-04-11 11:21   ` Jan Engelhardt
2006-04-10  3:06 ` Russell Senior
     [not found] <5ZjEd-4ym-37@gated-at.bofh.it>
     [not found] ` <5ZlZk-7VF-13@gated-at.bofh.it>
2006-04-08 14:05   ` Robert Hancock
2006-04-08  7:17     ` Andi Kleen
2006-04-08 16:28       ` James Courtier-Dutton
2006-04-08 22:28         ` JustFillBug
2006-04-09 17:09           ` James Courtier-Dutton
2006-04-10 18:53             ` Ville Herva
2006-04-09 15:04         ` Andi Kleen
2006-04-09 19:25           ` Eric W. Biederman
2006-04-10 12:18       ` linux-os (Dick Johnson)
2006-04-10 19:44         ` Krzysztof Halasa
2006-04-10 20:07           ` linux-os (Dick Johnson)
  -- strict thread matches above, loose matches on Subject: below --
2006-04-08 22:45 linux

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44379AB8.6050808@superbug.co.uk \
    --to=james@superbug.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox