From owner-freebsd-wireless@FreeBSD.ORG Sun Feb 26 00:40:05 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA983106566C for ; Sun, 26 Feb 2012 00:40:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A5B298FC13 for ; Sun, 26 Feb 2012 00:40:05 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q1Q0e5Wc012490 for ; Sun, 26 Feb 2012 00:40:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q1Q0e5Oe012488; Sun, 26 Feb 2012 00:40:05 GMT (envelope-from gnats) Date: Sun, 26 Feb 2012 00:40:05 GMT Message-Id: <201202260040.q1Q0e5Oe012488@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org From: Adrian Chadd Cc: Subject: Re: kern/163318: [ath] ath(4) stops working X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Adrian Chadd 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: Sun, 26 Feb 2012 00:40:05 -0000 The following reply was made to PR kern/163318; it has been noted by GNATS. From: Adrian Chadd To: Joel Dahl Cc: bug-followup@freebsd.org Subject: Re: kern/163318: [ath] ath(4) stops working Date: Sat, 25 Feb 2012 16:38:24 -0800 --f46d04388ee921d80204b9d3367a Content-Type: text/plain; charset=ISO-8859-1 Hi, Please try this patch. Adrian --f46d04388ee921d80204b9d3367a Content-Type: text/x-patch; charset=US-ASCII; name="ieee80211_scan_check.diff" Content-Disposition: attachment; filename="ieee80211_scan_check.diff" Content-Transfer-Encoding: base64 X-Attachment-Id: f_gz3cpoa90 SW5kZXg6IHN5cy9uZXQ4MDIxMS9pZWVlODAyMTFfc2Nhbi5jCj09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0KLS0tIHN5cy9u ZXQ4MDIxMS9pZWVlODAyMTFfc2Nhbi5jCShyZXZpc2lvbiAyMzIwOTcpCisrKyBzeXMvbmV0ODAy MTEvaWVlZTgwMjExX3NjYW4uYwkod29ya2luZyBjb3B5KQpAQCAtNDM0LDEzICs0MzQsMTIgQEAK IAkJCWljLT5pY19mbGFncyB8PSBJRUVFODAyMTFfRl9TQ0FOOwogCQkJaWVlZTgwMjExX3J1bnRh c2soaWMsICZTQ0FOX1BSSVZBVEUoc3MpLT5zc19zY2FuX3Rhc2spOwogCQl9Ci0JCXJldHVybiAx OwogCX0gZWxzZSB7CiAJCUlFRUU4MDIxMV9EUFJJTlRGKHZhcCwgSUVFRTgwMjExX01TR19TQ0FO LAogCQkgICAgIiVzOiAlcyBzY2FuIGFscmVhZHkgaW4gcHJvZ3Jlc3NcbiIsIF9fZnVuY19fLAog CQkgICAgc3MtPnNzX2ZsYWdzICYgSUVFRTgwMjExX1NDQU5fQUNUSVZFID8gImFjdGl2ZSIgOiAi cGFzc2l2ZSIpOwogCX0KLQlyZXR1cm4gMDsKKwlyZXR1cm4gISEgKGljLT5pY19mbGFncyAmIElF RUU4MDIxMV9GX1NDQU4pOwogfQogCiAvKgpAQCAtOTYwLDYgKzk1OSwxNyBAQAogCUlFRUU4MDIx MV9MT0NLKGljKTsKIAogCS8qCisJICogU2luY2UgYSBjYW5jZWxsYXRpb24gbWF5IGhhdmUgb2Nj dXJlZCBkdXJpbmcgb25lIG9mIHRoZQorCSAqIGRyaXZlciBjYWxscyAod2hpbHN0IHVubG9ja2Vk KSwgdXBkYXRlIHNjYW5kb25lLgorCSAqLworCWlmIChzY2FuZG9uZSA9PSAwICYmCisJICAgICgo U0NBTl9QUklWQVRFKHNzKS0+c3NfaWZsYWdzICYgSVNDQU5fQ0FOQ0VMKSAhPSAwKSkgeworCQlw cmludGYoIiVzOiBPT1BTISBzY2FuIGNhbmNlbGxlZCBkdXJpbmcgZHJpdmVyIGNhbGwhXG4iLAor CQkgICAgX19mdW5jX18pOworCX0KKwlzY2FuZG9uZSB8PSAoKFNDQU5fUFJJVkFURShzcyktPnNz X2lmbGFncyAmIElTQ0FOX0NBTkNFTCkgIT0gMCk7CisKKwkvKgogCSAqIFJlY29yZCBzY2FuIGNv bXBsZXRlIHRpbWUuICBOb3RlIHRoYXQgd2UgYWxzbyBkbwogCSAqIHRoaXMgd2hlbiBjYW5jZWxl ZCBzbyBhbnkgYmFja2dyb3VuZCBzY2FuIHdpbGwKIAkgKiBub3QgYmUgcmVzdGFydGVkIGZvciBh IHdoaWxlLgo= --f46d04388ee921d80204b9d3367a-- From owner-freebsd-wireless@FreeBSD.ORG Sun Feb 26 04:11:14 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 88F31106566B; Sun, 26 Feb 2012 04:11:14 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 608CC8FC13; Sun, 26 Feb 2012 04:11:14 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q1Q4BExM008655; Sun, 26 Feb 2012 04:11:14 GMT (envelope-from eadler@freefall.freebsd.org) Received: (from eadler@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q1Q4BEO6008646; Sun, 26 Feb 2012 04:11:14 GMT (envelope-from eadler) Date: Sun, 26 Feb 2012 04:11:14 GMT Message-Id: <201202260411.q1Q4BEO6008646@freefall.freebsd.org> To: eadler@FreeBSD.org, freebsd-i386@FreeBSD.org, freebsd-wireless@FreeBSD.org From: eadler@FreeBSD.org Cc: Subject: Re: kern/165463: FreeBSD doesn't work with NIC based on RLT8111E X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Sun, 26 Feb 2012 04:11:14 -0000 Old Synopsis: FreeBSD didnt work with NIC based on RLT8111E New Synopsis: FreeBSD doesn't work with NIC based on RLT8111E Responsible-Changed-From-To: freebsd-i386->freebsd-wireless Responsible-Changed-By: eadler Responsible-Changed-When: Sun Feb 26 04:10:05 UTC 2012 Responsible-Changed-Why: fix synopsis and assign http://www.freebsd.org/cgi/query-pr.cgi?pr=165463 From owner-freebsd-wireless@FreeBSD.ORG Sun Feb 26 04:16:19 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 933F7106566C; Sun, 26 Feb 2012 04:16:19 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 6AFA88FC12; Sun, 26 Feb 2012 04:16:19 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q1Q4GJq6013551; Sun, 26 Feb 2012 04:16:19 GMT (envelope-from eadler@freefall.freebsd.org) Received: (from eadler@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q1Q4GJPY013547; Sun, 26 Feb 2012 04:16:19 GMT (envelope-from eadler) Date: Sun, 26 Feb 2012 04:16:19 GMT Message-Id: <201202260416.q1Q4GJPY013547@freefall.freebsd.org> To: eadler@FreeBSD.org, freebsd-wireless@FreeBSD.org, freebsd-bugs@FreeBSD.org From: eadler@FreeBSD.org Cc: Subject: Re: kern/165463: FreeBSD doesn't work with NIC based on RLT8111E X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Sun, 26 Feb 2012 04:16:19 -0000 Synopsis: FreeBSD doesn't work with NIC based on RLT8111E Responsible-Changed-From-To: freebsd-wireless->freebsd-bugs Responsible-Changed-By: eadler Responsible-Changed-When: Sun Feb 26 04:16:02 UTC 2012 Responsible-Changed-Why: aah - this isn't wireless http://www.freebsd.org/cgi/query-pr.cgi?pr=165463 From owner-freebsd-wireless@FreeBSD.ORG Sun Feb 26 06:10:13 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E960C106566C for ; Sun, 26 Feb 2012 06:10:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D8AC48FC08 for ; Sun, 26 Feb 2012 06:10:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q1Q6ACkO014708 for ; Sun, 26 Feb 2012 06:10:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q1Q6ACY7014703; Sun, 26 Feb 2012 06:10:12 GMT (envelope-from gnats) Date: Sun, 26 Feb 2012 06:10:12 GMT Message-Id: <201202260610.q1Q6ACY7014703@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: kern/165475: commit references a PR X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service 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: Sun, 26 Feb 2012 06:10:13 -0000 The following reply was made to PR kern/165475; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/165475: commit references a PR Date: Sun, 26 Feb 2012 06:05:00 +0000 (UTC) Author: adrian Date: Sun Feb 26 06:04:44 2012 New Revision: 232170 URL: http://svn.freebsd.org/changeset/base/232170 Log: Add in some debugging code to check whether the current rate table has been bait-and-switched from the rate control code. This will avoid the panic that I saw and will avoid sending invalid rates (eg 11a/11g OFDM rates when in 11b, on 11b-only NICs (AR5211)) where the rate table is not "big". It also will point out situations where this occurs for the 11n NICs which will have sufficiently large rate tables that "invalid rix" doesn't occur. I'll try to follow this up with a commit that adds a current operating mode check. The "rix" is only relevant to the current operating mode and rate table. PR: kern/165475 Modified: head/sys/dev/ath/ath_rate/sample/sample.c head/sys/dev/ath/ath_rate/sample/sample.h Modified: head/sys/dev/ath/ath_rate/sample/sample.c ============================================================================== --- head/sys/dev/ath/ath_rate/sample/sample.c Sun Feb 26 02:24:40 2012 (r232169) +++ head/sys/dev/ath/ath_rate/sample/sample.c Sun Feb 26 06:04:44 2012 (r232170) @@ -495,6 +495,14 @@ ath_rate_findrate(struct ath_softc *sc, ath_rate_update_static_rix(sc, &an->an_node); + if (sn->currates != sc->sc_currates) { + device_printf(sc->sc_dev, "%s: currates != sc_currates!\n", + __func__); + rix = 0; + *try0 = ATH_TXMAXTRY; + goto done; + } + if (sn->static_rix != -1) { rix = sn->static_rix; *try0 = ATH_TXMAXTRY; @@ -621,6 +629,20 @@ ath_rate_findrate(struct ath_softc *sc, } *try0 = mrr ? sn->sched[rix].t0 : ATH_TXMAXTRY; done: + + /* + * This bug totally sucks and should be fixed. + * + * For now though, let's not panic, so we can start to figure + * out how to better reproduce it. + */ + if (rix < 0 || rix >= rt->rateCount) { + printf("%s: ERROR: rix %d out of bounds (rateCount=%d)\n", + __func__, + rix, + rt->rateCount); + rix = 0; /* XXX just default for now */ + } KASSERT(rix >= 0 && rix < rt->rateCount, ("rix is %d", rix)); *rix0 = rix; @@ -1073,6 +1095,8 @@ ath_rate_ctl_reset(struct ath_softc *sc, sn->static_rix = -1; ath_rate_update_static_rix(sc, ni); + sn->currates = sc->sc_currates; + /* * Construct a bitmask of usable rates. This has all * negotiated rates minus those marked by the hal as Modified: head/sys/dev/ath/ath_rate/sample/sample.h ============================================================================== --- head/sys/dev/ath/ath_rate/sample/sample.h Sun Feb 26 02:24:40 2012 (r232169) +++ head/sys/dev/ath/ath_rate/sample/sample.h Sun Feb 26 06:04:44 2012 (r232170) @@ -86,6 +86,8 @@ struct sample_node { uint32_t ratemask; /* bit mask of valid rate indices */ const struct txschedule *sched; /* tx schedule table */ + const HAL_RATE_TABLE *currates; + struct rate_stats stats[NUM_PACKET_SIZE_BINS][SAMPLE_MAXRATES]; int last_sample_rix[NUM_PACKET_SIZE_BINS]; _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Sun Feb 26 06:11:12 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AC58F106566C for ; Sun, 26 Feb 2012 06:11:12 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 3D93F8FC15 for ; Sun, 26 Feb 2012 06:11:11 +0000 (UTC) Received: by wgbds12 with SMTP id ds12so89989wgb.31 for ; Sat, 25 Feb 2012 22:11:11 -0800 (PST) Received-SPF: pass (google.com: domain of adrian.chadd@gmail.com designates 10.180.95.105 as permitted sender) client-ip=10.180.95.105; Authentication-Results: mr.google.com; spf=pass (google.com: domain of adrian.chadd@gmail.com designates 10.180.95.105 as permitted sender) smtp.mail=adrian.chadd@gmail.com; dkim=pass header.i=adrian.chadd@gmail.com Received: from mr.google.com ([10.180.95.105]) by 10.180.95.105 with SMTP id dj9mr17722825wib.18.1330236671223 (num_hops = 1); Sat, 25 Feb 2012 22:11:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=CEH2oxIFBi6tz6klHq0/ugqPi4L9x4x9JKpuHeeARZk=; b=bXkYrnG+xXDoh190axP3ZtSr6zwySzOZ/e/bb5gUSCm9n7p5qqZujr2HZjmKF45swG nUkxAXMm+TFCGk0q112+WDXli36EODlr0PU/LvYgFzqfIFkvOkIF4M/nnRbC+1uELWMl 0vP58gBxoC8V7u4yhz8W2AOm/WDoVyZafbJBc= MIME-Version: 1.0 Received: by 10.180.95.105 with SMTP id dj9mr14125770wib.18.1330236671162; Sat, 25 Feb 2012 22:11:11 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.154.199 with HTTP; Sat, 25 Feb 2012 22:11:11 -0800 (PST) Date: Sat, 25 Feb 2012 22:11:11 -0800 X-Google-Sender-Auth: I7tUxaEwDPT4SgKqsnnBhSCaZKY Message-ID: From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: [ath] please test -HEAD: trying to find/fix the rate control and bgscan races X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Sun, 26 Feb 2012 06:11:12 -0000 Hi all, In my "make ALL the old NICs work" work, I found that this AR5211 NIC would panic almost instantly after the first set of background scans. What was happening was an invalid rix was being passed. What really was happening was: * the nic would come up in 11a mode and establish a high throughput rate - eg, 36/54megabit rate; * the best rix in the sample rate module would be high, say 5; * then the operating mode would change (eg for scanning) and a frame would be tx'ed with the operating mode being 11b; * .. and it would pick best_rix, which would then happily return 5 * .. and that's outside of what the current rate map is, which for 11b is a few entries smaller than 11a. Similar weird things have happened before for 11bg/11a NICs as well as the 11n NICs. But this crashed frequently rather than having "weird stuff" happen. So I've committed some stuff to -HEAD which prints out warnings in case a rate control lookup is done with the current rate table not matching what ath_rate_sample was setup for. here's an example of what I saw: wlan0: Ethernet address: 00:03:7f:11:a3:f3 wlan0: link state changed to UP ar5416PerCalibrationN: NF calibration didn't finish; delaying CCA ath0: bad series0 hwrate 0x1b, tries 1 ts_status 0x0 ath0: bad series0 hwrate 0x1b, tries 1 ts_status 0x0 ath0: bad series0 hwrate 0x1b, tries 1 ts_status 0x0 wlan0: link state changed to DOWN wlan0: link state changed to UP ath0: bad series0 hwrate 0x1b, tries 1 ts_status 0x0 ath0: bad series0 hwrate 0x1b, tries 1 ts_status 0x0 ath0: bad series0 hwrate 0x1b, tries 1 ts_status 0x0 [100548] ath0: ath_rate_findrate: currates != sc_currates! [100548] ath0: ath_rate_findrate: currates != sc_currates! ath0: bad series0 hwrate 0x1b, tries 1 ts_status 0x0 ath0: bad series0 hwrate 0x1b, tries 1 ts_status 0x0 [100279] ath0: ath_rate_findrate: currates != sc_currates! ath0: bad series0 hwrate 0x1b, tries 1 ts_status 0x0 [100279] ath0: ath_rate_findrate: currates != sc_currates! I'd really appreciate it if other atheros NIC users would try out -HEAD and let me know if they see the same kind of issue. If you do then please email the list with some information and we'll see if we can track it down. Also as you can see above (this is happening on the AR9280 in 11ng mode), I get "bad series0 hwrate" messages. I need to investigate this a little closer. That's the 1mbit CCK rate - I should print out what the current operating mode is, as I bet that is occuring when we're in an 11a mode. 11ng includes the CCK rates. Thanks, Adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Feb 27 01:36:37 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ED1E6106566B for ; Mon, 27 Feb 2012 01:36:37 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 74E4A8FC12 for ; Mon, 27 Feb 2012 01:36:37 +0000 (UTC) Received: by wgbds12 with SMTP id ds12so492438wgb.31 for ; Sun, 26 Feb 2012 17:36:36 -0800 (PST) Received-SPF: pass (google.com: domain of adrian.chadd@gmail.com designates 10.180.93.4 as permitted sender) client-ip=10.180.93.4; Authentication-Results: mr.google.com; spf=pass (google.com: domain of adrian.chadd@gmail.com designates 10.180.93.4 as permitted sender) smtp.mail=adrian.chadd@gmail.com; dkim=pass header.i=adrian.chadd@gmail.com Received: from mr.google.com ([10.180.93.4]) by 10.180.93.4 with SMTP id cq4mr23151700wib.21.1330306596443 (num_hops = 1); Sun, 26 Feb 2012 17:36:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=wgNe7blKC7idneEQCIYJMAMBecrb7x7aujioes7/2TA=; b=KM2vTIrxS34kNWTqZsJT1CJRouwynB0uAJX0wRhR1+D05ZUE5GoRvVC//wZpdLEhyb X4xLa+JbLgo/xYWFDz5PB6yah5XJMHgZ6NrqKMkUDlgg7CeftphaGz5i9xNzGauwacY5 /QLqmaW7QMHM29nYseJZ/hwZymXhPcAfS1P+I= MIME-Version: 1.0 Received: by 10.180.93.4 with SMTP id cq4mr18439384wib.21.1330306596276; Sun, 26 Feb 2012 17:36:36 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.198.81 with HTTP; Sun, 26 Feb 2012 17:36:36 -0800 (PST) Date: Sun, 26 Feb 2012 17:36:36 -0800 X-Google-Sender-Auth: U7P4Xw4W3ZU2T6pfTlPNoCZT93A Message-ID: From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: [wi] Trying to make it work for people; a day of tinkering.. X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Feb 2012 01:36:38 -0000 Hi all, I've been tinkering with these orinoco/lucent wi(4) NICs. The one in particular is a Hermes firmware NIC, STA firmware 72801. The summary is pretty simple: * Setting sysctls hw.wi.debug=1 and hw.wi.txerate=1 makes for some interesting debugging output; * We _are_ receiving TX and RX interrupts from the NIC; * TXing for me is failing, with "invalid format" errors; * RX'ing for me fires off completion interrupts, but the rx function doesn't find the node, so it simply tosses the frame; * If I change the TX encapsulation from 802_11 to 802_3, TX is actually successful - but RX stays unsuccessful. r160991 is a likely culprit - it changed a whole lot of the TX codepath to support raw frame TX, but there's no evidence at all that it ever worked in STA/IBSS modes. I also am not sure whether the "ibss mode" value in wi_start_locked() should be "3". It looks like openbsd sets that to 0 unless you're in IBSS mode. Also: "ifconfig wlan0 list sta" always shows no node, so it's quite likely net80211 thinks there's no actual association going on. is this because mgmt frames aren't being received by the rx path and thus net80211 doesn't "know" about the new association? Also: scan logs that it's changing channels but I don't (yet) see beacon frames being received - and the scan cache is never populated. That's another thing to try and figure out. It'd be nice if someone were able to import the openbsd if_wi driver (mostly) verbatim. I'm not sure I want to spend hours trying to figure out which particular configuration bit is required to restore functionality here. Thanks to Justin Hibbits for sitting down with me and briefly brainstorming this stuff! Adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Feb 27 11:07:51 2012 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 108861065688 for ; Mon, 27 Feb 2012 11:07:51 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id F26208FC16 for ; Mon, 27 Feb 2012 11:07:50 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q1RB7o2l090400 for ; Mon, 27 Feb 2012 11:07:50 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q1RB7o8i090398 for freebsd-wireless@FreeBSD.org; Mon, 27 Feb 2012 11:07:50 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 27 Feb 2012 11:07:50 GMT Message-Id: <201202271107.q1RB7o8i090398@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-wireless@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-wireless@FreeBSD.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Feb 2012 11:07:51 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/165475 wireless [ath] operational mode change doesn't poke the underly o kern/165382 wireless [kernel] taskqueue_unblock doesn't unblock currently q o kern/165306 wireless [ath] race conditions between scanning and beacon time o kern/165220 wireless [ath] "ath_rx_tasklet: sc_inreset_cnt > 0; skipping" m o kern/165214 wireless [ieee80211] Kernel panic in ieee80211_output.c:2505 o kern/165212 wireless [ath] No WiFi on Acer Aspire One 751h (Atheros AR5BHB6 o kern/165149 wireless [ath] [net80211] Ping with data length more than iv_fr o kern/165146 wireless [net80211] Net802.11 Fragment number is assigned 1 (sh o kern/165060 wireless [ath] vap->iv_bss race conditions causing crashes insi o kern/165021 wireless [ath] ath device timeout during scan/attach, if wlan_c o kern/164721 wireless [ath] ath device timeouts o kern/164499 wireless [wi] [patch] if_wi needs fix for big endian architectu o kern/164382 wireless [ath] crash when down/deleting a vap - inside ieee8021 o kern/164365 wireless [iwi] iwi0: UP/DOWN in o bin/164102 wireless hostapd not configured for 802.11n o kern/163759 wireless [ath] ath(4) "stops working" in hostap mode o kern/163724 wireless [mwl] [patch] NULL check before dereference o kern/163719 wireless [ath] ath interface do not receive multicast o kern/163689 wireless [ath] TX timeouts when sending probe/mgmt frames durin o kern/163574 wireless [net80211] overly-frequent HT occupancy changes o kern/163573 wireless [ath] hostap mode TX buffer hang o kern/163559 wireless [ath] kernel panic AH_DEBUG o kern/163318 wireless [ath] ath(4) stops working p kern/163312 wireless [panic] [ath driver] kernel panic: page fault with ath o kern/163082 wireless [ath] ar9285 diversity fixes o kern/162648 wireless [ath] AR9227 ADC DC calibration failure o kern/162647 wireless [ath] 11n TX aggregation session / TX hang o kern/161293 wireless [iwn] hang at startup when starting network o kern/161035 wireless [ieee80211] Incorrect number describing 11ng MCS rate o kern/160391 wireless [ieee80211] [patch] Panic in mesh mode o kern/160296 wireless [zyd] [panic] 802.11 usb device reboots system on 'ifc o misc/160176 wireless [mips] [panic] Kernel panic on AR7161 platform with AR o kern/157449 wireless [ath] MAC address conflict causes system to freeze o kern/157243 wireless [ath] investigate beacon TX (AP) / RX (STA) when under o kern/156904 wireless [ath] AR9285 antenna diversity algorithm is buggy and o kern/156884 wireless [ath] ath instablity o kern/156327 wireless [bwn] bwn driver causes 20%-50% packet loss o kern/156322 wireless [wpi] no ahdemo support for if_wpi o kern/156321 wireless [ath] ahdemo doesn't work with if_ath o kern/155498 wireless [ral] ral(4) needs to be resynced with OpenBSD's to ga o kern/155100 wireless [ath] ath driver on busy channel: "stuck beacon" p kern/154598 wireless [ath] Atheros 5424/2424 can't connect to WPA network o kern/154567 wireless [ath] ath(4) lot of bad series(0) o kern/154327 wireless [ath] AR5416 in station mode hangs when transmitting f o kern/154284 wireless [ath] Modern ath wifi cards (such as AR9285) have miss o kern/154153 wireless [ath] AR5213 + MIPS + WPA group key packet corruption o kern/153448 wireless [ath] ath networking device loses association after a o kern/152750 wireless [ath] ath0 lot of bad series hwrate o kern/151198 wireless [ath] ath/5416 fails bgscan with "ath0: ath_chan_set: o kern/149786 wireless [bwn] bwn on Dell Inspiron 1150: connections stall o kern/149516 wireless [ath] ath(4) hostap with fake MAC/BSSID results in sta o kern/149373 wireless [realtek/atheros]: None of my network card working o kern/148322 wireless [ath] Triggering atheros wifi beacon misses in hostap o kern/148317 wireless [ath] FreeBSD 7.x hostap memory leak in net80211 or At o kern/148078 wireless [ath] wireless networking stops functioning o kern/145826 wireless [panic] [ath] Unable to configure adhoc mode on ath0/w o kern/144987 wireless [wpi] [panic] injecting packets with wlaninject using o bin/144109 wireless hostapd(8) uses the MAC of the wireless interface, but o conf/143079 wireless hostapd(8) startup missing multi wlan functionality p kern/140567 wireless [ath] [patch] ath is not worked on my notebook PC o kern/140245 wireless [ath] [panic] Kernel panic during network activity on o kern/137592 wireless [ath] panic - 7-STABLE (Aug 7, 2009 UTC) crashes on ne p bin/137484 wireless [patch] Integer overflow in wpa_supplicant(8) base64 e o kern/136943 wireless [wpi] [lor] wpi0_com_lock / wpi0 o kern/136836 wireless [ath] atheros card stops functioning after about 12 ho o kern/132722 wireless [ath] Wifi ath0 associates fine with AP, but DHCP or I o bin/131549 wireless ifconfig(8) can't clear 'monitor' mode on the wireless o kern/126475 wireless [ath] [panic] ath pcmcia card inevitably panics under o kern/125721 wireless [ath] Terrible throughput/high ping latency with Ubiqu o kern/125617 wireless [ath] [panic] ath(4) related panic o kern/125501 wireless [ath] atheros cardbus driver hangs o kern/125332 wireless [ath] [panic] crash under any non-tiny networking unde o kern/124767 wireless [iwi] Wireless connection using iwi0 driver (Intel 220 o kern/124753 wireless [ieee80211] net80211 discards power-save queue packets o docs/120456 wireless ath(4) needs to specify requirement on wlan_scan_sta o kern/119513 wireless [ath] [irq] inserting dlink dwl-g630 wireless card res o kern/116747 wireless [ndis] FreeBSD 7.0-CURRENT crash with Dell TrueMobile f kern/105348 wireless [ath] ath device stopps TX 78 problems total. From owner-freebsd-wireless@FreeBSD.ORG Tue Feb 28 02:42:33 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AD11F106564A; Tue, 28 Feb 2012 02:42:33 +0000 (UTC) (envelope-from adrian@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 8092B8FC0C; Tue, 28 Feb 2012 02:42:33 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q1S2gXHh076233; Tue, 28 Feb 2012 02:42:33 GMT (envelope-from adrian@freefall.freebsd.org) Received: (from adrian@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q1S2gXIA076229; Tue, 28 Feb 2012 02:42:33 GMT (envelope-from adrian) Date: Tue, 28 Feb 2012 02:42:33 GMT Message-Id: <201202280242.q1S2gXIA076229@freefall.freebsd.org> To: adrian@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: adrian@FreeBSD.org Cc: Subject: Re: kern/165517: [net80211] bgscan isn't triggered when invalid beacons are being sent X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 28 Feb 2012 02:42:33 -0000 Synopsis: [net80211] bgscan isn't triggered when invalid beacons are being sent Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: adrian Responsible-Changed-When: Tue Feb 28 02:42:25 UTC 2012 Responsible-Changed-Why: Reassign http://www.freebsd.org/cgi/query-pr.cgi?pr=165517 From owner-freebsd-wireless@FreeBSD.ORG Tue Feb 28 04:10:11 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6136C106564A for ; Tue, 28 Feb 2012 04:10:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 4C51B8FC0C for ; Tue, 28 Feb 2012 04:10:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q1S4ABXn049610 for ; Tue, 28 Feb 2012 04:10:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q1S4AB3M049608; Tue, 28 Feb 2012 04:10:11 GMT (envelope-from gnats) Date: Tue, 28 Feb 2012 04:10:11 GMT Message-Id: <201202280410.q1S4AB3M049608@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: kern/165517: commit references a PR X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service 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: Tue, 28 Feb 2012 04:10:11 -0000 The following reply was made to PR kern/165517; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/165517: commit references a PR Date: Tue, 28 Feb 2012 04:05:51 +0000 (UTC) Author: adrian Date: Tue Feb 28 04:05:35 2012 New Revision: 232244 URL: http://svn.freebsd.org/changeset/base/232244 Log: Track the number of bad beacons received. PR: kern/165517 Modified: head/sys/net80211/ieee80211_ioctl.h head/sys/net80211/ieee80211_sta.c Modified: head/sys/net80211/ieee80211_ioctl.h ============================================================================== --- head/sys/net80211/ieee80211_ioctl.h Tue Feb 28 03:11:02 2012 (r232243) +++ head/sys/net80211/ieee80211_ioctl.h Tue Feb 28 04:05:35 2012 (r232244) @@ -241,8 +241,9 @@ struct ieee80211_stats { uint32_t is_mesh_notproxy; /* dropped 'cuz not proxying */ uint32_t is_rx_badalign; /* dropped 'cuz misaligned */ uint32_t is_hwmp_proxy; /* PREP for proxy route */ + uint32_t is_beacon_bad; /* Number of bad beacons */ - uint32_t is_spare[11]; + uint32_t is_spare[10]; }; /* Modified: head/sys/net80211/ieee80211_sta.c ============================================================================== --- head/sys/net80211/ieee80211_sta.c Tue Feb 28 03:11:02 2012 (r232243) +++ head/sys/net80211/ieee80211_sta.c Tue Feb 28 04:05:35 2012 (r232244) @@ -1305,8 +1305,10 @@ sta_recv_mgmt(struct ieee80211_node *ni, return; } /* XXX probe response in sta mode when !scanning? */ - if (ieee80211_parse_beacon(ni, m0, &scan) != 0) + if (ieee80211_parse_beacon(ni, m0, &scan) != 0) { + vap->iv_stats.is_beacon_bad++; return; + } /* * Count frame now that we know it's to be processed. */ _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Tue Feb 28 04:10:13 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 62F0B106566B for ; Tue, 28 Feb 2012 04:10:13 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 4DD608FC13 for ; Tue, 28 Feb 2012 04:10:13 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q1S4ADkZ049666 for ; Tue, 28 Feb 2012 04:10:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q1S4ADOI049665; Tue, 28 Feb 2012 04:10:13 GMT (envelope-from gnats) Date: Tue, 28 Feb 2012 04:10:13 GMT Message-Id: <201202280410.q1S4ADOI049665@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: kern/165517: commit references a PR X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service 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: Tue, 28 Feb 2012 04:10:13 -0000 The following reply was made to PR kern/165517; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/165517: commit references a PR Date: Tue, 28 Feb 2012 04:06:52 +0000 (UTC) Author: adrian Date: Tue Feb 28 04:06:42 2012 New Revision: 232245 URL: http://svn.freebsd.org/changeset/base/232245 Log: Add is_beacon_bad. PR: kern/165517 Modified: head/tools/tools/net80211/wlanstats/wlanstats.c Modified: head/tools/tools/net80211/wlanstats/wlanstats.c ============================================================================== --- head/tools/tools/net80211/wlanstats/wlanstats.c Tue Feb 28 04:05:35 2012 (r232244) +++ head/tools/tools/net80211/wlanstats/wlanstats.c Tue Feb 28 04:06:42 2012 (r232245) @@ -370,6 +370,8 @@ static const struct fmt wlanstats[] = { { 5, "noise", "noise", "current noise floor (dBm)" }, #define S_SIGNAL AFTER(S_NOISE) { 5, "signal", "sig", "current signal (dBm)" }, +#define S_BEACON_BAD AFTER(S_SIGNAL) + { 9, "beacon_bad", "beaconbad", "bad beacons received" }, }; struct wlanstatfoo_p { @@ -814,6 +816,7 @@ wlan_get_curstat(struct statfoo *sf, int case S_RX_MCAST: NSTAT(rx_mcast); case S_TX_UCAST: NSTAT(tx_ucast); case S_TX_MCAST: NSTAT(tx_mcast); + case S_BEACON_BAD: STAT(beacon_bad); } return wlan_getinfo(wf, s, b, bs); #undef NSTAT @@ -972,6 +975,7 @@ wlan_get_totstat(struct statfoo *sf, int case S_RX_MCAST: NSTAT(rx_mcast); case S_TX_UCAST: NSTAT(tx_ucast); case S_TX_MCAST: NSTAT(tx_mcast); + case S_BEACON_BAD: STAT(beacon_bad); } return wlan_getinfo(wf, s, b, bs); #undef NSTAT _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Tue Feb 28 14:39:10 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7862F1065676 for ; Tue, 28 Feb 2012 14:39:10 +0000 (UTC) (envelope-from jhugo@meraka.csir.co.za) Received: from marge.meraka.csir.co.za (marge.meraka.csir.co.za [IPv6:2001:4200:7000:3::1]) by mx1.freebsd.org (Postfix) with ESMTP id B42018FC17 for ; Tue, 28 Feb 2012 14:39:08 +0000 (UTC) Received: from jeep.localnet (unknown [IPv6:2001:4200:7000:3:223:aeff:fea7:a3c2]) by marge.meraka.csir.co.za (Postfix) with ESMTP id C2EA8D0CC3C for ; Tue, 28 Feb 2012 16:39:05 +0200 (SAST) From: Johann Hugo Date: Tue, 28 Feb 2012 16:39:05 +0200 User-Agent: KMail/1.13.7 (FreeBSD/9.0-RELEASE; KDE/4.7.3; amd64; ; ) X-KMail-Markup: true MIME-Version: 1.0 To: freebsd-wireless@freebsd.org Message-Id: <201202281639.05140.jhugo@meraka.csir.co.za> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: performance in adhoc mode X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 28 Feb 2012 14:39:10 -0000 Hi I get lower throuputs in adhoc mode, compared to AP/client mode for the same two devices. Is there anything special that I need to configure in adhoc mode to get the same throughput. AP -> client iperf 27.2 MBytes 28.8 Mbits/sec adhoc -> adhoc iperf 12.1 MBytes 21.3 Mbits/sec The two devices are directly next to each other in the LAB HW platform = Gateworks Avila GW2348-4 Wifi adapters = Compex WLM54AGP23 Atheros driver from +- 10 Jan 2012 OS = FreeBSD 9.0-STABLE ------------------------------------------------------------------------------------------ Adhoc mode: ------------------------------------------------------------------------------------------ Device A - rc.conf: hostname="mesh-2893" wlans_ath0="wlan0" create_args_wlan0="wlanmode adhoc country ZA" ifconfig_wlan0="192.168.1.1/24 mode 11a ssid mesh channel 136 bssid 00:80:48:4f:28:90" Device B - rc.conf: hostname="mesh-2870" wlans_ath0="wlan0" create_args_wlan0="wlanmode adhoc country ZA" ifconfig_wlan0="192.168.1.2/24 mode 11a ssid mesh channel 136 bssid 00:80:48:4f:28:90" mesh-2893:~ # iperf -s ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 64.0 KByte (default) ------------------------------------------------------------ [ 4] local 192.168.1.1 port 5001 connected with 192.168.1.2 port 40262 [ ID] Interval Transfer Bandwidth [ 4] 0.0-10.2 sec 26.0 MBytes 21.3 Mbits/sec mesh-2870:~ # iperf -c 192.168.1.1 ------------------------------------------------------------ Client connecting to 192.168.1.1, TCP port 5001 TCP window size: 32.5 KByte (default) ------------------------------------------------------------ [ 3] local 192.168.1.2 port 40262 connected with 192.168.1.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 26.0 MBytes 21.7 Mbits/sec ------------------------------------------------------------------------------------------- AP/client mode: ------------------------------------------------------------------------------------------- Device A - rc.conf: hostname="mesh-2893" wlans_ath0="wlan0" create_args_wlan0="wlanmode hostap country ZA" ifconfig_wlan0="192.168.1.1/24 mode 11a ssid testAP channel 136" Device B - rc.conf: hostname="mesh-2870" wlans_ath0="wlan0" create_args_wlan0="wlanmode sta country ZA" ifconfig_wlan0="192.168.1.2/24 mode 11a ssid testAP" mesh-2893:~ # iperf -s ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 64.0 KByte (default) ------------------------------------------------------------ [ 4] local 192.168.1.1 port 5001 connected with 192.168.1.2 port 45379 [ ID] Interval Transfer Bandwidth [ 4] 0.0-10.1 sec 34.8 MBytes 28.8 Mbits/sec mesh-2870:~ # iperf -c 192.168.1.1 ------------------------------------------------------------ Client connecting to 192.168.1.1, TCP port 5001 TCP window size: 32.5 KByte (default) ------------------------------------------------------------ [ 3] local 192.168.1.2 port 45379 connected with 192.168.1.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.1 sec 34.8 MBytes 29.0 Mbits/sec Regards Johann From owner-freebsd-wireless@FreeBSD.ORG Tue Feb 28 15:50:41 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0B356106564A for ; Tue, 28 Feb 2012 15:50:41 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8EF148FC0C for ; Tue, 28 Feb 2012 15:50:40 +0000 (UTC) Received: by wibhn6 with SMTP id hn6so2208350wib.13 for ; Tue, 28 Feb 2012 07:50:39 -0800 (PST) Received-SPF: pass (google.com: domain of adrian.chadd@gmail.com designates 10.216.133.151 as permitted sender) client-ip=10.216.133.151; Authentication-Results: mr.google.com; spf=pass (google.com: domain of adrian.chadd@gmail.com designates 10.216.133.151 as permitted sender) smtp.mail=adrian.chadd@gmail.com; dkim=pass header.i=adrian.chadd@gmail.com Received: from mr.google.com ([10.216.133.151]) by 10.216.133.151 with SMTP id q23mr5955411wei.14.1330444239791 (num_hops = 1); Tue, 28 Feb 2012 07:50:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=LaZzXcrGtlGtOqu3Ee3ozdsnZJ849uGqKeF27zX+d1Q=; b=BP0jDbZg2Qa/SBNI9Bv+36e5TMaJLXtRDXhx1zgEfVPFBf3E7TWmwO7jdAALWagNbw 3pkAP2gsAvPqN0bfKFgBxKrtjaxmw6vg0KxER6t/2Yp6NDjpCykUpRTQlTCtoFBhPNUg 8/jdghBVdJBytjOEKH+jYkd+yIRjWTy8aN/5A= MIME-Version: 1.0 Received: by 10.216.133.151 with SMTP id q23mr4724317wei.14.1330444239684; Tue, 28 Feb 2012 07:50:39 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.198.81 with HTTP; Tue, 28 Feb 2012 07:50:39 -0800 (PST) In-Reply-To: <201202281639.05140.jhugo@meraka.csir.co.za> References: <201202281639.05140.jhugo@meraka.csir.co.za> Date: Tue, 28 Feb 2012 07:50:39 -0800 X-Google-Sender-Auth: GxsJNKUy1vDiJkphqu0P9nObi04 Message-ID: From: Adrian Chadd To: Johann Hugo Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: performance in adhoc mode X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 28 Feb 2012 15:50:41 -0000 I've not looked into adhoc _at all_. I'd start by looking at the behaviour of the rate control code - do 'sysctl dev.ath.X sample_stats=3D1' after you've done some traffic and check dmesg. Just ensure that the same rates are being used and the error rate is low. Adrian On 28 February 2012 06:39, Johann Hugo wrote: > Hi > > I get lower throuputs in adhoc mode, compared to AP/client mode for > the same two devices. Is there anything special that I need to configure = in > adhoc mode to get the same throughput. > > AP -> client =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0iperf =A0 27.2 MBytes= =A028.8 Mbits/sec > adhoc -> adhoc =A0 =A0 =A0 =A0 =A0iperf =A0 12.1 MBytes =A021.3 Mbits/sec > > The two devices are directly next to each other in the LAB > HW platform =3D Gateworks Avila GW2348-4 > Wifi adapters =3D Compex WLM54AGP23 > Atheros driver from +- 10 Jan 2012 > OS =3D FreeBSD 9.0-STABLE > > -------------------------------------------------------------------------= ----------------- > Adhoc mode: > -------------------------------------------------------------------------= ----------------- > Device A - rc.conf: > hostname=3D"mesh-2893" > wlans_ath0=3D"wlan0" > create_args_wlan0=3D"wlanmode adhoc country ZA" > ifconfig_wlan0=3D"192.168.1.1/24 mode 11a ssid mesh channel 136 bssid > 00:80:48:4f:28:90" > > Device B - rc.conf: > hostname=3D"mesh-2870" > wlans_ath0=3D"wlan0" > create_args_wlan0=3D"wlanmode adhoc country ZA" > ifconfig_wlan0=3D"192.168.1.2/24 mode 11a ssid mesh channel 136 bssid > 00:80:48:4f:28:90" > > mesh-2893:~ # iperf -s > ------------------------------------------------------------ > Server listening on TCP port 5001 > TCP window size: 64.0 KByte (default) > ------------------------------------------------------------ > [ =A04] local 192.168.1.1 port 5001 connected with 192.168.1.2 port 40262 > [ ID] Interval =A0 =A0 =A0 Transfer =A0 =A0 Bandwidth > [ =A04] =A00.0-10.2 sec =A026.0 MBytes =A021.3 Mbits/sec > > mesh-2870:~ # iperf -c 192.168.1.1 > ------------------------------------------------------------ > Client connecting to 192.168.1.1, TCP port 5001 > TCP window size: 32.5 KByte (default) > ------------------------------------------------------------ > [ =A03] local 192.168.1.2 port 40262 connected with 192.168.1.1 port 5001 > [ ID] Interval =A0 =A0 =A0 Transfer =A0 =A0 Bandwidth > [ =A03] =A00.0-10.0 sec =A026.0 MBytes =A021.7 Mbits/sec > > > > -------------------------------------------------------------------------= ------------------ > AP/client mode: > -------------------------------------------------------------------------= ------------------ > Device A - rc.conf: > hostname=3D"mesh-2893" > wlans_ath0=3D"wlan0" > create_args_wlan0=3D"wlanmode hostap country ZA" > ifconfig_wlan0=3D"192.168.1.1/24 mode 11a ssid testAP channel 136" > > Device B - rc.conf: > hostname=3D"mesh-2870" > wlans_ath0=3D"wlan0" > create_args_wlan0=3D"wlanmode sta country ZA" > ifconfig_wlan0=3D"192.168.1.2/24 mode 11a ssid testAP" > > > mesh-2893:~ # iperf -s > ------------------------------------------------------------ > Server listening on TCP port 5001 > TCP window size: 64.0 KByte (default) > ------------------------------------------------------------ > [ =A04] local 192.168.1.1 port 5001 connected with 192.168.1.2 port 45379 > [ ID] Interval =A0 =A0 =A0 Transfer =A0 =A0 Bandwidth > [ =A04] =A00.0-10.1 sec =A034.8 MBytes =A028.8 Mbits/sec > > mesh-2870:~ # iperf -c 192.168.1.1 > ------------------------------------------------------------ > Client connecting to 192.168.1.1, TCP port 5001 > TCP window size: 32.5 KByte (default) > ------------------------------------------------------------ > [ =A03] local 192.168.1.2 port 45379 connected with 192.168.1.1 port 5001 > [ ID] Interval =A0 =A0 =A0 Transfer =A0 =A0 Bandwidth > [ =A03] =A00.0-10.1 sec =A034.8 MBytes =A029.0 Mbits/sec > > Regards > Johann > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.or= g" From owner-freebsd-wireless@FreeBSD.ORG Tue Feb 28 19:01:30 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 15BF1106564A for ; Tue, 28 Feb 2012 19:01:30 +0000 (UTC) (envelope-from uzimac@da3m0n8t3r.com) Received: from z.umatar.com (z.umatar.com [66.135.39.87]) by mx1.freebsd.org (Postfix) with ESMTP id DB9B88FC08 for ; Tue, 28 Feb 2012 19:01:29 +0000 (UTC) Received: from z.umatar.com (localhost [127.0.0.1]) by z.umatar.com (8.14.5/8.14.3) with ESMTP id q1SJ1TCg099915 for ; Tue, 28 Feb 2012 11:01:29 -0800 (PST) (envelope-from uzimac@da3m0n8t3r.com) Received: (from uzimac@localhost) by z.umatar.com (8.14.5/8.14.3/Submit) id q1SJ1TaC099914 for freebsd-wireless@freebsd.org; Tue, 28 Feb 2012 11:01:29 -0800 (PST) (envelope-from uzimac@da3m0n8t3r.com) X-Authentication-Warning: z.umatar.com: uzimac set sender to uzimac@da3m0n8t3r.com using -f From: "Waitman Gobble" To: freebsd-wireless@freebsd.org Message-Id: <1330455688.99908@da3m0n8t3r.com> X-Originating-IP: 70.90.171.37 X-Mailer: Usermin 1.500 Date: Tue, 28 Feb 2012 11:01:29 -0800 (PST) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="bound1330455689" Subject: troubleshooting Atheros 9280 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 28 Feb 2012 19:01:30 -0000 This is a multi-part message in MIME format. --bound1330455689 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Hi, I have an Atheros 9280 that 'connects sometimes', could be a bad card. (?) here's syslog entries: ath0: mem 0xf01000000-0xf010fff irq 19 at device 0.0 on pic7 ath0: [HT] enabling HT modes ath0: [HT] 2 RS streams: 2 TX streams ath0: AR9280 mac 128.2 RF5133 phy 13.0 ath0: 2GHz radio: 0x00; 5GHz radio: 0x00c0 ath0: ath_reset_grablock: didn't finish after 10 iterations ath0: ath_reset_grablock: warning, recursive reset path! ath0: ath_chan_set: concurrent reset! Danger! ath0: ath_start: sc_inreset_cnt > 0; bailing I have not yet been able to get this card connected to 5GHz/HT40. but "usually" 11g works. Today it's being super-stubborn. :) I noticed if i do ifconfig the channel "floats" all over the woodshed. in 11g mode it's bumping around from 2 to 12, 11a mode from 2 to 169 (i think). Seems like it settles eventually and connects. Any troubleshooting tips/help appreciated. Thanks, -- Waitman Gobble San Jose California USA --bound1330455689-- From owner-freebsd-wireless@FreeBSD.ORG Tue Feb 28 19:27:23 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F1BFA1065673 for ; Tue, 28 Feb 2012 19:27:23 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 8178E8FC15 for ; Tue, 28 Feb 2012 19:27:23 +0000 (UTC) Received: by wgbds12 with SMTP id ds12so2229756wgb.31 for ; Tue, 28 Feb 2012 11:27:22 -0800 (PST) Received-SPF: pass (google.com: domain of adrian.chadd@gmail.com designates 10.181.11.227 as permitted sender) client-ip=10.181.11.227; Authentication-Results: mr.google.com; spf=pass (google.com: domain of adrian.chadd@gmail.com designates 10.181.11.227 as permitted sender) smtp.mail=adrian.chadd@gmail.com; dkim=pass header.i=adrian.chadd@gmail.com Received: from mr.google.com ([10.181.11.227]) by 10.181.11.227 with SMTP id el3mr41622487wid.18.1330457242487 (num_hops = 1); Tue, 28 Feb 2012 11:27:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=RrxwHDZQdvoAHjRFEeOz7g56oQpvNbAvO8LdvpO6b7k=; b=KvlFUUW/fZyZ2eDN6z2yfmx5x5umaQBbfmN3d1KVSmfRT1m0svUR6rP5qUsVv+hfOr JAsX/ghIEktsnPLp8qQDeKU13ru5lbclkgHg0AOhY1bB9TaRputN7b9EXHcq7TkmLMFS esv9RgERjFZXDnXwsPV1Ft2Bp9ID569awwkt4= MIME-Version: 1.0 Received: by 10.181.11.227 with SMTP id el3mr32984784wid.18.1330457242367; Tue, 28 Feb 2012 11:27:22 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.198.81 with HTTP; Tue, 28 Feb 2012 11:27:22 -0800 (PST) In-Reply-To: <1330455688.99908@da3m0n8t3r.com> References: <1330455688.99908@da3m0n8t3r.com> Date: Tue, 28 Feb 2012 11:27:22 -0800 X-Google-Sender-Auth: j7Gl-vA4IOmxxHPPTfQG8wAPlKs Message-ID: From: Adrian Chadd To: Waitman Gobble Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: troubleshooting Atheros 9280 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 28 Feb 2012 19:27:24 -0000 Ah, someone who lives close to me! That dramatically increases the chances of fixing this issue! On 28 February 2012 11:01, Waitman Gobble wrote: > Hi, > > > I have an Atheros 9280 that 'connects sometimes', could be a bad card. (?) > Does this happen at home? I think the driver getting confused is your problem, but it's likely being confused and stubborn because of a noisy environment. Ie, things taking too long to happen and increasing the chances of the overlapping reset/channel change that you're seeing. > here's syslog entries: > > ath0: mem 0xf01000000-0xf010fff irq 19 at device 0.0 on pic7 > ath0: [HT] enabling HT modes > ath0: [HT] 2 RS streams: 2 TX streams > ath0: AR9280 mac 128.2 RF5133 phy 13.0 > ath0: 2GHz radio: 0x00; 5GHz radio: 0x00c0 > ath0: ath_reset_grablock: didn't finish after 10 iterations > ath0: ath_reset_grablock: warning, recursive reset path! > ath0: ath_chan_set: concurrent reset! Danger! > ath0: ath_start: sc_inreset_cnt > 0; bailing > Does this happen often? This particular set of messages? adrian > > I have not yet been able to get this card connected to 5GHz/HT40. but "usually" 11g works. Today it's being super-stubborn. :) > > I noticed if i do ifconfig the channel "floats" all over the woodshed. in 11g mode it's bumping around from 2 to 12, 11a mode from 2 to 169 (i think). Seems like it settles eventually and connects. > > Any troubleshooting tips/help appreciated. > Thanks, > > > -- > Waitman Gobble > San Jose California USA > > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" > From owner-freebsd-wireless@FreeBSD.ORG Tue Feb 28 19:52:07 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 19311106566B; Tue, 28 Feb 2012 19:52:06 +0000 (UTC) (envelope-from uzimac@da3m0n8t3r.com) Received: from z.umatar.com (z.umatar.com [66.135.39.87]) by mx1.freebsd.org (Postfix) with ESMTP id 89A878FC0A; Tue, 28 Feb 2012 19:52:06 +0000 (UTC) Received: from z.umatar.com (localhost [127.0.0.1]) by z.umatar.com (8.14.5/8.14.3) with ESMTP id q1SJq5Mg066371; Tue, 28 Feb 2012 11:52:05 -0800 (PST) (envelope-from uzimac@da3m0n8t3r.com) Received: (from uzimac@localhost) by z.umatar.com (8.14.5/8.14.3/Submit) id q1SJq5hc066370; Tue, 28 Feb 2012 11:52:05 -0800 (PST) (envelope-from uzimac@da3m0n8t3r.com) X-Authentication-Warning: z.umatar.com: uzimac set sender to uzimac@da3m0n8t3r.com using -f From: "Waitman Gobble" To: Adrian Chadd Message-Id: <1330458725.66365@da3m0n8t3r.com> X-Originating-IP: 70.90.171.37 X-Mailer: Usermin 1.500 In-Reply-To: Date: Tue, 28 Feb 2012 11:52:05 -0800 (PST) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="bound1330458725" Cc: freebsd-wireless@freebsd.org Subject: Re: troubleshooting Atheros 9280 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 28 Feb 2012 19:52:07 -0000 This is a multi-part message in MIME format. --bound1330458725 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Adrian Chadd wrote .. > Ah, someone who lives close to me! That dramatically increases the > chances of fixing this issue! > > On 28 February 2012 11:01, Waitman Gobble wrote: > > Hi, > > > > > > I have an Atheros 9280 that 'connects sometimes', could be a bad card. (?) > > > > Does this happen at home? > > I think the driver getting confused is your problem, but it's likely > being confused and stubborn because of a noisy environment. Ie, things > taking too long to happen and increasing the chances of the > overlapping reset/channel change that you're seeing. > > > here's syslog entries: > > > > ath0: mem 0xf01000000-0xf010fff irq 19 at device 0.0 on pic7 > > ath0: [HT] enabling HT modes > > ath0: [HT] 2 RS streams: 2 TX streams > > ath0: AR9280 mac 128.2 RF5133 phy 13.0 > > ath0: 2GHz radio: 0x00; 5GHz radio: 0x00c0 > > ath0: ath_reset_grablock: didn't finish after 10 iterations > > ath0: ath_reset_grablock: warning, recursive reset path! > > ath0: ath_chan_set: concurrent reset! Danger! > > ath0: ath_start: sc_inreset_cnt > 0; bailing > > > > Does this happen often? This particular set of messages? > > > > adrian > > > > > I have not yet been able to get this card connected to 5GHz/HT40. but "usually" > 11g works. Today it's being super-stubborn. :) > > > > I noticed if i do ifconfig the channel "floats" all over the woodshed. in 11g > mode it's bumping around from 2 to 12, 11a mode from 2 to 169 (i think). Seems > like it settles eventually and connects. > > > > Any troubleshooting tips/help appreciated. > > Thanks, > > > > > > -- > > Waitman Gobble > > San Jose California USA > > > > _______________________________________________ > > freebsd-wireless@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" > > Hi Adrian, Thanks for the prompt reply. Those messages are happening often on this machine. I have some other Atheros cards to try (maybe another 9280) and have a 1/2 height one on order. This machine is made for a 1/2 height BC card but i ripped it out and have the full size Atheros 9280 taped in place. :) Sometimes this also happens on another machine with a 9280, but only occasionally. Same thing, seems like it can't find the channel for awhile. ifconfig shows it all over the place. That's happened at home in San Jose, which could be kinda noisy I suppose. But also in office in Los Altos Hills where it's not seemingly so noisy. -- Waitman Gobble San Jose California USA --bound1330458725-- From owner-freebsd-wireless@FreeBSD.ORG Tue Feb 28 22:49:37 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8837B1065834 for ; Tue, 28 Feb 2012 22:49:37 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id BDF0F8FC16 for ; Tue, 28 Feb 2012 22:49:33 +0000 (UTC) Received: by lagz14 with SMTP id z14so10347150lag.13 for ; Tue, 28 Feb 2012 14:49:32 -0800 (PST) Received-SPF: pass (google.com: domain of fernando.apesteguia@gmail.com designates 10.152.147.1 as permitted sender) client-ip=10.152.147.1; Authentication-Results: mr.google.com; spf=pass (google.com: domain of fernando.apesteguia@gmail.com designates 10.152.147.1 as permitted sender) smtp.mail=fernando.apesteguia@gmail.com; dkim=pass header.i=fernando.apesteguia@gmail.com Received: from mr.google.com ([10.152.147.1]) by 10.152.147.1 with SMTP id tg1mr17819030lab.22.1330469372954 (num_hops = 1); Tue, 28 Feb 2012 14:49:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=Kz03P31T6og82ktZ9h0UsixwCMlgoqS+wpwm4NkiinE=; b=fJiw0ttD/Qv69WI+q5hz8s4HNWxqt9+tv6dH6mXx8r/SuryLFaqVgojGbnRp6Z11Ou aWSgY5Z6ImnqpsTUm+bpKfNr/mYbaUeHjvpzDN65lMGOXZvw8mNlEhgogPk0iOh76C27 HRRZ4L2MHmexnh8PI4Z5Q0iElYUFwv5U1k4Fk= MIME-Version: 1.0 Received: by 10.152.147.1 with SMTP id tg1mr14736998lab.22.1330467613281; Tue, 28 Feb 2012 14:20:13 -0800 (PST) Received: by 10.152.13.72 with HTTP; Tue, 28 Feb 2012 14:20:13 -0800 (PST) Date: Tue, 28 Feb 2012 23:20:13 +0100 Message-ID: From: =?ISO-8859-1?Q?Fernando_Apestegu=EDa?= To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: iwi firmware X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 28 Feb 2012 22:49:37 -0000 Hi all, I recently installed 9.0-RELEASE on my old laptop. I used the ipw2200 card in this laptop with 8.2-RELEASE without problems. However I have missed something I can't figure out. I get the message: iwi0: timeout processing command blocks for iwi_bss firmware iwi0: could not load main firmware iwi_bss This is what I have in my loader.conf: # Agree Intel's agreement license legal.intel_iwi.license_ack=1 # wireless support #if_iwi_load="YES" This is in kernel now... wlan_load="YES" firmware_load="YES" iwi_bss_load="YES" iwi_ibss_load="YES" iwi_monitor_load="YES" what am I missing? Thanks in advance. From owner-freebsd-wireless@FreeBSD.ORG Wed Feb 29 06:56:29 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 59458106566B; Wed, 29 Feb 2012 06:56:29 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2CBE48FC08; Wed, 29 Feb 2012 06:56:29 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q1T6uTbb083272; Wed, 29 Feb 2012 06:56:29 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q1T6uTkO083268; Wed, 29 Feb 2012 06:56:29 GMT (envelope-from linimon) Date: Wed, 29 Feb 2012 06:56:29 GMT Message-Id: <201202290656.q1T6uTkO083268@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/165543: [ath] ath0 endless scanning of channels without connect - Atheros 9280 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 29 Feb 2012 06:56:29 -0000 Old Synopsis: ath0 endless scanning of channels without connect - Atheros 9280 New Synopsis: [ath] ath0 endless scanning of channels without connect - Atheros 9280 Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Wed Feb 29 06:56:16 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=165543 From owner-freebsd-wireless@FreeBSD.ORG Wed Feb 29 09:09:45 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3BC81106566B for ; Wed, 29 Feb 2012 09:09:45 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id B21F28FC0C for ; Wed, 29 Feb 2012 09:09:44 +0000 (UTC) Received: by lagv3 with SMTP id v3so247967lag.13 for ; Wed, 29 Feb 2012 01:09:43 -0800 (PST) Received-SPF: pass (google.com: domain of bschmidt@techwires.net designates 10.152.136.36 as permitted sender) client-ip=10.152.136.36; Authentication-Results: mr.google.com; spf=pass (google.com: domain of bschmidt@techwires.net designates 10.152.136.36 as permitted sender) smtp.mail=bschmidt@techwires.net Received: from mr.google.com ([10.152.136.36]) by 10.152.136.36 with SMTP id px4mr15112892lab.47.1330506583583 (num_hops = 1); Wed, 29 Feb 2012 01:09:43 -0800 (PST) MIME-Version: 1.0 Received: by 10.152.136.36 with SMTP id px4mr12669964lab.47.1330506583484; Wed, 29 Feb 2012 01:09:43 -0800 (PST) Received: by 10.152.22.231 with HTTP; Wed, 29 Feb 2012 01:09:43 -0800 (PST) X-Originating-IP: [79.140.39.245] In-Reply-To: References: Date: Wed, 29 Feb 2012 10:09:43 +0100 Message-ID: From: Bernhard Schmidt To: =?ISO-8859-1?Q?Fernando_Apestegu=EDa?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQlfcY7GEdCqnbBtdQiJFFzAf1EJa+UWpIFaGQrNPYECRZdliXIOToV3dUcZlQslupiX0mKK Cc: freebsd-wireless@freebsd.org Subject: Re: iwi firmware X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 29 Feb 2012 09:09:45 -0000 On Tue, Feb 28, 2012 at 23:20, Fernando Apestegu=EDa wrote: > Hi all, > > I recently installed 9.0-RELEASE on my old laptop. I used the ipw2200 car= d > in this laptop with 8.2-RELEASE without problems. However I have missed > something I can't figure out. I get the message: > > iwi0: timeout processing command blocks for iwi_bss firmware > iwi0: could not load main firmware iwi_bss > > This is what I have in my loader.conf: > > # Agree Intel's agreement license > legal.intel_iwi.license_ack=3D1 > > # wireless support > #if_iwi_load=3D"YES" =A0 =A0 =A0This is in kernel now... > wlan_load=3D"YES" > firmware_load=3D"YES" > > iwi_bss_load=3D"YES" > iwi_ibss_load=3D"YES" > iwi_monitor_load=3D"YES" > > what am I missing? > > Thanks in advance. Hmm, there haven't been any major changes to iwi(4) between 8.2 and 9.0, except what you've already noticed. You could try to remove iwi(4) from the kernel config and use it as module again, just to make sure it isn't related to that. Also, all modules iwi(4) depends on are pulled in automatically, even the firmware modules, no need to load em through loader.conf. Can you post dmesg and pciconf -lvc? --=20 Bernhard From owner-freebsd-wireless@FreeBSD.ORG Wed Feb 29 09:51:17 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 43813106564A; Wed, 29 Feb 2012 09:51:17 +0000 (UTC) (envelope-from jhugo@meraka.csir.co.za) Received: from marge.meraka.csir.co.za (marge.meraka.csir.co.za [IPv6:2001:4200:7000:3::1]) by mx1.freebsd.org (Postfix) with ESMTP id AB80E8FC1B; Wed, 29 Feb 2012 09:51:13 +0000 (UTC) Received: from jeep.localnet (unknown [IPv6:2001:4200:7000:3:223:aeff:fea7:a3c2]) by marge.meraka.csir.co.za (Postfix) with ESMTP id 0F5C7D0CC26; Wed, 29 Feb 2012 11:51:11 +0200 (SAST) From: Johann Hugo To: Adrian Chadd Date: Wed, 29 Feb 2012 11:51:10 +0200 User-Agent: KMail/1.13.7 (FreeBSD/9.0-RELEASE; KDE/4.7.3; amd64; ; ) References: <201202281639.05140.jhugo@meraka.csir.co.za> In-Reply-To: X-KMail-Markup: true MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_OUfTPmYoHjNrT+o" Message-Id: <201202291151.10365.jhugo@meraka.csir.co.za> X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: Re: performance in adhoc mode X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 29 Feb 2012 09:51:17 -0000 --Boundary-00=_OUfTPmYoHjNrT+o Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit On Tuesday 28 February 2012 17:50:39 Adrian Chadd wrote: > I've not looked into adhoc _at all_. please_do > > I'd start by looking at the behaviour of the rate control code - do > 'sysctl dev.ath.X sample_stats=1' after you've done some traffic and > check dmesg. > > Just ensure that the same rates are being used and the error rate is low. > The rates differ a bit and also some of the dev.ath.0 sysctl's. dev.ath.0.stats.ast_tx_longretry is more than double in adhoc mode. Johann --Boundary-00=_OUfTPmYoHjNrT+o Content-Type: text/plain; charset="UTF-8"; name="nodeA-ADHOCmode.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="nodeA-ADHOCmode.txt" mesh-2893:~ # ifconfig wlan0 wlan0: flags=8843 metric 0 mtu 1500 ether 00:80:48:4f:28:93 inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 inet6 fe80::280:48ff:fe4f:2893%wlan0 prefixlen 64 scopeid 0x8 nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11a status: running ssid mesh channel 136 (5680 MHz 11a) bssid 00:80:48:4f:28:90 regdomain NONE country ZA ecm authmode OPEN privacy OFF txpower 24 mcastrate 6 mgmtrate 6 scanvalid 60 wme burst mesh-2893:~ # ifconfig wlan0 list sta ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG 00:80:48:4f:28:70 1 136 54M 18.0 15 16999 11936 E AQ WME mesh-2893:~ # iperf -s ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 64.0 KByte (default) ------------------------------------------------------------ [ 4] local 192.168.1.1 port 5001 connected with 192.168.1.2 port 18158 [ ID] Interval Transfer Bandwidth [ 4] 0.0-10.2 sec 24.9 MBytes 20.5 Mbits/sec mesh-2893:~ # sysctl dev.ath.0.sample_stats=1 dev.ath.0.sample_stats: 0 [00:80:48:4f:28:93] refcnt 4 static_rix 0 ratemask 0x0 [ 250] cur rix 0 (6 Mb ) since switch: packets 0 ticks 0 [ 250] last sample 0 cur sample 0 packets sent 0 [ 250] packets since sample 0 sample tt 0 [1600] cur rix 0 (6 Mb ) since switch: packets 0 ticks 0 [1600] last sample 0 cur sample 0 packets sent 0 [1600] packets since sample 0 sample tt 0 [00:80:48:4f:28:70] refcnt 3 static_rix -1 ratemask 0xff [ 250] cur rix 7 (54 Mb ) since switch: packets 90 ticks 6589 [ 250] last sample 5 cur sample -1 packets sent 12503 [ 250] packets since sample 3 sample tt 464 [1600] cur rix 0 (6 Mb ) since switch: packets 0 ticks 0 [1600] last sample 0 cur sample -1 packets sent 0 [1600] packets since sample 0 sample tt 0 [12 Mb : 250] 30:30 (100%) T 33 F 0 avg 679 last 775 [18 Mb : 250] 107:107 (100%) T 116 F 0 avg 578 last 732 [24 Mb : 250] 1278:1278 (100%) T 1400 F 0 avg 594 last 729 [36 Mb : 250] 2522:2521 ( 99%) T 2817 F 0 avg 518 last 726 [36 Mb :1600] 1:0 ( 0%) T 5 F 1 avg 764 last 740 [48 Mb : 250] 5855:5853 ( 99%) T 6496 F 0 avg 534 last 729 [48 Mb :1600] 2:0 ( 0%) T 10 F 2 avg 672 last 956 [54 Mb : 250] 2713:2713 (100%) T 2982 F 0 avg 475 last 727 mesh-2893:~ # sysctl dev.ath.0 dev.ath.0.%desc: Atheros 5413 dev.ath.0.%driver: ath dev.ath.0.%location: slot=1 function=0 dev.ath.0.%pnpinfo: vendor=0x168c device=0x001b subvendor=0x168c subdevice=0x2063 class=0x020000 dev.ath.0.%parent: pci0 dev.ath.0.smoothing_rate: 95 dev.ath.0.sample_rate: 10 dev.ath.0.sample_stats: 0 dev.ath.0.countrycode: 0 dev.ath.0.regdomain: 0 dev.ath.0.debug: 0 dev.ath.0.slottime: 9 dev.ath.0.acktimeout: 25 dev.ath.0.ctstimeout: 25 dev.ath.0.softled: 0 dev.ath.0.ledpin: 0 dev.ath.0.ledon: 0 dev.ath.0.ledidle: 270 dev.ath.0.txantenna: 1 dev.ath.0.rxantenna: 1 dev.ath.0.diversity: 0 dev.ath.0.txintrperiod: 5 dev.ath.0.diag: 0 dev.ath.0.tpscale: 0 dev.ath.0.tpc: 0 dev.ath.0.tpack: 63 dev.ath.0.tpcts: 63 dev.ath.0.intmit: 1 dev.ath.0.monpass: 24 dev.ath.0.dbaprep: 2 dev.ath.0.swbaprep: 10 dev.ath.0.guardtime: 0 dev.ath.0.superframe: 0 dev.ath.0.setcca: 0 dev.ath.0.clear_stats: 0 dev.ath.0.stats.ast_watchdog: 0 dev.ath.0.stats.ast_hardware: 0 dev.ath.0.stats.ast_bmiss: 0 dev.ath.0.stats.ast_bmiss_phantom: 0 dev.ath.0.stats.ast_bstuck: 0 dev.ath.0.stats.ast_rxorn: 0 dev.ath.0.stats.ast_rxeol: 0 dev.ath.0.stats.ast_txurn: 0 dev.ath.0.stats.ast_mib: 0 dev.ath.0.stats.ast_intrcoal: 0 dev.ath.0.stats.ast_tx_packets: 0 dev.ath.0.stats.ast_tx_mgmt: 0 dev.ath.0.stats.ast_tx_discard: 0 dev.ath.0.stats.ast_tx_qstop: 0 dev.ath.0.stats.ast_tx_encap: 0 dev.ath.0.stats.ast_tx_nonode: 0 dev.ath.0.stats.ast_tx_nombuf: 0 dev.ath.0.stats.ast_tx_nomcl: 0 dev.ath.0.stats.ast_tx_linear: 0 dev.ath.0.stats.ast_tx_nodata: 0 dev.ath.0.stats.ast_tx_busdma: 0 dev.ath.0.stats.ast_tx_xretries: 3 dev.ath.0.stats.ast_tx_fifoerr: 0 dev.ath.0.stats.ast_tx_filtered: 0 dev.ath.0.stats.ast_tx_shortretry: 0 dev.ath.0.stats.ast_tx_longretry: 1352 dev.ath.0.stats.ast_tx_badrate: 0 dev.ath.0.stats.ast_tx_noack: 1 dev.ath.0.stats.ast_tx_rts: 0 dev.ath.0.stats.ast_tx_cts: 0 dev.ath.0.stats.ast_tx_shortpre: 0 dev.ath.0.stats.ast_tx_altrate: 3 dev.ath.0.stats.ast_tx_protect: 0 dev.ath.0.stats.ast_tx_ctsburst: 0 dev.ath.0.stats.ast_tx_ctsext: 0 dev.ath.0.stats.ast_rx_nombuf: 0 dev.ath.0.stats.ast_rx_busdma: 0 dev.ath.0.stats.ast_rx_orn: 0 dev.ath.0.stats.ast_rx_crcerr: 120 dev.ath.0.stats.ast_rx_fifoerr: 0 dev.ath.0.stats.ast_rx_badcrypt: 0 dev.ath.0.stats.ast_rx_badmic: 0 dev.ath.0.stats.ast_rx_phyerr: 0 dev.ath.0.stats.ast_rx_tooshort: 0 dev.ath.0.stats.ast_rx_toobig: 0 dev.ath.0.stats.ast_rx_packets: 0 dev.ath.0.stats.ast_rx_mgt: 0 dev.ath.0.stats.ast_rx_ctl: 0 dev.ath.0.stats.ast_be_xmit: 0 dev.ath.0.stats.ast_be_nombuf: 0 dev.ath.0.stats.ast_per_cal: 2 dev.ath.0.stats.ast_per_calfail: 0 dev.ath.0.stats.ast_per_rfgain: 1 dev.ath.0.stats.ast_rate_calls: 0 dev.ath.0.stats.ast_rate_raise: 0 dev.ath.0.stats.ast_rate_drop: 0 dev.ath.0.stats.ast_ant_defswitch: 0 dev.ath.0.stats.ast_ant_txswitch: 0 dev.ath.0.stats.ast_cabq_xmit: 0 dev.ath.0.stats.ast_cabq_busy: 0 dev.ath.0.stats.ast_tx_raw: 6 dev.ath.0.stats.ast_ff_txok: 0 dev.ath.0.stats.ast_ff_txerr: 0 dev.ath.0.stats.ast_ff_rx: 0 dev.ath.0.stats.ast_ff_flush: 0 dev.ath.0.stats.ast_tx_qfull: 0 dev.ath.0.stats.ast_tx_nobuf: 0 dev.ath.0.stats.ast_tdma_update: 0 dev.ath.0.stats.ast_tdma_timers: 0 dev.ath.0.stats.ast_tdma_tsf: 0 dev.ath.0.stats.ast_tdma_ack: 0 dev.ath.0.stats.ast_tx_raw_fail: 0 dev.ath.0.stats.ast_tx_nofrag: 0 dev.ath.0.stats.ast_be_missed: 0 dev.ath.0.stats.ast_ani_cal: 587 dev.ath.0.stats.ast_rx_agg: 0 dev.ath.0.stats.ast_rx_halfgi: 0 dev.ath.0.stats.ast_rx_2040: 0 dev.ath.0.stats.ast_rx_pre_crc_err: 0 dev.ath.0.stats.ast_rx_post_crc_err: 0 dev.ath.0.stats.ast_rx_decrypt_busy_err: 0 dev.ath.0.stats.ast_rx_hi_rx_chain: 0 dev.ath.0.stats.ast_tx_htprotect: 0 dev.ath.0.stats.ast_rx_hitqueueend: 0 dev.ath.0.stats.ast_tx_timeout: 0 dev.ath.0.stats.ast_tx_cst: 0 dev.ath.0.stats.ast_tx_xtxop: 0 dev.ath.0.stats.ast_tx_timerexpired: 0 dev.ath.0.stats.ast_tx_desccfgerr: 0 dev.ath.0.stats.rx_phy_err.0: 0 dev.ath.0.stats.rx_phy_err.1: 0 dev.ath.0.stats.rx_phy_err.2: 0 dev.ath.0.stats.rx_phy_err.3: 0 dev.ath.0.stats.rx_phy_err.4: 0 dev.ath.0.stats.rx_phy_err.5: 0 dev.ath.0.stats.rx_phy_err.6: 0 dev.ath.0.stats.rx_phy_err.7: 0 dev.ath.0.stats.rx_phy_err.8: 0 dev.ath.0.stats.rx_phy_err.9: 0 dev.ath.0.stats.rx_phy_err.10: 0 dev.ath.0.stats.rx_phy_err.11: 0 dev.ath.0.stats.rx_phy_err.12: 0 dev.ath.0.stats.rx_phy_err.13: 0 dev.ath.0.stats.rx_phy_err.14: 0 dev.ath.0.stats.rx_phy_err.15: 0 dev.ath.0.stats.rx_phy_err.16: 0 dev.ath.0.stats.rx_phy_err.17: 0 dev.ath.0.stats.rx_phy_err.18: 0 dev.ath.0.stats.rx_phy_err.19: 0 dev.ath.0.stats.rx_phy_err.20: 0 dev.ath.0.stats.rx_phy_err.21: 0 dev.ath.0.stats.rx_phy_err.22: 0 dev.ath.0.stats.rx_phy_err.23: 0 dev.ath.0.stats.rx_phy_err.24: 0 dev.ath.0.stats.rx_phy_err.25: 0 dev.ath.0.stats.rx_phy_err.26: 0 dev.ath.0.stats.rx_phy_err.27: 0 dev.ath.0.stats.rx_phy_err.28: 0 dev.ath.0.stats.rx_phy_err.29: 0 dev.ath.0.stats.rx_phy_err.30: 0 dev.ath.0.stats.rx_phy_err.31: 0 dev.ath.0.stats.rx_phy_err.32: 0 dev.ath.0.stats.rx_phy_err.33: 0 dev.ath.0.stats.rx_phy_err.34: 0 dev.ath.0.stats.rx_phy_err.35: 0 dev.ath.0.stats.rx_phy_err.36: 0 dev.ath.0.stats.rx_phy_err.37: 0 dev.ath.0.stats.rx_phy_err.38: 0 dev.ath.0.stats.rx_phy_err.39: 0 dev.ath.0.stats.rx_phy_err.40: 0 dev.ath.0.stats.rx_phy_err.41: 0 dev.ath.0.stats.rx_phy_err.42: 0 dev.ath.0.stats.rx_phy_err.43: 0 dev.ath.0.stats.rx_phy_err.44: 0 dev.ath.0.stats.rx_phy_err.45: 0 dev.ath.0.stats.rx_phy_err.46: 0 dev.ath.0.stats.rx_phy_err.47: 0 dev.ath.0.stats.rx_phy_err.48: 0 dev.ath.0.stats.rx_phy_err.49: 0 dev.ath.0.stats.rx_phy_err.50: 0 dev.ath.0.stats.rx_phy_err.51: 0 dev.ath.0.stats.rx_phy_err.52: 0 dev.ath.0.stats.rx_phy_err.53: 0 dev.ath.0.stats.rx_phy_err.54: 0 dev.ath.0.stats.rx_phy_err.55: 0 dev.ath.0.stats.rx_phy_err.56: 0 dev.ath.0.stats.rx_phy_err.57: 0 dev.ath.0.stats.rx_phy_err.58: 0 dev.ath.0.stats.rx_phy_err.59: 0 dev.ath.0.stats.rx_phy_err.60: 0 dev.ath.0.stats.rx_phy_err.61: 0 dev.ath.0.stats.rx_phy_err.62: 0 dev.ath.0.stats.rx_phy_err.63: 0 dev.ath.0.hal.debug: 0 dev.ath.0.hal.ar5416_biasadj: 0 dev.ath.0.hal.dma_brt: 2 dev.ath.0.hal.sw_brt: 10 dev.ath.0.hal.swba_backoff: 0 --Boundary-00=_OUfTPmYoHjNrT+o Content-Type: text/plain; charset="UTF-8"; name="nodeA-APmode.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="nodeA-APmode.txt" mesh-2893:~ # ifconfig wlan0 wlan0: flags=8843 metric 0 mtu 1500 ether 00:80:48:4f:28:93 inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 inet6 fe80::280:48ff:fe4f:2893%wlan0 prefixlen 64 scopeid 0x8 nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11a status: running ssid testAP channel 136 (5680 MHz 11a) bssid 00:80:48:4f:28:93 regdomain NONE country ZA ecm authmode OPEN privacy OFF txpower 24 mcastrate 6 mgmtrate 6 scanvalid 60 wme burst dtimperiod 1 -dfs mesh-2893:~ # ifconfig wlan0 list sta ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG 00:80:48:4f:28:70 1 136 48M 19.0 0 17082 14352 E AQ WME mesh-2893:~ # iperf -s ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 64.0 KByte (default) ------------------------------------------------------------ [ 4] local 192.168.1.1 port 5001 connected with 192.168.1.2 port 54772 [ ID] Interval Transfer Bandwidth [ 4] 0.0-10.2 sec 34.5 MBytes 28.5 Mbits/sec mesh-2893:~ # sysctl dev.ath.0.sample_stats=1 dev.ath.0.sample_stats: 0 [00:80:48:4f:28:93] refcnt 4 static_rix 0 ratemask 0x0 [ 250] cur rix 0 (6 Mb ) since switch: packets 0 ticks 0 [ 250] last sample 0 cur sample 0 packets sent 0 [ 250] packets since sample 0 sample tt 0 [1600] cur rix 0 (6 Mb ) since switch: packets 0 ticks 0 [1600] last sample 0 cur sample 0 packets sent 0 [1600] packets since sample 0 sample tt 0 [00:80:48:4f:28:70] refcnt 3 static_rix -1 ratemask 0xff [ 250] cur rix 7 (54 Mb ) since switch: packets 81 ticks 5659 [ 250] last sample 5 cur sample -1 packets sent 16901 [ 250] packets since sample 14 sample tt 464 [1600] cur rix 0 (6 Mb ) since switch: packets 0 ticks 0 [1600] last sample 0 cur sample -1 packets sent 0 [1600] packets since sample 0 sample tt 0 [ 6 Mb : 250] 1:1 (100%) T 1 F 0 avg 760 last 2752 [ 9 Mb : 250] 1:1 (100%) T 1 F 0 avg 648 last 1853 [12 Mb : 250] 1:1 (100%) T 1 F 0 avg 580 last 1451 [18 Mb : 250] 9:9 (100%) T 9 F 0 avg 524 last 884 [24 Mb : 250] 14:14 (100%) T 14 F 0 avg 492 last 907 [36 Mb : 250] 134:134 (100%) T 138 F 0 avg 478 last 876 [48 Mb : 250] 6622:6621 ( 99%) T 6814 F 0 avg 518 last 875 [48 Mb :1600] 1:0 ( 0%) T 5 F 1 avg 672 last 1567 [54 Mb : 250] 10125:10121 ( 99%) T 10413 F 0 avg 444 last 870 [54 Mb :1600] 4:0 ( 0%) T 22 F 4 avg 644 last 1210 mesh-2893:~ # sysctl dev.ath.0 dev.ath.0.%desc: Atheros 5413 dev.ath.0.%driver: ath dev.ath.0.%location: slot=1 function=0 dev.ath.0.%pnpinfo: vendor=0x168c device=0x001b subvendor=0x168c subdevice=0x2063 class=0x020000 dev.ath.0.%parent: pci0 dev.ath.0.smoothing_rate: 95 dev.ath.0.sample_rate: 10 dev.ath.0.sample_stats: 0 dev.ath.0.countrycode: 0 dev.ath.0.regdomain: 0 dev.ath.0.debug: 0 dev.ath.0.slottime: 9 dev.ath.0.acktimeout: 25 dev.ath.0.ctstimeout: 25 dev.ath.0.softled: 0 dev.ath.0.ledpin: 0 dev.ath.0.ledon: 0 dev.ath.0.ledidle: 270 dev.ath.0.txantenna: 1 dev.ath.0.rxantenna: 1 dev.ath.0.diversity: 0 dev.ath.0.txintrperiod: 5 dev.ath.0.diag: 0 dev.ath.0.tpscale: 0 dev.ath.0.tpc: 0 dev.ath.0.tpack: 63 dev.ath.0.tpcts: 63 dev.ath.0.intmit: 1 dev.ath.0.monpass: 24 dev.ath.0.dbaprep: 2 dev.ath.0.swbaprep: 10 dev.ath.0.guardtime: 0 dev.ath.0.superframe: 0 dev.ath.0.setcca: 0 dev.ath.0.clear_stats: 0 dev.ath.0.stats.ast_watchdog: 0 dev.ath.0.stats.ast_hardware: 0 dev.ath.0.stats.ast_bmiss: 0 dev.ath.0.stats.ast_bmiss_phantom: 0 dev.ath.0.stats.ast_bstuck: 0 dev.ath.0.stats.ast_rxorn: 0 dev.ath.0.stats.ast_rxeol: 0 dev.ath.0.stats.ast_txurn: 0 dev.ath.0.stats.ast_mib: 0 dev.ath.0.stats.ast_intrcoal: 0 dev.ath.0.stats.ast_tx_packets: 0 dev.ath.0.stats.ast_tx_mgmt: 0 dev.ath.0.stats.ast_tx_discard: 0 dev.ath.0.stats.ast_tx_qstop: 0 dev.ath.0.stats.ast_tx_encap: 0 dev.ath.0.stats.ast_tx_nonode: 0 dev.ath.0.stats.ast_tx_nombuf: 0 dev.ath.0.stats.ast_tx_nomcl: 0 dev.ath.0.stats.ast_tx_linear: 0 dev.ath.0.stats.ast_tx_nodata: 0 dev.ath.0.stats.ast_tx_busdma: 0 dev.ath.0.stats.ast_tx_xretries: 11 dev.ath.0.stats.ast_tx_fifoerr: 0 dev.ath.0.stats.ast_tx_filtered: 0 dev.ath.0.stats.ast_tx_shortretry: 0 dev.ath.0.stats.ast_tx_longretry: 526 dev.ath.0.stats.ast_tx_badrate: 0 dev.ath.0.stats.ast_tx_noack: 4 dev.ath.0.stats.ast_tx_rts: 0 dev.ath.0.stats.ast_tx_cts: 0 dev.ath.0.stats.ast_tx_shortpre: 0 dev.ath.0.stats.ast_tx_altrate: 5 dev.ath.0.stats.ast_tx_protect: 0 dev.ath.0.stats.ast_tx_ctsburst: 0 dev.ath.0.stats.ast_tx_ctsext: 0 dev.ath.0.stats.ast_rx_nombuf: 0 dev.ath.0.stats.ast_rx_busdma: 0 dev.ath.0.stats.ast_rx_orn: 0 dev.ath.0.stats.ast_rx_crcerr: 89 dev.ath.0.stats.ast_rx_fifoerr: 0 dev.ath.0.stats.ast_rx_badcrypt: 0 dev.ath.0.stats.ast_rx_badmic: 0 dev.ath.0.stats.ast_rx_phyerr: 0 dev.ath.0.stats.ast_rx_tooshort: 0 dev.ath.0.stats.ast_rx_toobig: 0 dev.ath.0.stats.ast_rx_packets: 0 dev.ath.0.stats.ast_rx_mgt: 0 dev.ath.0.stats.ast_rx_ctl: 0 dev.ath.0.stats.ast_be_xmit: 431 dev.ath.0.stats.ast_be_nombuf: 0 dev.ath.0.stats.ast_per_cal: 2 dev.ath.0.stats.ast_per_calfail: 0 dev.ath.0.stats.ast_per_rfgain: 1 dev.ath.0.stats.ast_rate_calls: 0 dev.ath.0.stats.ast_rate_raise: 0 dev.ath.0.stats.ast_rate_drop: 0 dev.ath.0.stats.ast_ant_defswitch: 1 dev.ath.0.stats.ast_ant_txswitch: 0 dev.ath.0.stats.ast_cabq_xmit: 0 dev.ath.0.stats.ast_cabq_busy: 0 dev.ath.0.stats.ast_tx_raw: 13 dev.ath.0.stats.ast_ff_txok: 0 dev.ath.0.stats.ast_ff_txerr: 0 dev.ath.0.stats.ast_ff_rx: 0 dev.ath.0.stats.ast_ff_flush: 0 dev.ath.0.stats.ast_tx_qfull: 0 dev.ath.0.stats.ast_tx_nobuf: 0 dev.ath.0.stats.ast_tdma_update: 0 dev.ath.0.stats.ast_tdma_timers: 0 dev.ath.0.stats.ast_tdma_tsf: 0 dev.ath.0.stats.ast_tdma_ack: 0 dev.ath.0.stats.ast_tx_raw_fail: 0 dev.ath.0.stats.ast_tx_nofrag: 0 dev.ath.0.stats.ast_be_missed: 5 dev.ath.0.stats.ast_ani_cal: 444 dev.ath.0.stats.ast_rx_agg: 0 dev.ath.0.stats.ast_rx_halfgi: 0 dev.ath.0.stats.ast_rx_2040: 0 dev.ath.0.stats.ast_rx_pre_crc_err: 0 dev.ath.0.stats.ast_rx_post_crc_err: 0 dev.ath.0.stats.ast_rx_decrypt_busy_err: 0 dev.ath.0.stats.ast_rx_hi_rx_chain: 0 dev.ath.0.stats.ast_tx_htprotect: 0 dev.ath.0.stats.ast_rx_hitqueueend: 0 dev.ath.0.stats.ast_tx_timeout: 0 dev.ath.0.stats.ast_tx_cst: 0 dev.ath.0.stats.ast_tx_xtxop: 0 dev.ath.0.stats.ast_tx_timerexpired: 0 dev.ath.0.stats.ast_tx_desccfgerr: 0 dev.ath.0.stats.rx_phy_err.0: 0 dev.ath.0.stats.rx_phy_err.1: 0 dev.ath.0.stats.rx_phy_err.2: 0 dev.ath.0.stats.rx_phy_err.3: 0 dev.ath.0.stats.rx_phy_err.4: 0 dev.ath.0.stats.rx_phy_err.5: 0 dev.ath.0.stats.rx_phy_err.6: 0 dev.ath.0.stats.rx_phy_err.7: 0 dev.ath.0.stats.rx_phy_err.8: 0 dev.ath.0.stats.rx_phy_err.9: 0 dev.ath.0.stats.rx_phy_err.10: 0 dev.ath.0.stats.rx_phy_err.11: 0 dev.ath.0.stats.rx_phy_err.12: 0 dev.ath.0.stats.rx_phy_err.13: 0 dev.ath.0.stats.rx_phy_err.14: 0 dev.ath.0.stats.rx_phy_err.15: 0 dev.ath.0.stats.rx_phy_err.16: 0 dev.ath.0.stats.rx_phy_err.17: 0 dev.ath.0.stats.rx_phy_err.18: 0 dev.ath.0.stats.rx_phy_err.19: 0 dev.ath.0.stats.rx_phy_err.20: 0 dev.ath.0.stats.rx_phy_err.21: 0 dev.ath.0.stats.rx_phy_err.22: 0 dev.ath.0.stats.rx_phy_err.23: 0 dev.ath.0.stats.rx_phy_err.24: 0 dev.ath.0.stats.rx_phy_err.25: 0 dev.ath.0.stats.rx_phy_err.26: 0 dev.ath.0.stats.rx_phy_err.27: 0 dev.ath.0.stats.rx_phy_err.28: 0 dev.ath.0.stats.rx_phy_err.29: 0 dev.ath.0.stats.rx_phy_err.30: 0 dev.ath.0.stats.rx_phy_err.31: 0 dev.ath.0.stats.rx_phy_err.32: 0 dev.ath.0.stats.rx_phy_err.33: 0 dev.ath.0.stats.rx_phy_err.34: 0 dev.ath.0.stats.rx_phy_err.35: 0 dev.ath.0.stats.rx_phy_err.36: 0 dev.ath.0.stats.rx_phy_err.37: 0 dev.ath.0.stats.rx_phy_err.38: 0 dev.ath.0.stats.rx_phy_err.39: 0 dev.ath.0.stats.rx_phy_err.40: 0 dev.ath.0.stats.rx_phy_err.41: 0 dev.ath.0.stats.rx_phy_err.42: 0 dev.ath.0.stats.rx_phy_err.43: 0 dev.ath.0.stats.rx_phy_err.44: 0 dev.ath.0.stats.rx_phy_err.45: 0 dev.ath.0.stats.rx_phy_err.46: 0 dev.ath.0.stats.rx_phy_err.47: 0 dev.ath.0.stats.rx_phy_err.48: 0 dev.ath.0.stats.rx_phy_err.49: 0 dev.ath.0.stats.rx_phy_err.50: 0 dev.ath.0.stats.rx_phy_err.51: 0 dev.ath.0.stats.rx_phy_err.52: 0 dev.ath.0.stats.rx_phy_err.53: 0 dev.ath.0.stats.rx_phy_err.54: 0 dev.ath.0.stats.rx_phy_err.55: 0 dev.ath.0.stats.rx_phy_err.56: 0 dev.ath.0.stats.rx_phy_err.57: 0 dev.ath.0.stats.rx_phy_err.58: 0 dev.ath.0.stats.rx_phy_err.59: 0 dev.ath.0.stats.rx_phy_err.60: 0 dev.ath.0.stats.rx_phy_err.61: 0 dev.ath.0.stats.rx_phy_err.62: 0 dev.ath.0.stats.rx_phy_err.63: 0 dev.ath.0.hal.debug: 0 dev.ath.0.hal.ar5416_biasadj: 0 dev.ath.0.hal.dma_brt: 2 dev.ath.0.hal.sw_brt: 10 dev.ath.0.hal.swba_backoff: 0 --Boundary-00=_OUfTPmYoHjNrT+o Content-Type: text/plain; charset="UTF-8"; name="nodeB-ADHOCmode.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="nodeB-ADHOCmode.txt" mesh-2870:~ # ifconfig wlan0 wlan0: flags=8843 metric 0 mtu 1500 ether 00:80:48:4f:28:70 inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255 inet6 fe80::280:48ff:fe4f:2870%wlan0 prefixlen 64 scopeid 0x8 nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11a status: running ssid mesh channel 136 (5680 MHz 11a) bssid 00:80:48:4f:28:90 regdomain NONE country ZA ecm authmode OPEN privacy OFF txpower 24 mcastrate 6 mgmtrate 6 scanvalid 60 wme burst mesh-2870:~ # ifconfig wlan0 list sta ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG 00:80:48:4f:28:70 0 136 0M 8.0 0 11 43024 I A 00:80:48:4f:28:93 0 136 54M 20.5 0 18172 3472 I AQ WME mesh-2870:~ # iperf -c 192.168.1.1 ------------------------------------------------------------ Client connecting to 192.168.1.1, TCP port 5001 TCP window size: 32.5 KByte (default) ------------------------------------------------------------ [ 3] local 192.168.1.2 port 18158 connected with 192.168.1.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 24.9 MBytes 20.8 Mbits/sec mesh-2870:~ # sysctl dev.ath.0.sample_stats=1 dev.ath.0.sample_stats: 0 [00:80:48:4f:28:70] refcnt 4 static_rix 0 ratemask 0x0 [ 250] cur rix 0 (6 Mb ) since switch: packets 0 ticks 0 [ 250] last sample 0 cur sample 0 packets sent 0 [ 250] packets since sample 0 sample tt 0 [1600] cur rix 0 (6 Mb ) since switch: packets 0 ticks 0 [1600] last sample 0 cur sample 0 packets sent 0 [1600] packets since sample 0 sample tt 0 [00:80:48:4f:28:93] refcnt 3 static_rix -1 ratemask 0xff [ 250] cur rix 7 (54 Mb ) since switch: packets 1 ticks 6755 [ 250] last sample 0 cur sample -1 packets sent 5 [ 250] packets since sample 5 sample tt 0 [1600] cur rix 7 (54 Mb ) since switch: packets 112 ticks 6745 [1600] last sample 6 cur sample -1 packets sent 18151 [1600] packets since sample 2 sample tt 1613 [24 Mb :1600] 4:4 (100%) T 4 F 0 avg 940 last 1746 [36 Mb : 250] 1:1 (100%) T 1 F 0 avg 464 last 2577 [36 Mb :1600] 153:153 (100%) T 174 F 0 avg 931 last 1569 [48 Mb :1600] 7414:7414 (100%) T 7959 F 0 avg 817 last 1560 [54 Mb : 250] 4:4 (100%) T 4 F 0 avg 444 last 1558 [54 Mb :1600] 10449:10448 ( 99%) T 11339 F 0 avg 647 last 1560 -> 0 mesh-2870:~ # sysctl dev.ath.0 dev.ath.0.%desc: Atheros 5413 dev.ath.0.%driver: ath dev.ath.0.%location: slot=1 function=0 dev.ath.0.%pnpinfo: vendor=0x168c device=0x001b subvendor=0x168c subdevice=0x2063 class=0x020000 dev.ath.0.%parent: pci0 dev.ath.0.smoothing_rate: 95 dev.ath.0.sample_rate: 10 dev.ath.0.sample_stats: 0 dev.ath.0.countrycode: 0 dev.ath.0.regdomain: 0 dev.ath.0.debug: 0 dev.ath.0.slottime: 9 dev.ath.0.acktimeout: 25 dev.ath.0.ctstimeout: 25 dev.ath.0.softled: 0 dev.ath.0.ledpin: 0 dev.ath.0.ledon: 0 dev.ath.0.ledidle: 270 dev.ath.0.txantenna: 1 dev.ath.0.rxantenna: 1 dev.ath.0.diversity: 0 dev.ath.0.txintrperiod: 5 dev.ath.0.diag: 0 dev.ath.0.tpscale: 0 dev.ath.0.tpc: 0 dev.ath.0.tpack: 63 dev.ath.0.tpcts: 63 dev.ath.0.intmit: 1 dev.ath.0.monpass: 24 dev.ath.0.dbaprep: 2 dev.ath.0.swbaprep: 10 dev.ath.0.guardtime: 0 dev.ath.0.superframe: 0 dev.ath.0.setcca: 0 dev.ath.0.clear_stats: 0 dev.ath.0.stats.ast_watchdog: 0 dev.ath.0.stats.ast_hardware: 0 dev.ath.0.stats.ast_bmiss: 0 dev.ath.0.stats.ast_bmiss_phantom: 0 dev.ath.0.stats.ast_bstuck: 0 dev.ath.0.stats.ast_rxorn: 0 dev.ath.0.stats.ast_rxeol: 0 dev.ath.0.stats.ast_txurn: 0 dev.ath.0.stats.ast_mib: 0 dev.ath.0.stats.ast_intrcoal: 0 dev.ath.0.stats.ast_tx_packets: 0 dev.ath.0.stats.ast_tx_mgmt: 0 dev.ath.0.stats.ast_tx_discard: 0 dev.ath.0.stats.ast_tx_qstop: 1146 dev.ath.0.stats.ast_tx_encap: 0 dev.ath.0.stats.ast_tx_nonode: 0 dev.ath.0.stats.ast_tx_nombuf: 0 dev.ath.0.stats.ast_tx_nomcl: 0 dev.ath.0.stats.ast_tx_linear: 0 dev.ath.0.stats.ast_tx_nodata: 0 dev.ath.0.stats.ast_tx_busdma: 0 dev.ath.0.stats.ast_tx_xretries: 1 dev.ath.0.stats.ast_tx_fifoerr: 0 dev.ath.0.stats.ast_tx_filtered: 0 dev.ath.0.stats.ast_tx_shortretry: 0 dev.ath.0.stats.ast_tx_longretry: 1449 dev.ath.0.stats.ast_tx_badrate: 0 dev.ath.0.stats.ast_tx_noack: 2 dev.ath.0.stats.ast_tx_rts: 0 dev.ath.0.stats.ast_tx_cts: 0 dev.ath.0.stats.ast_tx_shortpre: 0 dev.ath.0.stats.ast_tx_altrate: 1 dev.ath.0.stats.ast_tx_protect: 0 dev.ath.0.stats.ast_tx_ctsburst: 0 dev.ath.0.stats.ast_tx_ctsext: 0 dev.ath.0.stats.ast_rx_nombuf: 0 dev.ath.0.stats.ast_rx_busdma: 0 dev.ath.0.stats.ast_rx_orn: 0 dev.ath.0.stats.ast_rx_crcerr: 0 dev.ath.0.stats.ast_rx_fifoerr: 0 dev.ath.0.stats.ast_rx_badcrypt: 0 dev.ath.0.stats.ast_rx_badmic: 0 dev.ath.0.stats.ast_rx_phyerr: 0 dev.ath.0.stats.ast_rx_tooshort: 0 dev.ath.0.stats.ast_rx_toobig: 0 dev.ath.0.stats.ast_rx_packets: 0 dev.ath.0.stats.ast_rx_mgt: 0 dev.ath.0.stats.ast_rx_ctl: 0 dev.ath.0.stats.ast_be_xmit: 0 dev.ath.0.stats.ast_be_nombuf: 0 dev.ath.0.stats.ast_per_cal: 2 dev.ath.0.stats.ast_per_calfail: 0 dev.ath.0.stats.ast_per_rfgain: 1 dev.ath.0.stats.ast_rate_calls: 0 dev.ath.0.stats.ast_rate_raise: 0 dev.ath.0.stats.ast_rate_drop: 0 dev.ath.0.stats.ast_ant_defswitch: 0 dev.ath.0.stats.ast_ant_txswitch: 0 dev.ath.0.stats.ast_cabq_xmit: 0 dev.ath.0.stats.ast_cabq_busy: 0 dev.ath.0.stats.ast_tx_raw: 6 dev.ath.0.stats.ast_ff_txok: 0 dev.ath.0.stats.ast_ff_txerr: 0 dev.ath.0.stats.ast_ff_rx: 0 dev.ath.0.stats.ast_ff_flush: 0 dev.ath.0.stats.ast_tx_qfull: 0 dev.ath.0.stats.ast_tx_nobuf: 0 dev.ath.0.stats.ast_tdma_update: 0 dev.ath.0.stats.ast_tdma_timers: 0 dev.ath.0.stats.ast_tdma_tsf: 0 dev.ath.0.stats.ast_tdma_ack: 0 dev.ath.0.stats.ast_tx_raw_fail: 0 dev.ath.0.stats.ast_tx_nofrag: 0 dev.ath.0.stats.ast_be_missed: 0 dev.ath.0.stats.ast_ani_cal: 686 dev.ath.0.stats.ast_rx_agg: 0 dev.ath.0.stats.ast_rx_halfgi: 0 dev.ath.0.stats.ast_rx_2040: 0 dev.ath.0.stats.ast_rx_pre_crc_err: 0 dev.ath.0.stats.ast_rx_post_crc_err: 0 dev.ath.0.stats.ast_rx_decrypt_busy_err: 0 dev.ath.0.stats.ast_rx_hi_rx_chain: 0 dev.ath.0.stats.ast_tx_htprotect: 0 dev.ath.0.stats.ast_rx_hitqueueend: 0 dev.ath.0.stats.ast_tx_timeout: 0 dev.ath.0.stats.ast_tx_cst: 0 dev.ath.0.stats.ast_tx_xtxop: 0 dev.ath.0.stats.ast_tx_timerexpired: 0 dev.ath.0.stats.ast_tx_desccfgerr: 0 dev.ath.0.stats.rx_phy_err.0: 0 dev.ath.0.stats.rx_phy_err.1: 0 dev.ath.0.stats.rx_phy_err.2: 0 dev.ath.0.stats.rx_phy_err.3: 0 dev.ath.0.stats.rx_phy_err.4: 0 dev.ath.0.stats.rx_phy_err.5: 0 dev.ath.0.stats.rx_phy_err.6: 0 dev.ath.0.stats.rx_phy_err.7: 0 dev.ath.0.stats.rx_phy_err.8: 0 dev.ath.0.stats.rx_phy_err.9: 0 dev.ath.0.stats.rx_phy_err.10: 0 dev.ath.0.stats.rx_phy_err.11: 0 dev.ath.0.stats.rx_phy_err.12: 0 dev.ath.0.stats.rx_phy_err.13: 0 dev.ath.0.stats.rx_phy_err.14: 0 dev.ath.0.stats.rx_phy_err.15: 0 dev.ath.0.stats.rx_phy_err.16: 0 dev.ath.0.stats.rx_phy_err.17: 0 dev.ath.0.stats.rx_phy_err.18: 0 dev.ath.0.stats.rx_phy_err.19: 0 dev.ath.0.stats.rx_phy_err.20: 0 dev.ath.0.stats.rx_phy_err.21: 0 dev.ath.0.stats.rx_phy_err.22: 0 dev.ath.0.stats.rx_phy_err.23: 0 dev.ath.0.stats.rx_phy_err.24: 0 dev.ath.0.stats.rx_phy_err.25: 0 dev.ath.0.stats.rx_phy_err.26: 0 dev.ath.0.stats.rx_phy_err.27: 0 dev.ath.0.stats.rx_phy_err.28: 0 dev.ath.0.stats.rx_phy_err.29: 0 dev.ath.0.stats.rx_phy_err.30: 0 dev.ath.0.stats.rx_phy_err.31: 0 dev.ath.0.stats.rx_phy_err.32: 0 dev.ath.0.stats.rx_phy_err.33: 0 dev.ath.0.stats.rx_phy_err.34: 0 dev.ath.0.stats.rx_phy_err.35: 0 dev.ath.0.stats.rx_phy_err.36: 0 dev.ath.0.stats.rx_phy_err.37: 0 dev.ath.0.stats.rx_phy_err.38: 0 dev.ath.0.stats.rx_phy_err.39: 0 dev.ath.0.stats.rx_phy_err.40: 0 dev.ath.0.stats.rx_phy_err.41: 0 dev.ath.0.stats.rx_phy_err.42: 0 dev.ath.0.stats.rx_phy_err.43: 0 dev.ath.0.stats.rx_phy_err.44: 0 dev.ath.0.stats.rx_phy_err.45: 0 dev.ath.0.stats.rx_phy_err.46: 0 dev.ath.0.stats.rx_phy_err.47: 0 dev.ath.0.stats.rx_phy_err.48: 0 dev.ath.0.stats.rx_phy_err.49: 0 dev.ath.0.stats.rx_phy_err.50: 0 dev.ath.0.stats.rx_phy_err.51: 0 dev.ath.0.stats.rx_phy_err.52: 0 dev.ath.0.stats.rx_phy_err.53: 0 dev.ath.0.stats.rx_phy_err.54: 0 dev.ath.0.stats.rx_phy_err.55: 0 dev.ath.0.stats.rx_phy_err.56: 0 dev.ath.0.stats.rx_phy_err.57: 0 dev.ath.0.stats.rx_phy_err.58: 0 dev.ath.0.stats.rx_phy_err.59: 0 dev.ath.0.stats.rx_phy_err.60: 0 dev.ath.0.stats.rx_phy_err.61: 0 dev.ath.0.stats.rx_phy_err.62: 0 dev.ath.0.stats.rx_phy_err.63: 0 dev.ath.0.hal.debug: 0 dev.ath.0.hal.ar5416_biasadj: 0 dev.ath.0.hal.dma_brt: 2 dev.ath.0.hal.sw_brt: 10 dev.ath.0.hal.swba_backoff: 0 --Boundary-00=_OUfTPmYoHjNrT+o Content-Type: text/plain; charset="UTF-8"; name="nodeB-STAmode.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="nodeB-STAmode.txt" mesh-2870:~ # ifconfig wlan0 wlan0: flags=8843 metric 0 mtu 1500 ether 00:80:48:4f:28:70 inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255 inet6 fe80::280:48ff:fe4f:2870%wlan0 prefixlen 64 scopeid 0x8 nd6 options=29 media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11a status: associated ssid testAP channel 136 (5680 MHz 11a) bssid 00:80:48:4f:28:93 regdomain NONE country ZA ecm authmode OPEN privacy OFF txpower 24 bmiss 7 mcastrate 6 mgmtrate 6 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 12 wme burst mesh-2870:~ # ifconfig wlan0 list sta ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG 00:80:48:4f:28:93 1 136 54M 21.0 0 25477 18240 E AQ WME mesh-2870:~ # iperf -c 192.168.1.1 ------------------------------------------------------------ Client connecting to 192.168.1.1, TCP port 5001 TCP window size: 32.5 KByte (default) ------------------------------------------------------------ [ 3] local 192.168.1.2 port 54772 connected with 192.168.1.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.1 sec 34.5 MBytes 28.7 Mbits/sec mesh-2870:~ # sysctl dev.ath.0.sample_stats=1 dev.ath.0.sample_stats: 0 [00:80:48:4f:28:93] refcnt 4 static_rix -1 ratemask 0xff [ 250] cur rix 7 (54 Mb ) since switch: packets 1 ticks 4649 [ 250] last sample 0 cur sample -1 packets sent 11 [ 250] packets since sample 0 sample tt 0 [1600] cur rix 7 (54 Mb ) since switch: packets 116 ticks 5529 [1600] last sample 6 cur sample -1 packets sent 24984 [1600] packets since sample 4 sample tt 672 [36 Mb : 250] 1:1 (100%) T 1 F 0 avg 464 last 3150 [36 Mb :1600] 4:4 (100%) T 5 F 0 avg 1022 last 1423 [48 Mb :1600] 9304:9304 (100%) T 9538 F 0 avg 753 last 1271 [54 Mb : 250] 10:10 (100%) T 10 F 0 avg 444 last 1264 [54 Mb :1600] 15676:15676 (100%) T 16095 F 0 avg 644 last 1267 mesh-2870:~ # sysctl dev.ath.0 dev.ath.0.%desc: Atheros 5413 dev.ath.0.%driver: ath dev.ath.0.%location: slot=1 function=0 dev.ath.0.%pnpinfo: vendor=0x168c device=0x001b subvendor=0x168c subdevice=0x2063 class=0x020000 dev.ath.0.%parent: pci0 dev.ath.0.smoothing_rate: 95 dev.ath.0.sample_rate: 10 dev.ath.0.sample_stats: 0 dev.ath.0.countrycode: 0 dev.ath.0.regdomain: 0 dev.ath.0.debug: 0 dev.ath.0.slottime: 9 dev.ath.0.acktimeout: 25 dev.ath.0.ctstimeout: 25 dev.ath.0.softled: 0 dev.ath.0.ledpin: 0 dev.ath.0.ledon: 0 dev.ath.0.ledidle: 270 dev.ath.0.txantenna: 1 dev.ath.0.rxantenna: 1 dev.ath.0.diversity: 0 dev.ath.0.txintrperiod: 5 dev.ath.0.diag: 0 dev.ath.0.tpscale: 0 dev.ath.0.tpc: 0 dev.ath.0.tpack: 63 dev.ath.0.tpcts: 63 dev.ath.0.intmit: 1 dev.ath.0.monpass: 24 dev.ath.0.dbaprep: 2 dev.ath.0.swbaprep: 10 dev.ath.0.guardtime: 0 dev.ath.0.superframe: 0 dev.ath.0.setcca: 0 dev.ath.0.clear_stats: 0 dev.ath.0.stats.ast_watchdog: 0 dev.ath.0.stats.ast_hardware: 0 dev.ath.0.stats.ast_bmiss: 6 dev.ath.0.stats.ast_bmiss_phantom: 6 dev.ath.0.stats.ast_bstuck: 0 dev.ath.0.stats.ast_rxorn: 0 dev.ath.0.stats.ast_rxeol: 0 dev.ath.0.stats.ast_txurn: 0 dev.ath.0.stats.ast_mib: 0 dev.ath.0.stats.ast_intrcoal: 0 dev.ath.0.stats.ast_tx_packets: 0 dev.ath.0.stats.ast_tx_mgmt: 0 dev.ath.0.stats.ast_tx_discard: 0 dev.ath.0.stats.ast_tx_qstop: 5146 dev.ath.0.stats.ast_tx_encap: 0 dev.ath.0.stats.ast_tx_nonode: 0 dev.ath.0.stats.ast_tx_nombuf: 0 dev.ath.0.stats.ast_tx_nomcl: 0 dev.ath.0.stats.ast_tx_linear: 0 dev.ath.0.stats.ast_tx_nodata: 0 dev.ath.0.stats.ast_tx_busdma: 0 dev.ath.0.stats.ast_tx_xretries: 0 dev.ath.0.stats.ast_tx_fifoerr: 0 dev.ath.0.stats.ast_tx_filtered: 0 dev.ath.0.stats.ast_tx_shortretry: 0 dev.ath.0.stats.ast_tx_longretry: 654 dev.ath.0.stats.ast_tx_badrate: 0 dev.ath.0.stats.ast_tx_noack: 0 dev.ath.0.stats.ast_tx_rts: 0 dev.ath.0.stats.ast_tx_cts: 0 dev.ath.0.stats.ast_tx_shortpre: 0 dev.ath.0.stats.ast_tx_altrate: 0 dev.ath.0.stats.ast_tx_protect: 0 dev.ath.0.stats.ast_tx_ctsburst: 0 dev.ath.0.stats.ast_tx_ctsext: 0 dev.ath.0.stats.ast_rx_nombuf: 0 dev.ath.0.stats.ast_rx_busdma: 0 dev.ath.0.stats.ast_rx_orn: 0 dev.ath.0.stats.ast_rx_crcerr: 0 dev.ath.0.stats.ast_rx_fifoerr: 0 dev.ath.0.stats.ast_rx_badcrypt: 0 dev.ath.0.stats.ast_rx_badmic: 0 dev.ath.0.stats.ast_rx_phyerr: 0 dev.ath.0.stats.ast_rx_tooshort: 0 dev.ath.0.stats.ast_rx_toobig: 0 dev.ath.0.stats.ast_rx_packets: 0 dev.ath.0.stats.ast_rx_mgt: 0 dev.ath.0.stats.ast_rx_ctl: 0 dev.ath.0.stats.ast_be_xmit: 0 dev.ath.0.stats.ast_be_nombuf: 0 dev.ath.0.stats.ast_per_cal: 2 dev.ath.0.stats.ast_per_calfail: 0 dev.ath.0.stats.ast_per_rfgain: 1 dev.ath.0.stats.ast_rate_calls: 0 dev.ath.0.stats.ast_rate_raise: 0 dev.ath.0.stats.ast_rate_drop: 0 dev.ath.0.stats.ast_ant_defswitch: 0 dev.ath.0.stats.ast_ant_txswitch: 0 dev.ath.0.stats.ast_cabq_xmit: 0 dev.ath.0.stats.ast_cabq_busy: 0 dev.ath.0.stats.ast_tx_raw: 38 dev.ath.0.stats.ast_ff_txok: 0 dev.ath.0.stats.ast_ff_txerr: 0 dev.ath.0.stats.ast_ff_rx: 0 dev.ath.0.stats.ast_ff_flush: 0 dev.ath.0.stats.ast_tx_qfull: 0 dev.ath.0.stats.ast_tx_nobuf: 0 dev.ath.0.stats.ast_tdma_update: 0 dev.ath.0.stats.ast_tdma_timers: 0 dev.ath.0.stats.ast_tdma_tsf: 0 dev.ath.0.stats.ast_tdma_ack: 0 dev.ath.0.stats.ast_tx_raw_fail: 0 dev.ath.0.stats.ast_tx_nofrag: 0 dev.ath.0.stats.ast_be_missed: 0 dev.ath.0.stats.ast_ani_cal: 342 dev.ath.0.stats.ast_rx_agg: 0 dev.ath.0.stats.ast_rx_halfgi: 0 dev.ath.0.stats.ast_rx_2040: 0 dev.ath.0.stats.ast_rx_pre_crc_err: 0 dev.ath.0.stats.ast_rx_post_crc_err: 0 dev.ath.0.stats.ast_rx_decrypt_busy_err: 0 dev.ath.0.stats.ast_rx_hi_rx_chain: 0 dev.ath.0.stats.ast_tx_htprotect: 0 dev.ath.0.stats.ast_rx_hitqueueend: 0 dev.ath.0.stats.ast_tx_timeout: 0 dev.ath.0.stats.ast_tx_cst: 0 dev.ath.0.stats.ast_tx_xtxop: 0 dev.ath.0.stats.ast_tx_timerexpired: 0 dev.ath.0.stats.ast_tx_desccfgerr: 0 dev.ath.0.stats.rx_phy_err.0: 0 dev.ath.0.stats.rx_phy_err.1: 0 dev.ath.0.stats.rx_phy_err.2: 0 dev.ath.0.stats.rx_phy_err.3: 0 dev.ath.0.stats.rx_phy_err.4: 0 dev.ath.0.stats.rx_phy_err.5: 0 dev.ath.0.stats.rx_phy_err.6: 0 dev.ath.0.stats.rx_phy_err.7: 0 dev.ath.0.stats.rx_phy_err.8: 0 dev.ath.0.stats.rx_phy_err.9: 0 dev.ath.0.stats.rx_phy_err.10: 0 dev.ath.0.stats.rx_phy_err.11: 0 dev.ath.0.stats.rx_phy_err.12: 0 dev.ath.0.stats.rx_phy_err.13: 0 dev.ath.0.stats.rx_phy_err.14: 0 dev.ath.0.stats.rx_phy_err.15: 0 dev.ath.0.stats.rx_phy_err.16: 0 dev.ath.0.stats.rx_phy_err.17: 0 dev.ath.0.stats.rx_phy_err.18: 0 dev.ath.0.stats.rx_phy_err.19: 0 dev.ath.0.stats.rx_phy_err.20: 0 dev.ath.0.stats.rx_phy_err.21: 0 dev.ath.0.stats.rx_phy_err.22: 0 dev.ath.0.stats.rx_phy_err.23: 0 dev.ath.0.stats.rx_phy_err.24: 0 dev.ath.0.stats.rx_phy_err.25: 0 dev.ath.0.stats.rx_phy_err.26: 0 dev.ath.0.stats.rx_phy_err.27: 0 dev.ath.0.stats.rx_phy_err.28: 0 dev.ath.0.stats.rx_phy_err.29: 0 dev.ath.0.stats.rx_phy_err.30: 0 dev.ath.0.stats.rx_phy_err.31: 0 dev.ath.0.stats.rx_phy_err.32: 0 dev.ath.0.stats.rx_phy_err.33: 0 dev.ath.0.stats.rx_phy_err.34: 0 dev.ath.0.stats.rx_phy_err.35: 0 dev.ath.0.stats.rx_phy_err.36: 0 dev.ath.0.stats.rx_phy_err.37: 0 dev.ath.0.stats.rx_phy_err.38: 0 dev.ath.0.stats.rx_phy_err.39: 0 dev.ath.0.stats.rx_phy_err.40: 0 dev.ath.0.stats.rx_phy_err.41: 0 dev.ath.0.stats.rx_phy_err.42: 0 dev.ath.0.stats.rx_phy_err.43: 0 dev.ath.0.stats.rx_phy_err.44: 0 dev.ath.0.stats.rx_phy_err.45: 0 dev.ath.0.stats.rx_phy_err.46: 0 dev.ath.0.stats.rx_phy_err.47: 0 dev.ath.0.stats.rx_phy_err.48: 0 dev.ath.0.stats.rx_phy_err.49: 0 dev.ath.0.stats.rx_phy_err.50: 0 dev.ath.0.stats.rx_phy_err.51: 0 dev.ath.0.stats.rx_phy_err.52: 0 dev.ath.0.stats.rx_phy_err.53: 0 dev.ath.0.stats.rx_phy_err.54: 0 dev.ath.0.stats.rx_phy_err.55: 0 dev.ath.0.stats.rx_phy_err.56: 0 dev.ath.0.stats.rx_phy_err.57: 0 dev.ath.0.stats.rx_phy_err.58: 0 dev.ath.0.stats.rx_phy_err.59: 0 dev.ath.0.stats.rx_phy_err.60: 0 dev.ath.0.stats.rx_phy_err.61: 0 dev.ath.0.stats.rx_phy_err.62: 0 dev.ath.0.stats.rx_phy_err.63: 0 dev.ath.0.hal.debug: 0 dev.ath.0.hal.ar5416_biasadj: 0 dev.ath.0.hal.dma_brt: 2 dev.ath.0.hal.sw_brt: 10 dev.ath.0.hal.swba_backoff: 0 --Boundary-00=_OUfTPmYoHjNrT+o-- From owner-freebsd-wireless@FreeBSD.ORG Wed Feb 29 17:06:45 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EA24D1065675 for ; Wed, 29 Feb 2012 17:06:45 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: from mail-ee0-f54.google.com (mail-ee0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 74CA68FC0A for ; Wed, 29 Feb 2012 17:06:44 +0000 (UTC) Received: by eekd17 with SMTP id d17so2431587eek.13 for ; Wed, 29 Feb 2012 09:06:43 -0800 (PST) Received-SPF: pass (google.com: domain of fernando.apesteguia@gmail.com designates 10.112.85.137 as permitted sender) client-ip=10.112.85.137; Authentication-Results: mr.google.com; spf=pass (google.com: domain of fernando.apesteguia@gmail.com designates 10.112.85.137 as permitted sender) smtp.mail=fernando.apesteguia@gmail.com; dkim=pass header.i=fernando.apesteguia@gmail.com Received: from mr.google.com ([10.112.85.137]) by 10.112.85.137 with SMTP id h9mr544521lbz.51.1330535203645 (num_hops = 1); Wed, 29 Feb 2012 09:06:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=JTzzNddM4orOAsnhM5Zs6r6vJct4dHsc6H+BJoG7khM=; b=paB4HzEtJd7wZbZmYmXuzoucN/jIR4r3qY8GVOa5iitgat9i//as1ziLVWIS+POwzv MLcbRiBAH38c1FySn+o0oOAWJlSKK7cTUuy4OnjMNYohnsv0WROD+gPPmbxVMd2iyWzf FU597wuW4JBiBHJsx39hjVqpHp9Ntd3h7ZG/M= MIME-Version: 1.0 Received: by 10.112.85.137 with SMTP id h9mr444688lbz.51.1330535203498; Wed, 29 Feb 2012 09:06:43 -0800 (PST) Received: by 10.152.13.72 with HTTP; Wed, 29 Feb 2012 09:06:43 -0800 (PST) In-Reply-To: References: Date: Wed, 29 Feb 2012 18:06:43 +0100 Message-ID: From: =?ISO-8859-1?Q?Fernando_Apestegu=EDa?= To: Bernhard Schmidt Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: Re: iwi firmware X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 29 Feb 2012 17:06:46 -0000 On Wed, Feb 29, 2012 at 10:09 AM, Bernhard Schmidt wrote: > On Tue, Feb 28, 2012 at 23:20, Fernando Apestegu=EDa > wrote: > > Hi all, > > > > I recently installed 9.0-RELEASE on my old laptop. I used the ipw2200 > card > > in this laptop with 8.2-RELEASE without problems. However I have missed > > something I can't figure out. I get the message: > > > > iwi0: timeout processing command blocks for iwi_bss firmware > > iwi0: could not load main firmware iwi_bss > > > > This is what I have in my loader.conf: > > > > # Agree Intel's agreement license > > legal.intel_iwi.license_ack=3D1 > > > > # wireless support > > #if_iwi_load=3D"YES" This is in kernel now... > > wlan_load=3D"YES" > > firmware_load=3D"YES" > > > > iwi_bss_load=3D"YES" > > iwi_ibss_load=3D"YES" > > iwi_monitor_load=3D"YES" > > > > what am I missing? > > > > Thanks in advance. > > Hmm, there haven't been any major changes to iwi(4) between 8.2 and > 9.0, except what you've already noticed. You could try to remove > iwi(4) from the kernel config and use it as module again, just to make > sure it isn't related to that. Also, all modules iwi(4) depends on are > pulled in automatically, even the firmware modules, no need to load em > through loader.conf. > I copied GENERIC and removed the "device iwi" line. I rebooted but still got the same message. I also tried removing the iwi device and introducing the iwifw in the kernel (so I got a couple of complaints from the kernel when loading since I didn't change my loader.conf). Still the same error. > Can you post dmesg and pciconf -lvc? > Yes. dmesg: Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-RELEASE #0: Fri Feb 17 18:27:35 CET 2012 root@hammer:/usr/obj/usr/src/sys/APEKERNEL9 amd64 CPU: Mobile AMD Athlon(tm) 64 Processor 2800+ (1603.68-MHz K8-class CPU) Origin =3D "AuthenticAMD" Id =3D 0xf4a Family =3D f Model =3D 4 Stepp= ing =3D 10 Features=3D0x78bfbff AMD Features=3D0xe0500800 real memory =3D 1073741824 (1024 MB) avail memory =3D 1016823808 (969 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: on acpi0 acpi_ec0: port 0x62,0x66 on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: on hostb0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0x2000-0x20ff mem 0xd8000000-0xdfffffff,0xd0100000-0xd010ffff irq 18 at device 0.0 on pci1 iwi0: at device 5.0 on pci0 fwohci0: mem 0xd0008000-0xd00087ff,0xd0000000-0xd0003fff irq 17 at device 6.0 on pci0 fwohci0: OHCI version 1.10 (ROM=3D1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:90:f5:00:00:32:12:31 fwohci0: Phy 1394a available S400, 1 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 dcons_crom0: on firewire0 dcons_crom0: bus_addr 0x235c000 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:90:f5:32:12:31 fwe0: Ethernet address: 02:90:f5:32:12:31 fwip0: on firewire0 fwip0: Firewire address: 00:90:f5:00:00:32:12:31 @ 0xfffe00000000, S400, maxrec 2048 fwohci0: Initiate bus reset fwohci0: fwohci_intr_core: BUS reset fwohci0: fwohci_intr_core: node_id=3D0x00000000, SelfID Count=3D1, CYCLEMAS= TER mode re0: port 0x1000-0x10ff mem 0xd0008800-0xd00088ff irq 19 at device 8.0 on pci0 re0: Chip rev. 0x04000000 re0: MAC rev. 0x00000000 miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow re0: Ethernet address: 00:90:f5:32:12:31 cbb0: at device 12.0 on pci0 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 pci0: at device 14.0 (no driver attached) pci0: at device 14.1 (no driver attached) uhci0: port 0x1c00-0x1c1f at device 16.0 on pci= 0 usbus0: on uhci0 uhci1: port 0x1c20-0x1c3f at device 16.1 on pci= 0 usbus1: on uhci1 uhci2: port 0x1c40-0x1c5f at device 16.2 on pci= 0 usbus2: on uhci2 ehci0: mem 0xd0008c00-0xd0008cff at device 16.3 on pci0 usbus3: EHCI version 1.0 usbus3: on ehci0 isab0: at device 17.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1c60-0x1c6f at device 17.1 on pci0 ata0: on atapci0 ata1: on atapci0 pcm0: port 0x1400-0x14ff irq 22 at device 17.5 on pci0 pcm0: pcm0: pci0: at device 17.6 (no driver attached) battery0: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 acpi_acad0: on acpi0 acpi_lid0: on acpi0 acpi_tz0: on acpi0 atrtc0: port 0x70-0x75 irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 attimer0: port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model GlidePoint, device ID 0 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 ppc0: port 0x378-0x37f,0x778-0x77b irq 7 drq 1 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 powernow0: on cpu0 Timecounters tick every 1.000 msec firewire0: 1 nodes, maxhop <=3D 0 cable IRM irm(0) (me) firewire0: bus manager 0 usbus0: 12Mbps Full Speed USB v1.0 usbus1: 12Mbps Full Speed USB v1.0 usbus2: 12Mbps Full Speed USB v1.0 usbus3: 480Mbps High Speed USB v2.0 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 ugen2.1: at usbus2 uhub2: on usbus2 ugen3.1: at usbus3 uhub3: on usbus3 ada0 at ata0 bus 0 scbus0 target 0 lun 0 ada0: ATA-6 device ada0: 100.000MB/s transfers (UDMA5, PIO 8192bytes) ada0: 76319MB (156301488 512 byte sectors: 16H 63S/T 16383C) ada0: Previously was known as ad0 Timecounter "TSC" frequency 1603676920 Hz quality 800 cd0 at ata1 bus 0 scbus1 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) cd0: Attempt to query device size failed: NOT READY, Medium not present Root mount waiting for: usbus3 usbus2 usbus1 usbus0 uhub0: 2 ports with 2 removable, self powered uhub1: 2 ports with 2 removable, self powered uhub2: 2 ports with 2 removable, self powered Root mount waiting for: usbus3 Root mount waiting for: usbus3 uhub3: 6 ports with 6 removable, self powered Trying to mount root from ufs:/dev/ada0p2 [rw]... drm0: on vgapci0 info: [drm] AGP at 0xe0000000 256MB info: [drm] Initialized radeon 1.31.0 20080613 info: [drm] Setting GART location based on new memory map info: [drm] Loading R300 Microcode info: [drm] Num pipes: 1 info: [drm] writeback test succeeded in 1 usecs pciconf -lvc: hostb0@pci0:0:0:0: class=3D0x060000 card=3D0x31881106 chip=3D0x31881106 rev=3D0x01 hdr=3D0x00 vendor =3D 'VIA Technologies, Inc.' device =3D 'VT8385 [K8T800 AGP] Host Bridge' class =3D bridge subclass =3D HOST-PCI cap 02[80] =3D AGP v3 8x 4x SBA disabled cap 08[c0] =3D HT slave cap 01[68] =3D powerspec 2 supports D0 D3 current D0 cap 08[58] =3D HT interrupt pcib1@pci0:0:1:0: class=3D0x060400 card=3D0x00000000 chip=3D0xb1881106 rev=3D0x00 hdr=3D0x01 vendor =3D 'VIA Technologies, Inc.' device =3D 'VT8237 PCI bridge [K8T800/K8T890 South]' class =3D bridge subclass =3D PCI-PCI cap 01[80] =3D powerspec 2 supports D0 D1 D3 current D0 iwi0@pci0:0:5:0: class=3D0x028000 card=3D0x27028086 chip=3D0x42208086 re= v=3D0x05 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'PRO/Wireless 2200BG [Calexico2] Network Connection' class =3D network cap 01[dc] =3D powerspec 2 supports D0 D3 current D0 fwohci0@pci0:0:6:0: class=3D0x0c0010 card=3D0x47011558 chip=3D0x8026104c rev=3D0x00 hdr=3D0x00 vendor =3D 'Texas Instruments' device =3D 'TSB43AB21 IEEE-1394a-2000 Controller (PHY/Link)' class =3D serial bus subclass =3D FireWire cap 01[44] =3D powerspec 2 supports D0 D1 D2 D3 current D0 re0@pci0:0:8:0: class=3D0x020000 card=3D0x47011558 chip=3D0x816910ec rev= =3D0x10 hdr=3D0x00 vendor =3D 'Realtek Semiconductor Co., Ltd.' device =3D 'RTL-8169 Gigabit Ethernet' class =3D network subclass =3D ethernet cap 01[dc] =3D powerspec 2 supports D0 D1 D2 D3 current D0 cbb0@pci0:0:12:0: class=3D0x060700 card=3D0x47011558 chip=3D0x14101524 rev=3D0x01 hdr=3D0x02 vendor =3D 'ENE Technology Inc' device =3D 'CB1410 Cardbus Controller' class =3D bridge subclass =3D PCI-CardBus cap 01[a0] =3D powerspec 1 supports D0 D1 D2 D3 current D0 none0@pci0:0:14:0: class=3D0x018000 card=3D0x10501050 chip=3D0x84811050 rev=3D0x01 hdr=3D0x00 vendor =3D 'Winbond Electronics Corp' class =3D mass storage cap 01[c0] =3D powerspec 2 supports D0 D1 D2 D3 current D0 none1@pci0:0:14:1: class=3D0x018000 card=3D0x10501050 chip=3D0x84821050 rev=3D0x01 hdr=3D0x00 vendor =3D 'Winbond Electronics Corp' class =3D mass storage cap 01[c0] =3D powerspec 2 supports D0 D1 D2 D3 current D0 uhci0@pci0:0:16:0: class=3D0x0c0300 card=3D0x47011558 chip=3D0x30381106 rev=3D0x80 hdr=3D0x00 vendor =3D 'VIA Technologies, Inc.' device =3D 'VT82xxxxx UHCI USB 1.1 Controller' class =3D serial bus subclass =3D USB cap 01[80] =3D powerspec 2 supports D0 D1 D2 D3 current D0 uhci1@pci0:0:16:1: class=3D0x0c0300 card=3D0x47011558 chip=3D0x30381106 rev=3D0x80 hdr=3D0x00 vendor =3D 'VIA Technologies, Inc.' device =3D 'VT82xxxxx UHCI USB 1.1 Controller' class =3D serial bus subclass =3D USB cap 01[80] =3D powerspec 2 supports D0 D1 D2 D3 current D0 uhci2@pci0:0:16:2: class=3D0x0c0300 card=3D0x47011558 chip=3D0x30381106 rev=3D0x80 hdr=3D0x00 vendor =3D 'VIA Technologies, Inc.' device =3D 'VT82xxxxx UHCI USB 1.1 Controller' class =3D serial bus subclass =3D USB cap 01[80] =3D powerspec 2 supports D0 D1 D2 D3 current D0 ehci0@pci0:0:16:3: class=3D0x0c0320 card=3D0x47011558 chip=3D0x31041106 rev=3D0x82 hdr=3D0x00 vendor =3D 'VIA Technologies, Inc.' device =3D 'USB 2.0' class =3D serial bus subclass =3D USB cap 01[80] =3D powerspec 2 supports D0 D1 D2 D3 current D0 isab0@pci0:0:17:0: class=3D0x060100 card=3D0x47011558 chip=3D0x31771106 rev=3D0x00 hdr=3D0x00 vendor =3D 'VIA Technologies, Inc.' device =3D 'VT8235 ISA Bridge' class =3D bridge subclass =3D PCI-ISA cap 01[c0] =3D powerspec 2 supports D0 D3 current D0 atapci0@pci0:0:17:1: class=3D0x01018a card=3D0x47011558 chip=3D0x0571110= 6 rev=3D0x06 hdr=3D0x00 vendor =3D 'VIA Technologies, Inc.' device =3D 'VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE= ' class =3D mass storage subclass =3D ATA cap 01[c0] =3D powerspec 2 supports D0 D3 current D0 pcm0@pci0:0:17:5: class=3D0x040100 card=3D0x47011558 chip=3D0x30591106 rev=3D0x50 hdr=3D0x00 vendor =3D 'VIA Technologies, Inc.' device =3D 'VT8233/A/8235/8237 AC97 Audio Controller' class =3D multimedia subclass =3D audio cap 01[c0] =3D powerspec 2 supports D0 D1 D2 D3 current D0 none2@pci0:0:17:6: class=3D0x078000 card=3D0x47011558 chip=3D0x30681106 rev=3D0x80 hdr=3D0x00 vendor =3D 'VIA Technologies, Inc.' device =3D 'AC'97 Modem Controller' class =3D simple comms cap 01[d0] =3D powerspec 2 supports D0 D3 current D0 hostb1@pci0:0:24:0: class=3D0x060000 card=3D0x00000000 chip=3D0x11001022 rev=3D0x00 hdr=3D0x00 vendor =3D 'Advanced Micro Devices [AMD]' device =3D 'K8 [Athlon64/Opteron] HyperTransport Technology Configuration' class =3D bridge subclass =3D HOST-PCI cap 08[80] =3D HT host hostb2@pci0:0:24:1: class=3D0x060000 card=3D0x00000000 chip=3D0x11011022 rev=3D0x00 hdr=3D0x00 vendor =3D 'Advanced Micro Devices [AMD]' device =3D 'K8 [Athlon64/Opteron] Address Map' class =3D bridge subclass =3D HOST-PCI hostb3@pci0:0:24:2: class=3D0x060000 card=3D0x00000000 chip=3D0x11021022 rev=3D0x00 hdr=3D0x00 vendor =3D 'Advanced Micro Devices [AMD]' device =3D 'K8 [Athlon64/Opteron] DRAM Controller' class =3D bridge subclass =3D HOST-PCI hostb4@pci0:0:24:3: class=3D0x060000 card=3D0x00000000 chip=3D0x11031022 rev=3D0x00 hdr=3D0x00 vendor =3D 'Advanced Micro Devices [AMD]' device =3D 'K8 [Athlon64/Opteron] Miscellaneous Control' class =3D bridge subclass =3D HOST-PCI vgapci0@pci0:1:0:0: class=3D0x030000 card=3D0x47011558 chip=3D0x4e501002 rev=3D0x00 hdr=3D0x00 vendor =3D 'ATI Technologies Inc' device =3D 'RV350 [Mobility Radeon 9600 M10]' class =3D display subclass =3D VGA cap 02[58] =3D AGP v3 8x 4x SBA disabled cap 01[50] =3D powerspec 2 supports D0 D1 D2 D3 current D0 > > -- > Bernhard > From owner-freebsd-wireless@FreeBSD.ORG Wed Feb 29 17:48:55 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 12304106566B for ; Wed, 29 Feb 2012 17:48:55 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 90F3D8FC0A for ; Wed, 29 Feb 2012 17:48:54 +0000 (UTC) Received: by werl4 with SMTP id l4so2800443wer.13 for ; Wed, 29 Feb 2012 09:48:53 -0800 (PST) Received-SPF: pass (google.com: domain of adrian.chadd@gmail.com designates 10.216.134.136 as permitted sender) client-ip=10.216.134.136; Authentication-Results: mr.google.com; spf=pass (google.com: domain of adrian.chadd@gmail.com designates 10.216.134.136 as permitted sender) smtp.mail=adrian.chadd@gmail.com; dkim=pass header.i=adrian.chadd@gmail.com Received: from mr.google.com ([10.216.134.136]) by 10.216.134.136 with SMTP id s8mr776459wei.6.1330537733679 (num_hops = 1); Wed, 29 Feb 2012 09:48:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Dmq+leSebbUuC1hG1LlVFVoOf3EJF1gERuIVSNJ/bwk=; b=hMFQbojNormJYOaVRD6VNp0Hwdt7LyrPlFiC3H0L5Ff9MLt2c6ZEo5k2BIZmPLVAys HsyHuHKbHYuGyFVhtzxpAdnbAYJfZSM+qbLulyzloNCoYsuUi8bbKPq/5h/7gKDFsB1Q BxzJwRiJfKUmu5ok1L6IaK0gOxK2auBaGR64w= MIME-Version: 1.0 Received: by 10.216.134.136 with SMTP id s8mr623709wei.6.1330537733596; Wed, 29 Feb 2012 09:48:53 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.198.81 with HTTP; Wed, 29 Feb 2012 09:48:53 -0800 (PST) In-Reply-To: <201202291151.10365.jhugo@meraka.csir.co.za> References: <201202281639.05140.jhugo@meraka.csir.co.za> <201202291151.10365.jhugo@meraka.csir.co.za> Date: Wed, 29 Feb 2012 09:48:53 -0800 X-Google-Sender-Auth: y5aaORzxxLdncBhducpg-w-aQU8 Message-ID: From: Adrian Chadd To: Johann Hugo Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: performance in adhoc mode X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 29 Feb 2012 17:48:55 -0000 Ok, long_retry means that the hardware had to try more times to get the frame out. Either it's picking too high a rate, or the ACKs can't be heard. I wonder what changes in the MAC and driver when we flip on adhoc mode. I know it changes how the beacon queue is handled, I didn't think anything else changed.. Can you try forcing a lower rate on both ends (ifconfig wlanX ucastrate Y) and do your tests? Please file a PR with this. :) Thanks! Adrian On 29 February 2012 01:51, Johann Hugo wrote: > On Tuesday 28 February 2012 17:50:39 Adrian Chadd wrote: > >> I've not looked into adhoc _at all_. > > > > please_do > > > >> > >> I'd start by looking at the behaviour of the rate control code - do > >> 'sysctl dev.ath.X sample_stats=1' after you've done some traffic and > >> check dmesg. > >> > >> Just ensure that the same rates are being used and the error rate is low. > >> > > > > The rates differ a bit and also some of the dev.ath.0 sysctl's. > dev.ath.0.stats.ast_tx_longretry is more than double in adhoc mode. > > > > Johann > > From owner-freebsd-wireless@FreeBSD.ORG Wed Feb 29 19:45:04 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 73B27106564A for ; Wed, 29 Feb 2012 19:45:04 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id F1F818FC12 for ; Wed, 29 Feb 2012 19:45:03 +0000 (UTC) Received: by wibhn6 with SMTP id hn6so3324898wib.13 for ; Wed, 29 Feb 2012 11:45:02 -0800 (PST) Received-SPF: pass (google.com: domain of bschmidt@techwires.net designates 10.180.107.68 as permitted sender) client-ip=10.180.107.68; Authentication-Results: mr.google.com; spf=pass (google.com: domain of bschmidt@techwires.net designates 10.180.107.68 as permitted sender) smtp.mail=bschmidt@techwires.net Received: from mr.google.com ([10.180.107.68]) by 10.180.107.68 with SMTP id ha4mr3813082wib.9.1330544702962 (num_hops = 1); Wed, 29 Feb 2012 11:45:02 -0800 (PST) Received: by 10.180.107.68 with SMTP id ha4mr3052248wib.9.1330544702796; Wed, 29 Feb 2012 11:45:02 -0800 (PST) Received: from amy.lab.techwires.net (dslb-088-067-218-213.pools.arcor-ip.net. [88.67.218.213]) by mx.google.com with ESMTPS id s2sm92010623wix.3.2012.02.29.11.44.59 (version=SSLv3 cipher=OTHER); Wed, 29 Feb 2012 11:45:01 -0800 (PST) From: Bernhard Schmidt To: Fernando =?iso-8859-15?q?Apestegu=EDa?= Date: Wed, 29 Feb 2012 20:45:11 +0100 User-Agent: KMail/1.13.7 (FreeBSD/9.0-STABLE; KDE/4.7.4; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Message-Id: <201202292045.11498.bschmidt@techwires.net> X-Gm-Message-State: ALoCoQknwXd1ij7LMkDtVGCvmmChILszhxTe8x07gavCv6Y7KFqDTISgY8sLWTCVSw1Y9kdYIXFi Cc: freebsd-wireless@freebsd.org Subject: Re: iwi firmware X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 29 Feb 2012 19:45:04 -0000 On Wednesday 29 February 2012 18:06:43 Fernando Apestegu=EDa wrote: > On Wed, Feb 29, 2012 at 10:09 AM, Bernhard Schmidt > wrote: >=20 > > On Tue, Feb 28, 2012 at 23:20, Fernando Apestegu=EDa > > wrote: > > > Hi all, > > > > > > I recently installed 9.0-RELEASE on my old laptop. I used the ipw2200 > > card > > > in this laptop with 8.2-RELEASE without problems. However I have miss= ed > > > something I can't figure out. I get the message: > > > > > > iwi0: timeout processing command blocks for iwi_bss firmware > > > iwi0: could not load main firmware iwi_bss > > > > > > This is what I have in my loader.conf: > > > > > > # Agree Intel's agreement license > > > legal.intel_iwi.license_ack=3D1 > > > > > > # wireless support > > > #if_iwi_load=3D"YES" This is in kernel now... > > > wlan_load=3D"YES" > > > firmware_load=3D"YES" > > > > > > iwi_bss_load=3D"YES" > > > iwi_ibss_load=3D"YES" > > > iwi_monitor_load=3D"YES" > > > > > > what am I missing? > > > > > > Thanks in advance. > > > > Hmm, there haven't been any major changes to iwi(4) between 8.2 and > > 9.0, except what you've already noticed. You could try to remove > > iwi(4) from the kernel config and use it as module again, just to make > > sure it isn't related to that. Also, all modules iwi(4) depends on are > > pulled in automatically, even the firmware modules, no need to load em > > through loader.conf. > > >=20 > I copied GENERIC and removed the "device iwi" line. I rebooted but still > got the same message. I also tried removing the iwi device and introducing > the iwifw in the kernel (so I got a couple of complaints from the kernel > when loading since I didn't change my loader.conf). Still the same error. >=20 >=20 >=20 > > Can you post dmesg and pciconf -lvc? > > >=20 > Yes. Thanks, nothing obvious in there though. I played a bit around with an iwi(4) device on a i386 and a amd64 box and I was not able to reproduce the issue you are seeing. This smells like it's related to the laptop you are using, which model is that? Honestly, I have no clue currently what is to blame. Given that there were some ACPI/PCI bus changes between 8 and 9, mind posting the pciconf -lb output for the iwi0 device? You could also try to rule out as many automatic things as possible. Remove everything related to wireless out of the kernel config, remove the entries in loader.conf and rc.conf and run the following commands after a reboot (no wlan modules should be loaded at that point): kldload wlan_ccmp kldload wlan_tkip kldload if_iwi ifconfig wlan0 create wlandev iwi0 wpa_supplicant -Dbsd -iwlan0 -c/etc/wpa_supplicant.conf -B =2D-=20 Bernhard From owner-freebsd-wireless@FreeBSD.ORG Wed Feb 29 22:33:41 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 862F3106566C for ; Wed, 29 Feb 2012 22:33:41 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id EC71E8FC08 for ; Wed, 29 Feb 2012 22:33:40 +0000 (UTC) Received: by lagv3 with SMTP id v3so1382572lag.13 for ; Wed, 29 Feb 2012 14:33:39 -0800 (PST) Received-SPF: pass (google.com: domain of fernando.apesteguia@gmail.com designates 10.152.110.102 as permitted sender) client-ip=10.152.110.102; Authentication-Results: mr.google.com; spf=pass (google.com: domain of fernando.apesteguia@gmail.com designates 10.152.110.102 as permitted sender) smtp.mail=fernando.apesteguia@gmail.com; dkim=pass header.i=fernando.apesteguia@gmail.com Received: from mr.google.com ([10.152.110.102]) by 10.152.110.102 with SMTP id hz6mr2420871lab.21.1330554819847 (num_hops = 1); Wed, 29 Feb 2012 14:33:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=TBaE7C0c+B9X2grZYZEOhyoP8bmOzOJSKlFW3tVmbOE=; b=TMJI41qz3K3PryLV6utU097pfWorBzxamBG7bF/DM3fFad1c1cqJfoAFP47S4c8EUr VI1BvHMmQXgMcXNuH1Gzt8b8F78F7dAZRSKPXAp+4CPrpdoLy2MJzrRlF6EVJlL44EBj rhKPTFJbSDaE1nnMeBwMUpfGylEHwh1W46ZO8= MIME-Version: 1.0 Received: by 10.152.110.102 with SMTP id hz6mr1971393lab.21.1330554819759; Wed, 29 Feb 2012 14:33:39 -0800 (PST) Received: by 10.152.13.72 with HTTP; Wed, 29 Feb 2012 14:33:39 -0800 (PST) In-Reply-To: <201202292045.11498.bschmidt@techwires.net> References: <201202292045.11498.bschmidt@techwires.net> Date: Wed, 29 Feb 2012 23:33:39 +0100 Message-ID: From: =?ISO-8859-1?Q?Fernando_Apestegu=EDa?= To: Bernhard Schmidt Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: Re: iwi firmware X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 29 Feb 2012 22:33:41 -0000 On Wed, Feb 29, 2012 at 8:45 PM, Bernhard Schmidt w= rote: > On Wednesday 29 February 2012 18:06:43 Fernando Apestegu=EDa wrote: > > On Wed, Feb 29, 2012 at 10:09 AM, Bernhard Schmidt > > wrote: > > > > > On Tue, Feb 28, 2012 at 23:20, Fernando Apestegu=EDa > > > wrote: > > > > Hi all, > > > > > > > > I recently installed 9.0-RELEASE on my old laptop. I used the ipw22= 00 > > > card > > > > in this laptop with 8.2-RELEASE without problems. However I have > missed > > > > something I can't figure out. I get the message: > > > > > > > > iwi0: timeout processing command blocks for iwi_bss firmware > > > > iwi0: could not load main firmware iwi_bss > > > > > > > > This is what I have in my loader.conf: > > > > > > > > # Agree Intel's agreement license > > > > legal.intel_iwi.license_ack=3D1 > > > > > > > > # wireless support > > > > #if_iwi_load=3D"YES" This is in kernel now... > > > > wlan_load=3D"YES" > > > > firmware_load=3D"YES" > > > > > > > > iwi_bss_load=3D"YES" > > > > iwi_ibss_load=3D"YES" > > > > iwi_monitor_load=3D"YES" > > > > > > > > what am I missing? > > > > > > > > Thanks in advance. > > > > > > Hmm, there haven't been any major changes to iwi(4) between 8.2 and > > > 9.0, except what you've already noticed. You could try to remove > > > iwi(4) from the kernel config and use it as module again, just to mak= e > > > sure it isn't related to that. Also, all modules iwi(4) depends on ar= e > > > pulled in automatically, even the firmware modules, no need to load e= m > > > through loader.conf. > > > > > > > I copied GENERIC and removed the "device iwi" line. I rebooted but stil= l > > got the same message. I also tried removing the iwi device and > introducing > > the iwifw in the kernel (so I got a couple of complaints from the kerne= l > > when loading since I didn't change my loader.conf). Still the same erro= r. > > > > > > > > > Can you post dmesg and pciconf -lvc? > > > > > > > Yes. > > Thanks, nothing obvious in there though. > > I played a bit around with an iwi(4) device on a i386 and a amd64 box > and I was not able to reproduce the issue you are seeing. This smells > like it's related to the laptop you are using, which model is that? > It is an old Clevo D400K. The wireless always worked (with all the known ipw2200 firmware bugs...) > > Honestly, I have no clue currently what is to blame. > > Given that there were some ACPI/PCI bus changes between 8 and 9, mind > posting the pciconf -lb output for the iwi0 device? > Interesting. It occurred to me to disable the ACPI support in the bootloader. Guess what? I get a panic _every single time_ I try to boot. I don't have the complete backtrace (is it written anywhere on disk?) but I get a trapcode=3D12 coming from iwi_detach0x31 coming from iwi_attach0x313 coming from device_attach... (with the wireless card physically turn off). So you're probably right and this is related to ACPI. The result of pciconf -lb is: iwi0@pci0:0:5:0: class=3D0x028000 card=3D0x27028086 chip=3D0x4220808= 6 rev=3D0x05 hdr=3D0x00 bar [10] =3D type Memory, range 32, base 0x80000000, size 4096, enabl= ed > > You could also try to rule out as many automatic things as possible. > Remove everything related to wireless out of the kernel config, remove > the entries in loader.conf and rc.conf and run the following commands > after a reboot (no wlan modules should be loaded at that point): > > kldload wlan_ccmp > kldload wlan_tkip > kldload if_iwi > ifconfig wlan0 create wlandev iwi0 > wpa_supplicant -Dbsd -iwlan0 -c/etc/wpa_supplicant.conf -B > I'll try to do it as soon as possible so I can give more information. Thanks in advance. > > -- > Bernhard > From owner-freebsd-wireless@FreeBSD.ORG Thu Mar 1 12:33:07 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 893C2106566B for ; Thu, 1 Mar 2012 12:33:07 +0000 (UTC) (envelope-from damjan.marion@gmail.com) Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id 1221D8FC13 for ; Thu, 1 Mar 2012 12:33:06 +0000 (UTC) Received: by wibhn6 with SMTP id hn6so414898wib.13 for ; Thu, 01 Mar 2012 04:33:06 -0800 (PST) Received-SPF: pass (google.com: domain of damjan.marion@gmail.com designates 10.180.14.230 as permitted sender) client-ip=10.180.14.230; Authentication-Results: mr.google.com; spf=pass (google.com: domain of damjan.marion@gmail.com designates 10.180.14.230 as permitted sender) smtp.mail=damjan.marion@gmail.com; dkim=pass header.i=damjan.marion@gmail.com Received: from mr.google.com ([10.180.14.230]) by 10.180.14.230 with SMTP id s6mr10342657wic.2.1330605186085 (num_hops = 1); Thu, 01 Mar 2012 04:33:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; bh=9x9xfJUXLwwAXi92z9PiX1KrJ1bMqhfnj2xwRK7rTJ8=; b=jOL++TsJTomJ9JXw6JJK96nYvlqXB5Wz5qEgUDgxB731dqTZlI9OX4jgQ2WMPvItFl yDqP+YEJrrzTIFG9bM5iJ1SeqBQK19DqmRp1Zbw0dBRNcj2cU9FB+yZQvnQfzEjOJr+5 d72Q5BVYwjvUaHhlj8jSVBgFJmcfT7MMgsq/w= Received: by 10.180.14.230 with SMTP id s6mr8031380wic.2.1330603305222; Thu, 01 Mar 2012 04:01:45 -0800 (PST) Received: from dhcp-10-61-97-2.cisco.com (64-103-25-233.cisco.com. [64.103.25.233]) by mx.google.com with ESMTPS id be4sm8739463wib.8.2012.03.01.04.01.44 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 01 Mar 2012 04:01:44 -0800 (PST) From: Damjan Marion Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 1 Mar 2012 13:01:43 +0100 Message-Id: To: freebsd-wireless@freebsd.org Mime-Version: 1.0 (Apple Message framework v1257) X-Mailer: Apple Mail (2.1257) Subject: run(4) in AP mode and battery consumption of mobile devices X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 01 Mar 2012 12:33:07 -0000 Hi, I switched recently to my homebuilt AP running FreeBSD 9. I'm using run(4) in AP mode and it works well except I have issue with battery consumption of mobile devices associated to it. Battery discharges rapidly, several times faster than on old AP. Does anybody else have/had similar issue? Is there anything what can be tweaked to improve this? Thanks, Damjan From owner-freebsd-wireless@FreeBSD.ORG Thu Mar 1 16:25:49 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5A85A106566B for ; Thu, 1 Mar 2012 16:25:49 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id D2EDE8FC16 for ; Thu, 1 Mar 2012 16:25:48 +0000 (UTC) Received: by werl4 with SMTP id l4so612322wer.13 for ; Thu, 01 Mar 2012 08:25:48 -0800 (PST) Received-SPF: pass (google.com: domain of adrian.chadd@gmail.com designates 10.180.95.1 as permitted sender) client-ip=10.180.95.1; Authentication-Results: mr.google.com; spf=pass (google.com: domain of adrian.chadd@gmail.com designates 10.180.95.1 as permitted sender) smtp.mail=adrian.chadd@gmail.com; dkim=pass header.i=adrian.chadd@gmail.com Received: from mr.google.com ([10.180.95.1]) by 10.180.95.1 with SMTP id dg1mr12280093wib.21.1330619148005 (num_hops = 1); Thu, 01 Mar 2012 08:25:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=7sb6IQSniB05XjeYoFz+RiVEnzMMqP8r1Cmr+EYyZy0=; b=iCXVTvX+5LIme2sCZgi0eALYu7tJpd6HcurDoPW0Or+YiaSyTyWhzATMbttFobnjr0 fM9rCQvd4Jfa7BO12BdreaKihVKDzvKPfPpuEYM3jHZLqVRfAXyk6vxeSe41GhOH8Jmm eR2jsPqckS7B7EdfHtuJSH453MB0b4SZMo6J0= MIME-Version: 1.0 Received: by 10.180.95.1 with SMTP id dg1mr9825747wib.21.1330619147824; Thu, 01 Mar 2012 08:25:47 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.198.81 with HTTP; Thu, 1 Mar 2012 08:25:47 -0800 (PST) In-Reply-To: References: Date: Thu, 1 Mar 2012 08:25:47 -0800 X-Google-Sender-Auth: W8aOoyyBFOKoMicOWxqNLaQX-8g Message-ID: From: Adrian Chadd To: Damjan Marion Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: run(4) in AP mode and battery consumption of mobile devices X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 01 Mar 2012 16:25:49 -0000 Hi, What were you using as an access point? It could be a power saving management issue with freebsd net80211, but it's also quite likely that one of the other power saving methods (ps-poll, uapsd) is supported by your AP but not FreeBSD net80211. I'd love to see pspoll/uapsd support in FreeBSD.. Adrian On 1 March 2012 04:01, Damjan Marion wrote: > > > Hi, > > I switched recently to my homebuilt AP running FreeBSD 9. > I'm using run(4) in AP mode and it works well except I have issue with > battery consumption of mobile devices associated to it. > > Battery discharges rapidly, several times faster than on old AP. > > Does anybody else have/had similar issue? > > Is there anything what can be tweaked to improve this? > > Thanks, > > Damjan > > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Thu Mar 1 17:25:52 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DE272106566B for ; Thu, 1 Mar 2012 17:25:52 +0000 (UTC) (envelope-from damjan.marion@gmail.com) Received: from mail-ee0-f54.google.com (mail-ee0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 656608FC1C for ; Thu, 1 Mar 2012 17:25:51 +0000 (UTC) Received: by eekd17 with SMTP id d17so338578eek.13 for ; Thu, 01 Mar 2012 09:25:51 -0800 (PST) Received-SPF: pass (google.com: domain of damjan.marion@gmail.com designates 10.14.182.134 as permitted sender) client-ip=10.14.182.134; Authentication-Results: mr.google.com; spf=pass (google.com: domain of damjan.marion@gmail.com designates 10.14.182.134 as permitted sender) smtp.mail=damjan.marion@gmail.com; dkim=pass header.i=damjan.marion@gmail.com Received: from mr.google.com ([10.14.182.134]) by 10.14.182.134 with SMTP id o6mr3571260eem.40.1330622751138 (num_hops = 1); Thu, 01 Mar 2012 09:25:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=vT4KZgaJVWaexdibJwCjhQF560gCC2Kp27138O1yy4k=; b=JHi/8lTReCiVhh/ZIsQ1Hcc7+kg00aYjrTpwriKH9KP3xNaWmKTQr4pDLhnrG6Ek1Q B2XSc6aZG8KPn0PB4vPvyVfoF3jIdz/BJezzB94m4TW/xqN1d0hwDF7zFl3I4jf34QT7 bWdeI604lQlBT3yjgfH+rHCOaOPwhmP/nKo4A= Received: by 10.14.182.134 with SMTP id o6mr2747528eem.40.1330622750993; Thu, 01 Mar 2012 09:25:50 -0800 (PST) Received: from [192.168.123.4] (cpe-109-60-86-108.zg3.cable.xnet.hr. [109.60.86.108]) by mx.google.com with ESMTPS id u11sm9496388eeb.1.2012.03.01.09.25.49 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 01 Mar 2012 09:25:50 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1257) Content-Type: text/plain; charset=iso-8859-1 From: Damjan Marion In-Reply-To: Date: Thu, 1 Mar 2012 18:25:48 +0100 Content-Transfer-Encoding: 7bit Message-Id: References: To: Adrian Chadd X-Mailer: Apple Mail (2.1257) Cc: freebsd-wireless@freebsd.org Subject: Re: run(4) in AP mode and battery consumption of mobile devices X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 01 Mar 2012 17:25:52 -0000 On Mar 1, 2012, at 5:25 PM, Adrian Chadd wrote: > Hi, > > What were you using as an access point? Cisco 1100 and Linksys WRT350Nv2/OpenWRT, much longer battery life on both... > > It could be a power saving management issue with freebsd net80211, but > it's also quite likely that one of the other power saving methods > (ps-poll, uapsd) is supported by your AP but not FreeBSD net80211. > > I'd love to see pspoll/uapsd support in FreeBSD.. > Anybody else have some experience with for example iPhone and FreeBSD AP? My battery discharge time is around 10 hours. BTW My performance is similar to the following post: http://forums.freebsd.org/showthread.php?t=7562&page=11 (search for iPhone) Thanks, Damjan From owner-freebsd-wireless@FreeBSD.ORG Thu Mar 1 19:45:52 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 09B711065670 for ; Thu, 1 Mar 2012 19:45:52 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: from mail-ey0-f182.google.com (mail-ey0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id 805868FC12 for ; Thu, 1 Mar 2012 19:45:51 +0000 (UTC) Received: by eaaf13 with SMTP id f13so383508eaa.13 for ; Thu, 01 Mar 2012 11:45:50 -0800 (PST) Received-SPF: pass (google.com: domain of fernando.apesteguia@gmail.com designates 10.112.105.164 as permitted sender) client-ip=10.112.105.164; Authentication-Results: mr.google.com; spf=pass (google.com: domain of fernando.apesteguia@gmail.com designates 10.112.105.164 as permitted sender) smtp.mail=fernando.apesteguia@gmail.com; dkim=pass header.i=fernando.apesteguia@gmail.com Received: from mr.google.com ([10.112.105.164]) by 10.112.105.164 with SMTP id gn4mr3095805lbb.23.1330631150375 (num_hops = 1); Thu, 01 Mar 2012 11:45:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=EtOol8wEpyLLlewNt4cV5xMVi4Xf3gDoV3FKLl6g7XM=; b=WCdPelA3ejBdpWT6xeH0+2mknYdlgfxekvKDwdidzQR+98BNLYIqJ91OZ3KUIBSUHp LVdnbIAtWDbB7Z4ymZiK95QoS8SyGNSTixt3PDQASULZGaMMjGCgYUT0SnbJD73PDWrE MQj+ux9PUHEZeiwkn2TuZFaIexAuyWVqs5+c0LzGg44lVfDghoNbwgzuDgAeFl2GZS3b FC+gJIhu6gsgmkvqMG7DL10yNTOTHWia4Vn6uQbxnxsvKEFKRznOd7AQCdNDmcVZUqK0 OrhBPyQIk4nxx4C/QLEZ/gyyNPuge6vcBhScgwK7COglzAjn9B5PPxaLI8xi+u6ayHtt IMTQ== MIME-Version: 1.0 Received: by 10.112.105.164 with SMTP id gn4mr2525998lbb.23.1330631150281; Thu, 01 Mar 2012 11:45:50 -0800 (PST) Received: by 10.152.13.72 with HTTP; Thu, 1 Mar 2012 11:45:50 -0800 (PST) In-Reply-To: References: <201202292045.11498.bschmidt@techwires.net> Date: Thu, 1 Mar 2012 20:45:50 +0100 Message-ID: From: =?ISO-8859-1?Q?Fernando_Apestegu=EDa?= To: Bernhard Schmidt Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: Re: iwi firmware X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 01 Mar 2012 19:45:52 -0000 On Wed, Feb 29, 2012 at 11:33 PM, Fernando Apestegu=EDa < fernando.apesteguia@gmail.com> wrote: > > > On Wed, Feb 29, 2012 at 8:45 PM, Bernhard Schmidt wrote: > >> On Wednesday 29 February 2012 18:06:43 Fernando Apestegu=EDa wrote: >> > On Wed, Feb 29, 2012 at 10:09 AM, Bernhard Schmidt >> > wrote: >> > >> > > On Tue, Feb 28, 2012 at 23:20, Fernando Apestegu=EDa >> > > wrote: >> > > > Hi all, >> > > > >> > > > I recently installed 9.0-RELEASE on my old laptop. I used the >> ipw2200 >> > > card >> > > > in this laptop with 8.2-RELEASE without problems. However I have >> missed >> > > > something I can't figure out. I get the message: >> > > > >> > > > iwi0: timeout processing command blocks for iwi_bss firmware >> > > > iwi0: could not load main firmware iwi_bss >> > > > >> > > > This is what I have in my loader.conf: >> > > > >> > > > # Agree Intel's agreement license >> > > > legal.intel_iwi.license_ack=3D1 >> > > > >> > > > # wireless support >> > > > #if_iwi_load=3D"YES" This is in kernel now... >> > > > wlan_load=3D"YES" >> > > > firmware_load=3D"YES" >> > > > >> > > > iwi_bss_load=3D"YES" >> > > > iwi_ibss_load=3D"YES" >> > > > iwi_monitor_load=3D"YES" >> > > > >> > > > what am I missing? >> > > > >> > > > Thanks in advance. >> > > >> > > Hmm, there haven't been any major changes to iwi(4) between 8.2 and >> > > 9.0, except what you've already noticed. You could try to remove >> > > iwi(4) from the kernel config and use it as module again, just to ma= ke >> > > sure it isn't related to that. Also, all modules iwi(4) depends on a= re >> > > pulled in automatically, even the firmware modules, no need to load = em >> > > through loader.conf. >> > > >> > >> > I copied GENERIC and removed the "device iwi" line. I rebooted but sti= ll >> > got the same message. I also tried removing the iwi device and >> introducing >> > the iwifw in the kernel (so I got a couple of complaints from the kern= el >> > when loading since I didn't change my loader.conf). Still the same >> error. >> > >> > >> > >> > > Can you post dmesg and pciconf -lvc? >> > > >> > >> > Yes. >> >> Thanks, nothing obvious in there though. >> >> I played a bit around with an iwi(4) device on a i386 and a amd64 box >> and I was not able to reproduce the issue you are seeing. This smells >> like it's related to the laptop you are using, which model is that? >> > > It is an old Clevo D400K. The wireless always worked (with all the known > ipw2200 firmware bugs...) > > >> >> Honestly, I have no clue currently what is to blame. >> >> Given that there were some ACPI/PCI bus changes between 8 and 9, mind >> posting the pciconf -lb output for the iwi0 device? >> > > Interesting. It occurred to me to disable the ACPI support in the > bootloader. Guess what? I get a panic _every single time_ I try to boot. = I > don't have the complete backtrace (is it written anywhere on disk?) but I > get a trapcode=3D12 coming from iwi_detach0x31 coming from iwi_attach0x31= 3 > coming from device_attach... (with the wireless card physically turn off)= . > > So you're probably right and this is related to ACPI. > > The result of pciconf -lb is: > > > iwi0@pci0:0:5:0: class=3D0x028000 card=3D0x27028086 chip=3D0x42208= 086 > rev=3D0x05 hdr=3D0x00 > bar [10] =3D type Memory, range 32, base 0x80000000, size 4096, ena= bled > > > >> >> You could also try to rule out as many automatic things as possible. >> Remove everything related to wireless out of the kernel config, remove >> the entries in loader.conf and rc.conf and run the following commands >> after a reboot (no wlan modules should be loaded at that point): >> >> kldload wlan_ccmp >> kldload wlan_tkip >> kldload if_iwi >> ifconfig wlan0 create wlandev iwi0 >> wpa_supplicant -Dbsd -iwlan0 -c/etc/wpa_supplicant.conf -B >> > Hi again, I did it and I got the same result. After executing the last statement I got the same error. For the record, I tried with a GENERIC kernel but still no luck. I can't even get a kernel dump (I guess it crashes too early during booting?) Any ideas? How can I pin point what the problem is? Thanks > > I'll try to do it as soon as possible so I can give more information. > > Thanks in advance. > > >> >> -- >> Bernhard >> > > From owner-freebsd-wireless@FreeBSD.ORG Thu Mar 1 20:18:13 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 45A491065672 for ; Thu, 1 Mar 2012 20:18:13 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id B70548FC13 for ; Thu, 1 Mar 2012 20:18:12 +0000 (UTC) Received: by wibhn6 with SMTP id hn6so237834wib.13 for ; Thu, 01 Mar 2012 12:18:11 -0800 (PST) Received-SPF: pass (google.com: domain of adrian.chadd@gmail.com designates 10.216.133.151 as permitted sender) client-ip=10.216.133.151; Authentication-Results: mr.google.com; spf=pass (google.com: domain of adrian.chadd@gmail.com designates 10.216.133.151 as permitted sender) smtp.mail=adrian.chadd@gmail.com; dkim=pass header.i=adrian.chadd@gmail.com Received: from mr.google.com ([10.216.133.151]) by 10.216.133.151 with SMTP id q23mr3652021wei.14.1330633091723 (num_hops = 1); Thu, 01 Mar 2012 12:18:11 -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 :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=3miZLsecTXfFF52gGOiK361OLXgB2pHWzfoYSWzevfg=; b=S2cwKu4//Q95XXu7N0KYMp8LvjRCAU6haIac2iH4AkMpuPnE1dHJszk5dJNYQr8mgw nq2sjbb8eqtsg0k0TQF5gtFb0cJIJtaHf/1cabpYLsxb9y97FUy0sSax7FqFvO72TBhA aYOw9iFeew7zq5IJ+TgXAx8XLTeGao1o7yneCQVVsELPSyT4RbHsF0N86Xsl+opESKAf 4jFWGFbGGvDwXQ+DVJILLhLcw4DMPbqlnellgAyIWKvAEcZ62MC8ITvpu76iw0ewwG4/ ZDCeIu+VeJW1Dy8ZlqDhIhDFRHwYn65oFHrRBtmeXL/ApoVSYIqxnKaHe1CLG7cPMpFP GOrw== MIME-Version: 1.0 Received: by 10.216.133.151 with SMTP id q23mr2939954wei.14.1330633091531; Thu, 01 Mar 2012 12:18:11 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.198.81 with HTTP; Thu, 1 Mar 2012 12:18:11 -0800 (PST) In-Reply-To: References: <201202292045.11498.bschmidt@techwires.net> Date: Thu, 1 Mar 2012 12:18:11 -0800 X-Google-Sender-Auth: Nt0iFDfDHlZDSHlQgibyu9ttv-g Message-ID: From: Adrian Chadd To: =?ISO-8859-1?Q?Fernando_Apestegu=EDa?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: iwi firmware X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 01 Mar 2012 20:18:13 -0000 I'd suggest opening up a PR. Unfortunately then I'd suggest testing various snapshots of 9.0-CURRENT back to when 8.0 was branched from it.. we have to try and find when/where it broke. Thanks, Adrian 2012/3/1 Fernando Apestegu=EDa : > On Wed, Feb 29, 2012 at 11:33 PM, Fernando Apestegu=EDa < > fernando.apesteguia@gmail.com> wrote: > >> >> >> On Wed, Feb 29, 2012 at 8:45 PM, Bernhard Schmidt wrote: >> >>> On Wednesday 29 February 2012 18:06:43 Fernando Apestegu=EDa wrote: >>> > On Wed, Feb 29, 2012 at 10:09 AM, Bernhard Schmidt >>> > wrote: >>> > >>> > > On Tue, Feb 28, 2012 at 23:20, Fernando Apestegu=EDa >>> > > wrote: >>> > > > Hi all, >>> > > > >>> > > > I recently installed 9.0-RELEASE on my old laptop. I used the >>> ipw2200 >>> > > card >>> > > > in this laptop with 8.2-RELEASE without problems. However I have >>> missed >>> > > > something I can't figure out. I get the message: >>> > > > >>> > > > iwi0: timeout processing command blocks for iwi_bss firmware >>> > > > iwi0: could not load main firmware iwi_bss >>> > > > >>> > > > This is what I have in my loader.conf: >>> > > > >>> > > > # Agree Intel's agreement license >>> > > > legal.intel_iwi.license_ack=3D1 >>> > > > >>> > > > # wireless support >>> > > > #if_iwi_load=3D"YES" =A0 =A0 =A0This is in kernel now... >>> > > > wlan_load=3D"YES" >>> > > > firmware_load=3D"YES" >>> > > > >>> > > > iwi_bss_load=3D"YES" >>> > > > iwi_ibss_load=3D"YES" >>> > > > iwi_monitor_load=3D"YES" >>> > > > >>> > > > what am I missing? >>> > > > >>> > > > Thanks in advance. >>> > > >>> > > Hmm, there haven't been any major changes to iwi(4) between 8.2 and >>> > > 9.0, except what you've already noticed. You could try to remove >>> > > iwi(4) from the kernel config and use it as module again, just to m= ake >>> > > sure it isn't related to that. Also, all modules iwi(4) depends on = are >>> > > pulled in automatically, even the firmware modules, no need to load= em >>> > > through loader.conf. >>> > > >>> > >>> > I copied GENERIC and removed the "device iwi" line. I rebooted but st= ill >>> > got the same message. I also tried removing the iwi device and >>> introducing >>> > the iwifw in the kernel (so I got a couple of complaints from the ker= nel >>> > when loading since I didn't change my loader.conf). Still the same >>> error. >>> > >>> > >>> > >>> > > Can you post dmesg and pciconf -lvc? >>> > > >>> > >>> > Yes. >>> >>> Thanks, nothing obvious in there though. >>> >>> I played a bit around with an iwi(4) device on a i386 and a amd64 box >>> and I was not able to reproduce the issue you are seeing. This smells >>> like it's related to the laptop you are using, which model is that? >>> >> >> It is an old Clevo D400K. The wireless always worked (with all the known >> ipw2200 firmware bugs...) >> >> >>> >>> Honestly, I have no clue currently what is to blame. >>> >>> Given that there were some ACPI/PCI bus changes between 8 and 9, mind >>> posting the pciconf -lb output for the iwi0 device? >>> >> >> Interesting. It occurred to me to disable the ACPI support in the >> bootloader. Guess what? I get a panic _every single time_ I try to boot.= I >> don't have the complete backtrace (is it written anywhere on disk?) but = I >> get a trapcode=3D12 coming from iwi_detach0x31 coming from iwi_attach0x3= 13 >> coming from device_attach... (with the wireless card physically turn off= ). >> >> So you're probably right and this is related to ACPI. >> >> The result of pciconf -lb is: >> >> >> iwi0@pci0:0:5:0: =A0 =A0 =A0 =A0class=3D0x028000 card=3D0x27028086 chip= =3D0x42208086 >> rev=3D0x05 hdr=3D0x00 >> =A0 =A0 bar =A0 [10] =3D type Memory, range 32, base 0x80000000, size 40= 96, enabled >> >> >> >>> >>> You could also try to rule out as many automatic things as possible. >>> Remove everything related to wireless out of the kernel config, remove >>> the entries in loader.conf and rc.conf and run the following commands >>> after a reboot (no wlan modules should be loaded at that point): >>> >>> kldload wlan_ccmp >>> kldload wlan_tkip >>> kldload if_iwi >>> ifconfig wlan0 create wlandev iwi0 >>> wpa_supplicant -Dbsd -iwlan0 -c/etc/wpa_supplicant.conf -B >>> >> > Hi again, > > I did it and I got the same result. After executing the last statement I > got the same error. For the record, I tried with a GENERIC kernel but sti= ll > no luck. I can't even get a kernel dump (I guess it crashes too early > during booting?) > > Any ideas? > > How can I pin point what the problem is? > > Thanks > > >> >> I'll try to do it as soon as possible so I can give more information. >> >> Thanks in advance. >> >> >>> >>> -- >>> Bernhard >>> >> >> > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.or= g" From owner-freebsd-wireless@FreeBSD.ORG Thu Mar 1 20:59:45 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EDD80106564A for ; Thu, 1 Mar 2012 20:59:45 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 784F68FC0A for ; Thu, 1 Mar 2012 20:59:44 +0000 (UTC) Received: by wgbds12 with SMTP id ds12so901010wgb.31 for ; Thu, 01 Mar 2012 12:59:43 -0800 (PST) Received-SPF: pass (google.com: domain of adrian.chadd@gmail.com designates 10.180.95.105 as permitted sender) client-ip=10.180.95.105; Authentication-Results: mr.google.com; spf=pass (google.com: domain of adrian.chadd@gmail.com designates 10.180.95.105 as permitted sender) smtp.mail=adrian.chadd@gmail.com; dkim=pass header.i=adrian.chadd@gmail.com Received: from mr.google.com ([10.180.95.105]) by 10.180.95.105 with SMTP id dj9mr14269235wib.18.1330635583832 (num_hops = 1); Thu, 01 Mar 2012 12:59:43 -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 :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Xf7YH0mKVtaKfs+4xG9xeXAGG/qeeRc9Gnw+XYEvXWc=; b=uMn2LX0vSEIflcnAPi2gXz6WyuD8EQAAfloadjZLrV4qylruAcM0Qao5mFQMZYjjm1 rxbCf/wVj3RvyXA1yNcP9NY0KKf8G/UWrdMwHTsGZB1aNxzGqG5I3ty6Ogog2/ZSm60W 57jDIkEthWWO3Q9L167M8HS2o3y2bByOu/6lDl5mTPlALgHZ9ZV3M+6nVos+XS8oRnNC MME/XjGOOl+XbejVg5ykxxXxt11gQQ6bZar+uPFarscDd3RHIXpfG7JotZcNZwerOuWP NZJgPvlxCtM9utLoYRNA0A2FDZN3IxeExSSavoLBorBj/LSjuSQqyWs1uOtGHoUzXl2P ojww== MIME-Version: 1.0 Received: by 10.180.95.105 with SMTP id dj9mr11448491wib.18.1330635583654; Thu, 01 Mar 2012 12:59:43 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.198.81 with HTTP; Thu, 1 Mar 2012 12:59:43 -0800 (PST) In-Reply-To: References: Date: Thu, 1 Mar 2012 12:59:43 -0800 X-Google-Sender-Auth: IGYl0rKMTlIzByu2AZoqPFrCYtw Message-ID: From: Adrian Chadd To: Damjan Marion Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: run(4) in AP mode and battery consumption of mobile devices X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 01 Mar 2012 20:59:46 -0000 Hi, I'd get in dirty with an ath nic in monitor mode. See what's going on. I'd look at what the TIM bits are set in the access point beacon frames. Maybe it's doing something weird like waways setting them. Adrian On 1 March 2012 09:25, Damjan Marion wrote: > > On Mar 1, 2012, at 5:25 PM, Adrian Chadd wrote: > >> Hi, >> >> What were you using as an access point? > > Cisco 1100 and Linksys WRT350Nv2/OpenWRT, much longer battery life on both... > >> >> It could be a power saving management issue with freebsd net80211, but >> it's also quite likely that one of the other power saving methods >> (ps-poll, uapsd) is supported by your AP but not FreeBSD net80211. >> >> I'd love to see pspoll/uapsd support in FreeBSD.. >> > > Anybody else have some experience with for example iPhone and FreeBSD AP? > My battery discharge time is around 10 hours. > > BTW My performance is similar to the following post: > > http://forums.freebsd.org/showthread.php?t=7562&page=11 (search for iPhone) > > Thanks, > > Damjan > > > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Thu Mar 1 21:16:48 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7F17C106564A for ; Thu, 1 Mar 2012 21:16:48 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 6BD4A8FC19 for ; Thu, 1 Mar 2012 21:16:47 +0000 (UTC) Received: by lagv3 with SMTP id v3so1688904lag.13 for ; Thu, 01 Mar 2012 13:16:46 -0800 (PST) Received-SPF: pass (google.com: domain of fernando.apesteguia@gmail.com designates 10.152.122.74 as permitted sender) client-ip=10.152.122.74; Authentication-Results: mr.google.com; spf=pass (google.com: domain of fernando.apesteguia@gmail.com designates 10.152.122.74 as permitted sender) smtp.mail=fernando.apesteguia@gmail.com; dkim=pass header.i=fernando.apesteguia@gmail.com Received: from mr.google.com ([10.152.122.74]) by 10.152.122.74 with SMTP id lq10mr6990300lab.7.1330636606230 (num_hops = 1); Thu, 01 Mar 2012 13:16:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ZiRi1RD7siZWx9VibkKO32kf6tAZ3bPVyob1NGeuRtM=; b=XlxAyQcxBHf55gqS2Y40amjBXNh3bhsSRqSccdLs/VUJIVE9vCNK+sG4fQ/iEdBip8 Su/S0HjinrHvEnp6vQ1I7qOP/VtknjNbnmleasumPYcs3zOrn4oXf6Q2jKu0/v+0dB/O jkl1HEj3bWB0bp4Mtk3W9eqpwqid5DtDPfROJQex30h4kpkKXslhD5zZGkXQrcJsiimT secoGKob8U6NrS4OqahsJS6mwt5TS7jzYsb4FIdkxvp3SrK9WKtuCLwihp9SRO+43C+S bbyOj4BdNRji6oRmSewN8UttMqOibjUv1QeGXQaHjeIxrn1k+uCu5sLvWoB6lKGLx80D 2gqw== MIME-Version: 1.0 Received: by 10.152.122.74 with SMTP id lq10mr5711258lab.7.1330636606143; Thu, 01 Mar 2012 13:16:46 -0800 (PST) Received: by 10.152.13.72 with HTTP; Thu, 1 Mar 2012 13:16:46 -0800 (PST) In-Reply-To: References: <201202292045.11498.bschmidt@techwires.net> Date: Thu, 1 Mar 2012 22:16:46 +0100 Message-ID: From: =?ISO-8859-1?Q?Fernando_Apestegu=EDa?= To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: Re: iwi firmware X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 01 Mar 2012 21:16:48 -0000 On Thu, Mar 1, 2012 at 9:18 PM, Adrian Chadd wrote: > I'd suggest opening up a PR. > Done kern/165595 > > Unfortunately then I'd suggest testing various snapshots of > 9.0-CURRENT back to when 8.0 was branched from it.. we have to try and > find when/where it broke. > > Thanks, > > > Adrian > > 2012/3/1 Fernando Apestegu=EDa : > > On Wed, Feb 29, 2012 at 11:33 PM, Fernando Apestegu=EDa < > > fernando.apesteguia@gmail.com> wrote: > > > >> > >> > >> On Wed, Feb 29, 2012 at 8:45 PM, Bernhard Schmidt < > bschmidt@techwires.net>wrote: > >> > >>> On Wednesday 29 February 2012 18:06:43 Fernando Apestegu=EDa wrote: > >>> > On Wed, Feb 29, 2012 at 10:09 AM, Bernhard Schmidt > >>> > wrote: > >>> > > >>> > > On Tue, Feb 28, 2012 at 23:20, Fernando Apestegu=EDa > >>> > > wrote: > >>> > > > Hi all, > >>> > > > > >>> > > > I recently installed 9.0-RELEASE on my old laptop. I used the > >>> ipw2200 > >>> > > card > >>> > > > in this laptop with 8.2-RELEASE without problems. However I hav= e > >>> missed > >>> > > > something I can't figure out. I get the message: > >>> > > > > >>> > > > iwi0: timeout processing command blocks for iwi_bss firmware > >>> > > > iwi0: could not load main firmware iwi_bss > >>> > > > > >>> > > > This is what I have in my loader.conf: > >>> > > > > >>> > > > # Agree Intel's agreement license > >>> > > > legal.intel_iwi.license_ack=3D1 > >>> > > > > >>> > > > # wireless support > >>> > > > #if_iwi_load=3D"YES" This is in kernel now... > >>> > > > wlan_load=3D"YES" > >>> > > > firmware_load=3D"YES" > >>> > > > > >>> > > > iwi_bss_load=3D"YES" > >>> > > > iwi_ibss_load=3D"YES" > >>> > > > iwi_monitor_load=3D"YES" > >>> > > > > >>> > > > what am I missing? > >>> > > > > >>> > > > Thanks in advance. > >>> > > > >>> > > Hmm, there haven't been any major changes to iwi(4) between 8.2 a= nd > >>> > > 9.0, except what you've already noticed. You could try to remove > >>> > > iwi(4) from the kernel config and use it as module again, just to > make > >>> > > sure it isn't related to that. Also, all modules iwi(4) depends o= n > are > >>> > > pulled in automatically, even the firmware modules, no need to > load em > >>> > > through loader.conf. > >>> > > > >>> > > >>> > I copied GENERIC and removed the "device iwi" line. I rebooted but > still > >>> > got the same message. I also tried removing the iwi device and > >>> introducing > >>> > the iwifw in the kernel (so I got a couple of complaints from the > kernel > >>> > when loading since I didn't change my loader.conf). Still the same > >>> error. > >>> > > >>> > > >>> > > >>> > > Can you post dmesg and pciconf -lvc? > >>> > > > >>> > > >>> > Yes. > >>> > >>> Thanks, nothing obvious in there though. > >>> > >>> I played a bit around with an iwi(4) device on a i386 and a amd64 box > >>> and I was not able to reproduce the issue you are seeing. This smells > >>> like it's related to the laptop you are using, which model is that? > >>> > >> > >> It is an old Clevo D400K. The wireless always worked (with all the kno= wn > >> ipw2200 firmware bugs...) > >> > >> > >>> > >>> Honestly, I have no clue currently what is to blame. > >>> > >>> Given that there were some ACPI/PCI bus changes between 8 and 9, mind > >>> posting the pciconf -lb output for the iwi0 device? > >>> > >> > >> Interesting. It occurred to me to disable the ACPI support in the > >> bootloader. Guess what? I get a panic _every single time_ I try to > boot. I > >> don't have the complete backtrace (is it written anywhere on disk?) bu= t > I > >> get a trapcode=3D12 coming from iwi_detach0x31 coming from iwi_attach0= x313 > >> coming from device_attach... (with the wireless card physically turn > off). > >> > >> So you're probably right and this is related to ACPI. > >> > >> The result of pciconf -lb is: > >> > >> > >> iwi0@pci0:0:5:0: class=3D0x028000 card=3D0x27028086 chip=3D0x42= 208086 > >> rev=3D0x05 hdr=3D0x00 > >> bar [10] =3D type Memory, range 32, base 0x80000000, size 4096, > enabled > >> > >> > >> > >>> > >>> You could also try to rule out as many automatic things as possible. > >>> Remove everything related to wireless out of the kernel config, remov= e > >>> the entries in loader.conf and rc.conf and run the following commands > >>> after a reboot (no wlan modules should be loaded at that point): > >>> > >>> kldload wlan_ccmp > >>> kldload wlan_tkip > >>> kldload if_iwi > >>> ifconfig wlan0 create wlandev iwi0 > >>> wpa_supplicant -Dbsd -iwlan0 -c/etc/wpa_supplicant.conf -B > >>> > >> > > Hi again, > > > > I did it and I got the same result. After executing the last statement = I > > got the same error. For the record, I tried with a GENERIC kernel but > still > > no luck. I can't even get a kernel dump (I guess it crashes too early > > during booting?) > > > > Any ideas? > > > > How can I pin point what the problem is? > > > > Thanks > > > > > >> > >> I'll try to do it as soon as possible so I can give more information. > >> > >> Thanks in advance. > >> > >> > >>> > >>> -- > >>> Bernhard > >>> > >> > >> > > _______________________________________________ > > freebsd-wireless@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > > To unsubscribe, send any mail to " > freebsd-wireless-unsubscribe@freebsd.org" > From owner-freebsd-wireless@FreeBSD.ORG Thu Mar 1 21:33:10 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0CEB8106564A; Thu, 1 Mar 2012 21:33:10 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D91048FC08; Thu, 1 Mar 2012 21:33:09 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q21LX9bG098012; Thu, 1 Mar 2012 21:33:09 GMT (envelope-from gjb@freefall.freebsd.org) Received: (from gjb@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q21LX9Mu098008; Thu, 1 Mar 2012 21:33:09 GMT (envelope-from gjb) Date: Thu, 1 Mar 2012 21:33:09 GMT Message-Id: <201203012133.q21LX9Mu098008@freefall.freebsd.org> To: gjb@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: gjb@FreeBSD.org Cc: Subject: Re: kern/165595: [ipw] ipw(4): Can't load firmare for ipw2200bg X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 01 Mar 2012 21:33:10 -0000 Old Synopsis: Can't load firmare for ipw2200bg New Synopsis: [ipw] ipw(4): Can't load firmare for ipw2200bg Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: gjb Responsible-Changed-When: Thu Mar 1 21:32:22 UTC 2012 Responsible-Changed-Why: Over to maintainers. http://www.freebsd.org/cgi/query-pr.cgi?pr=165595 From owner-freebsd-wireless@FreeBSD.ORG Thu Mar 1 22:30:32 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2F35B1065673; Thu, 1 Mar 2012 22:30:32 +0000 (UTC) (envelope-from damjan.marion@gmail.com) Received: from mail-ey0-f182.google.com (mail-ey0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id 7435A8FC1A; Thu, 1 Mar 2012 22:30:31 +0000 (UTC) Received: by eaaf13 with SMTP id f13so425596eaa.13 for ; Thu, 01 Mar 2012 14:30:30 -0800 (PST) Received-SPF: pass (google.com: domain of damjan.marion@gmail.com designates 10.213.31.79 as permitted sender) client-ip=10.213.31.79; Authentication-Results: mr.google.com; spf=pass (google.com: domain of damjan.marion@gmail.com designates 10.213.31.79 as permitted sender) smtp.mail=damjan.marion@gmail.com; dkim=pass header.i=damjan.marion@gmail.com Received: from mr.google.com ([10.213.31.79]) by 10.213.31.79 with SMTP id x15mr802609ebc.100.1330641030621 (num_hops = 1); Thu, 01 Mar 2012 14:30:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=ZhaMp5rKapkGBoZVQnesUUtYZLCHD0HqewE73ZhPadQ=; b=m6iIbwK8e34yZ7jHj9f2HYHQNHwpSdwukRolUEqrysZdO+nQMv+x+WPRudsIss6Z7V pOB7Ky4CJTa47xG7yHAHINwAL+wkWQrQgriCApBJMMyTT9EkXK29pOAeUPc+X0V6uLHJ aacwUHxNjBpawRMVApwuSC0lta+A1CsS10u2/lkjwLI4N6HIydygukL9ICjvoy5QD0dK RC505lg/KUGoWneNAdcU4MbWnSiUn9jMDGFGBPIzmhcRhiT+8VrZuVfKUNQCsDLlPDmg Tj/dkUCcqBAwKxbyPQRpfWCTCVsydOt0NkW8uqDskKfPnzBRudZ6jdfONkRMYy2abMlw v7xw== Received: by 10.213.31.79 with SMTP id x15mr613681ebc.100.1330641030493; Thu, 01 Mar 2012 14:30:30 -0800 (PST) Received: from damarion-mac-wlan.home (cpe-109-60-86-108.zg3.cable.xnet.hr. [109.60.86.108]) by mx.google.com with ESMTPS id o49sm12356286eeb.7.2012.03.01.14.30.29 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 01 Mar 2012 14:30:29 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1257) Content-Type: text/plain; charset=iso-8859-1 From: Damjan Marion In-Reply-To: Date: Thu, 1 Mar 2012 23:30:27 +0100 Content-Transfer-Encoding: 7bit Message-Id: References: To: Adrian Chadd X-Mailer: Apple Mail (2.1257) Cc: freebsd-wireless@freebsd.org Subject: Re: run(4) in AP mode and battery consumption of mobile devices X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 01 Mar 2012 22:30:32 -0000 On Mar 1, 2012, at 9:59 PM, Adrian Chadd wrote: > Hi, > > I'd get in dirty with an ath nic in monitor mode. See what's going on. > > I'd look at what the TIM bits are set in the access point beacon > frames. Maybe it's doing something weird like waways setting them. > Ok, I captured one beacon[1] and also traffic from and to my iphone[2]. Phone is associated and in standby mode. Can you be so kind and take a look? Thanks, Damjan [1] http://pastebin.com/raw.php?i=kKYRYa9k [2] http://pastebin.com/raw.php?i=P7UnUYts From owner-freebsd-wireless@FreeBSD.ORG Thu Mar 1 22:32:44 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B9C9710657B8 for ; Thu, 1 Mar 2012 22:32:44 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id 4460E8FC1B for ; Thu, 1 Mar 2012 22:32:43 +0000 (UTC) Received: by wibhn6 with SMTP id hn6so321202wib.13 for ; Thu, 01 Mar 2012 14:32:43 -0800 (PST) Received-SPF: pass (google.com: domain of adrian.chadd@gmail.com designates 10.180.85.69 as permitted sender) client-ip=10.180.85.69; Authentication-Results: mr.google.com; spf=pass (google.com: domain of adrian.chadd@gmail.com designates 10.180.85.69 as permitted sender) smtp.mail=adrian.chadd@gmail.com; dkim=pass header.i=adrian.chadd@gmail.com Received: from mr.google.com ([10.180.85.69]) by 10.180.85.69 with SMTP id f5mr14773271wiz.18.1330641163316 (num_hops = 1); Thu, 01 Mar 2012 14:32:43 -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 :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=gYIYHGqEBtVlnjeMBCSM+HEnXGTcRKRPZTo3X3bnie0=; b=biH2aOPek5y/6/NWDfPGliaSEdteBHwEIg5bVHvP0zUnaIsx0gewdkIqDWiZwJna/D CkJRupTjzLfdudaUSxNkXAQhdJ5ra7nVePWcOeUxZNZKv/w81XJ4chRr1PI12e0iuRbW Pg0Lzl8s9si3rjygxqGUMi1z8X3lQSjHDwBpiWljYiRA3wD+DtUsyJIvA2YttVM9QJD+ XpikdBCA/pVA3tsgu3WXViHkiuj8IYW+o6v1+CAFM07jT/vKXGQlKJrf2qK77yvBXMoX rl7CEuHQSN3OLwysdATnv/jcUYFi3MRvn7JexdzCnY+3jDidXM++tFuLvKZcSo9m/TPY uSjg== MIME-Version: 1.0 Received: by 10.180.85.69 with SMTP id f5mr11842759wiz.18.1330641163267; Thu, 01 Mar 2012 14:32:43 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.198.81 with HTTP; Thu, 1 Mar 2012 14:32:43 -0800 (PST) In-Reply-To: References: Date: Thu, 1 Mar 2012 14:32:43 -0800 X-Google-Sender-Auth: IwmQIRNYdinlgfdvpUFX4P9YXG0 Message-ID: From: Adrian Chadd To: Damjan Marion Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: run(4) in AP mode and battery consumption of mobile devices X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 01 Mar 2012 22:32:44 -0000 Hi, I don't have the time unfortunately to sit down and debug this. I think you're going to be on your own for a while. I suggest comparing packet traces between openwrt and freebsd, looking for differences in how things work. I'm sorry I can't be more help at the moment. I'm oversubscribed as it is. Thanks and good luck! Adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Mar 1 22:48:53 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C1162106566C; Thu, 1 Mar 2012 22:48:53 +0000 (UTC) (envelope-from damjan.marion@gmail.com) Received: from mail-ey0-f182.google.com (mail-ey0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id 18E048FC1D; Thu, 1 Mar 2012 22:48:52 +0000 (UTC) Received: by eaaf13 with SMTP id f13so428931eaa.13 for ; Thu, 01 Mar 2012 14:48:51 -0800 (PST) Received-SPF: pass (google.com: domain of damjan.marion@gmail.com designates 10.14.38.193 as permitted sender) client-ip=10.14.38.193; Authentication-Results: mr.google.com; spf=pass (google.com: domain of damjan.marion@gmail.com designates 10.14.38.193 as permitted sender) smtp.mail=damjan.marion@gmail.com; dkim=pass header.i=damjan.marion@gmail.com Received: from mr.google.com ([10.14.38.193]) by 10.14.38.193 with SMTP id a41mr4235877eeb.125.1330642131964 (num_hops = 1); Thu, 01 Mar 2012 14:48:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=v7C5uKcAB4BzAn8GIzQmdfm4sKJGVzYSnowF2H2R1eA=; b=tyVpKLKWDuXb/XSXFAUl7QbhE+lE8PnMWxQ/S9zFGs4yv6YpjA8MJZf+XC/z5l02MW e5tzIiQ1sPDo62gA4slWtM+c+wN9jFOJ8t9iS61YHIaSc8re4GeS0lAU7LHwF2yVkT9Z d8lgE6NxaMhXMaHtKeCvdoZFVTSpgItkbWM3vTRqpqvTlGO0rcaJ1vo+SkPFMsxIplH5 NTFd4SxPqix0uvWNWYJOnskdxSQpzoJaa7vFxYa+MNQNp1FsW0nuHvQIE6iC/dO3+Cn0 1H52ttOyw5b1aNVOumZzLKHmpFhj7is4BJoFOBqUwlA/WggNNn4Tdk09l1bkUSVBukJg g/Qg== Received: by 10.14.38.193 with SMTP id a41mr3235003eeb.125.1330642131829; Thu, 01 Mar 2012 14:48:51 -0800 (PST) Received: from damarion-mac-wlan.home (cpe-109-60-86-108.zg3.cable.xnet.hr. [109.60.86.108]) by mx.google.com with ESMTPS id s48sm12612175eem.0.2012.03.01.14.48.50 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 01 Mar 2012 14:48:50 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1257) Content-Type: text/plain; charset=iso-8859-1 From: Damjan Marion In-Reply-To: Date: Thu, 1 Mar 2012 23:48:49 +0100 Content-Transfer-Encoding: 7bit Message-Id: References: To: Adrian Chadd X-Mailer: Apple Mail (2.1257) Cc: freebsd-wireless@freebsd.org Subject: Re: run(4) in AP mode and battery consumption of mobile devices X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 01 Mar 2012 22:48:53 -0000 On Mar 1, 2012, at 11:32 PM, Adrian Chadd wrote: > Hi, > > I don't have the time unfortunately to sit down and debug this. I > think you're going to be on your own for a while. > > I suggest comparing packet traces between openwrt and freebsd, looking > for differences in how things work. > > I'm sorry I can't be more help at the moment. I'm oversubscribed as it is. > > Thanks and good luck! > sorry, i didn't want to engage you into troubleshooting session. Just wanted to ask you to take a 10 seconds look, as maybe you will notice something obviously wrong. Thanks anyway. From owner-freebsd-wireless@FreeBSD.ORG Thu Mar 1 23:53:41 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 834211065674 for ; Thu, 1 Mar 2012 23:53:41 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 043C48FC13 for ; Thu, 1 Mar 2012 23:53:40 +0000 (UTC) Received: by werl4 with SMTP id l4so924055wer.13 for ; Thu, 01 Mar 2012 15:53:39 -0800 (PST) Received-SPF: pass (google.com: domain of adrian.chadd@gmail.com designates 10.216.133.151 as permitted sender) client-ip=10.216.133.151; Authentication-Results: mr.google.com; spf=pass (google.com: domain of adrian.chadd@gmail.com designates 10.216.133.151 as permitted sender) smtp.mail=adrian.chadd@gmail.com; dkim=pass header.i=adrian.chadd@gmail.com Received: from mr.google.com ([10.216.133.151]) by 10.216.133.151 with SMTP id q23mr3964084wei.14.1330646019981 (num_hops = 1); Thu, 01 Mar 2012 15:53:39 -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 :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=8b1N4gll37Le6ciuBYJ0UuYnUxwYaMf7rpdfV5GVm8Q=; b=qZ0F10BWp0k4+oXrMreoQqyjD7JrHSqjhiD588Lsf/XJNWjgUUQEJoGYJnQnEKU3Fm P9SrgDW0Rk3L2q6UJCbO6y/zwhJ4CwyoS+Nu/s3NWvDLj08fHIgunI1N+D/NgzJhoKlE joDFPt7o2rZImQr6EZpfeoFKdpn8upHdGdjsLb6tnrdeu8SrS2o3RIEIGUhTk3lS28hM ri/F/7qS3cUWV+HirlGaufJJYIAoZHX5YUSNotCWRWZcYrglPOF0G+57KbrwzB+nUrkN T74olZan69ol6I/EiWAGSxjb9+iSwIjpTS33mroJzgU6Q0YBOxm+2nS+TjQsf02P044s ZOpw== MIME-Version: 1.0 Received: by 10.216.133.151 with SMTP id q23mr3196154wei.14.1330646019890; Thu, 01 Mar 2012 15:53:39 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.198.81 with HTTP; Thu, 1 Mar 2012 15:53:39 -0800 (PST) In-Reply-To: References: Date: Thu, 1 Mar 2012 15:53:39 -0800 X-Google-Sender-Auth: WcpdvRxiisxLP8Gd86rUt9cssCI Message-ID: From: Adrian Chadd To: Damjan Marion Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: run(4) in AP mode and battery consumption of mobile devices X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 01 Mar 2012 23:53:41 -0000 Hm, can you please check what the TIM IE Has in both net80211 and openwrt? I notice it's "1" here. I wonder if all of your beacon frames have that set. If they do, I wonder if the last CABQ frame is properly being tagged as "no more", so the station can actually _go_ to sleep.. Adrian On 1 March 2012 14:48, Damjan Marion wrote: > > On Mar 1, 2012, at 11:32 PM, Adrian Chadd wrote: > >> Hi, >> >> I don't have the time unfortunately to sit down and debug this. I >> think you're going to be on your own for a while. >> >> I suggest comparing packet traces between openwrt and freebsd, looking >> for differences in how things work. >> >> I'm sorry I can't be more help at the moment. I'm oversubscribed as it is. >> >> Thanks and good luck! >> > > > sorry, i didn't want to engage you into troubleshooting session. > Just wanted to ask you to take a 10 seconds look, as maybe you will notice > something obviously wrong. > > Thanks anyway. > > From owner-freebsd-wireless@FreeBSD.ORG Fri Mar 2 03:00:35 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 975A8106564A for ; Fri, 2 Mar 2012 03:00:35 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 6D03E8FC15 for ; Fri, 2 Mar 2012 03:00:35 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q2230Zmo098603 for ; Fri, 2 Mar 2012 03:00:35 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q2230Z5B098602; Fri, 2 Mar 2012 03:00:35 GMT (envelope-from gnats) Date: Fri, 2 Mar 2012 03:00:35 GMT Message-Id: <201203020300.q2230Z5B098602@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: kern/163318: commit references a PR X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service 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: Fri, 02 Mar 2012 03:00:35 -0000 The following reply was made to PR kern/163318; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/163318: commit references a PR Date: Fri, 2 Mar 2012 02:53:55 +0000 (UTC) Author: adrian Date: Fri Mar 2 02:53:43 2012 New Revision: 232373 URL: http://svn.freebsd.org/changeset/base/232373 Log: Attempt to catch scan cancellations at exactly the wrong time from occuring. The scan code unlocks the comlock and calls into the driver. It then assumes the state hasn't changed from underneath it. Although I haven't seen this particular condition trigger, I'd like to be informed if I or anyone else sees it. What I'm thinking may occur: * A cancellation comes in during the scan_end call; * the cancel flag is set; * but it's never checked, so scandone isn't updated; * .. and the interface stays in the STA power save mode. It's a subtle race, if it even exists. PR: kern/163318 Modified: head/sys/net80211/ieee80211_scan.c Modified: head/sys/net80211/ieee80211_scan.c ============================================================================== --- head/sys/net80211/ieee80211_scan.c Fri Mar 2 00:21:07 2012 (r232372) +++ head/sys/net80211/ieee80211_scan.c Fri Mar 2 02:53:43 2012 (r232373) @@ -960,6 +960,19 @@ scan_task(void *arg, int pending) IEEE80211_LOCK(ic); /* + * Since a cancellation may have occured during one of the + * driver calls (whilst unlocked), update scandone. + */ + if (scandone == 0 && + ((SCAN_PRIVATE(ss)->ss_iflags & ISCAN_CANCEL) != 0)) { + /* XXX printf? */ + if_printf(vap->iv_ifp, + "%s: OOPS! scan cancelled during driver call!\n", + __func__); + } + scandone |= ((SCAN_PRIVATE(ss)->ss_iflags & ISCAN_CANCEL) != 0); + + /* * Record scan complete time. Note that we also do * this when canceled so any background scan will * not be restarted for a while. _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Fri Mar 2 03:20:12 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D4EC3106564A for ; Fri, 2 Mar 2012 03:20:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C451A8FC0C for ; Fri, 2 Mar 2012 03:20:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q223KCgK017842 for ; Fri, 2 Mar 2012 03:20:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q223KC0t017841; Fri, 2 Mar 2012 03:20:12 GMT (envelope-from gnats) Date: Fri, 2 Mar 2012 03:20:12 GMT Message-Id: <201203020320.q223KC0t017841@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: kern/163318: commit references a PR X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service 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: Fri, 02 Mar 2012 03:20:12 -0000 The following reply was made to PR kern/163318; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/163318: commit references a PR Date: Fri, 2 Mar 2012 03:12:06 +0000 (UTC) Author: adrian Date: Fri Mar 2 03:11:53 2012 New Revision: 232375 URL: http://svn.freebsd.org/changeset/base/232375 Log: Wrap another ATH_LOCK around the scanning flag. PR: kern/163318 Modified: head/sys/dev/ath/if_ath.c Modified: head/sys/dev/ath/if_ath.c ============================================================================== --- head/sys/dev/ath/if_ath.c Fri Mar 2 02:57:10 2012 (r232374) +++ head/sys/dev/ath/if_ath.c Fri Mar 2 03:11:53 2012 (r232375) @@ -5690,8 +5690,10 @@ ath_set_channel(struct ieee80211com *ic) * beacon timers. Note that since we only hear beacons in * sta/ibss mode this has no effect in other operating modes. */ + ATH_LOCK(sc); if (!sc->sc_scanning && ic->ic_curchan == ic->ic_bsschan) sc->sc_syncbeacon = 1; + ATH_UNLOCK(sc); } /* _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Fri Mar 2 22:46:42 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B832F1065670 for ; Fri, 2 Mar 2012 22:46:42 +0000 (UTC) (envelope-from moonlightakkiy@yahoo.ca) Received: from nm9.bullet.mail.ne1.yahoo.com (nm9.bullet.mail.ne1.yahoo.com [98.138.90.72]) by mx1.freebsd.org (Postfix) with SMTP id 6F3DE8FC13 for ; Fri, 2 Mar 2012 22:46:42 +0000 (UTC) Received: from [98.138.90.55] by nm9.bullet.mail.ne1.yahoo.com with NNFMP; 02 Mar 2012 22:33:34 -0000 Received: from [98.138.226.130] by tm8.bullet.mail.ne1.yahoo.com with NNFMP; 02 Mar 2012 22:33:34 -0000 Received: from [127.0.0.1] by smtp217.mail.ne1.yahoo.com with NNFMP; 02 Mar 2012 22:33:34 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s1024; t=1330727614; bh=VcXDy3eE+AHxGH1pky3hy7vXiX1Ng1x7WNQxx43ufvk=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Received:MIME-Version:Received:Received:Date:Message-ID:Subject:From:To:Cc:Content-Type:Content-Transfer-Encoding; b=N61VbHx5ZcEbNXRYCG3FhbB8Cj0VZEc8S7DT7hzarvv/e8d5Ygd+TXqyUv35aAjUFs6J7H6fXoskhuwDQuD2vOjmYxuRRpmTTWOzedEtVyU42jIWXoQaJcIZVh8PjRlg1AQLHIcQ/fET2rcZV+nmkzn/3Hci0xRw3Jaz8XOV2qQ= X-Yahoo-Newman-Id: 501275.58842.bm@smtp217.mail.ne1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: e.4T7zEVM1nBhR88G_sbI0dYVrHlVLDTE_xYV7CncZaAAG9 p6p0R6JKLXCswkPO7a57tNT9v3QZxLeybx6Lf8nV4P.2KIl2K1ufRkOfViCI Pfb3S__fcvng7iiolBu_9WRr80HoK9HsQyg_YzrtYWFZqguW7GEuEHL0qd0D ntHFwSJvUrhiXm8mwmXsSrjsquu0ClewA0UaNo7Y5Jw0VOtxbT5RaHX4VGnm qrl_6973DGLX8UGW0L.xcRWustj.FRGPuqVZZP6ko.LahgRNCxmcIbYJqj4n huw6TkJ3Oe_aaKZDjEQYGxxCdhAVU.lly.1cYRnKJ7VAYx2pqglW7h_RbL8Z dh3Z3lseKAkt6XtxJVxqtD1lemzUfXUaZ0rpYNOmaZ8bD0HqpVmSb5aL9t2C gXhci77U.cKhpc0UPhbI1269WU_idhb.XGkYj30eRusTK7WQhj0s5Hc4vGcI 6GjkFyqGi8cYpdCHeBY46GqCUpP5ra4AcGKu4Qf2zUbNz0i0TsdKkQ61_agA zApgkWPCnE0vSBP7N X-Yahoo-SMTP: Xr6qjFWswBAEmd20sAvB4Q3keqXvXsIH9TjJ Received: from mail-iy0-f182.google.com (moonlightakkiy@209.85.210.182 with plain) by smtp217.mail.ne1.yahoo.com with SMTP; 02 Mar 2012 14:33:34 -0800 PST Received: by iahk25 with SMTP id k25so3769711iah.13 for ; Fri, 02 Mar 2012 14:33:34 -0800 (PST) MIME-Version: 1.0 Received: by 10.50.77.168 with SMTP id t8mr113826igw.32.1330727614095; Fri, 02 Mar 2012 14:33:34 -0800 (PST) Received: by 10.231.108.133 with HTTP; Fri, 2 Mar 2012 14:33:33 -0800 (PST) Date: Fri, 2 Mar 2012 15:33:33 -0700 Message-ID: From: PseudoCylon To: Adrian Chadd , Damjan Marion Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: run(4) in AP mode and battery consumption of mobile devices X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Fri, 02 Mar 2012 22:46:42 -0000 > > Message: 6 > Date: Thu, 1 Mar 2012 12:59:43 -0800 > From: Adrian Chadd > Subject: Re: run(4) in AP mode and battery consumption of mobile > =A0 =A0 =A0 =A0devices > To: Damjan Marion > Cc: freebsd-wireless@freebsd.org > Message-ID: > =A0 =A0 =A0 =A0 > Content-Type: text/plain; charset=3DISO-8859-1 > > Hi, > > I'd get in dirty with an ath nic in monitor mode. See what's going on. > > I'd look at what the TIM bits are set in the access point beacon > frames. Maybe it's doing something weird like waways setting them. Yep, it does, and it is on todo list. http://fxr.watson.org/fxr/source/dev/usb/wlan/if_run.c#L3943 AK From owner-freebsd-wireless@FreeBSD.ORG Fri Mar 2 23:00:28 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 40B6A1065676 for ; Fri, 2 Mar 2012 23:00:28 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id B7D958FC0C for ; Fri, 2 Mar 2012 23:00:27 +0000 (UTC) Received: by wgbds12 with SMTP id ds12so1884448wgb.31 for ; Fri, 02 Mar 2012 15:00:26 -0800 (PST) Received-SPF: pass (google.com: domain of adrian.chadd@gmail.com designates 10.216.134.74 as permitted sender) client-ip=10.216.134.74; Authentication-Results: mr.google.com; spf=pass (google.com: domain of adrian.chadd@gmail.com designates 10.216.134.74 as permitted sender) smtp.mail=adrian.chadd@gmail.com; dkim=pass header.i=adrian.chadd@gmail.com Received: from mr.google.com ([10.216.134.74]) by 10.216.134.74 with SMTP id r52mr2286309wei.19.1330729226931 (num_hops = 1); Fri, 02 Mar 2012 15:00:26 -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 :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=9E1UpTeaKWkqiXdvX6PyRCxXRbaa6TbTWcc0BgkZ8/o=; b=nsW3J4bqwS/RPNjcHQaL5zaUasVkqpQlKkTIG/dYHntX7eX3CBCGNytORYPcgUv0dO tK6uVTdKxe65u/pOm/bAj3J/jlSmWNDyIF56s3xKSQR5gW3cJQylVdyhpgKXasYeXKVQ VReHV7iCXca5+OQ7RAkOR/bAPutDgjsYsv/qE+WTR8+q2L1zZVxemeffxxAOxsHPo0Kt cePsgLMqmXI4HGSTTvg+iIybvqn7I5+UVhqE1phG5CEC5pEnQam3Hng5o5N/WpkgO6wE cXTv/978uTeohJo48lD3Gi71PbmkcGmvg8JWGJgGJvxJEeHzW3XYw4VnOIXhtOlsNvPT a3sg== MIME-Version: 1.0 Received: by 10.216.134.74 with SMTP id r52mr1829782wei.19.1330729225351; Fri, 02 Mar 2012 15:00:25 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.198.81 with HTTP; Fri, 2 Mar 2012 15:00:25 -0800 (PST) In-Reply-To: References: Date: Fri, 2 Mar 2012 15:00:25 -0800 X-Google-Sender-Auth: QazHVAjfBYYSJTX9V6j22IsUvUs Message-ID: From: Adrian Chadd To: PseudoCylon Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: run(4) in AP mode and battery consumption of mobile devices X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Fri, 02 Mar 2012 23:00:28 -0000 Ok, can we please have this added to the PR, so we don't lose track of it? Thanks so much for popping up and pointing that out! Adrian On 2 March 2012 14:33, PseudoCylon wrote: >> >> Message: 6 >> Date: Thu, 1 Mar 2012 12:59:43 -0800 >> From: Adrian Chadd >> Subject: Re: run(4) in AP mode and battery consumption of mobile >> =A0 =A0 =A0 =A0devices >> To: Damjan Marion >> Cc: freebsd-wireless@freebsd.org >> Message-ID: >> =A0 =A0 =A0 =A0 >> Content-Type: text/plain; charset=3DISO-8859-1 >> >> Hi, >> >> I'd get in dirty with an ath nic in monitor mode. See what's going on. >> >> I'd look at what the TIM bits are set in the access point beacon >> frames. Maybe it's doing something weird like waways setting them. > > Yep, it does, and it is on todo list. > http://fxr.watson.org/fxr/source/dev/usb/wlan/if_run.c#L3943 > > AK From owner-freebsd-wireless@FreeBSD.ORG Sat Mar 3 00:47:53 2012 Return-Path: Delivered-To: wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8997D106566B; Sat, 3 Mar 2012 00:47:53 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id DD2668FC0A; Sat, 3 Mar 2012 00:47:52 +0000 (UTC) Received: by wgbds12 with SMTP id ds12so1925498wgb.31 for ; Fri, 02 Mar 2012 16:47:51 -0800 (PST) Received-SPF: pass (google.com: domain of adrian.chadd@gmail.com designates 10.216.134.74 as permitted sender) client-ip=10.216.134.74; Authentication-Results: mr.google.com; spf=pass (google.com: domain of adrian.chadd@gmail.com designates 10.216.134.74 as permitted sender) smtp.mail=adrian.chadd@gmail.com; dkim=pass header.i=adrian.chadd@gmail.com Received: from mr.google.com ([10.216.134.74]) by 10.216.134.74 with SMTP id r52mr2404071wei.19.1330735671904 (num_hops = 1); Fri, 02 Mar 2012 16:47: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 :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=MrdogIgZX0tWLmo9+PIFeV4bD9NsHHuRax4hv1lFz6w=; b=GZ7rmrEYu2+CXGnUbYoHU9NAMPoAngDVHy7Ng/UqTToJscnis64w8tpLAsXs5MO00V JTjrFyPoeUf+wdcVQhRfCxcaDwsSBXH0RAYR6OMVT4TCIQWuVYS7E8XqK3uekdcSEoNC 7o6ONnwDmBV66qitza/HjNtsJlRrutlxr0lMe4mvIhiZGm83DIBnyNOk/qvTgt3daSF9 QCA9e0VOjBfjZxlmMKhlmMrA4encB+wdBs9ut6evcgutMwYUraGfiF/Q1gwlXXo/XQWo /fdNZ0cdd7PfWEKLdeirPL/aSBPd0MKzlnMT4v9fv2iCNgho1UR+7Uq2uBA0/mp0qmdF Chkw== MIME-Version: 1.0 Received: by 10.216.134.74 with SMTP id r52mr1921201wei.19.1330735671736; Fri, 02 Mar 2012 16:47:51 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.198.81 with HTTP; Fri, 2 Mar 2012 16:47:51 -0800 (PST) In-Reply-To: References: Date: Fri, 2 Mar 2012 16:47:51 -0800 X-Google-Sender-Auth: Dlh8FSVD7MWHV99tlAuY0dbDR10 Message-ID: From: Adrian Chadd To: Jakob Pedersen Content-Type: text/plain; charset=ISO-8859-1 Cc: mobile@freebsd.org, wireless@freebsd.org Subject: Re: Problems with RaLink rt61pci/rt2561 wifi card X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Sat, 03 Mar 2012 00:47:53 -0000 Hi, On 25 February 2012 05:45, Jakob Pedersen wrote: > Hi Adrian, > > Thank you for the tips for diagnosing my WiFi issue. It seems to be the > gain settings on the wifi card somehow (I am in not much of a technical > person, but at least that's what it seems to me). For PC-BSD the signal > strength is measured to -54 dB just next to the router and when stepping > away like 5 - 6 metres the signal is lost at -95 dB (Same level as noise dB > level). The decrease in not sudden but drops gradually when distance to > router is being increased. I am dual booting Arch linux on the same laptop, > where WiFi works fine and it measures - 20 dBm next to the router and - 70 > dBm where PC-BSD looses connection. Not really sure, what to do from here > though.. Right. Well, you've got a starting point. Maybe go through the driver looking for things to do with RX gain, RX calibration, etc. Then look at the linux driver and see if there are any obvious differences. I know, I'm asking you to do code debugging, but I'm just not able to help you out at the moment I'm sorry! Adrian