Date: Mon, 9 Dec 2013 11:34:25 -0800 From: Adrian Chadd <adrian@freebsd.org> To: Alexander Motin <mav@freebsd.org> Cc: Lawrence Stewart <lstewart@freebsd.org>, "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org> Subject: Re: [iwn] 6235 support, initial patch Message-ID: <CAJ-VmomouJ=CY=MSyHre4jM5E0ccr5ZPWTzWOj45w1rRvrv%2B%2Bg@mail.gmail.com> In-Reply-To: <52A58777.3050107@FreeBSD.org> References: <CAJ-Vmom27NNX8bia4cchHuaM9ROoe7uiEO7FZ3PhxeRxGdgE9Q@mail.gmail.com> <52A58777.3050107@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Oh wait, I'm still using 17.x firmware? Let me fix that. I must not have committed it. -a On 9 December 2013 01:03, Alexander Motin <mav@freebsd.org> wrote: > Hi. > > > On 07.12.2013 22:21, Adrian Chadd wrote: >> >> Here's some fixes from mav, shoehorned into the current driver framework. >> >> Mav - where'd you get your changes from? > > > It was long ago. I would guess that from you. :) > > >> http://people.freebsd.org/~adrian/iwn/20131207-iwn-6235-1.diff >> >> This enables the 6235. >> >> It now doesn't firmware panic upon startup. I've passed _no_ traffic >> through it though - I don't have pigtails for the connectors on my >> NIC. Sorry :( >> >> I've added in mav's changes but I've done it by adding a new 6235 >> config / limits section rather than hacking up the existing 6000g2b >> section. I don't know what effect it'll have on the existing NICs. So >> I didn't want to change that behaviour. >> >> This is against the latest -HEAD. > > > I've updated to the latest HEAD including only your patch and immediately > got firmware crash during boot: > > firmware: 'iwn6000g2bfw' version 0: 460912 bytes loaded at > 0xffffffff81a120c0 > iwn0: iwn_intr: fatal firmware error > firmware error log: > error type = "UNKNOWN" (0x000019B6) > program counter = 0x00014DD0 > source line = 0x000002E2 > error data = 0x000000010000008C > branch link = 0x00014DC200014DC2 > interrupt link = 0x0000CFE200000000 > time = 26892 > 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=0 queued=0 > tx ring 4: qid=4 cur=0 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=2 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=2 > iwn0: iwn5000_post_alive: crystal calibration failed, error 35 > iwn0: iwn_init_locked: could not initialize hardware, error 35 > firmware: 'iwn6000g2bfw' version 0: 460912 bytes loaded at > 0xffffffff81a120c0 > iwn0: iwn_intr: fatal firmware error > firmware error log: > error type = "UNKNOWN" (0x000019B6) > program counter = 0x00014DD0 > source line = 0x000002E2 > error data = 0x000000010000008C > branch link = 0x00014DC200014DC2 > interrupt link = 0x0000CFE200000000 > time = 26907 > 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=0 queued=0 > tx ring 4: qid=4 cur=0 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=2 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=2 > iwn0: iwn5000_post_alive: crystal calibration failed, error 35 > iwn0: iwn_init_locked: could not initialize hardware, error 35 > > Adding usual -ht40 option didn't change anything. > > Then I switched from default 6000g2b firmware 17.168.5.2 to 18.168.6.1, > which I was using before. With -ht40 flag am able to connect and write this > letter. Without the flag card can't associate with AP: > > Dec 9 10:43:37 mavbook wpa_supplicant[467]: wlan0: Authentication with > 56:04:a6:d3:65:30 timed out. > Dec 9 10:43:37 mavbook wpa_supplicant[467]: wlan0: CTRL-EVENT-DISCONNECTED > bssid=56:04:a6:d3:65:30 reason=3 locally_generated=1 > Dec 9 10:43:41 mavbook wpa_supplicant[467]: wlan0: Trying to associate with > 56:04:a6:d3:65:30 (SSID='mavhome5' freq=5180 MHz) > Dec 9 10:43:41 mavbook wpa_supplicant[467]: wlan0: Associated with > 56:04:a6:d3:65:30 > Dec 9 10:43:41 mavbook kernel: wlan0: link state changed to UP > Dec 9 10:43:41 mavbook dhclient[1313]: send_packet: No buffer space > available > Dec 9 10:43:42 mavbook wpa_supplicant[467]: wlan0: CTRL-EVENT-DISCONNECTED > bssid=56:04:a6:d3:65:30 reason=0 > Dec 9 10:43:42 mavbook kernel: wlan0: link state changed to DOWN > Dec 9 10:43:45 mavbook dhclient[1313]: send_packet: Invalid argument > Dec 9 10:43:47 mavbook wpa_supplicant[467]: wlan0: Trying to associate with > 56:04:a6:d3:65:30 (SSID='mavhome5' freq=5180 MHz) > Dec 9 10:43:55 mavbook dhclient[1313]: send_packet: Network is down > Dec 9 10:43:57 mavbook wpa_supplicant[467]: wlan0: Authentication with > 56:04:a6:d3:65:30 timed out. > Dec 9 10:43:57 mavbook wpa_supplicant[467]: wlan0: CTRL-EVENT-DISCONNECTED > bssid=56:04:a6:d3:65:30 reason=3 locally_generated=1 > Dec 9 10:43:57 mavbook wpa_supplicant[467]: ioctl[SIOCS80211, op=20, val=0, > arg_len=7]: Can't assign requested address > Dec 9 10:43:59 mavbook dhclient[1313]: send_packet: Network is down > > Should I collect any other debugging? > > -- > Alexander Motin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmomouJ=CY=MSyHre4jM5E0ccr5ZPWTzWOj45w1rRvrv%2B%2Bg>