Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: Kurt Fitzner <kfitzner@excelcia.org>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Bug report data collection tool
Date: Thu, 21 Jul 2005 06:58:53 -0600	[thread overview]
Message-ID: <20050721125853.GC27330@colo.lackof.org> (raw)
In-Reply-To: <42DF53E8.5010904@excelcia.org>

On Thu, Jul 21, 2005 at 01:51:04AM -0600, Kurt Fitzner wrote:
> I was thinking that perhaps it would be useful to have a tool to help
> collate information after a hang/crash.  Something you would run on the
> next boot.
> 
> I wasn't able to tell from a cursory glance at pdc_stable.c, but if the
> driver supports it then perhaps the tool could read HPMC/TOC data post
> crash from nvram (rather than having to write out or use a serial
> console to capture 'ser pim' data).

We thought of that before but there are a few issues:
1) stable storage access is only via PDC calls.
2) format of PIM data is platform dependent - ie every model machine
   could have a different format. In practice, ISTR the format usually
   is the same for a given processor model and not each model of machine.

>  It could then cross reference the
> crash address with the System.map, gather pre-crash data from the logs
> and a machine profile from /proc.
> 
> If something like this would be useful, I could do with having a project
> to help me learn the ropes.

Lack of documentation will make this a fairly hard project. :^(

sorry,
grant
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  reply	other threads:[~2005-07-21 12:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-21  7:51 [parisc-linux] Bug report data collection tool Kurt Fitzner
2005-07-21 12:58 ` Grant Grundler [this message]
2005-07-21 14:22   ` Carlos O'Donell

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=20050721125853.GC27330@colo.lackof.org \
    --to=grundler@parisc-linux.org \
    --cc=kfitzner@excelcia.org \
    --cc=parisc-linux@lists.parisc-linux.org \
    /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