From: "Ryan Nielsen" <ran@krazynet.com>
To: Tom Rini <tmrini@ntplx.net>
Cc: linuxppc-dev@lists.linuxppc.org,
Cort Dougan <cort@persephone.cs.nmt.edu>,
Paul Mackerras <paulus@cs.anu.edu.au>
Subject: Re: ksymoops
Date: Sat, 5 Dec 1998 17:48:58 -0800 [thread overview]
Message-ID: <19981205174858.A31582@gondolin> (raw)
In-Reply-To: <Pine.LNX.4.05.9812051953170.954-100000@pc.wackyland.com>; from Tom Rini on Sat, Dec 05, 1998 at 07:53:43PM -0500
Tom Rini wrote:
> On Sat, 5 Dec 1998, Ryan Nielsen wrote:
>
> > > Hello,
> > > Has anyone played around with getting ksymoops working on PPC yet?
> > > Would be a rather useful tool (gonna take a stab at it if not).
> >
> > I assume you mean linux/scripts/ksymoops.cc, a package that does similar
> > and works on PPC can be got from ftp://ftp.ocs.com.au/pub/ksymoops.tar.gz
>
> Yeah, found that a bit later on. Ever pass on the patch for more detailed
> oops to Cort/Paul?
(CC'd to Cort and Paul)
its the same Instruction DUMP from the sparc code.
I've found it useful in finding out where modules fsck up.
--- linux/arch/ppc/kernel/process.c 1998/10/11 17:47:23 1.67
+++ linux/arch/ppc/kernel/process.c 1998/11/02 03:11:28
@@ -198,6 +200,19 @@
_enable_interrupts(s);
}
+void instruction_dump (unsigned long *pc)
+{
+ int i;
+
+ if((((unsigned long) pc) & 3))
+ return;
+
+ printk("Instruction DUMP:");
+ for(i = -3; i < 6; i++)
+ printk("%c%08lx%c",i?' ':'<',pc[i],i?' ':'>');
+ printk("\n");
+}
+
void show_regs(struct pt_regs * regs)
{
int i;
--- linux/arch/ppc/kernel/traps.c 1998/05/05 19:18:53 1.21
+++ linux/arch/ppc/kernel/traps.c 1998/11/02 03:11:36
@@ -79,6 +79,7 @@
debugger(regs);
#endif
print_backtrace((unsigned long *)regs->gpr[1]);
+ instruction_dump((unsigned long *)regs->nip);
panic("Exception in kernel pc %lx signal %d",regs->nip,signr);
}
force_sig(signr, current);
@@ -126,6 +127,7 @@
debugger(regs);
#endif
print_backtrace((unsigned long *)regs->gpr[1]);
+ instruction_dump((unsigned long *)regs->nip);
panic("machine check");
}
_exception(SIGSEGV, regs);
@@ -219,6 +221,7 @@
#endif
show_regs(regs);
print_backtrace((unsigned long *)regs->gpr[1]);
+ instruction_dump((unsigned long *)regs->nip);
panic("kernel stack overflow");
}
--- linux/arch/ppc/mm/fault.c 1998/10/06 03:13:19 1.28
+++ linux/arch/ppc/mm/fault.c 1998/11/02 03:11:36
@@ -89,6 +89,7 @@
printk("page fault in interrupt handler, addr=%lx\n",
address);
show_regs(regs);
+ instruction_dump((unsigned long *)regs->nip);
#if defined(CONFIG_XMON) || defined(CONFIG_KGDB)
if (debugger_kernel_faults)
debugger(regs);
@@ -174,6 +175,7 @@
/* kernel has accessed a bad area */
show_regs(regs);
print_backtrace( (unsigned long *)regs->gpr[1] );
+ instruction_dump((unsigned long *)regs->nip);
#if defined(CONFIG_XMON) || defined(CONFIG_KGDB)
if (debugger_kernel_faults)
debugger(regs);
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next prev parent reply other threads:[~1998-12-06 1:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.05.9812051203360.1133-100000@p04-08.hartford.dialin.ntplx.com>
1998-12-06 0:07 ` ksymoops Tom Rini
1998-12-06 0:47 ` ksymoops Ryan Nielsen
1998-12-06 0:53 ` ksymoops Tom Rini
1998-12-06 1:48 ` Ryan Nielsen [this message]
1998-12-06 18:59 ` mousemode Louis Kowolowski
1998-12-06 21:54 ` mousemode Hollis R Blanchard
1998-12-07 1:14 ` mousemode Mike DeSimone
2000-08-11 8:15 ksymoops Iain Sandoe
-- strict thread matches above, loose matches on Subject: below --
2006-08-01 6:16 Ksymoops jagannathanjay
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=19981205174858.A31582@gondolin \
--to=ran@krazynet.com \
--cc=cort@persephone.cs.nmt.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@cs.anu.edu.au \
--cc=tmrini@ntplx.net \
/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;
as well as URLs for NNTP newsgroup(s).