From: Mark Ruijter <bridge@siennax.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: davem@redhat.com, bridge@lists.osdl.org, shemminger@osdl.org
Subject: [Bridge] Re: Problem in changed VLAN code can cause systems to hang.
Date: Thu, 09 Sep 2004 17:34:46 +0200 [thread overview]
Message-ID: <41407816.4050908@siennax.com> (raw)
In-Reply-To: <20040909082129.62059694.davem@davemloft.net>
David S. Miller wrote:
> On Thu, 09 Sep 2004 15:16:33 +0200
> Mark Ruijter <bridge@siennax.com> wrote:
>
>
>>I noticed that the VLAN code of kernels >=2.6.8 contain the patch needed
>>to mirror link state information from the real device to the vlan device.
>>
>>This however causes the system to hang in combination with net-snmpd.
>>The last thing that I see is an ioctl(0x8947...
>
>
> What kind of ethernet devices do you have making use of VLAN?
The machine that would hang had these cards installed ( and had vlan's
on them) :
eth0: Tigon3 [partno(NA) rev 1002 PHY(5703)] (PCIX:100MHz:64-bit)
10/100/1000BaseT Ethernet 00:0f:20:32:35:53
eth0: HostTXDS[1] RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0]
WireSpeed[1] TSOcap[1]
eth1: Tigon3 [partno(NA) rev 1002 PHY(5703)] (PCIX:100MHz:64-bit)
10/100/1000BaseT Ethernet 00:0f:20:32:35:52
e1000: eth2: e1000_probe: Intel(R) PRO/1000 Network Connection
e1000: eth3: e1000_probe: Intel(R) PRO/1000 Network Connection
The laptop that I use however shows the same results:
eth0: RealTek RTL8139 at 0xd902a800, 00:02:3f:6e:58:6e, IRQ 19
eth0: Identified 8139 chip type 'RTL-8101'
So I don't think it's related to the hardware.
net-snmp-5.1 will demonstrate the problem right away.
Just start the deamon on the host and type:
snmpwalk -c public -v 2c 127.0.0.1
Mark.
--
next prev parent reply other threads:[~2004-09-09 15:34 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
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 [this message]
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=41407816.4050908@siennax.com \
--to=bridge@siennax.com \
--cc=bridge@lists.osdl.org \
--cc=davem@davemloft.net \
--cc=davem@redhat.com \
--cc=shemminger@osdl.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox