Date: Thu, 19 Jan 2017 11:14:06 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 211689] panic with lagg failover wireless ath and iwm Message-ID: <bug-211689-21060-vCE807kwjr@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-211689-21060@https.bugs.freebsd.org/bugzilla/> References: <bug-211689-21060@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=3D211689 --- Comment #15 from Robin Randhawa <robin.randhawa@arm.com> --- (In reply to Alan Somers from comment #14) Before I rebuild kernels and deploy to get you the pre-suspend ifconfig out= put, I thought I'll share my thoughts on your second question, lest it mean I do= n't have to go through the deployment cycle (which is not a problem - just a li= ttle bit of bother). So I'm pretty sure that a "$ service netif restart" invocation will end up taking the lagg interface down via the /etc/rc.conf cloned_interface=3D"lag= g0" specification. AFAICT, that means that the netif rc.d glue will end up invo= king clone_down() [See /etc/network.subr] which looks like it does indeed tear t= he lagg interface down. Does that imply that your patch will need some mods in order to accomodate things ? Please do let me know and I'll follow through as needed. --=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-211689-21060-vCE807kwjr>