https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211689

Jan Kokemüller <jan.kokemuel...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jan.kokemuel...@gmail.com

--- Comment #4 from Jan Kokemüller <jan.kokemuel...@gmail.com> ---
Created attachment 173477
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=173477&action=edit
remove pending lladdr change when destroying lagg device

Can you try the attached patch? I get similar crashes in "swi6: task queue"
when destroying a lagg device (em0 & iwn0/wlan0 in my case). Maybe this is
related. I'll open a new bug report if not.

In "lagg_clone_destroy" there can be tasks running on the sc_lladdr_task queue
that operate on the main lagg interface. Those tasks run at the same time the
main lagg interface is destroyed in "ether_ifdetach" and "if_free". Tasks that
operate on the lagg ports are correctly removed in "lagg_port_destroy". But
tasks that operate on the main lagg interface are not removed. The attached
patch fixes this.

I can reproduce this crash by running "service netif restart" a few times on an
unmodified 11.0-BETA4 kernel.

Also, can you try to change your lagg configuration in /etc/rc.conf to look
more like this:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211436#c2
This may fix/work around the infinite UP/DOWN loop when bringing up the lagg
interface.

My configuration looks like this (replace "xx:xx:xx:xx:xx:xx" with the MAC
address of the wifi card). The lagg interface comes up reliably.
wlans_iwn0="wlan0"
ifconfig_wlan0="WPA"
ifconfig_em0="ether xx:xx:xx:xx:xx:xx"
cloned_interfaces="lagg0"
ifconfig_lagg0="DHCP laggproto failover laggport em0 laggport wlan0"



Here is a backtrace:

#0  doadump (textdump=<value optimized out>) at pcpu.h:221
#1  0xffffffff80ad6d99 in kern_reboot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:366
#2  0xffffffff80ad734b in vpanic (fmt=<value optimized out>, ap=<value
optimized out>) at /usr/src/sys/kern/kern_shutdown.c:759
#3  0xffffffff80ad7183 in panic (fmt=0x0) at
/usr/src/sys/kern/kern_shutdown.c:690
#4  0xffffffff80f9cd51 in trap_fatal (frame=0xfffffe0227aef850, eva=0) at
/usr/src/sys/amd64/amd64/trap.c:841
#5  0xffffffff80f9cf43 in trap_pfault (frame=0xfffffe0227aef850, usermode=0) at
/usr/src/sys/amd64/amd64/trap.c:691
#6  0xffffffff80f9c4ec in trap (frame=0xfffffe0227aef850) at
/usr/src/sys/amd64/amd64/trap.c:442
#7  0xffffffff80f7fc01 in calltrap () at
/usr/src/sys/amd64/amd64/exception.S:236
#8  0xffffffff80c45800 in arp_iflladdr (arg=0x0, ifp=0xfffff800311d0800) at
/usr/src/sys/netinet/if_ether.c:1339
#9  0xffffffff82660516 in lagg_port_setlladdr (arg=<value optimized out>,
pending=<value optimized out>) at
/usr/src/sys/modules/if_lagg/../../net/if_lagg.c:718
#10 0xffffffff80b31dda in taskqueue_run_locked (queue=<value optimized out>) at
/usr/src/sys/kern/subr_taskqueue.c:465
#11 0xffffffff80b31bcf in taskqueue_run (queue=0xfffff80003f81200) at
/usr/src/sys/kern/subr_taskqueue.c:484
#12 0xffffffff80a9142f in intr_event_execute_handlers (p=<value optimized out>,
ie=<value optimized out>) at /usr/src/sys/kern/kern_intr.c:1262
#13 0xffffffff80a91696 in ithread_loop (arg=<value optimized out>) at
/usr/src/sys/kern/kern_intr.c:1275
#14 0xffffffff80a8e075 in fork_exit (callout=0xffffffff80a915d0 <ithread_loop>,
arg=0xfffff800041fb880, frame=0xfffffe0227aefac0) at
/usr/src/sys/kern/kern_fork.c:1038
#15 0xffffffff80f8013e in fork_trampoline () at
/usr/src/sys/amd64/amd64/exception.S:611
#16 0x0000000000000000 in ?? ()

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Reply via email to