From: Keith Owens <kaos@ocs.com.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] panic on ia64 ; need help
Date: Tue, 26 Jun 2001 01:59:23 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005765@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005759@msgid-missing>
On Mon, 25 Jun 2001 13:32:30 -0600,
"MEHTA,HIREN (A-SanJose,ex1)" <hiren_mehta@agilent.com> wrote:
>Today I got a panic on a ia64 machine and the kernel jumped into
>the kdb (with serial port attached). The following was the output
>from panic.
>
>I looked at the call trace and it shows the same return address
>4 times. I did run id command on each of the function pointer on
>the stack and I looked at the sources as well. It is for sure that
>we are not calling the same function from itself. Can somebody
>help in trying to understand on what it really means when you
>see something like this (4 same return addresses) ?
>
>This panic is coming from a driver loaded as a module. Does anyone
>know how to link the panic output with the symbols in module ?
The kdb 'bt' command will give you a decoded backtrace.
If you have a copy of /proc/ksyms after the module was loaded, you can
run the oops through ksymoops. 'man insmod', read 'KSYMOOPS
ASSISTANCE' for automatically saving /proc/ksyms as modules are loaded
and unloaded.
You did not say which kernel or ia64 patch you were using. There were
errors in the unwind handling for ia64 modules that were not fixed
until 2.4.5-ia64-010530. This could cause the stack unwind to give
invalid results, including duplicate addresses.
prev parent reply other threads:[~2001-06-26 1:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-25 19:32 [Linux-ia64] panic on ia64 ; need help MEHTA,HIREN (A-SanJose,ex1)
2001-06-25 20:26 ` David Mosberger
2001-06-26 1:59 ` Keith Owens [this message]
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=marc-linux-ia64-105590693005765@msgid-missing \
--to=kaos@ocs.com.au \
--cc=linux-ia64@vger.kernel.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