From: Grant Grundler <grundler@cup.hp.com>
To: Greg Ingram <ingram@symsys.com>
Cc: Linux/HPPA List <parisc-linux@parisc-linux.org>
Subject: Re: [parisc-linux] C100 & Latest CVS Bits
Date: Tue, 13 Feb 2001 11:46:34 -0800 [thread overview]
Message-ID: <200102131946.LAA10733@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Tue, 13 Feb 2001 12:32:01 PST." <Pine.LNX.4.21.0102131225540.14493-100000@maestro.symsys.com>
Greg Ingram wrote:
> As I recall, Grant said the stack dump itself isn't
> helpful unless it's a kernel built with the default configuration.
I can't (or won't) help with stack/register dumps unless they are built
with default config. That's different than saying they aren't helpful.
The problem is the symbols are what's interesting to me and I can't
determine them unless the bits match what's in a source tree I have.
I guess it's time we put together a "PARISC Kernel Debugging HOW-TO
for Dummies". ie how to look up symbols, explain TOC (and HPMC), how
to get/decode TOC/HPMC dumps, etc.
> As a side question, is it possible to have the system automatically reboot
> after it encounters these errors?
It can. There's a global variable someplace that is *disabled* by default.
If someone can just remember the global's name...
grant
Grant Grundler
parisc-linux {PCI|IOMMU|SMP} hacker
+1.408.447.7253
next prev parent reply other threads:[~2001-02-13 19:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-26 0:48 [parisc-linux] linux-2.4.0 Matthew Wilcox
2001-01-26 1:57 ` Grant Grundler
2001-01-26 3:04 ` Matthew Wilcox
2001-01-31 16:16 ` Alan Cox
2001-01-31 18:49 ` Andrew Shugg
2001-02-02 2:52 ` Matthew Wilcox
2001-02-13 18:32 ` [parisc-linux] C100 & Latest CVS Bits Greg Ingram
2001-02-13 19:46 ` Grant Grundler [this message]
2001-02-13 20:16 ` Greg Ingram
2001-02-13 22:46 ` Steven Pritchard
2001-02-14 16:17 ` Auto-rebooting (was Re: [parisc-linux] C100 & Latest CVS Bits) Greg Ingram
2001-01-26 10:23 ` [parisc-linux] linux-2.4.0 Richard Hirst
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=200102131946.LAA10733@milano.cup.hp.com \
--to=grundler@cup.hp.com \
--cc=ingram@symsys.com \
--cc=parisc-linux@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