From owner-freebsd-wireless@freebsd.org Mon Nov 13 16:40:25 2017 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6C8BCDBEBF7 for ; Mon, 13 Nov 2017 16:40:25 +0000 (UTC) (envelope-from khanzf@gmail.com) Received: from mail-qt0-x22a.google.com (mail-qt0-x22a.google.com [IPv6:2607:f8b0:400d:c0d::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 25177743E8 for ; Mon, 13 Nov 2017 16:40:25 +0000 (UTC) (envelope-from khanzf@gmail.com) Received: by mail-qt0-x22a.google.com with SMTP id d9so20271196qtd.7 for ; Mon, 13 Nov 2017 08:40:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:message-id:date:user-agent:mime-version :content-language:content-transfer-encoding; bh=LbLaWcStj1x1ayQ6wOwC8s6rK7++exSPBFqWdgtVhAE=; b=OWT0hlQPAHcJexkv+oJX0mdG/JTsO+MrVFOSsSuCvrGcSsgr9L32TfIPrZON1Pf/uD Svsl/EufKBc1PhBClAnm9IaKgepekPU6dOBHniy+j2Fa9Btn9QG98tdRf6/CLlPN1tVh Z+RBw5nIcMI0H1YDYwWZJy0HyJzgIsO2eBDBUlNGsLorBH0vg3b0ew5W2Sn2Ta9L526z hKz7PJmn43dC3pHpLsqpt9BAZY2FXWIsXAMAtopD3ei5VEDtKtruc0Vzs+xmZwuwk5lV MP9XwCxh/tb+PDehkCIvJRx59JOSTmCQIb+pd/gAiqPosW7aqS5OV8vlmsEL9PzEu62r HgzA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:message-id:date:user-agent :mime-version:content-language:content-transfer-encoding; bh=LbLaWcStj1x1ayQ6wOwC8s6rK7++exSPBFqWdgtVhAE=; b=jC26UOAzEqoIuWiO3EO5RjfIfnij/iuqMsByn1qL3fm6njylgx1fn/9klyL3/Tc2EP SXlzkxorn5M32M4VKD34Ch4KD5xgpnM1yQKTrS5qcLYBabkJHs+krm85KcTlMCii75TO /GgPp9515ZmxOkQtnOF1zry8exeFbwOWeACtn8MUsvy3sBbwu+x8Ri/B7dA0GaaXi4M7 YNXra2yfERdjF4cf2mql/w8Ekwt+tRM0qGBgyfr5ObZIQR3DLVcK3SOTH+I3f0rOgkKa IQa5FXZGDh6nIr25FE4tuT4oH/rrvg04LOf/M8Vbk68Bpkl59Yj7WJcXmN4bLoQbQ8fd Otgw== X-Gm-Message-State: AJaThX4Y2zNlSZjiJum9TiulGW/J5/q2QKkQcIoQMYnrQ3Kc2w+wyAUK tvPt7hkPKMjE3IH94ffHpCPSqhsr X-Google-Smtp-Source: AGs4zMb8i3aebxBLgGNcm9k+52k5SYp0Z8sHof0F2KmTPQif6Pn7bo9u/Zr9POTihPDDzlnicNgKYA== X-Received: by 10.237.42.15 with SMTP id c15mr9876532qtd.19.1510591223946; Mon, 13 Nov 2017 08:40:23 -0800 (PST) Received: from pc.farhan.codes ([2001:470:8:209::dead:c0de]) by smtp.gmail.com with ESMTPSA id s1sm11242865qte.8.2017.11.13.08.40.23 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 13 Nov 2017 08:40:23 -0800 (PST) From: Farhan Khan To: freebsd-wireless@freebsd.org Subject: ieee80211 scan function starting point Message-ID: Date: Mon, 13 Nov 2017 11:40:23 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.25 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, 13 Nov 2017 16:40:25 -0000 Hi all, I am trying to get the "ifconfig wlan0 list scan" command to display local access points. I am fairly certain I have the "up" part working (loading firmware, turning it on) but the scan portion does not yet. I am trying to identify what functions I might have missed with dtrace, but I do not know where to start off and the probes are too rapid to identify where it starts when I run the "ifconfig" command. I am fairly certain it originates in ieee80211 and kicks that off to the driver, but I cannot easily identify where. Does anyone know where? Thank you. Farhan From owner-freebsd-wireless@freebsd.org Mon Nov 13 16:59:24 2017 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 014EEDBF360 for ; Mon, 13 Nov 2017 16:59:24 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wr0-x22f.google.com (mail-wr0-x22f.google.com [IPv6:2a00:1450:400c:c0c::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 89A1A750D0 for ; Mon, 13 Nov 2017 16:59:23 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-wr0-x22f.google.com with SMTP id k61so15019414wrc.4 for ; Mon, 13 Nov 2017 08:59:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=u/WhS//Lw4zyUzi4oZCIBbP5W2pjgNseRATrAVFHnjM=; b=gDGboosVoqv4pbgmL5I19NE3c1RIhOrZizp/doprM51rJzDSQWUr/bedlgY0vyvT+z 9h10e8IA+enSfdLx9ZjOk+2CbrRKfbbeQnDCJhW7CuAbLmzXQh0E2MtNnOQT+FJ9BKpd OU9yLmOquH4eeEsPwQgR6t2fO199/+EYyNUrc/vCa48dUByFizrfJQhZwB8ACv4/cdin pSFWzZJ3hfF3a2xafdKuzPBGGXJ6DQYORA5TZwbvAm0g2lRaVQOtGm+4BoCUeKfIIzFd ajaMFJLHIH3PrW2yy2Nsd83Hbug5lSCrM6/AXuZc0vyaNrZO9qlUQxTgyfVyDbwSLoY/ FvkQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=u/WhS//Lw4zyUzi4oZCIBbP5W2pjgNseRATrAVFHnjM=; b=rv11bHJ7dCrZf+NHxR414kvej56AGw71p2WpWNkJ6ilWntHWH0EVyFZLWZrTpIcMKu Ob2lpMywC7BMG1UQQAMoe7cgPMd37dxJGoxkit3iPfm9V8Sbo+H5zPNTsU7uCx6r5C6V YcO09Gx758+xAppRIkMaOHUDesP7RSRBnaTBe5QwyZA0tkmrDAW6C7EWVdxmcGrFsExn X2hJtS0sSARwdNbug1N3IVGfCuHXtHb1CwQWrhWSd3B+UuvBTHOTYOuIJxLRcVXy/RWL 8tOd9JX/OtkbIfTs1EpzRAmtogFn4usj4bPIFhWAgVTlYcjTqyL+IIVUIvzBgEQq+1uN fqMg== X-Gm-Message-State: AJaThX4bHyJmO7UseciGfQjtZKIoJFyKLjUjUb5YdJGUkXwF4xBfGGBu R/FwSevwwagl1fgiUM0Bl+RgEX1lFtTGD7URUQD5ng== X-Google-Smtp-Source: AGs4zMbZ5sjDdDTvXjYKrFrxCYB/OKD5lmRBwjMOUZwOjfTtK0o1SnP6Y/4ZojTibjx+iohGREp9Jv7wlIVNSceT4a4= X-Received: by 10.223.179.194 with SMTP id x2mr8102671wrd.266.1510592361622; Mon, 13 Nov 2017 08:59:21 -0800 (PST) MIME-Version: 1.0 Received: by 10.28.46.209 with HTTP; Mon, 13 Nov 2017 08:59:20 -0800 (PST) In-Reply-To: References: From: Adrian Chadd Date: Mon, 13 Nov 2017 08:59:20 -0800 Message-ID: Subject: Re: ieee80211 scan function starting point To: Farhan Khan Cc: "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.25 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, 13 Nov 2017 16:59:24 -0000 hi! So, the scan portion works a couple ways. Firstly, the interface moves to mode IEEE80211_S_SCAN . That's when it's looking for networks to connect to. Secondly, it marks a FEXT or a normal flag SCAN, which says "i'm doing scanning as well as normal receive." Think of this for example like doing a background scan whilst doing traffic. The routines in ieee80211_scan.c and ieee80211_scan_sw.c and ieee80211_scan_sta.c take care of starting the scan, changing channels if needed, etc. There are two paths here. ieee80211_scan_sw.c implements the net80211 controlled scanner. This schedules channel changes, background scanning, etc. Most drivers do this. Drivers that implement scanning in the driver/firmware instead tie into the scan routines and will start their own scans. rsu, iwm, iwn do this - they send a scan command to the firmware. It doesn't require normal traffic to be stopped; the firmware takes care of scheduling when to do scanning and when to do data! Then there's two paths into populating the scan cache. One - the device (eg almost everything) just pass up received beacons in scan mode. ieee80211_input_sta() will filter out the relevant beacon frames. Look at sta_recv_mgmt(), SUBTYPE_BEACON, it'll eventually end up at ieee80211_add_scan() . Two - intelligent devices can populate the scan cache directly. I think if_ndis does this (via a call to ieee80211_add_scan()). Everything else so far returns beacon frames as RX frames when scanning. So, that's why I said "do monitor mode first." Ideally you'd like to get monitor mode RX working first. Once you get beacons showing up in an 802.11 tcpdump you know you're ready for doing STA mode (and transmit!). -adrian On 13 November 2017 at 08:40, Farhan Khan wrote: > Hi all, > > I am trying to get the "ifconfig wlan0 list scan" command to display local > access points. I am fairly certain I have the "up" part working (loading > firmware, turning it on) but the scan portion does not yet. > > I am trying to identify what functions I might have missed with dtrace, but > I do not know where to start off and the probes are too rapid to identify > where it starts when I run the "ifconfig" command. I am fairly certain it > originates in ieee80211 and kicks that off to the driver, but I cannot > easily identify where. > > Does anyone know where? Thank you. > > Farhan > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://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 Nov 14 23:55:15 2017 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 94116DB99E0 for ; Tue, 14 Nov 2017 23:55:15 +0000 (UTC) (envelope-from khanzf@gmail.com) Received: from mail-qt0-x232.google.com (mail-qt0-x232.google.com [IPv6:2607:f8b0:400d:c0d::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BBF575B0C for ; Tue, 14 Nov 2017 23:55:15 +0000 (UTC) (envelope-from khanzf@gmail.com) Received: by mail-qt0-x232.google.com with SMTP id p44so20078028qtj.6 for ; Tue, 14 Nov 2017 15:55:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:subject:to:message-id:date:user-agent:mime-version :content-language:content-transfer-encoding; bh=6h8CpPyFi8gzAi5Uef8JvBzZSC3cmhv4IqxUssUWWDA=; b=ff+xunxoReAiI1PTQzS4SrMPLCDqudbbf9BRJfjDqrks4cQLIGdm2pdIKhir/CLiYW T3ZLq2o014+H2xkI3p4ZhrGOirTRbt70oICuU0NthC6/fdMDaVFfw3UdkHCg6/I55Pj1 N1y9xfEd0qg18tFQfn/SSk91nsxX79k0K0K3o9r6sttsBPzAgFVnRD4yG+OVHwfbBa9U Ht7XSeeWVue41L5pnrOOKh1EPtFrnJEsRJ3fi1YEPVqF3vFKpppOzmQIInaJlmZD4oe8 sPqPGWjkzPMFnZUgNg/aq+MJwG/dNJX5ReNL2LCg4ZwKeTXWa3+pWh1TV9HLVwKr1uk5 rlYQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:message-id:date:user-agent :mime-version:content-language:content-transfer-encoding; bh=6h8CpPyFi8gzAi5Uef8JvBzZSC3cmhv4IqxUssUWWDA=; b=Q8AE7IKggU/Rn+nLJWIs4SLFNNtu28W9edoxbntWPc2CNJYfV9NRvQC3R0cbBggndE EmfqOwatv02cvGe4DPgsA/P6mJL+czqeA+6XJ63s8m9N6H+B1QaBLD7yao5VKFXgxsBe jA5LdENWJhpKhhcZ0rLT4cvJ+x92roussGGScT+e4QSrUy3bB/pNoGd41/FFKhWlQeXV X9Ml4jJrxlOYKzJRXfzTUmycG0qwEmIl9Vgb1HBiunoq6OvfnJEfDHRMJYNT7RJ7pfDT I119jMS9TvOSX20xNiYdZGcEzFEixhmiV4ZYI8fu/y+4AH3ipwR7MjLm/xknpQasfmHQ 41Ow== X-Gm-Message-State: AJaThX43WOvsd2/9Lqgh0n2hFRumIl698eOPQKjuU8Uyxy8lylvLHyfh Fl7zbOzJXzY3oegyTXG0lHfUc0u6 X-Google-Smtp-Source: AGs4zMYjrBtiVtxM23HHrlw4PcjIDyNSnThZDf9Kr5V5Na5tWj1s8bY7k4kejvz4BZvT/LCISx2Qog== X-Received: by 10.55.146.65 with SMTP id u62mr8485834qkd.112.1510703714067; Tue, 14 Nov 2017 15:55:14 -0800 (PST) Received: from pc.farhan.codes ([2001:470:8:209::dead:c0de]) by smtp.gmail.com with ESMTPSA id e96sm9775480qtb.84.2017.11.14.15.55.13 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Nov 2017 15:55:13 -0800 (PST) From: Farhan Khan Subject: rtwn card not delivering interrupts from beacon frames To: freebsd-wireless@freebsd.org Message-ID: <80883a0a-5ca3-0492-d10d-ceeb3fd41b4b@gmail.com> Date: Tue, 14 Nov 2017 18:55:13 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.25 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, 14 Nov 2017 23:55:15 -0000 Hi all, As discussed, I am working on the rtwn rtl8188ee driver. Per Adrian's advice, I am focusing on having the card reading beacon frames. I am running the following tcpdump line, which works on another machine with an rtwn card. # tcpdump -y IEEE802_11_RADIO -i wlan0 -e -s 256 type mgt Unfortunately, my card still does not receive beacon frames. Per IRC conversations, this information is delivered to the driver via an interrupt. I retracted my sc_init_intr code and found that the interrupt register was incorrectly set, so I updated them per the Linux driver and started having sc_classify_intr trigger very slowly (1-2 a minute), rather than with every beacon frame from a nearby Access Point. The 'status' was set to 0xffffffff, so it immediately exited. What might this mean? I am stuck and not certain why I am not receiving more beacon frames. I have retraced the code, but am not finding what I might have left out. Any ideas? I can show code if requested. Been on this driver for a little more than a year now and would like to start making progress. :/ Thank you, Farhan From owner-freebsd-wireless@freebsd.org Thu Nov 16 04:33:11 2017 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 77266DBC187 for ; Thu, 16 Nov 2017 04:33:11 +0000 (UTC) (envelope-from jguojun@sbcglobal.net) Received: from sonic305-5.consmr.mail.bf2.yahoo.com (sonic305-5.consmr.mail.bf2.yahoo.com [74.6.133.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3F8F46BA26 for ; Thu, 16 Nov 2017 04:33:09 +0000 (UTC) (envelope-from jguojun@sbcglobal.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sbcglobal.net; s=s2048; t=1510806788; bh=S+BANfls1y1ytW0SAR2R1zT+K2thCnm0ThQPwRtbEAg=; h=Date:From:Reply-To:To:Subject:References:From:Subject; b=NyZxK+AM5Jv898T/N2/1zS5ir1GygKfMifys3L75oWiyYWOj9gQBRBzSEn12AqWLUHpF43RL4MEHW5TGQGyILNW4/IkOiRHqIjj2j5cJZaug87t+DGrjcWMwtNeCPYTa4c6zrgTwnjwTx6aigRfW4G9RsqKVNEfZHJ2T0UKvEYOJ0PpyORqKQsZDlaRVrcnmtQMjgLOWz6m6AiwQrRpzYk9P9FIKFasJCWN69ux0CGbV7c+mW+jX+ciQ0aQuQJMr55VJWhDLH1Gh18ViBGnY/EPmBaacnxXLI9Af/aBSZYH03S9PBOvF1GExzONRFLGLxC7gHG6FyKrPt2p26raLFw== X-YMail-OSG: ppKCXwAVM1mlr.AkVqcy_KtJa8fpUpSWpMxDCuC1tA0hvUieBB6kZeafBR9hluF 3jXSKHwosUjr0YGeniJAGA8zIQtuhuYl8ixAhFIIqclN_6DR26epciDp2I2OUi4hTUovBBHDOVD4 F6s6Pi2NsUlKVoEys07ZYCkj8rFdimndwB74WONSmcjFj476BRHugqdBqzm61nC_W0.Z_BEo5dau wo15c6kaBsZCwmaYuDtKU4TzXs_iqTrEbaLfowxSrue6furRgZWzPKB.segORa0Yj5d8X6dRGenX AzU_Ph89_zJqmKFkrZztutRc0RiNQ_R4B.RKM.N3n3YGl7g4VBpsZyXjGnhwwwC8YoTVhBYMSwxB Ss5HYPa1.K_WMoPwwvrM6t3rV_X3IezX5gmxQQ_gUKxOyRBN6oq8ZG_1E0gSGfC8fpsQqAYPz8kF Kns_e3daYtJ4JPIIOX.nx84.d0YBw6b.8wVkcd4l2fC1vMm77dEpc9x3WRAdDVWe0t32pcZclp2S UPWsWhZ_oM3vjnv4KNepORnlZAfuZ Received: from sonic.gate.mail.ne1.yahoo.com by sonic305.consmr.mail.bf2.yahoo.com with HTTP; Thu, 16 Nov 2017 04:33:08 +0000 Date: Thu, 16 Nov 2017 04:22:56 +0000 (UTC) From: Jin Guojun Reply-To: Jin Guojun To: FreeBSD Questions Mailing List , "freebsd-wireless@freebsd.org" Message-ID: <1549082696.1167092.1510806176761@mail.yahoo.com> Subject: AR9565 wireless chip support MIME-Version: 1.0 References: <1549082696.1167092.1510806176761.ref@mail.yahoo.com> X-Mailer: WebService/1.1.10942 YahooMailNeo Mozilla/5.0 (X11; FreeBSD amd64; rv:56.0) Gecko/20100101 Firefox/56.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.25 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, 16 Nov 2017 04:33:11 -0000 Although the handbook does not says that Atheros AR95xx has been supported in current stage, ath(4) in both 10.4-R and 11.1-R seems able to connect to the AP with a short life.wlan0 can obtain the IP address via DHCP, but just cannot stay connected after getting the IP (no carrier). Is anywhere in the driver we can tweak to make this chip works? Thanks,-Jin From owner-freebsd-wireless@freebsd.org Sat Nov 18 08:07:51 2017 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DBCE1DF16D4 for ; Sat, 18 Nov 2017 08:07:51 +0000 (UTC) (envelope-from bounce+d721ed.69110-freebsd-wireless=freebsd.org@miator.net) Received: from mail-s68.mailgun.info (mail-s68.mailgun.info [184.173.153.196]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A4645675FA for ; Sat, 18 Nov 2017 08:07:51 +0000 (UTC) (envelope-from bounce+d721ed.69110-freebsd-wireless=freebsd.org@miator.net) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=miator.net; q=dns/txt; s=krs; t=1510992465; h=Content-Type: Cc: To: Subject: Message-ID: Date: From: References: In-Reply-To: MIME-Version: Sender; bh=O696Sczd93hoJz6OQsyeqbevKyeGM03Uvdj9f5dfZJQ=; b=NEHhOLRNNWXyK1JDxw2ptRkLuQqLWlP6oxHFwJ7ytqJ9iSdNXcxLpmMMmB/PBubLDoVOFH/y gBMRAmhUg+NTYTqtCxfh9xliESbcAF1va4pR+Bb9Riz4FJoYENnPZdnXe9/KU/aRYgPRrb5C ux0BP6MLV8SMsrDsMYhgtW6iQgo= Sender: zy@miator.net X-Mailgun-Sending-Ip: 184.173.153.196 X-Mailgun-Sid: WyIzOTc3YyIsICJmcmVlYnNkLXdpcmVsZXNzQGZyZWVic2Qub3JnIiwgIjY5MTEwIl0= Received: from mail-qt0-f171.google.com (mail-qt0-f171.google.com [209.85.216.171]) by mxa.mailgun.org with ESMTP id 5a0fea50.7f4c342071b0-smtp-out-n02; Sat, 18 Nov 2017 08:07:44 -0000 (UTC) Received: by mail-qt0-f171.google.com with SMTP id n32so9587891qtb.2; Sat, 18 Nov 2017 00:07:44 -0800 (PST) X-Gm-Message-State: AJaThX65WywW8iMYISv2KLjthq1EkKjZtvCfCbTmLGX+Ae1+X+dmCT9l Mc3G2JHgCeFHk78H/HAXkdLwfSLJi26ImT25vog= X-Google-Smtp-Source: AGs4zMYAHmk1LAHPbEwlaozg4XIieAiYHvt/Ae9ee/PU7NG292Z0ig7AdQ+Xezfk1qhrxsw2at+CQDXPDRLLkaItQiQ= X-Received: by 10.200.54.236 with SMTP id b41mr13132515qtc.280.1510992464246; Sat, 18 Nov 2017 00:07:44 -0800 (PST) MIME-Version: 1.0 Received: by 10.200.41.106 with HTTP; Sat, 18 Nov 2017 00:07:43 -0800 (PST) In-Reply-To: References: From: Zhihao Yuan Date: Sat, 18 Nov 2017 02:07:43 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: iwn crashing on 11n network To: Zhihao Yuan Cc: FreeBSD-STABLE Mailing List , freebsd-wireless@freebsd.org, avos@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.25 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, 18 Nov 2017 08:07:52 -0000 On Thu, Nov 9, 2017 at 2:53 AM, Zhihao Yuan wrote: > > The issues is here: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214435 > > We observed same error from two cards, > > Intel Centrino Wireless-N 1000 > > and > > Intel Centrino Ultimate-N 6300 > > both on 11. > Ping? Is iwn driver still maintained? -- Zhihao Yuan, ID lichray The best way to predict the future is to invent it. _______________________________________________ From owner-freebsd-wireless@freebsd.org Sat Nov 18 08:58:32 2017 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BAE14DF2332; Sat, 18 Nov 2017 08:58:32 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wr0-x232.google.com (mail-wr0-x232.google.com [IPv6:2a00:1450:400c:c0c::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F95268855; Sat, 18 Nov 2017 08:58:32 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-wr0-x232.google.com with SMTP id u40so3984618wrf.10; Sat, 18 Nov 2017 00:58:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=oa+YNyzOsRmSucrFhnM3KyF016CplqftP1uH15s00vY=; b=cQ3QweeLWBgO2Qm0GSnh4Q7WVOzTrlUdIakji+QA/3MYmhChMtAiZNw9mR88vNEveI zS7aEzDa1ulcS/cV87xN4EfJ5jam/VF3Dywr8fWtN2wdJnzuMrtTjeFnYBo1YNbSyPLU 5grWrQepIzhhnXJMSTYoP3AdAPKYgprtj7Xb3Nvm5hksfWYP+amzBuhGeElmUe70qxbs rbA02v2ItdAW/HVZ7yCCOtahdXJvUkMlOUmoORKamufRChjJ8zE1PTPtrYaysQ8Due8k +POLIps6K/JfKwcW64VubILENPnUm0Q5GaARBSSA7DoVZ2eRRJdlCI+l1yIMcrYka24A rjuQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=oa+YNyzOsRmSucrFhnM3KyF016CplqftP1uH15s00vY=; b=g0FWlc9HgDIIVsY7vpSxSvUKalWHSCGHohRV+xj8dKBwjd7WQHCNZz7yjxI1ioKInD XcQeA/4U8QnocUQA8tEx4AnRfEOrH5yiDuak5T6xyLO2DTPou2KkVZGkQjoHlvVHh6c2 IK0JcZLJ/j+jskXuARvibbHk8swLNoy82s17QopMxSRb2uDzFZZAKV/8K+DtGXR/xVrs c7Jn4Elol4RaqDM2nYzNZzmdAsmdCOvkW2fcGAUrU8leSaykQi+JfGt4/LBD5+yvHe9U +0OijH0RxSCjURmvht/3JlqYDIsu9SFsldTNd7d66Vuak+BG2cSZEfcPy6XyKdUAhlev 5DBA== X-Gm-Message-State: AJaThX79rhpwxWu/e+dfaGIfkroniCjguBy835AlAX7kiY4A5tCuYW4r XrOLmDSge2CZj/6wfhvSrOq+naqH4rLIAEfQHeY= X-Google-Smtp-Source: AGs4zMYiG819SW/8g8O8I/y3KHtz9n5SbALX78Q1VMMshOLb3NETbKzY34z1wZKM8fdGSOcDIZgyEL5n/sBuPFxIPZU= X-Received: by 10.223.179.194 with SMTP id x2mr6609319wrd.266.1510995509149; Sat, 18 Nov 2017 00:58:29 -0800 (PST) MIME-Version: 1.0 Received: by 10.28.213.131 with HTTP; Sat, 18 Nov 2017 00:58:28 -0800 (PST) In-Reply-To: References: From: Adrian Chadd Date: Sat, 18 Nov 2017 00:58:28 -0800 Message-ID: Subject: Re: iwn crashing on 11n network To: Zhihao Yuan Cc: "freebsd-wireless@freebsd.org" , FreeBSD-STABLE Mailing List Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.25 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, 18 Nov 2017 08:58:32 -0000 hi, I'm busy and there isn't a specific maintainer! Bug me in a couple days; we need to figure out how to enable the right command to enable debugging the firmware messages. Hopefully we can narrow down which firmware message its erroring out on! -a From owner-freebsd-wireless@freebsd.org Sat Nov 18 23:47:28 2017 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D468EDDFC89 for ; Sat, 18 Nov 2017 23:47:28 +0000 (UTC) (envelope-from s3erios@gmail.com) Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 567E5227E for ; Sat, 18 Nov 2017 23:47:28 +0000 (UTC) (envelope-from s3erios@gmail.com) Received: by mail-lf0-x229.google.com with SMTP id e143so6348853lfg.12 for ; Sat, 18 Nov 2017 15:47:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:subject:references:date:cc:mime-version :content-transfer-encoding:from:message-id:in-reply-to:user-agent; bh=PlSm4uwhFgFaMST8HJK7XkZ9F8vcDhbFpCmxQ6qlvPU=; b=UTJM6690h4Dl26mLQvVJz3twcviE3941iRAtRUNekCZCKTrKSRQsBRhKl3gwYhnz6G wz+SqOmBNdl4cmNl7rQxrqfVqlwWzaKVud2vqsr/uq3SRpYdV+EWRnzUb0EbTQBikwDr EUTQn4qgwRrZGP/q79vtx6mzFdVhEGswCyYoRrrvKRYGX9t9VgVwViENsXfqgjG6WGAZ MjfH4cm9gFcVHpjj6xiRvrzk0ayd7PbPNRyvyUmMtw7arqjSRieVUtW0PHSLHU6v6VYz hCGjIp3FieQbWnl2IRQGLt4JdzDbSWYFPs71nmR84M8o69LqV401EkOrk8+odE/WTNXb TFXA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:subject:references:date:cc:mime-version :content-transfer-encoding:from:message-id:in-reply-to:user-agent; bh=PlSm4uwhFgFaMST8HJK7XkZ9F8vcDhbFpCmxQ6qlvPU=; b=X6apXoToM8YiMpm0tl9CGJONVGxrdwOVTiJKqE6zrcFVu+98cbKPfQmGUApV9Ls8bw DmnDh8FQchlWiq9zm4PetV7XR5n3ALTjBoR/k+UBvYyA+B0hA7B/E4gKFnDjticl9U/2 059+owo9n9Yz1exKFGgSynE2TC172AXkGGa9VGvq8rpT0RL2PJuvO2hnQgWnJQ3/pSOs eyF0iQoqbXygtiWgwQa0EaDXoidPav000ATTvg1c5Lh091czF8b3uYZvovIc0E2EBx3c QgWXX+Jnt7x4pZuIPyFf9eTU41MgMEpVC0nav6zd7wUfHlhHaZozDOYLU4rnYZrg7CzD q2Jg== X-Gm-Message-State: AJaThX7KPCSRuJZ+GZSH2/r7uvoFOGwzb+rHyvHFFM/I6W3pm85cn8fl EZXhF+2rAbCZgwE5XJd19AA= X-Google-Smtp-Source: AGs4zMbAY4BGhHCy0u63xiAQRv09e08J4rbFS41VKsWh8E+sb0bzeC0xg7BXD2VSuGFf1LTWpubI+Q== X-Received: by 10.46.41.212 with SMTP id p81mr2407299ljp.173.1511048846032; Sat, 18 Nov 2017 15:47:26 -0800 (PST) Received: from localhost (46-133-109-44.dialup.umc.net.ua. [46.133.109.44]) by smtp.gmail.com with ESMTPSA id 2sm1693910lju.17.2017.11.18.15.47.24 (version=TLS1 cipher=AES128-SHA bits=128/128); Sat, 18 Nov 2017 15:47:25 -0800 (PST) Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "Farhan Khan" Subject: Re: rtwn card not delivering interrupts from beacon frames References: <80883a0a-5ca3-0492-d10d-ceeb3fd41b4b@gmail.com> Date: Sun, 19 Nov 2017 01:43:51 +0200 Cc: freebsd-wireless@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Andriy Voskoboinyk" Message-ID: In-Reply-To: <80883a0a-5ca3-0492-d10d-ceeb3fd41b4b@gmail.com> User-Agent: Opera Mail/12.15 (FreeBSD) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.25 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, 18 Nov 2017 23:47:28 -0000 Hi, For correct work pc_enable_intr / sc_start_xfers need to be adapted too; also, there may be need to utilize R88E_HIMRE / R88E_HISRE registers in addition to R88E_HIMR / R88E_HISR pair (see '8188 IMR/ISR bits' section in include/hal_com_reg.h in the vendor driver). > Hi all, > > As discussed, I am working on the rtwn rtl8188ee driver. Per Adrian's > advice, I am focusing on having the card reading beacon frames. I am > running the following tcpdump line, which works on another machine with > an rtwn card. > > # tcpdump -y IEEE802_11_RADIO -i wlan0 -e -s 256 type mgt > > Unfortunately, my card still does not receive beacon frames. Per IRC > conversations, this information is delivered to the driver via an > interrupt. > > I retracted my sc_init_intr code and found that the interrupt register > was incorrectly set, so I updated them per the Linux driver and started > having sc_classify_intr trigger very slowly (1-2 a minute), rather than > with every beacon frame from a nearby Access Point. The 'status' was set > to 0xffffffff, so it immediately exited. > > What might this mean? > > I am stuck and not certain why I am not receiving more beacon frames. I > have retraced the code, but am not finding what I might have left out. > Any ideas? I can show code if requested. Been on this driver for a > little more than a year now and would like to start making progress. :/ > > Thank you, > Farhan > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to > "freebsd-wireless-unsubscribe@freebsd.org"