From: "Jan Kundrát" <jan.kundrat@fzu.cz>
To: xen-devel <xen-devel@lists.sourceforge.net>
Subject: network dropouts
Date: Sun, 12 Dec 2004 21:34:54 +0100 [thread overview]
Message-ID: <41BCAB6E.8090608@fzu.cz> (raw)
Hi,
I had two ssh connection idle for some time, and suddenly the connection
"broke", no responses from ping. Using 3c59x NIC.
Kernel log:
after calling `wm destroy ttylinux`:
Dec 12 20:30:52 zirafa device vif3.0 left promiscuous mode
Dec 12 20:30:52 zirafa xen-br0: port 2(vif3.0) entering disabled state
Dec 12 20:30:52 zirafa xen-br0: port 2(vif3.0) entering disabled state
Dec 12 20:33:23 zirafa xen-br0: port 1(eth0) entering disabled state
Dec 12 20:34:23 zirafa xen-br0: port 1(eth0) entering learning state
Dec 12 20:34:23 zirafa xen-br0: topology change detected, propagating
Dec 12 20:34:23 zirafa xen-br0: port 1(eth0) entering forwarding state
...machine worked ok, I can see messages from cron in syslog...
maybe this is the time I tried to press some key in ssh connection to
domain0, +/- 1 minute or so:
Dec 12 21:12:23 zirafa xen-br0: port 1(eth0) entering disabled state
Dec 12 21:13:23 zirafa xen-br0: port 1(eth0) entering learning state
Dec 12 21:13:23 zirafa xen-br0: topology change detected, propagating
Dec 12 21:13:23 zirafa xen-br0: port 1(eth0) entering forwarding state
(login from serial console to see what happens)
Dec 12 21:13:31 zirafa login(pam_unix)[7594]: session opened for user
root by (uid=0)
(network connectivity restored)
I have no idea why is there 1 minute delay, according to syslog. Network
cable was *not* unplugged.
BTW, this is what happens when I unplug cable from eth0 (unplugged at
21:27:50, re-plugged at 21:28:33):
Dec 12 21:28:23 zirafa xen-br0: port 1(eth0) entering disabled state
Dec 12 21:29:23 zirafa xen-br0: port 1(eth0) entering learning state
Dec 12 21:29:23 zirafa xen-br0: topology change detected, propagating
Dec 12 21:29:23 zirafa xen-br0: port 1(eth0) entering forwarding state
Is it normal?
j.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next reply other threads:[~2004-12-12 20:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-12 20:34 Jan Kundrát [this message]
2004-12-13 20:08 ` network dropouts Jan Kundrát
2004-12-14 11:04 ` Ian Pratt
2004-12-14 11:27 ` Jan Kundrát
2004-12-14 11:36 ` Keir Fraser
2004-12-17 18:37 ` Jan Kundrát
2004-12-17 20:06 ` Keir Fraser
2004-12-17 20:25 ` Jan Kundrát
2004-12-17 20:54 ` Keir Fraser
2004-12-17 21:03 ` Jan Kundrát
2004-12-17 21:18 ` Jan Kundrát
2004-12-17 20:36 ` Jan Kundrát
2004-12-15 14:58 ` Jan Kundrát
2004-12-14 16:43 ` Nivedita Singhvi
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=41BCAB6E.8090608@fzu.cz \
--to=jan.kundrat@fzu.cz \
--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.