public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Dan Kegel <dkegel@ixiacom•com>
To: linuxppc-dev@lists•linuxppc.org
Subject: oops logging enhancements for ppc?
Date: Mon, 13 Oct 2003 16:18:46 -0700	[thread overview]
Message-ID: <3F8B32D6.2030208@ixiacom.com> (raw)


I'm interested in improving oops logging for ppc.
Two enhancements come to mind:

1. Log a few bytes of instruction space like other
architectures do, e.g.
http://lists.linuxppc.org/linuxppc-dev/199812/msg00109.html

2. Log module names and address ranges, as Andrea Arcangeli
proposed in
http://marc.theaimsgroup.com/?l=linux-kernel&m=102772338115172&w=2
and currently implements with the patch
http://www.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.23pre6aa3/90_module-oops-tracking-3

Is anyone aware of improvements along those lines,
or does anyone have objections to this sort of change,
before I dive in and implement them for the latest 2.4 for ppc?

(See also my post today to lkml,
http://marc.theaimsgroup.com/?l=linux-kernel&m=106608037825960&w=2
about making ksymoops aware of Andrea's enhanced oops logging. )

Thanks!
- Dan


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

                 reply	other threads:[~2003-10-13 23:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3F8B32D6.2030208@ixiacom.com \
    --to=dkegel@ixiacom$(echo .)com \
    --cc=linuxppc-dev@lists$(echo .)linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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