All of lore.kernel.org
 help / color / mirror / Atom feed
From: Serban Simu <serban@asperasoft.com>
To: linux-kernel@vger.kernel.org
Subject: page allocation failure & sk98lin
Date: Mon, 23 Aug 2004 23:28:40 -0700	[thread overview]
Message-ID: <412AE018.8000207@asperasoft.com> (raw)

Hello all,

I found a few references to similar problems in the list but no 
indications of whether this has been fixed or can be avoided.

I'm using 2.6.8.1 and the patch: sk98lin_v7.04_2.6.8_patch. This happens 
  when receiving data fast on the GigE card (about 600Mbps) and writing 
on disk. It seems to happen after writing 1 GB to disk (1024 MB) but I 
can't correlate that very reliably.

I would appreciate any information pointing me to a fix or explanation.

Thank you!

-Serban

swapper: page allocation failure. order:0, mode:0x20
  [<c013ec91>] __alloc_pages+0x2bf/0x2dd
  [<c013ecc7>] __get_free_pages+0x18/0x24
  [<c0141b8a>] kmem_getpages+0x20/0xc9
  [<c01427b3>] cache_grow+0xae/0x156
  [<c0142a2f>] cache_alloc_refill+0x1d4/0x211
  [<c0142e50>] __kmalloc+0x79/0x8c
  [<c027bd63>] alloc_skb+0x35/0xc9
  [<f8b7cbc4>] AllocAndMapRxBuffer+0x1e/0xc1 [sk98lin]
  [<f8b7af5a>] GiveRxBufferToHw+0x14e/0x3f4 [sk98lin]
  [<f8b7b274>] FillReceiveTableYukon2+0x74/0x7c [sk98lin]
  [<f8b7c467>] HandleStatusLEs+0xd4/0x30e [sk98lin]
  [<f8b7aa5f>] SkY2Poll+0x33/0xed [sk98lin]
  [<c02817cf>] net_rx_action+0x70/0xf2
  [<c0124fa2>] __do_softirq+0x52/0xab
  [<c0125028>] do_softirq+0x2d/0x2f
  [<c0107f9e>] do_IRQ+0xfb/0x112
  [<c01066d8>] common_interrupt+0x18/0x20
  [<c01040da>] mwait_idle+0x25/0x4a
  [<c01040a7>] cpu_idle+0x2e/0x3c
  [<c01216d5>] call_console_drivers+0xce/0xeb
  [<c01bb1b8>] vscnprintf+0x14/0x21
  [<c012191b>] printk+0x152/0x165


             reply	other threads:[~2004-08-24  6:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-24  6:28 Serban Simu [this message]
2004-08-24  7:50 ` page allocation failure & sk98lin Nick Piggin
2004-08-24 20:28   ` Serban Simu
2004-08-25  2:20     ` Nick Piggin

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=412AE018.8000207@asperasoft.com \
    --to=serban@asperasoft.com \
    --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.