Re: Kernel Panic with Atheros Card (TP-LINK N900)

2016-05-16 Thread Jason Morgan 
Ok. Thank you. And thanks for the quick response.
On May 16, 2016 10:16 PM, "Adrian Chadd"  wrote:

> hi,
>
> You'll need to update the whole system. No-one currently keeps the
> stable branches up to date with all the wifi changes / fixes we put
> into -HEAD.
>
>
>
> -adrian
>
>
> On 16 May 2016 at 18:47, Jason Morgan  wrote:
> > Thank you, Adrian. Do I need to upgrade the whole system or just the
> driver?
> > I was hoping to keep the system on RELEASE.
> >
> > On May 16, 2016 9:44 PM, "Adrian Chadd"  wrote:
> >>
> >> Hi,
> >>
> >> I think I've fixed this in head. Would you mind testing that out?
> >>
> >> Thanks!
> >>
> >> A
> >>
> >> On May 16, 2016 6:40 PM, "Jason Morgan" 
> wrote:
> >>>
> >>> Dear List,
> >>>
> >>> I am experiencing multiple kernel panics a day and I believe it's
> >>> related to a Atheros card I recently installed. Here is some detail I
> >>> got from dmesg after the last panic.
> >>>
> >>> ...
> >>> ath0: stuck beacon; resetting (bmiss count 0)
> >>> ath0: stuck beacon; resetting (bmiss count 4)
> >>> ath0: stuck beacon; resetting (bmiss count 4)
> >>> ath0: stuck beacon; resetting (bmiss count 0)
> >>> ath0: stuck beacon; resetting (bmiss count 4)
> >>> ath0: stuck beacon; resetting (bmiss count 0)
> >>> ath0: stuck beacon; resetting (bmiss count 4)
> >>> ath0: stuck beacon; resetting (bmiss count 4)
> >>> ath0: stuck beacon; resetting (bmiss count 0)
> >>> ath0: stuck beacon; resetting (bmiss count 4)
> >>> ath0: stuck beacon; resetting (bmiss count 0)
> >>> ath0: stuck beacon; resetting (bmiss count 4)
> >>> Fatal trap 18: integer divide fault while in kernel mode
> >>> ath0: stuck beacon; resetting (bmiss count 5)
> >>> cpuid = 1; apic id = 01
> >>> instruction pointer = 0x20:0x8045db0d
> >>> stack pointer= 0x28:0xfe01a609a920
> >>> frame pointer= 0x28:0xfe01a609a970
> >>> code segment = base 0x0, limit 0xf, type 0x1b
> >>> = DPL 0, pres 1, long 1, def32 0, gran 1
> >>> processor eflags = interrupt enabled, resume, IOPL = 0
> >>> current process = 12 (swi4: clock)
> >>> trap number = 18
> >>> panic: integer divide fault
> >>> cpuid = 1
> >>> KDB: stack backtrace:
> >>> #0 0x80984ef0 at kdb_backtrace+0x60
> >>> #1 0x80948aa6 at vpanic+0x126
> >>> #2 0x80948973 at panic+0x43
> >>> #3 0x80d4aacb at trap_fatal+0x36b
> >>> #4 0x80d4a74c at trap+0x75c
> >>> #5 0x80d307e2 at calltrap+0x8
> >>> #6 0x80467738 at ar9300_ani_poll_freebsd+0x48
> >>> #7 0x804158c6 at ath_calibrate+0xf6
> >>> #8 0x8095e50b at softclock_call_cc+0x17b
> >>> #9 0x8095e934 at softclock+0x94
> >>> #10 0x8091485b at intr_event_execute_handlers+0xab
> >>> #11 0x80914ca6 at ithread_loop+0x96
> >>> #12 0x8091247a at fork_exit+0x9a
> >>> #13 0x80d30d1e at fork_trampoline+0xe
> >>> Uptime: 1h53m50s
> >>>
> >>> And here are some details on my system and the card:
> >>>
> >>> $ uname -a
> >>> FreeBSD pilot.skepsi.net 10.2-RELEASE-p14 FreeBSD 10.2-RELEASE-p14 #0:
> >>> Wed Mar 16 20:46:12 UTC 2016
> >>> r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64
> >>>
> >>> $ ifconfig | grep -B3 -i wireless
> >>> ath0: flags=8843 metric 0 mtu
> >>> 2290
> >>> ether 30:b5:c2:05:c0:fe
> >>> nd6 options=21
> >>> media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng 
> >>> --
> >>> ether 30:b5:c2:05:c0:fe
> >>> inet 192.168.2.1 netmask 0xff00 broadcast 192.168.2.255
> >>> nd6 options=29
> >>> media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng 
> >>>
> >>> $ ifconfig wlan0 list caps
> >>>
> >>>
> drivercaps=4f85ed01
> >>> cryptocaps=1f
> >>> htcaps=701ee
> >>>
> >>> I am happy to provide any information I can to try to get to the
> >>> bottom of this. I have kernel dumps, etc, if that would help.
> >>>
> >>> Thanks!
> >>>
> >>> --
> >>> ~ Jason Morgan
> >>>
> >>> "Those who have had no share in the good fortunes of the mighty
> >>>  Often have a share in their misfortunes."
> >>> -- Bertolt Brecht, "Der Kaukasische Kreidekreis"
> >>> (The Caucasian Chalk Circle)
> >>> ___
> >>> 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"

