[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM_iQpXJ1cqJKkp9X1-56gUi4V_s7Gbx_GPo=rgXzJ_LwY+v7w@mail.gmail.com>
Date: Wed, 8 Nov 2017 22:34:10 -0800
From: Cong Wang <xiyou.wangcong@...il.com>
To: Fengguang Wu <fengguang.wu@...el.com>
Cc: Alexander Duyck <alexander.duyck@...il.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Jeff Kirsher <jeffrey.t.kirsher@...el.com>,
Network Development <netdev@...r.kernel.org>,
"David S. Miller" <davem@...emloft.net>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
intel-wired-lan <intel-wired-lan@...ts.osuosl.org>
Subject: Re: [vlan_device_event] BUG: unable to handle kernel paging request
at 6b6b6ccf
On Wed, Nov 8, 2017 at 7:12 PM, Fengguang Wu <fengguang.wu@...el.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)?
Powered by blists - more mailing lists