Re: IWN hangs periodically on 10.0RC3
On Tue, Jan 28, 2014 at 3:57 PM, Adrian Chadd wrote: > What's in dmesg? Did the firmware panic? > > Adrian > pci3: on pcib2 iwn0: mem 0xf240-0xf2401fff irq 17 at device 0.0 on pci3 [...] wlan0: Ethernet address: a0:88:b4:c6:ad:28 ipfw2 (+ipv6) initialized, divert loadable, nat loadable, default to deny, logging disabled These are the only entries that look even a bit related to the wireless. Let me know if you want the whole thing. No indication I see of a firmware panic in either dmesg or var/log/messages. [EOF] > On Jan 28, 2014 2:16 AM, "Kevin Oberman" wrote: > >> On Fri, Jan 10, 2014 at 9:51 PM, Kevin Oberman wrote: >> >>> On Fri, Jan 10, 2014 at 9:37 AM, Adrian Chadd wrote: >>> .. when you see it hang, does anything get logged in dmesg (eg a firmware panic) ? Try recompiling your kernel with: IEEE80211_DEBUG IWN_DEBUG That way it can be debugged :) The first thing I'd check is whether there's more fun races going on in the crypto code - try wlandebug +crypto . -a >>> >>> I just sent a message about issues I am seeing with my IWN to wireless@. >>> Then I saw these responses. Sorry. >>> >>> As far as logs go, I wee a number if cases of the following sequence: >>> Jan 1 18:00:12 rogue dbus[1451]: [system] Activating service >>> name='org.freedesktop.PackageKit' (using servicehelper) >>> Jan 1 18:00:12 rogue dbus[1451]: [system] Successfully activated >>> service 'org.freedesktop.PackageKit' >>> Jan 1 18:28:56 rogue wpa_supplicant[620]: wlan0: >>> CTRL-EVENT-DISCONNECTED bssid=00:26:b8:67:c3:2d reason=0 >>> Jan 1 18:28:56 rogue kernel: wlan0: link state changed to DOWN >>> Jan 1 18:28:59 rogue wpa_supplicant[620]: wlan0: Trying to associate >>> with 00:26:b8:67:c3:2d (SSID='babcom' freq=2437 MHz) >>> Jan 1 18:28:59 rogue wpa_supplicant[620]: wlan0: Associated with >>> 00:26:b8:67:c3:2d >>> Jan 1 18:28:59 rogue kernel: wlan0: link state changed to UP >>> Jan 1 18:28:59 rogue dhclient[652]: send_packet: No buffer space >>> available >>> Jan 1 18:28:59 rogue devd: Executing '/etc/rc.d/dhclient quietstart >>> wlan0' >>> Jan 1 18:28:59 rogue wpa_supplicant[620]: wlan0: WPA: Key negotiation >>> completed with 00:26:b8:67:c3:2d [PTK=CCMP GTK=CCMP] >>> Jan 1 18:28:59 rogue wpa_supplicant[620]: wlan0: CTRL-EVENT-CONNECTED - >>> Connection to 00:26:b8:67:c3:2d completed [id=1 id_str=] >>> Jan 1 18:29:02 rogue dhclient: New IP Address (wlan0): 192.168.1.5 >>> Jan 1 18:29:02 rogue dhclient: New Subnet Mask (wlan0): 255.255.255.0 >>> Jan 1 18:29:02 rogue dhclient: New Broadcast Address (wlan0): >>> 192.168.1.255 >>> Jan 1 18:29:02 rogue dhclient: New Routers (wlan0): 192.168.1.1 >>> >>> So it seems that the bounce is happening fairly often, but the system >>> usually recovers. It seems to be pretty consistently 2-3 time4s a day. >>> Note that the dbus messages about packagekit always immediately precede >>> the link going down. >>> >>> Every tthe or four of these fail to recover: >>> Jan 3 14:09:05 rogue kernel: wlan0: link state changed to DOWN >>> Jan 3 14:09:56 rogue ntpd[1303]: sendto(198.129.254.218) (fd=25): >>> Network is down >>> Jan 3 14:10:15 rogue ntpd[1303]: sendto(208.79.18.86) (fd=25): Network >>> is down >>> Jan 3 14:10:29 rogue ntpd[1303]: sendto(198.124.252.90) (fd=25): >>> Network is down >>> Jan 3 14:10:49 rogue ntpd[1303]: sendto(198.55.111.5) (fd=25): Network >>> is down >>> Jan 3 14:11:00 rogue ntpd[1303]: sendto(192.95.38.104) (fd=25): Network >>> is down >>> Jan 3 14:14:02 rogue ntpd[1303]: sendto(198.129.252.38) (fd=25): >>> Network is down >>> Jan 3 14:14:12 rogue wpa_supplicant[620]: ioctl[SIOCS80211, op=26, >>> val=0, arg_len=0]: Operation not supported >>> Jan 3 14:14:12 rogue wpa_supplicant[620]: ioctl[SIOCS80211, op=26, >>> val=0, arg_len=0]: Operation not supported >>> Jan 3 14:14:12 rogue wpa_supplicant[620]: wlan0: CTRL-EVENT-TERMINATING >>> Jan 3 14:14:12 rogue dhclient[652]: connection closed >>> Jan 3 14:14:12 rogue dhclient[652]: exiting. >>> Jan 3 14:14:12 rogue wpa_supplicant[67153]: Successfully initialized >>> wpa_supplicant >>> Jan 3 14:14:16 rogue wpa_supplicant[67154]: wlan0: Trying to associate >>> with 00:26:b8:67:c3:2d (SSID='babcom' freq=2437 MHz) >>> Jan 3 14:14:16 rogue wpa_supplicant[67154]: wlan0: Associated with >>> 00:26:b8:67:c3:2d >>> Jan 3 14:14:16 rogue kernel: wlan0: link state changed to UP >>> Jan 3 14:14:16 rogue devd: Executing '/etc/rc.d/dhclient quietstart >>> wlan0' >>> Jan 3 14:14:16 rogue dhclient[67191]: send_packet: No buffer space >>> available >>> Jan 3 14:14:17 rogue wpa_supplicant[67154]: wlan0: WPA: Key negotiation >>> completed with 00:26:b8:67:c3:2d [PTK=CCMP GTK=CCMP] >>> Jan 3 14:14:17 rogue wpa_supplicant[67154]: wlan0: CTRL-EVENT-CONNECTED >>> - Connection to 00:26:b8:67:c3:2d completed [id=1 id_str=] >>> Jan 3 14:14:18 rogue dhclient: New IP Address (wlan0): 192.168.1.5 >>> Jan 3 14:14:18 rogue dhclient: New S
Re: IWN hangs periodically on 10.0RC3
What's in dmesg? Did the firmware panic? Adrian On Jan 28, 2014 2:16 AM, "Kevin Oberman" wrote: > On Fri, Jan 10, 2014 at 9:51 PM, Kevin Oberman wrote: > >> On Fri, Jan 10, 2014 at 9:37 AM, Adrian Chadd wrote: >> >>> .. when you see it hang, does anything get logged in dmesg (eg a >>> firmware panic) ? >>> >>> Try recompiling your kernel with: >>> >>> IEEE80211_DEBUG >>> IWN_DEBUG >>> >>> That way it can be debugged :) >>> >>> The first thing I'd check is whether there's more fun races going on >>> in the crypto code - try wlandebug +crypto . >>> >>> >>> -a >>> >> >> I just sent a message about issues I am seeing with my IWN to wireless@. >> Then I saw these responses. Sorry. >> >> As far as logs go, I wee a number if cases of the following sequence: >> Jan 1 18:00:12 rogue dbus[1451]: [system] Activating service >> name='org.freedesktop.PackageKit' (using servicehelper) >> Jan 1 18:00:12 rogue dbus[1451]: [system] Successfully activated service >> 'org.freedesktop.PackageKit' >> Jan 1 18:28:56 rogue wpa_supplicant[620]: wlan0: CTRL-EVENT-DISCONNECTED >> bssid=00:26:b8:67:c3:2d reason=0 >> Jan 1 18:28:56 rogue kernel: wlan0: link state changed to DOWN >> Jan 1 18:28:59 rogue wpa_supplicant[620]: wlan0: Trying to associate >> with 00:26:b8:67:c3:2d (SSID='babcom' freq=2437 MHz) >> Jan 1 18:28:59 rogue wpa_supplicant[620]: wlan0: Associated with >> 00:26:b8:67:c3:2d >> Jan 1 18:28:59 rogue kernel: wlan0: link state changed to UP >> Jan 1 18:28:59 rogue dhclient[652]: send_packet: No buffer space >> available >> Jan 1 18:28:59 rogue devd: Executing '/etc/rc.d/dhclient quietstart >> wlan0' >> Jan 1 18:28:59 rogue wpa_supplicant[620]: wlan0: WPA: Key negotiation >> completed with 00:26:b8:67:c3:2d [PTK=CCMP GTK=CCMP] >> Jan 1 18:28:59 rogue wpa_supplicant[620]: wlan0: CTRL-EVENT-CONNECTED - >> Connection to 00:26:b8:67:c3:2d completed [id=1 id_str=] >> Jan 1 18:29:02 rogue dhclient: New IP Address (wlan0): 192.168.1.5 >> Jan 1 18:29:02 rogue dhclient: New Subnet Mask (wlan0): 255.255.255.0 >> Jan 1 18:29:02 rogue dhclient: New Broadcast Address (wlan0): >> 192.168.1.255 >> Jan 1 18:29:02 rogue dhclient: New Routers (wlan0): 192.168.1.1 >> >> So it seems that the bounce is happening fairly often, but the system >> usually recovers. It seems to be pretty consistently 2-3 time4s a day. >> Note that the dbus messages about packagekit always immediately precede >> the link going down. >> >> Every tthe or four of these fail to recover: >> Jan 3 14:09:05 rogue kernel: wlan0: link state changed to DOWN >> Jan 3 14:09:56 rogue ntpd[1303]: sendto(198.129.254.218) (fd=25): >> Network is down >> Jan 3 14:10:15 rogue ntpd[1303]: sendto(208.79.18.86) (fd=25): Network >> is down >> Jan 3 14:10:29 rogue ntpd[1303]: sendto(198.124.252.90) (fd=25): Network >> is down >> Jan 3 14:10:49 rogue ntpd[1303]: sendto(198.55.111.5) (fd=25): Network >> is down >> Jan 3 14:11:00 rogue ntpd[1303]: sendto(192.95.38.104) (fd=25): Network >> is down >> Jan 3 14:14:02 rogue ntpd[1303]: sendto(198.129.252.38) (fd=25): Network >> is down >> Jan 3 14:14:12 rogue wpa_supplicant[620]: ioctl[SIOCS80211, op=26, >> val=0, arg_len=0]: Operation not supported >> Jan 3 14:14:12 rogue wpa_supplicant[620]: ioctl[SIOCS80211, op=26, >> val=0, arg_len=0]: Operation not supported >> Jan 3 14:14:12 rogue wpa_supplicant[620]: wlan0: CTRL-EVENT-TERMINATING >> Jan 3 14:14:12 rogue dhclient[652]: connection closed >> Jan 3 14:14:12 rogue dhclient[652]: exiting. >> Jan 3 14:14:12 rogue wpa_supplicant[67153]: Successfully initialized >> wpa_supplicant >> Jan 3 14:14:16 rogue wpa_supplicant[67154]: wlan0: Trying to associate >> with 00:26:b8:67:c3:2d (SSID='babcom' freq=2437 MHz) >> Jan 3 14:14:16 rogue wpa_supplicant[67154]: wlan0: Associated with >> 00:26:b8:67:c3:2d >> Jan 3 14:14:16 rogue kernel: wlan0: link state changed to UP >> Jan 3 14:14:16 rogue devd: Executing '/etc/rc.d/dhclient quietstart >> wlan0' >> Jan 3 14:14:16 rogue dhclient[67191]: send_packet: No buffer space >> available >> Jan 3 14:14:17 rogue wpa_supplicant[67154]: wlan0: WPA: Key negotiation >> completed with 00:26:b8:67:c3:2d [PTK=CCMP GTK=CCMP] >> Jan 3 14:14:17 rogue wpa_supplicant[67154]: wlan0: CTRL-EVENT-CONNECTED >> - Connection to 00:26:b8:67:c3:2d completed [id=1 id_str=] >> Jan 3 14:14:18 rogue dhclient: New IP Address (wlan0): 192.168.1.5 >> Jan 3 14:14:18 rogue dhclient: New Subnet Mask (wlan0): 255.255.255.0 >> Jan 3 14:14:18 rogue dhclient: New Broadcast Address (wlan0): >> 192.168.1.255 >> Jan 3 14:14:18 rogue dhclient: New Routers (wlan0): 192.168.1.1 >> >> The restart took place when I restarted the interface about 5 minutes >> after it went down and, as you can see, it came up normally. I'll admit >> that I am completely baffled by the dbus/packagekit tie-in as I can't see >> what packagekit would do to touch the network. >> >> I'll be building a new kernel with debug shortly. >> >> In my other message (to wireless) I also mentioned t
Re: FreeBSD 10.0: hostapd crash with Ralink 3070
Yup. Is it?
Adrian
On Jan 28, 2014 6:10 PM, "Pedro Flynn" wrote:
> You mean rvp->beacon_mbuf is null?
>
> Thanks,
>
> pflynn
>
>
> On Tue, Jan 28, 2014 at 9:06 PM, Pedro Flynn wrote:
>
>> Just to bring to our attention frame 8:
>>
>> (kgdb) frame 8
>> #8 0x81a198bc in run_update_beacon (vap=0xf8000e8dd000,
>> item=2)
>> at /usr/src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c:3974
>> 3974 ieee80211_beacon_update(vap->iv_bss, &rvp->bo, rvp->beacon_mbuf,
>> mcast);
>> Current language: auto; currently minimal
>> (kgdb) print run_update_beacon
>> $23 = {void (struct ieee80211vap *,
>> int)} 0x81a19750
>> (kgdb)
>>
>> thanks,
>>
>> pflynn
>>
>>
>> On Tue, Jan 28, 2014 at 9:04 PM, Adrian Chadd wrote:
>>
>>> Right, frame 8 (the run beacon update) is passing a NULL mbuf into
>>> net80211. Why's it doing that.
>>>
>>>
>>>
>>> -a
>>>
>>>
>>> On 28 January 2014 15:02, Pedro Flynn wrote:
>>> > Here we go (this output is not beautiful...). Please, let me know if I
>>> > missed something or if I did something wrong:
>>> >
>>> > bt output:
>>> >
>>> > #0 doadump (textdump=) at pcpu.h:219
>>> > #1 0x808af530 in kern_reboot (howto=260)
>>> > at /usr/src/sys/kern/kern_shutdown.c:447
>>> > #2 0x808af8f4 in panic (fmt=)
>>> > at /usr/src/sys/kern/kern_shutdown.c:754
>>> > #3 0x80c8e692 in trap_fatal (frame=,
>>> > eva=) at /usr/src/sys/amd64/amd64/trap.c:882
>>> > #4 0x80c8e969 in trap_pfault (frame=0xfe009695f720,
>>> usermode=0)
>>> > at /usr/src/sys/amd64/amd64/trap.c:699
>>> > #5 0x80c8e0f6 in trap (frame=0xfe009695f720)
>>> > at /usr/src/sys/amd64/amd64/trap.c:463
>>> > #6 0x80c75392 in calltrap ()
>>> > at /usr/src/sys/amd64/amd64/exception.S:232
>>> > #7 0x809b1163 in ieee80211_beacon_update
>>> (ni=0xfeffc000,
>>> > bo=0xf8000e8dd9e8, m=0x0, mcast=0) at atomic.h:161
>>> > #8 0x81a198bc in run_update_beacon (vap=0xf8000e8dd000,
>>> item=2)
>>> > at /usr/src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c:3974
>>> > #9 0x809b42bd in ieee80211_wme_updateparams_locked (
>>> > vap=0xf8000e8dd000) at ieee80211_var.h:814
>>> > #10 0x809b437a in ieee80211_wme_updateparams
>>> > (vap=0xf8000e8dd000)
>>> > at /usr/src/sys/net80211/ieee80211_proto.c:1150
>>> > #11 0x809b3f43 in ieee80211_wme_initparams (vap=>> optimized
>>> > out>)
>>> > at /usr/src/sys/net80211/ieee80211_proto.c:955
>>> > #12 0x809a9aec in ieee80211_sta_join1 ()
>>> > at /usr/src/sys/net80211/ieee80211_node.c:741
>>> > #13 0x8099047b in hostap_newstate (vap=0xf8000e8dd000,
>>> > nstate=, arg=)
>>> > at /usr/src/sys/net80211/ieee80211_hostap.c:274
>>> > #14 0x81a1a36a in run_newstate (vap=,
>>> > nstate=IEEE80211_S_RUN, arg=-1)
>>> > at /usr/src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c:1881
>>> > #15 0x809b2edf in ieee80211_newstate_cb
>>> (xvap=0xf8000e8dd000,
>>> > npending=)
>>> > at /usr/src/sys/net80211/ieee80211_proto.c:1756
>>> > #16 0x808f5b66 in taskqueue_run_locked
>>> (queue=0xf8000e8e4600)
>>> > at /usr/src/sys/kern/subr_taskqueue.c:333
>>> > #17 0x808f63e8 in taskqueue_thread_loop (arg=>> out>)
>>> > at /usr/src/sys/kern/subr_taskqueue.c:535
>>> > #18 0x8088198a in fork_exit (
>>> > callout=0x808f6340 ,
>>> > arg=0xfeff60f0, frame=0xfe009695fc00)
>>> > at /usr/src/sys/kern/kern_fork.c:995
>>> > #19 0x80c758ce in fork_trampoline ()
>>> > at /usr/src/sys/amd64/amd64/exception.S:606
>>> > #20 0x in ?? ()
>>> >
>>> > frame 0
>>> > #0 doadump (textdump=) at pcpu.h:219
>>> > 219 pcpu.h: No such file or directory.
>>> > in pcpu.h
>>> > print doadump
>>> > $1 = {int (boolean_t)} 0x808af6f0
>>> >
>>> > frame 1:
>>> > #1 0x808af530 in kern_reboot (howto=260)
>>> > at /usr/src/sys/kern/kern_shutdown.c:447
>>> > 447 doadump(TRUE);
>>> > print kern_reboot
>>> > print kern_reboot
>>> > $3 = {void (int)} 0x808aedf0
>>> >
>>> > frame 2
>>> > #2 0x808af8f4 in panic (fmt=)
>>> > at /usr/src/sys/kern/kern_shutdown.c:754
>>> > 754 kern_reboot(bootopt);
>>> > (kgdb) print panic
>>> > $4 = {void (const char *)} 0x808af760
>>> >
>>> > frame 3
>>> > #3 0x80c8e692 in trap_fatal (frame=,
>>> > eva=) at /usr/src/sys/amd64/amd64/trap.c:882
>>> > 882 panic("%s", trap_msg[type]);
>>> > (kgdb) print trap_fatal
>>> > $5 = {void (struct trapframe *, vm_offset_t)} 0x80c8e2f0
>>> >
>>> > (kgdb) frame 4
>>> > #4 0x80c8e969 in trap_pfault (frame=0xfe009695f720,
>>> usermode=0)
>>> > at /usr/src/sys/amd64/amd64/trap.c:699
>>> > 699 trap_fatal(frame, eva);
>>> > (kgdb) print trap_pfault
>>> > $6 = {int (struct trapframe *, int)} 0x80c8e6a0
>>> > (kgdb) frame 5
>>> > #5 0x80c8e0f6 in trap (fra
Re: FreeBSD 10.0: hostapd crash with Ralink 3070
You mean rvp->beacon_mbuf is null?
Thanks,
pflynn
On Tue, Jan 28, 2014 at 9:06 PM, Pedro Flynn wrote:
> Just to bring to our attention frame 8:
>
> (kgdb) frame 8
> #8 0x81a198bc in run_update_beacon (vap=0xf8000e8dd000,
> item=2)
> at /usr/src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c:3974
> 3974 ieee80211_beacon_update(vap->iv_bss, &rvp->bo, rvp->beacon_mbuf,
> mcast);
> Current language: auto; currently minimal
> (kgdb) print run_update_beacon
> $23 = {void (struct ieee80211vap *,
> int)} 0x81a19750
> (kgdb)
>
> thanks,
>
> pflynn
>
>
> On Tue, Jan 28, 2014 at 9:04 PM, Adrian Chadd wrote:
>
>> Right, frame 8 (the run beacon update) is passing a NULL mbuf into
>> net80211. Why's it doing that.
>>
>>
>>
>> -a
>>
>>
>> On 28 January 2014 15:02, Pedro Flynn wrote:
>> > Here we go (this output is not beautiful...). Please, let me know if I
>> > missed something or if I did something wrong:
>> >
>> > bt output:
>> >
>> > #0 doadump (textdump=) at pcpu.h:219
>> > #1 0x808af530 in kern_reboot (howto=260)
>> > at /usr/src/sys/kern/kern_shutdown.c:447
>> > #2 0x808af8f4 in panic (fmt=)
>> > at /usr/src/sys/kern/kern_shutdown.c:754
>> > #3 0x80c8e692 in trap_fatal (frame=,
>> > eva=) at /usr/src/sys/amd64/amd64/trap.c:882
>> > #4 0x80c8e969 in trap_pfault (frame=0xfe009695f720,
>> usermode=0)
>> > at /usr/src/sys/amd64/amd64/trap.c:699
>> > #5 0x80c8e0f6 in trap (frame=0xfe009695f720)
>> > at /usr/src/sys/amd64/amd64/trap.c:463
>> > #6 0x80c75392 in calltrap ()
>> > at /usr/src/sys/amd64/amd64/exception.S:232
>> > #7 0x809b1163 in ieee80211_beacon_update
>> (ni=0xfeffc000,
>> > bo=0xf8000e8dd9e8, m=0x0, mcast=0) at atomic.h:161
>> > #8 0x81a198bc in run_update_beacon (vap=0xf8000e8dd000,
>> item=2)
>> > at /usr/src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c:3974
>> > #9 0x809b42bd in ieee80211_wme_updateparams_locked (
>> > vap=0xf8000e8dd000) at ieee80211_var.h:814
>> > #10 0x809b437a in ieee80211_wme_updateparams
>> > (vap=0xf8000e8dd000)
>> > at /usr/src/sys/net80211/ieee80211_proto.c:1150
>> > #11 0x809b3f43 in ieee80211_wme_initparams (vap=> > out>)
>> > at /usr/src/sys/net80211/ieee80211_proto.c:955
>> > #12 0x809a9aec in ieee80211_sta_join1 ()
>> > at /usr/src/sys/net80211/ieee80211_node.c:741
>> > #13 0x8099047b in hostap_newstate (vap=0xf8000e8dd000,
>> > nstate=, arg=)
>> > at /usr/src/sys/net80211/ieee80211_hostap.c:274
>> > #14 0x81a1a36a in run_newstate (vap=,
>> > nstate=IEEE80211_S_RUN, arg=-1)
>> > at /usr/src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c:1881
>> > #15 0x809b2edf in ieee80211_newstate_cb
>> (xvap=0xf8000e8dd000,
>> > npending=)
>> > at /usr/src/sys/net80211/ieee80211_proto.c:1756
>> > #16 0x808f5b66 in taskqueue_run_locked
>> (queue=0xf8000e8e4600)
>> > at /usr/src/sys/kern/subr_taskqueue.c:333
>> > #17 0x808f63e8 in taskqueue_thread_loop (arg=> out>)
>> > at /usr/src/sys/kern/subr_taskqueue.c:535
>> > #18 0x8088198a in fork_exit (
>> > callout=0x808f6340 ,
>> > arg=0xfeff60f0, frame=0xfe009695fc00)
>> > at /usr/src/sys/kern/kern_fork.c:995
>> > #19 0x80c758ce in fork_trampoline ()
>> > at /usr/src/sys/amd64/amd64/exception.S:606
>> > #20 0x in ?? ()
>> >
>> > frame 0
>> > #0 doadump (textdump=) at pcpu.h:219
>> > 219 pcpu.h: No such file or directory.
>> > in pcpu.h
>> > print doadump
>> > $1 = {int (boolean_t)} 0x808af6f0
>> >
>> > frame 1:
>> > #1 0x808af530 in kern_reboot (howto=260)
>> > at /usr/src/sys/kern/kern_shutdown.c:447
>> > 447 doadump(TRUE);
>> > print kern_reboot
>> > print kern_reboot
>> > $3 = {void (int)} 0x808aedf0
>> >
>> > frame 2
>> > #2 0x808af8f4 in panic (fmt=)
>> > at /usr/src/sys/kern/kern_shutdown.c:754
>> > 754 kern_reboot(bootopt);
>> > (kgdb) print panic
>> > $4 = {void (const char *)} 0x808af760
>> >
>> > frame 3
>> > #3 0x80c8e692 in trap_fatal (frame=,
>> > eva=) at /usr/src/sys/amd64/amd64/trap.c:882
>> > 882 panic("%s", trap_msg[type]);
>> > (kgdb) print trap_fatal
>> > $5 = {void (struct trapframe *, vm_offset_t)} 0x80c8e2f0
>> >
>> > (kgdb) frame 4
>> > #4 0x80c8e969 in trap_pfault (frame=0xfe009695f720,
>> usermode=0)
>> > at /usr/src/sys/amd64/amd64/trap.c:699
>> > 699 trap_fatal(frame, eva);
>> > (kgdb) print trap_pfault
>> > $6 = {int (struct trapframe *, int)} 0x80c8e6a0
>> > (kgdb) frame 5
>> > #5 0x80c8e0f6 in trap (frame=0xfe009695f720)
>> > at /usr/src/sys/amd64/amd64/trap.c:463
>> > 463 (void) trap_pfault(frame, FALSE);
>> > (kgdb) print trap
>> > $7 = {void (struct trapframe *)} 0x80c8db10
>> >
>> > frame 6
>> > #6
Re: FreeBSD 10.0: hostapd crash with Ralink 3070
Just to bring to our attention frame 8:
(kgdb) frame 8
#8 0x81a198bc in run_update_beacon (vap=0xf8000e8dd000, item=2)
at /usr/src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c:3974
3974 ieee80211_beacon_update(vap->iv_bss, &rvp->bo, rvp->beacon_mbuf,
mcast);
Current language: auto; currently minimal
(kgdb) print run_update_beacon
$23 = {void (struct ieee80211vap *,
int)} 0x81a19750
(kgdb)
thanks,
pflynn
On Tue, Jan 28, 2014 at 9:04 PM, Adrian Chadd wrote:
> Right, frame 8 (the run beacon update) is passing a NULL mbuf into
> net80211. Why's it doing that.
>
>
>
> -a
>
>
> On 28 January 2014 15:02, Pedro Flynn wrote:
> > Here we go (this output is not beautiful...). Please, let me know if I
> > missed something or if I did something wrong:
> >
> > bt output:
> >
> > #0 doadump (textdump=) at pcpu.h:219
> > #1 0x808af530 in kern_reboot (howto=260)
> > at /usr/src/sys/kern/kern_shutdown.c:447
> > #2 0x808af8f4 in panic (fmt=)
> > at /usr/src/sys/kern/kern_shutdown.c:754
> > #3 0x80c8e692 in trap_fatal (frame=,
> > eva=) at /usr/src/sys/amd64/amd64/trap.c:882
> > #4 0x80c8e969 in trap_pfault (frame=0xfe009695f720,
> usermode=0)
> > at /usr/src/sys/amd64/amd64/trap.c:699
> > #5 0x80c8e0f6 in trap (frame=0xfe009695f720)
> > at /usr/src/sys/amd64/amd64/trap.c:463
> > #6 0x80c75392 in calltrap ()
> > at /usr/src/sys/amd64/amd64/exception.S:232
> > #7 0x809b1163 in ieee80211_beacon_update (ni=0xfeffc000,
> > bo=0xf8000e8dd9e8, m=0x0, mcast=0) at atomic.h:161
> > #8 0x81a198bc in run_update_beacon (vap=0xf8000e8dd000,
> item=2)
> > at /usr/src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c:3974
> > #9 0x809b42bd in ieee80211_wme_updateparams_locked (
> > vap=0xf8000e8dd000) at ieee80211_var.h:814
> > #10 0x809b437a in ieee80211_wme_updateparams
> > (vap=0xf8000e8dd000)
> > at /usr/src/sys/net80211/ieee80211_proto.c:1150
> > #11 0x809b3f43 in ieee80211_wme_initparams (vap= > out>)
> > at /usr/src/sys/net80211/ieee80211_proto.c:955
> > #12 0x809a9aec in ieee80211_sta_join1 ()
> > at /usr/src/sys/net80211/ieee80211_node.c:741
> > #13 0x8099047b in hostap_newstate (vap=0xf8000e8dd000,
> > nstate=, arg=)
> > at /usr/src/sys/net80211/ieee80211_hostap.c:274
> > #14 0x81a1a36a in run_newstate (vap=,
> > nstate=IEEE80211_S_RUN, arg=-1)
> > at /usr/src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c:1881
> > #15 0x809b2edf in ieee80211_newstate_cb (xvap=0xf8000e8dd000,
> > npending=)
> > at /usr/src/sys/net80211/ieee80211_proto.c:1756
> > #16 0x808f5b66 in taskqueue_run_locked (queue=0xf8000e8e4600)
> > at /usr/src/sys/kern/subr_taskqueue.c:333
> > #17 0x808f63e8 in taskqueue_thread_loop (arg= out>)
> > at /usr/src/sys/kern/subr_taskqueue.c:535
> > #18 0x8088198a in fork_exit (
> > callout=0x808f6340 ,
> > arg=0xfeff60f0, frame=0xfe009695fc00)
> > at /usr/src/sys/kern/kern_fork.c:995
> > #19 0x80c758ce in fork_trampoline ()
> > at /usr/src/sys/amd64/amd64/exception.S:606
> > #20 0x in ?? ()
> >
> > frame 0
> > #0 doadump (textdump=) at pcpu.h:219
> > 219 pcpu.h: No such file or directory.
> > in pcpu.h
> > print doadump
> > $1 = {int (boolean_t)} 0x808af6f0
> >
> > frame 1:
> > #1 0x808af530 in kern_reboot (howto=260)
> > at /usr/src/sys/kern/kern_shutdown.c:447
> > 447 doadump(TRUE);
> > print kern_reboot
> > print kern_reboot
> > $3 = {void (int)} 0x808aedf0
> >
> > frame 2
> > #2 0x808af8f4 in panic (fmt=)
> > at /usr/src/sys/kern/kern_shutdown.c:754
> > 754 kern_reboot(bootopt);
> > (kgdb) print panic
> > $4 = {void (const char *)} 0x808af760
> >
> > frame 3
> > #3 0x80c8e692 in trap_fatal (frame=,
> > eva=) at /usr/src/sys/amd64/amd64/trap.c:882
> > 882 panic("%s", trap_msg[type]);
> > (kgdb) print trap_fatal
> > $5 = {void (struct trapframe *, vm_offset_t)} 0x80c8e2f0
> >
> > (kgdb) frame 4
> > #4 0x80c8e969 in trap_pfault (frame=0xfe009695f720,
> usermode=0)
> > at /usr/src/sys/amd64/amd64/trap.c:699
> > 699 trap_fatal(frame, eva);
> > (kgdb) print trap_pfault
> > $6 = {int (struct trapframe *, int)} 0x80c8e6a0
> > (kgdb) frame 5
> > #5 0x80c8e0f6 in trap (frame=0xfe009695f720)
> > at /usr/src/sys/amd64/amd64/trap.c:463
> > 463 (void) trap_pfault(frame, FALSE);
> > (kgdb) print trap
> > $7 = {void (struct trapframe *)} 0x80c8db10
> >
> > frame 6
> > #6 0x80c75392 in calltrap ()
> > at /usr/src/sys/amd64/amd64/exception.S:232
> > 232 call trap
> > Current language: auto; currently asm
> > (kgdb) print calltrap
> > $8 = {} 0x80c7538a
> > (kgdb) frame 7
> > #7 0x809b1163 in ieee8021
Re: FreeBSD 10.0: hostapd crash with Ralink 3070
Right, frame 8 (the run beacon update) is passing a NULL mbuf into
net80211. Why's it doing that.
-a
On 28 January 2014 15:02, Pedro Flynn wrote:
> Here we go (this output is not beautiful...). Please, let me know if I
> missed something or if I did something wrong:
>
> bt output:
>
> #0 doadump (textdump=) at pcpu.h:219
> #1 0x808af530 in kern_reboot (howto=260)
> at /usr/src/sys/kern/kern_shutdown.c:447
> #2 0x808af8f4 in panic (fmt=)
> at /usr/src/sys/kern/kern_shutdown.c:754
> #3 0x80c8e692 in trap_fatal (frame=,
> eva=) at /usr/src/sys/amd64/amd64/trap.c:882
> #4 0x80c8e969 in trap_pfault (frame=0xfe009695f720, usermode=0)
> at /usr/src/sys/amd64/amd64/trap.c:699
> #5 0x80c8e0f6 in trap (frame=0xfe009695f720)
> at /usr/src/sys/amd64/amd64/trap.c:463
> #6 0x80c75392 in calltrap ()
> at /usr/src/sys/amd64/amd64/exception.S:232
> #7 0x809b1163 in ieee80211_beacon_update (ni=0xfeffc000,
> bo=0xf8000e8dd9e8, m=0x0, mcast=0) at atomic.h:161
> #8 0x81a198bc in run_update_beacon (vap=0xf8000e8dd000, item=2)
> at /usr/src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c:3974
> #9 0x809b42bd in ieee80211_wme_updateparams_locked (
> vap=0xf8000e8dd000) at ieee80211_var.h:814
> #10 0x809b437a in ieee80211_wme_updateparams
> (vap=0xf8000e8dd000)
> at /usr/src/sys/net80211/ieee80211_proto.c:1150
> #11 0x809b3f43 in ieee80211_wme_initparams (vap= out>)
> at /usr/src/sys/net80211/ieee80211_proto.c:955
> #12 0x809a9aec in ieee80211_sta_join1 ()
> at /usr/src/sys/net80211/ieee80211_node.c:741
> #13 0x8099047b in hostap_newstate (vap=0xf8000e8dd000,
> nstate=, arg=)
> at /usr/src/sys/net80211/ieee80211_hostap.c:274
> #14 0x81a1a36a in run_newstate (vap=,
> nstate=IEEE80211_S_RUN, arg=-1)
> at /usr/src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c:1881
> #15 0x809b2edf in ieee80211_newstate_cb (xvap=0xf8000e8dd000,
> npending=)
> at /usr/src/sys/net80211/ieee80211_proto.c:1756
> #16 0x808f5b66 in taskqueue_run_locked (queue=0xf8000e8e4600)
> at /usr/src/sys/kern/subr_taskqueue.c:333
> #17 0x808f63e8 in taskqueue_thread_loop (arg=)
> at /usr/src/sys/kern/subr_taskqueue.c:535
> #18 0x8088198a in fork_exit (
> callout=0x808f6340 ,
> arg=0xfeff60f0, frame=0xfe009695fc00)
> at /usr/src/sys/kern/kern_fork.c:995
> #19 0x80c758ce in fork_trampoline ()
> at /usr/src/sys/amd64/amd64/exception.S:606
> #20 0x in ?? ()
>
> frame 0
> #0 doadump (textdump=) at pcpu.h:219
> 219 pcpu.h: No such file or directory.
> in pcpu.h
> print doadump
> $1 = {int (boolean_t)} 0x808af6f0
>
> frame 1:
> #1 0x808af530 in kern_reboot (howto=260)
> at /usr/src/sys/kern/kern_shutdown.c:447
> 447 doadump(TRUE);
> print kern_reboot
> print kern_reboot
> $3 = {void (int)} 0x808aedf0
>
> frame 2
> #2 0x808af8f4 in panic (fmt=)
> at /usr/src/sys/kern/kern_shutdown.c:754
> 754 kern_reboot(bootopt);
> (kgdb) print panic
> $4 = {void (const char *)} 0x808af760
>
> frame 3
> #3 0x80c8e692 in trap_fatal (frame=,
> eva=) at /usr/src/sys/amd64/amd64/trap.c:882
> 882 panic("%s", trap_msg[type]);
> (kgdb) print trap_fatal
> $5 = {void (struct trapframe *, vm_offset_t)} 0x80c8e2f0
>
> (kgdb) frame 4
> #4 0x80c8e969 in trap_pfault (frame=0xfe009695f720, usermode=0)
> at /usr/src/sys/amd64/amd64/trap.c:699
> 699 trap_fatal(frame, eva);
> (kgdb) print trap_pfault
> $6 = {int (struct trapframe *, int)} 0x80c8e6a0
> (kgdb) frame 5
> #5 0x80c8e0f6 in trap (frame=0xfe009695f720)
> at /usr/src/sys/amd64/amd64/trap.c:463
> 463 (void) trap_pfault(frame, FALSE);
> (kgdb) print trap
> $7 = {void (struct trapframe *)} 0x80c8db10
>
> frame 6
> #6 0x80c75392 in calltrap ()
> at /usr/src/sys/amd64/amd64/exception.S:232
> 232 call trap
> Current language: auto; currently asm
> (kgdb) print calltrap
> $8 = {} 0x80c7538a
> (kgdb) frame 7
> #7 0x809b1163 in ieee80211_beacon_update (ni=0xfeffc000,
> bo=0xf8000e8dd9e8, m=0x0, mcast=0) at atomic.h:161
> 161 atomic.h: No such file or directory.
> in atomic.h
> Current language: auto; currently minimal
> (kgdb) print ieee80211_beacon_update
> $9 = {int (struct ieee80211_node *, struct ieee80211_beacon_offsets *,
> struct mbuf *, int)} 0x809b1090
>
> frame 8
> #8 0x81a198bc in run_update_beacon (vap=0xf8000e8dd000, item=2)
> at /usr/src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c:3974
> 3974 ieee80211_beacon_update(vap->iv_bss, &rvp->bo, rvp->beacon_mbuf,
> mcast);
> (kgdb) print run_update_beacon
> $10 = {void (struct ieee80211vap *,
> int)} 0x81a19750
> (kgdb) frame 9
> #9
Re: FreeBSD 10.0: hostapd crash with Ralink 3070
Here we go (this output is not beautiful...). Please, let me know if I
missed something or if I did something wrong:
bt output:
#0 doadump (textdump=) at pcpu.h:219
#1 0x808af530 in kern_reboot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:447
#2 0x808af8f4 in panic (fmt=)
at /usr/src/sys/kern/kern_shutdown.c:754
#3 0x80c8e692 in trap_fatal (frame=,
eva=) at /usr/src/sys/amd64/amd64/trap.c:882
#4 0x80c8e969 in trap_pfault (frame=0xfe009695f720, usermode=0)
at /usr/src/sys/amd64/amd64/trap.c:699
#5 0x80c8e0f6 in trap (frame=0xfe009695f720)
at /usr/src/sys/amd64/amd64/trap.c:463
#6 0x80c75392 in calltrap ()
at /usr/src/sys/amd64/amd64/exception.S:232
#7 0x809b1163 in ieee80211_beacon_update (ni=0xfeffc000,
bo=0xf8000e8dd9e8, m=0x0, mcast=0) at atomic.h:161
#8 0x81a198bc in run_update_beacon (vap=0xf8000e8dd000, item=2)
at /usr/src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c:3974
#9 0x809b42bd in ieee80211_wme_updateparams_locked (
vap=0xf8000e8dd000) at ieee80211_var.h:814
#10 0x809b437a in ieee80211_wme_updateparams
(vap=0xf8000e8dd000)
at /usr/src/sys/net80211/ieee80211_proto.c:1150
#11 0x809b3f43 in ieee80211_wme_initparams (vap=)
at /usr/src/sys/net80211/ieee80211_proto.c:955
#12 0x809a9aec in ieee80211_sta_join1 ()
at /usr/src/sys/net80211/ieee80211_node.c:741
#13 0x8099047b in hostap_newstate (vap=0xf8000e8dd000,
nstate=, arg=)
at /usr/src/sys/net80211/ieee80211_hostap.c:274
#14 0x81a1a36a in run_newstate (vap=,
nstate=IEEE80211_S_RUN, arg=-1)
at /usr/src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c:1881
#15 0x809b2edf in ieee80211_newstate_cb (xvap=0xf8000e8dd000,
npending=)
at /usr/src/sys/net80211/ieee80211_proto.c:1756
#16 0x808f5b66 in taskqueue_run_locked (queue=0xf8000e8e4600)
at /usr/src/sys/kern/subr_taskqueue.c:333
#17 0x808f63e8 in taskqueue_thread_loop (arg=)
at /usr/src/sys/kern/subr_taskqueue.c:535
#18 0x8088198a in fork_exit (
callout=0x808f6340 ,
arg=0xfeff60f0, frame=0xfe009695fc00)
at /usr/src/sys/kern/kern_fork.c:995
#19 0x80c758ce in fork_trampoline ()
at /usr/src/sys/amd64/amd64/exception.S:606
#20 0x in ?? ()
frame 0
#0 doadump (textdump=) at pcpu.h:219
219 pcpu.h: No such file or directory.
in pcpu.h
print doadump
$1 = {int (boolean_t)} 0x808af6f0
frame 1:
#1 0x808af530 in kern_reboot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:447
447 doadump(TRUE);
print kern_reboot
print kern_reboot
$3 = {void (int)} 0x808aedf0
frame 2
#2 0x808af8f4 in panic (fmt=)
at /usr/src/sys/kern/kern_shutdown.c:754
754 kern_reboot(bootopt);
(kgdb) print panic
$4 = {void (const char *)} 0x808af760
frame 3
#3 0x80c8e692 in trap_fatal (frame=,
eva=) at /usr/src/sys/amd64/amd64/trap.c:882
882 panic("%s", trap_msg[type]);
(kgdb) print trap_fatal
$5 = {void (struct trapframe *, vm_offset_t)} 0x80c8e2f0
(kgdb) frame 4
#4 0x80c8e969 in trap_pfault (frame=0xfe009695f720, usermode=0)
at /usr/src/sys/amd64/amd64/trap.c:699
699 trap_fatal(frame, eva);
(kgdb) print trap_pfault
$6 = {int (struct trapframe *, int)} 0x80c8e6a0
(kgdb) frame 5
#5 0x80c8e0f6 in trap (frame=0xfe009695f720)
at /usr/src/sys/amd64/amd64/trap.c:463
463 (void) trap_pfault(frame, FALSE);
(kgdb) print trap
$7 = {void (struct trapframe *)} 0x80c8db10
frame 6
#6 0x80c75392 in calltrap ()
at /usr/src/sys/amd64/amd64/exception.S:232
232 call trap
Current language: auto; currently asm
(kgdb) print calltrap
$8 = {} 0x80c7538a
(kgdb) frame 7
#7 0x809b1163 in ieee80211_beacon_update (ni=0xfeffc000,
bo=0xf8000e8dd9e8, m=0x0, mcast=0) at atomic.h:161
161 atomic.h: No such file or directory.
in atomic.h
Current language: auto; currently minimal
(kgdb) print ieee80211_beacon_update
$9 = {int (struct ieee80211_node *, struct ieee80211_beacon_offsets *,
struct mbuf *, int)} 0x809b1090
frame 8
#8 0x81a198bc in run_update_beacon (vap=0xf8000e8dd000, item=2)
at /usr/src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c:3974
3974 ieee80211_beacon_update(vap->iv_bss, &rvp->bo, rvp->beacon_mbuf,
mcast);
(kgdb) print run_update_beacon
$10 = {void (struct ieee80211vap *,
int)} 0x81a19750
(kgdb) frame 9
#9 0x809b42bd in ieee80211_wme_updateparams_locked (
vap=0xf8000e8dd000) at ieee80211_var.h:814
814 vap->iv_update_beacon(vap, what);
(kgdb) print ieee80211_wme_updateparams_locked
$11 = {void (struct ieee80211vap
*)} 0x809b3f90
(kgdb) frame 10
#10 0x809b437a in ieee80211_wme_updateparams
(vap=0xf8000e8dd000)
at /usr/src/sys/net80211/ieee80211_pr
Re: FreeBSD 10.0: hostapd crash with Ralink 3070
ok, do 'bt', and see what's being passed into ieee80211_beacon_update. Use 'frame X' to switch to frame X, and 'print VARIABLE_NAME' to print out the contents of the given variable name. That mbuf looks like it's NULL, which is odd. Thanks! -a On 28 January 2014 14:45, Pedro Flynn wrote: > OK! This is what I have: > > list * (0x809b1163) > Undefined command: "". Try "help". > (kgdb) list * (0x809b1163) > 0x809b1163 is in ieee80211_beacon_update > (/usr/src/sys/net80211/ieee80211_output.c:3099). > 3094 /* XXX do WME aggressive mode processing? */ > 3095 IEEE80211_UNLOCK(ic); > 3096 return 1; /* just assume length changed */ > 3097 } > 3098 > 3099 wh = mtod(m, struct ieee80211_frame *); > 3100 seqno = ni->ni_txseqs[IEEE80211_NONQOS_TID]++; > 3101 *(uint16_t *)&wh->i_seq[0] = > 3102 htole16(seqno << IEEE80211_SEQ_SEQ_SHIFT); > 3103 M_SEQNO_SET(m, seqno); > Current language: auto; currently minimal > (kgdb) > > > (by the way, I'm building a kernel with debug symbols) > > Thanks, > > pflynn > > > > On Tue, Jan 28, 2014 at 8:34 PM, Adrian Chadd wrote: >> >> Ok, fire up kgdb >> >> # kgdb /boot/kernel/kernel /var/crash/vmcore.0 >> >> then >> >> (gdb) list * (0x809b1163) >> >> (.. that's the "instruction pointer" at the time of the panic.) >> >> I bet it's iv_bss. >> >> >> >> -a > > ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: FreeBSD 10.0: hostapd crash with Ralink 3070
OK! This is what I have: list * (0x809b1163) Undefined command: "". Try "help". (kgdb) list * (0x809b1163) 0x809b1163 is in ieee80211_beacon_update (/usr/src/sys/net80211/ieee80211_output.c:3099). 3094 /* XXX do WME aggressive mode processing? */ 3095 IEEE80211_UNLOCK(ic); 3096 return 1; /* just assume length changed */ 3097 } 3098 3099 wh = mtod(m, struct ieee80211_frame *); 3100 seqno = ni->ni_txseqs[IEEE80211_NONQOS_TID]++; 3101 *(uint16_t *)&wh->i_seq[0] = 3102 htole16(seqno << IEEE80211_SEQ_SEQ_SHIFT); 3103 M_SEQNO_SET(m, seqno); Current language: auto; currently minimal (kgdb) (by the way, I'm building a kernel with debug symbols) Thanks, pflynn On Tue, Jan 28, 2014 at 8:34 PM, Adrian Chadd wrote: > Ok, fire up kgdb > > # kgdb /boot/kernel/kernel /var/crash/vmcore.0 > > then > > (gdb) list * (0x809b1163) > > (.. that's the "instruction pointer" at the time of the panic.) > > I bet it's iv_bss. > > > > -a > ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: FreeBSD 10.0: hostapd crash with Ralink 3070
Ok, fire up kgdb # kgdb /boot/kernel/kernel /var/crash/vmcore.0 then (gdb) list * (0x809b1163) (.. that's the "instruction pointer" at the time of the panic.) I bet it's iv_bss. -a ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: FreeBSD 10.0: hostapd crash with Ralink 3070
Hi Adrian. Yes. There is a core.txt.0 file. I uploaded it to the folder. Thanks! pflynn On Tue, Jan 28, 2014 at 8:23 PM, Adrian Chadd wrote: > Hi, > > Did it create a crash .txt file? If so, that's mostly enough to go on. > Can you just attach that to a post to the mailing list? > > > -a > > > On 28 January 2014 13:26, Pedro Flynn wrote: > > Hi! > > > > I generated the crash dump and uploaded the image to a public folder on > > Google Drive. This is the link to the folder: > > > > > https://drive.google.com/folderview?id=0B0sVwxI7RI7oc3R2bjVQR0pXWG8&usp=sharing > > > > the image is xz compressed and the uncompressed size is 161 MB. I also > put > > the uname -a output in the file uname-a.output. This is the uname -a: > > > > FreeBSD wormhole2 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Thu Jan > > 16 22:34:59 UTC 2014 r...@snap.freebsd.org: > /usr/obj/usr/src/sys/GENERIC > > amd64 > > > > Hope this dump will have some information. I can build a kernel with > debug > > symbols if one think more information is better. > > > > Thanks, > > > > pflynn > > > > > > On Tue, Jan 28, 2014 at 2:21 PM, Pedro Flynn > wrote: > > > >> Hi Adrian, > >> > >> This morning I installed 10.0-RELEASE on a second machine (I had to > >> rollback my router to 9.2) with the same hardware with dumpdev set to > YES > >> in rc.conf. I will generate the crashdump as soon as I get home. > >> > >> Thanks, > >> > >> pflynn > >> > >> > >> On Tue, Jan 28, 2014 at 2:11 PM, Adrian Chadd > wrote: > >> > >>> Do you get a crashdump that you can feed into kgdb upon reboot? If > >>> not, would you mind enabling crashdumps? > >>> > >>> > >>> > >>> -a > >>> > >>> > >>> On 28 January 2014 02:57, Pedro Flynn wrote: > >>> > (sorry - this reply was sent only to Hiren. Here is it for the list) > >>> > > >>> > > >>> > Hi Hiren, > >>> > > >>> > this is what I get immediately after starting hostapd - via "service > >>> > hostapd onestart", since I need to do it manually as the system will > >>> reboot > >>> > in loop if I enable > >>> > hostapd in rc.conf): > >>> > > >>> > KDB: stack backtrace > >>> > #0 0x808e7dd0 at kbd_backtrace+0x60 > >>> > #1 0x808af8b5 at panic+0x115 > >>> > #2 0x80c8e692 at trap_fatal+0x3a2 > >>> > #3 0x80c8e969 at trap_pfault+0x2c9 > >>> > #4 0x80c8e0f6 at trap+0x5e6 > >>> > #5 0x80c75392 at calltrap+0x8 > >>> > #6 0x81a158bc at run_update_beacon+0x16c > >>> > #7 0x809b42bd at ieee80211_wme_update_params_locked+0x32d > >>> > #8 0x809b437a at ieee80211_wme_update_params+0x5a > >>> > #9 0x809bb3f43 at ieee80211_wme_init_params+0x2a3 > >>> > #10 0x809a9aec at ieee80211_sta_join1+0xdc > >>> > #11 0x8099047b at hostap_newstate+0x2eb > >>> > #12 0x81a1636a at run_newstate+0x83a > >>> > #13 0x809b2edf at ieee80211_newstate_cb+0x14f > >>> > #14 0x808f5b66 at taskqueue_run_locked+0xe6 > >>> > #15 0x808f63e8 at taskqueue_thread_loop+0xa8 > >>> > #16 0x8088198a at fork_exit+0x9a > >>> > #17 0x80c758ce at fork_trampoline+0xe > >>> > Uptime: 45 s > >>> > Automatic reboot in 15 seconds - press a key on the console to abort > >>> > --> Press a key on the console to reboot, > >>> > --> or switch off the station now. > >>> > > >>> > Thanks for any help or suggestion. > >>> > > >>> > pflynn > >>> > > >>> > > >>> > On Mon, Jan 27, 2014 at 8:43 PM, hiren panchasara < > >>> > hiren.panchas...@gmail.com> wrote: > >>> > > >>> >> On Mon, Jan 27, 2014 at 2:16 PM, Pedro Flynn > > >>> >> wrote: > >>> >> > >>> >> > I can provide information as needed. > >>> >> > >>> >> Sharing lots of kernel debug messages that you are seeing might be a > >>> >> good start :-) > >>> >> > >>> >> cheers, > >>> >> Hiren > >>> >> > >>> > ___ > >>> > freebsd-wireless@freebsd.org mailing list > >>> > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > >>> > To unsubscribe, send any mail to " > >>> freebsd-wireless-unsubscr...@freebsd.org" > >>> > >> > >> > >> > > ___ > > freebsd-wireless@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > > To unsubscribe, send any mail to " > freebsd-wireless-unsubscr...@freebsd.org" > ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: FreeBSD 10.0: hostapd crash with Ralink 3070
Hi, Did it create a crash .txt file? If so, that's mostly enough to go on. Can you just attach that to a post to the mailing list? -a On 28 January 2014 13:26, Pedro Flynn wrote: > Hi! > > I generated the crash dump and uploaded the image to a public folder on > Google Drive. This is the link to the folder: > > https://drive.google.com/folderview?id=0B0sVwxI7RI7oc3R2bjVQR0pXWG8&usp=sharing > > the image is xz compressed and the uncompressed size is 161 MB. I also put > the uname -a output in the file uname-a.output. This is the uname -a: > > FreeBSD wormhole2 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Thu Jan > 16 22:34:59 UTC 2014 r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC > amd64 > > Hope this dump will have some information. I can build a kernel with debug > symbols if one think more information is better. > > Thanks, > > pflynn > > > On Tue, Jan 28, 2014 at 2:21 PM, Pedro Flynn wrote: > >> Hi Adrian, >> >> This morning I installed 10.0-RELEASE on a second machine (I had to >> rollback my router to 9.2) with the same hardware with dumpdev set to YES >> in rc.conf. I will generate the crashdump as soon as I get home. >> >> Thanks, >> >> pflynn >> >> >> On Tue, Jan 28, 2014 at 2:11 PM, Adrian Chadd wrote: >> >>> Do you get a crashdump that you can feed into kgdb upon reboot? If >>> not, would you mind enabling crashdumps? >>> >>> >>> >>> -a >>> >>> >>> On 28 January 2014 02:57, Pedro Flynn wrote: >>> > (sorry - this reply was sent only to Hiren. Here is it for the list) >>> > >>> > >>> > Hi Hiren, >>> > >>> > this is what I get immediately after starting hostapd - via "service >>> > hostapd onestart", since I need to do it manually as the system will >>> reboot >>> > in loop if I enable >>> > hostapd in rc.conf): >>> > >>> > KDB: stack backtrace >>> > #0 0x808e7dd0 at kbd_backtrace+0x60 >>> > #1 0x808af8b5 at panic+0x115 >>> > #2 0x80c8e692 at trap_fatal+0x3a2 >>> > #3 0x80c8e969 at trap_pfault+0x2c9 >>> > #4 0x80c8e0f6 at trap+0x5e6 >>> > #5 0x80c75392 at calltrap+0x8 >>> > #6 0x81a158bc at run_update_beacon+0x16c >>> > #7 0x809b42bd at ieee80211_wme_update_params_locked+0x32d >>> > #8 0x809b437a at ieee80211_wme_update_params+0x5a >>> > #9 0x809bb3f43 at ieee80211_wme_init_params+0x2a3 >>> > #10 0x809a9aec at ieee80211_sta_join1+0xdc >>> > #11 0x8099047b at hostap_newstate+0x2eb >>> > #12 0x81a1636a at run_newstate+0x83a >>> > #13 0x809b2edf at ieee80211_newstate_cb+0x14f >>> > #14 0x808f5b66 at taskqueue_run_locked+0xe6 >>> > #15 0x808f63e8 at taskqueue_thread_loop+0xa8 >>> > #16 0x8088198a at fork_exit+0x9a >>> > #17 0x80c758ce at fork_trampoline+0xe >>> > Uptime: 45 s >>> > Automatic reboot in 15 seconds - press a key on the console to abort >>> > --> Press a key on the console to reboot, >>> > --> or switch off the station now. >>> > >>> > Thanks for any help or suggestion. >>> > >>> > pflynn >>> > >>> > >>> > On Mon, Jan 27, 2014 at 8:43 PM, hiren panchasara < >>> > hiren.panchas...@gmail.com> wrote: >>> > >>> >> On Mon, Jan 27, 2014 at 2:16 PM, Pedro Flynn >>> >> wrote: >>> >> >>> >> > I can provide information as needed. >>> >> >>> >> Sharing lots of kernel debug messages that you are seeing might be a >>> >> good start :-) >>> >> >>> >> cheers, >>> >> Hiren >>> >> >>> > ___ >>> > freebsd-wireless@freebsd.org mailing list >>> > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >>> > To unsubscribe, send any mail to " >>> freebsd-wireless-unsubscr...@freebsd.org" >>> >> >> >> > ___ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org" ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: FreeBSD 10.0: hostapd crash with Ralink 3070
Hi! I generated the crash dump and uploaded the image to a public folder on Google Drive. This is the link to the folder: https://drive.google.com/folderview?id=0B0sVwxI7RI7oc3R2bjVQR0pXWG8&usp=sharing the image is xz compressed and the uncompressed size is 161 MB. I also put the uname -a output in the file uname-a.output. This is the uname -a: FreeBSD wormhole2 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Thu Jan 16 22:34:59 UTC 2014 r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 Hope this dump will have some information. I can build a kernel with debug symbols if one think more information is better. Thanks, pflynn On Tue, Jan 28, 2014 at 2:21 PM, Pedro Flynn wrote: > Hi Adrian, > > This morning I installed 10.0-RELEASE on a second machine (I had to > rollback my router to 9.2) with the same hardware with dumpdev set to YES > in rc.conf. I will generate the crashdump as soon as I get home. > > Thanks, > > pflynn > > > On Tue, Jan 28, 2014 at 2:11 PM, Adrian Chadd wrote: > >> Do you get a crashdump that you can feed into kgdb upon reboot? If >> not, would you mind enabling crashdumps? >> >> >> >> -a >> >> >> On 28 January 2014 02:57, Pedro Flynn wrote: >> > (sorry - this reply was sent only to Hiren. Here is it for the list) >> > >> > >> > Hi Hiren, >> > >> > this is what I get immediately after starting hostapd - via "service >> > hostapd onestart", since I need to do it manually as the system will >> reboot >> > in loop if I enable >> > hostapd in rc.conf): >> > >> > KDB: stack backtrace >> > #0 0x808e7dd0 at kbd_backtrace+0x60 >> > #1 0x808af8b5 at panic+0x115 >> > #2 0x80c8e692 at trap_fatal+0x3a2 >> > #3 0x80c8e969 at trap_pfault+0x2c9 >> > #4 0x80c8e0f6 at trap+0x5e6 >> > #5 0x80c75392 at calltrap+0x8 >> > #6 0x81a158bc at run_update_beacon+0x16c >> > #7 0x809b42bd at ieee80211_wme_update_params_locked+0x32d >> > #8 0x809b437a at ieee80211_wme_update_params+0x5a >> > #9 0x809bb3f43 at ieee80211_wme_init_params+0x2a3 >> > #10 0x809a9aec at ieee80211_sta_join1+0xdc >> > #11 0x8099047b at hostap_newstate+0x2eb >> > #12 0x81a1636a at run_newstate+0x83a >> > #13 0x809b2edf at ieee80211_newstate_cb+0x14f >> > #14 0x808f5b66 at taskqueue_run_locked+0xe6 >> > #15 0x808f63e8 at taskqueue_thread_loop+0xa8 >> > #16 0x8088198a at fork_exit+0x9a >> > #17 0x80c758ce at fork_trampoline+0xe >> > Uptime: 45 s >> > Automatic reboot in 15 seconds - press a key on the console to abort >> > --> Press a key on the console to reboot, >> > --> or switch off the station now. >> > >> > Thanks for any help or suggestion. >> > >> > pflynn >> > >> > >> > On Mon, Jan 27, 2014 at 8:43 PM, hiren panchasara < >> > hiren.panchas...@gmail.com> wrote: >> > >> >> On Mon, Jan 27, 2014 at 2:16 PM, Pedro Flynn >> >> wrote: >> >> >> >> > I can provide information as needed. >> >> >> >> Sharing lots of kernel debug messages that you are seeing might be a >> >> good start :-) >> >> >> >> cheers, >> >> Hiren >> >> >> > ___ >> > freebsd-wireless@freebsd.org mailing list >> > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> > To unsubscribe, send any mail to " >> freebsd-wireless-unsubscr...@freebsd.org" >> > > > ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Fwd: FreeBSD 10.0: hostapd crash with Ralink 3070
Hi Adrian, This morning I installed 10.0-RELEASE on a second machine (I had to rollback my router to 9.2) with the same hardware with dumpdev set to YES in rc.conf. I will generate the crashdump as soon as I get home. Thanks, pflynn On Tue, Jan 28, 2014 at 2:11 PM, Adrian Chadd wrote: > Do you get a crashdump that you can feed into kgdb upon reboot? If > not, would you mind enabling crashdumps? > > > > -a > > > On 28 January 2014 02:57, Pedro Flynn wrote: > > (sorry - this reply was sent only to Hiren. Here is it for the list) > > > > > > Hi Hiren, > > > > this is what I get immediately after starting hostapd - via "service > > hostapd onestart", since I need to do it manually as the system will > reboot > > in loop if I enable > > hostapd in rc.conf): > > > > KDB: stack backtrace > > #0 0x808e7dd0 at kbd_backtrace+0x60 > > #1 0x808af8b5 at panic+0x115 > > #2 0x80c8e692 at trap_fatal+0x3a2 > > #3 0x80c8e969 at trap_pfault+0x2c9 > > #4 0x80c8e0f6 at trap+0x5e6 > > #5 0x80c75392 at calltrap+0x8 > > #6 0x81a158bc at run_update_beacon+0x16c > > #7 0x809b42bd at ieee80211_wme_update_params_locked+0x32d > > #8 0x809b437a at ieee80211_wme_update_params+0x5a > > #9 0x809bb3f43 at ieee80211_wme_init_params+0x2a3 > > #10 0x809a9aec at ieee80211_sta_join1+0xdc > > #11 0x8099047b at hostap_newstate+0x2eb > > #12 0x81a1636a at run_newstate+0x83a > > #13 0x809b2edf at ieee80211_newstate_cb+0x14f > > #14 0x808f5b66 at taskqueue_run_locked+0xe6 > > #15 0x808f63e8 at taskqueue_thread_loop+0xa8 > > #16 0x8088198a at fork_exit+0x9a > > #17 0x80c758ce at fork_trampoline+0xe > > Uptime: 45 s > > Automatic reboot in 15 seconds - press a key on the console to abort > > --> Press a key on the console to reboot, > > --> or switch off the station now. > > > > Thanks for any help or suggestion. > > > > pflynn > > > > > > On Mon, Jan 27, 2014 at 8:43 PM, hiren panchasara < > > hiren.panchas...@gmail.com> wrote: > > > >> On Mon, Jan 27, 2014 at 2:16 PM, Pedro Flynn > >> wrote: > >> > >> > I can provide information as needed. > >> > >> Sharing lots of kernel debug messages that you are seeing might be a > >> good start :-) > >> > >> cheers, > >> Hiren > >> > > ___ > > freebsd-wireless@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > > To unsubscribe, send any mail to " > freebsd-wireless-unsubscr...@freebsd.org" > ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: FreeBSD 10.0: hostapd crash with Ralink 3070
Do you get a crashdump that you can feed into kgdb upon reboot? If not, would you mind enabling crashdumps? -a On 28 January 2014 02:57, Pedro Flynn wrote: > (sorry - this reply was sent only to Hiren. Here is it for the list) > > > Hi Hiren, > > this is what I get immediately after starting hostapd - via "service > hostapd onestart", since I need to do it manually as the system will reboot > in loop if I enable > hostapd in rc.conf): > > KDB: stack backtrace > #0 0x808e7dd0 at kbd_backtrace+0x60 > #1 0x808af8b5 at panic+0x115 > #2 0x80c8e692 at trap_fatal+0x3a2 > #3 0x80c8e969 at trap_pfault+0x2c9 > #4 0x80c8e0f6 at trap+0x5e6 > #5 0x80c75392 at calltrap+0x8 > #6 0x81a158bc at run_update_beacon+0x16c > #7 0x809b42bd at ieee80211_wme_update_params_locked+0x32d > #8 0x809b437a at ieee80211_wme_update_params+0x5a > #9 0x809bb3f43 at ieee80211_wme_init_params+0x2a3 > #10 0x809a9aec at ieee80211_sta_join1+0xdc > #11 0x8099047b at hostap_newstate+0x2eb > #12 0x81a1636a at run_newstate+0x83a > #13 0x809b2edf at ieee80211_newstate_cb+0x14f > #14 0x808f5b66 at taskqueue_run_locked+0xe6 > #15 0x808f63e8 at taskqueue_thread_loop+0xa8 > #16 0x8088198a at fork_exit+0x9a > #17 0x80c758ce at fork_trampoline+0xe > Uptime: 45 s > Automatic reboot in 15 seconds - press a key on the console to abort > --> Press a key on the console to reboot, > --> or switch off the station now. > > Thanks for any help or suggestion. > > pflynn > > > On Mon, Jan 27, 2014 at 8:43 PM, hiren panchasara < > hiren.panchas...@gmail.com> wrote: > >> On Mon, Jan 27, 2014 at 2:16 PM, Pedro Flynn >> wrote: >> >> > I can provide information as needed. >> >> Sharing lots of kernel debug messages that you are seeing might be a >> good start :-) >> >> cheers, >> Hiren >> > ___ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org" ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Fwd: FreeBSD 10.0: hostapd crash with Ralink 3070
(sorry - this reply was sent only to Hiren. Here is it for the list) Hi Hiren, this is what I get immediately after starting hostapd - via "service hostapd onestart", since I need to do it manually as the system will reboot in loop if I enable hostapd in rc.conf): KDB: stack backtrace #0 0x808e7dd0 at kbd_backtrace+0x60 #1 0x808af8b5 at panic+0x115 #2 0x80c8e692 at trap_fatal+0x3a2 #3 0x80c8e969 at trap_pfault+0x2c9 #4 0x80c8e0f6 at trap+0x5e6 #5 0x80c75392 at calltrap+0x8 #6 0x81a158bc at run_update_beacon+0x16c #7 0x809b42bd at ieee80211_wme_update_params_locked+0x32d #8 0x809b437a at ieee80211_wme_update_params+0x5a #9 0x809bb3f43 at ieee80211_wme_init_params+0x2a3 #10 0x809a9aec at ieee80211_sta_join1+0xdc #11 0x8099047b at hostap_newstate+0x2eb #12 0x81a1636a at run_newstate+0x83a #13 0x809b2edf at ieee80211_newstate_cb+0x14f #14 0x808f5b66 at taskqueue_run_locked+0xe6 #15 0x808f63e8 at taskqueue_thread_loop+0xa8 #16 0x8088198a at fork_exit+0x9a #17 0x80c758ce at fork_trampoline+0xe Uptime: 45 s Automatic reboot in 15 seconds - press a key on the console to abort --> Press a key on the console to reboot, --> or switch off the station now. Thanks for any help or suggestion. pflynn On Mon, Jan 27, 2014 at 8:43 PM, hiren panchasara < hiren.panchas...@gmail.com> wrote: > On Mon, Jan 27, 2014 at 2:16 PM, Pedro Flynn > wrote: > > > I can provide information as needed. > > Sharing lots of kernel debug messages that you are seeing might be a > good start :-) > > cheers, > Hiren > ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
