From: Andre Tomt <andre@tomt.net>
To: Hasso Tepper <hasso@estpak.ee>
Cc: Ben Greear <greearb@candelatech.com>, netdev@oss.sgi.com
Subject: Re: 2.6.10 ipv6/8021q lockup on vconfig on interface removal
Date: Thu, 20 Jan 2005 15:04:38 +0100 [thread overview]
Message-ID: <41EFBA76.8040506@tomt.net> (raw)
In-Reply-To: <200501181014.12079.hasso@estpak.ee>
Hasso Tepper wrote:
> Ben Greear wrote:
>
>>Andre Tomt wrote:
>>
>>>I sent this initially about a week ago, but nobody have said anything,
>>>not even a confirmation that its beeing looked into, or about me beeing
>>>silly - highly unusual on netdev! So I'm reposting (with slight
>>>modifications), boo, shame on me. Just a bit worried it slipped through
>>>the cracks.
>>
>>My take on this is that it is a bug in the IPv6 code. If the IPv6 people
>>think that the VLAN code might could be causing this, then I am open to
>>suggestions as to how the VLAN code might be in error....
>
>
> There were similar problems with tunnels in 2.6.8 and 2.6.9 kernels. They
> seems to be gone now in 2.6.10.
>
> Does it help, Andre?
As said in the subject, 2.6.10 exibits this. I had a similar issue
earlier on in 2.6.8, that one got fixed with a host of other related
ones. Then the same symptoms popped up sometime later in the development
of the kernel; not sure exactly when this got introduced as we only ran
our own internal 2.6.8 tree with the fix in.
I should probably do a binary search and at least pinpoint when it
happened, but I won't have any free resources to do so until sometime
this weekend.
prev parent reply other threads:[~2005-01-20 14:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-16 6:30 2.6.10 ipv6/8021q lockup on vconfig on interface removal Andre Tomt
2005-01-17 19:16 ` Ben Greear
2005-01-18 8:14 ` Hasso Tepper
2005-01-20 14:04 ` Andre Tomt [this message]
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=41EFBA76.8040506@tomt.net \
--to=andre@tomt.net \
--cc=greearb@candelatech.com \
--cc=hasso@estpak.ee \
--cc=netdev@oss.sgi.com \
/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.