From: Shawn Starr <spstarr@sh0n.net>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: Mike Galbraith <mikeg@wen-online.de>, lkm <linux-kernel@vger.kernel.org>
Subject: Re: [ANOMALIES]: 2.4.2 - __alloc_pages: failed - Patch failed
Date: Sat, 24 Feb 2001 17:31:55 -0500 [thread overview]
Message-ID: <3A98365A.451C4473@sh0n.net> (raw)
In-Reply-To: <Pine.LNX.4.21.0102241357220.3684-100000@freak.distro.conectiva>
Doing so..., Im not sure hot to use ksymoops or where to get that program.
I just usually use the sysq and dump but its ugly ;-)
Shawn.
Marcelo Tosatti wrote:
> On Fri, 23 Feb 2001, Shawn Starr wrote:
>
> > Feb 23 21:17:47 coredump kernel: __alloc_pages: 3-order allocation failed.
> > Feb 23 21:17:47 coredump kernel: __alloc_pages: 2-order allocation failed.
> > Feb 23 21:17:47 coredump kernel: __alloc_pages: 1-order allocation failed.
> > Feb 23 21:17:47 coredump kernel: __alloc_pages: 3-order allocation failed.
> > Feb 23 21:17:47 coredump kernel: __alloc_pages: 3-order allocation failed.
> > Feb 23 21:17:47 coredump kernel: __alloc_pages: 2-order allocation failed.
> > Feb 23 21:17:47 coredump kernel: __alloc_pages: 1-order allocation failed.
> >
> > didnt, work, still causing this..
>
> Ok, could you please add a line with "BUG();" after the
> printk("__alloc_pages: %d-order allocation failed", ..) in mm/page_alloc.c
> function __alloc_pages() ?
>
> This will make you get an oops when an allocation fails and if you decode
> it (with ksymoops) we can have a pretty useful backtrace to have more clue
> of what's failing.
>
> TIA
next prev parent reply other threads:[~2001-02-24 22:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0102231409010.496-100000@mikeg.weiden.de>
2001-02-23 21:11 ` [ANOMALIES]: 2.4.2 - __alloc_pages: failed & mount hanging withloop device issues Shawn Starr
2001-02-24 2:18 ` [ANOMALIES]: 2.4.2 - __alloc_pages: failed - Patch failed Shawn Starr
2001-02-24 16:01 ` Marcelo Tosatti
2001-02-24 22:31 ` Shawn Starr [this message]
2001-02-24 21:43 ` Arnaldo Carvalho de Melo
2001-02-25 1:03 ` [ANOMALIES]: 2.4.2 - __alloc_pages: ksysoops debug info Shawn Starr
2001-02-25 5:36 ` [ANOMALIES]: 2.4.2 - __alloc_pages: failed - Patch failed Mike Galbraith
2001-02-24 2:25 ` [ANOMALIES]: 2.4.2 - __alloc_pages: failed & mount hanging withloop device issues Rik van Riel
[not found] <Pine.LNX.4.33.0102250725180.1864-100000@mikeg.weiden.de>
2001-02-25 6:35 ` [ANOMALIES]: 2.4.2 - __alloc_pages: failed - Patch failed Shawn Starr
2001-02-25 8:03 ` Mike Galbraith
2001-02-25 23:13 ` Shawn Starr
2001-02-26 3:42 ` Marcelo Tosatti
2001-02-26 9:26 ` Alan Cox
2001-02-26 10:24 ` Marcelo Tosatti
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=3A98365A.451C4473@sh0n.net \
--to=spstarr@sh0n.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=mikeg@wen-online.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.