oops-tracing: mention digital photos
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 9 lines · Linux Kernel
tree
849707fda27c41466eabae0119d6386826ddb7dc
parent113fab1386f0093602d9f48b424b945cafd3db23
author Diego Calleja <[email protected]> Mon, 14 Nov 2005 08:07:40 -0800 committer Linus Torvalds <[email protected]> Mon, 14 Nov 2005 10:14:17 -0800[PATCH] oops-tracing: mention digital photos
Signed-off-by Andrew Morton <[email protected]>Signed-off-by Linus Torvalds <[email protected]>
Something I've found handy countless times when users do this..
Documentation/oops-tracing.txt renamed from Documentation/oops-tracing.txt~ +4 -1
@@ -32,7 +32,10 @@ the disk is not available then you have 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
Randy.Dunlap
Acked-byQuoted 6 lines · Dave Jones
Quoted 5 lines · Linux Kernel
tree
849707fda27c41466eabae0119d6386826ddb7dc
parent113fab1386f0093602d9f48b424b945cafd3db23
author Diego Calleja <[email protected]> Mon, 14 Nov 2005 08:07:40 -0800 committer Linus Torvalds <[email protected]> Mon, 14 Nov 2005 10:14:17 -0800
Quoted 8 lines
Quoted 4 lines
[PATCH] oops-tracing: mention digital photos
Signed-off-by Andrew Morton <[email protected]>Signed-off-by Linus Torvalds <[email protected]>Something I've found handy countless times when users do this..
Signed-off-by Dave Jones <[email protected]>
I've mentioned that a few times also (to bug reporters), but your doc. is better than mine was.
Quoted 15 lines
Documentation/oops-tracing.txt renamed from Documentation/oops-tracing.txt~ +4
-2@@ -32,7 +32,10 @@ the disk is not available then you have 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 -
Signature · 1 line
~Randy
Quoted 13 lines · Randy.Dunlap
Quoted 11 lines · Dave Jones
Quoted 9 lines · Linux Kernel
tree
849707fda27c41466eabae0119d6386826ddb7dc
parent113fab1386f0093602d9f48b424b945cafd3db23
author Diego Calleja <[email protected]> Mon, 14 Nov 2005 08:07:40 -0800 committer Linus Torvalds <[email protected]> Mon, 14 Nov 2005 10:14:17 -0800[PATCH] oops-tracing: mention digital photos
Signed-off-by Andrew Morton <[email protected]>Signed-off-by Linus Torvalds <[email protected]>
Quoted 6 lines
Quoted 3 lines
Something I've found handy countless times when users do this..
Signed-off-by Dave Jones <[email protected]>I've mentioned that a few times also (to bug reporters), but your doc. is better than mine was.
I had come up to this idea before too, but never tried it. The higher resolution mode is ugly and fb was buggy at that time (not sure now).
I wonder if it's feasible to implement panic messages showing cyclically, or better like more (1).
Coywolf