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 <y...@rawbw.com> wrote:
> My laptop with ndis driver for BCM4313 NIC crashes periodically during the
> heavy traffic with this kernel stack:
> KDB: stack backtrace:
> #0 0xffffffff809906f0 at kdb_backtrace+0x60
> #1 0xffffffff80953436 at vpanic+0x126
> #2 0xffffffff80953303 at panic+0x43
> #3 0xffffffff80d5bedb at trap_fatal+0x36b
> #4 0xffffffff80d5c1dd at trap_pfault+0x2ed
> #5 0xffffffff80d5b85a at trap+0x47a
> #6 0xffffffff80d4192c at calltrap+0x8
> #7 0xffffffff82098a1d at ndis_start+0x49d
> #8 0xfffff8000438f0ce at dmapbase+0x438f0ce
> #9 0xffffffff82083aa9 at x86_64_call2+0x9
> #10 0xffffffff8091c5fa at fork_exit+0x9a
> #11 0xffffffff80d41e6e 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"

Reply via email to