Re: Kernel Panic with Atheros Card (TP-LINK N900)

2016-05-16 Thread Adrian Chadd 
hi,

You'll need to update the whole system. No-one currently keeps the
stable branches up to date with all the wifi changes / fixes we put
into -HEAD.



-adrian


On 16 May 2016 at 18:47, Jason Morgan  wrote:
> Thank you, Adrian. Do I need to upgrade the whole system or just the driver?
> I was hoping to keep the system on RELEASE.
>
> On May 16, 2016 9:44 PM, "Adrian Chadd"  wrote:
>>
>> Hi,
>>
>> I think I've fixed this in head. Would you mind testing that out?
>>
>> Thanks!
>>
>> A
>>
>> On May 16, 2016 6:40 PM, "Jason Morgan"  wrote:
>>>
>>> Dear List,
>>>
>>> I am experiencing multiple kernel panics a day and I believe it's
>>> related to a Atheros card I recently installed. Here is some detail I
>>> got from dmesg after the last panic.
>>>
>>> ...
>>> ath0: stuck beacon; resetting (bmiss count 0)
>>> ath0: stuck beacon; resetting (bmiss count 4)
>>> ath0: stuck beacon; resetting (bmiss count 4)
>>> ath0: stuck beacon; resetting (bmiss count 0)
>>> ath0: stuck beacon; resetting (bmiss count 4)
>>> ath0: stuck beacon; resetting (bmiss count 0)
>>> ath0: stuck beacon; resetting (bmiss count 4)
>>> ath0: stuck beacon; resetting (bmiss count 4)
>>> ath0: stuck beacon; resetting (bmiss count 0)
>>> ath0: stuck beacon; resetting (bmiss count 4)
>>> ath0: stuck beacon; resetting (bmiss count 0)
>>> ath0: stuck beacon; resetting (bmiss count 4)
>>> Fatal trap 18: integer divide fault while in kernel mode
>>> ath0: stuck beacon; resetting (bmiss count 5)
>>> cpuid = 1; apic id = 01
>>> instruction pointer = 0x20:0x8045db0d
>>> stack pointer= 0x28:0xfe01a609a920
>>> frame pointer= 0x28:0xfe01a609a970
>>> code segment = base 0x0, limit 0xf, type 0x1b
>>> = DPL 0, pres 1, long 1, def32 0, gran 1
>>> processor eflags = interrupt enabled, resume, IOPL = 0
>>> current process = 12 (swi4: clock)
>>> trap number = 18
>>> panic: integer divide fault
>>> cpuid = 1
>>> KDB: stack backtrace:
>>> #0 0x80984ef0 at kdb_backtrace+0x60
>>> #1 0x80948aa6 at vpanic+0x126
>>> #2 0x80948973 at panic+0x43
>>> #3 0x80d4aacb at trap_fatal+0x36b
>>> #4 0x80d4a74c at trap+0x75c
>>> #5 0x80d307e2 at calltrap+0x8
>>> #6 0x80467738 at ar9300_ani_poll_freebsd+0x48
>>> #7 0x804158c6 at ath_calibrate+0xf6
>>> #8 0x8095e50b at softclock_call_cc+0x17b
>>> #9 0x8095e934 at softclock+0x94
>>> #10 0x8091485b at intr_event_execute_handlers+0xab
>>> #11 0x80914ca6 at ithread_loop+0x96
>>> #12 0x8091247a at fork_exit+0x9a
>>> #13 0x80d30d1e at fork_trampoline+0xe
>>> Uptime: 1h53m50s
>>>
>>> And here are some details on my system and the card:
>>>
>>> $ uname -a
>>> FreeBSD pilot.skepsi.net 10.2-RELEASE-p14 FreeBSD 10.2-RELEASE-p14 #0:
>>> Wed Mar 16 20:46:12 UTC 2016
>>> r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64
>>>
>>> $ ifconfig | grep -B3 -i wireless
>>> ath0: flags=8843 metric 0 mtu
>>> 2290
>>> ether 30:b5:c2:05:c0:fe
>>> nd6 options=21
>>> media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng 
>>> --
>>> ether 30:b5:c2:05:c0:fe
>>> inet 192.168.2.1 netmask 0xff00 broadcast 192.168.2.255
>>> nd6 options=29
>>> media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng 
>>>
>>> $ ifconfig wlan0 list caps
>>>
>>> drivercaps=4f85ed01
>>> cryptocaps=1f
>>> htcaps=701ee
>>>
>>> I am happy to provide any information I can to try to get to the
>>> bottom of this. I have kernel dumps, etc, if that would help.
>>>
>>> Thanks!
>>>
>>> --
>>> ~ Jason Morgan
>>>
>>> "Those who have had no share in the good fortunes of the mighty
>>>  Often have a share in their misfortunes."
>>> -- Bertolt Brecht, "Der Kaukasische Kreidekreis"
>>> (The Caucasian Chalk Circle)
>>> ___
>>> 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"

