xfslogd Page Allocation Failure

xfslogd Page Allocation Failure

[Federico Sevilla III]

[-- Attachment #1: Type: text/plain, Size: 2563 bytes --]

Hi,

I noticed the below logs in my dmesg. The machine continues to be
useable, and I'm not aware of which process wasn't able to perform
correctly. Is this a cause for concern? Hope you can advise.

Thank you very much.

xfslogd/1: page allocation failure. order:0, mode:0x0
Pid: 261, comm: xfslogd/1 Not tainted 2.6.24.2 #1

Call Trace:
 [<ffffffff8025a9b2>] __alloc_pages+0x223/0x381
 [<ffffffff802753be>] __slab_alloc+0x178/0x53b
 [<ffffffff80321c39>] free_address+0x17/0x66
 [<ffffffff802759ac>] kmem_cache_alloc+0x76/0x7c
 [<ffffffff80321c39>] free_address+0x17/0x66
 [<ffffffff80321d03>] xfs_buf_free+0x7b/0x7d
 [<ffffffff802eb4fc>] xfs_buf_iodone_callbacks+0x107/0x17b
 [<ffffffff80322ba0>] xfs_buf_iodone_work+0x0/0x72
 [<ffffffff8023ca2b>] run_workqueue+0x7f/0x108
 [<ffffffff8023d2ce>] worker_thread+0x0/0xc8
 [<ffffffff8023d35f>] worker_thread+0x91/0xc8
 [<ffffffff802405af>] autoremove_wake_function+0x0/0x2e
 [<ffffffff8023d2ce>] worker_thread+0x0/0xc8
 [<ffffffff8023d2ce>] worker_thread+0x0/0xc8
 [<ffffffff80240244>] kthread+0x3d/0x61
 [<ffffffff8020c638>] child_rip+0xa/0x12
 [<ffffffff80240207>] kthread+0x0/0x61
 [<ffffffff8020c62e>] child_rip+0x0/0x12

Mem-info:
DMA per-cpu:
CPU    0: Hot: hi:    0, btch:   1 usd:   0   Cold: hi:    0, btch:   1 usd:   0
CPU    1: Hot: hi:    0, btch:   1 usd:   0   Cold: hi:    0, btch:   1 usd:   0
DMA32 per-cpu:
CPU    0: Hot: hi:  186, btch:  31 usd: 137   Cold: hi:   62, btch:  15 usd:  47
CPU    1: Hot: hi:  186, btch:  31 usd: 135   Cold: hi:   62, btch:  15 usd:  48
Active:385341 inactive:88628 dirty:29329 writeback:5822 unstable:0
 free:3056 slab:17672 mapped:15772 pagetables:11363 bounce:0
DMA free:8016kB min:28kB low:32kB high:40kB active:2180kB inactive:976kB present:11424kB pages_scanned:32 all_unreclaimable? no
lowmem_reserve[]: 0 2004 2004 2004
DMA32 free:4208kB min:5712kB low:7140kB high:8568kB active:1539184kB inactive:353536kB present:2052196kB pages_scanned:795 all_unreclaimable? no
lowmem_reserve[]: 0 0 0 0
DMA: 18*4kB 31*8kB 29*16kB 32*32kB 23*64kB 3*128kB 1*256kB 0*512kB 0*1024kB 0*2048kB 1*4096kB = 8016kB
DMA32: 31*4kB 1*8kB 1*16kB 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 1*4096kB = 4244kB
Swap cache: add 3597048, delete 3537164, find 170970595/171758094, race 0+9658
Free swap  = 535892kB
Total swap = 1048568kB
Free swap:       535892kB
524256 pages of RAM
9091 reserved pages
357974 pages shared
59885 pages swap cached


-- 
Federico Sevilla III
F S 3 Consulting Inc.
http://www.fs3.ph

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: xfslogd Page Allocation Failure

[David Chinner]

On Fri, Apr 11, 2008 at 06:06:37PM +0800, Federico Sevilla III wrote:
> Hi,
> 
> I noticed the below logs in my dmesg. The machine continues to be
> useable, and I'm not aware of which process wasn't able to perform
> correctly. Is this a cause for concern? Hope you can advise.
> 
> Thank you very much.
> 
> xfslogd/1: page allocation failure. order:0, mode:0x0
> Pid: 261, comm: xfslogd/1 Not tainted 2.6.24.2 #1
> 
> Call Trace:
>  [<ffffffff8025a9b2>] __alloc_pages+0x223/0x381
>  [<ffffffff802753be>] __slab_alloc+0x178/0x53b
>  [<ffffffff80321c39>] free_address+0x17/0x66
>  [<ffffffff802759ac>] kmem_cache_alloc+0x76/0x7c
>  [<ffffffff80321c39>] free_address+0x17/0x66
>  [<ffffffff80321d03>] xfs_buf_free+0x7b/0x7d
>  [<ffffffff802eb4fc>] xfs_buf_iodone_callbacks+0x107/0x17b
>  [<ffffffff80322ba0>] xfs_buf_iodone_work+0x0/0x72

There's nothing to worry about from an XFs perspective from this
error message.  XFS handles the memory allocation error here and
does the right thing. The memory allocator is just being noisy.

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group