From: Eric Dumazet <eric.dumazet@gmail.com>
To: Denys Fedoryshchenko <denys@visp.net.lb>
Cc: netdev@vger.kernel.org
Subject: Re: 2.6.39-rc7-git11, x86/32, failed on ppp2897'th interface, PERCPU: allocation failed
Date: Thu, 19 May 2011 08:39:18 +0200 [thread overview]
Message-ID: <1305787158.3019.12.camel@edumazet-laptop> (raw)
In-Reply-To: <f9797bb034f650a24e927629d1ab77d8@visp.net.lb>
Le jeudi 19 mai 2011 à 09:35 +0300, Denys Fedoryshchenko a écrit :
> Hi, again
>
> Just tried to upgrade large NAS from 2.6.38.6 to 2.6.39-rc7-git11, and
> at same time enabling ipv6 on it.
> Got that, after ppp2897 brought up (sure it means there is other 2896
> available, and also few ethernet vlans, around 32).
> I am not sure it is a bug, but it looks i had free memory(the box had
> 8GB free), and lowmem too, also i will try to enable there 64bit kernel
> at evening.
>
> May 17 16:00:42 194.146.155.70 kernel: [14925.897799] PERCPU:
> allocation failed, size=2048 align=4, failed to allocate new chunk
> May 17 16:00:42 194.146.155.70 kernel: [14925.898163] Pid: 24207, comm:
> pppd Not tainted 2.6.39-rc7-git11-build-0058 #4
> May 17 16:00:42 194.146.155.70 kernel: [14925.898164] Call Trace:
> May 17 16:00:42 194.146.155.70 kernel: [14925.898169] [<c0335548>] ?
> printk+0x18/0x20
> May 17 16:00:42 194.146.155.70 kernel: [14925.898173] [<c017ecd0>]
> pcpu_alloc+0x616/0x67a
> May 17 16:00:42 194.146.155.70 kernel: [14925.898176] [<c0194a80>] ?
> __kmalloc_track_caller+0x68/0xc0
> May 17 16:00:42 194.146.155.70 kernel: [14925.898189] [<f8ae196c>] ?
> kzalloc+0xb/0xd [ipv6]
> May 17 16:00:42 194.146.155.70 kernel: [14925.898193] [<c01320a5>] ?
> _local_bh_enable_ip.clone.6+0x18/0x71
> May 17 16:00:42 194.146.155.70 kernel: [14925.898195] [<c017ed3e>]
> __alloc_percpu+0xa/0xc
> May 17 16:00:42 194.146.155.70 kernel: [14925.898198] [<c030aa7d>]
> snmp_mib_init+0x2f/0x51
> May 17 16:00:42 194.146.155.70 kernel: [14925.898207] [<f8ae2ad0>]
> ipv6_add_dev+0x133/0x2a3 [ipv6]
> May 17 16:00:42 194.146.155.70 kernel: [14925.898209] [<c030e12d>] ?
> ip_mc_init_dev+0x75/0x86
> May 17 16:00:42 194.146.155.70 kernel: [14925.898211] [<c0309321>] ?
> devinet_sysctl_register+0x34/0x38
> May 17 16:00:42 194.146.155.70 kernel: [14925.898221] [<f8ae5754>]
> addrconf_notify+0x50/0x6a5 [ipv6]
> May 17 16:00:42 194.146.155.70 kernel: [14925.898224] [<c0218f52>] ?
> add_uevent_var+0xa3/0xa3
> May 17 16:00:42 194.146.155.70 kernel: [14925.898226] [<c0309901>] ?
> inetdev_event+0x55/0x3c0
> May 17 16:00:42 194.146.155.70 kernel: [14925.898230] [<c01446f9>]
> notifier_call_chain+0x26/0x48
> May 17 16:00:42 194.146.155.70 kernel: [14925.898232] [<c01447a7>]
> raw_notifier_call_chain+0x1a/0x1c
> May 17 16:00:42 194.146.155.70 kernel: [14925.898236] [<c02c8115>]
> call_netdevice_notifiers+0x44/0x4b
> May 17 16:00:42 194.146.155.70 kernel: [14925.898238] [<c01320a5>] ?
> _local_bh_enable_ip.clone.6+0x18/0x71
> May 17 16:00:42 194.146.155.70 kernel: [14925.898240] [<c0132106>] ?
> local_bh_enable_ip+0x8/0xa
> May 17 16:00:42 194.146.155.70 kernel: [14925.898242] [<c02ca19b>]
> register_netdevice+0x1fb/0x255
> May 17 16:00:42 194.146.155.70 kernel: [14925.898244] [<c02ca227>]
> register_netdev+0x32/0x41
> May 17 16:00:42 194.146.155.70 kernel: [14925.898247] [<c021d5cf>] ?
> sprintf+0x1c/0x1e
> May 17 16:00:42 194.146.155.70 kernel: [14925.898249] [<c029647a>]
> ppp_ioctl+0x224/0xaea
> May 17 16:00:42 194.146.155.70 kernel: [14925.898252] [<c01a35cc>] ?
> do_filp_open+0x26/0x67
> May 17 16:00:42 194.146.155.70 kernel: [14925.898254] [<c0296256>] ?
> ppp_write+0x98/0x98
> May 17 16:00:42 194.146.155.70 kernel: [14925.898256] [<c01a53ce>]
> do_vfs_ioctl+0x45e/0x498
> May 17 16:00:42 194.146.155.70 kernel: [14925.898258] [<c01a118e>] ?
> getname_flags+0x1e/0xad
> May 17 16:00:42 194.146.155.70 kernel: [14925.898260] [<c019391b>] ?
> kmem_cache_free+0x14/0x83
> May 17 16:00:42 194.146.155.70 kernel: [14925.898262] [<c01ab5bb>] ?
> alloc_fd+0x4e/0xba
> May 17 16:00:42 194.146.155.70 kernel: [14925.898265] [<c0199465>] ?
> do_sys_open+0xdb/0xe5
> May 17 16:00:42 194.146.155.70 kernel: [14925.898266] [<c019ac7b>] ?
> fput+0x13/0x155
> May 17 16:00:42 194.146.155.70 kernel: [14925.898268] [<c01a4387>] ?
> do_fcntl+0x227/0x3aa
> May 17 16:00:42 194.146.155.70 kernel: [14925.898270] [<c01a543b>]
> sys_ioctl+0x33/0x4c
> May 17 16:00:42 194.146.155.70 kernel: [14925.898273] [<c0336edd>]
> syscall_call+0x7/0xb
> --
Its a known problem : When ipv6 is enabled, we allocate percpu memory to
hold per device snmp counters.
make sure kernel idea of max possible cpus matches real number of cpus.
And yes, switching to 64bit kernel helps a lot.
next prev parent reply other threads:[~2011-05-19 6:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-19 6:35 2.6.39-rc7-git11, x86/32, failed on ppp2897'th interface, PERCPU: allocation failed Denys Fedoryshchenko
2011-05-19 6:39 ` Eric Dumazet [this message]
2011-05-19 6:47 ` Denys Fedoryshchenko
2011-05-19 6:55 ` Eric Dumazet
2011-05-19 7:28 ` Denys Fedoryshchenko
2011-05-19 7:44 ` Eric Dumazet
2011-05-19 11:14 ` [PATCH net-next-2.6] ipv6: reduce per device ICMP mib sizes Eric Dumazet
2011-05-19 11:26 ` Denys Fedoryshchenko
2011-05-19 20:19 ` David Miller
2011-05-19 7:51 ` 2.6.39-rc7-git11, x86/32, failed on ppp2897'th interface, PERCPU: allocation failed David Miller
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=1305787158.3019.12.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=denys@visp.net.lb \
--cc=netdev@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