From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 9 Sep 2004 08:51:49 -0700 From: "David S. Miller" Message-Id: <20040909085149.1d483349.davem@davemloft.net> In-Reply-To: <4405.131.188.28.69.1094744038.squirrel@www.osdl.org> References: <414057B1.1020902@siennax.com> <20040909082129.62059694.davem@davemloft.net> <4405.131.188.28.69.1094744038.squirrel@www.osdl.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: [Bridge] Re: Problem in changed VLAN code can cause systems to hang. List-Id: Linux Ethernet Bridging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: shemminger@osdl.org Cc: bridge@lists.osdl.org On Thu, 9 Sep 2004 08:33:58 -0700 (PDT) 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. It does, it's tg3. And it shouldn't hang the machine, it's not just hanging userspace. Therefore it is a kernel bug.