odd behaviour on wireless on latest -head
hiya, there's something odd with the latest -head. it's not updating from 11b to 11n on 2GHz channels, which is very bleh. Does anyone else see it? ifconfig wlan0 shows 11b associated, not HT20 or HT40. but it /says/ it was associated: Mar 3 15:51:44 victoria kernel: wlan0: start running, 0 vaps running Mar 3 15:51:44 victoria kernel: wlan0: ieee80211_start_locked: up parent iwn0 Mar 3 15:51:44 victoria kernel: iwn0: iwn_read_firmware: ucode rev=0x09dd0401 Mar 3 15:51:44 victoria kernel: wlan0: start running, 1 vaps running Mar 3 15:51:44 victoria kernel: wlan0: ieee80211_new_state_locked: INIT -> SCAN (nrunning 0 nscanning 0) Mar 3 15:51:44 victoria kernel: wlan0: ieee80211_newstate_cb: INIT -> SCAN arg 0 Mar 3 15:51:44 victoria kernel: wlan0: sta_newstate: INIT -> SCAN (0) Mar 3 15:51:45 victoria kernel: wlan0: [e8:fc:af:94:fc:fc] station assoc via MLME Mar 3 15:51:45 victoria kernel: wlan0: [e8:fc:af:94:fc:fc] ieee80211_ht_node_init: called Mar 3 15:51:45 victoria kernel: wlan0: ieee80211_new_state_locked: SCAN -> AUTH (nrunning 0 nscanning 0) Mar 3 15:51:45 victoria kernel: wlan0: ieee80211_newstate_cb: SCAN -> AUTH arg 192 Mar 3 15:51:45 victoria kernel: wlan0: sta_newstate: SCAN -> AUTH (192) Mar 3 15:51:45 victoria kernel: wlan0: ieee80211_new_state_locked: AUTH -> ASSOC (nrunning 0 nscanning 0) Mar 3 15:51:45 victoria kernel: wlan0: ieee80211_newstate_cb: AUTH -> ASSOC arg 0 Mar 3 15:51:45 victoria kernel: wlan0: sta_newstate: AUTH -> ASSOC (0) Mar 3 15:51:45 victoria kernel: wlan0: [e8:fc:af:94:fc:fc] assoc success at aid 11: long preamble, long slot time, QoS, HT20 (+AMPDU) Mar 3 15:51:45 victoria kernel: wlan0: ieee80211_new_state_locked: ASSOC -> RUN (nrunning 0 nscanning 0) Mar 3 15:51:45 victoria kernel: wlan0: ieee80211_newstate_cb: ASSOC -> RUN arg 16 Mar 3 15:51:45 victoria kernel: wlan0: sta_newstate: ASSOC -> RUN (16) Mar 3 15:51:45 victoria kernel: wlan0: link state changed to UP Mar 3 15:51:52 victoria dhclient: New IP Address (wlan0): 192.168.5.64 Mar 3 15:51:52 victoria dhclient: New Subnet Mask (wlan0): 255.255.0.0 Mar 3 15:51:52 victoria dhclient: New Broadcast Address (wlan0): 192.168.255.255 Mar 3 15:51:52 victoria dhclient: New Routers (wlan0): 192.168.1.1 ..the transmit rate is showing up as 11b, not 11b rates (sysctl dev.iwn.0.debug=0x1, and I can kinda read the plcp/rate values now ... sigh. :) Anyway, I know this used to work fine, so I'll have to go over the net80211 changes to see when they broke. 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"
iwm7265fw: fatal firmware error
Hi all, I recently acquired an ASUS Zenbook with Intel AC 7265 wireless. I'm mostly very happy with it, but a couple of times a day I see a "fatal firmware error" and lose association. I've attached my (grepped) dmesg... is there anything else I can do to help debug this issue? Thanks, Jon -- Jonathan Anderson jonat...@freebsd.orgPreloaded elf obj module "/boot/kernel/if_iwm.ko" at 0x825bca18. Preloaded elf obj module "/boot/kernel/iwm7265fw.ko" at 0x825bd000. firmware: 'iwm7265fw' version 0: 697828 bytes loaded at 0x8250a0b8 iwm0: mem 0xdf00-0xdf001fff at device 0.0 on pci1 iwm0: attempting to allocate 1 MSI vectors (1 supported) iwm0: using IRQ 266 for MSI random: harvesting attach, 8 bytes (4 bits) from iwm0 iwm0: revision: 0x210, firmware 25.228 (API ver. 9) iwm0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps iwm0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps iwm0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps iwm0: iwm_update_edca: called iwm0: iwm_update_edca: called iwm0: dumping device error log iwm0: Start IWL Error Log Dump: iwm0: Status: 0x3, count: 6 iwm0: 0x3001 | ADVANCED_SYSASSERT iwm0: 002002B1 | uPc iwm0: | branchlink1 iwm0: 0BA4 | branchlink2 iwm0: 000183B8 | interruptlink1 iwm0: 009050A7 | interruptlink2 iwm0: 0001 | data1 iwm0: | data2 iwm0: DEADBEEF | data3 iwm0: | beacon time iwm0: 0124E3A2 | tsf low iwm0: | tsf hi iwm0: | time gp1 iwm0: 0124E3A3 | time gp2 iwm0: | time gp3 iwm0: 000419E4 | uCode version iwm0: 0210 | hw version iwm0: 9000 | board version iwm0: 0923002B | hcmd iwm0: 00022080 | isr0 iwm0: 0100 | isr1 iwm0: 0002 | isr2 iwm0: 0041C080 | isr3 iwm0: 0001 | isr4 iwm0: 01000112 | isr_pref iwm0: | wait_event iwm0: 0080 | l2p_control iwm0: 0001 | l2p_duration iwm0: 003F | l2p_mhvalid iwm0: | l2p_addr_match iwm0: 0005 | lmpm_pmg_sel iwm0: 20111734 | timestamp iwm0: 8088 | flow_handler iwm0: driver status: iwm0: tx ring 0: qid=0 cur=1 queued=0 iwm0: tx ring 1: qid=1 cur=0 queued=0 iwm0: tx ring 2: qid=2 cur=0 queued=0 iwm0: tx ring 3: qid=3 cur=0 queued=0 iwm0: tx ring 4: qid=4 cur=0 queued=0 iwm0: tx ring 5: qid=5 cur=0 queued=0 iwm0: tx ring 6: qid=6 cur=0 queued=0 iwm0: tx ring 7: qid=7 cur=0 queued=0 iwm0: tx ring 8: qid=8 cur=0 queued=0 iwm0: tx ring 9: qid=9 cur=36 queued=0 iwm0: tx ring 10: qid=10 cur=0 queued=0 iwm0: tx ring 11: qid=11 cur=0 queued=0 iwm0: tx ring 12: qid=12 cur=0 queued=0 iwm0: tx ring 13: qid=13 cur=0 queued=0 iwm0: tx ring 14: qid=14 cur=0 queued=0 iwm0: tx ring 15: qid=15 cur=0 queued=0 iwm0: tx ring 16: qid=16 cur=0 queued=0 iwm0: tx ring 17: qid=17 cur=0 queued=0 iwm0: tx ring 18: qid=18 cur=0 queued=0 iwm0: tx ring 19: qid=19 cur=0 queued=0 iwm0: rx ring: cur=131 iwm0: 802.11 state 1 iwm0: fatal firmware error iwm0: iwm_auth: binding cmd iwm0: iwm_newstate: could not move to auth state: 35 iwm0: could not initiate scan iwm0: mem 0xdf00-0xdf001fff at device 0.0 on pci1 iwm0: revision: 0x210, firmware 25.228 (API ver. 9) iwm0: iwm_update_edca: called iwm0: iwm_update_edca: called iwm0: iwm_update_edca: called iwm0: iwm_update_edca: called iwm0: dumping device error log iwm0: Start IWL Error Log Dump: iwm0: Status: 0x3, count: 6 iwm0: 0x3001 | ADVANCED_SYSASSERT iwm0: 00A002B0 | uPc iwm0: | branchlink1 iwm0: 0BA4 | branchlink2 iwm0: 000183B8 | interruptlink1 iwm0: 00105027 | interruptlink2 iwm0: 0001 | data1 iwm0: | data2 iwm0: DEADBEEF | data3 iwm0: 003FAA59 | beacon time iwm0: 55A5 | tsf low iwm0: | tsf hi iwm0: | time gp1 iwm0: 55A6 | time gp2 iwm0: | time gp3 iwm0: 000419E4 | uCode version iwm0: 0210 | hw version iwm0: 9000 | board version iwm0: 091F002B | hcmd iwm0: 22E22081 | isr0 iwm0: | isr1 iwm0: 0002 | isr2 iwm0: 004004C0 | isr3 iwm0: 0001 | isr4 iwm0: 11002112 | isr_pref iwm0: | wait_event iwm0: 0080 | l2p_control iwm0: 00011420 | l2p_duration iwm0: 003F | l2p_mhvalid iwm0: 0080 | l2p_addr_match iwm0: 0005 | lmpm_pmg_sel iwm0: 20111734 | timestamp iwm0: 2028 | flow_handler iwm0: driver status: iwm0: tx ring 0: qid=0 cur=2 queued=2 iwm0: tx ring 1: qid=1 cur=0 queued=0 iwm0: tx ring 2: qid=2 cur=0 queued=0 iwm0: tx ring 3: qid=3 cur=0 queued=0 iwm0: tx ring 4: qid=4 cur=0 queued=0 iwm0: tx ring 5: qid=5 cur=0 queued=0 iwm0: tx ring 6: qid=6 cur=0 queued=0 iwm0: tx ring 7: qid=7 cur=0 queued=0 iwm0: tx ring 8: qid=8 cur=0 queued=0 iwm0: tx ring 9: qid=9 cur=32 queued=0 iwm0: tx ring 10: qid=10 cur=0 queued=0 iwm0: tx ring 11: qid=11 cur=0 queued=0 iwm0:
Re: iwm7265fw: fatal firmware error
It's a known problem. Someone has to fix the firmware api use. It's just wrong. Adrian On Mar 3, 2016 8:09 PM, "Jonathan Anderson" wrote: > Hi all, > > I recently acquired an ASUS Zenbook with Intel AC 7265 wireless. I'm > mostly very happy with it, but a couple of times a day I see a "fatal > firmware error" and lose association. I've attached my (grepped) dmesg... > is there anything else I can do to help debug this issue? > > Thanks, > > > Jon > -- > Jonathan Anderson > jonat...@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 > " > ___ 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: odd behaviour on wireless on latest -head
Rebooting it fixed it. I wonder if it's another manifestation of the interface mode flags getting set by the supplicant and not getting cleared and fixed later. Grr. Time to add more debugging. Adrian On Mar 3, 2016 3:53 PM, "Adrian Chadd" wrote: > hiya, > > there's something odd with the latest -head. it's not updating from > 11b to 11n on 2GHz channels, which is very bleh. > > Does anyone else see it? > > ifconfig wlan0 shows 11b associated, not HT20 or HT40. > > but it /says/ it was associated: > > Mar 3 15:51:44 victoria kernel: wlan0: start running, 0 vaps running > Mar 3 15:51:44 victoria kernel: wlan0: ieee80211_start_locked: up parent > iwn0 > Mar 3 15:51:44 victoria kernel: iwn0: iwn_read_firmware: ucode > rev=0x09dd0401 > Mar 3 15:51:44 victoria kernel: wlan0: start running, 1 vaps running > Mar 3 15:51:44 victoria kernel: wlan0: ieee80211_new_state_locked: > INIT -> SCAN (nrunning 0 nscanning 0) > Mar 3 15:51:44 victoria kernel: wlan0: ieee80211_newstate_cb: INIT -> > SCAN arg 0 > Mar 3 15:51:44 victoria kernel: wlan0: sta_newstate: INIT -> SCAN (0) > Mar 3 15:51:45 victoria kernel: wlan0: [e8:fc:af:94:fc:fc] station > assoc via MLME > Mar 3 15:51:45 victoria kernel: wlan0: [e8:fc:af:94:fc:fc] > ieee80211_ht_node_init: called > Mar 3 15:51:45 victoria kernel: wlan0: ieee80211_new_state_locked: > SCAN -> AUTH (nrunning 0 nscanning 0) > Mar 3 15:51:45 victoria kernel: wlan0: ieee80211_newstate_cb: SCAN -> > AUTH arg 192 > Mar 3 15:51:45 victoria kernel: wlan0: sta_newstate: SCAN -> AUTH (192) > Mar 3 15:51:45 victoria kernel: wlan0: ieee80211_new_state_locked: > AUTH -> ASSOC (nrunning 0 nscanning 0) > Mar 3 15:51:45 victoria kernel: wlan0: ieee80211_newstate_cb: AUTH -> > ASSOC arg 0 > Mar 3 15:51:45 victoria kernel: wlan0: sta_newstate: AUTH -> ASSOC (0) > Mar 3 15:51:45 victoria kernel: wlan0: [e8:fc:af:94:fc:fc] assoc > success at aid 11: long preamble, long slot time, QoS, HT20 (+AMPDU) > Mar 3 15:51:45 victoria kernel: wlan0: ieee80211_new_state_locked: > ASSOC -> RUN (nrunning 0 nscanning 0) > Mar 3 15:51:45 victoria kernel: wlan0: ieee80211_newstate_cb: ASSOC > -> RUN arg 16 > Mar 3 15:51:45 victoria kernel: wlan0: sta_newstate: ASSOC -> RUN (16) > Mar 3 15:51:45 victoria kernel: wlan0: link state changed to UP > Mar 3 15:51:52 victoria dhclient: New IP Address (wlan0): 192.168.5.64 > Mar 3 15:51:52 victoria dhclient: New Subnet Mask (wlan0): 255.255.0.0 > Mar 3 15:51:52 victoria dhclient: New Broadcast Address (wlan0): > 192.168.255.255 > Mar 3 15:51:52 victoria dhclient: New Routers (wlan0): 192.168.1.1 > > ..the transmit rate is showing up as 11b, not 11b rates (sysctl > dev.iwn.0.debug=0x1, and I can kinda read the plcp/rate values now ... > sigh. :) > > Anyway, I know this used to work fine, so I'll have to go over the > net80211 changes to see when they broke. > > 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"
[Bug 207445] net80211 Atheros AR938x: non-working WiFi hostap since ~ January
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207445 --- Comment #13 from ohart...@zedat.fu-berlin.de --- I tried to bisect, but the box is not the fastest, even compiling things with -DNO_CLEAN. @A. Chadd: I'll do as requested at the weekend and report the results back as soon as possible. -- You are receiving this mail because: You are the assignee for the bug. ___ 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"