Re: Kernel Panic with Atheros Card (TP-LINK N900)

2016-05-16 Thread Jason Morgan 
Thank you, Adrian. Do I need to upgrade the whole system or just the
driver? I was hoping to keep the system on RELEASE.
On May 16, 2016 9:44 PM, "Adrian Chadd"  wrote:

> Hi,
>
> I think I've fixed this in head. Would you mind testing that out?
>
> Thanks!
>
> A
> On May 16, 2016 6:40 PM, "Jason Morgan"  wrote:
>
>> Dear List,
>>
>> I am experiencing multiple kernel panics a day and I believe it's
>> related to a Atheros card I recently installed. Here is some detail I
>> got from dmesg after the last panic.
>>
>> ...
>> ath0: stuck beacon; resetting (bmiss count 0)
>> ath0: stuck beacon; resetting (bmiss count 4)
>> ath0: stuck beacon; resetting (bmiss count 4)
>> ath0: stuck beacon; resetting (bmiss count 0)
>> ath0: stuck beacon; resetting (bmiss count 4)
>> ath0: stuck beacon; resetting (bmiss count 0)
>> ath0: stuck beacon; resetting (bmiss count 4)
>> ath0: stuck beacon; resetting (bmiss count 4)
>> ath0: stuck beacon; resetting (bmiss count 0)
>> ath0: stuck beacon; resetting (bmiss count 4)
>> ath0: stuck beacon; resetting (bmiss count 0)
>> ath0: stuck beacon; resetting (bmiss count 4)
>> Fatal trap 18: integer divide fault while in kernel mode
>> ath0: stuck beacon; resetting (bmiss count 5)
>> cpuid = 1; apic id = 01
>> instruction pointer = 0x20:0x8045db0d
>> stack pointer= 0x28:0xfe01a609a920
>> frame pointer= 0x28:0xfe01a609a970
>> code segment = base 0x0, limit 0xf, type 0x1b
>> = DPL 0, pres 1, long 1, def32 0, gran 1
>> processor eflags = interrupt enabled, resume, IOPL = 0
>> current process = 12 (swi4: clock)
>> trap number = 18
>> panic: integer divide fault
>> cpuid = 1
>> KDB: stack backtrace:
>> #0 0x80984ef0 at kdb_backtrace+0x60
>> #1 0x80948aa6 at vpanic+0x126
>> #2 0x80948973 at panic+0x43
>> #3 0x80d4aacb at trap_fatal+0x36b
>> #4 0x80d4a74c at trap+0x75c
>> #5 0x80d307e2 at calltrap+0x8
>> #6 0x80467738 at ar9300_ani_poll_freebsd+0x48
>> #7 0x804158c6 at ath_calibrate+0xf6
>> #8 0x8095e50b at softclock_call_cc+0x17b
>> #9 0x8095e934 at softclock+0x94
>> #10 0x8091485b at intr_event_execute_handlers+0xab
>> #11 0x80914ca6 at ithread_loop+0x96
>> #12 0x8091247a at fork_exit+0x9a
>> #13 0x80d30d1e at fork_trampoline+0xe
>> Uptime: 1h53m50s
>>
>> And here are some details on my system and the card:
>>
>> $ uname -a
>> FreeBSD pilot.skepsi.net 10.2-RELEASE-p14 FreeBSD 10.2-RELEASE-p14 #0:
>> Wed Mar 16 20:46:12 UTC 2016
>> r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64
>>
>> $ ifconfig | grep -B3 -i wireless
>> ath0: flags=8843 metric 0 mtu 2290
>> ether 30:b5:c2:05:c0:fe
>> nd6 options=21
>> media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng 
>> --
>> ether 30:b5:c2:05:c0:fe
>> inet 192.168.2.1 netmask 0xff00 broadcast 192.168.2.255
>> nd6 options=29
>> media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng 
>>
>> $ ifconfig wlan0 list caps
>>
>> drivercaps=4f85ed01
>> cryptocaps=1f
>> htcaps=701ee
>>
>> I am happy to provide any information I can to try to get to the
>> bottom of this. I have kernel dumps, etc, if that would help.
>>
>> Thanks!
>>
>> --
>> ~ Jason Morgan
>>
>> "Those who have had no share in the good fortunes of the mighty
>>  Often have a share in their misfortunes."
>> -- Bertolt Brecht, "Der Kaukasische Kreidekreis"
>> (The Caucasian Chalk Circle)
>> ___
>> 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"

