netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Andrew Morton <akpm@osdl.org>
Cc: netdev@oss.sgi.com, dcmwai@pl.jaring.my
Subject: Re: Fw: [Bugme-new] [Bug 4441] New: unregister_netdevice Prompt and system shell lookup when trying to shutdown vlan
Date: Mon, 04 Apr 2005 08:44:17 -0700	[thread overview]
Message-ID: <425160D1.6060701@candelatech.com> (raw)
In-Reply-To: <20050404041822.2ea0c16a.akpm@osdl.org>

Andrew Morton wrote:
> 
> Begin forwarded message:
> 
> Date: Mon, 4 Apr 2005 04:15:25 -0700
> From: bugme-daemon@osdl.org
> To: bugme-new@lists.osdl.org
> Subject: [Bugme-new] [Bug 4441] New: unregister_netdevice Prompt and system shell lookup when trying to shutdown vlan
> 
> 
> http://bugme.osdl.org/show_bug.cgi?id=4441
> 
>            Summary: unregister_netdevice Prompt and system shell lookup when
>                     trying to shutdown vlan
>     Kernel Version: 2.6.11-gentoo-r4 i686
>             Status: NEW
>           Severity: high
>              Owner: acme@conectiva.com.br
>          Submitter: dcmwai@pl.jaring.my
> 
> 
> Distribution: 
> Gentoo, FC2, FC3 
> 
> Hardware Environment:
> Pentium 4 3.0E,
> Intel SE7210TP1-E Server Entry Board
> 512 MB DDR Ram
> 2x Intel® PRO/1000 Dual Port Adapters
> 
> Software Environment:
> Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.3.5, glibc-2.3.4.20041102-r1)
> Fc2 and Fc2 original kernel.
> 
> Problem Description:
> When Shutdown a Vlan using this command
> vconfig rem eth4.1001
> The interface will be down (using ifconfig)
> However the following error will be prompt on the screen and the log leaving the
> shell to be not responding.
> 
> Even if "ifconfig eth4.1001 down" is run before "vconfig rem" sill the problem
> will be there.
> The only way I tested on solve this problem is to shutdown the interface totally.
> ifconfig eth4 down
> 
> Then the vlan can be removed correctly.
> 
> This problem don't happen on the following "special Condition"
> 1) On another motherboard (Gigabyte GA-81PE1000-G) same NIC on Fc3
> 1) On eth0 
> 
> 
> Steps to reproduce:
> 1. get a vlan supported NIC, emerge vconfig
> 2. ifconfig ethx 0.0.0.0
> 3. create a vlan using "vconfig add ethx nnnn"
> 4. ifconfig ethx.nnnn aaa.bbb.ccc.ddd
> 5. remove the vlan using "vconfig rem ethx.nnnn"
> 6. Wait for the error like the below.
> * Motherboard and NIC seem to be a Problem in my case.
> 
> unregister_netdevice: waiting for ethx.nnnn to become free. Usage count = 6

In the past, IPv6 has often been the problem here.  Are you using IPv6?

What is the hardware/driver for eth4?

Thanks,
Ben

> 
> I've also open a bug in Gentoo
> http://bugs.gentoo.org/show_bug.cgi?id=87495
> 
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug, or are watching someone who is.
> 


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

  reply	other threads:[~2005-04-04 15:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-04 11:18 Fw: [Bugme-new] [Bug 4441] New: unregister_netdevice Prompt and system shell lookup when trying to shutdown vlan Andrew Morton
2005-04-04 15:44 ` Ben Greear [this message]
2005-04-04 15:59   ` Ganesh Venkatesan

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=425160D1.6060701@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=akpm@osdl.org \
    --cc=dcmwai@pl.jaring.my \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).