From: Ruben Rubio Rey <ruben@rentalia.com>
To: linux-kernel@vger.kernel.org
Subject: 2.6.9-1.667smp perl page allocation failure
Date: Wed, 14 Sep 2005 12:51:22 +0200 [thread overview]
Message-ID: <432800AA.10500@rentalia.com> (raw)
Hi,
Im specting some problems with a server. Somtimes (each 7 days more or
less) i can found some
errors in dmesg like the following:
perl5.8.5: page allocation failure. order:4, mode:0x50
[<0213d396>] __alloc_pages+0x28b/0x298
[<0213d3bb>] __get_free_pages+0x18/0x24
[<0213fc88>] kmem_getpages+0x1c/0xbb
[<021407d9>] cache_grow+0xae/0x136
[<021409c6>] cache_alloc_refill+0x165/0x19d
[<02140d9d>] __kmalloc+0x76/0x88
[<8293ee20>] kmem_alloc+0x50/0x9e [xfs]
[<8293eef0>] kmem_realloc+0x17/0x52 [xfs]
[<82924188>] xfs_iext_realloc+0xc9/0xdc [xfs]
[<82901912>] xfs_bmap_insert_exlist+0x22/0x77 [xfs]
[<828fed42>] xfs_bmap_add_extent_hole_delay+0x438/0x48e [xfs]
[<828fc7b4>] xfs_bmap_add_extent+0x146/0x399 [xfs]
[<829039bc>] xfs_bmapi+0xb00/0x12bf [xfs]
[<829031e2>] xfs_bmapi+0x326/0x12bf [xfs]
[<021398ef>] wake_up_page+0x9/0x29
[<82926bdf>] xfs_iomap_write_delay+0x628/0x702 [xfs]
[<8292ad03>] xlog_state_get_iclog_space+0x163/0x172 [xfs]
[<82925b32>] xfs_imap_to_bmap+0x2a/0x28a [xfs]
[<82925fcc>] xfs_iomap+0x23a/0x3ec [xfs]
[<82926076>] xfs_iomap+0x2e4/0x3ec [xfs]
[<82945e39>] xfs_bmap+0x1a/0x1e [xfs]
[<8294005f>] linvfs_get_block_core+0x6b/0x257 [xfs]
[<02139c3f>] find_or_create_page+0x18/0x72
[<022b7b17>] __cond_resched+0x14/0x39
[<02156002>] set_bh_page+0x2c/0x34
[<8294025e>] linvfs_get_block+0x13/0x17 [xfs]
[<0215664f>] __block_prepare_write+0x15d/0x3e4
[<02156f61>] block_prepare_write+0x16/0x23
[<8294024b>] linvfs_get_block+0x0/0x17 [xfs]
[<82940578>] linvfs_prepare_write+0x12/0x16 [xfs]
[<8294024b>] linvfs_get_block+0x0/0x17 [xfs]
[<0213b3c8>] generic_file_buffered_write+0x1b5/0x4ae
[<8290e4ed>] xfs_da_brelse+0x73/0x92 [xfs]
[<828f7400>] xfs_attr_leaf_get+0x4b/0x82 [xfs]
[<82945a87>] xfs_write+0x622/0x982 [xfs]
[<8294230d>] linvfs_write+0x6f/0x77 [xfs]
[<02153d7b>] do_sync_write+0x97/0xc9
[<8293a4d9>] xfs_inactive_free_eofblocks+0xd2/0x210 [xfs]
[<0211deca>] autoremove_wake_function+0x0/0x2d
[<02153e63>] vfs_write+0xb6/0xe2
[<02153f2d>] sys_write+0x3c/0x62
possible deadlock in kmem_alloc (mode:0x50)
There is alot of errors in a few second like that and its always follow
by several "possible deadlock in kmem_alloc (mode:0x50)"
Whats does it means?
The error is on a production server, is it dangerous?
What shoud I do to fix it?
Some extra info:
Filesystem: XFS
Kernel: 2.6.9-1.667smp
Thanks in advance. I have been searching several days and I have found nothing .
Ruben Rubio Rey
reply other threads:[~2005-09-14 10:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=432800AA.10500@rentalia.com \
--to=ruben@rentalia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox