From owner-freebsd-wireless@FreeBSD.ORG Sun Dec 22 02:33:36 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 117EC72; Sun, 22 Dec 2013 02:33:36 +0000 (UTC) Received: from mail0.glenbarber.us (mail0.glenbarber.us [IPv6:2607:fc50:1:2300:1001:1001:1001:face]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D821C1572; Sun, 22 Dec 2013 02:33:35 +0000 (UTC) Received: from glenbarber.us (70.15.88.86.res-cmts.sewb.ptd.net [70.15.88.86]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id 59F6925F49; Sun, 22 Dec 2013 02:33:34 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us 59F6925F49 Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Sat, 21 Dec 2013 21:33:31 -0500 From: Glen Barber To: Adrian Chadd Subject: Re: "disappearing" ath(4) Message-ID: <20131222023331.GJ1730@glenbarber.us> References: <20131221023558.GJ3148@glenbarber.us> <20131221023924.GK3148@glenbarber.us> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="2fjX3cMESU3XgGmZ" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.0-CURRENT amd64 User-Agent: Mutt/1.5.22 (2013-10-16) Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Dec 2013 02:33:36 -0000 --2fjX3cMESU3XgGmZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Dec 21, 2013 at 08:17:32AM -0800, Adrian Chadd wrote: > The second possibility is that it's asleep - and no, NIC reads aren't > showing 0xdeadc0de, 0xdeadbeef, etc. So no, it's not that. >=20 I didn't think of this when you first mentioned it, but I recently added this to rc.conf: performance_cx_lowest=3D"C2" economy_cx_lowest=3D"C2" Another thing I failed to mention, is the ath(4) is part of lagg(4), accompanied by alc(4). I'm half wondering if the *_cx_lowest is triggering something. The other half wonders if lagg(4) triggers something funky. > He's also recently opened up his laptop and fiddled around. >=20 "Trust me, I'm an engineer!" > he's going off to do some more testing. >=20 "What can possibly go wrong?" Glen --2fjX3cMESU3XgGmZ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCAAGBQJStk97AAoJELls3eqvi17QVGwP/jo7yEH85pc/ioKl3RnYn/7B tHTOtWI4dhscT7yJmxNYiFuYQ8eZ6Tvw8itVvdTdNUTBrXRBVS0N6MFyByK7s2C0 KlJn/QwqrAb/5Rv1wrca4R+EllEjYy3xSYMIMVHoQMDR/GOXXfnJ5s+F+BfTYur6 brVRR+qp1YCyWj8mELUAJFkPcAjwkW0qhhwf6YWG9eNOnWSUWdeeidVUABucPjZV nutAYuPNXf3wAgVD9tLFdQ2pUpbMl8iY/Ir/Ffq8oGmghmKc8d9vOxP1UcFluokB y5Qo3kkBxn5Cur0xb2DVgY8awTkyi4pZR2CvCywLI4c80yDtDkSROjDtfhePOM09 fAJcx0Wu1blGjNM9iNgv3n2EWX7AVHoJXT6X5ykZgJnI8GjyQkz0PSHIHLX84UvI renRX9xphQKyhxivgOXx3cTQ4EsXxdgqGBgT9AeSCyeEH9uyE1GerqQwWexvU9ab BkHk3dluXb6bWEMn+6Z2NjV5xu5b55UXvP6l9yAB3e2As7i2htOn02YxuzM70Ie/ Jhysy2COp+OzO3RexVIUN2ascxuV5gqyF22HpbzHQEbBB6ylzVJj1JM4rhPn8KgO 5OKqmu2B7mCm29wY4XL5XKg+Fva/oJzec/P2Vhn65o0/fgYIw1wFCtGT2fNEQhDE /F0ERFEXeM163ADDMO53 =1uXj -----END PGP SIGNATURE----- --2fjX3cMESU3XgGmZ-- From owner-freebsd-wireless@FreeBSD.ORG Sun Dec 22 02:44:18 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 37632218; Sun, 22 Dec 2013 02:44:18 +0000 (UTC) Received: from mail-qe0-x22c.google.com (mail-qe0-x22c.google.com [IPv6:2607:f8b0:400d:c02::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D601815E9; Sun, 22 Dec 2013 02:44:17 +0000 (UTC) Received: by mail-qe0-f44.google.com with SMTP id nd7so3941240qeb.17 for ; Sat, 21 Dec 2013 18:44:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=3gSKNgq1lQZV+b+rNAhkUTtZx37wPJp8eq5qcfhKeJU=; b=qQWfFeGUeBKXO4r7eapUpPAGVYuXGEwD7nsJkm5bHe3DTMTO8Lx6VYPI3QsUr9FWm7 Le4v+DSsZxYLdRFcl6gzBDXjaG+fP7OlvVuiLcftpjNFmRyRVdeFw4yZQmJbPrCp6fmZ ih7cIIjim2Ap9+G44ugkFX+Bk9M1PS8wuH5If6KvugIOA84+QQnNXuKENPvbbGavGKJi aI3rCM/ETNe3v3rE9mtNmOo2aZw00C0HdATYEa1QSRoqQMtuNb6qQZMOfoMhXbEosNxR h7lgzU3E1YBvPweF8QImhj7eOB6PE0cf+jRNdKl3d09bEi6rTM33Nje2E33Ob6ghVtsp 1Eng== MIME-Version: 1.0 X-Received: by 10.224.46.8 with SMTP id h8mr29355647qaf.49.1387680257067; Sat, 21 Dec 2013 18:44:17 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.53.200 with HTTP; Sat, 21 Dec 2013 18:44:16 -0800 (PST) Received: by 10.224.53.200 with HTTP; Sat, 21 Dec 2013 18:44:16 -0800 (PST) In-Reply-To: <20131222023331.GJ1730@glenbarber.us> References: <20131221023558.GJ3148@glenbarber.us> <20131221023924.GK3148@glenbarber.us> <20131222023331.GJ1730@glenbarber.us> Date: Sat, 21 Dec 2013 18:44:16 -0800 X-Google-Sender-Auth: IaP5U114rW6iIH2feyColuuYz8w Message-ID: Subject: Re: "disappearing" ath(4) From: Adrian Chadd To: Glen Barber Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Dec 2013 02:44:18 -0000 Yeah. Try killing those. Leave it at c1 and no lagg. C2 and later may be triggering some weird stuff. Adrian On Dec 21, 2013 8:33 PM, "Glen Barber" wrote: > On Sat, Dec 21, 2013 at 08:17:32AM -0800, Adrian Chadd wrote: > > The second possibility is that it's asleep - and no, NIC reads aren't > > showing 0xdeadc0de, 0xdeadbeef, etc. So no, it's not that. > > > > I didn't think of this when you first mentioned it, but I recently added > this to rc.conf: > > performance_cx_lowest="C2" > economy_cx_lowest="C2" > > Another thing I failed to mention, is the ath(4) is part of lagg(4), > accompanied by alc(4). > > I'm half wondering if the *_cx_lowest is triggering something. The > other half wonders if lagg(4) triggers something funky. > > > He's also recently opened up his laptop and fiddled around. > > > > "Trust me, I'm an engineer!" > > > he's going off to do some more testing. > > > > "What can possibly go wrong?" > > Glen > > From owner-freebsd-wireless@FreeBSD.ORG Sun Dec 22 02:49:09 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D077D35C; Sun, 22 Dec 2013 02:49:09 +0000 (UTC) Received: from mail0.glenbarber.us (mail0.glenbarber.us [208.86.227.67]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A19611604; Sun, 22 Dec 2013 02:49:09 +0000 (UTC) Received: from glenbarber.us (70.15.88.86.res-cmts.sewb.ptd.net [70.15.88.86]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id 620A825074; Sun, 22 Dec 2013 02:49:07 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us 620A825074 Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Sat, 21 Dec 2013 21:49:05 -0500 From: Glen Barber To: Adrian Chadd Subject: Re: "disappearing" ath(4) Message-ID: <20131222024905.GK1730@glenbarber.us> References: <20131221023558.GJ3148@glenbarber.us> <20131221023924.GK3148@glenbarber.us> <20131222023331.GJ1730@glenbarber.us> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="F55Y67F01HNW3AgB" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.0-CURRENT amd64 User-Agent: Mutt/1.5.22 (2013-10-16) Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Dec 2013 02:49:10 -0000 --F55Y67F01HNW3AgB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I doubt lagg(4) is the issue. I've been doing that evil for years. I'll kill the *_cs_lowest, and see if that changes anything over the next few days. I'm 200% certain lagg(4) is not a factor, but if it continues, I'll disable that for S&G. Glen On Sat, Dec 21, 2013 at 06:44:16PM -0800, Adrian Chadd wrote: > Yeah. Try killing those. Leave it at c1 and no lagg. C2 and later may be > triggering some weird stuff. >=20 > Adrian > On Dec 21, 2013 8:33 PM, "Glen Barber" wrote: >=20 > > On Sat, Dec 21, 2013 at 08:17:32AM -0800, Adrian Chadd wrote: > > > The second possibility is that it's asleep - and no, NIC reads aren't > > > showing 0xdeadc0de, 0xdeadbeef, etc. So no, it's not that. > > > > > > > I didn't think of this when you first mentioned it, but I recently added > > this to rc.conf: > > > > performance_cx_lowest=3D"C2" > > economy_cx_lowest=3D"C2" > > > > Another thing I failed to mention, is the ath(4) is part of lagg(4), > > accompanied by alc(4). > > > > I'm half wondering if the *_cx_lowest is triggering something. The > > other half wonders if lagg(4) triggers something funky. > > > > > He's also recently opened up his laptop and fiddled around. > > > > > > > "Trust me, I'm an engineer!" > > > > > he's going off to do some more testing. > > > > > > > "What can possibly go wrong?" > > > > Glen > > > > --F55Y67F01HNW3AgB Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCAAGBQJStlMhAAoJELls3eqvi17Qb5gQAIbTlopwVRUy0GH9OU81aWY8 H4FMwKfl2f1CL8VUC8aJqZ4H/UmUG+zwzB5rl0x22RFQGw8hfKEgHgeIsKErRIQO OPyqR9M4ajKw5JGiPfV8w5mTCeRJ9QYE0+GI+7lX0+YuLIq3W4rOTzGLG355WE+E tjOSmEpKXKjlSf5RLsfsx9cChwhTQt1y0uRRqYHNyZt173CdwLRg9TSI6IPMITnN BBUnvs8yDgb55f3/jR+62ktnVC4jcKCarIRvuKYT77eYS09jGfGPS6LTzGSSkbjv zpSjAgojD9faJRdTQIFaDHj1seQpqXgS+4YoWIx+vNmL2ifOIXSZHcUtHEwIWI4U n9PCQUy6vajuCVeM98sVNX4RfVe6u/f+RiBw5ba0XRoCMxWqqeiVxwvSMqNVpZUN 287/1pROs2IqQHaD4IWyEBdPqIgen6YjMYRVLGUjPq1V8FNcSYvqJ5JO6qo8elDz xRcCj7ktreAkGVpo0jvd6RJsjTMKyw+4GDWYDzNjI2rfMHqeNmMxz1sS1OYiqBoS uQbWf/oCD9fDXUt0AS2kP92yp00+l5D/eWxK6urh24sQqn7FUhipkMuttEbVE7ky Q191fauGtZpZXpZyQoxwJ3LpuquE/9TQBHYXYB2uG7op4v0tviTKds+KX4RgIXAA GlK9gfWfir0i1dIAOTbM =+EVo -----END PGP SIGNATURE----- --F55Y67F01HNW3AgB-- From owner-freebsd-wireless@FreeBSD.ORG Sun Dec 22 02:52:40 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0F3FF3B3; Sun, 22 Dec 2013 02:52:40 +0000 (UTC) Received: from mail-qe0-x22d.google.com (mail-qe0-x22d.google.com [IPv6:2607:f8b0:400d:c02::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id ACD6E1657; Sun, 22 Dec 2013 02:52:39 +0000 (UTC) Received: by mail-qe0-f45.google.com with SMTP id 6so3903334qea.4 for ; Sat, 21 Dec 2013 18:52:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=QRSlqYhtuKEnbA9/y0xtTZueLo2GBl467jBjowzrmFU=; b=FIIQzWTaAbrQ/W+2/bA4k1vXjmnV0YqX+73zJAb7RZtheVtJf2122i99YAA4h1oNGc jWY6G6tC9z/182rfCB36VhdcGM0/zD3mqBl5vHLrbqUG2veKK19TEb92TtEAKMSCfcVE tPwth4B4M3IGtYnrrZystT1l1uEmlp+WAvTtUFjgCLpYUlEJURuY+xpgPCgXOQfUEPH6 GMy2pCLdVISAJWwEErH4VYgcERyCc2j7Y/08v3v1GIq7qswaBIQDGyISB0zKRw+FygtT Zx2cu2kmqN/fHdjLghiaE6Cep5T8y6SQyZNSt053lI5uInsxUTQHg8x/OEEchmnUVCTc YVPQ== MIME-Version: 1.0 X-Received: by 10.224.13.141 with SMTP id c13mr21672891qaa.76.1387680758375; Sat, 21 Dec 2013 18:52:38 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.53.200 with HTTP; Sat, 21 Dec 2013 18:52:38 -0800 (PST) Received: by 10.224.53.200 with HTTP; Sat, 21 Dec 2013 18:52:38 -0800 (PST) In-Reply-To: <20131222024905.GK1730@glenbarber.us> References: <20131221023558.GJ3148@glenbarber.us> <20131221023924.GK3148@glenbarber.us> <20131222023331.GJ1730@glenbarber.us> <20131222024905.GK1730@glenbarber.us> Date: Sat, 21 Dec 2013 18:52:38 -0800 X-Google-Sender-Auth: 134tyb4i3sVY9zr_iRfSmgMmg5E Message-ID: Subject: Re: "disappearing" ath(4) From: Adrian Chadd To: Glen Barber Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Dec 2013 02:52:40 -0000 Okay. Lemme know if it does. Also I hope we aren't enabling aspm yet. Argh. Adrian On Dec 21, 2013 8:49 PM, "Glen Barber" wrote: > I doubt lagg(4) is the issue. I've been doing that evil for years. > > I'll kill the *_cs_lowest, and see if that changes anything over the > next few days. > > I'm 200% certain lagg(4) is not a factor, but if it continues, I'll > disable that for S&G. > > Glen > > On Sat, Dec 21, 2013 at 06:44:16PM -0800, Adrian Chadd wrote: > > Yeah. Try killing those. Leave it at c1 and no lagg. C2 and later may be > > triggering some weird stuff. > > > > Adrian > > On Dec 21, 2013 8:33 PM, "Glen Barber" wrote: > > > > > On Sat, Dec 21, 2013 at 08:17:32AM -0800, Adrian Chadd wrote: > > > > The second possibility is that it's asleep - and no, NIC reads aren't > > > > showing 0xdeadc0de, 0xdeadbeef, etc. So no, it's not that. > > > > > > > > > > I didn't think of this when you first mentioned it, but I recently > added > > > this to rc.conf: > > > > > > performance_cx_lowest="C2" > > > economy_cx_lowest="C2" > > > > > > Another thing I failed to mention, is the ath(4) is part of lagg(4), > > > accompanied by alc(4). > > > > > > I'm half wondering if the *_cx_lowest is triggering something. The > > > other half wonders if lagg(4) triggers something funky. > > > > > > > He's also recently opened up his laptop and fiddled around. > > > > > > > > > > "Trust me, I'm an engineer!" > > > > > > > he's going off to do some more testing. > > > > > > > > > > "What can possibly go wrong?" > > > > > > Glen > > > > > > > From owner-freebsd-wireless@FreeBSD.ORG Mon Dec 23 03:15:48 2013 Return-Path: Delivered-To: wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 87586C5E; Mon, 23 Dec 2013 03:15:48 +0000 (UTC) Received: from felyko.com (felyko.com [174.136.100.2]) by mx1.freebsd.org (Postfix) with ESMTP id 68D451132; Mon, 23 Dec 2013 03:15:48 +0000 (UTC) Received: from [10.0.1.3] (c-24-6-16-155.hsd1.ca.comcast.net [24.6.16.155]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by felyko.com (Postfix) with ESMTPSA id 501423983B; Sun, 22 Dec 2013 19:15:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=felyko.com; s=mail; t=1387768542; bh=4N+0pBhkF8A5ajQCIfTG7QyENQTUDLQ0GS1xCjGWgMU=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=MyNBhI32cuY3Q4dOqvkI2vQOaf12PE+EsdCCHLzj0/8nGMpgXpziBquWFYZkYcjMv j364MrA2C11sLhJjAMNHFNtM3GUOB/E9Xxw9SUq+uLa9hA50dYSWopktgHetyuxhtv ggGZcg6AKi5iNNodFt8BJ0PVeZO0F7B0diALA82w= Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) Subject: Re: ral(4) panic. head, r257837 From: Rui Paulo In-Reply-To: Date: Sun, 22 Dec 2013 19:15:50 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <906BAA48-3702-464C-A079-ABBD09600405@felyko.com> References: <20131219100438.117a3576@laptop.minsk.domain> <20131219110746.51c90249@laptop.minsk.domain> To: Adrian Chadd X-Mailer: Apple Mail (2.1827) Cc: "current@freebsd.org Current" , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Dec 2013 03:15:48 -0000 "ni" is NULL, so it's probably line 1475. On 19 Dec 2013, at 16:02, Adrian Chadd wrote: > Well there's a null node pointer. Need to figure out why. Its totally = legit > to have them too, so the code has to cope. >=20 > Grr. >=20 > Adrian > On Dec 19, 2013 2:07 AM, "Sergey V. Dyatko" = wrote: >=20 >> On Wed, 18 Dec 2013 23:40:23 -0800 >> Adrian Chadd wrote: >>=20 >>> What's at frame 10? >>>=20 >>> And list the IP, ie: >>>=20 >>> list *0xffffffff817da911 >>>=20 >>=20 >> (kgdb) f 10 >> #10 0xffffffff817da911 in rt2860_tx (sc=3D0xfffffe00009bd000, >> m=3D0xfffff80004c6dd00, ni=3D0x0) >> at /usr/src/sys/modules/ral/../../dev/ral/rt2860.c:1472 1472 { >> Current language: auto; currently minimal >>=20 >> (kgdb) list *0xffffffff817da911 >> 0xffffffff817da911 is in rt2860_tx >> (/usr/src/sys/modules/ral/../../dev/ral/rt2860.c:1475). 1470 = static >> int 1471 rt2860_tx(struct rt2860_softc *sc, struct mbuf *m, struct >> ieee80211_node *ni) 1472 { >> 1473 struct ifnet *ifp =3D sc->sc_ifp; >> 1474 struct ieee80211com *ic =3D ifp->if_l2com; >> 1475 struct ieee80211vap *vap =3D ni->ni_vap; >> 1476 struct rt2860_tx_ring *ring; >> 1477 struct rt2860_tx_data *data; >> 1478 struct rt2860_txd *txd; >> 1479 struct rt2860_txwi *txwi; >>=20 >>> -a >>>=20 >>> On 18 December 2013 23:04, Sergey V. Dyatko = >>> wrote: >>>> Hi, >>>>=20 >>>> I have following setup: >>>>=20 >>>> wlans_ral0=3D"wlan0" >>>> ifconfig_wlan0=3D"WPA" >>>>=20 >>>> cloned_interfaces=3D"lagg0 bridge0 tap0" >>>> ifconfig_lagg0=3D"laggproto failover laggport alc0 laggport wlan0 >>>> DHCP" ifconfig_bridge0=3D"addm tap0 addm lagg0" >>>>=20 >>>> When system boot I have reproducible panic after messages >>>> Waiting 30s for the default route interface: . >>>> ral0: need multicast update callback >>>> ral0: need multicast update callback >>>> ........ : >>>>=20 >>>> Fatal trap 12: page fault while in kernel mode >>>> cpuid =3D 0; apic id =3D 00 >>>> fault virtual address =3D 0x0 >>>> fault code =3D supervisor read data, page not present >>>> instruction pointer =3D 0x20:0xffffffff817da911 >>>> stack pointer =3D 0x28:0xfffffe011fe61da0 >>>> frame pointer =3D 0x28:0xfffffe011fe62630 >>>> <118>. >>>> code segment =3D base 0x0, limit 0xfffff, type 0x1b >>>> =3D DPL 0, pres 1, long 1, def32 0, gran 1 >>>> processor eflags =3D interrupt enabled, resume, IOPL =3D 0 >>>> current process =3D 1815 (dhclient) >>>>=20 >>>> Reading symbols from /boot/kernel/zfs.ko.symbols...done. >>>> Loaded symbols for /boot/kernel/zfs.ko.symbols >>>> Reading symbols from /boot/kernel/opensolaris.ko.symbols...done. >>>> Loaded symbols for /boot/kernel/opensolaris.ko.symbols >>>> Reading symbols from /boot/kernel/linux.ko.symbols...done. >>>> Loaded symbols for /boot/kernel/linux.ko.symbols >>>> Reading symbols from /boot/kernel/if_alc.ko.symbols...done. >>>> Loaded symbols for /boot/kernel/if_alc.ko.symbols >>>> Reading symbols from /boot/kernel/if_ral.ko.symbols...done. >>>> Loaded symbols for /boot/kernel/if_ral.ko.symbols >>>> Reading symbols from /boot/kernel/snd_hda.ko.symbols...done. >>>> Loaded symbols for /boot/kernel/snd_hda.ko.symbols >>>> Reading symbols from /boot/kernel/sound.ko.symbols...done. >>>> Loaded symbols for /boot/kernel/sound.ko.symbols >>>> Reading symbols from /boot/kernel/acpi_video.ko.symbols...done. >>>> Loaded symbols for /boot/kernel/acpi_video.ko.symbols >>>> Reading symbols from /boot/modules/nvidia.ko...done. >>>> Loaded symbols for /boot/modules/nvidia.ko >>>> Reading symbols from /boot/modules/cuse4bsd.ko...done. >>>> Loaded symbols for /boot/modules/cuse4bsd.ko >>>> Reading symbols from /boot/kernel/sem.ko.symbols...done. >>>> Loaded symbols for /boot/kernel/sem.ko.symbols >>>> Reading symbols from /boot/kernel/linprocfs.ko.symbols...done. >>>> Loaded symbols for /boot/kernel/linprocfs.ko.symbols >>>> Reading symbols from /boot/kernel/if_lagg.ko.symbols...done. >>>> Loaded symbols for /boot/kernel/if_lagg.ko.symbols >>>> Reading symbols from /boot/kernel/if_bridge.ko.symbols...done. >>>> Loaded symbols for /boot/kernel/if_bridge.ko.symbols >>>> Reading symbols from /boot/kernel/bridgestp.ko.symbols...done. >>>> Loaded symbols for /boot/kernel/bridgestp.ko.symbols >>>> Reading symbols from /boot/kernel/if_tap.ko.symbols...done. >>>> Loaded symbols for /boot/kernel/if_tap.ko.symbols >>>>=20 >>>> #0 doadump (textdump=3D0) at pcpu.h:219 >>>> 219 pcpu.h: No such file or directory. >>>> in pcpu.h >>>> (kgdb) #0 doadump (textdump=3D0) at pcpu.h:219 >>>> #1 0xffffffff803023ae in db_dump (dummy=3D, >>>> dummy2=3D0, dummy3=3D0, dummy4=3D0x0) at = /usr/src/sys/ddb/db_command.c:543 >>>> #2 0xffffffff80301e8d in db_command (cmd_table=3D>>> out>) at /usr/src/sys/ddb/db_command.c:449 >>>> #3 0xffffffff80301c04 in db_command_loop () >>>> at /usr/src/sys/ddb/db_command.c:502 >>>> #4 0xffffffff80304570 in db_trap (type=3D, >>>> code=3D0) at /usr/src/sys/ddb/db_main.c:231 >>>> #5 0xffffffff8072e9d3 in kdb_trap (type=3D12, code=3D0, tf=3D>>> optimized out>) at /usr/src/sys/kern/subr_kdb.c:656 >>>> #6 0xffffffff80a81bb2 in trap_fatal (frame=3D0xfffffe011fe61cf0, >>>> eva=3D) >>>> at /usr/src/sys/amd64/amd64/trap.c:870 #7 0xffffffff80a81ec9 in >>>> trap_pfault (frame=3D0xfffffe011fe61cf0, usermode=3D0) >>>> at /usr/src/sys/amd64/amd64/trap.c:692 #8 0xffffffff80a8165b in >>>> trap (frame=3D0xfffffe011fe61cf0) >>>> at /usr/src/sys/amd64/amd64/trap.c:456 #9 0xffffffff80a68222 in >>>> calltrap () at /usr/src/sys/amd64/amd64/exception.S:232 >>>> #10 0xffffffff817da911 in rt2860_tx (sc=3D0xfffffe00009bd000, >>>> m=3D0xfffff80004c6dd00, ni=3D0x0) >>>> at /usr/src/sys/modules/ral/../../dev/ral/rt2860.c:1472 >>>> #11 0xffffffff817da89e in rt2860_start_locked >>>> (ifp=3D0xfffff80003bed800) >>>> at /usr/src/sys/modules/ral/../../dev/ral/rt2860.c:1998 #12 >>>> 0xffffffff817d57b0 in rt2860_start (ifp=3D0xfffff80003bed800) >>>> at /usr/src/sys/modules/ral/../../dev/ral/rt2860.c:1972 #13 >>>> 0xffffffff807b5f35 in if_transmit (ifp=3D, >>>> m=3D) at /usr/src/sys/net/if.c:3352 #14 >>>> 0xffffffff807fbd96 in ieee80211_vap_pkt_send_dest ( vap=3D>>> optimized out>, m=3D, ni=3D0xfffffe0003bae000) >>>> at /usr/src/sys/net80211/ieee80211_output.c:243 #15 >>>> 0xffffffff807fce09 in ieee80211_vap_transmit (ifp=3D>>> out>, m=3D) >>>> out>at /usr/src/sys/net80211/ieee80211_output.c:393 >>>> #16 0xffffffff8261d91f in lagg_transmit (ifp=3D0xfffff80003bec000, >>>> m=3D0xfffff80004c6dd00) >>>> at /usr/src/sys/modules/if_lagg/../../net/if_lagg.c:1314 >>>> #17 0xffffffff8262b11d in bridge_enqueue (sc=3D0xfffff80006597c00, >>>> dst_ifp=3D0xfffff80003bec000, m=3D) >>>> at /usr/src/sys/modules/if_bridge/../../net/if_bridge.c:1864 >>>> #18 0xffffffff8262a2e0 in bridge_output (ifp=3D0xfffff80003bec000, >>>> m=3D, sa=3D, rt=3D0x1) >>>> at /usr/src/sys/modules/if_bridge/../../net/if_bridge.c:2009 >>>> #19 0xffffffff807b8014 in ether_output (ifp=3D, >>>> m=3D0xfffff80004001200, dst=3D0xfffffe011fe62928, ro=3D>>> optimized >>>> out>) at /usr/src/sys/net/if_ethersubr.c:387 >>>> #20 0xffffffff807abe92 in bpfwrite (dev=3D, >>>> uio=3D0xfffff800064d9c00, ioflag=3D) >>>> at /usr/src/sys/net/bpf.c:1082 >>>> #21 0xffffffff805ecacf in devfs_write_f (fp=3D0xfffff800065f79b0, >>>> uio=3D0xfffff800064d9c00, cred=3D, flags=3D0,= >>>> td=3D0xfffff800062ea920) >>>> at /usr/src/sys/fs/devfs/devfs_vnops.c:1672 #22 0xffffffff8074594a >>>> in dofilewrite (td=3D0xfffff800062ea920, fd=3D6, = fp=3D0xfffff800065f79b0, >>>> auio=3D0xfffff800064d9c00, offset=3D, flags=3D0)= at >>>> file.h:303 #23 0xffffffff80745675 in kern_writev >>>> (td=3D0xfffff800062ea920, fd=3D6, auio=3D0xfffff800064d9c00) >>>> at /usr/src/sys/kern/sys_generic.c:467 #24 0xffffffff80745896 in >>>> sys_writev (td=3D0xfffff800062ea920, uap=3D0xfffffe011fe62b40) >>>> at /usr/src/sys/kern/sys_generic.c:452 #25 0xffffffff80a824e7 in >>>> amd64_syscall (td=3D0xfffff800062ea920, traced=3D0) at >>>> subr_syscall.c:134 #26 0xffffffff80a6850b in Xfast_syscall () >>>> at /usr/src/sys/amd64/amd64/exception.S:391 >>>> #27 0x0000000800b5cf3a in ?? () >>>> Previous frame inner to this frame (corrupt stack?) >>>> Current language: auto; currently minimal >>>> (kgdb) >>>>=20 >>>> at office, laggport alc0 is MASTER on lagg and all works fine. >>>>=20 >>>> I have vmcore file and I can enter the necessary commands if this >>>> will help >>>>=20 >>>>=20 >>>> -- >>>> wbr, tiger >>>> _______________________________________________ >>>> freebsd-current@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>>> To unsubscribe, send any mail to >>>> "freebsd-current-unsubscribe@freebsd.org" >>=20 >>=20 >>=20 >> -- >> wbr, tiger >>=20 > _______________________________________________ > 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" -- Rui Paulo From owner-freebsd-wireless@FreeBSD.ORG Mon Dec 23 04:45:20 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BE4E49B8 for ; Mon, 23 Dec 2013 04:45:20 +0000 (UTC) Received: from mail-qc0-x233.google.com (mail-qc0-x233.google.com [IPv6:2607:f8b0:400d:c01::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7AFFA1720 for ; Mon, 23 Dec 2013 04:45:20 +0000 (UTC) Received: by mail-qc0-f179.google.com with SMTP id i8so4399780qcq.38 for ; Sun, 22 Dec 2013 20:45:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:from:date:message-id:subject:to:content-type; bh=kVunOow5ptaWl+l13YdR6RDPuPqqNZSNw+rWduV18y0=; b=PzsuvSYTTUI6gDAIDptmg1mcRGpg2p3EWtCT0hPYeebBa67XoAzvpsi1tL1C3NrfZq m9b1Lli/+aM6NbSAgwDb0dCgiwB+lGmtj4V0whw9QBFRNBIhdskhQYPhs64dwHACREmf Uw24Z+/qFxA+xiWLyOiTe2I7GzsNGhMuxX2VU= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-type; bh=kVunOow5ptaWl+l13YdR6RDPuPqqNZSNw+rWduV18y0=; b=i6KMiluGV5eKJUN1/v0oJA9wwR1HEXSCimMnEuwEdqD7TV/Mq1cPWn3LZa7C7tfDRW V5a6tlZfyLz8tA90XmO5c3L0RG7hWPCnl47b3NI6hBaQuvmo/HhJOnjIF6+C6185d/Q1 +z7cfbNHLhaqlcexYcQUhZpPFxbmgWGqcs8y7Un+4Ut3mHefkn+CFCv8rMq8D85fd9LR D7GX59/yAlkHUNkvzxQbwouqamatGniqPXP4UnI/1oE1Mt0WOFCxLYWEuTL92fl6YmVm KmthXI2ZCbmPem9v2WPBBq3GVUsdu/fvrMrZgj/ifX8Si4HGJaCFeG0qiMuyg/G7b5GW Dz9A== X-Gm-Message-State: ALoCoQmdrBrzYChhFHHSlQt0JdKd5FHPkyAv/Ye7JJNpGXqv1PY/d6+K9m2K6PEKNqmw6KrarZoR X-Received: by 10.224.34.71 with SMTP id k7mr38186879qad.15.1387773919586; Sun, 22 Dec 2013 20:45:19 -0800 (PST) MIME-Version: 1.0 Received: by 10.96.30.194 with HTTP; Sun, 22 Dec 2013 20:44:49 -0800 (PST) From: Eitan Adler Date: Sun, 22 Dec 2013 23:44:49 -0500 Message-ID: Subject: iwn disconnect To: "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Dec 2013 04:45:20 -0000 Per Adrian's request - our IRC conversation: adrian_: I just had iwn randomly disconnect on me. I restarted wpa_supplicant and it blacklisted every network it knew about - including the one it was just connected too. When I did 'kldunload if_iwn && kldload iwn' it worked again also load: 0.08 cmd: ping 60362 [select] 151.25r 0.00u 0.01s 0% 1532k 107/150 packets received (71.3%) 66.844 min / 761.791 avg / 2770.682 max something seems ... odd <@adrian_> It happens <@adrian_> iwn needs a lot more inspection tools <@adrian_> did it log any reasons in dmesg when it was failing entirely? no, I checked just "state changed to DOWN" <@adrian_> right <@adrian_> blacklitsing only happens if it tries transmitting and/or authenticating and it fails <@adrian_> that's the kind of inspection that's required <@adrian_> i cna't help out more than that, sorry. Best ot email the list so I can braindump ideas when i have a moment -- Eitan Adler From owner-freebsd-wireless@FreeBSD.ORG Mon Dec 23 11:06:58 2013 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EBD90689 for ; Mon, 23 Dec 2013 11:06:57 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BD4BD11E2 for ; Mon, 23 Dec 2013 11:06:57 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id rBNB6vX8030200 for ; Mon, 23 Dec 2013 11:06:57 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id rBNB6vjt030198 for freebsd-wireless@FreeBSD.org; Mon, 23 Dec 2013 11:06:57 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 23 Dec 2013 11:06:57 GMT Message-Id: <201312231106.rBNB6vjt030198@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 Subject: Current problem reports assigned to freebsd-wireless@FreeBSD.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Dec 2013 11:06:58 -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/184762 wireless Wlan(Intel Centrino Wireless-N 1000) can't connect to o kern/184756 wireless [iwn] iwn(4) (5100 model) radio peridiocally gets disa o kern/184692 wireless [iwi] [panic] kernel panic in iwi0 driver o conf/184657 wireless freebsd 10 unable to connect hidden wifi o kern/184631 wireless [iwn] [patch] hook in iwn2000fw and iwn2030fw to kerne o kern/184626 wireless [wlan] wlan0 missing some ifmib(4) data o kern/183759 wireless [iwn] [wlan] Interface dies, OACTIVE set on wlan0 o kern/183727 wireless [wlan] ENOBUFFS incorrectly returned when tx packet is o kern/183644 wireless [ath] [patch] ath(4) "stops" working o kern/183430 wireless [iwn] latest change to the rate code setup uses 11n ra o kern/183428 wireless [net80211] [iwn] Some APs seem to announce HT but no H o kern/181898 wireless [iwn] [patch] Centrino Advanced-N 6235 with latest iwn o kern/181694 wireless [iwn] [patch] Initialize hardware in iwn(4) resume cod o kern/181161 wireless [wl] config a old compaq wl-110 wireless card make ker o kern/181132 wireless [iwn] stream calculation is wrong for the Intel 4965 o kern/181100 wireless [bwi] Turning up bwi0 crashes / deadlocks the kernel o kern/180816 wireless [iwl] Intel Centrino Wireless-N 2200 not supported o kern/179847 wireless [ath] [patch] Update regdomain in ath drivers includin o kern/179709 wireless [ath] Atheros 5212 does not work: stuck beacon; resett o kern/179547 wireless [ath] Add AR9485 custom board fixes (CUS198) o kern/179482 wireless [ath] [patch] Fix AR9462 external LNA configuration o kern/179269 wireless [ath] [AR9285] RX antenna diversity is not functioning o kern/179232 wireless [ath] panic in ath o kern/178986 wireless [ath] Change mac address of ath(4) is not reflected wh o kern/178492 wireless [ath] ath0 (AR9287) panic o kern/178491 wireless [ath] ath0 (AR9287) stuck beacon o kern/178477 wireless [ath] missed beacon / soft reset in STA mode results i o kern/178470 wireless [panic][ath] bss vap can and does change o kern/178411 wireless [ral] [panic] FreeBSD kernel crash in rt2860 o kern/178379 wireless [net80211] [ath] WPA rekey on the STA side fails when o kern/178378 wireless [net80211] crypto state isn't reset during a reassocia o kern/178263 wireless [ath] review the use of ic_freq / ic_ieee / ic_flags / o kern/177847 wireless [ath] With TPC enabled, TX power values aren't clamped o kern/177846 wireless [ath] [net80211] net80211 TX power limit isn't correct o conf/177688 wireless WiFi regodmains information is inconsistent between "e o kern/177530 wireless [ath] ath driver isn't 32 bit int clean o kern/177465 wireless [iwn] 20%-100% packet loss with iwn driver o kern/177451 wireless [ieee80211] page fault in ieee80211_tx_mgt_timeout o kern/176238 wireless [ath] [patch] Correct buffer size calculation and simp o kern/176201 wireless [net80211] [patch] 11n station includes unrelated ht p o kern/176104 wireless [iwn] iwn0: iwn_intr: fatal firmware error o kern/175722 wireless [ath]lot of bad seriesx hwrate in kernel messages o kern/175446 wireless [ath] high volumes of PHY errors lead to BB/MAC hangs o kern/175227 wireless [ath] beacon timers aren't necessarily reprogrammed af o kern/175183 wireless [iwn] iwn(4) becomes unresponsive during initial confi o kern/175053 wireless [iwn] iwn firmware error on 9-stable with Ultimate-N 6 o kern/174891 wireless [ieee80211] struct ieee80211_node is freed during acti o kern/174722 wireless [wlan] can't use channel 12 and 13 (14) with my wifi i o kern/174661 wireless [wlan] lost alias on wlan interface o kern/174283 wireless [net80211] panics in ieee80211_ff_age() and ieee80211_ o kern/174276 wireless [ath] if_ath memory modified after free o kern/174273 wireless [net80211] taking down a net80211 node with active fas o kern/173917 wireless [iwn] wpa-supplicant issues on iwn o kern/173898 wireless [iwn] [patch] iwn(4) DOES support 6235 chip. o kern/173883 wireless [ath] ath0: unable to attach - pci issue? o kern/173711 wireless [ath] powerd kills ath on the Asus EeePC 1005HA o kern/173342 wireless PS-Poll isn't working o kern/173336 wireless [ath] Atheros card improper device poweroff handling o o kern/172955 wireless [ath] 11n does not work in adhoc mode o kern/172706 wireless [wpi] wpi0 fails to load firmware when using country o kern/172672 wireless [ubt] Bluetooth device recognised but not working o kern/172661 wireless hostapd(8) securing wireless adapter in HostAP mode is o kern/172338 wireless [ath] [net80211] CCMP IV transmit counters are not cor o kern/171598 wireless [ath] TP-Link TL-WN951N W-LAN PCI Adapter 300 MBit stu o kern/171235 wireless [ath] ath loses connection, system freezes on netif re o kern/170889 wireless [ath] ath driver uses some uninitilized memory o kern/170620 wireless [ath] LOR and deadlock when multiple vaps are used o kern/170573 wireless [iwi] Intel 2200BG iwi NIC hangs with need multicast c o kern/170513 wireless [ath] ath logs: ath_tx_aggr_comp_aggr: AR5416 bug: o kern/170433 wireless [ath] TX hang after a stuck beacon message with active o kern/170411 wireless [ath] Uninitialized variables in if_ath.c o kern/170397 wireless [ath] [patch] Uninitialized variables in ah_eeprom_928 o kern/170302 wireless [ath] 802.11n frames are not being transmitted with mu o kern/170281 wireless [ath] 802.11n locks up on aggregation setup (ampdutx) o kern/170098 wireless [ath] [net80211] VAPs (Virtual access points) with Ath o kern/170066 wireless [ral] ral(4) rt61pci Linksys freezes the machine as so o kern/169432 wireless [ath] BAR TX hang when aggregation session is reset du p kern/169362 wireless [ath] AR5416: radar pulse PHY errors sometimes include o kern/169336 wireless [ath] ANI isn't triggering in a busy/noisy environment o kern/169199 wireless [ath] Cannot set up static ip addresses for wireless w o kern/169084 wireless [ath] suspend/resume doesn't cause a rescan; the assoc o kern/168530 wireless [ath] Broken WEP probably o kern/168393 wireless AR9285: suspend/resume sometimes fails o kern/168170 wireless [net80211] ieee80211_send_bar() doesn't complete corre o kern/167870 wireless [ath] adhoc wifi client does not join an existing IBSS o kern/167834 wireless [ath] kickpcu; 'handled 0 packets' o kern/167828 wireless [iwn] iwn(4) doesn't recover automatically after firmw o kern/167798 wireless ifconfig(8): problem with "ifconfig list scan" command o kern/167491 wireless [ath] TID != hardware queue TID in ath_tx_aggr_comp_ag o kern/167113 wireless [ath] AR5210: "stuck" TX seems to be occuring, without o kern/167080 wireless [ath] channel switch on another VAP break channel setu o kern/166684 wireless [ath] [net80211] mgmtrate/mcastrate isn't updated base p kern/166642 wireless [ieee80211] [patch] in 802.11n mode for FreeBSD AP, ha o kern/166641 wireless [ieee80211] [patch] mbuf/cluster leak in AP mode in 80 p kern/166357 wireless [ath] 802.11n TX stall when the first frame in the BAW o kern/166286 wireless [net80211] [ath] initial switch to HT40 isn't causing p kern/166190 wireless [ath] TX hangs and frames stuck in TX queue o kern/166086 wireless [Patch][ath] Reflect state of rfkill switch in a sysct o kern/165969 wireless [ath] Slower performance in adhoc mode vs Client/AP mo o kern/165966 wireless [ath] ath0: device timeout on SMP machines due to race o kern/165895 wireless [ath] overly busy cabq can tie up all tx buffers o kern/165870 wireless [bwn] bwn driver does not attach on HP Pavilion dv9420 o kern/165866 wireless [ath] TX hangs, requiring a "scan" to properly reset t o kern/165849 wireless [ath] [hang] network ath driver freeze o kern/165595 wireless [ipw] ipw(4): Can't load firmare for ipw2200bg o kern/165543 wireless [ath] ath0 endless scanning of channels without connec o kern/165517 wireless [net80211] bgscan isn't triggered when invalid beacons 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/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/163237 wireless [ath] AR5416 as HostAP. Delays among clients when a cl 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/153594 wireless [wlan] netif/devd race 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/146426 wireless [mwl] 802.11n rates not possible on mwl o kern/146425 wireless [mwl] mwl dropping all packets during and after high u 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 kern/144755 wireless [wlan] netif/devd race 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 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 kern/121061 wireless [ath] [panic] panic while ejecting ath(4)-adapter duri 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 189 problems total. From owner-freebsd-wireless@FreeBSD.ORG Mon Dec 23 16:40:26 2013 Return-Path: Delivered-To: wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F0637D88 for ; Mon, 23 Dec 2013 16:40:26 +0000 (UTC) Received: from mail-la0-x235.google.com (mail-la0-x235.google.com [IPv6:2a00:1450:4010:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 780CA1A53 for ; Mon, 23 Dec 2013 16:40:26 +0000 (UTC) Received: by mail-la0-f53.google.com with SMTP id mc6so2356058lab.40 for ; Mon, 23 Dec 2013 08:40:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=N5KZ/UOCf052H3rRBuyRMriUBHOwr59Lr1gbyS4R1dg=; b=yYchSdduAPVxA+41UR0zB2CXfiNKYruvQrI3KKf1yWcCauCHuyQ+F6hUnPH1SNFzSg Fi++YFPl+fcFXYzjhEo/F/HYhjQ4nP9a8RBLmho9BUcvbk0X8C9Pq1phOlheUiKxlRfY qoLL5XL7qRvpukYBfXzckosn4gwoZhun4lwPhdSnwHcXRle+PrR2j3xJH3VtSesc+lmL Gkw8ooMWp2AyqsmBUvQ6GTJ2JSEMV63nJwAPrr0xmiv++PgpP/GAL1YJWnCgKADZkhsj r0EElzHPd3hTNs7fi6XoFHcY9LPrdha9ljWeAWy4KFBOkik4glb7Stgg9umo5Xg08eJq FAUA== X-Received: by 10.152.234.37 with SMTP id ub5mr670574lac.51.1387816824364; Mon, 23 Dec 2013 08:40:24 -0800 (PST) Received: from [192.168.1.129] (mau.donbass.com. [92.242.127.250]) by mx.google.com with ESMTPSA id sd11sm15353785lab.2.2013.12.23.08.40.22 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 23 Dec 2013 08:40:23 -0800 (PST) Message-ID: <52B86771.7010102@gmail.com> Date: Mon, 23 Dec 2013 18:40:17 +0200 From: Volodymyr Kostyrko User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: "freebsd-wireless@freebsd.org" Subject: rum fails to transmit packets Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Dec 2013 16:40:27 -0000 Hi all. I got one rum stick bundled with problems: 14-Nov-2013 15:56:49.396 client 192.168.57.7#2494 (mtalk.google.com): view internal: error sending response: not enough free resources 14-Nov-2013 15:56:49.527 client 192.168.57.7#11463 (oc.umeng.com): view internal: error sending response: not enough free resources Those are typical errors spitted by named when it tries to reply over UDP. Number of dropped UDP packets is also raised. Typical DNS sessions looks like: * client asks; * client asks; * client asks; * client asks; * client bails off and reconnects, asks server IP by ARP and then everything magically works. I'm on ^/stable/10 and if anyone wants to try some patches - I'm open. -- Sphinx of black quartz, judge my vow. From owner-freebsd-wireless@FreeBSD.ORG Wed Dec 25 10:14:54 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A34DFE79 for ; Wed, 25 Dec 2013 10:14:54 +0000 (UTC) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8622A1843 for ; Wed, 25 Dec 2013 10:14:53 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1VvlUE-000893-QK for freebsd-wireless@freebsd.org; Wed, 25 Dec 2013 02:14:46 -0800 Date: Wed, 25 Dec 2013 02:14:46 -0800 (PST) From: Jakub Lach To: freebsd-wireless@freebsd.org Message-ID: <1387966486761-5871359.post@n5.nabble.com> Subject: I get wpa_supplicant[526]: WPA: Unsupported AES-WRAP len 34 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Dec 2013 10:14:54 -0000 Once a hour. Is this anything to worry about? No other problems I'm aware of. FreeBSD 9.2-STABLE #0 r259819 ath0: mem 0xf4200000-0xf420ffff irq 17 at device 0.0 on pci3 ath0: AR2425 mac 14.2 RF5424 phy 7.0 ifconfig: <...> media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: associated <...> media: IEEE 802.11 Wireless Ethernet OFDM/18Mbps mode 11g <...> regdomain 103 indoor ecm authmode WPA2/802.11i privacy ON deftxkey UNDEF AES-CCM 3:128-bit txpower 20 bmiss 7 scanvalid 450 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS wme burst roaming MANUAL <...> -- View this message in context: http://freebsd.1045724.n5.nabble.com/I-get-wpa-supplicant-526-WPA-Unsupported-AES-WRAP-len-34-tp5871359.html Sent from the freebsd-wireless mailing list archive at Nabble.com. From owner-freebsd-wireless@FreeBSD.ORG Wed Dec 25 16:02:50 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C0BB4496 for ; Wed, 25 Dec 2013 16:02:50 +0000 (UTC) Received: from mail-qc0-x22c.google.com (mail-qc0-x22c.google.com [IPv6:2607:f8b0:400d:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7F7FC1FE8 for ; Wed, 25 Dec 2013 16:02:50 +0000 (UTC) Received: by mail-qc0-f172.google.com with SMTP id e16so6992573qcx.3 for ; Wed, 25 Dec 2013 08:02:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=PSV30D3AEx1HMZqTQZGvsy5VsHoVNHqgUJGfaeMgLCY=; b=E2hrrgSYriwKrA1eXoYc32NCvPSz1wmxhK/e56xawujYYznUNXei0jmzsdJbqdVpUG XL1zveVOlW4bqpVCXRrfwvt5W/5nrwv4sofC+FewFnCjX/bm92y4ntFrNB6JEr0u2BO0 iMN6EpaiI41uNRixKg23MSp+DAw2Ok5T1p1IQwamCCUzqHHUPkC+fkmb0LF7dw3Nrq0Q 4oZw1oe6GotmTBtJXwKIBbEOyTpxVE/JVoteBTPaave4bUMKdY7L2oy9FGVE33RZCWFN kam5NIquoBh763LTdLy0HnFpZnUCIcSgMgOG9wuFRGW7Z9b6F4dlsmMUKB+ZWUtaWtWP qXKA== MIME-Version: 1.0 X-Received: by 10.224.124.195 with SMTP id v3mr64211437qar.55.1387987369068; Wed, 25 Dec 2013 08:02:49 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.53.200 with HTTP; Wed, 25 Dec 2013 08:02:49 -0800 (PST) In-Reply-To: <1387966486761-5871359.post@n5.nabble.com> References: <1387966486761-5871359.post@n5.nabble.com> Date: Wed, 25 Dec 2013 08:02:49 -0800 X-Google-Sender-Auth: AyTLRdFMzh7s5wtpQOMaicnQp-o Message-ID: Subject: Re: I get wpa_supplicant[526]: WPA: Unsupported AES-WRAP len 34 From: Adrian Chadd To: Jakub Lach Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Dec 2013 16:02:50 -0000 I've no idea what that is, sorry. -a On 25 December 2013 02:14, Jakub Lach wrote: > Once a hour. Is this anything to worry about? > > No other problems I'm aware of. > > FreeBSD 9.2-STABLE #0 r259819 > > ath0: mem 0xf4200000-0xf420ffff irq 17 at device 0.0 on > pci3 > ath0: AR2425 mac 14.2 RF5424 phy 7.0 > > ifconfig: > > <...> > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g > status: associated > <...> > media: IEEE 802.11 Wireless Ethernet OFDM/18Mbps mode 11g > <...> > regdomain 103 indoor ecm authmode WPA2/802.11i privacy ON > deftxkey UNDEF AES-CCM 3:128-bit txpower 20 bmiss 7 scanvalid 450 > bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 > protmode CTS wme burst roaming MANUAL > <...> > > > > > -- > View this message in context: http://freebsd.1045724.n5.nabble.com/I-get-wpa-supplicant-526-WPA-Unsupported-AES-WRAP-len-34-tp5871359.html > Sent from the freebsd-wireless mailing list archive at Nabble.com. > _______________________________________________ > 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 Dec 26 06:53:38 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A51E84AA for ; Thu, 26 Dec 2013 06:53:38 +0000 (UTC) Received: from mail-la0-x22e.google.com (mail-la0-x22e.google.com [IPv6:2a00:1450:4010:c03::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2D69E16F9 for ; Thu, 26 Dec 2013 06:53:38 +0000 (UTC) Received: by mail-la0-f46.google.com with SMTP id eh20so3490786lab.5 for ; Wed, 25 Dec 2013 22:53:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=YnwlDfa9XJzjvLZMmG8ghUmtSmxJggy7ERRaH0YA8R4=; b=LRnZ/pz4407W8yXGpIx5OXmS98WZ5uIwCz8f8nLW+a500NnDOC3aZbDPkJLm61j3TC j3N1zEiezCw9GjWPlgVr9rk6yo0unvduA0UfFe42y2oER5sRlODSbga4gf+wGCTs/Fil JZMTm3ZRCzbbupOhVGMbrXiI9U6XBEqQ+NhmhTDqj4I8D6yxvfTcFZK12CunW6wRWZVF CEMo2zGWLoqxj1HnVHo1+Smeh08v35HVqryQSB2Giguhhb1TdyQE1dXpDlU4vqtjl0vV wfl40B7PDfGbTCGf2UUjo/YGooQzCbdFGOj/03tkEzRbwAOyKE/iZyf1008q+SRmV97b wA/Q== X-Received: by 10.112.182.72 with SMTP id ec8mr210609lbc.75.1388040816132; Wed, 25 Dec 2013 22:53:36 -0800 (PST) Received: from [10.10.1.18] (gmpg.ur.ru. [195.58.11.229]) by mx.google.com with ESMTPSA id m5sm23107162laj.4.2013.12.25.22.53.34 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 25 Dec 2013 22:53:35 -0800 (PST) Message-ID: <52BBD26D.1060306@gmail.com> Date: Thu, 26 Dec 2013 12:53:33 +0600 From: Anton Mazunin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-wireless@freebsd.org Subject: Ralink RT5372l support Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Dec 2013 06:53:38 -0000 Hello everybody. Recently I was choosing usb wifi adapter for my pc, and decided the best way to be happy in this things is to buy one which is in freebsd supported hardware list. After few minutes of searching, the choise was done and I went to the closest shop and bought D-Link DWA-140. I have to say that I was very upset when my OS only showed me: at usbus1 (connected) but no device appeared in ifconfig. The only string appeared in dmesg was at usbus1 (connected). Ok, lets see what my linux laptop would show me. And you know what? The same thing! Then I decided to open the cover and see which chip is on the board. It was Ralink RT5372l. After some time of googling I recognized there is no support for this chip in run driver. So here is the question: is there any way to make this device work on my pc? btw I'm using freebsd 9.2 Thank you for help! Hope I didn't get much of your time. From owner-freebsd-wireless@FreeBSD.ORG Thu Dec 26 09:06:50 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D1B4F8CB for ; Thu, 26 Dec 2013 09:06:50 +0000 (UTC) Received: from ns.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7DAC31F7F for ; Thu, 26 Dec 2013 09:06:49 +0000 (UTC) Received: from srg.kevlo.org (mail.kevlo.org [220.135.115.6]) by ns.kevlo.org (8.14.6/8.14.6) with ESMTP id rBQ914uR025066; Thu, 26 Dec 2013 17:01:05 +0800 (CST) (envelope-from kevlo@FreeBSD.org) Message-ID: <52BBF055.1050507@FreeBSD.org> Date: Thu, 26 Dec 2013 17:01:09 +0800 From: Kevin Lo User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Anton Mazunin Subject: Re: Ralink RT5372l support References: <52BBD26D.1060306@gmail.com> In-Reply-To: <52BBD26D.1060306@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Dec 2013 09:06:50 -0000 On 2013/12/26 14:53, Anton Mazunin wrote: > Hello everybody. Recently I was choosing usb wifi adapter for my pc, > and decided the best way to be happy in this things is to buy one > which is in freebsd supported hardware list. After few minutes of > searching, the choise was done and I went to the closest shop and > bought D-Link DWA-140. > I have to say that I was very upset when my OS only showed me: > at usbus1 (connected) but no device appeared in ifconfig. The > only string appeared in dmesg was at usbus1 (connected). Ok, > lets see what my linux laptop would show me. And you know what? The > same thing! > Then I decided to open the cover and see which chip is on the board. > It was Ralink RT5372l. After some time of googling I recognized there > is no support for this chip in run driver. > So here is the question: is there any way to make this device work on > my pc? btw I'm using freebsd 9.2 > Thank you for help! Hope I didn't get much of your time. Hi Anton, RT5372 is supported in -HEAD: http://lists.freebsd.org/pipermail/svn-src-head/2013-November/053372.html If you want to give it a try, you can install FreeBSD -CURRENT using the snapshots images which you can find here: https://pub.allbsd.org/FreeBSD-snapshots/i386-i386/11.0-HEAD-r259869-JPSNAP/ Let me know if it works for you, thanks. Kevin From owner-freebsd-wireless@FreeBSD.ORG Thu Dec 26 15:13:54 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7345FB15 for ; Thu, 26 Dec 2013 15:13:54 +0000 (UTC) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5330D1826 for ; Thu, 26 Dec 2013 15:13:52 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1VwCd8-0000pw-Be for freebsd-wireless@freebsd.org; Thu, 26 Dec 2013 07:13:46 -0800 Date: Thu, 26 Dec 2013 07:13:46 -0800 (PST) From: Jakub Lach To: freebsd-wireless@freebsd.org Message-ID: <1388070826317-5871602.post@n5.nabble.com> In-Reply-To: References: <1387966486761-5871359.post@n5.nabble.com> Subject: Re: I get wpa_supplicant[526]: WPA: Unsupported AES-WRAP len 34 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Dec 2013 15:13:54 -0000 psk is 62 characters long. Coincidence? -- View this message in context: http://freebsd.1045724.n5.nabble.com/I-get-wpa-supplicant-526-WPA-Unsupported-AES-WRAP-len-34-tp5871359p5871602.html Sent from the freebsd-wireless mailing list archive at Nabble.com. From owner-freebsd-wireless@FreeBSD.ORG Thu Dec 26 15:15:09 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BC5E8B31 for ; Thu, 26 Dec 2013 15:15:09 +0000 (UTC) Received: from mail-qc0-x231.google.com (mail-qc0-x231.google.com [IPv6:2607:f8b0:400d:c01::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7A30C182A for ; Thu, 26 Dec 2013 15:15:09 +0000 (UTC) Received: by mail-qc0-f177.google.com with SMTP id m20so7626055qcx.8 for ; Thu, 26 Dec 2013 07:15:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=7IEHUOi2Ndg/inLEkUNrnnlDU9+U5OnQm5DhfntUaz0=; b=Mp2715LbIgnjN2s68AWKvvGBpmwYgqRFr6AC6gDB6stqiWrP0mrfpcXmHzdN3zcTef dRhPOWBJYYNzL/EkixWRiNR8pNlzoWJsT+Zhccmh/x3J26WJc5b8Pr1DTujhfISHc6dN UB3ol0zZePGT0+GwtT2DIO4czvdvGTufXA8hCRcPeGftOm34GHa0Xp932lH8BKZk4zlg QisvwR/458o4d+IJbvYL/OhDQJCgiNvNQL89iTqaSQyKPbpZrswnQf+o6Eb3opq4iULe QFmDSegN4EY8eIrCGygkQXh17q3Q+ZBnQW46bgmuENEuAzBG19BDQxb3kdZCDXGo2ZVi g6ng== MIME-Version: 1.0 X-Received: by 10.229.24.4 with SMTP id t4mr71728843qcb.13.1388070908579; Thu, 26 Dec 2013 07:15:08 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.52.8 with HTTP; Thu, 26 Dec 2013 07:15:08 -0800 (PST) In-Reply-To: <1388070826317-5871602.post@n5.nabble.com> References: <1387966486761-5871359.post@n5.nabble.com> <1388070826317-5871602.post@n5.nabble.com> Date: Thu, 26 Dec 2013 07:15:08 -0800 X-Google-Sender-Auth: Wbb8xAD9k0RKjWuDwInPJ5NizjM Message-ID: Subject: Re: I get wpa_supplicant[526]: WPA: Unsupported AES-WRAP len 34 From: Adrian Chadd To: Jakub Lach Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Dec 2013 15:15:09 -0000 Looks like a new encryption key exchange? -a On 26 December 2013 07:13, Jakub Lach wrote: > psk is 62 characters long. Coincidence? > > > > -- > View this message in context: http://freebsd.1045724.n5.nabble.com/I-get-wpa-supplicant-526-WPA-Unsupported-AES-WRAP-len-34-tp5871359p5871602.html > Sent from the freebsd-wireless mailing list archive at Nabble.com. > _______________________________________________ > 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 Dec 26 15:29:16 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 48C93228 for ; Thu, 26 Dec 2013 15:29:16 +0000 (UTC) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 27045190E for ; Thu, 26 Dec 2013 15:29:15 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1VwCs7-0001il-13 for freebsd-wireless@freebsd.org; Thu, 26 Dec 2013 07:29:15 -0800 Date: Thu, 26 Dec 2013 07:29:15 -0800 (PST) From: Jakub Lach To: freebsd-wireless@freebsd.org Message-ID: <1388071755017-5871615.post@n5.nabble.com> In-Reply-To: References: <1387966486761-5871359.post@n5.nabble.com> <1388070826317-5871602.post@n5.nabble.com> Subject: Re: I get wpa_supplicant[526]: WPA: Unsupported AES-WRAP len 34 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Dec 2013 15:29:16 -0000 I think so, only I don't know what is "unsupported" here, as connection works, and is RSN exclusive. -- View this message in context: http://freebsd.1045724.n5.nabble.com/I-get-wpa-supplicant-526-WPA-Unsupported-AES-WRAP-len-34-tp5871359p5871615.html Sent from the freebsd-wireless mailing list archive at Nabble.com. From owner-freebsd-wireless@FreeBSD.ORG Thu Dec 26 18:10:02 2013 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id ED3FC7FC for ; Thu, 26 Dec 2013 18:10:02 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BFF7C159E for ; Thu, 26 Dec 2013 18:10:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id rBQIA29V061835 for ; Thu, 26 Dec 2013 18:10:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id rBQIA203061834; Thu, 26 Dec 2013 18:10:02 GMT (envelope-from gnats) Date: Thu, 26 Dec 2013 18:10:02 GMT Message-Id: <201312261810.rBQIA203061834@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org Cc: From: Michael Gmelin Subject: Re: kern/176104: [iwn] iwn0: iwn_intr: fatal firmware error X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Michael Gmelin 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, 26 Dec 2013 18:10:03 -0000 The following reply was made to PR kern/176104; it has been noted by GNATS. From: Michael Gmelin To: bug-followup@FreeBSD.org, mexas@bristol.ac.uk Cc: Subject: Re: kern/176104: [iwn] iwn0: iwn_intr: fatal firmware error Date: Thu, 26 Dec 2013 17:56:39 +0000 Did you ever find a solution to this? I'm experiencing the same issue and it's happening way too often to ignore it. From owner-freebsd-wireless@FreeBSD.ORG Thu Dec 26 18:52:16 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3A106904 for ; Thu, 26 Dec 2013 18:52:16 +0000 (UTC) Received: from starfish.geekisp.com (starfish.geekisp.com [216.168.135.166]) by mx1.freebsd.org (Postfix) with SMTP id B866118E0 for ; Thu, 26 Dec 2013 18:52:15 +0000 (UTC) Received: (qmail 18540 invoked by uid 1003); 26 Dec 2013 18:52:09 -0000 Received: from unknown (HELO kiwi) (tyler@monkeypox.org@24.170.47.207) by mail.geekisp.com with (DHE-RSA-AES256-SHA encrypted) SMTP; 26 Dec 2013 18:52:09 -0000 Date: Thu, 26 Dec 2013 10:52:06 -0800 From: "R. Tyler Croy" To: freebsd-wireless@freebsd.org Subject: Checking the current iwn(4) firmware version and upgrading it Message-ID: <20131226185206.GB2259@kiwi> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+g7M9IMkV8truYOl" Content-Disposition: inline User-Agent: Mutt/1.5.22 (2013-10-16) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Dec 2013 18:52:16 -0000 --+g7M9IMkV8truYOl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I'm rather familiar with the FreeBSD source code and buildworld process, but I don't have a good idea of where binary blobs for chipset firmwares are kept. Is there a document I missed in the handbook or on the wiki which details where the firmware comes from and how one might be able to experiment with later versions? Cheers - R. Tyler Croy ------------------ Code: https://github.com/rtyler Chatter: https://twitter.com/agentdero rtyler@jabber.org --+g7M9IMkV8truYOl Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iEYEARECAAYFAlK8etYACgkQFCbH3D9R4W9bxACfQDIKq+JHC0huptmix78HcnMf RpoAn2XNJ2AJ2sDNiiAJ7x6HogtJhvDG =UnEU -----END PGP SIGNATURE----- --+g7M9IMkV8truYOl-- From owner-freebsd-wireless@FreeBSD.ORG Fri Dec 27 11:25:41 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AF466640 for ; Fri, 27 Dec 2013 11:25:41 +0000 (UTC) Received: from alpha.kreiz-it.fr (alpha.kreiz-it.fr [IPv6:2001:41d0:8:dda6::1]) by mx1.freebsd.org (Postfix) with ESMTP id 71D831762 for ; Fri, 27 Dec 2013 11:25:41 +0000 (UTC) Received: from DirTech (lnr56-1-82-246-51-185.fbx.proxad.net [82.246.51.185]) by alpha.kreiz-it.fr (Postfix) with ESMTPSA id BDE596CD; Fri, 27 Dec 2013 12:25:39 +0100 (CET) From: "Cedric GROSS" To: "'R. Tyler Croy'" References: <20131226185206.GB2259@kiwi> In-Reply-To: <20131226185206.GB2259@kiwi> Subject: RE: Checking the current iwn(4) firmware version and upgrading it Date: Fri, 27 Dec 2013 12:25:35 +0100 Message-ID: <004101cf02f6$5e93ab20$1bbb0160$@info> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac8Ca6Rm11mIJM7pQ+mEfVGneL1iKwAiJLHA Content-Language: fr Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Dec 2013 11:25:41 -0000 Hello Tyler, All iwn firmware files are kept in /usr/src/sys/contrib/dev/iwn (if your source tree is in /usr/src). But there are not used as is within kernel. If you wish to use a new firmware file you will need to : - Download firmware you wish here (http://wireless.kernel.org/en/users/Drivers/iwlwifi) - untar downloaded file and then uuencode firmware (ie: #uuencode -o iwlwifi-7260-22.0.7.0.fw.uu iwlwifi-7260-7.ucode = iwlwifi-7260-22.0.7.0.fw) - Change file's name in IMG line within Makefile of corresponding = subfolder in /usr/src/sys/modules/iwnfw/ - Rebuild your kernel (or if you remove iwnfw from your kernel config, = just rebuild iwnfw) Best regards Cedric -----Message d'origine----- De=A0: owner-freebsd-wireless@freebsd.org [mailto:owner-freebsd-wireless@freebsd.org] De la part de R. Tyler Croy Envoy=E9=A0: jeudi 26 d=E9cembre 2013 19:52 =C0=A0: freebsd-wireless@freebsd.org Objet=A0: Checking the current iwn(4) firmware version and upgrading it I'm rather familiar with the FreeBSD source code and buildworld process, = but I don't have a good idea of where binary blobs for chipset firmwares are kept. Is there a document I missed in the handbook or on the wiki which = details where the firmware comes from and how one might be able to experiment = with later versions? Cheers - R. Tyler Croy ------------------ Code: https://github.com/rtyler Chatter: https://twitter.com/agentdero rtyler@jabber.org From owner-freebsd-wireless@FreeBSD.ORG Fri Dec 27 14:50:02 2013 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C204CD29 for ; Fri, 27 Dec 2013 14:50:02 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 94F7E1506 for ; Fri, 27 Dec 2013 14:50:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id rBREo2m1050650 for ; Fri, 27 Dec 2013 14:50:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id rBREo2Ba050649; Fri, 27 Dec 2013 14:50:02 GMT (envelope-from gnats) Date: Fri, 27 Dec 2013 14:50:02 GMT Message-Id: <201312271450.rBREo2Ba050649@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org Cc: From: Eimar Koort Subject: Re: conf/184657: freebsd 10 unable to connect hidden wifi X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Eimar Koort 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, 27 Dec 2013 14:50:02 -0000 The following reply was made to PR conf/184657; it has been noted by GNATS. From: Eimar Koort To: bug-followup@FreeBSD.org Cc: Subject: Re: conf/184657: freebsd 10 unable to connect hidden wifi Date: Fri, 27 Dec 2013 16:46:07 +0200 --bcaec502d5ea820fa104ee852763 Content-Type: text/plain; charset=UTF-8 Hi, Tested a bit more. Using iwn (lenovo x200) driver i can connect to wireless network configured like this: network={ ssid="eduroam" key_mgmt=WPA-EAP proto=RSN eap=PEAP ... } and also to network which has no password at all: network={ ssid="xyz" bssid=00:... key_mgmt=NONE } I can't connect to: network={ ssid="zyx" bssid=00: key_mgmt=NONE wep_tx_keyidx=0 wep_tx_keyidx=0 wep_key0=... } network={ ssid="mywifi" scan_ssid=1 key_mgmt=WPA-PSK psk="hello nsa" } -- Eimar Koort --bcaec502d5ea820fa104ee852763 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: base64 PGRpdiBkaXI9Imx0ciI+SGksPGJyPjxicj5UZXN0ZWQgYSBiaXQgbW9yZS48YnI+PGJyPlVzaW5n IGl3biAobGVub3ZvIHgyMDApIGRyaXZlciBpIGNhbiBjb25uZWN0IHRvIHdpcmVsZXNzIG5ldHdv cmsgY29uZmlndXJlZCBsaWtlIHRoaXM6PGJyPm5ldHdvcms9eyBzc2lkPSZxdW90O2VkdXJvYW0m cXVvdDs8YnI+wqDCoMKgwqDCoMKgwqAga2V5X21nbXQ9V1BBLUVBUDxicj7CoMKgwqDCoMKgwqDC oCBwcm90bz1SU048YnI+DQrCoMKgwqDCoMKgwqDCoCBlYXA9UEVBUDxicj7CoMKgwqAgLi4uPGJy Pn08YnI+YW5kIGFsc28gdG8gbmV0d29yayB3aGljaCBoYXMgbm8gcGFzc3dvcmQgYXQgYWxsOjxi cj5uZXR3b3JrPXs8YnI+wqDCoMKgwqDCoMKgwqAgc3NpZD0mcXVvdDt4eXomcXVvdDs8YnI+wqDC oMKgwqDCoMKgwqAgYnNzaWQ9MDA6Li4uPGJyPsKgwqDCoMKgwqDCoMKgIGtleV9tZ210PU5PTkU8 YnI+fTxicj48YnI+SSBjYW4mIzM5O3QgY29ubmVjdCB0bzo8YnI+bmV0d29yaz17PGJyPg0KwqDC oMKgwqDCoMKgwqAgc3NpZD0mcXVvdDt6eXgmcXVvdDs8YnI+wqDCoMKgwqDCoMKgwqAgYnNzaWQ9 MDA6PGJyPsKgwqDCoMKgwqDCoMKgIGtleV9tZ210PU5PTkU8YnI+wqDCoMKgwqDCoMKgwqAgd2Vw X3R4X2tleWlkeD0wPGJyPsKgwqDCoMKgwqDCoMKgIHdlcF90eF9rZXlpZHg9MDxicj7CoMKgwqDC oMKgwqDCoCB3ZXBfa2V5MD0uLi48YnI+fTxicj5uZXR3b3JrPXs8YnI+wqDCoMKgwqDCoMKgwqAg c3NpZD0mcXVvdDtteXdpZmkmcXVvdDs8YnI+wqDCoMKgwqDCoMKgwqAgc2Nhbl9zc2lkPTE8YnI+ DQrCoMKgwqDCoMKgwqDCoCBrZXlfbWdtdD1XUEEtUFNLPGJyPsKgwqDCoMKgwqDCoMKgIHBzaz0m cXVvdDtoZWxsbyBuc2EmcXVvdDs8YnI+fTxicj48YnI+PGRpdiBjbGFzcz0iZ21haWxfZXh0cmEi PjxiciBjbGVhcj0iYWxsIj48ZGl2Pi0tPGJyPkVpbWFyIEtvb3J0PGJyPjxicj48L2Rpdj4NCjwv ZGl2PjwvZGl2Pg0K --bcaec502d5ea820fa104ee852763-- From owner-freebsd-wireless@FreeBSD.ORG Fri Dec 27 19:34:30 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4A84E8E9 for ; Fri, 27 Dec 2013 19:34:30 +0000 (UTC) Received: from mail-qc0-x229.google.com (mail-qc0-x229.google.com [IPv6:2607:f8b0:400d:c01::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0914D1980 for ; Fri, 27 Dec 2013 19:34:29 +0000 (UTC) Received: by mail-qc0-f169.google.com with SMTP id r5so9063731qcx.28 for ; Fri, 27 Dec 2013 11:34:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=roqHXnrpCc+uLu00axE1U+S/Aw3FBJ+MWN6QWjRFnlk=; b=A6FtTVmTIf1dpO7Ol8pjsQ9kTPIf2ZJw0+kkz3ja7vscbq+VqOEqLKlbiOadwohlq3 BF+FiKj3Jo8XEm+FHUH687i6SD4ETTXaIltnQE9vCS9fAdHbKX/PQv8BFkiy+LOo6Kqy LqIXDIy63rG1oHyE5VBIaYuRYIENH8szbOdPY/OZg/rPW479twrJtF+8hX4eEDmCOd2I Li6QG4dEusZb0W6cGdrzS74l3V4gFe/qwcKXWqw++zVAVF0h54F6LNP64I7VIC+0orV4 l2lsAzCe5s1KamTZ+PiHmAj5uKrt77JLNcZdNA72l96ZnUXjhGhpRO7V8QM4AOJ+kpPM UKaw== MIME-Version: 1.0 X-Received: by 10.224.46.8 with SMTP id h8mr82831223qaf.49.1388172869167; Fri, 27 Dec 2013 11:34:29 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.52.8 with HTTP; Fri, 27 Dec 2013 11:34:29 -0800 (PST) In-Reply-To: <201312271450.rBREo2Ba050649@freefall.freebsd.org> References: <201312271450.rBREo2Ba050649@freefall.freebsd.org> Date: Fri, 27 Dec 2013 11:34:29 -0800 X-Google-Sender-Auth: MnKSh7NnFWWeS6HNHbktIkrAFds Message-ID: Subject: Re: conf/184657: freebsd 10 unable to connect hidden wifi From: Adrian Chadd To: Eimar Koort Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Dec 2013 19:34:30 -0000 I've not tried associating to a hidden SSID before. Guess it needs some debugging. Sorry, -a On 27 December 2013 06:50, Eimar Koort wrote: > The following reply was made to PR conf/184657; it has been noted by GNATS. > > From: Eimar Koort > To: bug-followup@FreeBSD.org > Cc: > Subject: Re: conf/184657: freebsd 10 unable to connect hidden wifi > Date: Fri, 27 Dec 2013 16:46:07 +0200 > > --bcaec502d5ea820fa104ee852763 > Content-Type: text/plain; charset=UTF-8 > > Hi, > > Tested a bit more. > > Using iwn (lenovo x200) driver i can connect to wireless network configured > like this: > network={ ssid="eduroam" > key_mgmt=WPA-EAP > proto=RSN > eap=PEAP > ... > } > and also to network which has no password at all: > network={ > ssid="xyz" > bssid=00:... > key_mgmt=NONE > } > > I can't connect to: > network={ > ssid="zyx" > bssid=00: > key_mgmt=NONE > wep_tx_keyidx=0 > wep_tx_keyidx=0 > wep_key0=... > } > network={ > ssid="mywifi" > scan_ssid=1 > key_mgmt=WPA-PSK > psk="hello nsa" > } > > > -- > Eimar Koort > > --bcaec502d5ea820fa104ee852763 > Content-Type: text/html; charset=UTF-8 > Content-Transfer-Encoding: base64 > > PGRpdiBkaXI9Imx0ciI+SGksPGJyPjxicj5UZXN0ZWQgYSBiaXQgbW9yZS48YnI+PGJyPlVzaW5n > IGl3biAobGVub3ZvIHgyMDApIGRyaXZlciBpIGNhbiBjb25uZWN0IHRvIHdpcmVsZXNzIG5ldHdv > cmsgY29uZmlndXJlZCBsaWtlIHRoaXM6PGJyPm5ldHdvcms9eyBzc2lkPSZxdW90O2VkdXJvYW0m > cXVvdDs8YnI+wqDCoMKgwqDCoMKgwqAga2V5X21nbXQ9V1BBLUVBUDxicj7CoMKgwqDCoMKgwqDC > oCBwcm90bz1SU048YnI+DQrCoMKgwqDCoMKgwqDCoCBlYXA9UEVBUDxicj7CoMKgwqAgLi4uPGJy > Pn08YnI+YW5kIGFsc28gdG8gbmV0d29yayB3aGljaCBoYXMgbm8gcGFzc3dvcmQgYXQgYWxsOjxi > cj5uZXR3b3JrPXs8YnI+wqDCoMKgwqDCoMKgwqAgc3NpZD0mcXVvdDt4eXomcXVvdDs8YnI+wqDC > oMKgwqDCoMKgwqAgYnNzaWQ9MDA6Li4uPGJyPsKgwqDCoMKgwqDCoMKgIGtleV9tZ210PU5PTkU8 > YnI+fTxicj48YnI+SSBjYW4mIzM5O3QgY29ubmVjdCB0bzo8YnI+bmV0d29yaz17PGJyPg0KwqDC > oMKgwqDCoMKgwqAgc3NpZD0mcXVvdDt6eXgmcXVvdDs8YnI+wqDCoMKgwqDCoMKgwqAgYnNzaWQ9 > MDA6PGJyPsKgwqDCoMKgwqDCoMKgIGtleV9tZ210PU5PTkU8YnI+wqDCoMKgwqDCoMKgwqAgd2Vw > X3R4X2tleWlkeD0wPGJyPsKgwqDCoMKgwqDCoMKgIHdlcF90eF9rZXlpZHg9MDxicj7CoMKgwqDC > oMKgwqDCoCB3ZXBfa2V5MD0uLi48YnI+fTxicj5uZXR3b3JrPXs8YnI+wqDCoMKgwqDCoMKgwqAg > c3NpZD0mcXVvdDtteXdpZmkmcXVvdDs8YnI+wqDCoMKgwqDCoMKgwqAgc2Nhbl9zc2lkPTE8YnI+ > DQrCoMKgwqDCoMKgwqDCoCBrZXlfbWdtdD1XUEEtUFNLPGJyPsKgwqDCoMKgwqDCoMKgIHBzaz0m > cXVvdDtoZWxsbyBuc2EmcXVvdDs8YnI+fTxicj48YnI+PGRpdiBjbGFzcz0iZ21haWxfZXh0cmEi > PjxiciBjbGVhcj0iYWxsIj48ZGl2Pi0tPGJyPkVpbWFyIEtvb3J0PGJyPjxicj48L2Rpdj4NCjwv > ZGl2PjwvZGl2Pg0K > --bcaec502d5ea820fa104ee852763-- > _______________________________________________ > 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 Sat Dec 28 05:52:20 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 30655B1E; Sat, 28 Dec 2013 05:52:20 +0000 (UTC) Received: from mail-qe0-x232.google.com (mail-qe0-x232.google.com [IPv6:2607:f8b0:400d:c02::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D1B2E10AB; Sat, 28 Dec 2013 05:52:19 +0000 (UTC) Received: by mail-qe0-f50.google.com with SMTP id 1so9948428qec.9 for ; Fri, 27 Dec 2013 21:52:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=4ZVGrWrGuhmCbsHsRWSIXVMEQsVnGVhUD+qNcrO2xvU=; b=rRM/EzZ2ZzqPnF3VhfF3RL/CzQvP3fm6QWfw8V+nIaVTaiXY289t4qhlgMgEccrB2p ZTrlR7iL9CpZYjXNMKZanCnLMRuN+hAC2M7lN/Mdk25GRsDYbW2Bzv0lSdrg6+BmAhiY CxO+Bslcf7i7k0TicxtEUJ1ij9frjOJ71tB7CgBnAbYohyT0xoGYcfrDaU6bWUtt/sWR epG2lpHonPSqYQ5ZKNl6WBH46zMq68aOFBsCAfiLnLUz/Me5JSi+f5wDH/uot9D1WvCT A+XoJ3LAb+eyHqQPq0J0wyjyBUYI/XKhlFbefvWf0BbPzXTkfAtV5V5XTgoqacgYVSAn uqsg== MIME-Version: 1.0 X-Received: by 10.229.56.200 with SMTP id z8mr85838650qcg.1.1388209938551; Fri, 27 Dec 2013 21:52:18 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.52.8 with HTTP; Fri, 27 Dec 2013 21:52:18 -0800 (PST) In-Reply-To: <52B6F654.1000804@mehnert.org> References: <52B6F654.1000804@mehnert.org> Date: Fri, 27 Dec 2013 21:52:18 -0800 X-Google-Sender-Auth: NfExN8gfX5qBxvauck2EAXElN88 Message-ID: Subject: Re: iwn trouble From: Adrian Chadd To: Hannes Mehnert , "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Dec 2013 05:52:20 -0000 Hi, I just fixed the Intel 6150 support. I'm emailing this from said Intel 6150. Please update to the very latest -HEAD and try! Thanks! -a On 22 December 2013 06:25, Hannes Mehnert wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA384 > > Hi, > > I'm running current and iwn fails to load. > > branch user/ed/newcons (from github) with latest commit: > commit d16cc4039855b100f5b3e966a43dabe2028f2b57 > Author: emaste > Date: Fri Dec 6 13:58:23 2013 +0000 > > Make Newcons options clear in GENERIC on the project branch > > My intel card is the following (pciconf -lv): > iwn0@pci0:3:0:0: class=0x028000 card=0x13118086 chip=0x00898086 > rev=0x5e hdr=0x00 > vendor = 'Intel Corporation' > device = 'Centrino Advanced-N + WiMAX 6250 [Kilmer Peak]' > class = network > > > dmesg has the following information: > iwn0: mem > 0xf2500000-0xf2501fff irq 17 at device 0.0 on pci3 > > [and after service wpa_supplicant start wlan0] > iwn0: iwn_config: could not configure runtime calibration > iwn0: iwn_init_locked: could not configure device, error 35 > > An earlier kernel (from mid November) from the same branch works like > a charm. > > Any hints? Is there more debug output I can provide to track this down? > > > Cheers and thanks, > > Hannes > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.19 (FreeBSD) > > iQIcBAEBCQAGBQJStvZUAAoJELyJZYjffCjupYoP/j3SLrU21mSmydo6AxJaaBA3 > +1I79QyyGoz6Kp3ea4sxSVMrnuWK3J6NKO5YCf0b10gjISA/iYOoHNh12Vltch3g > x30+APbFtOq5IswO66HY816LOzYDo2fXGxMk/CZhspyOhJptC4bZWb9nrSoEQHEI > UvjysflDUUDTa+vs/1CQ0Rall7FVmNSr7eeNdTCHhgV0xF7F7IqyUW6JbnDaYQEA > mDwi5cxQNVhOeHjMd0wACO5rf09/bMdvo4m4DNnQNWrg9oPtbuWdRLMRtPZ0UC8W > 4w+2ETWYgMCMiZO3kmwG76NI2jzXKHYwQO2/RrTahyWWcWuDzeJm5tK5PjxoN+JB > B4B7AB/DIUQsUmBUhjZHTvg+U9Qa37wCWYGN5UO3aM4BEp4FTR4lsp80oEbt5/bt > axOi1QVtZl1ZPOgZaoCXFiW4SQKA568uAiX8hlxfs2W1yAJ7CU4bfRyCugUVhBBK > ZQAS1hX2sxXJHddrJwNNmAJ2/x+5NcYvzf4ij4hSIk5Gw4oP280rp/u2QIzCyhKx > x8c5aPpJgIw/UNHYrBjAoHj+t5qHYANtgqLQUk3BEGOAoCsR2LzgBxObIZn+wRLv > aS8qjC3NCknZLNuWPWdrQBleQV9EkqlJ7ODcgv82bqFUdNMwSKcmcX4TmLIvigDH > CD+7c6uMkJB681a/IHTX > =h++r > -----END PGP SIGNATURE----- > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"