Home
Reading
Searching
Subscribe
Sponsors
Statistics
Posting
Contact
Spam
Lists
Links
About
Hosting
Filtering
Features Download
Marketing
Archives
FAQ
Blog
 
Gmane
From: Dave Jones <davej <at> codemonkey.org.uk>
Subject: GFP_ATOMIC page allocation failures.
Newsgroups: gmane.linux.kernel
Date: Tuesday 1st April 2008 23:56:09 UTC (over 8 years ago)
I found a few ways to cause pages and pages of spew to dmesg
of the following form..

rhythmbox: page allocation failure. order:3, mode:0x4020
Pid: 4299, comm: rhythmbox Not tainted 2.6.25-0.172.rc7.git4.fc9.x86_64 #1

Call Trace:
   [] __alloc_pages+0x3a3/0x3c3
 [] ? trace_hardirqs_on_thunk+0x35/0x3a
 [] alloc_pages_current+0x100/0x109
 [] new_slab+0x4a/0x249
 [] __slab_alloc+0x251/0x4e0
 [] ? __netdev_alloc_skb+0x31/0x4f
 [] __kmalloc_node_track_caller+0x8a/0xe2
 [] ? __netdev_alloc_skb+0x31/0x4f
 [] __alloc_skb+0x6f/0x135
 [] __netdev_alloc_skb+0x31/0x4f
 [] :e1000e:e1000_alloc_rx_buffers+0xb7/0x1dc
 [] :e1000e:e1000_clean_rx_irq+0x271/0x307
 [] :e1000e:e1000_clean+0x66/0x205
 [] net_rx_action+0xd9/0x20e
 [] __do_softirq+0x70/0xf1
 [] call_softirq+0x1c/0x28
 [] do_softirq+0x39/0x8a
 [] irq_exit+0x4e/0x8f
 [] do_IRQ+0x145/0x167
 [] ret_from_intr+0x0/0xf
   [] ? _spin_unlock_irqrestore+0x42/0x47
 [] ? __wake_up+0x43/0x50
 [] ? wake_futex+0x47/0x53
 [] ? do_futex+0x697/0xc57
 [] ? hrtick_set+0xa1/0xfc
 [] ? sys_futex+0xf5/0x113
 [] ? syscall_trace_enter+0xb5/0xb9
 [] ? tracesys+0xd5/0xda


Given that we seem to recover from these events without negative effects
(ie, no apps get oom-killed), is there any value to actually flooding
syslog with this stuff ?

iirc, SuSE have been patching out these traces for GFP_ATOMIC allocations
for a long time.  Should mainline do the same ?

	Dave

-- 
http://www.codemonkey.org.uk
 
CD: 2ms