Re: Kernel Panic with Atheros Card (TP-LINK N900)

2016-05-16 Thread Adrian Chadd 
Hi,

I think I've fixed this in head. Would you mind testing that out?

Thanks!

A
On May 16, 2016 6:40 PM, "Jason Morgan"  wrote:

> Dear List,
>
> I am experiencing multiple kernel panics a day and I believe it's
> related to a Atheros card I recently installed. Here is some detail I
> got from dmesg after the last panic.
>
> ...
> ath0: stuck beacon; resetting (bmiss count 0)
> ath0: stuck beacon; resetting (bmiss count 4)
> ath0: stuck beacon; resetting (bmiss count 4)
> ath0: stuck beacon; resetting (bmiss count 0)
> ath0: stuck beacon; resetting (bmiss count 4)
> ath0: stuck beacon; resetting (bmiss count 0)
> ath0: stuck beacon; resetting (bmiss count 4)
> ath0: stuck beacon; resetting (bmiss count 4)
> ath0: stuck beacon; resetting (bmiss count 0)
> ath0: stuck beacon; resetting (bmiss count 4)
> ath0: stuck beacon; resetting (bmiss count 0)
> ath0: stuck beacon; resetting (bmiss count 4)
> Fatal trap 18: integer divide fault while in kernel mode
> ath0: stuck beacon; resetting (bmiss count 5)
> cpuid = 1; apic id = 01
> instruction pointer = 0x20:0x8045db0d
> stack pointer= 0x28:0xfe01a609a920
> frame pointer= 0x28:0xfe01a609a970
> code segment = base 0x0, limit 0xf, type 0x1b
> = DPL 0, pres 1, long 1, def32 0, gran 1
> processor eflags = interrupt enabled, resume, IOPL = 0
> current process = 12 (swi4: clock)
> trap number = 18
> panic: integer divide fault
> cpuid = 1
> KDB: stack backtrace:
> #0 0x80984ef0 at kdb_backtrace+0x60
> #1 0x80948aa6 at vpanic+0x126
> #2 0x80948973 at panic+0x43
> #3 0x80d4aacb at trap_fatal+0x36b
> #4 0x80d4a74c at trap+0x75c
> #5 0x80d307e2 at calltrap+0x8
> #6 0x80467738 at ar9300_ani_poll_freebsd+0x48
> #7 0x804158c6 at ath_calibrate+0xf6
> #8 0x8095e50b at softclock_call_cc+0x17b
> #9 0x8095e934 at softclock+0x94
> #10 0x8091485b at intr_event_execute_handlers+0xab
> #11 0x80914ca6 at ithread_loop+0x96
> #12 0x8091247a at fork_exit+0x9a
> #13 0x80d30d1e at fork_trampoline+0xe
> Uptime: 1h53m50s
>
> And here are some details on my system and the card:
>
> $ uname -a
> FreeBSD pilot.skepsi.net 10.2-RELEASE-p14 FreeBSD 10.2-RELEASE-p14 #0:
> Wed Mar 16 20:46:12 UTC 2016
> r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64
>
> $ ifconfig | grep -B3 -i wireless
> ath0: flags=8843 metric 0 mtu 2290
> ether 30:b5:c2:05:c0:fe
> nd6 options=21
> media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng 
> --
> ether 30:b5:c2:05:c0:fe
> inet 192.168.2.1 netmask 0xff00 broadcast 192.168.2.255
> nd6 options=29
> media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng 
>
> $ ifconfig wlan0 list caps
>
> drivercaps=4f85ed01
> cryptocaps=1f
> htcaps=701ee
>
> I am happy to provide any information I can to try to get to the
> bottom of this. I have kernel dumps, etc, if that would help.
>
> Thanks!
>
> --
> ~ Jason Morgan
>
> "Those who have had no share in the good fortunes of the mighty
>  Often have a share in their misfortunes."
> -- Bertolt Brecht, "Der Kaukasische Kreidekreis"
> (The Caucasian Chalk Circle)
> ___
> 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"