From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <41407E10.7040000@candelatech.com> Date: Thu, 09 Sep 2004 09:00:16 -0700 From: Ben Greear MIME-Version: 1.0 Subject: Re: [Bridge] Re: Problem in changed VLAN code can cause systems to hang. References: <414057B1.1020902@siennax.com> <20040909082129.62059694.davem@davemloft.net> <4405.131.188.28.69.1094744038.squirrel@www.osdl.org> In-Reply-To: <4405.131.188.28.69.1094744038.squirrel@www.osdl.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit List-Id: Linux Ethernet Bridging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: shemminger@osdl.org Cc: davem@redhat.com, "David S. Miller" , bridge@lists.osdl.org shemminger@osdl.org wrote: >>On Thu, 09 Sep 2004 15:16:33 +0200 >>Mark Ruijter 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? > > > I suspect the underlying device doesn't support mii interface. > If that is true, then the code is doing the right thing (and net-snmp) > is being too dependant on MII. Why would it cause a hang though? I would expect net-snmp to immediately fail the IOCTL and continue on it's merry way. Ben > _______________________________________________ > Bridge mailing list > Bridge@lists.osdl.org > http://lists.osdl.org/mailman/listinfo/bridge > -- Ben Greear Candela Technologies Inc http://www.candelatech.com