linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdlab.org>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Shane Wegner <shane@cm.nu>, linux-kernel@vger.kernel.org
Subject: Re: __alloc_pages: 0-order allocation failed still in -pre12
Date: Thu, 20 Sep 2001 08:02:45 -0700	[thread overview]
Message-ID: <3BAA0515.9CC823A1@osdlab.org> (raw)
In-Reply-To: <Pine.OSF.4.21.0109121502420.18976-100000@prfdec.natur.cuni.cz> <Pine.OSF.4.21.0109191615070.3826-100000@prfdec.natur.cuni.cz> <20010919153441.A30940@cm.nu> <20010920004543.Z720@athlon.random> <20010919193128.A8650@cm.nu> <20010919193649.A8824@cm.nu> <20010920045235.N720@athlon.random>

Andrea Arcangeli wrote:
> 
> Can you also resolve "c012e052" so we know who's allocating those pages
> just in case?

It's trivial to do that, of course, but if someone needs an
automated way to do it (several times, easy lookup), you can
try  http://www.osdlab.org/sw_resources/scripts/ksysmap .

Usage is:  ksysmap [system_map_file] offset

and it spits out address/symbol before offset, exact match if
present, and address/symbol after offset.

Example:

[rddunlap@dragon linux]$ ksysmap ./System.map-249acpi c012e052
ksysmap: searching './System.map-249acpi' for 'c012e052'

c012df20 T sys_truncate
c012e052 ..... <<<<<
c012e0a0 T sys_ftruncate

~Randy

  reply	other threads:[~2001-09-20 15:04 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-04 13:11 __alloc_pages: 0-order allocation failed Martin MOKREJŠ
2001-09-04 16:12 ` Daniel Phillips
2001-09-07 12:53   ` Martin MOKREJŠ
2001-09-07 13:06   ` Martin MOKREJŠ
2001-09-07 20:43     ` Daniel Phillips
2001-09-07 21:00     ` Daniel Phillips
2001-09-12 13:06       ` Martin MOKREJŠ
2001-09-19 14:21         ` __alloc_pages: 0-order allocation failed still in -pre12 Martin MOKREJŠ
2001-09-19 15:03           ` Martin MOKREJŠ
2001-09-19 15:16           ` Rik van Riel
2001-09-19 15:51             ` Martin MOKREJŠ
2001-09-19 22:34           ` Shane Wegner
2001-09-19 22:45             ` Andrea Arcangeli
2001-09-20  2:31               ` Shane Wegner
2001-09-20  2:36                 ` Andrea Arcangeli
2001-09-20  2:36                 ` Shane Wegner
2001-09-20  2:52                   ` Andrea Arcangeli
2001-09-20 15:02                     ` Randy.Dunlap [this message]
2001-09-21  1:54                       ` Keith Owens
2001-09-20  9:57                 ` Cannot compile 2.4.10pre12aa1 with 2.95.2 on Debian Martin MOKREJŠ
2001-09-20 10:10                   ` Magnus Naeslund(f)
2001-09-20 10:26                     ` Martin MOKREJŠ
2001-09-20 10:26                     ` Magnus Naeslund(f)
2001-09-20 10:59                     ` Perf improvements in 2.4.10pre12aa1 Martin MOKREJŠ
2001-09-20 15:28                       ` Martin MOKREJŠ
2001-09-20 15:40                         ` Martin MOKREJŠ
2001-09-20 10:24                   ` [PATCH] Make kernel build numbers work again (was: Re: Cannot compile 2.4.10pre12aa1 with 2.95.2 on Debian) Russell King
2001-09-20 12:54                     ` Alan Cox
2001-09-19 22:39           ` __alloc_pages: 0-order allocation failed still in -pre12 Andrea Arcangeli

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=3BAA0515.9CC823A1@osdlab.org \
    --to=rddunlap@osdlab.org \
    --cc=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shane@cm.nu \
    /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;
as well as URLs for NNTP newsgroup(s).