public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Kenneth Chen" <kenneth.w.chen@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: crash on SysRq : Show Memory
Date: Tue, 09 Mar 2004 22:49:26 +0000	[thread overview]
Message-ID: <200403092249.i29MnQm30840@unix-os.sc.intel.com> (raw)
In-Reply-To: <20040309160904.GF7569@mustard.americas.cpqcorp.net>

Aron Griffis wrote on Tue, March 09, 2004 1:36 PM
> > Looks like it passed beyond show_free_areas(), faulting IP was
> > in the while loop accessing mem_map variable.

> How did you determine that?

Do objdump on vmlinux, then look at the disassembled code at
faulting IP:

Show_mem+0x100
a00000010003cd00:    [MMI]       ld4.acq r21=[r16];;

It is page faulting on r16, lookup r16 in the panic dump, it shows:
r16 : a0007fffff0fffb0, which basically points to a page struct in
the mem_map array, you might want to verify whether that address is
valid or not.

Exam the code up/down a little bit, you would realize the while loop
is in between show_mem+0xe0 and show_mem+0x1dc, variable i is stored
in r17/r3, lookup up these instructions to see how the pointer is
calculated with index i:
(i*5*16 + base mem_map, sizeof(struct page) = 80).

a00000010003cce6:                  sxt4 r23=r17;;
a00000010003ccec:                  shladd r22=r23,2,r23;;
a00000010003ccf0:      [MMI]       shladd r16=r22,4,r19;;

Anyway, hope you get the idea ....

- Ken



  parent reply	other threads:[~2004-03-09 22:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-09 16:09 crash on SysRq : Show Memory Aron Griffis
2004-03-09 17:14 ` Aron Griffis
2004-03-09 17:21 ` Aron Griffis
2004-03-09 17:54 ` Jesse Barnes
2004-03-09 18:47 ` Aron Griffis
2004-03-09 18:57 ` Grant Grundler
2004-03-09 19:25 ` Jesse Barnes
2004-03-09 20:10 ` Kenneth Chen
2004-03-09 21:13 ` Aron Griffis
2004-03-09 21:36 ` Aron Griffis
2004-03-09 22:49 ` Kenneth Chen [this message]
2004-03-09 23:31 ` Aron Griffis
2004-03-09 23:39 ` Andreas Schwab

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=200403092249.i29MnQm30840@unix-os.sc.intel.com \
    --to=kenneth.w.chen@intel.com \
    --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