From owner-freebsd-wireless@FreeBSD.ORG Sun Dec 2 06:35:13 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CC99E74B for ; Sun, 2 Dec 2012 06:35:13 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 5BEF88FC13 for ; Sun, 2 Dec 2012 06:35:12 +0000 (UTC) Received: by mail-we0-f182.google.com with SMTP id u54so784725wey.13 for ; Sat, 01 Dec 2012 22:35:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=b4tRBbL4734jRdCrtRITVwaNxqdSqmRaYu8TsI/FcTk=; b=09FKSNwdm4mS43hqNgKhqWnqPJAiNwJN6mm6MO+HduZ8+OPo0VOAd4omMP1RJf80oK CwmTSdd7DowupJuuXOZLlLuNv+GJdyiKGPqkK62KSRQ9HA5Hgv7a0RckKNu+oFNFAzsH UqmasNWoY0jqocer3Wi5G3Z1v1M9iJdiHHURI4kyjPh+z0VD0+FYHK4hsDHUnR/+0I0j hbQFAd+UHgNFb3fq8kIMeYSDTLwKsd1pS5KtzTOpB1s834sG7RQXkvXLu7/wR5jcQ5Yv 5r+ZJh2fIMwRdzJsXNQFH5UX+Pygm8YdR37VwrukdmwcLdVIRztZiqGxwAhxKlK7D8Fy Hwfw== MIME-Version: 1.0 Received: by 10.216.139.140 with SMTP id c12mr2216387wej.46.1354430105368; Sat, 01 Dec 2012 22:35:05 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Sat, 1 Dec 2012 22:35:05 -0800 (PST) In-Reply-To: <50BA2ACA.5080400@queue.to> References: <50BA2ACA.5080400@queue.to> Date: Sat, 1 Dec 2012 22:35:05 -0800 X-Google-Sender-Auth: Fj25pihOugds5lE_KndVR5rAYtY Message-ID: Subject: Re: Please test - collapsing the TX locking down to ATH_TX_LOCK() From: Adrian Chadd To: Howard Goldstein Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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, 02 Dec 2012 06:35:13 -0000 On 1 December 2012 08:05, Howard Goldstein wrote: > I've been beating the patched head up on an Asus EEE 701 notebook for > the better part of a day without any issues. Looks great > The 701 identifies as an AR2425/5424 ("Swan") Thanks Howard Thanks! Adrian From owner-freebsd-wireless@FreeBSD.ORG Sun Dec 2 06:37:45 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AE8F17F4 for ; Sun, 2 Dec 2012 06:37:45 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com [209.85.212.174]) by mx1.freebsd.org (Postfix) with ESMTP id 357918FC08 for ; Sun, 2 Dec 2012 06:37:44 +0000 (UTC) Received: by mail-wi0-f174.google.com with SMTP id hm9so480356wib.13 for ; Sat, 01 Dec 2012 22:37:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=gzi70b9NH0Da3RlI3oF+jmYxy7HWOXn4q4IW59VCvi4=; b=KAvXWXSzqSgUrziLmpYTU3ifCXJ50iSMyacZ/+GeLXZGB2z8dIKcl0EMkhOMaWqe9N J0VFjyqqZVkG0nN1JDamRb4cHfgBWIhxfIuMZRYCUbwnCQZF6H1qA3A/nnetcqHfTRaM N3z6makkr696e4L7+Mg2lYwJPLxn3bqdJid4g27IYPueP7pEuoYxtXT4nmKBgxzXIZUh Jr/kwh9jFYzT5xbnItWeFFYPkfFdOQOs5+xwQ7l0/rZl0dHDHStwQSyqnCXcgrASmrT2 6w72QqOgqOn0zmVhzYfEH9n0XAatn3hpvePgdOxVXiTGzUQGYEK8cktDBfk7EPiwlRn1 Eujw== MIME-Version: 1.0 Received: by 10.180.103.106 with SMTP id fv10mr4301113wib.19.1354430264037; Sat, 01 Dec 2012 22:37:44 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Sat, 1 Dec 2012 22:37:43 -0800 (PST) In-Reply-To: References: Date: Sat, 1 Dec 2012 22:37:43 -0800 X-Google-Sender-Auth: niUumlF9kGSpsi5iYx2XY49ZYCo Message-ID: Subject: Re: Please test - collapsing the TX locking down to ATH_TX_LOCK() From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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, 02 Dec 2012 06:37:45 -0000 Hi, I've committed the patch, with an extra bugfix (recursive locking, eek.) I'm now going to go through and begin un-doing the couple of LORs I know will occur when ieee80211_free_node() is called whilst the TX lock is held. Please update to -HEAD and test thoroughly with WITNESS enabled. I'm going to make a big push now to simplify a lot of the locking in the TX path so I can squeeze some more TX performance out of the code. Thanks, Adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Dec 3 05:03:50 2012 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DCCFB826; Mon, 3 Dec 2012 05:03:50 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id AA2D08FC16; Mon, 3 Dec 2012 05:03:50 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id qB353o8P003006; Mon, 3 Dec 2012 05:03:50 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qB353olB003002; Mon, 3 Dec 2012 05:03:50 GMT (envelope-from linimon) Date: Mon, 3 Dec 2012 05:03:50 GMT Message-Id: <201212030503.qB353olB003002@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/173917: [iwn] wpa-supplicant issues on iwn X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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, 03 Dec 2012 05:03:50 -0000 Old Synopsis: wpa-supplicant issues on iwn New Synopsis: [iwn] wpa-supplicant issues on iwn Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Mon Dec 3 05:03:26 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=173917 From owner-freebsd-wireless@FreeBSD.ORG Mon Dec 3 08:26:14 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BD39B5FA for ; Mon, 3 Dec 2012 08:26:14 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 4C7958FC14 for ; Mon, 3 Dec 2012 08:26:13 +0000 (UTC) Received: by mail-we0-f182.google.com with SMTP id u54so1188067wey.13 for ; Mon, 03 Dec 2012 00:26:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=mdg7Mk40NxOsaW+ye1ELsQkDVeOrqE9p0ur8/GDC/xA=; b=Y1W0uEbvnypxSUo21/8JvitkmYEAFHIhnBax4UeENUGDJG3M5/CE99yyXp8Ei6kD31 OqkNNwuVjZCZxaCsJp69nWKWYM1oCdgOMcUYRoOVY20IYSSuwyA16FE2d647Dq/ki39/ /Ps68Z3lY0orw0EE0KZV7pfxnFFRjyrTCsahwyezRv6cRH0KjVOsD2qEesJ9/cWbR9fc k5JZ7Y9GV2uBzqnggk5f/3waGorNsROGMSrsyxgzYIkYGPKwmUK2Gv2PEa9dBO1hqV7G nCRSfvlGa3WHkI6NmIf4uxb/ijyYEiJl2NiuJDVbmJ1QiB6AWY1CN8ER96pd3ZUPhSs4 cYCA== MIME-Version: 1.0 Received: by 10.216.139.140 with SMTP id c12mr3199439wej.46.1354523166722; Mon, 03 Dec 2012 00:26:06 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Mon, 3 Dec 2012 00:26:06 -0800 (PST) In-Reply-To: <188790082.20121202234216@takeda.tk> References: <188790082.20121202234216@takeda.tk> Date: Mon, 3 Dec 2012 00:26:06 -0800 X-Google-Sender-Auth: oN3IeRgLj0iop8aDZXR5o-Vm2QI Message-ID: Subject: Re: Problem with Atheros card, regression? Layer 8 problem? From: Adrian Chadd To: Derek Kulinski Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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, 03 Dec 2012 08:26:14 -0000 Hi, If it's not recognising the card then it's either a whacky PCI bus code problem, or the device is just plainly not being seen by the motherboard or BIOS. Can you try booting Linux and see if it sees the PCI device? Adrian On 2 December 2012 23:42, Derek Kulinski wrote: > Hello Adrian, > > I'm having some issues with a NIC card that worked fine in another > FreeBSD box (very old hardware - Celeron 366MHz :) that was running > version 8. > > The box died, and I decided to just move the card to recent machine > (running FreeBSD 9.1 RC3). > > Unfortunately the machine does not recognize the card, I asked on the > forum, and person trying to help me thinks that perhaps it is a bug: > > http://forums.freebsd.org/showthread.php?t=36099 > > I thought initially that I couldn't see the card even in pciconf, but > seems like the card probably is: > > none3@pci0:4:0:0: class=0x020000 card=0x3a131186 chip=0x00130000 rev=0x01 hdr=0x00 > class = network > subclass = ethernet > cap 01[44] = powerspec 2 supports D0 D3 current D0 > > I tried to follow his advice and changed value of AR5212_DEVID to > 0x0000 but that did not seem to do anything (I recompiled if_ath and > if_ath_pci). > > So I went further and modified ar5212Probe() > and put a printf() statement there (as a first instruction). > Unfortunately it doesn't look that the statement was ever called, or > at least I did not see anything in the logs. > > I decided to not file PR because there is still a possibility I might > be doing something wrong. I configured that old machine a while ago > and I no longer have access to it's contents :/ > > The old machine was running i386 kernel, the new one is running amd64. > The new one has Gigabyte GA-H77-DS3H motherboard and the NIC in > question is D-Link, I belive DWL-G520. > -- > Best regards, > Derek mailto:takeda@takeda.tk > > -- I can see clearly now, the brain is gone... > From owner-freebsd-wireless@FreeBSD.ORG Mon Dec 3 11:06:55 2012 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 15278108 for ; Mon, 3 Dec 2012 11:06:55 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id EDC608FC16 for ; Mon, 3 Dec 2012 11:06:54 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id qB3B6sbD027763 for ; Mon, 3 Dec 2012 11:06:54 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qB3B6stQ027761 for freebsd-wireless@FreeBSD.org; Mon, 3 Dec 2012 11:06:54 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 3 Dec 2012 11:06:54 GMT Message-Id: <201212031106.qB3B6stQ027761@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.14 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, 03 Dec 2012 11:06:55 -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/173917 wireless [iwn] wpa-supplicant issues on iwn 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/170904 wireless [ath] ath driver: configure related parameters when ra 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/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/164499 wireless [wi] [patch] if_wi needs fix for big endian architectu o kern/164382 wireless [ath] crash when down/deleting a vap - inside ieee8021 o kern/164365 wireless [iwi] iwi0: UP/DOWN in o bin/164102 wireless hostapd not configured for 802.11n o kern/163759 wireless [ath] ath(4) "stops working" in hostap mode o kern/163724 wireless [mwl] [patch] NULL check before dereference o kern/163719 wireless [ath] ath interface do not receive multicast o kern/163689 wireless [ath] TX timeouts when sending probe/mgmt frames durin o kern/163574 wireless [net80211] overly-frequent HT occupancy changes o kern/163573 wireless [ath] hostap mode TX buffer hang o kern/163559 wireless [ath] kernel panic AH_DEBUG o kern/163318 wireless [ath] ath(4) stops working p kern/163312 wireless [panic] [ath driver] kernel panic: page fault with ath o kern/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 p bin/137484 wireless [patch] Integer overflow in wpa_supplicant(8) base64 e o kern/136943 wireless [wpi] [lor] wpi0_com_lock / wpi0 o kern/136836 wireless [ath] atheros card stops functioning after about 12 ho o kern/132722 wireless [ath] Wifi ath0 associates fine with AP, but DHCP or I o bin/131549 wireless ifconfig(8) can't clear 'monitor' mode on the wireless o kern/126475 wireless [ath] [panic] ath pcmcia card inevitably panics under o kern/125721 wireless [ath] Terrible throughput/high ping latency with Ubiqu o kern/125617 wireless [ath] [panic] ath(4) related panic o kern/125501 wireless [ath] atheros cardbus driver hangs o kern/125332 wireless [ath] [panic] crash under any non-tiny networking unde o kern/124767 wireless [iwi] Wireless connection using iwi0 driver (Intel 220 o kern/124753 wireless [ieee80211] net80211 discards power-save queue packets o 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 138 problems total. From owner-freebsd-wireless@FreeBSD.ORG Mon Dec 3 17:28:32 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 65D39DD2; Mon, 3 Dec 2012 17:28:32 +0000 (UTC) (envelope-from takeda@takeda.tk) Received: from chinatsu.takeda.tk (mail.takeda.tk [74.0.89.210]) by mx1.freebsd.org (Postfix) with ESMTP id 185008FC16; Mon, 3 Dec 2012 17:28:31 +0000 (UTC) Received: from takeda-ws2.lan (takeda-ws2.lan [10.0.0.123]) (authenticated bits=0) by chinatsu.takeda.tk (8.14.5/8.14.5) with ESMTP id qB3HSUPN017760 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Mon, 3 Dec 2012 09:28:31 -0800 (PST) (envelope-from takeda@takeda.tk) Date: Mon, 3 Dec 2012 09:28:29 -0800 From: Derek Kulinski X-Priority: 3 (Normal) Message-ID: <1942047897.20121203092829@takeda.tk> To: Adrian Chadd Subject: Re: Problem with Atheros card, regression? Layer 8 problem? In-Reply-To: References: <188790082.20121202234216@takeda.tk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.97.6 at chinatsu.takeda.tk X-Virus-Status: Clean Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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, 03 Dec 2012 17:28:32 -0000 Hello Adrian, That could take a while... Ok I'll try to put a linux on USB and try to boot from it and will let you know. Thanks, Derek Monday, December 3, 2012, 12:26:06 AM, you wrote: > Hi, > If it's not recognising the card then it's either a whacky PCI bus > code problem, or the device is just plainly not being seen by the > motherboard or BIOS. > Can you try booting Linux and see if it sees the PCI device? > Adrian > On 2 December 2012 23:42, Derek Kulinski wrote: >> Hello Adrian, >> >> I'm having some issues with a NIC card that worked fine in another >> FreeBSD box (very old hardware - Celeron 366MHz :) that was running >> version 8. >> >> The box died, and I decided to just move the card to recent machine >> (running FreeBSD 9.1 RC3). >> >> Unfortunately the machine does not recognize the card, I asked on the >> forum, and person trying to help me thinks that perhaps it is a bug: >> >> http://forums.freebsd.org/showthread.php?t=36099 >> >> I thought initially that I couldn't see the card even in pciconf, but >> seems like the card probably is: >> >> none3@pci0:4:0:0: class=0x020000 card=0x3a131186 chip=0x00130000 rev=0x01 hdr=0x00 >> class = network >> subclass = ethernet >> cap 01[44] = powerspec 2 supports D0 D3 current D0 >> >> I tried to follow his advice and changed value of AR5212_DEVID to >> 0x0000 but that did not seem to do anything (I recompiled if_ath and >> if_ath_pci). >> >> So I went further and modified ar5212Probe() >> and put a printf() statement there (as a first instruction). >> Unfortunately it doesn't look that the statement was ever called, or >> at least I did not see anything in the logs. >> >> I decided to not file PR because there is still a possibility I might >> be doing something wrong. I configured that old machine a while ago >> and I no longer have access to it's contents :/ >> >> The old machine was running i386 kernel, the new one is running amd64. >> The new one has Gigabyte GA-H77-DS3H motherboard and the NIC in >> question is D-Link, I belive DWL-G520. >> -- >> Best regards, >> Derek mailto:takeda@takeda.tk >> >> -- I can see clearly now, the brain is gone... >> -- Best regards, Derek mailto:takeda@takeda.tk If you have a procedure with ten parameters, you probably missed some. -- Alan J. Perlis From owner-freebsd-wireless@FreeBSD.ORG Tue Dec 4 01:31:45 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6FDCBD6C for ; Tue, 4 Dec 2012 01:31:45 +0000 (UTC) (envelope-from prvs=1685a61a7f=evendas@krazer.com.br) Received: from krazer.com.br (usaimport.com.br [74.208.147.131]) by mx1.freebsd.org (Postfix) with ESMTP id 30EED8FC39 for ; Tue, 4 Dec 2012 01:31:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=krazer.com.br; s=MDaemon; t=1354583465; x=1355188265; q=dns/txt; h=DomainKey-Signature: Received:From:To:Subject:Date:MIME-Version:Content-Type: Message-ID; bh=/AGF6JRzB/J7iTsWt8UkF/2jJ0/KNRujXWNnXTa6qHA=; b=U L7uUeWjI0KxG1Q4aQznpd0yZrj0Wr0ezLdBPVw8GHUWid/V2U0aYzl5Qt4QxFio9 Sz4UViBCQ3nKeGdZDYFMYt8bsVKZPNIM2tlu61cOMU3Guu93zN6C2WWoLb8R4itX ECwKFwWQd34jLU36qCYi8gg4EZAOXVOCmOetLfSjp4= DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=krazer.com.br; c=simple; q=dns; h=from:message-id; b=rgDwZp9K+ji6kKzZRGUHXximkvU5LIzaEm8uWKxyMOsv3zKAWWSpmkOL5axh 4naMTElo26aGir6rGOQrybUdUaoJiOYA0hK6bSf6w77pfWHuGV+lp75Zk AduSY5Xq8PpkX3HdfMnLu89TaP+6gilR1qM3AJ1IwhrY66HjPNHBbw=; X-MDAV-Processed: allearth.com.br, Mon, 03 Dec 2012 23:11:05 -0200 Received: from krazer by allearth.com.br (MDaemon PRO v11.0.0) with ESMTP id md50003170669.msg for ; Mon, 03 Dec 2012 23:11:05 -0200 X-Spam-Processed: allearth.com.br, Mon, 03 Dec 2012 23:11:05 -0200 (not processed: message from trusted or authenticated source) X-Authenticated-Sender: evendas@krazer.com.br X-MDRemoteIP: 74.208.167.75 X-Return-Path: prvs=1685a61a7f=evendas@krazer.com.br X-Envelope-From: evendas@krazer.com.br X-MDaemon-Deliver-To: freebsd-wireless@freebsd.org From: "Vendas Krazer Technologies" To: Subject: =?utf-8?B?Tm92YSBDUEUgS3JhemVyIFNreSBTdGF0aW9uIDVHSHo=?= =?utf-8?B?IE4gLSBDUEUgQW50ZW5hIEludGVncmFkYSBkZSAxOGRCaQ==?= =?utf-8?B?IGUgQ29tIFNhw61kYSBwYXJhIEFudGVuYSBFeHRlcm5h?= Date: Mon, 03 Dec 2012 22:08:18 -0200 MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=45652905_3502_4801_0078_850943129657" Message-ID: X-Mailer: Clientes Krazer X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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, 04 Dec 2012 01:31:45 -0000 This is a multi-part message in MIME format. ------=45652905_3502_4801_0078_850943129657 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Lan=C3=A7amento CPE Krazer Sky Station 5GHz N Voc=C3=AA cliente pediu que a Krazer fizesse uma nova CPE num formato mais = estiloso, pequena, de menor tamanho e que tivesse novas funcionabilidade, m= ais especificamente acesso f=C3=A1cil ao bot=C3=A3o de reset, prote=C3=A7= =C3=A3o contra queima e a t=C3=A3o desejada SA=C3=8DDA PARA ANTENA EXTERNA!= !! R$ 179.90 Antena Integrada de 18dBi 60=C2=BA Duas Portas de Rede Lan e Wan PA Real de 630mW e LNA Ultra Ganho PoE Passivo com Prote=C3=A7=C3=A3o Dupla de 12 a 24V Fonte Chaveada 12V Full Range 110 a 220V Exclusiva Sa=C3=ADda para Antena Externa Homologa=C3=A7=C3=A3o Anatel 0269-11-5280 Instala=C3=A7=C3=A3o R=C3=A1pida e Simples. Software Amigavel e em Portugu=C3=AAs! Suporte a PPPoE Wisp Cliente! Controle de Banda! Excelente sinal de recep=C3=A7=C3=A3o! Longa Dist=C3=A2ncia! Fa=C3=A7a um teste em sua rede e compare com os concorrentes, muito mais si= nal que UBNT, muito mais dados, transmiss=C3=A3o de quase 90Mbps TCP/IP con= tinuamente! Lat=C3=AAncia de rede de 1 a 5 ms com carga completa! Contate-nos Val Campos // Carla Maria // Eder Roberto Email / MSN: vendas@allearth.com.br Vendas / SAC (19) 3256-5557 (19) 3245-0708 www.krazer.com.br Envio de Email n=C3=A3o autorizado =C3=A9 crime, n=C3=A3o seja o vil=C3=A3o= da hist=C3=B3ria! Email =C3=A9 protegido sobre sigilo fiscal e federal. Le= i Federal Brasil. ------=45652905_3502_4801_0078_850943129657-- From owner-freebsd-wireless@FreeBSD.ORG Tue Dec 4 06:27:08 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 39E91AD1; Tue, 4 Dec 2012 06:27:08 +0000 (UTC) (envelope-from takeda@takeda.tk) Received: from chinatsu.takeda.tk (mail.takeda.tk [74.0.89.210]) by mx1.freebsd.org (Postfix) with ESMTP id F2AAE8FC0C; Tue, 4 Dec 2012 06:27:06 +0000 (UTC) Received: from takeda-ws2.lan (takeda-ws2.lan [10.0.0.123]) (authenticated bits=0) by chinatsu.takeda.tk (8.14.5/8.14.5) with ESMTP id qB46R6RF002441 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Mon, 3 Dec 2012 22:27:06 -0800 (PST) (envelope-from takeda@takeda.tk) Date: Mon, 3 Dec 2012 22:20:02 -0800 From: Derek Kulinski X-Priority: 3 (Normal) Message-ID: <978297250.20121203222002@takeda.tk> To: Adrian Chadd Subject: Re: Problem with Atheros card, regression? Layer 8 problem? In-Reply-To: References: <188790082.20121202234216@takeda.tk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.97.6 at chinatsu.takeda.tk X-Virus-Status: Clean Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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, 04 Dec 2012 06:27:08 -0000 Hello Adrian, So I figured the problem out. This is how it went. I booted OpenSuSE and couldn't find the device as well... At that point I was sure that the problem is with my PC. I decided to install the card in a PC that is running Windows. After start it recognized new hardware but I did not have drivers, looking at hardware information it showed correct values. I then put back the card to the FreeBSD machine and started SuSE. The card became correctly recognized by Linux, I booted FreeBSD and the card was no longer visible (though this time devid value was correct), switched to Linux and Linux did not see it as well. At that point I took isopropyl alcohol and cleaned the connection, plugged it back and FreeBSD is seeing it now. That card was in that old PC for many years, so probably the connection oxidized (or maybe just dirt built up - I'm no chemist). In any case it looks like it was a layer 8 problem after all. I'm sorry for bugging you. Thanks, Derek Monday, December 3, 2012, 12:26:06 AM, you wrote: > Hi, > If it's not recognising the card then it's either a whacky PCI bus > code problem, or the device is just plainly not being seen by the > motherboard or BIOS. > Can you try booting Linux and see if it sees the PCI device? > Adrian > On 2 December 2012 23:42, Derek Kulinski wrote: >> Hello Adrian, >> >> I'm having some issues with a NIC card that worked fine in another >> FreeBSD box (very old hardware - Celeron 366MHz :) that was running >> version 8. >> >> The box died, and I decided to just move the card to recent machine >> (running FreeBSD 9.1 RC3). >> >> Unfortunately the machine does not recognize the card, I asked on the >> forum, and person trying to help me thinks that perhaps it is a bug: >> >> http://forums.freebsd.org/showthread.php?t=36099 >> >> I thought initially that I couldn't see the card even in pciconf, but >> seems like the card probably is: >> >> none3@pci0:4:0:0: class=0x020000 card=0x3a131186 chip=0x00130000 rev=0x01 hdr=0x00 >> class = network >> subclass = ethernet >> cap 01[44] = powerspec 2 supports D0 D3 current D0 >> >> I tried to follow his advice and changed value of AR5212_DEVID to >> 0x0000 but that did not seem to do anything (I recompiled if_ath and >> if_ath_pci). >> >> So I went further and modified ar5212Probe() >> and put a printf() statement there (as a first instruction). >> Unfortunately it doesn't look that the statement was ever called, or >> at least I did not see anything in the logs. >> >> I decided to not file PR because there is still a possibility I might >> be doing something wrong. I configured that old machine a while ago >> and I no longer have access to it's contents :/ >> >> The old machine was running i386 kernel, the new one is running amd64. >> The new one has Gigabyte GA-H77-DS3H motherboard and the NIC in >> question is D-Link, I belive DWL-G520. >> -- >> Best regards, >> Derek mailto:takeda@takeda.tk >> >> -- I can see clearly now, the brain is gone... >> -- Best regards, Derek mailto:takeda@takeda.tk What happens if you get scared half to death twice? From owner-freebsd-wireless@FreeBSD.ORG Tue Dec 4 07:51:12 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E942DF90 for ; Tue, 4 Dec 2012 07:51:12 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 728538FC13 for ; Tue, 4 Dec 2012 07:51:12 +0000 (UTC) Received: by mail-we0-f182.google.com with SMTP id u54so1788570wey.13 for ; Mon, 03 Dec 2012 23:51:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=ty2TKVkz3zL7Lx/9tl9qvxR6iZfawgttesd/0Odcydc=; b=fwBTGJzgBC589fZvY6QP07byMsZSmiDmIEplZG4AkXIIFCtMWhUQbVGxkFuogDYgJc wn+kode5FvO1ILe3AV+OdQu5p90KaLLvMfUpodO+DCa7wCPyLBhVr4ccZov6byxqfkk/ 6v54iEYcPVcBoE0hEP+r5HwDNhxlAzkWwFNw3oF3RDpm3VLNEs2Z3KcrqU2VfJEGmUeN evmKbO/60nHArAKrD8nUeSncGEACarWwMmziYdbgSqiXZcmBp/XpI7BSs3MDiUQNc2tU TEUBnlXEgU/gZ7NGUieCTju1ii5O3CuPZ8+LgyZ6kzs1NM/RRpDFhXoKbLZvxvnsDSeO YFDw== MIME-Version: 1.0 Received: by 10.180.88.71 with SMTP id be7mr2559291wib.17.1354607471132; Mon, 03 Dec 2012 23:51:11 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Mon, 3 Dec 2012 23:51:10 -0800 (PST) In-Reply-To: <978297250.20121203222002@takeda.tk> References: <188790082.20121202234216@takeda.tk> <978297250.20121203222002@takeda.tk> Date: Mon, 3 Dec 2012 23:51:10 -0800 X-Google-Sender-Auth: Vx8gqU5kx56RJPgxl-OZuHvCfxU Message-ID: Subject: Re: Problem with Atheros card, regression? Layer 8 problem? From: Adrian Chadd To: Derek Kulinski Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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, 04 Dec 2012 07:51:13 -0000 That's really good to know! Thanks! Adrian On 3 December 2012 22:20, Derek Kulinski wrote: > Hello Adrian, > > So I figured the problem out. > > This is how it went. I booted OpenSuSE and couldn't find the device as > well... > > At that point I was sure that the problem is with my PC. I decided to > install the card in a PC that is running Windows. After start it > recognized new hardware but I did not have drivers, looking at > hardware information it showed correct values. > > I then put back the card to the FreeBSD machine and started SuSE. The > card became correctly recognized by Linux, I booted FreeBSD and the > card was no longer visible (though this time devid value was correct), > switched to Linux and Linux did not see it as well. At that point I > took isopropyl alcohol and cleaned the connection, plugged it back and > FreeBSD is seeing it now. > > That card was in that old PC for many years, so probably the > connection oxidized (or maybe just dirt built up - I'm no chemist). > > In any case it looks like it was a layer 8 problem after all. I'm > sorry for bugging you. > > Thanks, > Derek > > Monday, December 3, 2012, 12:26:06 AM, you wrote: > >> Hi, > >> If it's not recognising the card then it's either a whacky PCI bus >> code problem, or the device is just plainly not being seen by the >> motherboard or BIOS. > >> Can you try booting Linux and see if it sees the PCI device? > > >> Adrian > > >> On 2 December 2012 23:42, Derek Kulinski wrote: >>> Hello Adrian, >>> >>> I'm having some issues with a NIC card that worked fine in another >>> FreeBSD box (very old hardware - Celeron 366MHz :) that was running >>> version 8. >>> >>> The box died, and I decided to just move the card to recent machine >>> (running FreeBSD 9.1 RC3). >>> >>> Unfortunately the machine does not recognize the card, I asked on the >>> forum, and person trying to help me thinks that perhaps it is a bug: >>> >>> http://forums.freebsd.org/showthread.php?t=36099 >>> >>> I thought initially that I couldn't see the card even in pciconf, but >>> seems like the card probably is: >>> >>> none3@pci0:4:0:0: class=0x020000 card=0x3a131186 chip=0x00130000 rev=0x01 hdr=0x00 >>> class = network >>> subclass = ethernet >>> cap 01[44] = powerspec 2 supports D0 D3 current D0 >>> >>> I tried to follow his advice and changed value of AR5212_DEVID to >>> 0x0000 but that did not seem to do anything (I recompiled if_ath and >>> if_ath_pci). >>> >>> So I went further and modified ar5212Probe() >>> and put a printf() statement there (as a first instruction). >>> Unfortunately it doesn't look that the statement was ever called, or >>> at least I did not see anything in the logs. >>> >>> I decided to not file PR because there is still a possibility I might >>> be doing something wrong. I configured that old machine a while ago >>> and I no longer have access to it's contents :/ >>> >>> The old machine was running i386 kernel, the new one is running amd64. >>> The new one has Gigabyte GA-H77-DS3H motherboard and the NIC in >>> question is D-Link, I belive DWL-G520. >>> -- >>> Best regards, >>> Derek mailto:takeda@takeda.tk >>> >>> -- I can see clearly now, the brain is gone... >>> > > > > -- > Best regards, > Derek mailto:takeda@takeda.tk > > What happens if you get scared half to death twice? > From owner-freebsd-wireless@FreeBSD.ORG Sat Dec 8 09:24:06 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3244D218 for ; Sat, 8 Dec 2012 09:24:06 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com [209.85.212.174]) by mx1.freebsd.org (Postfix) with ESMTP id B0DEC8FC12 for ; Sat, 8 Dec 2012 09:24:05 +0000 (UTC) Received: by mail-wi0-f174.google.com with SMTP id hm9so137380wib.13 for ; Sat, 08 Dec 2012 01:24:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=xr//CNb0ZuCwYlpVftN7kUtLV0oAyKEEU0HKUl8GiYo=; b=Ob+NB8U+4IZmTQ5wn/0w8r4uhfzBMjnc4c73m2nKnqxgh8CSxWLWDQ/SywroKJ3dYu zyGfI/hQPhqKi7jb532T7ay+m7emucnY3+O3M2C0U9IMLUASmT8s8zX738tw5zA9A6tS dN5EYf0uvnPxbdE+FPI6DYrXF6+PQs8OLuYt9PMfamYLSzSXYyTe7c2eZ+V398kiLlYU X9RmT5MlDiDYaKY5agVS2AgmBkTdhDnbGHVERHKut5iFigTZGdDLDb07mWBKRC10SSjD fYlraKt8JwR4oKKU6GMpz6g/NVzTa+xjorwZWWuI99pKUk0MLicEBB1o3J8GbpgjsRPC Ogyg== MIME-Version: 1.0 Received: by 10.216.139.140 with SMTP id c12mr3328732wej.46.1354958644553; Sat, 08 Dec 2012 01:24:04 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Sat, 8 Dec 2012 01:24:04 -0800 (PST) Date: Sat, 8 Dec 2012 01:24:04 -0800 X-Google-Sender-Auth: s19I0uYLb9WWeW97yQ2IljD2AaI Message-ID: Subject: Hm, somehow the fast frames code is broken (surprise) From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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, 08 Dec 2012 09:24:06 -0000 Hi, I've started seeing panics in the fast frames code in FreeBSD-HEAD. It's quite possible this has been here a while; I've heard rumours about this dating back to last year. The reason? Because I was doing iperf tests between AR5212/AR5413/AR5414 NICs and the HAL/driver enables the fast frames support. Which was working fine (which I'm honestly shocked about!) - except that there are two rather grr-y bugs: * upon a node purge, there's a panic inside m_free() from ieee80211_ff_node_cleanup(), where it dereferences a pointer 0xdeadc0de. So there's some use-after-free nonsense going * the TX staging code panics when flushing the staging queue; it claims the staging queue is empty when it shouldn't be. The latter is likely due to r227352 - Bernhard and I shuffled the code around to make the TX AMPDU state be per-TID rather than per-AC. I may have screwed something up in the mapping and it's checking the wrong staging queue. It doesn't show up with the 802.11n NICs because they disable the fast frames HAL support. (The chips support fast frames just fine, for what it's worth.) Anyway. If you've ever seen his panic, please let me know. I'm not going to disable fast frames; I'm going to try and figure out why it's busted and then fix it up. Fast frames for legacy atheros cards speaking to an 802.11n AP is conceptually just fine. (This just resurrects my desire to extend ath_rate_sample to have a third packet 'size', for aggregates and fast frames packets..) Adrian From owner-freebsd-wireless@FreeBSD.ORG Sat Dec 8 09:47:39 2012 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5842C786; Sat, 8 Dec 2012 09:47:39 +0000 (UTC) (envelope-from adrian@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 220218FC0C; Sat, 8 Dec 2012 09:47:39 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id qB89lc7v005684; Sat, 8 Dec 2012 09:47:38 GMT (envelope-from adrian@freefall.freebsd.org) Received: (from adrian@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qB89lcGB005680; Sat, 8 Dec 2012 09:47:38 GMT (envelope-from adrian) Date: Sat, 8 Dec 2012 09:47:38 GMT Message-Id: <201212080947.qB89lcGB005680@freefall.freebsd.org> To: adrian@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: adrian@FreeBSD.org Subject: Re: kern/174273: [net80211] taking down a net80211 node with active fast frames traffic causes a panic X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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, 08 Dec 2012 09:47:39 -0000 Synopsis: [net80211] taking down a net80211 node with active fast frames traffic causes a panic Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: adrian Responsible-Changed-When: Sat Dec 8 09:47:28 UTC 2012 Responsible-Changed-Why: Shuffle! http://www.freebsd.org/cgi/query-pr.cgi?pr=174273 From owner-freebsd-wireless@FreeBSD.ORG Sat Dec 8 09:53:44 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6C5DCC11 for ; Sat, 8 Dec 2012 09:53:44 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-f52.google.com (mail-wg0-f52.google.com [74.125.82.52]) by mx1.freebsd.org (Postfix) with ESMTP id E824C8FC12 for ; Sat, 8 Dec 2012 09:53:43 +0000 (UTC) Received: by mail-wg0-f52.google.com with SMTP id 12so761009wgh.31 for ; Sat, 08 Dec 2012 01:53:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=U3xtlmc+L2tW1kbpW2ZweeL+HmpZEGkNiYb/NOWBCqo=; b=ynZmAFuOwD3qNSABsCbD4KdoRO9Fo3ck844azxd50yopEHkxgEBmbLlWAPQ8OEUETP gHzqpa0htU27O6AjVSpL43EbFaZ0+2PHk6avaSsAoYvWOEEvA5GCBVJHprZwShsUP9Y9 89JylS1YCX71ikXugUjstZsDPhAKbMwI0P1YQFTp88831VeRHV8tQGbtkdXWUZos47pT xqdqXI5YOwWazvvKHS6RMPEaBkZiLtNBPqYPtv/PEi506mlh365tPhXzizuh6fvvFepz TiBpwxTAZyJoUwooxjEjUH9SEWIPiNGyUJtJnyYoS+kO/lviAjIa9pMRKgONGft+Qsf/ k6XA== MIME-Version: 1.0 Received: by 10.180.97.137 with SMTP id ea9mr2451354wib.13.1354960422741; Sat, 08 Dec 2012 01:53:42 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Sat, 8 Dec 2012 01:53:42 -0800 (PST) In-Reply-To: References: Date: Sat, 8 Dec 2012 01:53:42 -0800 X-Google-Sender-Auth: 7aSPflCTlzKJqUWAAwI3BQ51weQ Message-ID: Subject: Re: Hm, somehow the fast frames code is broken (surprise) From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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, 08 Dec 2012 09:53:44 -0000 ... On 8 December 2012 01:24, Adrian Chadd wrote: > * upon a node purge, there's a panic inside m_free() from > ieee80211_ff_node_cleanup(), where it dereferences a pointer > 0xdeadc0de. So there's some use-after-free nonsense going ... aaand look at that, I've just fixed it in -HEAD. The second panic hasn't shown up yet but I don't believe that fixing the first panic magically made the second panic go away. In any case I'll just plod along with some further testing and see how things go. Thanks, Adrian From owner-freebsd-wireless@FreeBSD.ORG Sat Dec 8 17:49:48 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8717C58E for ; Sat, 8 Dec 2012 17:49:48 +0000 (UTC) (envelope-from gosha-necr@yandex.ru) Received: from forward3.mail.yandex.net (forward3.mail.yandex.net [IPv6:2a02:6b8:0:602::3]) by mx1.freebsd.org (Postfix) with ESMTP id 8B51C8FC08 for ; Sat, 8 Dec 2012 17:49:47 +0000 (UTC) Received: from web22d.yandex.ru (web22d.yandex.ru [77.88.46.52]) by forward3.mail.yandex.net (Yandex) with ESMTP id E0223B469D0 for ; Sat, 8 Dec 2012 21:49:45 +0400 (MSK) Received: from 127.0.0.1 (localhost.localdomain [127.0.0.1]) by web22d.yandex.ru (Yandex) with ESMTP id A977515B002D; Sat, 8 Dec 2012 21:49:45 +0400 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1354988985; bh=MIaYEJYoXxMHc1qozHO4nGD3iXYda8V1z3FJ5ovG/Wk=; h=From:To:Subject:Date; b=bypLDwCo1nNCUXvLh61IbMnoqRgxU+J7wBEf4Oj84BN2dZvM0+pl3QIPetithEyhl BVwcyYBU6j4z/Om9nvzpl0tbKTSGDz2YUKQGV3XAmBFkjVYGarpQCtVZTsM5X3vOPO TPA3i/wVjVT+/oC80yIBMIePJQt8ZHfPz3eXKmj0= Received: from mx0.manul-it.ru (mx0.manul-it.ru [92.54.86.120]) by web22d.yandex.ru with HTTP; Sat, 08 Dec 2012 21:49:45 +0400 From: =?koi8-r?B?59XM0cXXIOfP28E=?= To: freebsd-wireless@freebsd.org Subject: Need help to get working Netgear WNA-3100 USB wireless adapter Message-Id: <1358581354988985@web22d.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Sat, 08 Dec 2012 23:49:45 +0600 X-Mailman-Approved-At: Sat, 08 Dec 2012 17:59:43 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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, 08 Dec 2012 17:49:48 -0000 Good day! Since my laptop internal wireless card RT8723AE doesn't working in FreeBSD nor with ndis nor with ndisulator, I'm try to get working other wireless card getting from friend. Wireless card is Netgear WNA-3100 ( ID 0846:9020) on broadcom chipset. Since FreeBSD has not drivers for usb broadcom Wi-Fi, I'm try to use ndis and ndis from ndisulator project. And my trying nas no results :( But system not reboots immediately as with RT8723AE tryings. Additional info which I found on web for that card and maybe it helps for someone: Solution with ndiswrapper for Linux Mint 13: http://forum.linuxmint.com/viewtopic.php?f=197&t=92044 So there is info from my system: OS: FreeBSD-Current (07 Dec 2012) amd64 === lsusb Bus /dev/usb Device /dev/ugen2.3: ID 5986:0315 Acer, Inc Bus /dev/usb Device /dev/ugen1.3: ID 046d:c05f Logitech, Inc. Bus /dev/usb Device /dev/ugen0.3: ID 0bda:8723 Realtek Semiconductor Corp. Bus /dev/usb Device /dev/ugen2.2: ID 8087:0024 Bus /dev/usb Device /dev/ugen1.2: ID 8087:0024 Bus /dev/usb Device /dev/ugen0.2: ID 0846:9020 NetGear, Inc. === Output for kldload ndisgen'ed bcmwlhigh564_sys.ko: Dec 8 23:40:55 MYBSD root: Unknown USB device: vendor 0x0846 product 0x9020 bus uhub0 Dec 8 23:40:55 MYBSD kernel: no match for ExInterlockedRemoveHeadList Dec 8 23:40:55 MYBSD kernel: no match for ExInterlockedInsertTailList Dec 8 23:40:55 MYBSD kernel: no match for IoUnregisterPlugPlayNotification Dec 8 23:40:55 MYBSD root: Unknown USB device: vendor 0x5986 product 0x0315 bus uhub4 Dec 8 23:40:55 MYBSD kernel: ndis0: on usbus0 Dec 8 23:40:55 MYBSD kernel: ndis0: NDIS API version: 5.1 Dec 8 23:40:55 MYBSD kernel: ndis0: ioctl 0xffffff80 isn't supported Dec 8 23:40:55 MYBSD kernel: ndis0: ioctl 0xffffff80 isn't supported Dec 8 23:40:55 MYBSD kernel: ndis0: init handler failed Dec 8 23:40:55 MYBSD kernel: device_attach: ndis0 attach returned 6 Dec 8 23:40:55 MYBSD root: Unknown USB device: vendor 0x5986 product 0x0315 bus uhub4 -------------------------------------------- С уважением, Гуляев Гоша.