public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Diego Calleja <diegocg@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: abonilla@linuxwireless.org, jesper.juhl@gmail.com,
	linux-kernel@vger.kernel.org, rml@novell.com
Subject: Re: Kernel Panic 2.6.14-git (pictures)
Date: Fri, 11 Nov 2005 12:09:30 +0100	[thread overview]
Message-ID: <20051111120930.346b985a.diegocg@gmail.com> (raw)
In-Reply-To: <20051110175522.1d50c084.akpm@osdl.org>

El Thu, 10 Nov 2005 17:55:22 -0800,
Andrew Morton <akpm@osdl.org> escribió:

> Yes, photos of the screen work very nicely, thanks.

So, it may be aceptable as "official method"?

--- stable/Documentation/oops-tracing.txt.old	2005-11-11 11:54:01.000000000 +0100
+++ stable/Documentation/oops-tracing.txt	2005-11-11 11:59:42.000000000 +0100
@@ -30,7 +30,9 @@ the disk is not available then you have 
 
 (1) Hand copy the text from the screen and type it in after the machine
     has restarted.  Messy but it is the only option if you have not
-    planned for a crash.
+    planned for a crash. Alternatively, you can take a picture of
+    the screen with a digital camera - not nice, but better than
+    nothing.
 
 (2) Boot with a serial console (see Documentation/serial-console.txt),
     run a null modem to a second machine and capture the output there

  parent reply	other threads:[~2005-11-11 11:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-10 15:15 Kernel Panic 2.6.14-git (pictures) Alejandro Bonilla
2005-11-11  1:55 ` Andrew Morton
2005-11-11  3:10   ` Dmitry Torokhov
2005-11-11  3:33   ` Robert Love
2005-11-11  6:22     ` Alejandro Bonilla Beeche
2005-11-11  6:31       ` Dmitry Torokhov
2005-11-11  6:37         ` Alejandro Bonilla Beeche
2005-11-11 11:09   ` Diego Calleja [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-11-11 21:16 Alejandro Bonilla

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=20051111120930.346b985a.diegocg@gmail.com \
    --to=diegocg@gmail.com \
    --cc=abonilla@linuxwireless.org \
    --cc=akpm@osdl.org \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@novell.com \
    /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