From 5040aade39a19637fa813e05b2799c8cced70bfa Mon Sep 17 00:00:00 2001 From: Dave Jones Date: Tue, 15 Nov 2005 00:09:24 -0800 Subject: [PATCH] --- yaml --- r: 14240 b: refs/heads/master c: e1f1def6ef3f0c71d0df302c3759f6937adaf9ae h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/Documentation/oops-tracing.txt | 5 ++++- 2 files changed, 5 insertions(+), 2 deletions(-) diff --git a/[refs] b/[refs] index f7d4e399e811..6a576578515d 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 1d193f4f112b9d8855ba1339fa784ee95f25b9c7 +refs/heads/master: e1f1def6ef3f0c71d0df302c3759f6937adaf9ae diff --git a/trunk/Documentation/oops-tracing.txt b/trunk/Documentation/oops-tracing.txt index 9f30ac6ca47b..05960f8a748e 100644 --- a/trunk/Documentation/oops-tracing.txt +++ b/trunk/Documentation/oops-tracing.txt @@ -32,7 +32,10 @@ the disk is not available then you have three options :- has restarted. Messy but it is the only option if you have not planned for a crash. Alternatively, you can take a picture of the screen with a digital camera - not nice, but better than - nothing. + nothing. If the messages scroll off the top of the console, you + may find that booting with a higher resolution (eg, vga=791) + will allow you to read more of the text. (Caveat: This needs vesafb, + so won't help for 'early' oopses) (2) Boot with a serial console (see Documentation/serial-console.txt), run a null modem to a second machine and capture the output there