* ksymoops @ 2000-08-11 8:15 Iain Sandoe 0 siblings, 0 replies; 6+ messages in thread From: Iain Sandoe @ 2000-08-11 8:15 UTC (permalink / raw) To: linuxppc-dev Hi list, A couple of us are experiencing some trouble with the latest ksymoops (2.3.3/4). It says that the symbols mismatch between /proc/ksyms and the System.map. any ideas what is wrong? do we need a different version of ksyslogd? I'm using (I believe) the latest modutils & binutils. Iain. ** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/ ^ permalink raw reply [flat|nested] 6+ messages in thread
* Ksymoops @ 2006-08-01 6:16 jagannathanjay 0 siblings, 0 replies; 6+ messages in thread From: jagannathanjay @ 2006-08-01 6:16 UTC (permalink / raw) To: linuxppc-embedded [-- Attachment #1: Type: text/plain, Size: 501 bytes --] Hi all We are using a Embedded Planet 8260 board with Embedded linux loaded in it. The target processor is MPC 8260. We need a kysmoops (rpm) for debugging oops messages in kernel. Can anyone suggest the link or how can i install kysmoops for Embedded Planet 8260 board with Embedded linux? Regards Jay ________________________________________________________________________ Check Out the new free AIM(R) Mail -- 2 GB of storage and industry-leading spam and email virus protection. [-- Attachment #2: Type: text/html, Size: 728 bytes --] ^ permalink raw reply [flat|nested] 6+ messages in thread
[parent not found: <Pine.LNX.4.05.9812051203360.1133-100000@p04-08.hartford.dialin.ntplx.com>]
* Re: ksymoops [not found] <Pine.LNX.4.05.9812051203360.1133-100000@p04-08.hartford.dialin.ntplx.com> @ 1998-12-06 0:07 ` Tom Rini 1998-12-06 0:47 ` ksymoops Ryan Nielsen 1 sibling, 0 replies; 6+ messages in thread From: Tom Rini @ 1998-12-06 0:07 UTC (permalink / raw) To: linuxppc-dev On Sat, 5 Dec 1998, Tom Rini 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). nm. Found ksymmoops 0.6. On another note, anyone know why the patches in it for a more usaeable oops log aren't in vger/samba? --- Tom Rini (TR1265) http://dobbstown.yeti.edu/ [[ 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 ]] ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ksymoops [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 ` Ryan Nielsen 1998-12-06 0:53 ` ksymoops Tom Rini 1 sibling, 1 reply; 6+ messages in thread From: Ryan Nielsen @ 1998-12-06 0:47 UTC (permalink / raw) To: Tom Rini, linuxppc-dev > 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 [[ 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 ]] ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ksymoops 1998-12-06 0:47 ` ksymoops Ryan Nielsen @ 1998-12-06 0:53 ` Tom Rini 1998-12-06 1:48 ` ksymoops Ryan Nielsen 0 siblings, 1 reply; 6+ messages in thread From: Tom Rini @ 1998-12-06 0:53 UTC (permalink / raw) To: Ryan Nielsen; +Cc: linuxppc-dev 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? --- Tom Rini (TR1265) http://dobbstown.yeti.edu/ [[ 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 ]] ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ksymoops 1998-12-06 0:53 ` ksymoops Tom Rini @ 1998-12-06 1:48 ` Ryan Nielsen 0 siblings, 0 replies; 6+ messages in thread From: Ryan Nielsen @ 1998-12-06 1:48 UTC (permalink / raw) To: Tom Rini; +Cc: linuxppc-dev, Cort Dougan, Paul Mackerras 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 ]] ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2006-08-01 6:17 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2000-08-11 8:15 ksymoops Iain Sandoe
-- strict thread matches above, loose matches on Subject: below --
2006-08-01 6:16 Ksymoops jagannathanjay
[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 ` ksymoops Ryan Nielsen
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).