Re: [PATCH] oops-tracing: mention digital photos

Randy.Dunlap
2005-11-14T21:56:34Z

On Mon, 14 Nov 2005, Dave Jones wrote:

> On Sun, Nov 13, 2005 at 07:02:57PM -0800, Linux Kernel wrote:
> > tree 849707fda27c41466eabae0119d6386826ddb7dc
> > parent 113fab1386f0093602d9f48b424b945cafd3db23
> > author Diego Calleja <diegocg@gmail.com> Mon, 14 Nov 2005 08:07:40 -0800
> > committer Linus Torvalds <torvalds@g5.osdl.org> Mon, 14 Nov 2005 10:14:17 -0800
> >
> > [PATCH] oops-tracing: mention digital photos
> >
> > Signed-off-by: Andrew Morton <akpm@osdl.org>
> > Signed-off-by: Linus Torvalds <torvalds@osdl.org>
>
> Something I've found handy countless times when users do this..
>
> Signed-off-by: Dave Jones <davej@redhat.com>

I've mentioned that a few times also (to bug reporters),
but your doc. is better than mine was.

Acked-by: Randy Dunlap <rdunlap@xenotime.net>

> --- linus/Documentation/oops-tracing.txt~ 2005-11-14 16:47:54.000000000 -0500
> +++ linus/Documentation/oops-tracing.txt 2005-11-14 16:51:02.000000000 -0500
> @@ -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