From: Jaco Kroon <jkroon@cs.up.ac.za>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: OOPS in __alloc_pages on x86
Date: Wed, 07 Apr 2004 09:14:55 +0200 [thread overview]
Message-ID: <4073AA6F.3010308@cs.up.ac.za> (raw)
In-Reply-To: <20040406232215.62d88593.akpm@osdl.org>
Andrew Morton wrote:
>Jaco Kroon <jkroon@cs.up.ac.za> wrote:
>
>
>>And on 2.6.5:
>>
>>ifconfig: page allocation failure. order:0, mode:0x20
>>Call Trace:
>>[<c013df67>] __alloc_pages+0x2d7/0x390
>>[<c013e042>] __get_free_pages+0x22/0x60
>>[<c014216f>] cache_grow+0x11f/0x470
>>[<c014262f>] cache_alloc_refill+0x16f/0x4e0
>>[<c014306f>] kmem_cache_alloc+0x19f/0x1c0
>>[<c0260dfc>] alloc_skb+0x1c/0xe0
>>[<c023cb41>] tulip_init_ring+0xa1/0x160
>>[<c023c6f6>] tulip_open+0x36/0x50
>>[<c0265437>] dev_open+0xb7/0xf0
>>[<c0266cf8>] dev_change_flags+0x58/0x140
>>[<c02a4b27>] devinet_ioctl+0x2b7/0x6a0
>>[<c02a6cf0>] inet_ioctl+0xb0/0xf0
>>[<c025d93c>] sock_ioctl+0xac/0x260
>>[<c0174a1d>] sys_ioctl+0x8d/0x220
>>[<c0107a77>] syscall_call+0x7/0xb
>>
>>When configuring the network card upon boot.
>>
>>
>
>I don't know why you'd fail an allocation on boot. How much memory does
>that machine have?
>
>
64MB. And by upon boot I mean during the init process, not actually the
kernel boot itself. System startup might be a better phrase in the
context. By the time ifconfig executes there should still be plenty of
memory left, plus 128MB swap.
>You should increase /proc/sys/vm/min_free_kbytes.
>
>There's not a lot more we can do about this really, unless the driver is
>actually buggy. Perhaps the default min_free_kbytes could be increased for
>however much memory you have.
>
>
>
Will deffinately try this.
Thanks
Jaco
===========================================
This message and attachments are subject to a disclaimer. Please refer to www.it.up.ac.za/documentation/governance/disclaimer/ for full details.
Hierdie boodskap en aanhangsels is aan 'n vrywaringsklousule onderhewig. Volledige besonderhede is by www.it.up.ac.za/documentation/governance/disclaimer/ beskikbaar.
===========================================
prev parent reply other threads:[~2004-04-07 7:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-06 17:25 OOPS in __alloc_pages on x86 Jaco Kroon
2004-04-07 6:07 ` Jaco Kroon
2004-04-07 6:22 ` Andrew Morton
2004-04-07 7:14 ` Jaco Kroon [this message]
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=4073AA6F.3010308@cs.up.ac.za \
--to=jkroon@cs.up.ac.za \
--cc=akpm@osdl.org \
--cc=linux-kernel@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 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.