mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@in.ibm.com>
To: Steven Truong <midair77@gmail.com>
Cc: linux-kernel@vger.kernel.org, crash-utility@redhat.com,
	Dave Anderson <anderson@redhat.com>
Subject: Re: kdump/kexec/crash on vmcore file
Date: Fri, 13 Oct 2006 10:14:46 -0400	[thread overview]
Message-ID: <20061013141446.GA27375@in.ibm.com> (raw)
In-Reply-To: <28bb77d30610121450n6cfd9c6ejd6b0370d2400a378@mail.gmail.com>

On Thu, Oct 12, 2006 at 02:50:33PM -0700, Steven Truong wrote:
> Hi, all.  This is my first attempt to troubleshoot a kernel panic so I
> am quite newbie in this area. I have been able to obtain a kdump when
> my box had kernel panic.
> 
> I set up Kdump and Kexec and then the captured/crash kernel to boot
> into Level 1 and then copy /proc/vmcore file to the disk for later
> analysis.  However, after the server booted back to Level 3 and I
> utilized the crash command to analyzed the vmcore file.  I got error
> message:
> 
> ./crash /boot/vmlinux ../vmcore.test
> 
> 
> crash: read error: kernel virtual address: ffffffff8123d1e0  type:
> "kernel_config_data"
> WARNING: cannot read kernel_config_data
> crash: read error: kernel virtual address: ffffffff813b5180  type: "xtime"
> 

Hi Steven,

which vmlinux are you using for analysis? First kernel's vmlinux or
second kernel's vmlinux. You should be using first kernel's vmlinux.

crash is trying to read some symbols from the core file and crash thinks
that virtual address for kernel_config_data is ffffffff8123d1e0. I think
this is too high a address. I guess this will be the address if you
compile your kernel for physical address 16MB. So my first guess is that
you are using second kernel's vmlinux for analysis.

Which kernel version and kexec-tools version are you using?

I am also copying the mail to crash-utility mailing list where folks
keep a watch on crash related issues.

Thanks
Vivek

  parent reply	other threads:[~2006-10-13 14:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-12 21:50 Steven Truong
2006-10-12 21:56 ` Steven Truong
2006-10-12 22:01   ` Steven Truong
2006-10-13 14:18     ` Vivek Goyal
2006-10-13 14:14 ` Vivek Goyal [this message]
2006-10-13 15:42   ` [Crash-utility] " Jean-Marc Saffroy
2006-10-13 17:51     ` Steven Truong
2006-10-13 17:50   ` Steven Truong

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=20061013141446.GA27375@in.ibm.com \
    --to=vgoyal@in.ibm.com \
    --cc=anderson@redhat.com \
    --cc=crash-utility@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=midair77@gmail.com \
    /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

all inboxes | Powered by JetHome®