From: Stephen Hemminger <shemminger@osdl.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: bridge@lists.osdl.org
Subject: Re: [Bridge] Re: Problem in changed VLAN code can cause systems to hang.
Date: Fri, 10 Sep 2004 04:56:03 -0700 [thread overview]
Message-ID: <20040910045603.32e8ded3@linux.site> (raw)
In-Reply-To: <20040909085149.1d483349.davem@davemloft.net>
I can't reproduce the problem on a test machine (SMP) with eth0 (e100) and eth2 (e1000)
Doesn't seem to hang either with commands or custom program.
[root@dev4-009 root]# vconfig add eth2 1
Added VLAN with VID == 1 to IF -:eth2:-
WARNING: VLAN 1 does not work with many switches,
consider another number if you have problems.
[root@dev4-009 root]# ifconfig eth2:1
eth2:1 Link encap:Ethernet HWaddr 00:03:47:9A:33:D5
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Memory:fa420000-fa440000
[root@dev4-009 root]# mii-tool eth2:1
SIOCGMIIPHY on 'eth2:1' failed: Operation not supported
This is what we would expect since e1000 doesn't support MII ioctl when
running in 1000Gbit mode.
[root@dev4-009 root]# vconfig add eth0 11
Added VLAN with VID == 11 to IF -:eth0:-
[root@dev4-009 root]# mii-tool eth0:11
eth0:11: negotiated 100baseTx-FD, link ok
The e100 link works, and also eth1 (e1000 in 100mbit mode).
If someone can reproduce the problem, please tell me how and/or do it
on a console; it is probably a OOPs.
next prev parent reply other threads:[~2004-09-10 11:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-09 13:16 [Bridge] Problem in changed VLAN code can cause systems to hang Mark Ruijter
2004-09-09 15:21 ` [Bridge] " David S. Miller
2004-09-09 15:33 ` shemminger
2004-09-09 15:51 ` David S. Miller
2004-09-10 11:56 ` Stephen Hemminger [this message]
2004-09-10 12:38 ` Tommy Christensen
2004-09-10 13:17 ` Stephen Hemminger
2004-09-10 13:02 ` Mark Ruijter
2004-09-09 15:54 ` Mark Ruijter
2004-09-09 16:00 ` Ben Greear
2004-09-09 15:34 ` Mark Ruijter
2004-09-10 12:43 ` [Bridge] " Tommy Christensen
2004-09-10 13:14 ` Stephen Hemminger
2004-09-10 13:29 ` Mark Ruijter
2004-09-10 23:01 ` David S. Miller
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=20040910045603.32e8ded3@linux.site \
--to=shemminger@osdl.org \
--cc=bridge@lists.osdl.org \
--cc=davem@davemloft.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.