All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Becker <becker@cs.duke.edu>
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
Cc: Christian Limpach <Christian.Limpach@cl.cam.ac.uk>,
	Keir Fraser <Keir.Fraser@cl.cam.ac.uk>,
	xen-devel@lists.sourceforge.net
Subject: Re: network_alloc_rx_buffers panic
Date: Sun, 26 Sep 2004 08:20:09 -0400	[thread overview]
Message-ID: <20040926122009.GF20890@cs.duke.edu> (raw)
In-Reply-To: <E1CBV8A-00080x-00@mta1.cl.cam.ac.uk>


" > " Could you try updating to the latest version, with writable pagetables
" > " reenabled.  Keir has spotted an incorrect check in the writable
" > 
" > xen is faulting the same as the previous pull.

I am now seeing a new behaviour from xen0.  Some of them drop off the
net for a minute or so and come back apparently ok, except for lots of
console messages from swapper, shown below.   I suppose it could be the
bug that has been panicking xenU didn't manage a panic but did corrupt
the system..

This network delay effect is on some (but not all) of the xen0 e100 hosts.
(The xenU panic I reported before has happened on all types of hosts.)
Additionally the clocks are off on the xen0 hosts that show this symptom.
They xen0 domains are all running ntp, so I'd guess this symptom is
messing up ntp.

xen0 is configured with the same amount of mem on all hosts.

xen0 has plenty of swap space:
$ swapon -s
Filename                             Type            Size    Used Priority
/dev/sda2                               partition    987988  9316 -1


xen0 dmesg:

swapper: page allocation failure. order:0, mode:0x20
 [<c0138448>] __alloc_pages+0x2d7/0x347

 [<c01384d7>] __get_free_pages+0x1f/0x3b

 [<c013b9e6>] kmem_getpages+0x22/0xdc

 [<c013c632>] cache_grow+0xb9/0x189

 [<c013c86b>] cache_alloc_refill+0x169/0x20a

 [<c013cb0f>] kmem_cache_alloc+0x6c/0x70

 [<c031e0da>] alloc_skb_from_cache+0x44/0xdc

 [<c010a557>] __dev_alloc_skb+0x23/0x39

 [<c023e42a>] e100_intr+0x1b0/0x60b

 [<c031e170>] alloc_skb_from_cache+0xda/0xdc

 [<c010bc5a>] handle_IRQ_event+0x47/0x80

 [<c010bfc2>] do_IRQ+0x93/0x132

 [<c01092d0>] evtchn_do_upcall+0xa8/0x111

 [<c010d93b>] hypervisor_callback+0x33/0x49

 [<c0109226>] force_evtchn_callback+0xa/0xc

 [<c0118d2a>] try_to_wake_up+0xab/0xbd

 [<c01248d4>] process_timeout+0x0/0x9

 [<c0118d5a>] wake_up_process+0x1e/0x22

 [<c0124613>] run_timer_softirq+0xe3/0x1e6

 [<c012066b>] __do_softirq+0x93/0x9c

 [<c01206b9>] do_softirq+0x45/0x47

 [<c010c02f>] do_IRQ+0x100/0x132

 [<c01092d0>] evtchn_do_upcall+0xa8/0x111

 [<c010d93b>] hypervisor_callback+0x33/0x49

 [<c0109bcc>] xen_cpu_idle+0x0/0x8c

 [<c0109bcc>] xen_cpu_idle+0x0/0x8c

 [<c010eebc>] cpu_idle+0x2a/0x35

 [<c046269d>] start_kernel+0x1a0/0x1e9

 [<c04622bc>] unknown_bootoption+0x0/0x149



-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php

  reply	other threads:[~2004-09-26 12:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-23 13:08 network_alloc_rx_buffers panic David Becker
2004-09-23 13:47 ` Keir Fraser
2004-09-23 20:41   ` David Becker
2004-09-23 20:47     ` Christian Limpach
2004-09-23 21:03       ` David Becker
2004-09-23 22:07     ` Ian Pratt
2004-09-23 22:21       ` Ian Pratt
2004-09-24 13:28       ` David Becker
2004-09-24 15:05         ` Christian Limpach
2004-09-26  1:45           ` David Becker
2004-09-26  9:15             ` Ian Pratt
2004-09-26 12:20               ` David Becker [this message]
2004-09-26 16:07                 ` Keir Fraser
2004-09-28 10:05             ` Christian Limpach
2004-09-28 10:23               ` Keir Fraser
2004-09-28 11:29                 ` David Becker
2004-09-23 14:03 ` Mark A. Williamson

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=20040926122009.GF20890@cs.duke.edu \
    --to=becker@cs.duke.edu \
    --cc=Christian.Limpach@cl.cam.ac.uk \
    --cc=Ian.Pratt@cl.cam.ac.uk \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=xen-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.