From: Ben Greear <greearb@candelatech.com>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: netdev@vger.kernel.org,
LKML Kernel <linux-kernel@vger.kernel.org>,
Stephen Hemminger <shemminger@linux-foundation.org>,
OSDL Linux Bridging <bridge@osdl.org>
Subject: Re: [BUG][debian-2.6.20-1-686] bridging + vlans + "vconfig rem" == stuck kernel
Date: Wed, 09 May 2007 21:25:54 -0700 [thread overview]
Message-ID: <46429ED2.10809@candelatech.com> (raw)
In-Reply-To: <2638DE26-D672-4245-BE88-D13B7F0F34A9@mac.com>
Kyle Moffett wrote:
>
> vconfig D 83CCD8CE 0 16564 16562 (NOTLB)
> efdd7e7c 00000086 ee120afb 83ccd8ce 98f00788 b7083ffa 5384b49a
> c76c0b05
> 9ebaf791 00000004 efdd7e4e 00000007 f1468a90 2ab74174 00000362
> 00000326
> f1468b9c c180e420 00000001 00000286 c012933c efdd7e8c df98a000
> c180e468
> Call Trace:
> [<c012933c>] lock_timer_base+0x15/0x2f
> [<c0129445>] __mod_timer+0x91/0x9b
> [<c02988f5>] schedule_timeout+0x70/0x8d
> [<f8b75209>] vlan_device_event+0x13/0xf8 [8021q]
Looks like a deadlock in the vlan code. Any chance you can run this
test with
lockdep enabled?
You could also add a printk in vlan_device_event() to check which event
it is hanging on, and
the netdevice that is passed in.
Since the vlan code holds RTNL at this point, then most other network
tasks will eventually
hang as well.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2007-05-10 4:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 2:54 [BUG][debian-2.6.20-1-686] bridging + vlans + "vconfig rem" == stuck kernel Kyle Moffett
2007-05-10 4:25 ` Ben Greear [this message]
2007-05-10 4:34 ` Kyle Moffett
2007-05-11 5:49 ` Kyle Moffett
2007-05-12 12:13 ` Kyle Moffett
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=46429ED2.10809@candelatech.com \
--to=greearb@candelatech.com \
--cc=bridge@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mrmacman_g4@mac.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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