Date: Sat, 7 Dec 2013 09:50:27 -0800 From: Adrian Chadd <adrian@freebsd.org> To: =?UTF-8?B?5LmU5qWa?= <honestqiao@gmail.com>, "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org> Cc: Current FreeBSD <freebsd-current@freebsd.org> Subject: Re: Intel Centrino Wireless-N 1000 can't connect to AP Message-ID: <CAJ-Vmo=P2O_M876mbitdgC-e5byJZM56R5XSNYoE5K32SH0bUA@mail.gmail.com> In-Reply-To: <CAMAY4VgKjxdrNZHiciTr1keYZVFWkO65u=hkgxtxAmAeHKdiQA@mail.gmail.com> References: <CAMAY4VgKjxdrNZHiciTr1keYZVFWkO65u=hkgxtxAmAeHKdiQA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
A lot of work has gone on in -current with the iwn driver. It's quite possible that the recent changes has broken things. Would you please do this: * recompile with IWN_DEBUG defined in your kernel cofig * sysctl dev.iwn.0.debug=3D0x13ff (That turns on command debugging, tx/rx debugging, interrupt debugging and calibration debugging.) If you do that for both 10b3 and -head I can compare the two. Also, please post the output of pciconf -lv. I'd like to see which centrino-100 you're using. I thought I had tested it out on the Centrino 100 (I have a couple here) but there may be more variants that I haven't yet tested on. Thanks! -a On 7 December 2013 05:34, =E4=B9=94=E6=A5=9A <honestqiao@gmail.com> wrote: > Today ,I upgrade my freebsd from 10-beta4 to current. > Now, my freebsd can't connect to wireless AP. Wireless LAN strike. > > iwn0 in /var/log/message: > Dec 7 08:02:00 x201i kernel: iwn0: <Intel Centrino Wireless-N 1000> mem > 0xf2400000-0xf2401fff irq 16 at device 0.0 on pci2 > > Dec 7 08:02:00 x201i kernel: iwn0: attempting to allocate 1 MSI vectors = (1 > supported) > Dec 7 08:02:00 x201i kernel: msi: routing MSI IRQ 266 to local APIC 0 > vector 62 > Dec 7 08:02:00 x201i kernel: iwn0: using IRQ 266 for MSI > Dec 7 08:02:00 x201i kernel: iwn0: MIMO 1T2R, BGS, address > 8c:a9:82:5a:41:58 > Dec 7 08:02:00 x201i kernel: iwn0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps > Dec 7 08:02:00 x201i kernel: iwn0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps > 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps > Dec 7 08:02:00 x201i kernel: iwn0: 1T2R > Dec 7 08:02:00 x201i kernel: iwn0: 11ng MCS 20MHz > Dec 7 08:02:00 x201i kernel: iwn0: MCS 0-7: 6.5Mbps - 65Mbps > Dec 7 08:02:00 x201i kernel: iwn0: 11ng MCS 20MHz SGI > Dec 7 08:02:00 x201i kernel: iwn0: MCS 0-7: 7Mbps - 72Mbps > Dec 7 08:02:00 x201i kernel: iwn0: 11ng MCS 40MHz: > Dec 7 08:02:00 x201i kernel: iwn0: MCS 0-7: 13.5Mbps - 135Mbps > Dec 7 08:02:00 x201i kernel: iwn0: 11ng MCS 40MHz SGI: > Dec 7 08:02:00 x201i kernel: iwn0: MCS 0-7: 15Mbps - 150Mbps > ...... > Dec 7 08:02:00 x201i kernel: wlan0: Ethernet address: f0:de:f1:52:cf:16 > Dec 7 08:02:00 x201i kernel: iwn0: iwn_intr: fatal firmware error > Dec 7 08:02:00 x201i kernel: firmware error log: > Dec 7 08:02:00 x201i kernel: error type =3D "SYSASSERT" (0x00000005= ) > Dec 7 08:02:00 x201i kernel: program counter =3D 0x00018DBC > Dec 7 08:02:00 x201i kernel: source line =3D 0x00000032 > Dec 7 08:02:00 x201i kernel: error data =3D 0x0000000100000000 > Dec 7 08:02:00 x201i kernel: branch link =3D 0x00018D6E00018D6E > Dec 7 08:02:00 x201i kernel: interrupt link =3D 0x0000082600000000 > Dec 7 08:02:00 x201i kernel: time =3D 1538064582 > Dec 7 08:02:00 x201i kernel: driver status: > Dec 7 08:02:00 x201i kernel: tx ring 0: qid=3D0 cur=3D0 queued=3D0-- > Dec 7 08:02:00 x201i kernel: tx ring 1: qid=3D1 cur=3D0 queued=3D0-- > Dec 7 08:02:00 x201i kernel: tx ring 2: qid=3D2 cur=3D0 queued=3D0-- > Dec 7 08:02:00 x201i kernel: tx ring 3: qid=3D3 cur=3D2 queued=3D0-- > Dec 7 08:02:00 x201i kernel: tx ring 4: qid=3D4 cur=3D57 queued=3D0-- > Dec 7 08:02:00 x201i kernel: tx ring 5: qid=3D5 cur=3D0 queued=3D0-- > Dec 7 08:02:00 x201i kernel: tx ring 6: qid=3D6 cur=3D0 queued=3D0-- > Dec 7 08:02:00 x201i kernel: tx ring 7: qid=3D7 cur=3D0 queued=3D0-- > Dec 7 08:02:00 x201i kernel: tx ring 8: qid=3D8 cur=3D0 queued=3D0-- > Dec 7 08:02:00 x201i kernel: tx ring 9: qid=3D9 cur=3D0 queued=3D0-- > Dec 7 08:02:00 x201i kernel: tx ring 10: qid=3D10 cur=3D0 queued=3D0-- > Dec 7 08:02:00 x201i kernel: tx ring 11: qid=3D11 cur=3D0 queued=3D0-- > Dec 7 08:02:00 x201i kernel: tx ring 12: qid=3D12 cur=3D0 queued=3D0-- > Dec 7 08:02:00 x201i kernel: tx ring 13: qid=3D13 cur=3D0 queued=3D0-- > Dec 7 08:02:00 x201i kernel: tx ring 14: qid=3D14 cur=3D0 queued=3D0-- > Dec 7 08:02:00 x201i kernel: tx ring 15: qid=3D15 cur=3D0 queued=3D0-- > Dec 7 08:02:00 x201i kernel: tx ring 16: qid=3D16 cur=3D0 queued=3D0-- > Dec 7 08:02:00 x201i kernel: tx ring 17: qid=3D17 cur=3D0 queued=3D0-- > Dec 7 08:02:00 x201i kernel: tx ring 18: qid=3D18 cur=3D0 queued=3D0-- > Dec 7 08:02:00 x201i kernel: tx ring 19: qid=3D19 cur=3D0 queued=3D0-- > Dec 7 08:02:00 x201i kernel: rx ring: cur=3D29 > ...... > Dec 7 08:02:01 x201i wpa_supplicant[667]: ioctl[SIOCS80211, op=3D103, va= l=3D0, > arg_len=3D128]: Device not configured > Dec 7 08:02:01 x201i wpa_supplicant[667]: wlan0: Failed to initiate AP s= can > > I do not know where the problem is? > If necessary, I can tie debugging. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= "
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=P2O_M876mbitdgC-e5byJZM56R5XSNYoE5K32SH0bUA>