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 20:10:50 +0000 [thread overview]
Message-ID: <200403092010.i29KAom28428@unix-os.sc.intel.com> (raw)
In-Reply-To: <20040309160904.GF7569@mustard.americas.cpqcorp.net>
Jesse Barnes wrote on Tue, March 09, 2004 11:26 AM
> On Tue, Mar 09, 2004 at 10:57:48AM -0800, Grant Grundler wrote:
> > On Tue, Mar 09, 2004 at 01:47:15PM -0500, Aron Griffis wrote:
> > > Jesse Barnes wrote: [Tue Mar 09 2004, 12:54:25PM EST]
> > > > What kind of machine are you running on?
> > >
> > > Long's Peak.
> >
> > That's an RX2600 for anyone wanting to find the product on www.hp.com
>
> Ah, zx1 then. I accidentally deleted the original backtrace and it
> doesn't appear to be in the list archives yet, but I'm guessing that
> since the panic occured at arch/ia64/mm/contig.c:show_mem+0x100, I'm
> guessing the problem is somewhere after the call to show_free_areas().
> I don't have a zx1 box that's easy to test with, so I probably won't be
> much help.
Looks like it passed beyond show_free_areas(), faulting IP was in the
while loop accessing mem_map variable.
By the way, the local variable total is redundant in that function.
Same data already exists with max_mapnr.
- Ken
next prev parent reply other threads:[~2004-03-09 20:10 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 [this message]
2004-03-09 21:13 ` Aron Griffis
2004-03-09 21:36 ` Aron Griffis
2004-03-09 22:49 ` Kenneth Chen
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=200403092010.i29KAom28428@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