All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Birger Tödtmann" <btoedtmann@iem.uni-due.de>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Subject: Re: kernel oops/IRQ exception when networking between many domUs
Date: Mon, 06 Jun 2005 14:30:10 +0200	[thread overview]
Message-ID: <1118061010.7357.10.camel@lomin> (raw)
In-Reply-To: <ed4c4684b80b36948ce5e4dd7ac938b6@cl.cam.ac.uk>

Am Montag, den 06.06.2005, 10:26 +0100 schrieb Keir Fraser:
[...]
> > somewhere around the magic 128 (NR_IRQS problem in 2.0.x!) when the
> > crash happens - could this hint to something?
> 
> The crashes you see with free_mfn removed will be impossible to debug 
> -- things are very screwed by that point. Even the crash within 
> free_mfn might be far removed from the cause of the crash, if it's due 
> to memory corruption.
> 
> It's perhaps worth investigating what critical limit you might be 
> hitting, and what resource it is that's limited. e.g., can you can 
> create a few vifs, but connected together by some very large number of 
> bridges (daisy chained together)? Or can you create a large number of 
> vifs if they are connected together by just one bridge?

This is getting really weird - as I found out I'll enounter problems
with far fewer vifs/bridges that suspected.  I just fired up a network
with 7 nodes, all with four interfaces each connected to the same four
bridge interfaces.  The nodes can ping through the network, however
after a short time, the system (dom0) crashes as well.  This time, it
dies in net_rx_action() at a slightly different place:

[...]
 [<c02b6e15>] kfree_skbmem+0x12/0x29
 [<c02b6ed1>] __kfree_skb+0xa5/0x13f
 [<c028c9b3>] net_rx_action+0x23d/0x4df
[...]

Funnily, I cannot reproduce this with 5 nodes (domUs) running.  I'm a
bit unsure where to go from here...  Maybe I should try a different
machine for further testing.


Regards
-- 
Birger Tödtmann
Technik der Rechnernetze, Institut für Experimentelle Mathematik
Universität Duisburg-Essen, Campus Essen email:btoedtmann@iem.uni-due.de
skype:birger.toedtmann pgp:0x6FB166C9

  reply	other threads:[~2005-06-06 12:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1117904746.7507.31.camel@lomin>
     [not found] ` <b60a57e1c8d95c01eb0c5b383b9b8e18@cl.cam.ac.uk>
2005-06-06  6:42   ` kernel oops/IRQ exception when networking between many domUs Birger Toedtmann
     [not found]   ` <20050605165716.GA1231@exp-math.uni-essen.de>
2005-06-06  8:23     ` [Xen-devel] " Keir Fraser
2005-06-06  8:52       ` Birger Tödtmann
2005-06-06  8:56         ` [Xen-devel] " Birger Tödtmann
2005-06-06  9:26         ` Keir Fraser
2005-06-06 12:30           ` Birger Tödtmann [this message]
2005-06-07 16:46             ` Nils Toedtmann
2005-06-07 16:47             ` Nils Toedtmann
2005-06-08 12:34               ` Nils Toedtmann
2005-06-08 14:40                 ` Nils Toedtmann

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=1118061010.7357.10.camel@lomin \
    --to=btoedtmann@iem.uni-due.de \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-users@lists.xensource.com \
    /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.