Re: bf_next not NULL!

[Adrian Chadd]

Hi,

Yeah, the problem is that the NF calibration will time out, and I
don't know if it's logging that by default.

Do sysctl dev.ath.0.hal.debug=0x8 and then see what it lsogging when
things hang.

Thanks!



-adrian
___
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: bf_next not NULL!

[Andrew Stevenson]

On 29 Jul 2016, at 22:43, Adrian Chadd  wrote:

> oh god damint, wait. It's an AR9227, right?

Yep.

> ok, please just twist my arm to figure out and commit the "am i deaf?
> restart please" workaround I think i need for the AR9227/AR9287. Grr.

Sorry! If it helps I’m happy to make a donation to your wifi (or beer!) fund if 
you send details.

I don’t see anything else about ath0 logged at the time. There is one "ath0: 
device timeout” but I think it was probably well before the actual clients lost 
connection.

Thanks,

Andrew
___
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: bf_next not NULL!

[Glen Barber]

On Fri, Jul 29, 2016 at 01:43:20PM -0700, Adrian Chadd wrote:
> oh god damint, wait. It's an AR9227, right?
> 
> ok, please just twist my arm to figure out and commit the "am i deaf?
> restart please" workaround I think i need for the AR9227/AR9287. Grr.
> 

Consider your arm twisted.

Glen



signature.asc
Description: PGP signature

Re: bf_next not NULL!

[Adrian Chadd]

oh god damint, wait. It's an AR9227, right?

ok, please just twist my arm to figure out and commit the "am i deaf?
restart please" workaround I think i need for the AR9227/AR9287. Grr.


-a
___
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: bf_next not NULL!

[Andrew Stevenson]

Well after a week of running 11 (BETA1 r303134) I think sadly its worse than 
10. No more bf_next errors. Still lots of "ath0: stuck beacon; resetting (bmiss 
count 4)”. The main thing though is the the clients drop of the network and 
can’t reattach.

Sometimes restarting hostapd is all that is needed, though occasionally I have 
to “restart" the interface (/etc/rc.d/netif restart wlan0).

Happens usually once or twice a day. Is there anything I can do to help debug? 
I tried to attach to hostapd with gdb last time but gdb had an internal error 
and killed the process.

Thanks,

Andrew
___
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

[Adrian Chadd]

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

[Yuri]

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"