From: Alexander Aring <aring@mojatatu.com>
To: Roman Makhov <roman.makhov@gmail.com>
Cc: linux-wpan@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Kernel panic on kernel-3.10.0-693.21.1.el7 in ndisc.h
Date: Mon, 14 May 2018 11:40:02 -0400 [thread overview]
Message-ID: <20180514154002.ehab2ss25a45l5p6@x220t> (raw)
In-Reply-To: <CAKyrCQUJWq8aOMskFkr3FJF3Kgt2mKz5tsMCYH7PKqNawybJnA@mail.gmail.com>
Hi,
On Sun, May 13, 2018 at 02:35:07PM +0300, Roman Makhov wrote:
> Hello,
>
> We have a problem with Kernel panic after upgrade from CentOS 7.3
> (kernel-3.10.0-514.el7) to CentOS 7.4 (kernel-3.10.0-693.21.1.el7).
> It occurs when we have the incoming traffic from other nodes and we
> are performing the re-configuration of IPv6 interfaces.
>
> It is high-availability system without 802.15.4 support.
>
> The log of crash:
> =========================================================
> #10 [ffff88043fc03cf0] async_page_fault at ffffffff816b7798
> [exception RIP: ndisc_send_rs+238]
> RIP: ffffffff8166575e RSP: ffff88043fc03da8 RFLAGS: 00010202
> RAX: 0000000000000002 RBX: ffff88042caa9000 RCX: 0000000000000001
> RDX: 0000000000000000 RSI: 0000000000000200 RDI: ffffffff816534f7
> RBP: ffff88043fc03dd0 R8: 0000000000000000 R9: ffffffff81e9f1c0
> R10: 0000000000000002 R11: ffff88043fc03da8 R12: 0000000000000008
> R13: 0000000000000006 R14: ffff88043fc03de0 R15: ffffffff81772410
> ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018
> #11 [ffff88043fc03da0] ndisc_send_rs at ffffffff81665704
> =========================================================
>
> I see that crash points on ndisc.h, it is ndisc_ops_opt_addr_space()
> in function:
> =========================================================
> crash> kmem ffffffff8166575e
> ffffffff8166575e (T) ndisc_send_rs+238
> /usr/src/debug/kernel-3.10.0-693.21.1.el7/linux-3.10.0-693.21.1.el7.x86_64/include/net/ndisc.h:
> 251
>
> PAGE PHYSICAL MAPPING INDEX CNT FLAGS
> ffffea0000059940 1665000 0 0 1 1fffff00000400 reserved
> crash>
> =========================================================
>
> I checked the difference between 514 and 693 kernels is in the patch
> https://patchwork.kernel.org/patch/9179229/ .
>
> Any suggesions about what I am doing wrong are welcome.
>
Me as original author of this patch,
I cannot help you with such a dinosaurs kernel. Please try it with the
latest one and check if the problem still exists.
- Alex
next prev parent reply other threads:[~2018-05-14 15:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-13 11:35 Kernel panic on kernel-3.10.0-693.21.1.el7 in ndisc.h Roman Makhov
2018-05-14 15:40 ` Alexander Aring [this message]
2018-05-14 15:41 ` Alexander Aring
2018-05-14 18:29 ` Roman Makhov
2018-05-14 21:06 ` Stephen Hemminger
2018-05-15 6:55 ` Michal Kubecek
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=20180514154002.ehab2ss25a45l5p6@x220t \
--to=aring@mojatatu.com \
--cc=linux-wpan@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=roman.makhov@gmail.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