From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Alternatives to serial console for oops.
Date: Mon, 28 Nov 2005 14:10:47 +0100 [thread overview]
Message-ID: <20051128131047.GH13985@lug-owl.de> (raw)
In-Reply-To: <Pine.LNX.4.62.0511281100520.12624@pademelon.sonytel.be>
[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]
On Mon, 2005-11-28 11:02:03 +0100, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> On Sun, 27 Nov 2005, Mateusz Berezecki wrote:
> > On 11/27/05, Jesper Juhl <jesper.juhl@gmail.com> wrote:
> >
> > > Pen & paper to manually write down the Oops.
> >
> > you really need to be _desperate_ :-) I tried this literally _once_ .
>
> Obviously you never flashed the screen using 8 colors (3 bits of information),
> to transfer a crash dump message...
In 1998, we used a video camera to capture a long-scrolling Oops at
the CLOWN cluster project in the University of Paderborn, Germany...
So we could finally fix the problem and make this Cluster event a real
success 8^P
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 _ O _
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O
für einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-11-28 13:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-27 15:52 James Courtier-Dutton
2005-11-27 16:20 ` Willy Tarreau
2005-11-27 17:09 ` Jesper Juhl
2005-11-27 17:15 ` Mateusz Berezecki
2005-11-28 10:02 ` Geert Uytterhoeven
2005-11-28 13:10 ` Jan-Benedict Glaw [this message]
2005-11-27 18:30 ` Michael Tokarev
2005-11-27 20:04 ` Michael Frank
2005-11-28 4:48 ` Randy.Dunlap
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=20051128131047.GH13985@lug-owl.de \
--to=jbglaw@lug-owl.de \
--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®