From: LaMont Jones <lamont@hp.com>
To: Grant Grundler <grundler@puffin.external.hp.com>
Cc: Matthew Wilcox <willy@debian.org>,
parisc-linux@lists.parisc-linux.org, lamont@hp.com
Subject: B132 dies too (was Re: [parisc-linux] 2.4.6-pa5 crashes on B160L)
Date: Mon, 09 Jul 2001 09:34:38 -0600 [thread overview]
Message-ID: <20010709153451.4D2731872C@security.hp.com> (raw)
In-Reply-To: Your message of "Sun, 08 Jul 2001 17:31:25 MDT." <200107082331.RAA09058@puffin.external.hp.com>
My B132 (which works 2.4.0) crashes sometime between palo launching the
kernel, and it having a working console (serial). That is to say, no info
at all. If someone wants the machine in order to debug it, just holler...
> If one is really good (like jsm) and has a matching vmlinux and System.map,
> one can backtrace the stack by hand by looking at stack frame (return pointer
> is in the stack frame) and seeing how much each subroutine grows the stack
> (look at code around subroutine call, iirc). I think the mail archives
> have a concise desription of exactly how to use the stack dump.
> But I am too lazy to look for it now.
Backtracing is extremely straight-forward, and can be automated, AFAIK.
Walking the stack forward is a bit more challenging, but not entirely
beyond possibility most of the time...
lamont
next prev parent reply other threads:[~2001-07-09 15:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-08 15:21 [parisc-linux] 2.4.6-pa5 crashes on B160L Scott Ashcroft
2001-07-08 21:10 ` Matthew Wilcox
2001-07-08 23:31 ` Grant Grundler
2001-07-08 23:48 ` Matthew Wilcox
2001-07-09 1:20 ` Grant Grundler
2001-07-09 15:34 ` LaMont Jones [this message]
2001-07-09 1:41 ` Scott Ashcroft
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=20010709153451.4D2731872C@security.hp.com \
--to=lamont@hp.com \
--cc=grundler@puffin.external.hp.com \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=willy@debian.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