public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alexander V. Lukyanov" <lav@netis.ru>
To: Jarek Poplawski <jarkao2@gmail.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: 2.6.29.1: unregister_netdevice problem
Date: Sun, 10 May 2009 11:35:59 +0400	[thread overview]
Message-ID: <20090510073559.GA8929@night.netis.ru> (raw)
In-Reply-To: <20090508104628.GA6287@ff.dom.local>

On Fri, May 08, 2009 at 10:46:28AM +0000, Jarek Poplawski wrote:
> I can't see anything suspicious for now, except these UDP and TCP
> warnings. Did you see similar messages with 2.6.27? Btw., could this

Yes. Such messages show up with any kernel version.

> eth0.987 be "connected" with any of this traffic? (IP# ?)

No, eth0.987 is only used for traffic output.

BTW, it seems that only actively used vlan interfaces have the problem
(even when the traffic stops). Other vlan interfaces with little traffic
can be removed with no problems.

-- 
   Alexander..

  reply	other threads:[~2009-05-10  7:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-22  5:57 2.6.29.1: unregister_netdevice problem Alexander V. Lukyanov
2009-04-23 23:30 ` Eric W. Biederman
2009-04-24 21:16   ` Bruno Prémont
2009-04-27  5:41 ` Alexander V. Lukyanov
2009-04-28 12:57   ` Alexander V. Lukyanov
2009-04-28 20:49     ` Jarek Poplawski
2009-04-29  5:45       ` Alexander V. Lukyanov
2009-04-29  9:08         ` Jarek Poplawski
2009-05-08  6:26           ` Alexander V. Lukyanov
2009-05-08 10:46             ` Jarek Poplawski
2009-05-10  7:35               ` Alexander V. Lukyanov [this message]
2009-05-10 12:46                 ` Jarek Poplawski
2009-05-15  7:19                   ` Alexander V. Lukyanov
2009-05-15  8:06                     ` Jarek Poplawski
2009-05-15  8:54                       ` Alexander V. Lukyanov
2009-05-15 10:12                         ` Jarek Poplawski
2009-05-16  7:06                           ` Jarek Poplawski

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=20090510073559.GA8929@night.netis.ru \
    --to=lav@netis.ru \
    --cc=jarkao2@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.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