mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: vherva@vianova.fi
Cc: bunk@stusta.de, folkert@vanheusden.com, linux-kernel@vger.kernel.org
Subject: Re: capturing oopses
Date: Sun, 27 Nov 2005 20:41:32 -0800	[thread overview]
Message-ID: <20051127204132.2b0d7406.rdunlap@xenotime.net> (raw)
In-Reply-To: <20051126193358.GF22255@vianova.fi>

On Sat, 26 Nov 2005 21:33:58 +0200 Ville Herva wrote:

> 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.)

BTW, status of that:  it needs a little work to be more reliable.
(It hangs sometimes when switching from protected to real mode.)
I'm hoping that some of the APIC/IOAPIC/PIC patches that are being
done for kdump will also help kmsgdump.  I'll be working more on it
in the next few weeks/months.

so yes, when it's working, it's very useful IMO.

---
~Randy

  reply	other threads:[~2005-11-28  4:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-22 13:07 Folkert van Heusden
2005-11-22 14:08 ` bert hubert
2005-11-23  1:27   ` Brice Goglin
2005-11-23 10:55   ` Folkert van Heusden
2005-11-23 11:17     ` bert hubert
2005-11-26 15:56 ` Adrian Bunk
2005-11-26 19:33   ` Ville Herva
2005-11-28  4:41     ` Randy.Dunlap [this message]
2005-11-28 16:20       ` mgross
2005-11-28 16:42         ` Christopher Friesen
2005-11-28 19:35         ` Ville Herva
2005-11-28  5:11 ` Maneesh Soni
     [not found] <5bG4q-8ks-17@gated-at.bofh.it>
     [not found] ` <5daDm-1Cg-15@gated-at.bofh.it>
     [not found]   ` <5de3Z-6CJ-13@gated-at.bofh.it>
2005-11-27  1:10     ` Bodo Eggert
2005-11-27 12:16       ` Ville Herva
2005-11-27 13:55         ` Sander
2005-11-27 14:44           ` Ville Herva
2005-11-27 14:56             ` Ville Herva

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=20051127204132.2b0d7406.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=bunk@stusta.de \
    --cc=folkert@vanheusden.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vherva@vianova.fi \
    /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

all inboxes | Powered by JetHome®