Date: Wed, 13 Jun 2018 18:54:24 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 228982] [panic] page fault in mld_v2_cancel_link_timers() on boot Message-ID: <bug-228982-7501-qgpQZKk4Bn@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-228982-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-228982-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228982 --- Comment #2 from Andrey V. Elsukov <ae@FreeBSD.org> --- (In reply to Matthew Macy from comment #1) > This looks a lot more like it's tied to my deferred deletion of multicast > addresses. Could you test with a kernel prior to my epoch changes? Also, > could you give me a specific configuration that is most likely to produce > the issue? I update this host periodically, and never seen such panics before epoch changes. I can test some prior revision, but as I said it happens rarely. I think relevant settings are: cloned_interfaces=3D"lagg0" ifconfig_lagg0=3D"laggproto failover laggport em0 laggport re0 DHCP" ifconfig_em0=3D"up" # this port is unplugged ifconfig_re0=3D"up" ipv6_activate_all_interfaces=3D"YES" And my local network usually have some IPv6 activity, at least IPv6 is enab= led. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-228982-7501-qgpQZKk4Bn>