All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Becker <becker@cs.duke.edu>
To: xen-devel@lists.sourceforge.net
Subject: network_alloc_rx_buffers panic
Date: Thu, 23 Sep 2004 09:08:07 -0400	[thread overview]
Message-ID: <20040923130807.GE921@cs.duke.edu> (raw)


Some users are hitting this panic in network_alloc_rx_buffers()
when running a big network intensive app:
    /* Check return status of HYPERVISOR_dom_mem_op(). */
   if ( rx_mcl[nr_pfns].args[5] != nr_pfns )
	        panic("Unable to reduce memory reservation\n");

I'm not clear on what is happening here.   Are the domains changing size?
Which memory reservation is being reduced, xen0 or xenU?
All the domains are v2.6.8.1, changeset 1.1331 from  Tuesday.

David


-------------------------------------------------------
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-23 13:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-23 13:08 David Becker [this message]
2004-09-23 13:47 ` network_alloc_rx_buffers panic 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
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=20040923130807.GE921@cs.duke.edu \
    --to=becker@cs.duke.edu \
    --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.