WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 		  
Home Products Support Community News
 
   
 

xen-bugs

[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

[Xen-bugs] [Bug 675] page allocation failures

from [bugzilla-daemon] [Permanent Link][Original]
To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 675] page allocation failures
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Mon, 4 Feb 2008 18:53:04 -0800
Delivery-date: Mon, 04 Feb 2008 18:53:14 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <bug-675-3@xxxxxxxxxxxxxxxxxxxxxxxxxxx/bugzilla/>
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx 
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=675


andy@xxxxxxxxxxxxxx changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |andy@xxxxxxxxxxxxxx
             Status|RESOLVED                    |REOPENED
         Resolution|WONTFIX                     |




------- Comment #2 from andy@xxxxxxxxxxxxxx  2008-02-04 18:53 -------
(In reply to comment #1)
> I'm closing this bug in the course of bugzilla 2007 spring cleaning.
> No patch has been attached, and no developer has dealt with it since months,
> so I'm closing it as "wontfix" which matches this fact best.
> Please reopen this bug if it still exists in current Xen versions, and is
> important to you - sorry for the inconvenience in that case.

I am still seeing this using Debian Etch stock xen kernel and hypervisor:

Feb  5 00:04:22 corona kernel: swapper: page allocation failure. order:0,
mode:0x20
Feb  5 00:04:22 corona kernel:  [<c0140759>] __alloc_pages+0x261/0x275
Feb  5 00:04:22 corona kernel:  [<c015622a>] cache_alloc_refill+0x297/0x493
Feb  5 00:04:22 corona kernel:  [<c0104a51>] hypervisor_callback+0x3d/0x48
Feb  5 00:04:22 corona kernel:  [<c020007b>] put_queue+0x7a/0x8b
Feb  5 00:04:22 corona kernel:  [<c0155f7a>] kmem_cache_alloc+0x3b/0x54
Feb  5 00:04:22 corona kernel:  [<c022eb45>] alloc_skb_from_cache+0x48/0x110
Feb  5 00:04:22 corona kernel:  [<c020d8b4>] __alloc_skb+0x6c/0x70
Feb  5 00:04:22 corona kernel:  [<c0215f07>] netif_be_start_xmit+0x118/0x3d5
Feb  5 00:04:22 corona kernel:  [<c023284e>] dev_hard_start_xmit+0x19a/0x1f0
Feb  5 00:04:22 corona kernel:  [<c02341d0>] dev_queue_xmit+0x247/0x2e3
Feb  5 00:04:22 corona kernel:  [<ee415dfe>] br_dev_queue_push_xmit+0x155/0x178
[bridge]
Feb  5 00:04:22 corona kernel:  [<ee415e64>] br_forward_finish+0x43/0x45
[bridge]
Feb  5 00:04:22 corona kernel:  [<ee419ae4>] br_nf_forward_finish+0xc6/0xcc
[bridge]
Feb  5 00:04:22 corona kernel:  [<ee41a34a>] br_nf_forward_arp+0x116/0x128
[bridge]
Feb  5 00:04:22 corona kernel:  [<c0246fd8>] nf_iterate+0x30/0x61
Feb  5 00:04:22 corona kernel:  [<ee415e21>] br_forward_finish+0x0/0x45
[bridge]
Feb  5 00:04:22 corona kernel:  [<c02470fe>] nf_hook_slow+0x3a/0x90
Feb  5 00:04:22 corona kernel:  [<ee415e21>] br_forward_finish+0x0/0x45
[bridge]
Feb  5 00:04:22 corona kernel:  [<ee415eac>] __br_forward+0x46/0x57 [bridge]
Feb  5 00:04:22 corona kernel:  [<ee415e21>] br_forward_finish+0x0/0x45
[bridge]
Feb  5 00:04:22 corona kernel:  [<ee415c59>] br_flood+0x65/0x9d [bridge]
Feb  5 00:04:22 corona kernel:  [<ee415e66>] __br_forward+0x0/0x57 [bridge]
Feb  5 00:04:22 corona kernel:  [<ee415c9b>] br_flood_forward+0xa/0xc [bridge]
Feb  5 00:04:22 corona kernel:  [<ee415e66>] __br_forward+0x0/0x57 [bridge]
Feb  5 00:04:22 corona kernel:  [<ee416868>] br_handle_frame_finish+0x80/0xcf
[bridge]
Feb  5 00:04:22 corona kernel:  [<ee416a16>] br_handle_frame+0x15f/0x179
[bridge]
Feb  5 00:04:22 corona kernel:  [<c02323e1>] netif_receive_skb+0x25e/0x357
Feb  5 00:04:22 corona kernel:  [<ee04b130>] e1000_clean_rx_irq_ps+0x4a6/0x569
[e1000]
Feb  5 00:04:22 corona kernel:  [<ee049c4c>] e1000_clean+0x69/0x136 [e1000]
Feb  5 00:04:22 corona kernel:  [<c0233e90>] net_rx_action+0x96/0x18f
Feb  5 00:04:22 corona kernel:  [<c011f41e>] __do_softirq+0x5e/0xc3
Feb  5 00:04:22 corona kernel:  [<c011f4bd>] do_softirq+0x3a/0x4a
Feb  5 00:04:22 corona kernel:  [<c0106131>] do_IRQ+0x48/0x53
Feb  5 00:04:22 corona kernel:  [<c020c378>] evtchn_do_upcall+0x64/0x9b
Feb  5 00:04:22 corona kernel:  [<c0104a51>] hypervisor_callback+0x3d/0x48
Feb  5 00:04:22 corona kernel:  [<c0107342>] raw_safe_halt+0x8c/0xaf
Feb  5 00:04:22 corona kernel:  [<c0102c5f>] xen_idle+0x22/0x2e
Feb  5 00:04:22 corona kernel:  [<c0102d7e>] cpu_idle+0x91/0xab
Feb  5 00:04:22 corona kernel:  [<c03256fc>] start_kernel+0x378/0x37f
Feb  5 00:04:22 corona kernel: Mem-info:
Feb  5 00:04:22 corona kernel: DMA per-cpu:
Feb  5 00:04:22 corona kernel: cpu 0 hot: high 186, batch 31 used:30
Feb  5 00:04:22 corona kernel: cpu 0 cold: high 62, batch 15 used:51
Feb  5 00:04:22 corona kernel: DMA32 per-cpu: empty
Feb  5 00:04:22 corona kernel: Normal per-cpu: empty
Feb  5 00:04:22 corona kernel: HighMem per-cpu:
Feb  5 00:04:22 corona kernel: cpu 0 hot: high 90, batch 15 used:77
Feb  5 00:04:22 corona kernel: cpu 0 cold: high 30, batch 7 used:0
Feb  5 00:04:22 corona kernel: Free pages:       45644kB (44448kB HighMem)
Feb  5 00:04:22 corona kernel: Active:147427 inactive:28380 dirty:31
writeback:0 unstable:0 free:11411 slab:27096 mapped:3000 pagetables:241
Feb  5 00:04:22 corona kernel: DMA free:1196kB min:3452kB low:4312kB
high:5176kB active:474076kB inactive:72956kB present:745464kB
pages_scanned:84 all_unreclaimable? no
Feb  5 00:04:22 corona kernel: lowmem_reserve[]: 0 0 0 204
Feb  5 00:04:22 corona kernel: DMA32 free:0kB min:0kB low:0kB high:0kB
active:0kB inactive:0kB present:0kB pages_scanned:0
all_unreclaimable? no
Feb  5 00:04:22 corona kernel: lowmem_reserve[]: 0 0 0 204
Feb  5 00:04:22 corona kernel: Normal free:0kB min:0kB low:0kB high:0kB
active:0kB inactive:0kB present:0kB pages_scanned:0
all_unreclaimable? no
Feb  5 00:04:22 corona kernel: lowmem_reserve[]: 0 0 0 1632
Feb  5 00:04:22 corona kernel: HighMem free:44448kB min:204kB low:444kB
high:684kB active:115632kB inactive:40564kB present:208904kB
pages_scanned:0 all_unreclaimable? no
Feb  5 00:04:22 corona kernel: lowmem_reserve[]: 0 0 0 0
Feb  5 00:04:22 corona kernel: DMA: 1*4kB 1*8kB 0*16kB 1*32kB 0*64kB 1*128kB
0*256kB 0*512kB 1*1024kB 0*2048kB 0*4096kB = 1196kB
Feb  5 00:04:22 corona kernel: DMA32: empty
Feb  5 00:04:22 corona kernel: Normal: empty
Feb  5 00:04:22 corona kernel: HighMem: 1230*4kB 1919*8kB 249*16kB 91*32kB
168*64kB 19*128kB 16*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB =
44448kB
Feb  5 00:04:22 corona kernel: Swap cache: add 29, delete 29, find 0/0, race
0+0
Feb  5 00:04:22 corona kernel: Free swap  = 1975556kB
Feb  5 00:04:22 corona kernel: Total swap = 1975672kB
Feb  5 00:04:22 corona kernel: Free swap:       1975556kB
Feb  5 00:04:22 corona kernel: 238592 pages of RAM
Feb  5 00:04:22 corona kernel: 52226 pages of HIGHMEM
Feb  5 00:04:22 corona kernel: 19814 reserved pages
Feb  5 00:04:22 corona kernel: 159360 pages shared
Feb  5 00:04:22 corona kernel: 0 pages swap cached
Feb  5 00:04:22 corona kernel: 31 pages dirty
Feb  5 00:04:22 corona kernel: 0 pages writeback
Feb  5 00:04:22 corona kernel: 3000 pages mapped
Feb  5 00:04:22 corona kernel: 27096 pages slab
Feb  5 00:04:22 corona kernel: 241 pages pagetables

It stalls the networking for a minute or so while it is happening but then
everything seems to recover.  This may happen 6 times a day, or once or twice
in 6 months.

Cheers,
Andy


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] [Bug 675] page allocation failures, bugzilla-daemon <=
Previous by Date:  [Xen-bugs] [Bug 1164] New: Dom0 "BUG: soft lockup detected on CPU#0!", (ntpd?), bugzilla-daemon
Next by Date:  [Xen-bugs] [Bug 1164] Dom0 "BUG: soft lockup detected on CPU#0!", (ntpd?), bugzilla-daemon
Previous by Thread:  [Xen-bugs] [Bug 1164] New: Dom0 "BUG: soft lockup detected on CPU#0!", (ntpd?), bugzilla-daemon
Next by Thread:  [Xen-bugs] [Bug 1165] New: bnx2 driver needs to be updated to work with Xen, bugzilla-daemon
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

Copyright , Citrix Systems Inc. All rights reserved. Legal and Privacy