Re: kernel crashes in ndis_start
Hi, Ok, it looks like it's something deep in the ndis driver itself, and it's likely that we've not set it all up right. Trouble is, no, you likely won't get symbols from the .dll. :-) So someone who likes assembly and can read the NDIS spec needs to figure it out. Sorry! -a On 29 July 2016 at 13:20, Yuri wrote: > On 07/20/2016 15:34, Adrian Chadd wrote: >> >> it's doing that for transmitting packets. can you load the crashdump >> into kgdb and get a debug backtrace? >> and/or /var/crash/core.txt.X ? > > > > Hi Adrian, > > > My kgdb kernel crash stack is below. > > Do you know is there a way to also generate .symbols file for > bcmwl564_sys.ko with ndisgen, like is normally generated for all other > kernel modules? Or otherwise where do I go from here? > > > Thanks, > > Yuri > > > (kgdb) bt > #0 doadump (textdump=) at pcpu.h:219 > #1 0x80953092 in kern_reboot (howto=260) at > /usr/src/sys/kern/kern_shutdown.c:486 > #2 0x80953475 in vpanic (fmt=, ap= optimized out>) at /usr/src/sys/kern/kern_shutdown.c:889 > #3 0x80953303 in panic (fmt=0x0) at > /usr/src/sys/kern/kern_shutdown.c:818 > #4 0x80d5bedb in trap_fatal (frame=, > eva=) at /usr/src/sys/amd64/amd64/trap.c:858 > #5 0x80d5c1dd in trap_pfault (frame=0xfe003fc11950, > usermode=) at /usr/src/sys/amd64/amd64/trap.c:681 > #6 0x80d5b85a in trap (frame=0xfe003fc11950) at > /usr/src/sys/amd64/amd64/trap.c:447 > #7 0x80d4192c in calltrap () at > /usr/src/sys/amd64/amd64/exception.S:238 > #8 0x81c37cd0 in ndis_bcmwl564_sys_drv_data_start () from > /boot/modules/bcmwl564_sys.ko > #9 0x81c37e8c in ndis_bcmwl564_sys_drv_data_start () from > /boot/modules/bcmwl564_sys.ko > #10 0x82083aa9 in x86_64_call2 () at > /usr/src/sys/modules/ndis/../../compat/ndis/winx64_wrap.S:138 > #11 0xf800047e9ea0 in ?? () > #12 0xf800047d53a0 in ?? () > #13 0xf800047e9ea0 in ?? () > #14 0xf80004206148 in ?? () > #15 0xfed1e000 in ?? () > #16 0xf800047d5380 in ?? () > #17 0xfed1e000 in ?? () > #18 0x81c379f1 in ndis_bcmwl564_sys_drv_data_start () from > /boot/modules/bcmwl564_sys.ko > #19 0xfed1e001 in ?? () > #20 0xf800047d5380 in ?? () > #21 0x81c37e8c in ndis_bcmwl564_sys_drv_data_start () from > /boot/modules/bcmwl564_sys.ko > #22 0xf800047d5380 in ?? () > #23 0x81c37e8c in ndis_bcmwl564_sys_drv_data_start () from > /boot/modules/bcmwl564_sys.ko > #24 0x81c37edb in ndis_bcmwl564_sys_drv_data_start () from > /boot/modules/bcmwl564_sys.ko > ___ 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"
Re: kernel crashes in ndis_start
On 07/20/2016 15:34, Adrian Chadd wrote: it's doing that for transmitting packets. can you load the crashdump into kgdb and get a debug backtrace? and/or /var/crash/core.txt.X ? Hi Adrian, My kgdb kernel crash stack is below. Do you know is there a way to also generate .symbols file for bcmwl564_sys.ko with ndisgen, like is normally generated for all other kernel modules? Or otherwise where do I go from here? Thanks, Yuri (kgdb) bt #0 doadump (textdump=) at pcpu.h:219 #1 0x80953092 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:486 #2 0x80953475 in vpanic (fmt=, ap=optimized out>) at /usr/src/sys/kern/kern_shutdown.c:889 #3 0x80953303 in panic (fmt=0x0) at /usr/src/sys/kern/kern_shutdown.c:818 #4 0x80d5bedb in trap_fatal (frame=, eva=) at /usr/src/sys/amd64/amd64/trap.c:858 #5 0x80d5c1dd in trap_pfault (frame=0xfe003fc11950, usermode=) at /usr/src/sys/amd64/amd64/trap.c:681 #6 0x80d5b85a in trap (frame=0xfe003fc11950) at /usr/src/sys/amd64/amd64/trap.c:447 #7 0x80d4192c in calltrap () at /usr/src/sys/amd64/amd64/exception.S:238 #8 0x81c37cd0 in ndis_bcmwl564_sys_drv_data_start () from /boot/modules/bcmwl564_sys.ko #9 0x81c37e8c in ndis_bcmwl564_sys_drv_data_start () from /boot/modules/bcmwl564_sys.ko #10 0x82083aa9 in x86_64_call2 () at /usr/src/sys/modules/ndis/../../compat/ndis/winx64_wrap.S:138 #11 0xf800047e9ea0 in ?? () #12 0xf800047d53a0 in ?? () #13 0xf800047e9ea0 in ?? () #14 0xf80004206148 in ?? () #15 0xfed1e000 in ?? () #16 0xf800047d5380 in ?? () #17 0xfed1e000 in ?? () #18 0x81c379f1 in ndis_bcmwl564_sys_drv_data_start () from /boot/modules/bcmwl564_sys.ko #19 0xfed1e001 in ?? () #20 0xf800047d5380 in ?? () #21 0x81c37e8c in ndis_bcmwl564_sys_drv_data_start () from /boot/modules/bcmwl564_sys.ko #22 0xf800047d5380 in ?? () #23 0x81c37e8c in ndis_bcmwl564_sys_drv_data_start () from /boot/modules/bcmwl564_sys.ko #24 0x81c37edb in ndis_bcmwl564_sys_drv_data_start () from /boot/modules/bcmwl564_sys.ko ___ 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"
Re: kernel crashes in ndis_start
On 07/20/2016 15:34, Adrian Chadd wrote: it's doing that for transmitting packets. can you load the crashdump into kgdb and get a debug backtrace? and/or /var/crash/core.txt.X ? kgdb shows that the crash occurs in ndis_bcmwl564_sys_drv_data_start(). #5 0x80d5c1dd in trap_pfault (frame=0xfe003fc08910, usermode=) at /usr/src/sys/amd64/amd64/trap.c:681 #6 0x80d5b85a in trap (frame=0xfe003fc08910) at /usr/src/sys/amd64/amd64/trap.c:447 #7 0x80d4192c in calltrap () at /usr/src/sys/amd64/amd64/exception.S:238 #8 0x81c3571a in ndis_bcmwl564_sys_drv_data_start () from /boot/modules/bcmwl564_sys.ko #9 0x05a8 in ?? () #10 0xf80017617194 in ?? () Otherwise there is no useful info in vmcore.0. I will rerun with the debug kernel and will get more information. Yuri ___ 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"
Re: kernel crashes in ndis_start
hi, it's doing that for transmitting packets. can you load the crashdump into kgdb and get a debug backtrace? and/or /var/crash/core.txt.X ? thanks, -a On 19 July 2016 at 19:34, Yuri wrote: > My laptop with ndis driver for BCM4313 NIC crashes periodically during the > heavy traffic with this kernel stack: > KDB: stack backtrace: > #0 0x809906f0 at kdb_backtrace+0x60 > #1 0x80953436 at vpanic+0x126 > #2 0x80953303 at panic+0x43 > #3 0x80d5bedb at trap_fatal+0x36b > #4 0x80d5c1dd at trap_pfault+0x2ed > #5 0x80d5b85a at trap+0x47a > #6 0x80d4192c at calltrap+0x8 > #7 0x82098a1d at ndis_start+0x49d > #8 0xf8000438f0ce at dmapbase+0x438f0ce > #9 0x82083aa9 at x86_64_call2+0x9 > #10 0x8091c5fa at fork_exit+0x9a > #11 0x80d41e6e at fork_trampoline+0xe > > Crashes happen when wifi connection is established, and wpa_supplicant from > ports is running with a single network in wpa_supplicant.conf. > I am not sure why ndis_start is called. It is possible that wpa_supplicant > decides to bring the interface down and up for some reason. > > FreeBSD 10.3 > > Yuri > ___ > 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" ___ 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"
