mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matti Aarnio <matti.aarnio@zmailer.org>
To: James Courtier-Dutton <James@superbug.co.uk>
Cc: linux list <linux-kernel@vger.kernel.org>
Subject: Re: Black box flight recorder for Linux
Date: Sat, 8 Apr 2006 20:30:38 +0300	[thread overview]
Message-ID: <20060408173038.GR8304@mea-ext.zmailer.org> (raw)
In-Reply-To: <44379AB8.6050808@superbug.co.uk>

On Sat, Apr 08, 2006 at 12:12:56PM +0100, James Courtier-Dutton wrote:
> 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.

The idea of  dmesg  buffer comes to Linux from SunOS 4.x series
on hardware, where system boot code explicitely left aside memory
space which was not _cleared_ during boot (it was parity-regenerated,
though).  The command to display that ring-buffer content was (no
surprise there?) "dmesg".

I do wish so many things from PC hardware, but it has stayed so b***y
inferior to real computers forever.  Lattest AMD CPUs have nice
features making them almost as good as IBM S/370 from early 1970es,
but still BIOSes are rather primitive things keeping things back.
( IOMMUs are things that have been invented since, and are definitely
a good thing.  Otherwise it has been faster and more capacitious
processing and memory at cheaper system cost... )

Like others have noted, display card memory spaces have been used
for this kind of "survives over reset" uses  -- I do also know some
embedded boot codes that created similar ring buffers for similar
reasons.  They don't generally survive over power-cycling, of course.


> 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


/Matti Aarnio

  parent reply	other threads:[~2006-04-08 17:30 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-08 11:12 James Courtier-Dutton
2006-04-08 13:41 ` Andi Kleen
2006-04-08 19:42   ` Guennadi Liakhovetski
2006-04-08 16:40 ` Lee Revell
2006-04-08 17:30 ` Matti Aarnio [this message]
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)
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=20060408173038.GR8304@mea-ext.zmailer.org \
    --to=matti.aarnio@zmailer.org \
    --cc=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

all inboxes | Powered by JetHome®