From: Jarek Poplawski <jarkao2@gmail.com>
To: "Alexander V. Lukyanov" <lav@netis.ru>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: 2.6.29.1: unregister_netdevice problem
Date: Wed, 29 Apr 2009 11:08:09 +0200 [thread overview]
Message-ID: <20090429090809.GA2995@ami.dom.local> (raw)
In-Reply-To: <20090429054510.GA8267@night.netis.ru>
On Wed, Apr 29, 2009 at 09:45:10AM +0400, Alexander V. Lukyanov wrote:
> On Tue, Apr 28, 2009 at 10:49:58PM +0200, Jarek Poplawski wrote:
> > Do you mean if you wait a bit longer (until the first one is really removed)
>
> The problem is that it is never removed. I waited for at least 30 minutes.
>
> > before running another one, it doesn't s(t)uck? Is there a change e.g. wrt.
> > 2.6.28?
>
> I mean, 'vconfig rem' on another interface stucks if the previous vconfig
> has not finished, and it never finishes. So I cannot check if other vlan
> interfaces have the same 'refcnt' problem. So far I tried 'vconfig rem' on
> two vlan interfaces and I have a dozen.
>
> Again, the problem only happens after I notice surprisingly high LA (30
> instead of 2-6) and interactive slowness. When it happens, I check network
> usage, disk usage, cpu usage, mem usage - they are normal or even lower than
> usual.
>
> The server is running transparent squid and named. The last kernel version
> was 2.6.27.21 and it did not have this problem.
So looks like a regression. Alas this thing could be hard to debug and
still more data is needed. For the beginning maybe: .config, dmesg,
and a few SysRq logs while this happens e.g. Alt-PrtScr with t, d, w, q
(gzipped or as attachments to a bugzilla report). (If it's not a big
problem trying 2.6.28.9 could be helpful too.)
Thanks,
Jarek P.
next prev parent reply other threads:[~2009-04-29 9:11 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 [this message]
2009-05-08 6:26 ` Alexander V. Lukyanov
2009-05-08 10:46 ` Jarek Poplawski
2009-05-10 7:35 ` Alexander V. Lukyanov
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=20090429090809.GA2995@ami.dom.local \
--to=jarkao2@gmail.com \
--cc=lav@netis.ru \
--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