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
|