From owner-freebsd-wireless@FreeBSD.ORG Mon Dec 9 19:35:52 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 69592599; Mon, 9 Dec 2013 19:35:52 +0000 (UTC) Received: from mail-qe0-x235.google.com (mail-qe0-x235.google.com [IPv6:2607:f8b0:400d:c02::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 047D8197B; Mon, 9 Dec 2013 19:35:51 +0000 (UTC) Received: by mail-qe0-f53.google.com with SMTP id nc12so3168372qeb.26 for ; Mon, 09 Dec 2013 11:35:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=GS0jMi/GcQeI75ZsISHNF71tkpPwmI7zseAQDnwzyNA=; b=rTbFIzxy9zzJ8cQUeqmfvMnUsGrpnXYh+s0r706Wlk5hoFLl4EIcV3ckA2l4ZaPjYG k85oI/HJTUJDnBBwDEhQFRT7Mwr9Eep2w5jVB5ujXWBrmVXXLLKH8ZVVCSHGhKpsl30X DbGqRA3MUCUzAbnQmtih0uDbo+iInXGpdPTjCBhGAL+WWOMNNIkVXCetgo+tMGJUlqAu Ipta15l3GB8KsvKVLmWVtv3uCTyd7npteaMpl+rZhq+Bd2ceLo91gaprnCdqUD8GiOOE FI4Y43FKvu8nmQjLIBvB+da9Dq+615XiqLS3aLOluBHHptY2ofF8FKbiuTfMybDEZVtI vw3A== MIME-Version: 1.0 X-Received: by 10.224.24.131 with SMTP id v3mr37411366qab.48.1386617751198; Mon, 09 Dec 2013 11:35:51 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.53.200 with HTTP; Mon, 9 Dec 2013 11:35:51 -0800 (PST) In-Reply-To: References: <52A58777.3050107@FreeBSD.org> Date: Mon, 9 Dec 2013 11:35:51 -0800 X-Google-Sender-Auth: g7VGtpTOXapUIaPZzraeyDikjyQ Message-ID: Subject: Re: [iwn] 6235 support, initial patch From: Adrian Chadd To: Alexander Motin Content-Type: text/plain; charset=ISO-8859-1 Cc: Lawrence Stewart , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Dec 2013 19:35:52 -0000 There, fixed in r259135. On 9 December 2013 11:34, Adrian Chadd wrote: > 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 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