From: "Chris Friesen" <cfriesen@nortel.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: looking for help interpreting softlockup/stack trace
Date: Wed, 06 Aug 2008 12:35:58 -0600 [thread overview]
Message-ID: <4899EF0E.705@nortel.com> (raw)
In-Reply-To: <20080805191618.GB8629@linux-mips.org>
Ralf Baechle wrote:
> $LBB378 is an internal symbol. The value of RA may not be very informative
> if it was overwritten by a random subroutine call.
What determines which function names get compiled into the object file,
and which ones get these numerical symbols?
> You may also try lockdep; it gives much more detailed information though
> it's more heavyweight.
I would love to be able to use lockdep...however I'm stuck on an old kernel.
Chris
next prev parent reply other threads:[~2008-08-06 18:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 18:25 looking for help interpreting softlockup/stack trace Chris Friesen
2008-08-05 19:11 ` Kaz Kylheku
2008-08-05 19:11 ` Kaz Kylheku
2008-08-05 21:38 ` Chris Friesen
2008-08-05 19:16 ` Ralf Baechle
2008-08-06 18:35 ` Chris Friesen [this message]
2008-08-06 18:57 ` David Daney
2008-08-07 13:43 ` Ralf Baechle
2008-08-07 14:19 ` Thiemo Seufer
2008-08-07 21:57 ` David Daney
2008-08-05 20:28 ` Chad Reese
2008-08-05 20:46 ` Chris Friesen
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=4899EF0E.705@nortel.com \
--to=cfriesen@nortel.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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