Your message dated Mon, 13 Dec 2010 01:22:19 +0000 with message-id <1292203339.3136.414.camel@localhost> and subject line Re: Bug#533180: linux-image-amd64: page allocation failure has caused the Debian Bug report #533180, regarding linux-image-amd64: page allocation failure within kernel swapper to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 533180: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=533180 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: linux-image-amd64: page allocation failure within kernel swapper
- From: Giorgos Mavrikas <gmavrikas@yahoo.com>
- Date: Mon, 15 Jun 2009 15:51:45 +0300
- Message-id: <20090615125145.5574.78681.reportbug@tube.fep.upatras.gr>
Package: linux-image-amd64 Version: 2.6.26-2 Severity: normal I run a standard amd64 kernel in a core 2 duo machine under heavy network traffic, and I keep getting tons of these (more than 28 in less that 2 days) the last few weeks, regardless of all reboots: [186974.720505] swapper: page allocation failure. order:0, mode:0x20 [186974.720543] Pid: 0, comm: swapper Not tainted 2.6.26-2-amd64 #1 [186974.720577] [186974.720578] Call Trace: [186974.720626] <IRQ> [<ffffffff80276b64>] __alloc_pages_internal+0x3a6/0x3bf [186974.720683] [<ffffffff802954bc>] kmem_getpages+0x96/0x164 [186974.720719] [<ffffffff80295b1c>] fallback_alloc+0x16b/0x1e1 [186974.720758] [<ffffffff8029572e>] kmem_cache_alloc_node+0x105/0x138 [186974.720797] [<ffffffff803b5a2f>] __alloc_skb+0x3c/0x12d [186974.720834] [<ffffffff803f0497>] tcp_delack_timer+0x0/0x1eb [186974.720869] [<ffffffff803eda19>] tcp_send_ack+0x28/0xca [186974.720905] [<ffffffff803f061a>] tcp_delack_timer+0x183/0x1eb [186974.720940] [<ffffffff803f0497>] tcp_delack_timer+0x0/0x1eb [186974.720977] [<ffffffff8023ca35>] run_timer_softirq+0x16a/0x1e2 [186974.721015] [<ffffffff802393fb>] __do_softirq+0x5c/0xd1 [186974.721052] [<ffffffff8020d2cc>] call_softirq+0x1c/0x28 [186974.721087] [<ffffffff8020f3d0>] do_softirq+0x3c/0x81 [186974.721121] [<ffffffff8023935b>] irq_exit+0x3f/0x83 [186974.721154] [<ffffffff8020f630>] do_IRQ+0xb9/0xd9 [186974.721188] [<ffffffff80212c37>] mwait_idle+0x0/0x4d [186974.721222] [<ffffffff8020c46d>] ret_from_intr+0x0/0x19 [186974.721255] <EOI> [<ffffffff80212c78>] mwait_idle+0x41/0x4d [186974.721298] [<ffffffff8020ac79>] cpu_idle+0x89/0xb3 [186974.721337] [186974.721360] Mem-info: [186974.721385] Node 0 DMA per-cpu: [186974.721415] CPU 0: hi: 0, btch: 1 usd: 0 [186974.721448] CPU 1: hi: 0, btch: 1 usd: 0 [186974.721480] Node 0 DMA32 per-cpu: [186974.721510] CPU 0: hi: 186, btch: 31 usd: 85 [186974.725684] CPU 1: hi: 186, btch: 31 usd: 163 [186974.725715] Node 0 Normal per-cpu: [186974.725745] CPU 0: hi: 186, btch: 31 usd: 156 [186974.725777] CPU 1: hi: 186, btch: 31 usd: 176 [186974.725811] Active:432816 inactive:512117 dirty:47642 writeback:1354 unstable:0 [186974.725812] free:4360 slab:37261 mapped:147385 pagetables:2094 bounce:0 [186974.725903] Node 0 DMA free:11712kB min:20kB low:24kB high:28kB active:0kB inactive:0kB present:10784kB pages_scanned:0 all_unreclaimable? yes [186974.725975] lowmem_reserve[]: 0 3254 3948 3948 [186974.726012] Node 0 DMA32 free:5220kB min:6616kB low:8268kB high:9924kB active:1405280kB inactive:1720956kB present:3332192kB pages_scanned:0 all_unreclaimable? no [186974.726107] lowmem_reserve[]: 0 0 694 694 [186974.726142] Node 0 Normal free:508kB min:1412kB low:1764kB high:2116kB active:325984kB inactive:327512kB present:711040kB [186974.726236] lowmem_reserve[]: 0 0 0 0 [186974.726271] Node 0 DMA: 6*4kB 1*8kB 6*16kB 6*32kB 4*64kB 1*128kB 1*256kB 1*512kB 2*1024kB 0*2048kB 2*4096kB = 11712kB [186974.726352] Node 0 DMA32: 1*4kB 1*8kB 1*16kB 0*32kB 1*64kB 0*128kB 0*256kB 0*512kB 1*1024kB 0*2048kB 1*4096kB = 5212kB [186974.726433] Node 0 Normal: 31*4kB 1*8kB 1*16kB 1*32kB 0*64kB 1*128kB 1*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 564kB [186974.726514] 895787 total pagecache pages [186974.726544] Swap cache: add 52586, delete 47804, find 34432/40126 [186974.726580] Free swap = 1900728kB [186974.726608] Total swap = 1959800kB [186974.728623] 1032192 pages of RAM [186974.728623] 33128 reserved pages [186974.728623] 964284 pages shared [186974.728623] 4782 pages swap cached -- System Information: Debian Release: 5.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
- To: Eduardo Silvestre <eduardo.silvestre@nfsi.pt>, Giorgos Mavrikas <gmavrikas@yahoo.com>
- Cc: 533180-done@bugs.debian.org
- Subject: Re: Bug#533180: linux-image-amd64: page allocation failure
- From: Ben Hutchings <ben@decadent.org.uk>
- Date: Mon, 13 Dec 2010 01:22:19 +0000
- Message-id: <1292203339.3136.414.camel@localhost>
- In-reply-to: <[🔎] 1766331962.4434.1292201962227.JavaMail.root@zimbra.nfsi.pt>
- References: <[🔎] 1766331962.4434.1292201962227.JavaMail.root@zimbra.nfsi.pt>
On Mon, 2010-12-13 at 00:59 +0000, Eduardo Silvestre wrote: > Hello, > > i'm facing the same problem with last debian kernel. This machine > have a huge network traffic. [...] > Any idea how can i fix this? This is simply the result of running low on memory, and almost certainly *not* a bug. So the way to fix it is to install more RAM, or to stop or limit some memory-hungry programs. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.Attachment: signature.asc
Description: This is a digitally signed message part
--- End Message ---