http://bugme.osdl.org/show_bug.cgi?id=4153
------- Additional Comments From tino.keitel@xxxxxx 2005-02-03 05:35 -------
I got some more kernel messages now after the call trace:
tar: page allocation failure. order:5, mode:0xd0
[<c0142e59>] __alloc_pages+0x2f9/0x370
[<c0142ef5>] __get_free_pages+0x25/0x40
[<c0146a03>] kmem_getpages+0x23/0xd0
[<c01477b6>] cache_grow+0xe6/0x1e0
[<c0147a43>] cache_alloc_refill+0x193/0x250
[<c0141529>] mempool_alloc+0x79/0x180
[<c0147f78>] __kmalloc+0x88/0xa0
[<e07c84b9>] kmem_alloc+0x59/0xc0 [xfs]
[<e07a3220>] xfs_iread_extents+0x50/0x110 [xfs]
[<c02169a5>] as_add_request+0x1b5/0x220
[<e077a7fe>] xfs_bmapi+0x24e/0x1640 [xfs]
[<c020d855>] __elv_add_request+0x45/0xb0
[<c0210d3b>] __make_request+0x30b/0x590
[<c0165622>] bio_alloc+0x22/0x1e0
[<c011e420>] autoremove_wake_function+0x0/0x60
[<e00b2a5b>] __split_bio+0x12b/0x150 [dm_mod]
[<e07a766a>] xfs_iomap+0x19a/0x560 [xfs]
[<e07c9d3a>] linvfs_get_block_core+0xaa/0x300 [xfs]
[<c029c9b7>] schedule+0x4b7/0x8a0
[<e07c9fd4>] linvfs_get_block+0x44/0x50 [xfs]
[<c0185e18>] do_mpage_readpage+0x158/0x4b0
[<e07ccb76>] .text.lock.xfs_buf+0x37/0x41 [xfs]
[<e07cbb18>] pagebuf_iostart+0x78/0xc0 [xfs]
[<c01b5fff>] radix_tree_node_alloc+0x1f/0x70
[<c01b62dd>] radix_tree_insert+0xed/0x110
[<c013de52>] add_to_page_cache+0x72/0xf0
[<c01862bb>] mpage_readpages+0x14b/0x180
[<e07c9f90>] linvfs_get_block+0x0/0x50 [xfs]
[<e07a1e61>] xfs_iformat+0x4a1/0x5f0 [xfs]
[<e07a27fe>] xfs_xlate_dinode_core+0x13e/0x850 [xfs]
[<c0145f78>] read_pages+0x138/0x150
[<e07c9f90>] linvfs_get_block+0x0/0x50 [xfs]
[<c0142e70>] __alloc_pages+0x310/0x370
[<e00b5169>] dm_table_any_congested+0x19/0x70 [dm_mod]
[<e00b2ba0>] dm_any_congested+0x30/0x60 [dm_mod]
[<c01462f7>] do_page_cache_readahead+0x137/0x1d0
[<c014649d>] page_cache_readahead+0x10d/0x210
[<c013e867>] do_generic_mapping_read+0xc7/0x480
[<c013ef22>] __generic_file_aio_read+0x212/0x250
[<c013ec20>] file_read_actor+0x0/0xf0
[<e07d0d1f>] xfs_read+0x18f/0x2c0 [xfs]
[<e07ccc0b>] linvfs_read+0x8b/0xa0 [xfs]
[<c015f880>] do_sync_read+0x80/0xb0
[<c015ea58>] filp_open+0x68/0x70
[<c015f99d>] vfs_read+0xed/0x160
[<c015fc71>] sys_read+0x51/0x80
[<c01061fb>] syscall_call+0x7/0xb
possible deadlock in kmem_alloc (mode:0xd0)
possible deadlock in kmem_alloc (mode:0xd0)
possible deadlock in kmem_alloc (mode:0xd0)
possible deadlock in kmem_alloc (mode:0xd0)
possible deadlock in kmem_alloc (mode:0xd0)
possible deadlock in kmem_alloc (mode:0xd0)
possible deadlock in kmem_alloc (mode:0xd0)
possible deadlock in kmem_alloc (mode:0xd0)
possible deadlock in kmem_alloc (mode:0xd0)
possible deadlock in kmem_alloc (mode:0xd0)
possible deadlock in kmem_alloc (mode:0xd0)
possible deadlock in kmem_alloc (mode:0xd0)
possible deadlock in kmem_alloc (mode:0xd0)
possible deadlock in kmem_alloc (mode:0xd0)
possible deadlock in kmem_alloc (mode:0xd0)
possible deadlock in kmem_alloc (mode:0xd0)
possible deadlock in kmem_alloc (mode:0xd0)
possible deadlock in kmem_alloc (mode:0xd0)
possible deadlock in kmem_alloc (mode:0xd0)
I don't know how to reproduce this. It looks like I have an error on my XFS
partition and everytime the file with the error will be accessed, this kernel
message will occur.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
|