From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757705Ab1KVWNr (ORCPT ); Tue, 22 Nov 2011 17:13:47 -0500 Received: from victor.provo.novell.com ([137.65.250.26]:50262 "EHLO victor.provo.novell.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756861Ab1KVWNq (ORCPT ); Tue, 22 Nov 2011 17:13:46 -0500 Subject: RE: A kernel panic occurred when I do some operation about vlan From: joeyli To: Qianhuibin Cc: Jiri Pirko , "jeffrey.t.kirsher@intel.com" , "e1000-devel@lists.sourceforge.net" , "davem@davemloft.net" , Wuchangyi , Qinchuanyu , Zhanghaoyu , "linux-kernel@vger.kernel.org" , lichunhe , Wangzhenguo In-Reply-To: References: <20111122074850.GC2190@minipsycho> Content-Type: text/plain; charset="UTF-8" Date: Wed, 23 Nov 2011 06:11:35 +0800 Message-ID: <1321999895.11930.237.camel@linux-s257.site> Mime-Version: 1.0 X-Mailer: Evolution 2.28.2 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Qianhuibin, 於 二，2011-11-22 於 08:20 +0000，Qianhuibin 提到： > We find the crash on SLES11SP1. > > The igb version is 3.0.6-k2 which comes with SLES11SP1 > Did you file this bug to novell bugzilla: https://bugzilla.novell.com/ I didn't search out your bug from bugzilla, please kindly file it. Let our experts can help. Thank's a lot! Joey Lee > > ________________________________________ > From: Jiri Pirko [jpirko@redhat.com] > Sent: Tuesday, November 22, 2011 15:48 > To: Qianhuibin > Cc: jeffrey.t.kirsher@intel.com; e1000-devel@lists.sourceforge.net; davem@davemloft.net; Wuchangyi; Qinchuanyu; Zhanghaoyu > Subject: Re: A kernel panic occurred when I do some operation about vlan > > Tue, Nov 22, 2011 at 08:11:51AM CET, qianhuibin@huawei.com wrote: > >Hi, all > >A kernel panic occurred when I do some operation about vlan. > > > > > >The operation is as below: > >ifconfig eth2 up > >modprobe bonding > >modprobe 8021q > >ifconfig bond0 up > >ifenslave bond0 eth2 > >vconfig add eth2 3300 > >vconfig add bond0 33 > >vconfig rem eth2.3300 > > > > > >the panic stack is as below: > >[] panic_event+0x49/0x70 [ipmi_msghandler] > >[] notifier_call_chain+0x37/0x70 > >[] panic+0xa2/0x195 > >[] oops_end+0xd8/0x140 > >[] no_context+0xf7/0x280 > >[] __bad_area_nosemaphore+0x175/0x250 > >[] page_fault+0x28/0x30 > >[] igb_vlan_rx_kill_vid+0x4d/0x100 [igb] > >[] bond_vlan_rx_kill_vid+0x9f/0x290 [bonding] > >[] unregister_vlan_dev+0x136/0x180 [8021q] > >[] vlan_ioctl_handler+0x170/0x3f0 [8021q] > >[] sock_ioctl+0x21f/0x280 > >[] vfs_ioctl+0x2f/0xb0 > >[] do_vfs_ioctl+0x3cb/0x5a0 > >[] sys_ioctl+0xa1/0xb0 > >[] system_call_fastpath+0x16/0x1b > >[<00007f108a2b8bd7>] 0x7f108a2b8bd7 > > > > > >And the nic is as below: > >[root@localhost ~]# ethtool -i eth2 > >driver: igb > >version: 3.0.6-k2 > >firmware-version: 1.2-1 > >bus-info: 0000:04:00.0 > > > > > ># lspci | grep Eth > >01:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01) > > > > > >kernel version： > >2.6.32.12-0.7 also happen in 2.6.32-131 > > What kernel is this? RHEL? And what driver you are using? The one which > came with kernel? In case of [yes, yes] answers I suggest filling up bug > at bugzilla.redhat.com > > Jirka > > > > > > >I had tried the same operation on other nics, like tg3,bnx2. But they haven’t panic. > >So I find the reason is that igb have two more netdev_ops (ndo_vlan_rx_add_vid and ndo_vlan_rx_kill_vid) than tg3 and bnx2. > >I think the reason of panic is that when ndo_vlan_rx_kill_vid has been called, the vlgrp haven’t been correctly find. > > > > > >My question is what the purpose of "vlan_group_set_device(adapter->vlgrp, vid, NULL);" in method igb_vlan_rx_kill_vid? > > > >unregister_vlan_dev(vlan.c) has done the same thing after ops->ndo_vlan_rx_kill_vid was called. > > > >If I delete it , Would it cause somthing bad? > > > > > >qinchuanyu > NР骒rybX肚v^)藓{.n+伐{赙zXФ≤}财z&j:+v赙zZ++zf＂h~izwア?ㄨ&)撷f^j谦ym@Aa囤 0鹅hi