突然出来的错误log：kernel: nginx: page allocation failure. order:2, mode:0x20

chuantong.huang · 2014-03-26T20:09:41+00:00

Hello! 2014-03-26 2:58 GMT-07:00 coderesty: > 另外我想问一下, lua_check_client_abort on;时候&#x5982...

突然出来的错误log：kernel: nginx: page allocation failure. order:2, mode:0x20

chuantong.huang

今天出现的log，求解释。

pid 对应的进程31714还在。

此ngx只作https反向代理，并不是openresty。

版本如下:

/usr/local/nginx/sbin/nginx -V

nginx version: nginx/1.4.4

built by gcc 4.4.7 20120313 (Red Hat 4.4.7-4) (GCC)

TLS SNI support enabled

configure arguments: --with-http_stub_status_module --without-mail_pop3_module --without-mail_imap_module --without-mail_smtp_module --with-http_realip_module --with-http_secure_link_module --with-http_gzip_static_module --with-http_ssl_module --prefix=/usr/local/nginx --user=nginx --group=www

cat /var/log/message

Mar 26 17:41:17 localhost kernel: nginx: page allocation failure. order:2, mode:0x20

Mar 26 17:41:17 localhost kernel: Pid: 31714, comm: nginx Tainted: G W ---------------- 2.6.32-220.el6.x86_64 #1

Mar 26 17:41:17 localhost kernel: Call Trace:

Mar 26 17:41:17 localhost kernel: [<ffffffff81123f0f>] ? __alloc_pages_nodemask+0x77f/0x940

Mar 26 17:41:17 localhost kernel: [<ffffffffa0226b00>] ? tcp_packet+0x5d0/0x15f0 [nf_conntrack]

Mar 26 17:41:17 localhost kernel: [<ffffffff8115ddc2>] ? kmem_getpages+0x62/0x170

Mar 26 17:41:17 localhost kernel: [<ffffffff8115e9da>] ? fallback_alloc+0x1ba/0x270

Mar 26 17:41:17 localhost kernel: [<ffffffff8115e42f>] ? cache_grow+0x2cf/0x320

Mar 26 17:41:17 localhost kernel: [<ffffffff8115e759>] ? ____cache_alloc_node+0x99/0x160

Mar 26 17:41:17 localhost kernel: [<ffffffff814218ba>] ? __alloc_skb+0x7a/0x180

Mar 26 17:41:17 localhost kernel: [<ffffffff8115f61f>] ? kmem_cache_alloc_node_notrace+0x6f/0x130

Mar 26 17:41:17 localhost kernel: [<ffffffff8115f85b>] ? __kmalloc_node+0x7b/0x100

Mar 26 17:41:17 localhost kernel: [<ffffffff814218ba>] ? __alloc_skb+0x7a/0x180

Mar 26 17:41:17 localhost kernel: [<ffffffff814229c6>] ? skb_copy+0x36/0xa0

Mar 26 17:41:17 localhost kernel: [<ffffffffa0100d24>] ? tg3_start_xmit+0xcd4/0x1030 [tg3]

Mar 26 17:41:17 localhost kernel: [<ffffffff8142c7bc>] ? dev_hard_start_xmit+0x2bc/0x3f0

Mar 26 17:41:17 localhost kernel: [<ffffffff81449b6a>] ? sch_direct_xmit+0x15a/0x1c0

Mar 26 17:41:17 localhost kernel: [<ffffffff81430eb8>] ? dev_queue_xmit+0x4b8/0x6b0

Mar 26 17:41:17 localhost kernel: [<ffffffff814576b4>] ? nf_hook_slow+0x74/0x110

Mar 26 17:41:17 localhost kernel: [<ffffffff81467ea0>] ? ip_finish_output+0x0/0x310

Mar 26 17:41:17 localhost kernel: [<ffffffff81467fdc>] ? ip_finish_output+0x13c/0x310

Mar 26 17:41:17 localhost kernel: [<ffffffff81468268>] ? ip_output+0xb8/0xc0

Mar 26 17:41:17 localhost kernel: [<ffffffff8146752f>] ? __ip_local_out+0x9f/0xb0

Mar 26 17:41:17 localhost kernel: [<ffffffff81467565>] ? ip_local_out+0x25/0x30

Mar 26 17:41:17 localhost kernel: [<ffffffff81467a40>] ? ip_queue_xmit+0x190/0x420

Mar 26 17:41:17 localhost kernel: [<ffffffff8115f85b>] ? __kmalloc_node+0x7b/0x100

Mar 26 17:41:17 localhost kernel: [<ffffffff8147c77e>] ? tcp_transmit_skb+0x3fe/0x7b0

Mar 26 17:41:17 localhost kernel: [<ffffffff8147eb17>] ? tcp_write_xmit+0x1e7/0x9e0

Mar 26 17:41:17 localhost kernel: [<ffffffff8147f4a0>] ? __tcp_push_pending_frames+0x30/0xe0

Mar 26 17:41:17 localhost kernel: [<ffffffff8146eabe>] ? tcp_push+0x6e/0x90

Mar 26 17:41:17 localhost kernel: [<ffffffff8146faaa>] ? tcp_sendmsg+0x64a/0xa10

Mar 26 17:41:17 localhost kernel: [<ffffffff8141bd9e>] ? sock_aio_write+0x15e/0x170

Mar 26 17:41:17 localhost kernel: [<ffffffff811762da>] ? do_sync_write+0xfa/0x140

Mar 26 17:41:17 localhost kernel: [<ffffffff81090bf0>] ? autoremove_wake_function+0x0/0x40

Mar 26 17:41:17 localhost kernel: [<ffffffff8120c3b6>] ? security_file_permission+0x16/0x20

Mar 26 17:41:17 localhost kernel: [<ffffffff811766a4>] ? vfs_write+0x184/0x1a0

Mar 26 17:41:17 localhost kernel: [<ffffffff810d46e2>] ? audit_syscall_entry+0x272/0x2a0

Mar 26 17:41:17 localhost kernel: [<ffffffff81176fe1>] ? sys_write+0x51/0x90

Mar 26 17:41:17 localhost kernel: [<ffffffff8100b0f2>] ? system_call_fastpath+0x16/0x1b

agentzh

Hello!

On Wed, Mar 26, 2014 at 5:09 AM, Huang ChuanTong wrote:
> 今天出现的log，求解释。
> pid 对应的进程31714还在。
> Mar 26 17:41:17 localhost kernel: nginx: page allocation failure. order:2,
> mode:0x20
> Mar 26 17:41:17 localhost kernel: Pid: 31714, comm: nginx Tainted: G
> W  ----------------   2.6.32-220.el6.x86_64 #1
> Mar 26 17:41:17 localhost kernel: Call Trace:
> Mar 26 17:41:17 localhost kernel: [<ffffffff81123f0f>] ?
> __alloc_pages_nodemask+0x77f/0x940

这个明显是 Linux 内核的调用栈，即你的 Linux 内核出现了崩溃，特别地，是在 TCP
协议栈发送数据时因为内存页分配失败而导致的崩溃，和用户态程序没什么关系。你应该找你的内核的维护者求解释。

Regards,
-agentzh