Re: iwn firmware sysassert
Ok, then I have no idea. There's active work on iwn going on in -HEAD. I suggest updating to that and then tracking development. No, I won't be backporting anything to -9 or -8; someone else will have to take charge of that (and field support queries when things don't work.) -adrian On 25 July 2013 16:38, Sean C. Farley s...@freebsd.org wrote: On Thu, 25 Jul 2013, Adrian Chadd wrote: Try jsut doing: ifconfig wlan0 create wlandev iwn0 wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf .. ie, don't do an ifconfig iwn0 up Same result. I ran with ifconfig_wlan0=WPA removed from /etc/rc.conf else wpa_supplicant would start: ifconfig wlan0 destroy ifconfig wlan0 create wlandev iwn0 wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf On 25 July 2013 15:25, Sean C. Farley s...@freebsd.org wrote: After upgrading my laptop from 8.4-STABLE to 9-STABLE, I have been unable to use the wireless NIC. The indicator light will flash for a moment and surrender. The error is always the same and reproducible with ifconfig iwn0 up. The system is 9-STABLE (r253048). This appears to be the same or similar to PR 175053: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/175053 Boot: iwn0: Intel Ultimate N WiFi Link 5300 mem 0xf800-0xf8001fff irq 17 at device 0.0 on pci4 Card details: iwn0@pci0:4:0:0:class=0x028000 card=0x11218086 chip=0x42358086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'Ultimate N WiFi Link 5300' class = network bar [10] = type Memory, range 64, base 0xf800, size 8192, enabled cap 01[c8] = powerspec 3 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message cap 10[e0] = PCI-Express 1 endpoint max data 128(128) FLR link x1(x1) speed 2.5(2.5) ASPM L1(L0s/L1) ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 corrected ecap 0003[140] = Serial 1 00216a985c6e Error (same each time except for time): wlan0: link state changed to UP iwn0: iwn_intr: fatal firmware error firmware error log: error type = SYSASSERT (0x0005) program counter = 0x3130 source line = 0x0585 error data = 0x0001 branch link = 0x312A312A interrupt link = 0x0916 time= 1611815765 driver status: tx ring 0: qid=0 cur=0 queued=0 tx ring 1: qid=1 cur=0 queued=0 tx ring 2: qid=2 cur=0 queued=0 tx ring 3: qid=3 cur=2 queued=0 tx ring 4: qid=4 cur=67 queued=0 tx ring 5: qid=5 cur=0 queued=0 tx ring 6: qid=6 cur=0 queued=0 tx ring 7: qid=7 cur=0 queued=0 tx ring 8: qid=8 cur=0 queued=0 tx ring 9: qid=9 cur=0 queued=0 tx ring 10: qid=10 cur=0 queued=0 tx ring 11: qid=11 cur=0 queued=0 tx ring 12: qid=12 cur=0 queued=0 tx ring 13: qid=13 cur=0 queued=0 tx ring 14: qid=14 cur=0 queued=0 tx ring 15: qid=15 cur=0 queued=0 tx ring 16: qid=16 cur=0 queued=0 tx ring 17: qid=17 cur=0 queued=0 tx ring 18: qid=18 cur=0 queued=0 tx ring 19: qid=19 cur=0 queued=0 rx ring: cur=0 wlan0: link state changed to DOWN vmstat -i: ... irq258: iwn0 973 0 ... Any ideas on what is broken and how to get it to work? Please Cc me as I am not on this specific list. Thank you. Sean -- s...@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: iwn firmware sysassert
On Thu, 25 Jul 2013, Adrian Chadd wrote: Ok, then I have no idea. There's active work on iwn going on in -HEAD. I suggest updating to that and then tracking development. No, I won't be backporting anything to -9 or -8; someone else will have to take charge of that (and field support queries when things don't work.) Thank you for the help. I did see your iwn RFC when I was looking for other reports of this problem. I will try a kernel from -HEAD to see if it helps. BTW, any idea what changes between 8 and 9 may have caused this to stop working? The firmware is the same for 8, 9 and -HEAD. On 25 July 2013 16:38, Sean C. Farley s...@freebsd.org wrote: On Thu, 25 Jul 2013, Adrian Chadd wrote: Try jsut doing: ifconfig wlan0 create wlandev iwn0 wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf .. ie, don't do an ifconfig iwn0 up Same result. I ran with ifconfig_wlan0=WPA removed from /etc/rc.conf else wpa_supplicant would start: ifconfig wlan0 destroy ifconfig wlan0 create wlandev iwn0 wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf On 25 July 2013 15:25, Sean C. Farley s...@freebsd.org wrote: After upgrading my laptop from 8.4-STABLE to 9-STABLE, I have been unable to use the wireless NIC. The indicator light will flash for a moment and surrender. The error is always the same and reproducible with ifconfig iwn0 up. The system is 9-STABLE (r253048). This appears to be the same or similar to PR 175053: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/175053 Boot: iwn0: Intel Ultimate N WiFi Link 5300 mem 0xf800-0xf8001fff irq 17 at device 0.0 on pci4 Card details: iwn0@pci0:4:0:0:class=0x028000 card=0x11218086 chip=0x42358086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'Ultimate N WiFi Link 5300' class = network bar [10] = type Memory, range 64, base 0xf800, size 8192, enabled cap 01[c8] = powerspec 3 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message cap 10[e0] = PCI-Express 1 endpoint max data 128(128) FLR link x1(x1) speed 2.5(2.5) ASPM L1(L0s/L1) ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 corrected ecap 0003[140] = Serial 1 00216a985c6e Error (same each time except for time): wlan0: link state changed to UP iwn0: iwn_intr: fatal firmware error firmware error log: error type = SYSASSERT (0x0005) program counter = 0x3130 source line = 0x0585 error data = 0x0001 branch link = 0x312A312A interrupt link = 0x0916 time= 1611815765 driver status: tx ring 0: qid=0 cur=0 queued=0 tx ring 1: qid=1 cur=0 queued=0 tx ring 2: qid=2 cur=0 queued=0 tx ring 3: qid=3 cur=2 queued=0 tx ring 4: qid=4 cur=67 queued=0 tx ring 5: qid=5 cur=0 queued=0 tx ring 6: qid=6 cur=0 queued=0 tx ring 7: qid=7 cur=0 queued=0 tx ring 8: qid=8 cur=0 queued=0 tx ring 9: qid=9 cur=0 queued=0 tx ring 10: qid=10 cur=0 queued=0 tx ring 11: qid=11 cur=0 queued=0 tx ring 12: qid=12 cur=0 queued=0 tx ring 13: qid=13 cur=0 queued=0 tx ring 14: qid=14 cur=0 queued=0 tx ring 15: qid=15 cur=0 queued=0 tx ring 16: qid=16 cur=0 queued=0 tx ring 17: qid=17 cur=0 queued=0 tx ring 18: qid=18 cur=0 queued=0 tx ring 19: qid=19 cur=0 queued=0 rx ring: cur=0 wlan0: link state changed to DOWN vmstat -i: ... irq258: iwn0 973 0 ... Any ideas on what is broken and how to get it to work? Please Cc me as I am not on this specific list. Thank you. Sean -- s...@freebsd.org Sean -- s...@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: iwn firmware sysassert
On Thu, 25 Jul 2013, Adrian Chadd wrote: Ok, then I have no idea. There's active work on iwn going on in -HEAD. I suggest updating to that and then tracking development. No, I won't be backporting anything to -9 or -8; someone else will have to take charge of that (and field support queries when things don't work.) I experimented a bit. A workaround for me is to set the mode to 11b on wlan0. While not the best solution, it hopefully narrows down the issue. I will at the code later for some ideas of what changed. On 25 July 2013 16:38, Sean C. Farley s...@freebsd.org wrote: On Thu, 25 Jul 2013, Adrian Chadd wrote: Try jsut doing: ifconfig wlan0 create wlandev iwn0 wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf .. ie, don't do an ifconfig iwn0 up Same result. I ran with ifconfig_wlan0=WPA removed from /etc/rc.conf else wpa_supplicant would start: ifconfig wlan0 destroy ifconfig wlan0 create wlandev iwn0 wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf On 25 July 2013 15:25, Sean C. Farley s...@freebsd.org wrote: After upgrading my laptop from 8.4-STABLE to 9-STABLE, I have been unable to use the wireless NIC. The indicator light will flash for a moment and surrender. The error is always the same and reproducible with ifconfig iwn0 up. The system is 9-STABLE (r253048). This appears to be the same or similar to PR 175053: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/175053 Boot: iwn0: Intel Ultimate N WiFi Link 5300 mem 0xf800-0xf8001fff irq 17 at device 0.0 on pci4 Card details: iwn0@pci0:4:0:0:class=0x028000 card=0x11218086 chip=0x42358086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'Ultimate N WiFi Link 5300' class = network bar [10] = type Memory, range 64, base 0xf800, size 8192, enabled cap 01[c8] = powerspec 3 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message cap 10[e0] = PCI-Express 1 endpoint max data 128(128) FLR link x1(x1) speed 2.5(2.5) ASPM L1(L0s/L1) ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 corrected ecap 0003[140] = Serial 1 00216a985c6e Error (same each time except for time): wlan0: link state changed to UP iwn0: iwn_intr: fatal firmware error firmware error log: error type = SYSASSERT (0x0005) program counter = 0x3130 source line = 0x0585 error data = 0x0001 branch link = 0x312A312A interrupt link = 0x0916 time= 1611815765 driver status: tx ring 0: qid=0 cur=0 queued=0 tx ring 1: qid=1 cur=0 queued=0 tx ring 2: qid=2 cur=0 queued=0 tx ring 3: qid=3 cur=2 queued=0 tx ring 4: qid=4 cur=67 queued=0 tx ring 5: qid=5 cur=0 queued=0 tx ring 6: qid=6 cur=0 queued=0 tx ring 7: qid=7 cur=0 queued=0 tx ring 8: qid=8 cur=0 queued=0 tx ring 9: qid=9 cur=0 queued=0 tx ring 10: qid=10 cur=0 queued=0 tx ring 11: qid=11 cur=0 queued=0 tx ring 12: qid=12 cur=0 queued=0 tx ring 13: qid=13 cur=0 queued=0 tx ring 14: qid=14 cur=0 queued=0 tx ring 15: qid=15 cur=0 queued=0 tx ring 16: qid=16 cur=0 queued=0 tx ring 17: qid=17 cur=0 queued=0 tx ring 18: qid=18 cur=0 queued=0 tx ring 19: qid=19 cur=0 queued=0 rx ring: cur=0 wlan0: link state changed to DOWN vmstat -i: ... irq258: iwn0 973 0 ... Any ideas on what is broken and how to get it to work? Please Cc me as I am not on this specific list. Thank you. Sean -- s...@freebsd.org Sean -- s...@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: My WLI-UC-GNM up crash
我更新到最新的源码（r253662），这次错误信息变成了0xde9f4d34
[root@FreeBSD.ttyu0] ~ # Fatal kernel mode data abort: 'Alignment Fault 1'
trapframe: 0xde9f4d34
FSR=0801, FAR=c284afbb, spsr=0013
r0 =c284c000, r1 =c284afbb, r2 =c284c210, r3 =096c
r4 =c284c024, r5 =c05f07c5, r6 =0014, r7 =c2844800
r8 =c05f07c5, r9 =c284c000, r10=35cb, r11=de9f4e10
r12=002e, ssp=de9f4d80, slr=, pc =c046d20c
[ thread pid 0 tid 100053 ]
Stopped at ieee80211_radiotap_chan_change+0x90:strhr3, [r1]
db
---
Kernel wlan related options
device wlan# 802.11 support
options IEEE80211_DEBUG # enable debug msgs
options IEEE80211_AMPDU_AGE # age frames in AMPDU reorder q's
options IEEE80211_SUPPORT_MESH # enable 802.11s draft support
device wlan_wep# 802.11 WEP support
device wlan_ccmp # 802.11 CCMP support
device wlan_tkip # 802.11 TKIP support
device wlan_amrr # AMRR transmit rate control algorithm
device firmware# firmware assist module
device run #Ralink Technology USB IEEE 802.11a/g/n
wireless network device
device runfw#Firmware Module for Ralink driver
---
The compiler command
make TARGET_ARCH=armv6 TARGET_CPUTYPE=armv6 KERNCONF=BBB WITH_FDT=yes
buildkernel
--
Regards.
By: XiaoQI Ge; PGP:8B09D5F7
WWW: https://www.7axu.com/
2013/7/24 XiaoQI Ge g...@7axu.com:
How do I debug it? Can provide useful information
login: root
Jul 24 18:27:31 FreeBSD login: ROOT LOGIN (root) ON ttyu0
FreeBSD 10.0-CURRENT (BBB) #4 r253585M: Wed Jul 24 17:07:53 CST 2013
[root@FreeBSD.ttyu0] ~ # ifconfig wlan create wlandev run0
wlan0: Ethernet address: 10:6f:3f:2b:fd:6d
wlan0
[root@FreeBSD.ttyu0] ~ # ifconfig wlan0 up
run0: firmware RT2870 ver. 0.236 loaded
Fatal kernel mode data abort: 'Alignment Fault 1'
trapframe: 0xde9e4d5c
FSR=0801, FAR=c282ffbb, spsr=0013
r0 =c2831000, r1 =c282ffbb, r2 =c2831210, r3 =096c
r4 =c2831024, r5 =c2831000, r6 =c05d9362, r7 =c2829800
r8 =0014, r9 =c08144d8, r10=80001cce, r11=de9e4e10
r12=002e, ssp=de9e4da8, slr=, pc =c045c510
[ thread pid 0 tid 100053 ]
Stopped at ieee80211_radiotap_chan_change+0x90:strhr3, [r1]
db
These two places modified:
2522 }
2523
2524 ant = run_maxrssi_chain(sc, rxwi);
2525 rssi = rxwi-rssi[ant];
2526 nf = run_rssi2dbm(sc, rssi, ant);
2527
2528 m-m_pkthdr.rcvif = ifp;
2529 m-m_pkthdr.len = m-m_len = len;
2530 /*
2531 if (ni != NULL) {
2532 (void)ieee80211_input(ni, m, rssi, nf);
2533 ieee80211_free_node(ni);
2534 } else {
2535 (void)ieee80211_input_all(ic, m, rssi, nf);
2536 }
2537 */
2538 /*
2539 * DAAN: fill-in tap header BEFORE calling ieee80211_input*() so the
2540 * user will see the actual data that belongs to THIS packet..
2541 */
2542 if (__predict_false(ieee80211_radiotap_active(ic))) {
2543 struct run_rx_radiotap_header *tap = sc-sc_rxtap;
2544
2545 tap-wr_flags = 0;
2546 tap-wr_chan_freq = htole16(ic-ic_curchan-ic_freq);
2547 tap-wr_chan_flags = htole16(ic-ic_curchan-ic_flags);
2548 tap-wr_antsignal = rssi;
2549 tap-wr_antenna = ant;
2550 tap-wr_dbm_antsignal = run_rssi2dbm(sc, rssi, ant);
2551 tap-wr_rate = 2; /* in case it can't be found below */
2552 phy = le16toh(rxwi-phy);
2553 switch (phy RT2860_PHY_MODE) {
2554 case RT2860_PHY_CCK:
2555 switch ((phy RT2860_PHY_MCS) ~RT2860_PHY_SHPRE) {
2556 case 0: tap-wr_rate = 2; break;
2557 case 1: tap-wr_rate = 4; break;
2558 case 2: tap-wr_rate = 11; break;
2559 case 3: tap-wr_rate = 22; break;
2560 }
2561 if (phy RT2860_PHY_SHPRE)
2562 tap-wr_flags |= IEEE80211_RADIOTAP_F_SHORTPRE;
2563 break;
2564 case RT2860_PHY_OFDM:
2565 switch (phy RT2860_PHY_MCS) {
2566 case 0: tap-wr_rate = 12; break;
2567 case 1: tap-wr_rate = 18; break;
2568 case 2: tap-wr_rate = 24; break;
2569 case 3: tap-wr_rate = 36; break;
2570 case 4: tap-wr_rate = 48; break;
2571 case 5: tap-wr_rate = 72; break;
2572 case 6: tap-wr_rate = 96; break;
2573 case 7: tap-wr_rate = 108; break;
2574 }
2575 break;
2576 }
2577 }
2578
2579 if (ni != NULL) {
2580 (void)ieee80211_input(ni, m, rssi, nf);
2581 ieee80211_free_node(ni);
2582 } else {
2583 (void)ieee80211_input_all(ic, m, rssi, nf);
2584 }
2585
2586 }
2587
2588 static void
Index: sys/vm/vm_map.c
===
--- sys/vm/vm_map.c (revision 253514)
+++ sys/vm/vm_map.c (working copy)
