linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@bonn-fries.net>
To: Andrew Kay <Andrew.J.Kay@syntegra.com>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>, linux-mm@kvack.org
Subject: Re: kernel: __alloc_pages: 1-order allocation failed
Date: Wed, 29 Aug 2001 20:00:35 +0200	[thread overview]
Message-ID: <20010829175351Z16158-32383+2308@humbolt.nl.linux.org> (raw)
In-Reply-To: <3B8D14E5.7070204@syntegra.com>

On August 29, 2001 06:14 pm, Andrew Kay wrote:
> > OK, it's not a bounce buffer because the allocation isn't __GFP_WAIT 
(0x10).
> > It's GFP_ATOMIC and there are several hundred of those throughout the 
kernel so
> > I'm not going to try to guess which one.  Could you please pass a few of 
your
> > backtraces through ksymoops make them meaningful?
> > Daniel
> 
> I'm not sure I did this right, but here is my attempt.  I ran a 
> 'ksymoops' and gave it a couple of the errors.  The parts that look 
> somewhat recognizable are the sk98lin, which is a Syskonnect gig over 
> copper card.  It is the only module I have running on the system.

Close, but see the warning where it tells you your System.map doesn't match 
your running kernel.  Try symlinking /boot/System.map to the System.map in
the source tree you built from.

> Warning: You did not tell me where to find symbol information.  I will
> assume that the log matches the kernel and modules that are running
> right now and I'll use the default options above for symbol resolution.
> If the current kernel and/or modules do not match the log, you can get
> more accurate output by telling me the kernel version and where to find
> map, modules, ksyms etc.  ksymoops -h explains the options.

I'm willing to guess at this point that this atomic failure is not a bug, the 
only bug is that we print the warning message, potentially slowing things 
down.  I'd like to see a correct backtrace first.

Do you detect any slowdown in your system when you're getting these messages? 
I wouldn't expect so from what you've described so far.

--
Daniel
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

  reply	other threads:[~2001-08-29 18:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-27 20:14 Andrew Kay
2001-08-27 22:57 ` Daniel Phillips
2001-08-27 22:28   ` Marcelo Tosatti
2001-08-28  0:08     ` Daniel Phillips
2001-08-29 13:48       ` Andrew Kay
2001-08-29 15:13         ` Daniel Phillips
2001-08-29 16:14           ` Andrew Kay
2001-08-29 18:00             ` Daniel Phillips [this message]
2001-08-30 14:24               ` Andrew Kay
2001-08-30 22:19                 ` Daniel Phillips
2001-08-30 22:39                   ` Andrew Kay
2001-08-30 23:04                     ` Daniel Phillips
2001-08-31 13:44                       ` Andrew Kay
2001-08-28  6:27     ` Roger Larsson

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=20010829175351Z16158-32383+2308@humbolt.nl.linux.org \
    --to=phillips@bonn-fries.net \
    --cc=Andrew.J.Kay@syntegra.com \
    --cc=linux-mm@kvack.org \
    --cc=marcelo@conectiva.com.br \
    /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