From: Cong Wang <xiyou.wangcong@gmail.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Alexander Duyck <alexander.duyck@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
Network Development <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
intel-wired-lan <intel-wired-lan@lists.osuosl.org>
Subject: Re: [vlan_device_event] BUG: unable to handle kernel paging request at 6b6b6ccf
Date: Wed, 8 Nov 2017 22:34:10 -0800 [thread overview]
Message-ID: <CAM_iQpXJ1cqJKkp9X1-56gUi4V_s7Gbx_GPo=rgXzJ_LwY+v7w@mail.gmail.com> (raw)
In-Reply-To: <20171109031206.x6ta5ysdalf3lk3s@wfg-t540p.sh.intel.com>
On Wed, Nov 8, 2017 at 7:12 PM, Fengguang Wu <fengguang.wu@intel.com> wrote:
> Hi Alex,
>
>> So looking over the trace the panic seems to be happening after a
>> decnet interface is getting deleted. Is there any chance we could try
>> compiling the kernel without decnet support to see if that is the
>> source of these issues? I don't know if anyone on the Intel Wired Lan
>> team is testing with that enabled so if we can eliminate that as a
>> possible cause that would be useful.
>
>
> Sure and thank you for the suggestion!
>
> It looks disabling DECNET still triggers the vlan_device_event BUG.
> However when looking at the dmesgs, I find another warning just before
> the vlan_device_event BUG. Not sure if it's related one or independent
> now-fixed issue.
Those decnet symbols are probably noises.
How do you reproduce it? And what is your setup? Vlan device on
top of your eth0 (e1000)?
next prev parent reply other threads:[~2017-11-09 6:34 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 10:21 [vlan_device_event] BUG: unable to handle kernel paging request at 6b6b6ccf Fengguang Wu
2017-11-07 16:25 ` Linus Torvalds
2017-11-07 16:46 ` Fengguang Wu
2017-11-08 9:48 ` Fengguang Wu
2017-11-08 16:20 ` Linus Torvalds
2017-11-08 17:12 ` Fengguang Wu
2017-11-08 17:18 ` Fengguang Wu
2017-11-08 18:05 ` Linus Torvalds
2017-11-08 18:36 ` Alexander Duyck
2017-11-09 3:12 ` Fengguang Wu
2017-11-09 4:09 ` Fengguang Wu
2017-11-09 7:22 ` Fengguang Wu
2017-11-09 6:34 ` Cong Wang [this message]
2017-11-09 6:55 ` Fengguang Wu
2017-11-09 7:43 ` Fengguang Wu
2017-11-09 15:51 ` Girish Moodalbail
2017-11-10 0:16 ` Cong Wang
2017-11-12 19:31 ` Linus Torvalds
2017-11-13 1:13 ` CONFIG_DEBUG_INFO_SPLIT impacts on faddr2line Fengguang Wu
2017-11-13 2:05 ` Zhang Rui
2017-11-13 2:22 ` Fengguang Wu
2017-11-13 18:52 ` Andi Kleen
2017-11-13 19:14 ` Linus Torvalds
2017-11-13 20:10 ` Andi Kleen
2017-11-13 20:14 ` H.J. Lu
2017-11-13 20:56 ` Linus Torvalds
2017-11-13 21:41 ` Andi Kleen
2017-11-13 21:57 ` Linus Torvalds
2017-11-13 23:51 ` Andi Kleen
2017-11-14 8:13 ` Fengguang Wu
2017-11-09 2:43 ` [vlan_device_event] BUG: unable to handle kernel paging request at 6b6b6ccf Fengguang Wu
2017-11-09 6:48 ` Fengguang Wu
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='CAM_iQpXJ1cqJKkp9X1-56gUi4V_s7Gbx_GPo=rgXzJ_LwY+v7w@mail.gmail.com' \
--to=xiyou.wangcong@gmail.com \
--cc=alexander.duyck@gmail.com \
--cc=davem@davemloft.net \
--cc=fengguang.wu@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@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;
as well as URLs for NNTP newsgroup(s).