From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: GFP_ATOMIC page allocation failures.
Date: Wed, 2 Apr 2008 12:28:16 +1100 [thread overview]
Message-ID: <200804021228.16875.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <20080401235609.GA6947@codemonkey.org.uk>
On Wednesday 02 April 2008 10:56, Dave Jones wrote:
> 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:
> <IRQ> [<ffffffff810862dc>] __alloc_pages+0x3a3/0x3c3
> [<ffffffff812a58df>] ? trace_hardirqs_on_thunk+0x35/0x3a
> [<ffffffff8109fd94>] alloc_pages_current+0x100/0x109
> [<ffffffff810a6fd5>] new_slab+0x4a/0x249
> [<ffffffff810a776a>] __slab_alloc+0x251/0x4e0
> [<ffffffff8121c322>] ? __netdev_alloc_skb+0x31/0x4f
> [<ffffffff810a8736>] __kmalloc_node_track_caller+0x8a/0xe2
> [<ffffffff8121c322>] ? __netdev_alloc_skb+0x31/0x4f
> [<ffffffff8121b5db>] __alloc_skb+0x6f/0x135
> [<ffffffff8121c322>] __netdev_alloc_skb+0x31/0x4f
> [<ffffffff8814e5b4>] :e1000e:e1000_alloc_rx_buffers+0xb7/0x1dc
> [<ffffffff8814eada>] :e1000e:e1000_clean_rx_irq+0x271/0x307
> [<ffffffff8814c71a>] :e1000e:e1000_clean+0x66/0x205
> [<ffffffff8121eeb8>] net_rx_action+0xd9/0x20e
> [<ffffffff81038757>] __do_softirq+0x70/0xf1
> [<ffffffff8100d25c>] call_softirq+0x1c/0x28
> [<ffffffff8100e485>] do_softirq+0x39/0x8a
> [<ffffffff81038290>] irq_exit+0x4e/0x8f
> [<ffffffff8100e781>] do_IRQ+0x145/0x167
> [<ffffffff8100c5e6>] ret_from_intr+0x0/0xf
> <EOI> [<ffffffff812a5ed8>] ? _spin_unlock_irqrestore+0x42/0x47
> [<ffffffff8102a040>] ? __wake_up+0x43/0x50
> [<ffffffff81056b7f>] ? wake_futex+0x47/0x53
> [<ffffffff810584cf>] ? do_futex+0x697/0xc57
> [<ffffffff8102fbc4>] ? hrtick_set+0xa1/0xfc
> [<ffffffff81058b84>] ? sys_futex+0xf5/0x113
> [<ffffffff810133e7>] ? syscall_trace_enter+0xb5/0xb9
> [<ffffffff8100c1d0>] ? 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 ?
It's nice to have. Perhaps it could just be hardlimited to print
say 10 times, and maybe we could have a vmstat counter to keep
count after that.
next prev parent reply other threads:[~2008-04-02 1:28 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 23:56 GFP_ATOMIC page allocation failures Dave Jones
2008-04-02 1:28 ` Nick Piggin [this message]
2008-04-02 1:35 ` Dave Jones
2008-04-02 6:28 ` Chris Snook
2008-04-02 7:56 ` Andrew Morton
2008-04-02 8:17 ` KOSAKI Motohiro
2008-04-02 8:24 ` David Miller
2008-04-02 8:43 ` Andrew Morton
2008-04-02 10:00 ` KOSAKI Motohiro
2008-04-02 10:56 ` KOSAKI Motohiro
2008-04-02 18:44 ` David Miller
2008-04-02 20:12 ` Michael Chan
2008-04-02 20:53 ` David Miller
2008-04-02 11:04 ` Peter Zijlstra
2008-04-02 18:45 ` David Miller
2008-04-02 19:06 ` Jeff Garzik
2008-04-02 9:12 ` Nick Piggin
2008-04-02 15:54 ` Andrew Morton
2008-04-03 5:22 ` Nick Piggin
2008-04-03 5:32 ` Andrew Morton
2008-04-03 8:59 ` Evgeniy Polyakov
2008-06-26 21:06 ` Dave Jones
2008-06-26 22:26 ` Chris Snook
2008-06-27 10:01 ` Evgeniy Polyakov
2008-04-02 17:21 ` Jeff Garzik
2008-04-02 17:33 ` Andrew Morton
2008-04-02 18:18 ` Jeff Garzik
2008-04-02 18:37 ` Kok, Auke
2008-04-03 5:57 ` Nick Piggin
2008-04-03 18:20 ` Jeff Garzik
[not found] <adYyJ-20N-11@gated-at.bofh.it>
[not found] ` <aef6w-6rx-45@gated-at.bofh.it>
[not found] ` <aefJ9-7KR-15@gated-at.bofh.it>
[not found] ` <aeqF6-45P-29@gated-at.bofh.it>
2008-04-04 9:52 ` Bodo Eggert
2008-04-04 10:59 ` Nick Piggin
2008-04-04 11:35 ` Bodo Eggert
2008-04-05 1:06 ` Nick Piggin
2008-04-06 12:12 ` Bodo Eggert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200804021228.16875.nickpiggin@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox