[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#273527: possible deadlock in kmem_alloc (mode 0x50)



Package: kernel-image-2.6.8-1-686
Version: 2.6.8-3

My gateway/fileserver machine running Debian Unstable was unresponsive
this morning.  When I plugged in a monitor and keyboard, I saw:

possible deadlock in kmem_alloc (mode 0x50) 

on the screen.  I was unable to get the machine to reboot, so I hit the
reset button.  After a reboot, I looked at /var/log/syslog and found
thousands of messages (see below).  I'm not a kernel hacker by any
means, so I'm submitting this in hopes that someone else can make sense
of it and forward it upstream, if appropriate.  

Just briefly, the machine is a Pentium III 1.0 Ghz, ASUS TUSI-M
motherboard, 384MB SDRAM.  I have XFS on /dev/md0 mounted at /raid is a
RAID1 array over two parallel ATA drives (/dev/hde and /dev/hdg); Debian
is installed on an EXT3 partition on /dev/hda, also a parallel ATA
drive.  

Here is the first message in syslog.  I have the entire relevant portion
of syslog saved (size is ~690k), as well as the machine's dmesg, if
necessary.  Please let me know if I can help in any other way.  

kernel: kswapd0: page allocation failure. order:4, mode:0x50
kernel:  [__alloc_pages+760/880] __alloc_pages+0x2f8/0x370
kernel:  [__get_free_pages+37/64] __get_free_pages+0x25/0x40
kernel:  [kmem_getpages+34/192] kmem_getpages+0x22/0xc0
kernel:  [cache_grow+186/384] cache_grow+0xba/0x180
kernel:  [cache_alloc_refill+362/544] cache_alloc_refill+0x16a/0x220
kernel:  [__kmalloc+116/128] __kmalloc+0x74/0x80
kernel:  [__crc_dq_data_lock+456637/3868974] kmem_alloc+0x59/0xc0 [xfs]
kernel:  [__crc_dq_data_lock+456927/3868974] kmem_realloc+0x2b/0x80
[xfs]
kernel:  [__crc_dq_data_lock+315547/3868974] xfs_iext_realloc+0xf7/0x150
[xfs]
kernel:  [__crc_dq_data_lock+136029/3868974] xfs_bmap_insert_exlist
+0x39/0x90 [xfs]
kernel:  [__crc_dq_data_lock+111221/3868974]
xfs_bmap_add_extent_delay_real+0x7b1/0x16b0 [xfs]
kernel:  [__crc_dq_data_lock+470791/3868974] _pagebuf_ioapply
+0x243/0x2f0 [xfs]
kernel:  [scheduler_tick+364/1104] scheduler_tick+0x16c/0x450
kernel:  [__crc_dq_data_lock+108936/3868974] xfs_bmap_add_extent
+0x3a4/0x4e0 [xfs]
kernel:  [__crc_dq_data_lock+144882/3868974] xfs_bmapi+0x73e/0x1610
[xfs]
kernel:  [__crc_dq_data_lock+468880/3868974] pagebuf_rele+0x2c/0x120
[xfs]
kernel:  [__crc_dq_data_lock+174467/3868974] xfs_bmbt_get_state
+0x2f/0x40 [xfs]
kernel:  [__crc_dq_data_lock+137200/3868974] xfs_bmap_do_search_extents
+0xbc/0x3f0 [xfs]
kernel:  [__crc_dq_data_lock+341475/3868974] xfs_log_reserve+0xbf/0xd0
[xfs]
kernel:  [__crc_dq_data_lock+330222/3868974] xfs_iomap_write_allocate
+0x2aa/0x4d0 [xfs]
kernel:  [__crc_dq_data_lock+326131/3868974] xfs_iomap+0x3ff/0x560 [xfs]
kernel:  [__crc_dq_data_lock+457788/3868974] xfs_map_blocks+0x58/0xa0
[xfs]
kernel:  [__crc_dq_data_lock+462167/3868974] xfs_page_state_convert
+0x513/0x680 [xfs]
kernel:  [free_buffer_head+57/112] free_buffer_head+0x39/0x70
kernel:  [__crc_dq_data_lock+464592/3868974] linvfs_release_page
+0xbc/0xe0 [xfs]
kernel:  [try_to_release_page+81/128] try_to_release_page+0x51/0x80
kernel:  [shrink_list+998/1248] shrink_list+0x3e6/0x4e0
kernel:  [shrink_cache+335/832] shrink_cache+0x14f/0x340
kernel:  [shrink_slab+120/416] shrink_slab+0x78/0x1a0
kernel:  [shrink_zone+170/224] shrink_zone+0xaa/0xe0
kernel:  [balance_pgdat+469/576] balance_pgdat+0x1d5/0x240
kernel:  [kswapd+210/240] kswapd+0xd2/0xf0
kernel:  [autoremove_wake_function+0/96] autoremove_wake_function
+0x0/0x60
kernel:  [ret_from_fork+6/20] ret_from_fork+0x6/0x14
kernel:  [autoremove_wake_function+0/96] autoremove_wake_function
+0x0/0x60
kernel:  [kswapd+0/240] kswapd+0x0/0xf0
kernel:  [kernel_thread_helper+5/24] kernel_thread_helper+0x5/0x18


-- 
jon@tgpsolutions.com

Administrator, tgpsolutions
http://www.tgpsolutions.com

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: