All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Knorr <kraxel@suse.de>
To: Ewan Mellor <ewan@xensource.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: unstable network trouble
Date: Mon, 31 Oct 2005 11:58:10 +0100	[thread overview]
Message-ID: <4365F8C2.4040809@suse.de> (raw)
In-Reply-To: <4360F5AA.20207@suse.de>

> Hmm, no, seems to be a missing hotplug event.

Sticked some printk's into the net backend, looks like a xenbus issue:

domU boot with broken network:

   netback_probe: add backend watch
   netback_probe: add frontend watch
   netback_probe: done
   frontend_changed: called
   frontend_changed: called
   frontend_changed: called
   frontend_changed: called

domU boot with working network:

   netback_probe: add backend watch
   netback_probe: add frontend watch
   netback_probe: done
   backend_changed: called
   backend_changed: hotplug online
   netback_hotplug: called
   frontend_changed: called
   frontend_changed: called
   device vif2.0 entered promiscuous mode
   xenbr0: port 3(vif2.0) entering learning state
   xenbr0: topology change detected, propagating
   xenbr0: port 3(vif2.0) entering forwarding state
   frontend_changed: called
   frontend_changed: called
   frontend_changed: called

Note that backend_changed is never called in the first case.

cheers,

   Gerd

      parent reply	other threads:[~2005-10-31 10:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-27 13:57 unstable network trouble Gerd Knorr
2005-10-27 15:12 ` Ewan Mellor
2005-10-27 15:43   ` Gerd Knorr
2005-10-27 15:57     ` Ewan Mellor
2005-10-28  9:06       ` Gerd Knorr
2005-10-28  9:59         ` Gerd Knorr
2005-10-28 11:11           ` Ewan Mellor
2005-10-28 10:03         ` Gerd Knorr
2005-10-31 10:58     ` Gerd Knorr [this message]

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=4365F8C2.4040809@suse.de \
    --to=kraxel@suse.de \
    --cc=ewan@xensource.com \
    --cc=xen-devel@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.