From: "David S. Miller" <davem@davemloft.net>
To: shemminger@osdl.org
Cc: bridge@lists.osdl.org
Subject: [Bridge] Re: Problem in changed VLAN code can cause systems to hang.
Date: Thu, 9 Sep 2004 08:51:49 -0700 [thread overview]
Message-ID: <20040909085149.1d483349.davem@davemloft.net> (raw)
In-Reply-To: <4405.131.188.28.69.1094744038.squirrel@www.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 <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?
>
> 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.
next prev parent reply other threads:[~2004-09-09 15:51 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 [this message]
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
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=20040909085149.1d483349.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bridge@lists.osdl.org \
--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 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.