Messages in this thread | | | Date | Sat, 26 Nov 2005 21:33:58 +0200 | From | Ville Herva <> | Subject | Re: capturing oopses |
| |
On Sat, Nov 26, 2005 at 04:56:56PM +0100, you [Adrian Bunk] wrote: > On Tue, Nov 22, 2005 at 02:07:54PM +0100, Folkert van Heusden wrote: > > > Hi, > > Hi Folkert, > > > My 2.6.14 system occasionally crashes; gives a kernel panic. Of course I > > would like to report it. Now the system locks up hard so I can't copy > > the stacktrace. The crash dump patches mentioned in oops-tracing.txt all > > don't work for 2.6.14 it seems. So: what should I do? Get my digicam and > > take a picture of the display? > > yes, digicams have become a common tool for reporting Oops'es.
Speaking of which, does anybody know a feasible (as in "not too much harder than manually typing it in manually") way to OCR characters from vga text mode screen captures - or even digican shots?
The vga text mode captures are from a remote administration interface (such as HP RILOE or vmware gsx console) so they are pixel perfect and OCR should be doable. The digican shots on the other hand... Well at least it would have hack value :).
(My personal opinion is that Linus' unwillingness to include anything like kmsgdump (http://www.xenotime.net/linux/kmsgdump/) is somewhat unfortunate.)
-- v --
v@iki.fi
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |