From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 31 01:12:47 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 03E777FD for ; Sun, 31 Mar 2013 01:12:47 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-yh0-x233.google.com (mail-yh0-x233.google.com [IPv6:2607:f8b0:4002:c01::233]) by mx1.freebsd.org (Postfix) with ESMTP id BED062D3 for ; Sun, 31 Mar 2013 01:12:46 +0000 (UTC) Received: by mail-yh0-f51.google.com with SMTP id q1so191406yhf.10 for ; Sat, 30 Mar 2013 18:12:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=kZnbDX/cn/nGdGas987LruCJJbqnn3NDUxTcUJQRLxc=; b=CzGzqREymU3++I77sGkFhh1fYXPxzUThFeFkaGQfZu7Mxd42jzwGaHx+x+WZTlz9l2 5OmBnR6e9E+ta8YRNJ+mSUKANiLLKSl65ubstF7xDfTIXCxgZntpUDUo12Lt6FjnxQGO INx9dMdPZKa1EHluA1v63yVapMlHqo5U6YTDJKsYtmnbttxkJxQ/nGbNjzAouZ2Nwgsm eezHjIqJvASnE8KTnihwY6lJF7NP4ryWU06Dg1ekdsnY4KLhkkoJj+bR9y4piqJayKqO PjRWax2SYTYg2MdUihqFJdIX6QgfvZH7p4qOvVyhkPcCb1SogEAy2yPpJrRffVmR4Edw 1b+A== X-Received: by 10.236.98.66 with SMTP id u42mr5003912yhf.157.1364691889886; Sat, 30 Mar 2013 18:04:49 -0700 (PDT) Received: from [192.168.1.34] (c-98-212-197-211.hsd1.il.comcast.net. [98.212.197.211]) by mx.google.com with ESMTPS id u80sm14146126yhj.5.2013.03.30.18.04.48 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 30 Mar 2013 18:04:49 -0700 (PDT) Message-ID: <51578BAC.4090608@gmail.com> Date: Sat, 30 Mar 2013 20:04:44 -0500 From: Joshua Isom User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: "freebsd-wireless@freebsd.org" Subject: ath not working after a motherboard and ram upgrade 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.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, 31 Mar 2013 01:12:47 -0000 I've been longing to upgrade my motherboard and ram, and with a tax refund it came time. The current kernel was working well enough for me, where the only ath problems were my antenna and "harmless." After upgrading, 2Gb DDR2 to 32Gb DDR3, I've yet to get ath to be stable. The only system changes were motherboard, a cheap video card, and ram. There's periods where ath will work, then packet loss grows until it's unusable. When I scan, I can find the router, and when I'm connected I get an RSSI of 10.5 after I hung the antenna over the monitor, better than before. I'm getting a lot of kernel debug logs, but when I'm looking I can't notice anything specific. I still need to dig through the logs but I probably couldn't match up the logs with what I was doing at the time. What steps should I try to figure out why a motherboard and ram change would break the networking? From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 31 06:25:44 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8ED33635 for ; Sun, 31 Mar 2013 06:25:44 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) by mx1.freebsd.org (Postfix) with ESMTP id 2A775CC9 for ; Sun, 31 Mar 2013 06:25:44 +0000 (UTC) Received: by mail-wi0-f169.google.com with SMTP id c10so1416641wiw.4 for ; Sat, 30 Mar 2013 23:25:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=IwLLeLGVy5Cb/AAYquBoPYfi3TLVXCp+U1LClvWhtrY=; b=ndi8WICg/sW3gEWb6jiJ/VCUyd1mIYHdPXJb2sd1DJR/aobFEgQzwsEmfNIfdkKgF9 32Trl15hHMgHCvl7mSPMy6yUFqUHD03fbwByBPycu6fPrhQu35hYF7+EclLO5O0nKGYN RW61eFWxC3yvIwTRepY3yRQud8jcfvHHDK/Vz27DhMuybcwKQRyuMd8cX0H1kCmfpZMq JmR5lDq6cTvWBbYlRe6E/US6xhbY5/U9qyozZR8VHgttJSqGWvafhuq6IYZA8f9svM+M MKpO0Zz7MTrtkxu5un9IDw/Eml0A5FAdTfl05sFXrQQ5u5FCwPTSmDNSubbt6i6jcdIo 6cUQ== MIME-Version: 1.0 X-Received: by 10.180.189.205 with SMTP id gk13mr4851550wic.25.1364711143186; Sat, 30 Mar 2013 23:25:43 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.108.130 with HTTP; Sat, 30 Mar 2013 23:25:42 -0700 (PDT) In-Reply-To: <51578BAC.4090608@gmail.com> References: <51578BAC.4090608@gmail.com> Date: Sat, 30 Mar 2013 23:25:42 -0700 X-Google-Sender-Auth: LQDK80FeUR1xm-TwC4EwRCTtjsA Message-ID: Subject: Re: ath not working after a motherboard and ram upgrade From: Adrian Chadd To: Joshua Isom 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, 31 Mar 2013 06:25:44 -0000 does downgrading the motherboard/ram fix it? You were already running 64 bit, right? What if you just boot with 2gb of ram? adrian On 30 March 2013 18:04, Joshua Isom wrote: > I've been longing to upgrade my motherboard and ram, and with a tax refund > it came time. The current kernel was working well enough for me, where the > only ath problems were my antenna and "harmless." After upgrading, 2Gb DDR2 > to 32Gb DDR3, I've yet to get ath to be stable. The only system changes > were motherboard, a cheap video card, and ram. There's periods where ath > will work, then packet loss grows until it's unusable. When I scan, I can > find the router, and when I'm connected I get an RSSI of 10.5 after I hung > the antenna over the monitor, better than before. I'm getting a lot of > kernel debug logs, but when I'm looking I can't notice anything specific. I > still need to dig through the logs but I probably couldn't match up the logs > with what I was doing at the time. > > What steps should I try to figure out why a motherboard and ram change would > break the networking? > _______________________________________________ > 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 Sun Mar 31 12:35:15 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id AE28DEE3; Sun, 31 Mar 2013 12:35:15 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-gh0-f175.google.com (mail-gh0-f175.google.com [209.85.160.175]) by mx1.freebsd.org (Postfix) with ESMTP id 65CE1AB5; Sun, 31 Mar 2013 12:35:15 +0000 (UTC) Received: by mail-gh0-f175.google.com with SMTP id f1so245190ghb.20 for ; Sun, 31 Mar 2013 05:35:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=s90HMHXUMX8vvsw/3tH0iP403eDjHVvL0MxaMIBDtYY=; b=dV16HUCTOpSvRi8Sog1fycBz3pJaj/vEqZRkS85u7N73sHO77AxARXuu4gIOE3ABbV WqzQd35V95zyS2PNz1Yp4kMYjwXarXnvlfMXLd76UCwfNYyNEbNoSXewYiC9/7FZhjlV WA9SaJmN9YtziYaC2CR7s7529/5HhNA7y/Mc4qUa1h4O7c3GxAQGdwRh+FfA9pj3vi5N OEXjdRMPpsfqFNigNkccey+fkkCPa7prJhFfHh35lOPA5mXFW4JwAGVenBbkECKwBXJI 1jHNVaPVBW9vJuHaLFZsOhEuoGM06iH9U0GHYIgOFax4cc1Cceg+7gK3owhMNlXH2cj7 QfvQ== X-Received: by 10.236.26.203 with SMTP id c51mr6254477yha.89.1364733309768; Sun, 31 Mar 2013 05:35:09 -0700 (PDT) Received: from [192.168.1.34] (c-98-212-197-211.hsd1.il.comcast.net. [98.212.197.211]) by mx.google.com with ESMTPS id w69sm18130883yhe.4.2013.03.31.05.35.08 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 31 Mar 2013 05:35:09 -0700 (PDT) Message-ID: <51582D78.1070100@gmail.com> Date: Sun, 31 Mar 2013 07:35:04 -0500 From: Joshua Isom User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: ath not working after a motherboard and ram upgrade References: <51578BAC.4090608@gmail.com> <515826B9.6070509@gmail.com> In-Reply-To: <515826B9.6070509@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.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, 31 Mar 2013 12:35:15 -0000 I spoke too soon, it can still degrade, it's just takes longer to happen. This is with `ping -i .25 192.168.1.1` > 64 bytes from 192.168.1.1: icmp_seq=743 ttl=64 time=1.595 ms > 64 bytes from 192.168.1.1: icmp_seq=765 ttl=64 time=1.696 ms > 64 bytes from 192.168.1.1: icmp_seq=771 ttl=64 time=3.118 ms > 64 bytes from 192.168.1.1: icmp_seq=772 ttl=64 time=1.573 ms > 64 bytes from 192.168.1.1: icmp_seq=778 ttl=64 time=1.796 ms > 64 bytes from 192.168.1.1: icmp_seq=779 ttl=64 time=9222.495 ms > 64 bytes from 192.168.1.1: icmp_seq=780 ttl=64 time=8967.619 ms > 64 bytes from 192.168.1.1: icmp_seq=781 ttl=64 time=8701.003 ms > 64 bytes from 192.168.1.1: icmp_seq=782 ttl=64 time=8434.659 ms > 64 bytes from 192.168.1.1: icmp_seq=865 ttl=64 time=2.744 ms > 64 bytes from 192.168.1.1: icmp_seq=871 ttl=64 time=1.548 ms > 64 bytes from 192.168.1.1: icmp_seq=872 ttl=64 time=4.107 ms > 64 bytes from 192.168.1.1: icmp_seq=873 ttl=64 time=1.570 ms > 64 bytes from 192.168.1.1: icmp_seq=876 ttl=64 time=1.534 ms > 64 bytes from 192.168.1.1: icmp_seq=900 ttl=64 time=1.530 ms > 64 bytes from 192.168.1.1: icmp_seq=903 ttl=64 time=1.520 ms > 64 bytes from 192.168.1.1: icmp_seq=904 ttl=64 time=6964.209 ms > 64 bytes from 192.168.1.1: icmp_seq=905 ttl=64 time=6697.696 ms > 64 bytes from 192.168.1.1: icmp_seq=906 ttl=64 time=7045.536 ms > 64 bytes from 192.168.1.1: icmp_seq=907 ttl=64 time=6790.528 ms > 64 bytes from 192.168.1.1: icmp_seq=908 ttl=64 time=6524.030 ms It'll be very stable, ping times of less than 2ms, then dropped packets and jumping up to high ping times. My messages file doesn't report anything noticeable other than losing network and regaining. On 3/31/2013 7:06 AM, Joshua Isom wrote: > If I drop down to one 8Gb stick, and I don't have other wifi devices > near causing interference, I can get a reliable connection and low loss. > If I have 16Gb, I can get about a minute or two of decent ping times > before it degrades to multi-second pings of the router. Even at 8Gb, > it's not guaranteed on boot, but rebooting does seem to fix it. At > 16Gb, I tried two different sticks just to see if maybe it was one bad > chip but it didn't change it. That means it's probably an address > conflict, or cache size issue, right? > > On 3/31/2013 1:25 AM, Adrian Chadd wrote: >> does downgrading the motherboard/ram fix it? >> >> You were already running 64 bit, right? What if you just boot with 2gb >> of ram? >> >> >> >> >> adrian >> From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 31 13:14:40 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id BF528C1F; Sun, 31 Mar 2013 13:14:40 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-gg0-x236.google.com (mail-gg0-x236.google.com [IPv6:2607:f8b0:4002:c02::236]) by mx1.freebsd.org (Postfix) with ESMTP id 77749CDC; Sun, 31 Mar 2013 13:14:40 +0000 (UTC) Received: by mail-gg0-f182.google.com with SMTP id u2so248181ggn.27 for ; Sun, 31 Mar 2013 06:14:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=gbLBWSsszMMjh1YO7dMby0ukTGBMCMSddUTh6nJJx84=; b=JdiVRcnOgTtG8EN3YSioRycL7obpHuOL441ECN+l8gHCtn2tyCS/dSH2lvq8EPjF2q OAz02dw0ZlXgvTC86g+koOwwCUx78WwqUUkGsgLvq7IC/dtm2jmkVLZHtwaEmnntA6tJ TFuaq0czM2NAu6gN+13jZkUAZQSZgcEYA1AIGDtv6PkgoscX2s4PA6iUW+BSMy8z6uXX 9wWEQl6lCRF2+vtUeVoUdwkXh/vUS68JsV+I0/bum8euS7GA6bSSaX3SejuHgBsi/sak N5OJMZcyhVdZ7EjqQVrqxE2vHSsymu3vMCRhkSQPw6sqUinzABAeod4SAR87SRC1jqz0 +3tA== X-Received: by 10.236.190.200 with SMTP id e48mr6061972yhn.137.1364731583101; Sun, 31 Mar 2013 05:06:23 -0700 (PDT) Received: from [192.168.1.34] (c-98-212-197-211.hsd1.il.comcast.net. [98.212.197.211]) by mx.google.com with ESMTPS id x71sm17970209yhg.17.2013.03.31.05.06.21 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 31 Mar 2013 05:06:22 -0700 (PDT) Message-ID: <515826B9.6070509@gmail.com> Date: Sun, 31 Mar 2013 07:06:17 -0500 From: Joshua Isom User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: ath not working after a motherboard and ram upgrade References: <51578BAC.4090608@gmail.com> In-Reply-To: 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.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, 31 Mar 2013 13:14:40 -0000 If I drop down to one 8Gb stick, and I don't have other wifi devices near causing interference, I can get a reliable connection and low loss. If I have 16Gb, I can get about a minute or two of decent ping times before it degrades to multi-second pings of the router. Even at 8Gb, it's not guaranteed on boot, but rebooting does seem to fix it. At 16Gb, I tried two different sticks just to see if maybe it was one bad chip but it didn't change it. That means it's probably an address conflict, or cache size issue, right? On 3/31/2013 1:25 AM, Adrian Chadd wrote: > does downgrading the motherboard/ram fix it? > > You were already running 64 bit, right? What if you just boot with 2gb of ram? > > > > > adrian > From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 31 15:25:18 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id DCE1B991; Sun, 31 Mar 2013 15:25:18 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-yh0-x235.google.com (mail-yh0-x235.google.com [IPv6:2607:f8b0:4002:c01::235]) by mx1.freebsd.org (Postfix) with ESMTP id 94DCE75; Sun, 31 Mar 2013 15:25:18 +0000 (UTC) Received: by mail-yh0-f53.google.com with SMTP id q3so238644yhf.12 for ; Sun, 31 Mar 2013 08:25:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Ug8KR1XhFeLTKkUmnIbjsw8IFiEMJr3kcIJh8fcQYQE=; b=NWpznTDutotB62jaEcKKgHCgAw9og4wUX+0C8QPdi5SCaJllmHu9MhEjNEqbifdqUL rwm1jNmzEN1Uk0kExE2/CxYLqyddSl2Mk48t6Xj5t2CpbrOaBHS7SzxlRzjafTAi1uez uG1IaKdVh4DjOu2kt+328+RL1hEfFNK//jM08GFAPcAgcg/zvIGzBpypsp99zGIJlZ9+ y99WR+8pe5d8Iiq0nxGdIkj2aTz4Y9IafELiOjRw5J2K15Z3t2n0qWdWP0eQx/eb9a0A X0H3vs8eQb/QwnTDVU9V4xA3U1YGjrf6sPWgl58x0iQLACMD04zWmfjB+6lvwDcxdGDk F3ig== X-Received: by 10.236.92.241 with SMTP id j77mr6542765yhf.147.1364743518158; Sun, 31 Mar 2013 08:25:18 -0700 (PDT) Received: from [192.168.1.34] (c-98-212-197-211.hsd1.il.comcast.net. [98.212.197.211]) by mx.google.com with ESMTPS id 30sm19261491yhb.6.2013.03.31.08.25.17 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 31 Mar 2013 08:25:17 -0700 (PDT) Message-ID: <51585558.8040202@gmail.com> Date: Sun, 31 Mar 2013 10:25:12 -0500 From: Joshua Isom User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: ath not working after a motherboard and ram upgrade References: <51578BAC.4090608@gmail.com> <515826B9.6070509@gmail.com> In-Reply-To: <515826B9.6070509@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.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, 31 Mar 2013 15:25:18 -0000 I tried updating today to the new code, it seemed to make it worse and never get decent ping times. With the code from before, it's dependent on boot, either it will work fine on boot or fail. But it has to be related to the "handled npkts 0" message. When I'm getting no messages, it's perfect. The number and speed of the messages is the inverse of the network quality. When it's an intermittent loss, it degrades a couple seconds before the messages start. On 3/31/2013 7:06 AM, Joshua Isom wrote: > If I drop down to one 8Gb stick, and I don't have other wifi devices > near causing interference, I can get a reliable connection and low loss. > If I have 16Gb, I can get about a minute or two of decent ping times > before it degrades to multi-second pings of the router. Even at 8Gb, > it's not guaranteed on boot, but rebooting does seem to fix it. At > 16Gb, I tried two different sticks just to see if maybe it was one bad > chip but it didn't change it. That means it's probably an address > conflict, or cache size issue, right? > > On 3/31/2013 1:25 AM, Adrian Chadd wrote: >> does downgrading the motherboard/ram fix it? >> >> You were already running 64 bit, right? What if you just boot with 2gb >> of ram? >> >> >> >> >> adrian >> From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 31 15:54:41 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B672091 for ; Sun, 31 Mar 2013 15:54:41 +0000 (UTC) (envelope-from gofdw-freebsd-wireless@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) by mx1.freebsd.org (Postfix) with ESMTP id 76D871A6 for ; Sun, 31 Mar 2013 15:54:41 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1UMKb2-0006CA-HW for freebsd-wireless@freebsd.org; Sun, 31 Mar 2013 17:55:04 +0200 Received: from a91-154-115-217.elisa-laajakaista.fi ([91.154.115.217]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 31 Mar 2013 17:55:04 +0200 Received: from rakuco by a91-154-115-217.elisa-laajakaista.fi with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 31 Mar 2013 17:55:04 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-wireless@freebsd.org From: Raphael Kubo da Costa Subject: Re: [rft] ar9300 HAL updated Date: Sun, 31 Mar 2013 17:49:43 +0300 Lines: 43 Message-ID: <86bo9z39q0.fsf@orwell.Elisa> References: Mime-Version: 1.0 Content-Type: text/plain X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: a91-154-115-217.elisa-laajakaista.fi User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.3 (berkeley-unix) Cancel-Lock: sha1:2Y8vTz9yHd4R6AG+QoZTmhx5DaQ= 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, 31 Mar 2013 15:54:41 -0000 Adrian Chadd writes: > I've just updated the AR9300 HAL to the March 13 snapshot from QCA. > > This includes calibration and TX power calibration changes that may > improve stability. > > As always, it's possible I broke something! > > I'd appreciate it if people would test this in STA and AP mode. I'm at r248944 here using HEAD. After checking out the code, I created the expected symlinks at the new contrib/ location (BTW, are you sure you want sys/contrib/sys/dev/ath instead of sys/contrib/dev/ath, which seems to be the chosen location for other modules?). The first error I got was in ar9300_radio.c:90 -- clang complained `ichan' was not being used. It is now failing like this: cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I/usr/src/sys/modules/ath/../.. /dev/ath -I/usr/src/sys/modules/ath/../../dev/ath/ath_hal -I. -I/usr/src/sys/modules/ath/../../contrib/sys/dev/a th/ath_hal/ -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj/usr/src/sys/ORWELL/opt_global.h -I. -I@ -I@/contrib/a ltq -fno-common -g -fno-omit-frame-pointer -I/usr/obj/usr/src/sys/ORWELL -mno-aes -mno-avx -mcmodel=kernel -mno -red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -std= iso9899:1999 -Qunused-arguments -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmiss ing-include-dirs -fdiagnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-pa rentheses-equality -c /usr/src/sys/modules/ath/../../contrib/sys/dev/ath/ath_hal/ar9300/ar9300_eeprom.c In file included from /usr/src/sys/modules/ath/../../contrib/sys/dev/ath/ath_hal/ar9300/ar9300_eeprom.c:27: /usr/src/sys/modules/ath/../../contrib/sys/dev/ath/ath_hal/ar9300/ar9300template_generic.h:113:3: error: implicit conversion from 'int' to 'u_int8_t' (aka 'unsigned char') changes value from -477 to 35 [-Werror,-Wconstant-conversion] FREQ2FBIN(2412, 1), ^~~~~~~~~~~~~~~~~~ /usr/src/sys/modules/ath/../../contrib/sys/dev/ath/ath_hal/ar9300/ar9300eep.h:142:65: note: expanded from macro 'FREQ2FBIN' (((y) == HAL_FREQ_BAND_2GHZ) ? ((x) - 2300) : (((x) - 4800) / 5)) ~~~~~~~~~~~~~^~~ The error message is repeated multiple times (one for each FREQ2FBIN call). From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 31 16:13:39 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E728F5EB for ; Sun, 31 Mar 2013 16:13:39 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-ye0-f170.google.com (mail-ye0-f170.google.com [209.85.213.170]) by mx1.freebsd.org (Postfix) with ESMTP id B03DE24E for ; Sun, 31 Mar 2013 16:13:39 +0000 (UTC) Received: by mail-ye0-f170.google.com with SMTP id q9so263747yen.29 for ; Sun, 31 Mar 2013 09:13:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=E78eS3pgTm53r6mgt8jzVQliX+vO7td7rEjZE3XM7SA=; b=T2H3x3AYPRo0j3Ov4phaPWq6HHBJmfLtdUiYM0wwRGi0HgXVizbKN6l+CLT6x3/OI0 nU3sXPQt0Nm7RzxfWaPIcrWo6uCCigF5IFBz0l029tDVC+ABqxtXF53VUmAYXqtqtzZC O7WsA1jQYnTFt3FmSgrDdvmsGMDS/DLFoIqqU4h4jNebtV6fgtvICd1PncsA0bYpSANe syNl1/0+w7zuZwRefwLvDguPzzgyudQ7x1TT5uYUEc7YrmjwfB2PWWnymPZ5mczW+/HQ GPcPzzQu+Nf0EwPlKo/aL5xLn4gFF1TdUen2rLEw6qsLNMMEDdl/798ZxD42mmiZZiqK bxdg== X-Received: by 10.236.149.1 with SMTP id w1mr6949025yhj.46.1364746418827; Sun, 31 Mar 2013 09:13:38 -0700 (PDT) Received: from [192.168.1.34] (c-98-212-197-211.hsd1.il.comcast.net. [98.212.197.211]) by mx.google.com with ESMTPS id h6sm19616456yhf.19.2013.03.31.09.13.37 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 31 Mar 2013 09:13:38 -0700 (PDT) Message-ID: <515860AD.2040003@gmail.com> Date: Sun, 31 Mar 2013 11:13:33 -0500 From: Joshua Isom User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: freebsd-wireless@freebsd.org Subject: Re: [rft] ar9300 HAL updated References: <86bo9z39q0.fsf@orwell.Elisa> In-Reply-To: <86bo9z39q0.fsf@orwell.Elisa> 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.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, 31 Mar 2013 16:13:40 -0000 On 3/31/2013 9:49 AM, Raphael Kubo da Costa wrote: > The first error I got was in ar9300_radio.c:90 -- clang complained > `ichan' was not being used. I keep forgetting about this, but if you open the file go to line 89 and change the ifdef to '#if 0' it'll compile. Also, for your kernel config, generic won't work. Comment out the device lines for ath, ath_pci, and ath_hal. Three options need added, so it'll look like this. #device ath # Atheros NICs #device ath_pci # Atheros pci/cardbus glue #device ath_hal # pci/cardbus chip support options ATH_DEBUG options AH_DEBUG options ATH_DIAGAPI options AH_SUPPORT_AR5416 # enable AR5416 tx/rx descriptors options AH_AR5416_INTERRUPT_MITIGATION # AR5416 interrupt mitigation options ATH_ENABLE_11N # Enable 802.11n support for AR5416 and later #device ath_rate_sample # SampleRate tx rate control for ath You can add 'if_ath_load="YES"' and 'if_ath_pci_load="YES"' to your loader.conf to get it loaded on boot. From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 31 17:29:13 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 2052366D for ; Sun, 31 Mar 2013 17:29:13 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-f53.google.com (mail-wg0-f53.google.com [74.125.82.53]) by mx1.freebsd.org (Postfix) with ESMTP id AFF9A7AE for ; Sun, 31 Mar 2013 17:29:12 +0000 (UTC) Received: by mail-wg0-f53.google.com with SMTP id c11so1606828wgh.20 for ; Sun, 31 Mar 2013 10:29:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=kxrOQ0xJGKXnUL35Rvr7NZuGV/0ZuBGCV6LyuHPmiTo=; b=KRgr0cuJdBSAQTzZbZR8Eh4NS2mrfAHrjCUQ/I2j/BkqCrWtrs3DDhtO+ZDNljA4qp RT5BkvxV/poT7ujJMJo8njwdIbTo6WSoXna6UclCH9E1PAEB8Kswgu4HF+ma0DJMf1Fs gWh2NPVGuiU5RUhnicsHzqxrc+ThCy/Jz0XqibdIrMn8qtwEbTs5qsE5aKHA1msYbrYV Sk0Hu/sLLlYpU7ne1huZMfOFHIh5nnNPSD9D7hInv9Z+xiTpOnxCMG9XjqCU72ky+HkH UNB7i/gVSyhg3AzPr2OYVVxYxQDdxG3kGqCRIygspRJp5KbitTZfoydUtSeq5Dcqysrr 45eQ== MIME-Version: 1.0 X-Received: by 10.181.11.164 with SMTP id ej4mr6588206wid.29.1364750946347; Sun, 31 Mar 2013 10:29:06 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.108.130 with HTTP; Sun, 31 Mar 2013 10:29:06 -0700 (PDT) In-Reply-To: <51585558.8040202@gmail.com> References: <51578BAC.4090608@gmail.com> <515826B9.6070509@gmail.com> <51585558.8040202@gmail.com> Date: Sun, 31 Mar 2013 10:29:06 -0700 X-Google-Sender-Auth: mM4B3EZxIRY4ptthp2AmRTzQkhQ Message-ID: Subject: Re: ath not working after a motherboard and ram upgrade From: Adrian Chadd To: Joshua Isom 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, 31 Mar 2013 17:29:13 -0000 ... that message is because it's scanning. :-) Try booting it with only 2GB of physical RAM. It may be something odd to do with how the DMA code works; the ath NIC is a 32 bit PCI device. I need to make sure it's totally 64 bit clean - not only 64 bit pointer clean, but all the mbufs need to be in the lower 32 bits of physical memory :) Adrian On 31 March 2013 08:25, Joshua Isom wrote: > I tried updating today to the new code, it seemed to make it worse and never > get decent ping times. With the code from before, it's dependent on boot, > either it will work fine on boot or fail. > > But it has to be related to the "handled npkts 0" message. When I'm getting > no messages, it's perfect. The number and speed of the messages is the > inverse of the network quality. When it's an intermittent loss, it degrades > a couple seconds before the messages start. > > > On 3/31/2013 7:06 AM, Joshua Isom wrote: >> >> If I drop down to one 8Gb stick, and I don't have other wifi devices >> near causing interference, I can get a reliable connection and low loss. >> If I have 16Gb, I can get about a minute or two of decent ping times >> before it degrades to multi-second pings of the router. Even at 8Gb, >> it's not guaranteed on boot, but rebooting does seem to fix it. At >> 16Gb, I tried two different sticks just to see if maybe it was one bad >> chip but it didn't change it. That means it's probably an address >> conflict, or cache size issue, right? >> >> On 3/31/2013 1:25 AM, Adrian Chadd wrote: >>> >>> does downgrading the motherboard/ram fix it? >>> >>> You were already running 64 bit, right? What if you just boot with 2gb >>> of ram? >>> >>> >>> >>> >>> adrian >>> > From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 31 17:49:55 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 14488C4B; Sun, 31 Mar 2013 17:49:55 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-gg0-x231.google.com (mail-gg0-x231.google.com [IPv6:2607:f8b0:4002:c02::231]) by mx1.freebsd.org (Postfix) with ESMTP id BF2A28A1; Sun, 31 Mar 2013 17:49:54 +0000 (UTC) Received: by mail-gg0-f177.google.com with SMTP id q1so271499gge.36 for ; Sun, 31 Mar 2013 10:49:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=uBP2fq/aGcJMMuaPHRUj1/DVqiUVs1WleI3eNHuNicA=; b=lV1tibn3pBZOXzE9sBUC/s21nM+C9L0Uk21l9eDNXy8qlsf3UhbsFKAplHm9rq+5DE HVgSHbqSoR9FIs9qB+fo2Xpv4HuNFJ/UJEn4lCyQp7TrOhyzRdLTS4KXG7USLNzHtIue 1RyablUzhabuB5asOcULDb5emLJJiF0obv9suW5PoInNIWT77KA9gM9D7K0Wrzau9RYy ICLLvID2yZsfxykFyr5m06q5haAEB90W7109fDN3fUbo44HRGpn2bij7Rpfi/gWV8XWe 01Eh51x7U5e3BpgQI6HAauKGBlgLINDhXkQdE94FU1JaR9AZDJUh+Ff+0Xhdv83tf46T PU7A== X-Received: by 10.236.73.231 with SMTP id v67mr7155902yhd.88.1364752193905; Sun, 31 Mar 2013 10:49:53 -0700 (PDT) Received: from [192.168.1.34] (c-98-212-197-211.hsd1.il.comcast.net. [98.212.197.211]) by mx.google.com with ESMTPS id b7sm20248042yhl.10.2013.03.31.10.49.52 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 31 Mar 2013 10:49:53 -0700 (PDT) Message-ID: <5158773C.4080201@gmail.com> Date: Sun, 31 Mar 2013 12:49:48 -0500 From: Joshua Isom User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: ath not working after a motherboard and ram upgrade References: <51578BAC.4090608@gmail.com> <515826B9.6070509@gmail.com> <51585558.8040202@gmail.com> In-Reply-To: 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.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, 31 Mar 2013 17:49:55 -0000 I seems someone working on the kernel's already figured out how to deal with this. The hw.physmem sysctl can be set at boot time, with 2Gb it seems to be working fine. I reinstalled all the sticks, and it's working fine with the sysctl set to 2Gb. On 3/31/2013 12:29 PM, Adrian Chadd wrote: > ... that message is because it's scanning. :-) > > Try booting it with only 2GB of physical RAM. > > It may be something odd to do with how the DMA code works; the ath NIC > is a 32 bit PCI device. I need to make sure it's totally 64 bit clean > - not only 64 bit pointer clean, but all the mbufs need to be in the > lower 32 bits of physical memory :) > > > > > Adrian From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 31 18:38:46 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C17F7509 for ; Sun, 31 Mar 2013 18:38:46 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com [IPv6:2a00:1450:400c:c05::231]) by mx1.freebsd.org (Postfix) with ESMTP id 5BE2B9D3 for ; Sun, 31 Mar 2013 18:38:46 +0000 (UTC) Received: by mail-wi0-f177.google.com with SMTP id hm14so1058634wib.4 for ; Sun, 31 Mar 2013 11:38:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=vRmQY4iwjmPazXERGCzANRtYp+/82tBkbsJSOavb9sI=; b=sXnnnBNyRGy8AG4x7to0anXzNTdwOmFCxL2nPIrhGyhjiyVT+7Rk0E7SalBqQLNzr+ OidI4Oh+NATD5HOHYdwHDtRw6QlzZVK2v4jAuVIGQb6fuWGk0ZnxpO6qRzAphKGjJMsj waGkl0NNZpNzkXt2jzajVl7pzHvWiYAMUtKhXbVo3eNlD/SyA4zsVLmmGZ1+//QaT8pE jCYGheNHxtVBft9Lc/i6BtsRlZZZVgp6FBILdLO7T/iQoOFjJ0epgrK3TnlQWXCCOax9 vembOYaWeuXT1zOX/3rWXwmpkjijaQwZTQf6YJmFjY4WKyI0hDpIIvqooMVdF7hueaVb twZQ== MIME-Version: 1.0 X-Received: by 10.194.120.169 with SMTP id ld9mr12340471wjb.24.1364755125563; Sun, 31 Mar 2013 11:38:45 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.108.130 with HTTP; Sun, 31 Mar 2013 11:38:45 -0700 (PDT) In-Reply-To: <5158773C.4080201@gmail.com> References: <51578BAC.4090608@gmail.com> <515826B9.6070509@gmail.com> <51585558.8040202@gmail.com> <5158773C.4080201@gmail.com> Date: Sun, 31 Mar 2013 11:38:45 -0700 X-Google-Sender-Auth: 18T4oWmfksSuci58-gweYvL0FIs Message-ID: Subject: Re: ath not working after a motherboard and ram upgrade From: Adrian Chadd To: Joshua Isom 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, 31 Mar 2013 18:38:46 -0000 On 31 March 2013 10:49, Joshua Isom wrote: > I seems someone working on the kernel's already figured out how to deal with > this. The hw.physmem sysctl can be set at boot time, with 2Gb it seems to > be working fine. I reinstalled all the sticks, and it's working fine with > the sysctl set to 2Gb. Ooooooo Yay! I mean, damn, that's busted. But yay, now we can narrow down what the problem is! Try bumping it to 4GB. It should be fine at that. If it is, please create a PR with all the above information and I'll start re-reviewing the DMA / buffer code to see what's going on. Thanks! Adrian From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 31 19:03:25 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1F56CB85; Sun, 31 Mar 2013 19:03:25 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-gg0-x22a.google.com (mail-gg0-x22a.google.com [IPv6:2607:f8b0:4002:c02::22a]) by mx1.freebsd.org (Postfix) with ESMTP id C87ABA82; Sun, 31 Mar 2013 19:03:24 +0000 (UTC) Received: by mail-gg0-f170.google.com with SMTP id k4so275271ggn.1 for ; Sun, 31 Mar 2013 12:03:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=ei3yWFcyexL0VcZ2okvbUw57/KWKtds7Y3xq1wG8NRo=; b=mha+IJxL+CzTLUiXISyCdeQFEWVzu0tR38icwJPL/uc6Er8n2nM5eRjTzewO2JbWS+ 7uG0ogEZTQHQkCsexLA2a4DV/qWz3bPwemphhfEORpkgTdk2tyMu908mqkYEXYQa/GoZ qz+7f/ywZ0D2TnF0d7zfAlSdJaJjfmNXKzP8PNg9++MEjMLv3uM3uvUm1hIJ19wGpBic z69PQGYlsyLwwVj7ZwmHdW47XE7WzKwCils2blUPxUIwbUR/8v7ABCvgEv4x5DgRPd0n RsdiVm02wXblls1h/xg+fgikEI5zw2nahbT00uqJwcyZ/YnFJpHUL3oU56z/4x9FYd5P hZlw== X-Received: by 10.236.106.9 with SMTP id l9mr7317353yhg.149.1364756603897; Sun, 31 Mar 2013 12:03:23 -0700 (PDT) Received: from [192.168.1.34] (c-98-212-197-211.hsd1.il.comcast.net. [98.212.197.211]) by mx.google.com with ESMTPS id s45sm20767782yhk.22.2013.03.31.12.03.23 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 31 Mar 2013 12:03:23 -0700 (PDT) Message-ID: <51588876.1080705@gmail.com> Date: Sun, 31 Mar 2013 14:03:18 -0500 From: Joshua Isom User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: ath not working after a motherboard and ram upgrade References: <51578BAC.4090608@gmail.com> <515826B9.6070509@gmail.com> <51585558.8040202@gmail.com> <5158773C.4080201@gmail.com> In-Reply-To: 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.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, 31 Mar 2013 19:03:25 -0000 I switched it to 4Gb shortly after you mentioned 32 bit pci. I've been using amd64 for so long I forgot about 32 bit memory limits. On 3/31/2013 1:38 PM, Adrian Chadd wrote: > On 31 March 2013 10:49, Joshua Isom wrote: >> I seems someone working on the kernel's already figured out how to deal with >> this. The hw.physmem sysctl can be set at boot time, with 2Gb it seems to >> be working fine. I reinstalled all the sticks, and it's working fine with >> the sysctl set to 2Gb. > > Ooooooo Yay! I mean, damn, that's busted. But yay, now we can narrow > down what the problem is! > > Try bumping it to 4GB. It should be fine at that. > > If it is, please create a PR with all the above information and I'll > start re-reviewing the DMA / buffer code to see what's going on. > > Thanks! > > > > > Adrian > From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 31 19:47:24 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 38AD86DE; Sun, 31 Mar 2013 19:47:24 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-qe0-f53.google.com (mail-qe0-f53.google.com [209.85.128.53]) by mx1.freebsd.org (Postfix) with ESMTP id DE02FCF3; Sun, 31 Mar 2013 19:47:23 +0000 (UTC) Received: by mail-qe0-f53.google.com with SMTP id q19so918177qeb.40 for ; Sun, 31 Mar 2013 12:47:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=UfgCMaQ6O+VV6xAV5udlFli6YMJpk9m1xTHw/52lyiw=; b=b65lR7ZNETZKfdXzUk6FZkxsDIRA8ZKlZzCspKyPWTCmw0FRMxZKTdiJg4P2Mrz7zA mxesNCF3gJOyl1nJVE4uY8UqC57s8A86h0pIqEPdeohzWtYkGDjrVJJ1F5bBoPKSf5Jb kJIQddPUss1iodxnnCxbT2EVl25v2Qglo9nU/EyPWEYUPd8Msomnbnrpfm4p6ouquWBj UD4/HwRjnsV0tcivxKl5X6Z12iT5tbjdlkaP+Ddn0afpPJu7ZwDnK/H6RwlbdJf2eN6C I34xn1XfsN3iv+wq4S7LJ6kuBnL+Jh3/ZNBIFrb+TER+sMgIVGCU+ghX0CazfwwJZPXt X+dg== X-Received: by 10.224.195.10 with SMTP id ea10mr10927302qab.9.1364759242401; Sun, 31 Mar 2013 12:47:22 -0700 (PDT) Received: from [192.168.1.34] (c-98-212-197-211.hsd1.il.comcast.net. [98.212.197.211]) by mx.google.com with ESMTPS id m8sm6342090qav.8.2013.03.31.12.47.21 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 31 Mar 2013 12:47:21 -0700 (PDT) Message-ID: <515892C4.1060002@gmail.com> Date: Sun, 31 Mar 2013 14:47:16 -0500 From: Joshua Isom User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: ath not working after a motherboard and ram upgrade References: <51578BAC.4090608@gmail.com> <515826B9.6070509@gmail.com> <51585558.8040202@gmail.com> <5158773C.4080201@gmail.com> In-Reply-To: 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.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, 31 Mar 2013 19:47:24 -0000 From if_ath.c:2995: "For some situations (eg EDMA TX completion), there isn't a requirement for the ath_buf entries to be allocated." The EDMA code uses malloc, but would contigmalloc work instead? On 3/31/2013 1:38 PM, Adrian Chadd wrote: > On 31 March 2013 10:49, Joshua Isom wrote: >> I seems someone working on the kernel's already figured out how to deal with >> this. The hw.physmem sysctl can be set at boot time, with 2Gb it seems to >> be working fine. I reinstalled all the sticks, and it's working fine with >> the sysctl set to 2Gb. > > Ooooooo Yay! I mean, damn, that's busted. But yay, now we can narrow > down what the problem is! > > Try bumping it to 4GB. It should be fine at that. > > If it is, please create a PR with all the above information and I'll > start re-reviewing the DMA / buffer code to see what's going on. > > Thanks! > > > > > Adrian > From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 31 19:58:37 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 54346751; Sun, 31 Mar 2013 19:58:37 +0000 (UTC) (envelope-from sib@tormail.org) Received: from outgoing.tormail.org (outgoing.tormail.org [82.221.96.22]) by mx1.freebsd.org (Postfix) with ESMTP id 1604ED26; Sun, 31 Mar 2013 19:58:36 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=internal.tormail.org) by outgoing.tormail.org with esmtp (Exim 4.72) (envelope-from ) id 1UMOOV-0003um-OK; Sun, 31 Mar 2013 23:58:29 +0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tormail.org; s=tm; h=Message-Id:X-TorMail-User:Content-Transfer-Encoding:Content-Type:MIME-Version:Cc:To:From:Subject:Date; bh=f2Z8+h7qgCkg/i1PG32XWcCJQ3I7YuVZcvMbSctkz94=; b=aTQCbZYbl5qtPMEAxM6DC9tpFlDRznnPud8xCHGtLqyRaOD2+OSuplgM69ZdbwXwTd8M1N+1UI6m2R2bAkEu41M7yhK9V5RIJs+2VJT14BzSSPJth/i26yyPL5k7Oo0+Svs92a1HAZZsoeIIofO4DFRfvzSmy1NinhjICMMUZm0=; Received: from sib by internal.tormail.org with local (Exim 4.63) (envelope-from ) id 1UMOLy-000KOi-6Q; Sun, 31 Mar 2013 19:55:46 +0000 Date: Sun, 31 Mar 2013 19:55:46 -0000 Subject: Suggested hardware From: sib@tormail.org To: freebsd-wireless@freebsd.org MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Importance: High X-TorMail-User: sib Message-Id: <1UMOLy-000KOi-6Q@internal.tormail.org> Cc: lme@FreeBSD.org, freebsd-hardware@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, 31 Mar 2013 19:58:37 -0000 Hi. I'm looking to get a netbook or small laptop for FreeBSD. I've only run it on servers and desktops in the past, so I'm unsure about some of the hardware requirements. I'd like to be able to connect to wifi with no auth, wep, wpa and wpa2 and be able to fully utilize the aircrack-ng suite of tools. I need regular wifi, monitor mode/ahdemo and packet injection working. Thankfully I saw this PR was added to the port: https://www.freebsd.org/cgi/query-pr.cgi?pr=ports/160564 Any suggestions for either a netbook or an add-on (usb maybe?) wireless card would be greatly appreciated, thanks. From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 31 20:58:30 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B19B0D3 for ; Sun, 31 Mar 2013 20:58:30 +0000 (UTC) (envelope-from gofdw-freebsd-wireless@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) by mx1.freebsd.org (Postfix) with ESMTP id 71A7EECF for ; Sun, 31 Mar 2013 20:58:30 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1UMPL2-0001HK-0O for freebsd-wireless@freebsd.org; Sun, 31 Mar 2013 22:58:52 +0200 Received: from a91-154-115-217.elisa-laajakaista.fi ([91.154.115.217]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 31 Mar 2013 22:58:51 +0200 Received: from rakuco by a91-154-115-217.elisa-laajakaista.fi with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 31 Mar 2013 22:58:51 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-wireless@freebsd.org From: Raphael Kubo da Costa Subject: Re: [rft] ar9300 HAL updated Date: Sun, 31 Mar 2013 22:58:18 +0300 Lines: 32 Message-ID: <86y5d31gv9.fsf@orwell.Elisa> References: <86bo9z39q0.fsf@orwell.Elisa> <515860AD.2040003@gmail.com> Mime-Version: 1.0 Content-Type: text/plain X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: a91-154-115-217.elisa-laajakaista.fi User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.3 (berkeley-unix) Cancel-Lock: sha1:IcuxUGLWNUr2HLyPv/UlaQswWY0= 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, 31 Mar 2013 20:58:30 -0000 Joshua Isom writes: > On 3/31/2013 9:49 AM, Raphael Kubo da Costa wrote: >> The first error I got was in ar9300_radio.c:90 -- clang complained >> `ichan' was not being used. > > I keep forgetting about this, but if you open the file go to line 89 > and change the ifdef to '#if 0' it'll compile. Yeah, I did something similar and compilation went a little bit further. > Also, for your kernel config, generic won't work. Comment out the > device lines for ath, ath_pci, and ath_hal. Three options need added, > so it'll look like this. Gah, thanks for reminding me about removing those `device' entries from my kernel configuration. I build my kernel as a "diff" against GENERIC [1], and this is what I'm currently using (the rest of the options are already present in GENERIC): # For the experimental AR9485 support. options ATH_DEBUG options AH_DEBUG options ATH_DIAGAPI nodevice ath nodevice ath_pci nodevice ath_hal nodevice ath_rate_sample [1] http://www.wonkity.com/~wblock/docs/html/kernelconfig.html Anyway, I'm still stuck at those other warnings/errors I posted before. From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 31 22:25:34 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1F3F4B9; Sun, 31 Mar 2013 22:25:34 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-gg0-x22c.google.com (mail-gg0-x22c.google.com [IPv6:2607:f8b0:4002:c02::22c]) by mx1.freebsd.org (Postfix) with ESMTP id CA3A9355; Sun, 31 Mar 2013 22:25:33 +0000 (UTC) Received: by mail-gg0-f172.google.com with SMTP id f4so296425ggn.31 for ; Sun, 31 Mar 2013 15:25:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:to:cc:reply-to:subject:in-reply-to :x-mailer:mime-version:content-type; bh=fXE4wN77tC0UqtaoyGcS4bQo/dDamLcduwKllUrabDQ=; b=I6ibjaYJADM27c4QoVrO+qRNB/H2wWxFEYo0PR3WbRRigFgS/usFwb6saIzTpDlkRF F9Zqc4W4fYtCokqHCaNZ7TSR0i/jpVvrIArTxsWUh1JTB9rgrDymP/JF1P1XT44hTS6V WevuE397pXjQUdUGXnvU+Pl+zmdB/PGPguh+xkDzJBrSES46jbR6tzqA5fE8rX4A/jB7 G/VA2N4A33V5VV2ZobHa6LjHXWD1+Bp7OIlCXnlSK3Qx1Gq1A4/ZNl/im06nNAnmtoEF C89EROICnXaWddLQtIpnox/seUTorTL8Mn+t/knJSgC86/Tzyf1hgKlg9IsW1Ur+svaF qAqg== X-Received: by 10.236.116.33 with SMTP id f21mr7560538yhh.130.1364768732442; Sun, 31 Mar 2013 15:25:32 -0700 (PDT) Received: from www.palm.com ([107.225.197.182]) by mx.google.com with ESMTPS id t9sm22047068yhh.0.2013.03.31.15.25.28 (version=TLSv1 cipher=RC4-SHA bits=128/128); Sun, 31 Mar 2013 15:25:31 -0700 (PDT) Message-ID: <5158b7db.897aec0a.42d0.ffffaac4@mx.google.com> Date: Sun, 31 Mar 2013 18:24:28 -0400 From: "Adrian Chadd" To: "Joshua Isom" , "Adrian Chadd" Subject: Re: ath not working after a motherboard and ram upgrade In-Reply-To: <515892C4.1060002@gmail.com> X-Mailer: Palm webOS v1.0.1 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Adrian Chadd List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Mar 2013 22:25:34 -0000 The problem isn't contigmalloc, it's making sure that it gets bounced via= the local 32 bits of address space right. I'll talk with other developers and see what the deal is with 64 bit addres= s space for 32 bit nics. Thanks, Adrian Sent from my Palm Pre on AT&T On Mar 31, 2013 3:47 PM, Joshua Isom <jrisom@gmail.com> wrote:=20 From if_ath.c:2995: "For some situations (eg EDMA TX completion),=20 there isn't a requirement for the ath_buf entries to be allocated." The EDMA code uses malloc, but would contigmalloc work instead? On 3/31/2013 1:38 PM, Adrian Chadd wrote: > On 31 March 2013 10:49, Joshua Isom <jrisom@gmail.com> wrote: >> I seems someone working on the kernel's already figured out how to= deal with >> this. The hw.physmem sysctl can be set at boot time, with 2Gb it= seems to >> be working fine. I reinstalled all the sticks, and it's working= fine with >> the sysctl set to 2Gb. > > Ooooooo Yay! I mean, damn, that's busted. But yay, now we can narrow > down what the problem is! > > Try bumping it to 4GB. It should be fine at that. > > If it is, please create a PR with all the above information and I'll > start re-reviewing the DMA / buffer code to see what's going on. > > Thanks! > > > > > Adrian > From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 31 22:25:37 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id CE60EBB; Sun, 31 Mar 2013 22:25:37 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-gg0-x235.google.com (mail-gg0-x235.google.com [IPv6:2607:f8b0:4002:c02::235]) by mx1.freebsd.org (Postfix) with ESMTP id 873CF356; Sun, 31 Mar 2013 22:25:37 +0000 (UTC) Received: by mail-gg0-f181.google.com with SMTP id l4so295519ggi.40 for ; Sun, 31 Mar 2013 15:25:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:to:reply-to:subject:in-reply-to :x-mailer:mime-version:content-type; bh=eDbQup11A2mz8B83We3jZRrPsBO7NlY3NVFvHPp4w7I=; b=FIxLu/RdrVebLEBk+sj2p9hez2oZInxSqqE2U76Ai5qwBJ2IdScqNtBF3I1Sd6ZgJ3 g072EMJ/74t4mxiiAWzS2FOA1LvJbuQZ37jXflRN5xGk2W9Qrip6ZE6OxEBgEomM9jzI WdOsR/PR3J+O83Jx0BNlvoeF3hWydGyY6Ig41tGyk8vzHyg7Jfp95k38+xKElM9uhwTW dSn8JfpfIlegZ2yec5iCBTAHbQ0SMz2Zd6+z4Btf1UoYkyXo8RXZ3sYtWMhYaJr+5D6o PeYMcOBwEN90TW0ZgniLWJBDpBTAjzvOeSEAqQT64wI+UjZeuEm1y53AEBkAldp+H2TL Bvrw== X-Received: by 10.236.133.194 with SMTP id q42mr7487855yhi.174.1364768737133; Sun, 31 Mar 2013 15:25:37 -0700 (PDT) Received: from www.palm.com ([107.225.197.182]) by mx.google.com with ESMTPS id t9sm22047068yhh.0.2013.03.31.15.25.32 (version=TLSv1 cipher=RC4-SHA bits=128/128); Sun, 31 Mar 2013 15:25:36 -0700 (PDT) Message-ID: <5158b7e0.897aec0a.42d0.ffffaac9@mx.google.com> Date: Sun, 31 Mar 2013 18:25:37 -0400 From: "Adrian Chadd" To: "Raphael Kubo da Costa" , "freebsd-wireless@freebsd.org" Subject: Re: [rft] ar9300 HAL updated In-Reply-To: <86bo9z39q0.fsf@orwell.Elisa> X-Mailer: Palm webOS v1.0.1 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Adrian Chadd List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Mar 2013 22:25:37 -0000 Look in ath/makefile .. At the bottom. There's clang warning overrides ther= e. Uncomment them! Adrian Sent from my Palm Pre on AT&T On Mar 31, 2013 11:54 AM, Raphael Kubo da Costa <rakuco@freebsd.org>= wrote:=20 Adrian Chadd <adrian@freebsd.org> writes: > I've just updated the AR9300 HAL to the March 13 snapshot from QCA. > > This includes calibration and TX power calibration changes that may > improve stability. > > As always, it's possible I broke something! > > I'd appreciate it if people would test this in STA and AP mode. I'm at r248944 here using HEAD. After checking out the code, I created the expected symlinks at the new contrib/ location (BTW, are you sure you want sys/contrib/sys/dev/ath instead of sys/contrib/dev/ath, which seems to be the chosen location for other modules?). The first error I got was in ar9300_radio.c:90 -- clang complained `ichan' was not being used. It is now failing like this: cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc= -I. -I/usr/src/sys/modules/ath/../.. /dev/ath -I/usr/src/sys/modules/ath/../../dev/ath/ath_hal -I. -I/usr/src/sy= s/modules/ath/../../contrib/sys/dev/a th/ath_hal/ -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj/usr/src/sys/ORWE= LL/opt_global.h -I. -I@ -I@/contrib/a ltq -fno-common -g -fno-omit-frame-pointer -I/usr/obj/usr/src/sys/ORWELL = -mno-aes -mno-avx -mcmodel=3Dkernel -mno -red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables= -ffreestanding -fstack-protector -std=3D iso9899:1999 -Qunused-arguments -fstack-protector -Wall -Wredundant-decls= -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-poi= nter-sign -fformat-extensions -Wmiss ing-include-dirs -fdiagnostics-show-option -Wno-error-tautological-compare= -Wno-error-empty-body -Wno-error-pa rentheses-equality -c /usr/src/sys/modules/ath/../../contrib/sys/dev/ath/a= th_hal/ar9300/ar9300_eeprom.c In file included from /usr/src/sys/modules/ath/../../contrib/sys/dev/ath/at= h_hal/ar9300/ar9300_eeprom.c:27: /usr/src/sys/modules/ath/../../contrib/sys/dev/ath/ath_hal/ar9300/ar9300tem= plate_generic.h:113:3: error: implicit conversion from 'int' to 'u_int8_t' (aka 'unsigned char') ch= anges value from -477 to 35 [-Werror,-Wconstant-conversion] FREQ2FBIN(2412, 1), ^~~~~~~~~~~~~~~~~~ /usr/src/sys/modules/ath/../../contrib/sys/dev/ath/ath_hal/ar9300/ar9300eep= =2Eh:142:65: note: expanded from macro 'FREQ2FBIN' (((y) =3D=3D HAL_FREQ_BAND_2GHZ) ? ((x) - 2300) : (((x) - 4800) / 5)) ~~~~~~~~~~~~~^~~ The error message is repeated multiple times (one for each FREQ2FBIN call). _______________________________________________ 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 Sun Mar 31 23:03:34 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]) by hub.freebsd.org (Postfix) with ESMTP id 79CE3975; Sun, 31 Mar 2013 23:03:34 +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 5391B6F9; Sun, 31 Mar 2013 23:03:34 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r2VN3YeX090235; Sun, 31 Mar 2013 23:03:34 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r2VN3Y2t090234; Sun, 31 Mar 2013 23:03:34 GMT (envelope-from linimon) Date: Sun, 31 Mar 2013 23:03:34 GMT Message-Id: <201303312303.r2VN3Y2t090234@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/177465: [iwn] 20%-100% packet loss with iwn driver 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, 31 Mar 2013 23:03:34 -0000 Old Synopsis: 20%-100% packet loss with iwn driver New Synopsis: [iwn] 20%-100% packet loss with iwn driver Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Sun Mar 31 23:03:19 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=177465 From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 1 00:38:02 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 437C966E; Mon, 1 Apr 2013 00:38:02 +0000 (UTC) (envelope-from erich@alogt.com) Received: from alogt.com (alogt.com [69.36.191.58]) by mx1.freebsd.org (Postfix) with ESMTP id 0BE1B9E0; Mon, 1 Apr 2013 00:38:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:Mime-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=bew0LX5R5zmWUsCQOxTbRC39QEC02vZreVKMYmevd1I=; b=JgC+YDSt5BJCKCggCdYEAo19SXs0LWKvr4wjLJeBmzmb8qPsDgW3ANBwJVvew3acXyRnRaTwWGrFGZdhYM3lxCRogN1GNIuBnBCjlG2t8i7UzgIeVX9zolzf/k0NkMqyLOVXljfUue30Z6zpmm+1NSZzz8FOYKAAzCCB7W9RQ0M=; Received: from [122.129.203.50] (port=41337 helo=X220.ovitrap.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:DHE-RSA-AES128-SHA:128) (Exim 4.80) (envelope-from ) id 1UMSl3-001ub7-Gt; Sun, 31 Mar 2013 18:37:58 -0600 Date: Mon, 1 Apr 2013 07:37:53 +0700 From: Erich Dollansky To: sib@tormail.org Subject: Re: Suggested hardware Message-ID: <20130401073753.025ef1c5@X220.ovitrap.com> In-Reply-To: <1UMOLy-000KOi-6Q@internal.tormail.org> References: <1UMOLy-000KOi-6Q@internal.tormail.org> Organization: ALO Green Technologies X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.6; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erich@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: lme@FreeBSD.org, freebsd-wireless@freebsd.org, freebsd-hardware@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, 01 Apr 2013 00:38:02 -0000 Hi, On Sun, 31 Mar 2013 19:55:46 -0000 sib@tormail.org wrote: > Hi. I'm looking to get a netbook or small laptop for FreeBSD. I've > only run it on servers and desktops in the past, so I'm unsure about > some of the hardware requirements. I'd like to be able to connect to > wifi with no auth, wep, wpa and wpa2 and be able to fully utilize the > aircrack-ng suite of tools. I need regular wifi, monitor mode/ahdemo > and packet injection working. Thankfully I saw this PR was added to > the port: https://www.freebsd.org/cgi/query-pr.cgi?pr=ports/160564 > > Any suggestions for either a netbook or an add-on (usb maybe?) > wireless card would be greatly appreciated, thanks. > with netbook you mean the low-cost machines? Lenovo was a good pick for me. Erich From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 1 01:05:13 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E0026B70; Mon, 1 Apr 2013 01:05:13 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) by mx1.freebsd.org (Postfix) with ESMTP id 2DDEFA7C; Mon, 1 Apr 2013 01:05:13 +0000 (UTC) Received: by mail-wi0-f170.google.com with SMTP id hm11so1784471wib.3 for ; Sun, 31 Mar 2013 18:05:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Pjye8/aFmaGPkgeJhgfrWCU5BoHJLCJ/LN9LHG481pQ=; b=Bh859ZGQEusUrTX5sldLIDGkL+thxGpxYx7HbFZI8zs5b2CsxZ1UndKcvI+8R5BvXU qqxzn55ejxM0rky/H7oik35+VXwNdascZtBtZRSNz5F3O0X5WJLWYs5jYOdK/RSDwnCO cr5HjNcc7eqdJePkxkV8vVyyAAETwMPEcbvMlPSq/EptjXh1kWpcV4NZb83YDotEhXbc CyDqf0gb8lRq17C0NTQUs96N3LSi7E4+4tXBa2S+RnYuJUJYFeP/vuAflFj7snOvolD9 CCN3Gu9YK+uBPmpmyVYqL9zrDVGvNv9M2/VBG/LpO4+lTxUahRXpYavl0zozyd2lUBK5 ZnkA== MIME-Version: 1.0 X-Received: by 10.194.120.169 with SMTP id ld9mr13219904wjb.24.1364778312257; Sun, 31 Mar 2013 18:05:12 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.108.130 with HTTP; Sun, 31 Mar 2013 18:05:12 -0700 (PDT) In-Reply-To: <20130401073753.025ef1c5@X220.ovitrap.com> References: <1UMOLy-000KOi-6Q@internal.tormail.org> <20130401073753.025ef1c5@X220.ovitrap.com> Date: Sun, 31 Mar 2013 18:05:12 -0700 X-Google-Sender-Auth: UehYyR4paSmOnmAteWrpsUQU15o Message-ID: Subject: Re: Suggested hardware From: Adrian Chadd To: Erich Dollansky Content-Type: text/plain; charset=ISO-8859-1 Cc: lme@freebsd.org, freebsd-wireless@freebsd.org, freebsd-hardware@freebsd.org, sib@tormail.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, 01 Apr 2013 01:05:13 -0000 .. anything with an Atheros PCI/PCIe chipset will work. The only chipset I don't have support for atm is: * AR5523, but i doubt you'll ever see this unless you still use cardbus; * QCA9880 and derivates (11ac) - but that won't work at the moment and likely won't do raw injection more for aircrack any time soon. If there are bugs with ahdemo/packet injection then please file bugs and participate on freebsd-wireless. I don't have time to debug that stuff at the moment but I'd love to see ti work. Thanks! Adrian On 31 March 2013 17:37, Erich Dollansky wrote: > Hi, > > On Sun, 31 Mar 2013 19:55:46 -0000 > sib@tormail.org wrote: > >> Hi. I'm looking to get a netbook or small laptop for FreeBSD. I've >> only run it on servers and desktops in the past, so I'm unsure about >> some of the hardware requirements. I'd like to be able to connect to >> wifi with no auth, wep, wpa and wpa2 and be able to fully utilize the >> aircrack-ng suite of tools. I need regular wifi, monitor mode/ahdemo >> and packet injection working. Thankfully I saw this PR was added to >> the port: https://www.freebsd.org/cgi/query-pr.cgi?pr=ports/160564 >> >> Any suggestions for either a netbook or an add-on (usb maybe?) >> wireless card would be greatly appreciated, thanks. >> > with netbook you mean the low-cost machines? > > Lenovo was a good pick for me. > > Erich > _______________________________________________ > 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 Mon Apr 1 03:56:27 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]) by hub.freebsd.org (Postfix) with ESMTP id 1E56A734; Mon, 1 Apr 2013 03:56:27 +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 EBF0E307; Mon, 1 Apr 2013 03:56:26 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r313uQtV052528; Mon, 1 Apr 2013 03:56:26 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r313uQHR052527; Mon, 1 Apr 2013 03:56:26 GMT (envelope-from linimon) Date: Mon, 1 Apr 2013 03:56:26 GMT Message-Id: <201304010356.r313uQHR052527@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/177530: [ath] ath driver isn't 32 bit int clean 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, 01 Apr 2013 03:56:27 -0000 Old Synopsis: ath driver isn't 32 bit int clean New Synopsis: [ath] ath driver isn't 32 bit int clean Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Mon Apr 1 03:56:14 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=177530 From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 1 11:06:53 2013 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B66BD913 for ; Mon, 1 Apr 2013 11:06:53 +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 A749934C for ; Mon, 1 Apr 2013 11:06:53 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r31B6rBM033859 for ; Mon, 1 Apr 2013 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r31B6rTR033857 for freebsd-wireless@FreeBSD.org; Mon, 1 Apr 2013 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 1 Apr 2013 11:06:53 GMT Message-Id: <201304011106.r31B6rTR033857@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, 01 Apr 2013 11:06:53 -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/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/175870 wireless [iwn] /etc/rc.d/netif restart cause system crash 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/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 156 problems total. From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 1 15:01:21 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 5BE619F9 for ; Mon, 1 Apr 2013 15:01:21 +0000 (UTC) (envelope-from gofdw-freebsd-wireless@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) by mx1.freebsd.org (Postfix) with ESMTP id 1E05CADD for ; Mon, 1 Apr 2013 15:01:21 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1UMgEv-00034c-Mx for freebsd-wireless@freebsd.org; Mon, 01 Apr 2013 17:01:41 +0200 Received: from a91-154-115-217.elisa-laajakaista.fi ([91.154.115.217]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 01 Apr 2013 17:01:41 +0200 Received: from rakuco by a91-154-115-217.elisa-laajakaista.fi with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 01 Apr 2013 17:01:41 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-wireless@freebsd.org From: Raphael Kubo da Costa Subject: Re: [rft] ar9300 HAL updated Date: Mon, 01 Apr 2013 18:01:02 +0300 Lines: 6 Message-ID: <86zjxis3bl.fsf@orwell.Elisa> References: <86bo9z39q0.fsf@orwell.Elisa> <5158b7e0.897aec0a.42d0.ffffaac9@mx.google.com> Mime-Version: 1.0 Content-Type: text/plain X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: a91-154-115-217.elisa-laajakaista.fi User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.3 (berkeley-unix) Cancel-Lock: sha1:rchODvdxDOwRhZXG0BR483MXN9I= 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, 01 Apr 2013 15:01:21 -0000 "Adrian Chadd" writes: > Look in ath/makefile .. At the bottom. There's clang warning overrides > there. Uncomment them! Thanks, that did the trick. From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 1 15:07:23 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 62746BB8 for ; Mon, 1 Apr 2013 15:07:23 +0000 (UTC) (envelope-from gofdw-freebsd-wireless@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) by mx1.freebsd.org (Postfix) with ESMTP id 23AFEB2D for ; Mon, 1 Apr 2013 15:07:22 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1UMgKm-0005Vu-Pg for freebsd-wireless@freebsd.org; Mon, 01 Apr 2013 17:07:44 +0200 Received: from a91-154-115-217.elisa-laajakaista.fi ([91.154.115.217]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 01 Apr 2013 17:07:44 +0200 Received: from rakuco by a91-154-115-217.elisa-laajakaista.fi with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 01 Apr 2013 17:07:44 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-wireless@freebsd.org From: Raphael Kubo da Costa Subject: Re: [rft] ar9300 HAL updated Date: Mon, 01 Apr 2013 18:07:10 +0300 Lines: 27 Message-ID: <86sj3as31d.fsf@orwell.Elisa> References: Mime-Version: 1.0 Content-Type: text/plain X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: a91-154-115-217.elisa-laajakaista.fi User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.3 (berkeley-unix) Cancel-Lock: sha1:ktudGj/Ab6ChcToG5n2oUorggRs= 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, 01 Apr 2013 15:07:23 -0000 Adrian Chadd writes: > I've just updated the AR9300 HAL to the March 13 snapshot from QCA. > > This includes calibration and TX power calibration changes that may > improve stability. > > As always, it's possible I broke something! > > I'd appreciate it if people would test this in STA and AP mode. Alright, I've finally managed to get everything built and loaded. As I mentioned before, this is HEAD at r248944. I have a Sony Vaio SVT1312 Ultrabook with an Atheros AR9485 wireless card (I _think_ it is also responsible for providing the Bluetooth stuff as well, but I'm not sure). I use this laptop at home to connect to a WPA2 ADSL router. Connecting to it using wpa_supplicant did work, but most of the packages are lost and the ones which actually get through do so with a very high latency. Meanwhile, my terminal gets spammed with the following: ath0: ath_edma_recv_proc_queue: handled npkts 0 ar9300_reset[4366]: ar9300_stop_dma_receive failed Please let me know what other additional information you may need. From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 1 15:08:55 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id AB915CF8; Mon, 1 Apr 2013 15:08:55 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) by mx1.freebsd.org (Postfix) with ESMTP id 21DF7B58; Mon, 1 Apr 2013 15:08:54 +0000 (UTC) Received: by mail-wi0-f175.google.com with SMTP id c10so1628101wiw.14 for ; Mon, 01 Apr 2013 08:08:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=YLLABc6QpQuQ2XJePmmThvdPGl9c/hjU0xaSh/UJltk=; b=oaASEd8PsxNE4OH4PTBqlsORI1AO21Df6ctOSktrSdQJqkZGgqBPkojo6DVlGecpCp Q0+xKHETQyyjTeshQnxaswdlNBh8iXXM2ENizvnxzzxNdSbCkeOZz52pvBf1UmmUsuAj lDgc7FKBSz/jsYs+bR14d1wlSIc6hjPGnM8BjjG1EURqjd7Ti4isC9OFR8abWixZ4dG/ 6jvXVsnyLmhtH4Quyl2vziD+vY58NBC31TFJctr1Ygg83CH8LmmS8jjh5RuKyOhDBJQw 4Wfzk6fHp7LZol9tMJ6e9O+fTtVz1vJWRoydOn4GG9K9U1yggLkSUvVSLK0qNPHkPqf0 Mcxw== MIME-Version: 1.0 X-Received: by 10.181.11.164 with SMTP id ej4mr10476138wid.29.1364828934212; Mon, 01 Apr 2013 08:08:54 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.108.130 with HTTP; Mon, 1 Apr 2013 08:08:54 -0700 (PDT) In-Reply-To: <86sj3as31d.fsf@orwell.Elisa> References: <86sj3as31d.fsf@orwell.Elisa> Date: Mon, 1 Apr 2013 08:08:54 -0700 X-Google-Sender-Auth: yZF7LMaePnTVPdA5tn5oD_Q1Uqs Message-ID: Subject: Re: [rft] ar9300 HAL updated From: Adrian Chadd To: Raphael Kubo da Costa 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, 01 Apr 2013 15:08:55 -0000 64 bit kernel? >4 gig RAM? Adrian On 1 April 2013 08:07, Raphael Kubo da Costa wrote: > Adrian Chadd writes: > >> I've just updated the AR9300 HAL to the March 13 snapshot from QCA. >> >> This includes calibration and TX power calibration changes that may >> improve stability. >> >> As always, it's possible I broke something! >> >> I'd appreciate it if people would test this in STA and AP mode. > > Alright, I've finally managed to get everything built and loaded. As I > mentioned before, this is HEAD at r248944. I have a Sony Vaio SVT1312 > Ultrabook with an Atheros AR9485 wireless card (I _think_ it is also > responsible for providing the Bluetooth stuff as well, but I'm not > sure). > > I use this laptop at home to connect to a WPA2 ADSL router. Connecting > to it using wpa_supplicant did work, but most of the packages are lost > and the ones which actually get through do so with a very high latency. > Meanwhile, my terminal gets spammed with the following: > > ath0: ath_edma_recv_proc_queue: handled npkts 0 > ar9300_reset[4366]: ar9300_stop_dma_receive failed > > Please let me know what other additional information you may need. > > > _______________________________________________ > 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 Mon Apr 1 15:13:26 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id AFF0C6C for ; Mon, 1 Apr 2013 15:13:26 +0000 (UTC) (envelope-from gofdw-freebsd-wireless@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) by mx1.freebsd.org (Postfix) with ESMTP id 71824BF2 for ; Mon, 1 Apr 2013 15:13:26 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1UMgQd-0007yR-Hc for freebsd-wireless@freebsd.org; Mon, 01 Apr 2013 17:13:47 +0200 Received: from a91-154-115-217.elisa-laajakaista.fi ([91.154.115.217]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 01 Apr 2013 17:13:47 +0200 Received: from rakuco by a91-154-115-217.elisa-laajakaista.fi with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 01 Apr 2013 17:13:47 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-wireless@freebsd.org From: Raphael Kubo da Costa Subject: Re: [rft] ar9300 HAL updated Date: Mon, 01 Apr 2013 18:13:13 +0300 Lines: 5 Message-ID: <86k3oms2ra.fsf@orwell.Elisa> References: <86sj3as31d.fsf@orwell.Elisa> Mime-Version: 1.0 Content-Type: text/plain X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: a91-154-115-217.elisa-laajakaista.fi User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.3 (berkeley-unix) Cancel-Lock: sha1:08TxkJ4WFWdGE1GyviylJ0hJ6Wc= 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, 01 Apr 2013 15:13:26 -0000 Adrian Chadd writes: > 64 bit kernel? >4 gig RAM? Yes, amd64 with 8GB of RAM. From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 1 15:19:55 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 7D27B2B0; Mon, 1 Apr 2013 15:19:55 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by mx1.freebsd.org (Postfix) with ESMTP id E52B1CDF; Mon, 1 Apr 2013 15:19:54 +0000 (UTC) Received: by mail-wg0-f44.google.com with SMTP id z12so2136953wgg.23 for ; Mon, 01 Apr 2013 08:19:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=3kktBXNmqxAiRf4BvF32D1yMrwTMvKUjRewPzbJJy+o=; b=lsXMog6+WTLT7P+Nb/fHDrggzOC5b7mhVdEzLqWtQtZ5FlqM2ywm3QlavojnyDt9VZ XtRm5eyjVWvST91oENnFBIq91R2A28iei6u46yZgKenl77pVPDsuFMePuML5voVrMDsz KqPWOarlDCSOH+DquqWo0lXLKudWua3H/bRyvYU7l79yIknXDxxin5LqjubESTNBr5sX +/tzzIC60cCct/CktvQTlwxoD2/dfeg1eUVtcMZu0rEcVyXqbcnczGSqSt+BobgzCJEe m/d/rX2GUHIE3hb/9G2NiRYy6kNTxysHPiGsLae7F3k2k6srGa2WFI4swvuQVrOeaJbL exhA== MIME-Version: 1.0 X-Received: by 10.181.11.164 with SMTP id ej4mr10532755wid.29.1364829588630; Mon, 01 Apr 2013 08:19:48 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.108.130 with HTTP; Mon, 1 Apr 2013 08:19:48 -0700 (PDT) In-Reply-To: <86k3oms2ra.fsf@orwell.Elisa> References: <86sj3as31d.fsf@orwell.Elisa> <86k3oms2ra.fsf@orwell.Elisa> Date: Mon, 1 Apr 2013 08:19:48 -0700 X-Google-Sender-Auth: W9-TA3_TJM3fKSFmoFxZ3t7IDcA Message-ID: Subject: Re: [rft] ar9300 HAL updated From: Adrian Chadd To: Raphael Kubo da Costa 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, 01 Apr 2013 15:19:55 -0000 Please reboot with 4GB of RAM configured. See if that fixes it. Adrian On 1 April 2013 08:13, Raphael Kubo da Costa wrote: > Adrian Chadd writes: > >> 64 bit kernel? >4 gig RAM? > > Yes, amd64 with 8GB of RAM. > > _______________________________________________ > 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 Mon Apr 1 15:44:37 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 03C1BE75 for ; Mon, 1 Apr 2013 15:44:37 +0000 (UTC) (envelope-from gofdw-freebsd-wireless@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) by mx1.freebsd.org (Postfix) with ESMTP id B8A79E6D for ; Mon, 1 Apr 2013 15:44:36 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1UMgup-0003ps-Cd for freebsd-wireless@freebsd.org; Mon, 01 Apr 2013 17:44:59 +0200 Received: from a91-154-115-217.elisa-laajakaista.fi ([91.154.115.217]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 01 Apr 2013 17:44:59 +0200 Received: from rakuco by a91-154-115-217.elisa-laajakaista.fi with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 01 Apr 2013 17:44:59 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-wireless@freebsd.org From: Raphael Kubo da Costa Subject: Re: [rft] ar9300 HAL updated Date: Mon, 01 Apr 2013 18:44:24 +0300 Lines: 16 Message-ID: <86k3om5k87.fsf@orwell.Elisa> References: <86sj3as31d.fsf@orwell.Elisa> <86k3oms2ra.fsf@orwell.Elisa> Mime-Version: 1.0 Content-Type: text/plain X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: a91-154-115-217.elisa-laajakaista.fi User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.3 (berkeley-unix) Cancel-Lock: sha1:X75i/Z/lxkH6pkWo2qmSmGxc/0Y= 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, 01 Apr 2013 15:44:37 -0000 Adrian Chadd writes: > Please reboot with 4GB of RAM configured. > > See if that fixes it. Indeed, booting with hw.physmem="4G" makes the connection much more reliable -- I do see some of those warnings in the beginning, but they go away after the connection is established. My gut feeling is that the average connection speed is still below the one I get when I use my WLAN->Ethernet adapter, but I haven't done any precise measurements to back that up. On a side note: this card is also supposed to provide Bluetooth support, right? Is any of your work going to help with that as well? From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 1 16:54:26 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 276286BA; Mon, 1 Apr 2013 16:54:26 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-f53.google.com (mail-wg0-f53.google.com [74.125.82.53]) by mx1.freebsd.org (Postfix) with ESMTP id 8E8122B6; Mon, 1 Apr 2013 16:54:25 +0000 (UTC) Received: by mail-wg0-f53.google.com with SMTP id c11so2352298wgh.32 for ; Mon, 01 Apr 2013 09:54:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=/DWbB+8E2FipEAURM1QjjWbA+PBCKt+/wYi9XBxxnT0=; b=B02smOCgG54aDUb+xKXCacnhuCjoUyLxitAS5dpKP32ucrZQ+Xuh37S+kFMUiO0ydK iuZ18ysAUq9OEYMhQRf7/6KAKzLSk3jP7u+GBCNqy4cBRT2dbP1gWZR3I3IbLxgNUPm0 OxlYiHDsK4orKido1xWMJwjwDkXKwdBmBIWfKNBlrQHnevcj9qct/OCU5xmHZ8sFJWli 6mAAaV42EESoMI4dcG2Btnw3uBFC6V2j/nb71pWWgyqSpxKXt6gi4C0WVudaWBqvub7z iXgnjQzU2bk5JoaLXaEEmwuRxavkpKY7xAGEu0wIiKvECYX1ewgiyTf4yb88pz02iuzz hBig== MIME-Version: 1.0 X-Received: by 10.194.22.5 with SMTP id z5mr16763550wje.5.1364835264160; Mon, 01 Apr 2013 09:54:24 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.108.130 with HTTP; Mon, 1 Apr 2013 09:54:24 -0700 (PDT) In-Reply-To: <86k3om5k87.fsf@orwell.Elisa> References: <86sj3as31d.fsf@orwell.Elisa> <86k3oms2ra.fsf@orwell.Elisa> <86k3om5k87.fsf@orwell.Elisa> Date: Mon, 1 Apr 2013 09:54:24 -0700 X-Google-Sender-Auth: MCqI_nrXCDRFgbc0J7iyezLvG8w Message-ID: Subject: Re: [rft] ar9300 HAL updated From: Adrian Chadd To: Raphael Kubo da Costa 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, 01 Apr 2013 16:54:26 -0000 On 1 April 2013 08:44, Raphael Kubo da Costa wrote: > Adrian Chadd writes: > >> Please reboot with 4GB of RAM configured. >> >> See if that fixes it. > > Indeed, booting with hw.physmem="4G" makes the connection much more > reliable -- I do see some of those warnings in the beginning, but they > go away after the connection is established. Yup. Those warnings are fine. I need to trace that down and fix it but it's fine if it happens only whilst scanning. > My gut feeling is that the average connection speed is still below the > one I get when I use my WLAN->Ethernet adapter, but I haven't done any > precise measurements to back that up. It's still a work in progress! WHat's the signal strength? (ifconfig wlan0 list sta gives that to you.) > On a side note: this card is also supposed to provide Bluetooth support, > right? Is any of your work going to help with that as well? Well, bluetooth support will work: * when ath3kfw is patched to include the ability to select an arbitrary USB device id; * when we include the updated ath3k firmware images in the base system. I have the relevant NICs here (AR9462+BT, AR9485+BT) but I haven't yet sat down and tested the bluetooth side. Mostly because I want to focus on wifi, not bluetooth. I haven't yet sat down and figured out the bluetooth coexistence thing yet either. The code is in there, it's just not enabled. So if you load the firmware it'll bring up bluetooth but it and 2GHz wifi will interfere. Adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 1 20:22:01 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D84475B6; Mon, 1 Apr 2013 20:22:01 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x22a.google.com (mail-we0-x22a.google.com [IPv6:2a00:1450:400c:c03::22a]) by mx1.freebsd.org (Postfix) with ESMTP id 480EFE75; Mon, 1 Apr 2013 20:22:01 +0000 (UTC) Received: by mail-we0-f170.google.com with SMTP id z2so2117059wey.1 for ; Mon, 01 Apr 2013 13:22:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=M3QvKlC8evi0DdE8KukHdLKeeMM4YThptTPAC2noCLY=; b=nP2E8cASbq+3SqFGZPnb63jCRtHrmv45F8XCvef8Ychg7nGlbDcb1lj9N3MQOv9Vi2 j3ZFr2nigPVOSE0SVM6Vuvie5NPphCLHgMBwQgu+KaLRJbXlpVcr/AjkNZvsxq2nemEn 0N/PMSV8dlW6MpjpKJyDaWpbNEmpnfxBYuJTt+8Kq2licQdVK2Boh7qEB7o/FEsB444y r+6o3moNfldbITyEgXMUCB0gajlAgEMENXI3mWEvbdSrU9houXb5+ZG5AUlaKjWhDb0J gpbh5QSwAZ9t9KdGlAZNXImiHttUvS04EuJ1CCUUBi8OfSA/4sPb+RqpqnN2TGbRv+ay Vh8w== MIME-Version: 1.0 X-Received: by 10.194.120.169 with SMTP id ld9mr17513938wjb.24.1364847720517; Mon, 01 Apr 2013 13:22:00 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.108.130 with HTTP; Mon, 1 Apr 2013 13:22:00 -0700 (PDT) In-Reply-To: <5158b7db.897aec0a.42d0.ffffaac4@mx.google.com> References: <515892C4.1060002@gmail.com> <5158b7db.897aec0a.42d0.ffffaac4@mx.google.com> Date: Mon, 1 Apr 2013 13:22:00 -0700 X-Google-Sender-Auth: S3RlNUBWTOPuFaCfiZ-ja-8b9lE Message-ID: Subject: Re: ath not working after a motherboard and ram upgrade From: Adrian Chadd To: Joshua Isom , Adrian Chadd 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, 01 Apr 2013 20:22:01 -0000 On 31 March 2013 15:24, Adrian Chadd wrote: > The problem isn't contigmalloc, it's making sure that it gets bounced via > the local 32 bits of address space right. > > I'll talk with other developers and see what the deal is with 64 bit address > space for 32 bit nics. Please do an svn update in sys/dev/ath/ and rebuild. I've fixed something in the RX side. I haven't yet gone and fully reviewed all the descriptor / buffer gymnastics on the TX side so it's very possible things will stay broken until I do that. Thanks, Adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 1 21:04:51 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 5D137A77; Mon, 1 Apr 2013 21:04:51 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-ia0-x22c.google.com (mail-ia0-x22c.google.com [IPv6:2607:f8b0:4001:c02::22c]) by mx1.freebsd.org (Postfix) with ESMTP id 275D112E; Mon, 1 Apr 2013 21:04:51 +0000 (UTC) Received: by mail-ia0-f172.google.com with SMTP id l29so2241609iag.3 for ; Mon, 01 Apr 2013 14:04:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=mZUQsBG4rC1sFVQiysJyK3COiy6/ol9BICNq2Dkiv+8=; b=udU4F7QZQu+mEDa000w4oHezFOpWnvXvh0ZL3slF4kMWh5JodBqhRm3uTmwh0w5ksq GlfiZXHXIMd3qyaU5yte6px/BK8YsfQ5aISO6Lf1oGNOdrULY9vcnUaDRRcEscNfGm4F /tnGLHT+n/SOHK7Mpf92bOiAJCwxSD1F17bo1kGKXo85yuLNnRnIXzR9Shz3vRGpL5YP 2uulQ4wTZ7QwolMAEJam6bL9S3mPTe++0fBponzAzxwMnpH6u4uR22nyo8GTJOE1iCBj 2SjZbSzph8hfRkG97DzLi1avjOSfuWtSLkubirBVZrGYFzxwCmf6ahXIi6UW5Qg+jlC9 ZV7Q== X-Received: by 10.50.135.105 with SMTP id pr9mr4194457igb.6.1364850290881; Mon, 01 Apr 2013 14:04:50 -0700 (PDT) Received: from [192.168.1.34] (c-98-212-197-211.hsd1.il.comcast.net. [98.212.197.211]) by mx.google.com with ESMTPS id ih1sm4386365igc.3.2013.04.01.14.04.49 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 01 Apr 2013 14:04:50 -0700 (PDT) Message-ID: <5159F66B.2040600@gmail.com> Date: Mon, 01 Apr 2013 16:04:43 -0500 From: Joshua Isom User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: ath not working after a motherboard and ram upgrade References: <515892C4.1060002@gmail.com> <5158b7db.897aec0a.42d0.ffffaac4@mx.google.com> In-Reply-To: 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.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, 01 Apr 2013 21:04:51 -0000 I just tested it, the network problem's the same. On 4/1/2013 3:22 PM, Adrian Chadd wrote: > On 31 March 2013 15:24, Adrian Chadd wrote: >> The problem isn't contigmalloc, it's making sure that it gets bounced via >> the local 32 bits of address space right. >> >> I'll talk with other developers and see what the deal is with 64 bit address >> space for 32 bit nics. > > Please do an svn update in sys/dev/ath/ and rebuild. > > I've fixed something in the RX side. I haven't yet gone and fully > reviewed all the descriptor / buffer gymnastics on the TX side so it's > very possible things will stay broken until I do that. > > Thanks, > > > > Adrian > From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 1 21:11:15 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 76FA3BC0 for ; Mon, 1 Apr 2013 21:11:15 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x233.google.com (mail-wi0-x233.google.com [IPv6:2a00:1450:400c:c05::233]) by mx1.freebsd.org (Postfix) with ESMTP id 11D17188 for ; Mon, 1 Apr 2013 21:11:14 +0000 (UTC) Received: by mail-wi0-f179.google.com with SMTP id hn17so1914174wib.12 for ; Mon, 01 Apr 2013 14:11:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=UmKcD4JJyP86PCiGrGlw61KlxlfT4CqtZmDEDm8alqU=; b=X7mTTRsFpAnHGAKCuQZYnVVKht6B/F0dEZhDIDhmILJDZftEwV389koKy4LvV+3dxJ Hk9FjvM7gsswukQpRIIo/8Vm0dkyjp2eQeJU84PNDDQ4irSr7tfgCCrLbk3UgWPkZMi8 0XFRzew9HiHXwAJbCHNrpM1TLod4G/oINxSDPZ5/Mn4/Nn+QZvruSyRqEDajn/WuaTeb TaZC4sBP34Iqz+gPU39XsxhyMRVAErQWwEQq+pNKiCXFSfLZY94FSuzx9/hcPOiRHh5C 0KH8F0kEup44oEYlb2cNvSssDAsMiZoAieaUwkWX1ze7dCWld5JR5c/CEZ+V3fRM0Gi/ 6K3g== MIME-Version: 1.0 X-Received: by 10.180.89.105 with SMTP id bn9mr11767122wib.26.1364850673922; Mon, 01 Apr 2013 14:11:13 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.108.130 with HTTP; Mon, 1 Apr 2013 14:11:13 -0700 (PDT) In-Reply-To: <5159F66B.2040600@gmail.com> References: <515892C4.1060002@gmail.com> <5158b7db.897aec0a.42d0.ffffaac4@mx.google.com> <5159F66B.2040600@gmail.com> Date: Mon, 1 Apr 2013 14:11:13 -0700 X-Google-Sender-Auth: SSz0gXMLFEqIVNJyU4z8o-NNsnc Message-ID: Subject: Re: ath not working after a motherboard and ram upgrade From: Adrian Chadd To: Joshua Isom 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, 01 Apr 2013 21:11:15 -0000 update again again; I just did some TX related changes. adrian On 1 April 2013 14:04, Joshua Isom wrote: > I just tested it, the network problem's the same. > > > On 4/1/2013 3:22 PM, Adrian Chadd wrote: >> >> On 31 March 2013 15:24, Adrian Chadd wrote: >>> >>> The problem isn't contigmalloc, it's making sure that it gets bounced via >>> the local 32 bits of address space right. >>> >>> I'll talk with other developers and see what the deal is with 64 bit >>> address >>> space for 32 bit nics. >> >> >> Please do an svn update in sys/dev/ath/ and rebuild. >> >> I've fixed something in the RX side. I haven't yet gone and fully >> reviewed all the descriptor / buffer gymnastics on the TX side so it's >> very possible things will stay broken until I do that. >> >> Thanks, >> >> >> >> Adrian >> > From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 1 21:29:09 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id BACAD2AB for ; Mon, 1 Apr 2013 21:29:09 +0000 (UTC) (envelope-from gofdw-freebsd-wireless@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) by mx1.freebsd.org (Postfix) with ESMTP id 790E4228 for ; Mon, 1 Apr 2013 21:29:09 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1UMmIE-0002av-S1 for freebsd-wireless@freebsd.org; Mon, 01 Apr 2013 23:29:30 +0200 Received: from a91-154-115-217.elisa-laajakaista.fi ([91.154.115.217]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 01 Apr 2013 23:29:30 +0200 Received: from rakuco by a91-154-115-217.elisa-laajakaista.fi with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 01 Apr 2013 23:29:30 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-wireless@freebsd.org From: Raphael Kubo da Costa Subject: Re: [rft] ar9300 HAL updated Date: Tue, 02 Apr 2013 00:28:56 +0300 Lines: 12 Message-ID: <867gkmaqjr.fsf@orwell.Elisa> References: <86sj3as31d.fsf@orwell.Elisa> <86k3oms2ra.fsf@orwell.Elisa> <86k3om5k87.fsf@orwell.Elisa> Mime-Version: 1.0 Content-Type: text/plain X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: a91-154-115-217.elisa-laajakaista.fi User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.3 (berkeley-unix) Cancel-Lock: sha1:5x1stB6u99tLifaY9j9liBxD1dA= 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, 01 Apr 2013 21:29:09 -0000 Adrian Chadd writes: > On 1 April 2013 08:44, Raphael Kubo da Costa wrote: >> My gut feeling is that the average connection speed is still below the >> one I get when I use my WLAN->Ethernet adapter, but I haven't done any >> precise measurements to back that up. > > It's still a work in progress! WHat's the signal strength? (ifconfig > wlan0 list sta gives that to you.) ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG 00:0c:c3:d9:2a:13 5 6 13M 19.5 0 163 2816 EPS AQEHTRs RSN HTCAP WME ATH WPS From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 1 21:39:33 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 25C1552E for ; Mon, 1 Apr 2013 21:39:33 +0000 (UTC) (envelope-from gofdw-freebsd-wireless@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) by mx1.freebsd.org (Postfix) with ESMTP id D905827E for ; Mon, 1 Apr 2013 21:39:32 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1UMmSD-0007r5-JR for freebsd-wireless@freebsd.org; Mon, 01 Apr 2013 23:39:49 +0200 Received: from a91-154-115-217.elisa-laajakaista.fi ([91.154.115.217]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 01 Apr 2013 23:39:49 +0200 Received: from rakuco by a91-154-115-217.elisa-laajakaista.fi with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 01 Apr 2013 23:39:49 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-wireless@freebsd.org From: Raphael Kubo da Costa Subject: Re: ath not working after a motherboard and ram upgrade Date: Tue, 02 Apr 2013 00:39:13 +0300 Lines: 5 Message-ID: <86eheu3p8e.fsf@orwell.Elisa> References: <515892C4.1060002@gmail.com> <5158b7db.897aec0a.42d0.ffffaac4@mx.google.com> <5159F66B.2040600@gmail.com> Mime-Version: 1.0 Content-Type: text/plain X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: a91-154-115-217.elisa-laajakaista.fi User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.3 (berkeley-unix) Cancel-Lock: sha1:Jqe9CxIeawFnw+j1bdx1ilFAFU8= 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, 01 Apr 2013 21:39:33 -0000 Adrian Chadd writes: > update again again; I just did some TX related changes. No changes as of r248988. From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 1 21:41:47 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 04679571; Mon, 1 Apr 2013 21:41:47 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-ob0-x22a.google.com (mail-ob0-x22a.google.com [IPv6:2607:f8b0:4003:c01::22a]) by mx1.freebsd.org (Postfix) with ESMTP id B7A2A28C; Mon, 1 Apr 2013 21:41:46 +0000 (UTC) Received: by mail-ob0-f170.google.com with SMTP id wc20so2266227obb.15 for ; Mon, 01 Apr 2013 14:41:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=4zAZUnhcIuEX8OCoA+IbTDeoubDSYpcrzKTOYtoL1TY=; b=mQE+B2YZSaCXy+U12P0QYfJSCYM58nKTjhGJpGdH8ZN10wLJ32lfc1ZhJZqZF5Ojun wM2KQnwt8QG+Jr3JHh4tMS36WR1YywbYiJCD8dpSOfYAsJ+b9dUqclmB1TcK05u4nB6w fsh8a5NTfgVNi46YD7cpZwmC/E4rHty5ZnwtVWYRxf+uJCK6e76z/b/+t3Ho4RUR4M3Y VCwfpW2m4hc+swFu+fcoiQoM+rYKzhB8AyCRNsky1TlNyNQZaIrMS2vjysdbmv9Qxeod PYzZCnbkdfEjXl4zdfWnOGBZJftwYwR3rfXilWcs7+SXbt67Bjr4CAn4/eSEE/NKdjw7 MwCw== X-Received: by 10.60.1.73 with SMTP id 9mr4807735oek.129.1364852506169; Mon, 01 Apr 2013 14:41:46 -0700 (PDT) Received: from [192.168.1.34] (c-98-212-197-211.hsd1.il.comcast.net. [98.212.197.211]) by mx.google.com with ESMTPS id gs18sm2751603obb.12.2013.04.01.14.41.45 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 01 Apr 2013 14:41:45 -0700 (PDT) Message-ID: <5159FF12.8030702@gmail.com> Date: Mon, 01 Apr 2013 16:41:38 -0500 From: Joshua Isom User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: ath not working after a motherboard and ram upgrade References: <515892C4.1060002@gmail.com> <5158b7db.897aec0a.42d0.ffffaac4@mx.google.com> <5159F66B.2040600@gmail.com> In-Reply-To: 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.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, 01 Apr 2013 21:41:47 -0000 I was the same. I got these two messages, but I'm only assuming it's related because the val makes me think of the pci id. These were while using 16GB, and trying an ifconfig scan. Apr 1 16:32:51 jri kernel: Memory modified after free 0xfffffe003ce3a000(4096) val=168c000c @ 0xfffffe003ce3a000 Apr 1 16:32:58 jri kernel: Memory modified after free 0xfffffe003ce36000(4096) val=168c000c @ 0xfffffe003ce36000 On 4/1/2013 4:11 PM, Adrian Chadd wrote: > update again again; I just did some TX related changes. > > > > adrian > From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 1 21:46:45 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id D602D879 for ; Mon, 1 Apr 2013 21:46:45 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by mx1.freebsd.org (Postfix) with ESMTP id 708942CC for ; Mon, 1 Apr 2013 21:46:44 +0000 (UTC) Received: by mail-wg0-f44.google.com with SMTP id z12so2541351wgg.35 for ; Mon, 01 Apr 2013 14:46:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=SNNdVGNigLMXEN48+KTheHUowzWgqE/jYMCwaSGZpEk=; b=g8cz66TRZk37CWCTTH/TW+Iwod7h7qexU8Q2p7UfrYJpf/dnyBNXYGhUKG6NIuvMis fMNxyBtgKKIUnRBt5y2an6u32kxtl9aPtAujydMODEj8IvGaIkRhpEHsQsrSmQReJ5U4 lus6jrls4vQy+xT+WMFD1hIXf9JkKn4bbiBPUecVP0w7wui4480VDbGu3flYvTg0lNfo CMvgcsWweLPvpnUDyp9+OeJSzuaolDdV46h2OUY4v/3Lm92GilmSeFaMjS1d/ia2vhtT 5Fywjac9HN0HUDsiF1zmQQs7XXHlDEQZoekLTSyqfSl7XgQBIvA5y14qTGlpC2f8Jvo1 pm7g== MIME-Version: 1.0 X-Received: by 10.181.11.164 with SMTP id ej4mr12115787wid.29.1364852804034; Mon, 01 Apr 2013 14:46:44 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.108.130 with HTTP; Mon, 1 Apr 2013 14:46:43 -0700 (PDT) In-Reply-To: <5159FF12.8030702@gmail.com> References: <515892C4.1060002@gmail.com> <5158b7db.897aec0a.42d0.ffffaac4@mx.google.com> <5159F66B.2040600@gmail.com> <5159FF12.8030702@gmail.com> Date: Mon, 1 Apr 2013 14:46:43 -0700 X-Google-Sender-Auth: icD1rPd2qTpC6fotBFk8qF8ZCdU Message-ID: Subject: Re: ath not working after a motherboard and ram upgrade From: Adrian Chadd To: Joshua Isom 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, 01 Apr 2013 21:46:45 -0000 I'm still trying to chase down the root cause of these. I doubt it's specifically bceause of your particular issue. Adrian On 1 April 2013 14:41, Joshua Isom wrote: > I was the same. I got these two messages, but I'm only assuming it's > related because the val makes me think of the pci id. These were while > using 16GB, and trying an ifconfig scan. > > Apr 1 16:32:51 jri kernel: Memory modified after free > 0xfffffe003ce3a000(4096) val=168c000c @ 0xfffffe003ce3a000 > Apr 1 16:32:58 jri kernel: Memory modified after free > 0xfffffe003ce36000(4096) val=168c000c @ 0xfffffe003ce36000 > > > > On 4/1/2013 4:11 PM, Adrian Chadd wrote: >> >> update again again; I just did some TX related changes. >> >> >> >> adrian >> > > From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 1 22:15:31 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 9732070 for ; Mon, 1 Apr 2013 22:15:31 +0000 (UTC) (envelope-from gromanov@hellok.org) Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0235.outbound.protection.outlook.com [207.46.163.235]) by mx1.freebsd.org (Postfix) with ESMTP id 5F7F03FC for ; Mon, 1 Apr 2013 22:15:30 +0000 (UTC) Received: from BN1PR05MB060.namprd05.prod.outlook.com (10.255.202.153) by BN1PR05MB057.namprd05.prod.outlook.com (10.255.202.139) with Microsoft SMTP Server (TLS) id 15.0.651.16; Mon, 1 Apr 2013 22:10:42 +0000 Received: from BN1PR05MB060.namprd05.prod.outlook.com ([169.254.12.168]) by BN1PR05MB060.namprd05.prod.outlook.com ([169.254.12.168]) with mapi id 15.00.0651.000; Mon, 1 Apr 2013 22:10:42 +0000 From: Gleb Romanov To: "freebsd-wireless@freebsd.org" Subject: 802.11n performance for AR9280 Thread-Topic: 802.11n performance for AR9280 Thread-Index: Ac4vJECdyYHAOVSiQXCZMBDbE5REkQ== Date: Mon, 1 Apr 2013 22:10:41 +0000 Message-ID: <1ca04345430c497abdd21b72680e4e0b@BN1PR05MB060.namprd05.prod.outlook.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [128.239.153.252] x-forefront-antispam-report: SFV:SKI; SFS:; DIR:OUT; SFP:; SCL:-1; SRVR:BN1PR05MB057; H:BN1PR05MB060.namprd05.prod.outlook.com; LANG:en; Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: hellok.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, 01 Apr 2013 22:15:31 -0000 Hello, I have a question about 802.11n performance for AR9280 ( my card is Ubiquit= i SR71E ) in hostap mode. To measure performance, I'm looking at the downlo= ad speeds from my file server (Samba) through a FreeBSD AP to a laptop with= Centrino 6300 (agn 3x3:3). I see 3-4 MBytes/s on the 2.4 GHz band (using ht/20 or ht/40 - doesn't matt= er) and around 5-6 MB/s on the 5 GHz band (ht/40).=20 The laptop is running Win 7 and can do 8-9 MB/s with a commercial AP (2.4 G= Hz ht/20 2x2:2) I run 9.1-RELEASE GENERIC and the question is this is the expected performa= nce (from 9.1 RELEASE ) or I'm just doing something wrong? May be bad anten= nas or wires? If it is expected and I need to switch to HEAD to do better, can I only upd= ate the "ATH_module_releated_stuff" and leave the rest of the base untouche= d? Any comments would be helpful! Gleb ------- Here is some info about the system: Right now it is configured for 2.4 GHz simply because of the range. With 5 = GHz I need to in the same room with the AP to get the speeds I mentioned. uname -a FreeBSD fwall 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:= 10 UTC 2012 root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC = amd64 pciconf -lv ath0@pci0:3:0:0: class=3D0x028000 card=3D0x4e050777 chip=3D0x002a168= c rev=3D0x01 hdr=3D0x00 vendor =3D 'Atheros Communications Inc.' device =3D 'AR928X Wireless Network Adapter (PCI-Express)' class =3D network /etc/rc.conf wlans_ath0=3D"wlan0" create_args_wlan0=3D"wlanmode hostap" ifconfig_wlan0=3D"apbridge mode 11ng ht channel 3:ht/40" hostapd_enable=3D"YES" #for wlan0 hostapd_program=3D"/usr/local/sbin/hostapd" #run from port instead of bas= e ifconfig wlan0: flags=3D8943 metric = 0 mtu 1500 ether 00:15:6d:85:25:13 nd6 options=3D29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng status: running ssid badaboom-n channel 3 (2422 MHz 11g ht/40+) bssid 00:15:6d:85:2= 5:13 country US ecm authmode WPA2/802.11i privacy MIXED deftxkey 2 AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 27 scanvalid 60 protmode CTS -htcompat -ampdu ampdulimit 64k ampdudensity 8 -amsdu smps wme burst dtimperiod 1 -dfs /etc/hostapd.conf:=20 ht_capab=3D[HT40+][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC12][DELAYED-BA= ][MAX-AMSDU-7935][DSSS_CCK-40][LDPC][GF][SMPS-DYNAMIC][PSMP][LSIG-TXOP-PROT= ] (Here I used all available options. I don't see any difference between usin= g the line and commenting it out. Huh?) From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 1 22:21:45 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 0FA83134 for ; Mon, 1 Apr 2013 22:21:45 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by mx1.freebsd.org (Postfix) with ESMTP id A03C060E for ; Mon, 1 Apr 2013 22:21:44 +0000 (UTC) Received: by mail-wg0-f44.google.com with SMTP id z12so2481076wgg.23 for ; Mon, 01 Apr 2013 15:21:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=ggeS5t5uPmkoKnoWic0aFXh/BdV/DlrvTk5EmjFc7M0=; b=SNh5fFBChJrxykt34umP0O/l29o17WBYH19TBtBpL5UY5o249BgpSMTf0nVy+NcYgo UjHpNoToVqSyHUw0gyHaaXStQxKfHNKL1/BCGI3/g3HhXlmdbXDgvly+jy8heUECcI0j 9QKE73PmhqxQdC3u54ohw+6E9wZsZBlPWMxH590Gof6uFG0QXElwl5lnoM95vA2SRMiL tjqYUzSai0M93ktOMyDaG21bkU7xftpXElTXy6X8B4P0dL3wlNnOsuVYzjBEligNBhQk QK6l0as9o3iVT/5O9Y8/o4yc2kFKJEB693bSllOEe49vF+fP35NsaMwTrNNTVLdY1kmC AkHA== MIME-Version: 1.0 X-Received: by 10.180.13.34 with SMTP id e2mr12220212wic.29.1364854903607; Mon, 01 Apr 2013 15:21:43 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.108.130 with HTTP; Mon, 1 Apr 2013 15:21:43 -0700 (PDT) In-Reply-To: <1ca04345430c497abdd21b72680e4e0b@BN1PR05MB060.namprd05.prod.outlook.com> References: <1ca04345430c497abdd21b72680e4e0b@BN1PR05MB060.namprd05.prod.outlook.com> Date: Mon, 1 Apr 2013 15:21:43 -0700 X-Google-Sender-Auth: pvo1UMTZddD2TH4NWV7LgRUdI9k Message-ID: Subject: Re: 802.11n performance for AR9280 From: Adrian Chadd To: Gleb Romanov 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, 01 Apr 2013 22:21:45 -0000 Hi, 9.x doesn't implement 11n aggregation transmission. It only supports 11n MCS rate transmission (with no aggregation) and 11n RX with MCS and aggregation. If you update to -HEAD you should see the performance increase. Adrian On 1 April 2013 15:10, Gleb Romanov wrote: > Hello, > > I have a question about 802.11n performance for AR9280 ( my card is Ubiquiti SR71E ) in hostap mode. To measure performance, I'm looking at the download speeds from my file server (Samba) through a FreeBSD AP to a laptop with Centrino 6300 (agn 3x3:3). > I see 3-4 MBytes/s on the 2.4 GHz band (using ht/20 or ht/40 - doesn't matter) and around 5-6 MB/s on the 5 GHz band (ht/40). > The laptop is running Win 7 and can do 8-9 MB/s with a commercial AP (2.4 GHz ht/20 2x2:2) > > I run 9.1-RELEASE GENERIC and the question is this is the expected performance (from 9.1 RELEASE ) or I'm just doing something wrong? May be bad antennas or wires? > If it is expected and I need to switch to HEAD to do better, can I only update the "ATH_module_releated_stuff" and leave the rest of the base untouched? > Any comments would be helpful! > > Gleb > > > ------- > Here is some info about the system: > Right now it is configured for 2.4 GHz simply because of the range. With 5 GHz I need to in the same room with the AP to get the speeds I mentioned. > > uname -a > FreeBSD fwall 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 > > pciconf -lv > ath0@pci0:3:0:0: class=0x028000 card=0x4e050777 chip=0x002a168c rev=0x01 hdr=0x00 > vendor = 'Atheros Communications Inc.' > device = 'AR928X Wireless Network Adapter (PCI-Express)' > class = network > > /etc/rc.conf > wlans_ath0="wlan0" > create_args_wlan0="wlanmode hostap" > ifconfig_wlan0="apbridge mode 11ng ht channel 3:ht/40" > hostapd_enable="YES" #for wlan0 > hostapd_program="/usr/local/sbin/hostapd" #run from port instead of base > > ifconfig > wlan0: flags=8943 metric 0 mtu 1500 > ether 00:15:6d:85:25:13 > nd6 options=29 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng > status: running > ssid badaboom-n channel 3 (2422 MHz 11g ht/40+) bssid 00:15:6d:85:25:13 > country US ecm authmode WPA2/802.11i privacy MIXED deftxkey 2 > AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 27 scanvalid 60 > protmode CTS -htcompat -ampdu ampdulimit 64k ampdudensity 8 -amsdu > smps wme burst dtimperiod 1 -dfs > > /etc/hostapd.conf: > ht_capab=[HT40+][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC12][DELAYED-BA][MAX-AMSDU-7935][DSSS_CCK-40][LDPC][GF][SMPS-DYNAMIC][PSMP][LSIG-TXOP-PROT] > (Here I used all available options. I don't see any difference between using the line and commenting it out. Huh?) > _______________________________________________ > 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 Mon Apr 1 22:38:22 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id D860A48C; Mon, 1 Apr 2013 22:38:22 +0000 (UTC) (envelope-from gromanov@hellok.org) Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0205.outbound.protection.outlook.com [207.46.163.205]) by mx1.freebsd.org (Postfix) with ESMTP id 828316AE; Mon, 1 Apr 2013 22:38:21 +0000 (UTC) Received: from BN1PR05MB060.namprd05.prod.outlook.com (10.255.202.153) by BN1PR05MB057.namprd05.prod.outlook.com (10.255.202.139) with Microsoft SMTP Server (TLS) id 15.0.651.16; Mon, 1 Apr 2013 22:38:13 +0000 Received: from BN1PR05MB060.namprd05.prod.outlook.com ([169.254.12.168]) by BN1PR05MB060.namprd05.prod.outlook.com ([169.254.12.168]) with mapi id 15.00.0651.000; Mon, 1 Apr 2013 22:38:12 +0000 From: Gleb Romanov To: Adrian Chadd Subject: RE: 802.11n performance for AR9280 Thread-Topic: 802.11n performance for AR9280 Thread-Index: Ac4vJECdyYHAOVSiQXCZMBDbE5REkQAAwlCAAAAwcbA= Date: Mon, 1 Apr 2013 22:38:12 +0000 Message-ID: <58ea1b99a8c24d3bbda383ad87f05f46@BN1PR05MB060.namprd05.prod.outlook.com> References: <1ca04345430c497abdd21b72680e4e0b@BN1PR05MB060.namprd05.prod.outlook.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [128.239.153.252] x-forefront-antispam-report: SFV:SKI; SFS:; DIR:OUT; SFP:; SCL:-1; SRVR:BN1PR05MB057; H:BN1PR05MB060.namprd05.prod.outlook.com; LANG:en; Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: hellok.org 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, 01 Apr 2013 22:38:22 -0000 Thanks! Do you recommend to update everything or only ATH module will be enough? IE get all the sources and follow https://www.freebsd.org/doc/en_US.ISO8859= -1/books/handbook/makeworld.html Or Download the ATH sources and "make all install" ? Gleb > -----Original Message----- > From: adrian.chadd@gmail.com [mailto:adrian.chadd@gmail.com] On > Behalf Of Adrian Chadd > Sent: Monday, April 01, 2013 6:22 PM > To: Gleb Romanov > Cc: freebsd-wireless@freebsd.org > Subject: Re: 802.11n performance for AR9280 >=20 > Hi, >=20 > 9.x doesn't implement 11n aggregation transmission. It only supports 11n > MCS rate transmission (with no aggregation) and 11n RX with MCS and > aggregation. >=20 > If you update to -HEAD you should see the performance increase. >=20 >=20 >=20 > Adrian >=20 > On 1 April 2013 15:10, Gleb Romanov wrote: > > Hello, > > > > I have a question about 802.11n performance for AR9280 ( my card is > Ubiquiti SR71E ) in hostap mode. To measure performance, I'm looking at > the download speeds from my file server (Samba) through a FreeBSD AP to a > laptop with Centrino 6300 (agn 3x3:3). > > I see 3-4 MBytes/s on the 2.4 GHz band (using ht/20 or ht/40 - doesn't > matter) and around 5-6 MB/s on the 5 GHz band (ht/40). > > The laptop is running Win 7 and can do 8-9 MB/s with a commercial AP > > (2.4 GHz ht/20 2x2:2) > > > > I run 9.1-RELEASE GENERIC and the question is this is the expected > performance (from 9.1 RELEASE ) or I'm just doing something wrong? May be > bad antennas or wires? > > If it is expected and I need to switch to HEAD to do better, can I only > update the "ATH_module_releated_stuff" and leave the rest of the base > untouched? > > Any comments would be helpful! > > > > Gleb > > > > > > ------- > > Here is some info about the system: > > Right now it is configured for 2.4 GHz simply because of the range. Wit= h 5 > GHz I need to in the same room with the AP to get the speeds I mentioned. > > > > uname -a > > FreeBSD fwall 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 > 09:23:10 UTC 2012 > root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 > > > > pciconf -lv > > ath0@pci0:3:0:0: class=3D0x028000 card=3D0x4e050777 chip=3D0x002= a168c > rev=3D0x01 hdr=3D0x00 > > vendor =3D 'Atheros Communications Inc.' > > device =3D 'AR928X Wireless Network Adapter (PCI-Express)' > > class =3D network > > > > /etc/rc.conf > > wlans_ath0=3D"wlan0" > > create_args_wlan0=3D"wlanmode hostap" > > ifconfig_wlan0=3D"apbridge mode 11ng ht channel 3:ht/40" > > hostapd_enable=3D"YES" #for wlan0 > > hostapd_program=3D"/usr/local/sbin/hostapd" #run from port instead of > base > > > > ifconfig > > wlan0: > flags=3D8943 metric > 0 mtu 1500 > > ether 00:15:6d:85:25:13 > > nd6 options=3D29 > > media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng > > status: running > > ssid badaboom-n channel 3 (2422 MHz 11g ht/40+) bssid > 00:15:6d:85:25:13 > > country US ecm authmode WPA2/802.11i privacy MIXED deftxkey 2 > > AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 27 scanvalid 60 > > protmode CTS -htcompat -ampdu ampdulimit 64k ampdudensity 8 - > amsdu > > smps wme burst dtimperiod 1 -dfs > > > > /etc/hostapd.conf: > > ht_capab=3D[HT40+][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX- > STBC12][DELAYED > > -BA][MAX-AMSDU-7935][DSSS_CCK-40][LDPC][GF][SMPS- > DYNAMIC][PSMP][LSIG-T > > XOP-PROT] (Here I used all available options. I don't see any > > difference between using the line and commenting it out. Huh?) > > _______________________________________________ > > 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 Mon Apr 1 22:42:21 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id F266B4D5 for ; Mon, 1 Apr 2013 22:42:21 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x233.google.com (mail-we0-x233.google.com [IPv6:2a00:1450:400c:c03::233]) by mx1.freebsd.org (Postfix) with ESMTP id 8BAF76CD for ; Mon, 1 Apr 2013 22:42:21 +0000 (UTC) Received: by mail-we0-f179.google.com with SMTP id p43so2048809wea.38 for ; Mon, 01 Apr 2013 15:42:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=AXg6w9IThNIauCcMKHlBYvrLS4D5WShyw/mU42dVboY=; b=THwedxo4HhXQpGjmcC1pcBHrpWkDe4Gp4LSZTIeOhqN39MaI+YSnHwJMrCaw0g5uwI zPf/3LjtPkMHxLGmOyruySQkTWkyJoGJfVJGcbHnVMS//fqJwWP/SoknomxWttSY++25 nMdF3WOUGPkx60D6lD8tYrPD7TKr7ReiuhHx+KctgerLxUQ72eXZuofOBfV2RK4KJPHb uK09jjBO870N3YEHMFrNBkcYw694IPtyePVoheRGVF9dcfITpJcwxYjgJ+u2pftxbsF4 PbCHixWi9WpduFXYDwMk0Q8IJ93C3GN5Acb3l3QVg8Axr9p6JPV7Fli6HH5I2gD0HsBG dcIA== MIME-Version: 1.0 X-Received: by 10.181.11.164 with SMTP id ej4mr12282950wid.29.1364856140695; Mon, 01 Apr 2013 15:42:20 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.108.130 with HTTP; Mon, 1 Apr 2013 15:42:20 -0700 (PDT) In-Reply-To: <58ea1b99a8c24d3bbda383ad87f05f46@BN1PR05MB060.namprd05.prod.outlook.com> References: <1ca04345430c497abdd21b72680e4e0b@BN1PR05MB060.namprd05.prod.outlook.com> <58ea1b99a8c24d3bbda383ad87f05f46@BN1PR05MB060.namprd05.prod.outlook.com> Date: Mon, 1 Apr 2013 15:42:20 -0700 X-Google-Sender-Auth: iV5vZez2BAno7S83Rex6SLXdJG4 Message-ID: Subject: Re: 802.11n performance for AR9280 From: Adrian Chadd To: Gleb Romanov 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, 01 Apr 2013 22:42:22 -0000 On 1 April 2013 15:38, Gleb Romanov wrote: > Thanks! > > Do you recommend to update everything or only ATH module will be enough? I suggest that people who wish to try the ath 11n support update and track -HEAD. Make sure you add this to your kernel config as well: options ATH_ENABLE_11N options ATH_DEBUG options AH_DEBUG options ATH_DIAGAPI There may be occasional issues with -HEAD as it's the development branch. So just keep that in mind. Thanks, Adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 1 22:47:53 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 22E338AA for ; Mon, 1 Apr 2013 22:47:53 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-f54.google.com (mail-wg0-f54.google.com [74.125.82.54]) by mx1.freebsd.org (Postfix) with ESMTP id B16DE6F9 for ; Mon, 1 Apr 2013 22:47:52 +0000 (UTC) Received: by mail-wg0-f54.google.com with SMTP id a12so2497963wgh.33 for ; Mon, 01 Apr 2013 15:47:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=wJ7Z8Tnloc3hzxfLzhfSxyL1Z15cYkn9Sc60IzEnYbc=; b=bOLoWp9oIVgvTfnqGDWrzohVfzbWTnvssDJULwKulFsvP5RWCjlwj+XC0vJhHc+mzu eOTMl6zXU6Rq6JlrX/g+5LMlXTjksmA6tyzpNJ3NUyhNOxQeRbch2B6n7hHDgM2QOa0o AVEAB7dDGrmMsjKeP0lLwtC0y/ztLROLD6IkHIIL9GU5gDaDU04ul7MN9byZjsEvHw3P UKdUY4Kn7zdy8LqAYm+pVBykc4k7+p7E/vvLJJtsLGtc+Qf0G+pz1UUvp7v74GxYF+D+ iycALMgAH00zPJSw5DrI1heRt/1Ny2k6r70U7BlitwOlmU1/Yp96n/p3yiOok2Os+wq1 P5Lg== MIME-Version: 1.0 X-Received: by 10.194.171.74 with SMTP id as10mr18017787wjc.0.1364856465494; Mon, 01 Apr 2013 15:47:45 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.108.130 with HTTP; Mon, 1 Apr 2013 15:47:45 -0700 (PDT) In-Reply-To: <5159FF12.8030702@gmail.com> References: <515892C4.1060002@gmail.com> <5158b7db.897aec0a.42d0.ffffaac4@mx.google.com> <5159F66B.2040600@gmail.com> <5159FF12.8030702@gmail.com> Date: Mon, 1 Apr 2013 15:47:45 -0700 X-Google-Sender-Auth: bIKKiiSr1ykfPmt-NB-9lRF_T_g Message-ID: Subject: Re: ath not working after a motherboard and ram upgrade From: Adrian Chadd To: Joshua Isom 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, 01 Apr 2013 22:47:53 -0000 ... and that particular value means that some TX descriptor was written into free'd memory. Sigh. As I said, I'll chase this down later, but I don't think it's the root cause of your bug. I still have a lot more review of the TX path and descriptor handling but it may take some time. Thanks, adrian On 1 April 2013 14:41, Joshua Isom wrote: > I was the same. I got these two messages, but I'm only assuming it's > related because the val makes me think of the pci id. These were while > using 16GB, and trying an ifconfig scan. > > Apr 1 16:32:51 jri kernel: Memory modified after free > 0xfffffe003ce3a000(4096) val=168c000c @ 0xfffffe003ce3a000 > Apr 1 16:32:58 jri kernel: Memory modified after free > 0xfffffe003ce36000(4096) val=168c000c @ 0xfffffe003ce36000 > > > > On 4/1/2013 4:11 PM, Adrian Chadd wrote: >> >> update again again; I just did some TX related changes. >> >> >> >> adrian >> > > From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 2 03:24:27 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 11B2422E for ; Tue, 2 Apr 2013 03:24:27 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-f46.google.com (mail-wg0-f46.google.com [74.125.82.46]) by mx1.freebsd.org (Postfix) with ESMTP id 9EED620B for ; Tue, 2 Apr 2013 03:24:26 +0000 (UTC) Received: by mail-wg0-f46.google.com with SMTP id l18so2610646wgh.1 for ; Mon, 01 Apr 2013 20:24:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=VGe9g2PLFVXDd8er5lG2rG57XVsWkfFpoERk4jQJqPM=; b=bMjRrIHKhQHm26886jHv4TPdWUmV5s/gvB/0km5RVOYAV8yiYBtqbG6DU1uh3382Aj wcBrbKNIhgnvQNpJ/tFjNBZhKOZdW+XkWdMPbmHmiVrONe4k/wUdOR2y1u357Gjzr9wL 7jKsQh8VwpDDIUEqqcc54zFE4//howpKvyIrXKvHnKrxphMNv8HVjJAM4hu1zrjG/MMu b4cKkiqtJeChdb2uOE9HwC5YpmHmCXcUsOoIN5EE5TRDbDXjiEnTpWZ7Q4VEooAXy/Ca U4eZmPU+EtnvwK1PnurR4vPHAoL/Ti55IBaoxV6VcyYHFv1QoKc8uxrUdeIvKen8Zo9o op2g== MIME-Version: 1.0 X-Received: by 10.180.89.105 with SMTP id bn9mr12796301wib.26.1364873065395; Mon, 01 Apr 2013 20:24:25 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.108.130 with HTTP; Mon, 1 Apr 2013 20:24:25 -0700 (PDT) In-Reply-To: References: <515892C4.1060002@gmail.com> <5158b7db.897aec0a.42d0.ffffaac4@mx.google.com> <5159F66B.2040600@gmail.com> <5159FF12.8030702@gmail.com> Date: Mon, 1 Apr 2013 20:24:25 -0700 X-Google-Sender-Auth: 85V1s6qxD-wOLcBLP9jx7y4oIHc Message-ID: Subject: Re: ath not working after a motherboard and ram upgrade From: Adrian Chadd To: Joshua Isom 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, 02 Apr 2013 03:24:27 -0000 Hi Joshua, Would you please reboot back into full RAM, let it fail for a bit, then record dmesg: dmesg > ~/dmesg.txt and sysctl: sysctl dev.ath.0 > ~/sysctl.txt then reboot back to normal, and email me those two textfiles? Thanks, Adrian From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 2 03:40:21 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 510F3520 for ; Tue, 2 Apr 2013 03:40:21 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) by mx1.freebsd.org (Postfix) with ESMTP id DCEE029E for ; Tue, 2 Apr 2013 03:40:20 +0000 (UTC) Received: by mail-wi0-f170.google.com with SMTP id hm11so2740378wib.5 for ; Mon, 01 Apr 2013 20:40:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=KYS2pNdRNNLTghfRroD/lhBooF5HGtI3UbNJ6yTB4S4=; b=HUz7l+oBKJvoDFdODZBuUCIt3QVGFnZAjmDLk3zW60IP5wrZ08cEB4mNpfa8alFBLN zPslpO2a6OsN1qcbw9anc6/JmC6yNXugKqd+DeFrXqXNVMz8JW43SZAppQtN4ygu13+i IL8wOZDKCue2kqGAV4r6jMkVVyEyFXe1KWCvrKQjyYa38kEfUn+zCJv/ue0Wazm8DQIM wgw3XpKfoG5EYcS+N7BdeQAVgPzXKjE35XIbejM+s1z3iPKsja0T+/yDlnUKnV0zR5LM pxmSWC9DvXecHsR4+E7NocN5tEDv2ZO4fpxCWV2IceQm9AXxPB+MDL7X/eDuWA7cjXw9 aCkg== MIME-Version: 1.0 X-Received: by 10.180.81.232 with SMTP id d8mr12976825wiy.25.1364874020050; Mon, 01 Apr 2013 20:40:20 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.108.130 with HTTP; Mon, 1 Apr 2013 20:40:19 -0700 (PDT) In-Reply-To: References: <515892C4.1060002@gmail.com> <5158b7db.897aec0a.42d0.ffffaac4@mx.google.com> <5159F66B.2040600@gmail.com> <5159FF12.8030702@gmail.com> Date: Mon, 1 Apr 2013 20:40:19 -0700 X-Google-Sender-Auth: ePWf4n048kdNEhwRuke68yG8mrc Message-ID: Subject: Re: ath not working after a motherboard and ram upgrade From: Adrian Chadd To: Joshua Isom 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, 02 Apr 2013 03:40:21 -0000 .. and please supply the output of 'sysctl hw.busdma' too when it's failing: sysctl hw.busdma > ~/sysctl-busdma.txt and include that too. Thanks, adrian On 1 April 2013 20:24, Adrian Chadd wrote: > Hi Joshua, > > Would you please reboot back into full RAM, let it fail for a bit, > then record dmesg: > > dmesg > ~/dmesg.txt > > and sysctl: > > sysctl dev.ath.0 > ~/sysctl.txt > > then reboot back to normal, and email me those two textfiles? > > Thanks, > > > Adrian From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 2 06:35:26 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 9B778968 for ; Tue, 2 Apr 2013 06:35:26 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) by mx1.freebsd.org (Postfix) with ESMTP id 3389BADB for ; Tue, 2 Apr 2013 06:35:26 +0000 (UTC) Received: by mail-wi0-f170.google.com with SMTP id hm11so2819981wib.3 for ; Mon, 01 Apr 2013 23:35:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=bPnQQ8XbRzdyNqLsLZCOzNcKtNyTgj5DaSQ24AN22do=; b=ECMMt6XSN2+1J4y6ELkK9oJn8tQ6ypR879AUY0g9uR7aDDThWeQLc74GXx6vo77/zF G59EGh0jqfFoQDLtqUSWgSP3E6DQzZqIOxlr6wxaibso7aKr9+eetIPO3YTUhXneDckQ mjSXV8di6+ptiCofQ7HIDN8gSprcIHM6BAR9OLpMyebqUIiKp2aVD4DBB7rd3mTNrtTW xH/pOjDx+8xLAbb50vS/jo43IoUILzCiwS1Yyw6PQzuNYUe3we52X2WLhK+BYWhcdeUF ZaJ9I+gpONYGjSuNHdkdEaAPX0xDN71HrpMycTQ8oBFGhVbtAbpIDNsCW2INHsDKNGEP qFZw== MIME-Version: 1.0 X-Received: by 10.194.120.169 with SMTP id ld9mr19360763wjb.24.1364884525410; Mon, 01 Apr 2013 23:35:25 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.108.130 with HTTP; Mon, 1 Apr 2013 23:35:24 -0700 (PDT) In-Reply-To: References: <515892C4.1060002@gmail.com> <5158b7db.897aec0a.42d0.ffffaac4@mx.google.com> <5159F66B.2040600@gmail.com> <5159FF12.8030702@gmail.com> Date: Mon, 1 Apr 2013 23:35:24 -0700 X-Google-Sender-Auth: HNc66Lsruo62Pqd2yegoE8WuRn0 Message-ID: Subject: Re: ath not working after a motherboard and ram upgrade From: Adrian Chadd To: Joshua Isom 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, 02 Apr 2013 06:35:26 -0000 .. and there's been some more work in -HEAD, so please svn update first! Thanks, adrian From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 2 21:31: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]) by hub.freebsd.org (Postfix) with ESMTP id 208C761C; Tue, 2 Apr 2013 21:31:18 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-ve0-f173.google.com (mail-ve0-f173.google.com [209.85.128.173]) by mx1.freebsd.org (Postfix) with ESMTP id BF72ACD8; Tue, 2 Apr 2013 21:31:17 +0000 (UTC) Received: by mail-ve0-f173.google.com with SMTP id cy12so1126682veb.4 for ; Tue, 02 Apr 2013 14:31:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type; bh=dS7hnYynp8dpbdaf+1kZAJEsyVo0654BaG5eQXqa68w=; b=Ru21dWGj1X9A6gH6eaj9uZLdJl5/wUsdMyXHa7nW944z6eO1gBmudDyZFmCaUmaDFe UkRbd47TvR77ZvRAymwiTO3EHmeh4n04GYhZ0biT7fppT47lmiCb4t6Ok5JiKfouFqFs 1YOtD84ExStGeG1VxIdE0SArmqdLqMfSK6DsMkVXJD4/7edCIqf8zNEuZKpw+L9gdTQS AqjWp+KRh17sKvkG33Z6yZ50s9igweKISPmFHDd4njMWGb5DeDmPRBpkbt5o4mpjAxgc 2vHLg7NxDy2xwZyMFYWAFRjgUx4FlXK27ccH3Rqj2Wa5fklbSauGeQVP5Dvd8VinxuQm 0Xug== X-Received: by 10.52.230.10 with SMTP id su10mr11964490vdc.50.1364938271108; Tue, 02 Apr 2013 14:31:11 -0700 (PDT) Received: from [192.168.1.34] (c-98-212-197-211.hsd1.il.comcast.net. [98.212.197.211]) by mx.google.com with ESMTPS id dz9sm3592146vdc.4.2013.04.02.14.31.09 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 02 Apr 2013 14:31:10 -0700 (PDT) Message-ID: <515B4E16.3050901@gmail.com> Date: Tue, 02 Apr 2013 16:31:02 -0500 From: Joshua Isom User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: ath not working after a motherboard and ram upgrade References: <515892C4.1060002@gmail.com> <5158b7db.897aec0a.42d0.ffffaac4@mx.google.com> <5159F66B.2040600@gmail.com> <5159FF12.8030702@gmail.com> In-Reply-To: Content-Type: multipart/mixed; boundary="------------040204090703080205080907" 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, 02 Apr 2013 21:31:18 -0000 This is a multi-part message in MIME format. --------------040204090703080205080907 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit sysctl.1.txt is right after boot, sysctl.2.txt is while failing. One thing different when using 4GB is that hw.busdma.zone0.lowaddr is 0xfffffffffffffff, 60 bits and not 64, but when 32GB it's 0xffffffff, 32 bits. I don't know if that has anything to do with it, but it seems strange. On 4/2/2013 1:35 AM, Adrian Chadd wrote: > .. and there's been some more work in -HEAD, so please svn update first! > > Thanks, > > > adrian > --------------040204090703080205080907 Content-Type: application/octet-stream; name="logs.tgz" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="logs.tgz" H4sIAHBIW1EAA+09a3PjNpL79fQrsNm6OrtGkgG+RGkzUyvL9tiV0VixNJPJplI6igQtxuJj SMqW8+uvGyQlUuLDk8lmHyckkUX0A41Go9EAmorl8ui+G2/iP/3jCqVUUxSCf6Hs/5V7ikQJ k5ikaYqsSSqhTKay9CdC/4Eybcs6io0QRAl9v1YHT0vOVzXw/c79m5SRHzyHzv0yJifmKWH9 vtSRQP9ktuTkKuT8fHpBJqH/Czfjbmsfuddvw6dOxacsPjXxqYtPAe0z8SmJT4HTV1r/hezv +D334oj4Nonh8YPnPPIwcuJnrBkZK8f2Q88xumS4WhHRbERCHvHwkVvdViacExEDqu+dKOYh t0gcGhZ3jfABueR7ceWvPcuIHd/bETPapZ3Rh7u7y/cz8hfGSCgpfbC98YDM1pwMg5AQiTB1 IOsDVSWjixlB7bQIFDSYv/0SOt2l7/K152y6pu8OztZReOYvfjlD8Nlwdn225IZ1Fj1H+EAM 19KUbfPmyvDuiei17xG5K5GT2LiPzu4u310Op5dzWTqzHc9YEdajPUZPsXGYJxJr/TC8e3/z /u2A/HAze385nRI/wJ4R7hmLFbfahG8CGDJQjLU2QSsBD0GbruGZHIZx8mFAhuMLMoyXK987 id1TcnNDPilEk1UcbZNHkR+SE6nP+l1V64yvfyXf6R0QN4oIUJ+CAm5hRByPvCbfDNcwfF7s mMDyG0JuLKikG0aprcqEXBmus3pOqwgZ+xZfiSeVkGnMg8ABFbwmqNMrbsRrGOHXgNrTF/bC tr+9mnxofxxfti8u25PpZXs2HbXH07v2ZHjZHo8u26NPens4uRm1p5eT9nh2B5C3CBm2R+Pb j4A2QzJZa4/eXb37ML1uj8ef2lefgMMUuMF/Uvt6NnuTa1yC1nUqUdr/FsBye3z7HlphWnty Oxm9F6ioupysnKuU6pR+O/1xOhq+e9d+/wmbedW+Eg1NjHvO3p637y5A+En73bgtX7z3n/78 Kv27zxEFkHvQ9XfD6yvoxqQ9/ThuX25i0c/RHXT4fIyiK8P2eDhtT0Ju89hctm+nH39o35xP 29Pvbt7fzNo/XAhpodUBmXTAzcWcON6jETqGF7dCDnblctcPnwnqX5HVfk/WZU0nJ7LUgz/j 89OW8Wg4WzTAYn1ZUanS1yhgUQXmBGJdPsL4k9hxeUi+eYdyfkM+r2EGw1xWKG0NR5MbgtVk huY5IN++PZ/hHII/HxD4JpsSZ9PxZEDG61XsBFs7nD7D3HbJBY/BpLk1IAoaYVSkYSQwzAfQ 9Ul0SjaAYvohfm8RM1iDtOfTyekgEeLmYkAIFQBGTobFeibqpYN6SdTLB/Vyy/GNwDHpgIyW MJ3RnFMoiX2iZ2Dy7cd0nktd9oY44eeI0I4kE6hxfZhB4cI3Qqvl+tZ6xeeZR5s7nhODRm4v 5u9uhxfk5JFHRhumj50WnS4sjS3AB4N/4GEI+tJaDwuLESMm8Nddb2jLMAOHpmrf6ny/5RRp 4j/BMJ6v4xjgJ7az4dZpBkvcr3Ci6F6hUUOsdifyKbHBUrhVgcnEqtgmC9s8oMDxAdmEkcC4 CrkEF4SwSohUCZHLIUYsLFS0NUus9Q0J/DAGbSq0Ax/yDnkGYBNWjBhN2tElVfmG2CH/vOae +UwYzAOmSwT8YmbntDgLXkICSmktAx6jRNewvoHr5aYjbCThNUtkdGCBcXHIuSXU2Em/yraN dgTDoFcIfj25nBWEUEAGptO8FH0VVRPGZqoYdAzYCVidfPNhq6EeNtvLaajQ3bvZKN9O4kAK 2inIhaPTsY0oLhCpvb6qqAXZaGK78+3IyVJn4WTNgoXL3YQKlqitqDrVO/i5yI09MlkIm0Yu eRvPWUhgOoutKV77UdyZjG7IInSse77lbtrI3QTd5+m2ZIJiHQmugp/gynLgAlMcP6ZjTyz+ 6JgcvANNSQUlq+LLWo/3Rtrwx7fDDgQfAUw3cK/EcqJgZTxvJbZsYTOW3bNJakkLurWkReJH 2tAnuq017W2txbe1Vlp7KDXdSs1aS8sQtvT+483FzZCc0A1dcJju1xdDMvK9OPRXKzTrVBRo ykxFMfPs+wX2bMseOy/VqlPLUSpFdUpV6pRam2WizE/XADqB0JSHDkS5H6bnYGQUlpMDyS0L vG8iuWXlJNdKFbNtQVPI4hnWYuTINzGJnF8hKFtHII7AFWiim3JtN3u5ZtRiN+Wqbsow1ZfC VtHv+xEZ3vVlfbPr0sLM7MJaWLsu9Uq7BNzCvkzpPOLxPIrXi7m99kz0+dGAQF2MiyHWk239 b6cA922YywExjdUKsdLq5VMKae1XHKByDjGFu4duQ1C7nLtGMCAQxLvBirvg1yBkhniZeP5T 645HsR8iG9iTENhBGOCzfAhH7objSuDl5eTudlwiUpko4HIh8vOgTZoOz90ngvHaOiIr7t3H QKfoO9BibdvgvtBuAED7WgqafYIhiszQCUCmLSWT9B18j6ucI024RrhVyLGBBraagnBrEVk4 dOtgvpnHmzniJWrGPQdM9DNa/JOyh885t1wjpQ03NmzuBiR+DvhrQL26ubqFNoN4CTEmTB8Y gNDh0QuI2T6xpO9R/3Q9+znZFuEoXc8g5LEqgNES/GXn7Q1EybDTwk0P4uZRGSgQ1keXTGfn Ixg2k8OeNdt0VSPCntSLXFi2SjDlZLAROforPM22TymWmKGUuIZJFEXvAv6VymArFSyfcSqm WNJbEBe2vg5oBjQP5a9EPagTXkWp9Sp5t9srehWlyquAiaTOc2zA7hy267o+vewzaUOG6E2n w9mw4EDThclIFib404OFxuDJE6cyPlnJk5XAzOTJTGCL5GlBtwua1bftzHHB1175KpJ1Zyuw EO+RdSVKnhywIJ1obxdBJASM2hALg5zJbmTlcPQH4K7XAUJxFIGHmXhTZGNC+O/x1RtsMf1O RIOirRSb1WGzfWypDlvax5brsOV9bKUOW9nHVuuw1X1srQ5b28fu1WH3cthxFvAcmNmHi/GQ yXKpkRmJsRiJIfWTp35iSHrypCewXvLUS2Ba8qQVjIzvjAy+li74bGtkODfUF6/h/eJsU6tm m5pBPR4/+eFDm3BczOHpzZ6xn3g+sUI8ViPJSoNbOWShvTgcZbQolVYllSbCG/ZlARTbBVCs MbLctlATQLEsgGLCtsRsm92Qm08TGNt6Z2QnzshOnJHN032WsAXbSqVMYGYariawRRpH5+zE 3jkj+CqXOSOWd66prPveSKv3RvueSH+RJ2Ipdv9FnijDZrVuTjpAr/Vz8gF6raNTDtBrPZ26 Q/fTZQnP16bnPYhIpue6+OxvqLDMMqu0d7McvpZaJdNzoycsT6hAtNfija1KFfPBRkPLWrZo WfQNLUvFlkEZl8Jw0vMl1s0AiCeEEYpgv0ER5k4cs1wR/X1FKJkimFBEfavViljsWl6UK6K/ rwi1ShFqpgiWbdUj8E0QsAOsTabjc/RjuS14pe/ErW3mU6bnsEBUbWpBamXXgV7p1hCa2XXA iQxx9IAO+WY63DrkArqcR0dsgZk6YcFBePdelXcvMFPybr1X5dZ7GTSvsSsn5D/Af3mOTKlS GtqC9Btsz9gp0Ci1PeiEWrQALbM9SShCf4EiWHF906sUoYt+yL+hH/1dP/rl/ZD251Av64cs 5lC99qrnkL5rWS+dQ9Dy3hzSq+aQns0hqWW4VszdIHNxo8kHcut1LhyO922hC1Yy5V7kh4ny ln4Uww5hbYTioJNpqgq9DcnuwGq7BMviaC1bLhUCe/P7KLk42p61ReJsKb0SgG5H/ioZ0B0y TadDivzx7RCbJY9OGK9BuJQI7FiQ4HULpW/wOE0ckSdxC8GpBZSCdSaeidqULXt7ImukhyXi DG3bqhE/LCwh5nf8WZyt58aHnDg6VaTTPGONQhyhKUUG6XFsxiKNzYQiEv54yk+RS4K+pfrp 7c3w/azz7nb03eXFz60gQFFMWBv9OLs/JTdnt0njsDO9563lUyDuh7DNke+v/tf7n+/XDo/R tsQg4hl96+9XU2I7oLlE+amJDIgqIHgQYtxzYOuvdjA7vdXKghVyooLKTvPHwRGJHfOBcKB5 RnuD8XMjbgpnmz9IfDuT2CZxuLcXl6NkzTesJLIRh45IYhxQDNewAyZX6XkSeRv660AQe46V KDRpCaa/e0B8cn0xvjm7mBDdXJ5uqdSUyqCJlKxZSlaU8oDihVLiCuYeEDdImZzJmlKzlFJR ygOKF0qJ7tc9IG6QUkqklJullItSHlC8UEoZpTwgbpBSTqTE3fNHoPk4k6hE66xSKN/Yw3+h hLiFdPdIT4aesfLvSa/LXl1PzmCG7qSUtbast+VeW+63FfANnkUUua2wtpINrCFYqnss77gR dgIDo+cL596JjdWOp6IWSLUvIdV2pMn59gBPqsWeZrrGg8ZpwLklVrFHOVtp2EuQJDzYHCPO 1Xq1yqPswl88NaUCR9yu5XCkDEdpZqO+gI3WzKbXjKI3tARbatbFuQ+L3EKzhZoTjbXWy7UI HxMIEVtwzEAh1x/O2yRJ3OjjqWzIH3E3Ts/Q0baJYVkhYcLFZ5ygFVraChWtsN+hlaQvSjcN pXdNKKIJKY2wb2v5s2r+iuAvH/KXBX855X9Zy1+q5i8L/tIhf0nwV75Wfknw7x3y7wn+6tfy 7wn+2iF/TfDXvpa/Jvirh/xVwb/3tfpXBX/9kL8u+Otfy1/P1CAlRy/JaYwEZK7/iCf4bRLx lQ3AJ8w5ywZFyWMrtdhg4moeW63FVr4Im36RJOyLsPUvwpa/SO7ey7HF7EA38c6HJYeby8IU EbaB0Esjil3DI9/5lvEA23TYcHjPBWtxwSTEgfJ0dFEY/xRApqPpDfEfRbbA6qFz662e/0o+ r53wIRJZbOJWJZEH3coj9yzY24CDlBRWECqN6AsIwrdnAX5moHQ3wRiF5b2fGahcmMCJgEwZ 0EEHjw7T7TbmHEUmenIF9weSECHZHmRn7RPYh4gECn8dI8doBTOEpnuRHZoDoqSFmNvvjES5 +jBXH9sQJVEYqDDMEbpWmvtDtdaJEYT+AjYZWRsU/zkdkPe3ky4Zjs4HQNj4bzWb0XCcXnAO cLBdDH/SflYTXYqUKbVN7ri4NiR8szTWEZ6qnqQkQtedyHHplurm/fcfbu5+7JLRxTku7DsB JQ0/62jzYgrzmiaXskKSOkKBvO3gkpto057lYAjZTAdbco6qnpG7y+HFj8SIzIFstCGEG3PL WbvicivADaIXn9axSzSmtckHLwSdPeMETTLPWoZlJDvS5DwaD1DAsoQ96iQ2wnuOlrZae2ho ltiqTSGOpPTiHaVyp/9xxjSNjEay9IYMZ8OOnpzWy91NemKRUmmU4j5xfH4WJZer4ub6JENu i/sgkHByc0t01pfwuiA6TYkz0/h+zdcc7323t7ICzPq015P643NyIsNXKvWZphMVxlhcOsDO FDa6MABMuyaaPD2bwTdZl0eCPdv1vp/vfb+k90z0Xob9sCbT4RQEHw6/S/rdS/rNCv0GfKZW 95vV9pvV9xtXgZ7WVyh2u9/Tej35C3ot7XrNWL7b8HTYb2nbb1nCfk8v2LAw3MVuS1/Tbam+ 29JXdVvOdVsqdFsq6bb8m4xd/hpjl+t7L3+NsZtWbqYzWug+3e++yNAdTsRR4V8YeWfAxhcW qz8jF1DLbDqdmX4YgDe9+HjxA5ledyRJGp6T6TmFVfQuCwMA3rm7HQuH1qHZIWaRu7TPvcp4 8kRyjqhoVbAwwPPkBny80OuBmkUbsPpyN4hx8f28xmOsVDS8mUzTXHOut00OPS7poHDPmHQZ wegUsiVn01Fn5T8VEznVfq/X01khXVKH1fGr3gx4e3k7no9v7u5u7wbkIumD66BrP4uejICs Ui2RE+lMOu22ZuEz2hR020Vhk2BbJED9akeDX8XjTz93u90sh2iKKV9veTyaTWfJypylD305 xhC043nGFILFLNnrpUhPKwPzQC/Te3MRX/EowqvlQQ9WOWnA9IFmDfrqfg5SyM3HOaamzz/j jBqQJcwuYEm84AEC14OEpyP+Ef+If8Q/4v+b4q9dcUCQHTSQWWiYDwtYRqr261K2X5eK+3Vk I5PkHYRIHM3/9OnHv/9MTN8PLcczIJogNxev8ZTV+X2PClaBuHmdhI4XFw45EsA6wjV84XQs B7SBwQK+GYaZr05gP0nk5JUTPGqnBN9EciDQ+BWjCAsv+WOy8iGOFAc00IHck8VtY70SAZHF vec2gO7Fq1EWpingEowvlxDoOQQ4IV79RcZq0CIsirN3mzhl1JI1hUJACtEEOYGPU/I3UvJm 5QOs4mePdjQXUUjXHOgqaxEJVFzgpejIC0Iz5Cb+NPGL1osQ2Ems12t9hzt92H2D2Av4gGjN 5IOWtZiLb3M8oJo/hUYAAdXJqbhjLwO9ohtpcWaHhsu3L3HpumnYfR3flHsAoi33hE2hCsjl fgX5grYgyvEgjpmbeDgglJvwOKwHRqbSK+ekyrQ1n+MAuffhHCL5KOFSrAMOmlkhi6bR1qMf zKPYQpKEPFeB3TArSHXa+ng7meP1NZsPJx8T4kIVkNtVLYMW5o/efNds9vQKE4bLiXoSiAv7 lVRO+PYKX3iqQO7RljCeOTgB33xMBztXg+JZFcRmRoxWlyfF51f4DloFoQ0iAprle8LIU1Fz NUDMmFRBjjfVYNnzPPHuGXsrVRBy2hIvLc8BHaPnhLZQhTatqeX0C5D7E77pVaQvVKG+KkYG yTudDkkxYZfa09vbV7ov311pSjvXkVNwh04gDmZhL2T0VUkzoSpKqnrp60umuQAm4SJDZJT2 qaITaKj1z34f/48uqNh41WX/yJ+AqP/9B/Ctkrb/+w+KdPz9hz+kgPPpQjDUpd3/Tl7mKb4Y 1srDRWKfiJ3y1eDxxGu+A3GR8Jpu39x6TfNogRc4Hr63k4Q1+I6/ppvpQclrvEiRKYH1tgiG ii2GDO4tCXwQXcLktkIDRsi9eJC8l7arj1wY2CWEHvMQQqwB6al5oIEvfKUQRg8heNoeDUge Io5lwmcTAqQiIOT3lu8aDmhCzktg8cX6voiKmsKbiQHp52pxkc+OPDQl32QcbQEFNr4di6Ol fCVUBCjDXp1/WOVY+C6+1CvocQnxZRnPucfjuWDcYXuQ4CksgcQbIzl7Ac3mtVRebWU//lFs ON5AzBpC3OT4Fiaa5QmMPaXGAa4RfL/S3K8ANR/g7A8yCH+/x972Q5Mvoni9T45v/YvAqljt +l5g4JmSlB/K5dPn+cpx8Z1+Kd+eY80FyC+vXzr4Il7OVO4hCkv5aCoGbDkNxxCI7MG1gj0C YO463jwwrP1uf57jS4wIxdf99iYFgl0TVm74Y2zEO3cDPCzOm+qKG2HZtBFVXVz1n4zYXFr+ /pTYwtECn2AyV8EXrhNVMhfAeQBjEvtuJVLJKO6g4cYPvWog91cwwaVSaLxZV5O6zqIKhEZu +rADqoDHmzmaLa9WKmC49+6+f8iDYedlgmZrMD5HsR/UwLlnGnVwz/cOnOIegrtY2/UIZp0S Vo4H5lXLAM23BgE2vrDtr0HYhMk9MMxDrQoHX0DlYZ0ctrMSP0dUgyLeNhUXqLAKsMoe+959 iiTDJrSqV4aVrGE1ijlwewV4WGtaB/7xsCdB9YQFFGMVJwJKaqWBhz7+vku9FIt1GDWg8E0l QthkgmGTgQBCrXOYm7BIoGWU+4ew0XZCMZhm+BzU9QJQXMesQQiWz/WNxL4vhq0eZeFUeumw 0SWF6JLqGoCNR6WH5vONWLwqwfUDCRHD3ER/Wj4OKRhv5uo4hPa9sR9K5XoABo1cVtUaQIzQ cKLKqSEwrLDa7cI6Nre4HaX3V9VI8aYexzQWn2t1KhDA+p/rvITxBAt+vxRs24DhV/oYAa6x SYCHmxqgvVpHlZ3Dxcter+qWDs+vW3rwKHgdWHU+FFHEz85Uu0KBEtW30uCGjad5nVWKjtjh fuhbmBkYAVWvPIbnJDND6ZcvJzAxD2LfAnQJE+feqUGQqELr3EbI0U3OhTGwSkcZ+GiUGV4l N4sLZykstwF16Qivs6yZ06DfZbxdiRhVqnnF4sIAdqs1vLa7NqV6xapdzzYwpepCLmGQfBM4 9bEGbu1N+74+ZometqFPA84zRP91reEOYu1Z0Ny6TtPJRuQFiGI3g9PCqJ3iAq3aA+UZ1VgJ xuK4aZKrmCQIklYZyaRbJMwatVf+U01bD/w52czola1FT3WxZLLUo913S6dcDs4a4FIDXG6A Kw1wtQGuNcB7DXC9Ad5v0k+jAps0yJpUyJp0yJqUyJq0yJrUyJr0yJoUyZo0KTVpUmq0xSZN Sk2alJo0KTVpUmrSpNSkSalJk1KTJuUmTcpNmpQbp3WTJuUmTcpNmpSbNCk3aVJu0qTcpMny iCSP0KRJpUmTSqOHbNKk0qRJpUmTSpMmlSZNKk2aVJs0qTZpUm3SpNqkSbVxsWnSpNqkSbVJ k2qTJtUmTWpNmtSaNKk1aVIr1WT07JkijCkPGnbg0vZ34NLWd+CGtkvHcAcuHcEduHT8duDS 0duBS8duBy4duZxamtTWoLfyQCEHb9BceZiQgzforjxIyMEbtFceIuTgDforDxBy8Ca7a9Bf eXSQgzforzw2yMEb9FceGeTgDforjwtyE6tBf/tRAezYy24hsdoIVYVp84VjRIb1SwmZa8wX 4d5tFQKip6Se7VNETwtDJCz5tn3IT9yizfGsZo6J7/EhRvJDM04kfgN7/pQc9y+fusnBbDf2 Y2M1XwTGPW5UdUnNA3/1PU5fgoKXWzkMhR1gZP+ngS3WIRPDjJ3HHZt+lSD+2jNx+yb1q2S1 uA3eOtni7WPADhJz+ga53/w+lGTl3HuuuP4Wvwf68vv/NP9D+qfmf8jyNv+jp9Ik/4Me8z/+ iLKbe8f8D3oIEZ616KOO+R/H/I+9ReuY/7Ez1WP+RxXpMf/jmP+RP9jP539UmVMh/0Ov7tUx /+NfLf+j8ubwmADyhyaAlNvbMQGkAuGYAFKL8p+UAMIkvT4DpDr54XfNACm3pn+NDBCJ6tW8 jhkgla39B2SAMLVfbpnbFBClVxm2/YYUEEZrdH7MATnmgBxzQPYQjjkgxxyQYw7IIcIxB+SY A3LMATnmgNTDjzkg9fBjDsiW7P9FDoik/g45ICVM9pJAekz5l0sCOZZjOZZjOZZjOZZjOZZj OZZjOZZjOZZjOZZjOZZjOZZjOZZjOZb/mPJ/Rsdz8QCgAAA= --------------040204090703080205080907-- From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 2 22:29:18 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7860C943 for ; Tue, 2 Apr 2013 22:29:18 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x230.google.com (mail-we0-x230.google.com [IPv6:2a00:1450:400c:c03::230]) by mx1.freebsd.org (Postfix) with ESMTP id 1095AF62 for ; Tue, 2 Apr 2013 22:29:17 +0000 (UTC) Received: by mail-we0-f176.google.com with SMTP id s43so697623wey.7 for ; Tue, 02 Apr 2013 15:29:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=ktzQip1uA6ifgcxdBF8ad8nHh7GIZt+dSgCNdKn0aSE=; b=e+eq9+dubC2g+YXcPqc+YYWQRXFMJZhuhwwpDohX+ojDZhG5VCzL9ySUl3/VL8vNH6 XGj4WYrBdLtW0wFXIBtDS2lo1WNHaUDxF8tpfOkiaOUuwVUJAltVnQpHIzFXMGd2s98f ycidr/l9wrezFWbD8wa1QCsMm+jhlMjfStqNZJxDauoVQ5uJ+ULlf6t0XwkkZPXGFWWg X8Es5I/6Qrgb1cTD/unZKqiFObC4DAIGcXZytmgHMJ1Lpa1rlh+0uhGqcCsB5qVEjYaN zfT/VZi6LQUYJ9md+5xgUYCjv8OIxg/2UqGWNROoKM7LeXEPwFGeuiQZihRov0se8K16 Z4zw== MIME-Version: 1.0 X-Received: by 10.180.89.105 with SMTP id bn9mr379961wib.26.1364941757129; Tue, 02 Apr 2013 15:29:17 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.108.130 with HTTP; Tue, 2 Apr 2013 15:29:16 -0700 (PDT) In-Reply-To: <515B4E16.3050901@gmail.com> References: <515892C4.1060002@gmail.com> <5158b7db.897aec0a.42d0.ffffaac4@mx.google.com> <5159F66B.2040600@gmail.com> <5159FF12.8030702@gmail.com> <515B4E16.3050901@gmail.com> Date: Tue, 2 Apr 2013 15:29:16 -0700 X-Google-Sender-Auth: f78Ll9DtmtWF_tCCq1Ts7LKqWkc Message-ID: Subject: Re: ath not working after a motherboard and ram upgrade From: Adrian Chadd To: Joshua Isom 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, 02 Apr 2013 22:29:18 -0000 Right; when you've booted with <4 GB there's no need to create a separate zone for 32 bit only memory, so it doesn't bother. thanks, adrian On 2 April 2013 14:31, Joshua Isom wrote: > sysctl.1.txt is right after boot, sysctl.2.txt is while failing. One thing > different when using 4GB is that hw.busdma.zone0.lowaddr is > 0xfffffffffffffff, 60 bits and not 64, but when 32GB it's 0xffffffff, 32 > bits. I don't know if that has anything to do with it, but it seems > strange. > > > > On 4/2/2013 1:35 AM, Adrian Chadd wrote: >> >> .. and there's been some more work in -HEAD, so please svn update first! >> >> Thanks, >> >> >> adrian >> > From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 2 22:33:06 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 3866499A for ; Tue, 2 Apr 2013 22:33:06 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::235]) by mx1.freebsd.org (Postfix) with ESMTP id C39F7F85 for ; Tue, 2 Apr 2013 22:33:05 +0000 (UTC) Received: by mail-wi0-f181.google.com with SMTP id hj8so941882wib.14 for ; Tue, 02 Apr 2013 15:33:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=W71qF3OvTiGS1vLpDmj24jrdojF8pL3f+HYTONdZZyw=; b=m8IwYBoxSXWRII7zz8vxCjhfz4L0Z/+tWQ1VEKySuqYDDnANwMLCaF9S905wonmQqw rXyLLt8n+tfXIBRzaRGRCGgG7EODOelyN+2XdxVCHuvfh0fmqllImTg77fsTYUd0HryE 4Hmr38UaY7wCKVmqz/DtkLPeSKZieRenqXWzsauMKEbSefMRfvwlcuvRyIU+y77r9p1j Q6Wv6vXGvG1houyiOHbfiOAiSx/8NMZ/RikuLy7ecEcO/4BovjRmoHu3uL1OD0V/8uJw y79ixeI1BlWlzoyjJaphp+mXQk4AxX+81fJ3IxWw1nFG0O4VMbDTPgjCZuaDGgDQ4jQc TB7g== MIME-Version: 1.0 X-Received: by 10.180.89.105 with SMTP id bn9mr392879wib.26.1364941984951; Tue, 02 Apr 2013 15:33:04 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.108.130 with HTTP; Tue, 2 Apr 2013 15:33:04 -0700 (PDT) In-Reply-To: References: <515892C4.1060002@gmail.com> <5158b7db.897aec0a.42d0.ffffaac4@mx.google.com> <5159F66B.2040600@gmail.com> <5159FF12.8030702@gmail.com> <515B4E16.3050901@gmail.com> Date: Tue, 2 Apr 2013 15:33:04 -0700 X-Google-Sender-Auth: PfZMRmiiztdX6fJYfEma2PC2tVw Message-ID: Subject: Re: ath not working after a motherboard and ram upgrade From: Adrian Chadd To: Joshua Isom 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, 02 Apr 2013 22:33:06 -0000 Ok, can you: * bring the interface down cleanly (ifconfig wlan0 down); * unload the ath driver (kldunload if_ath and kldunload if_ath_pci) * sysctl hw.busdma, and just add it to the list here? I'd like to make sure that it's freeing all the bounce buffer pages. Thanks, adrian From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 3 00:24:16 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A1BEFECC; Wed, 3 Apr 2013 00:24:16 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-qe0-f50.google.com (mail-qe0-f50.google.com [209.85.128.50]) by mx1.freebsd.org (Postfix) with ESMTP id 4E55371D; Wed, 3 Apr 2013 00:24:16 +0000 (UTC) Received: by mail-qe0-f50.google.com with SMTP id k5so585301qej.37 for ; Tue, 02 Apr 2013 17:24:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=R5LSSgL/ow/Zj/I82xUh/hKTnHZHIS0ewwaOARPJ0Pg=; b=PD6MnhXTVrq2iotseitBqi0PUZrZfbFZZvBHiAT9gYbiHMOhw6ueKuS4wr5cru+YRC 28NkzxRdYI70yEgoR54V1N/SQCtx0DFb9KAk+C9zJKzvUpVPqcP+DLOwvYoamcbES+Ur v4lmlhZD8MUvM7k1mWX3EWOW/iRqP0vk7DIWS1DJXVCDYIxQ7QfL8Bj2wFiUu6cB2n4y lY8TM/+dSqp4nuRcY/7GPysbZ0JQQlKDFgcxeGgTEWE1jCoBhqdSbwx2LnphRvON4r0G y8jQwtydkYN4efPDzLMBrZaESPxuHZLvsfyEw5JA+949BZ2rQDg1vpc/ZKlLhSJzqOIf FO0g== X-Received: by 10.49.132.72 with SMTP id os8mr19957498qeb.52.1364948655634; Tue, 02 Apr 2013 17:24:15 -0700 (PDT) Received: from [192.168.1.34] (c-98-212-197-211.hsd1.il.comcast.net. [98.212.197.211]) by mx.google.com with ESMTPS id a15sm2225832qad.4.2013.04.02.17.24.13 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 02 Apr 2013 17:24:15 -0700 (PDT) Message-ID: <515B76A6.7080804@gmail.com> Date: Tue, 02 Apr 2013 19:24:06 -0500 From: Joshua Isom User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: ath not working after a motherboard and ram upgrade References: <515892C4.1060002@gmail.com> <5158b7db.897aec0a.42d0.ffffaac4@mx.google.com> <5159F66B.2040600@gmail.com> <5159FF12.8030702@gmail.com> <515B4E16.3050901@gmail.com> In-Reply-To: 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.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: Wed, 03 Apr 2013 00:24:16 -0000 hw.busdma.total_bpages: 8250 hw.busdma.zone0.total_bpages: 8250 hw.busdma.zone0.free_bpages: 8250 hw.busdma.zone0.reserved_bpages: 0 hw.busdma.zone0.active_bpages: 0 hw.busdma.zone0.total_bounced: 3836 hw.busdma.zone0.total_deferred: 0 hw.busdma.zone0.lowaddr: 0xffffffff hw.busdma.zone0.alignment: 4096 They'd not freed. On 4/2/2013 5:33 PM, Adrian Chadd wrote: > Ok, can you: > > * bring the interface down cleanly (ifconfig wlan0 down); > * unload the ath driver (kldunload if_ath and kldunload if_ath_pci) > * sysctl hw.busdma, and just add it to the list here? > > I'd like to make sure that it's freeing all the bounce buffer pages. > > Thanks, > > > adrian > From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 3 00:28:04 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 0DF47E0 for ; Wed, 3 Apr 2013 00:28:04 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x232.google.com (mail-we0-x232.google.com [IPv6:2a00:1450:400c:c03::232]) by mx1.freebsd.org (Postfix) with ESMTP id 983CB73E for ; Wed, 3 Apr 2013 00:28:03 +0000 (UTC) Received: by mail-we0-f178.google.com with SMTP id z53so746612wey.23 for ; Tue, 02 Apr 2013 17:28:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=7au3VZLyxjXmAa1qGkPUtJFK+YHcX79CANSG42sr9s4=; b=S9+tJG2lbIUEce3ZOHDycb6VhNUGyprmbD+p0lISubsG5BFQ1l3wMrlb733Cw+atg8 DaRPQnNSYHLEbFduprTHiLpgRLdhCD8BeUpxFqmIHR5bdoY9WP80JivjCLAqmHAzWkZL hZ4Wn8P7t1/Rg1CV6rG7DTOd/HPS1um20g4yMKZo7C2LGAYH8anVLX569LYvCkHE3Ler ktlETtm9qMuop3TQR5AuWCcesa4BLr4v1MFw613ZJUASgwkQhJhZk75/oKEeAdK7KyT9 kj4lNflIEwkE9n8NfKL63AySGpluc0IvmO5XdGqiz5ENwMJO8XqvZIYCE4wfaTObozAf XOlg== MIME-Version: 1.0 X-Received: by 10.180.79.6 with SMTP id f6mr19136086wix.26.1364948882588; Tue, 02 Apr 2013 17:28:02 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.108.130 with HTTP; Tue, 2 Apr 2013 17:28:02 -0700 (PDT) In-Reply-To: <515B76A6.7080804@gmail.com> References: <515892C4.1060002@gmail.com> <5158b7db.897aec0a.42d0.ffffaac4@mx.google.com> <5159F66B.2040600@gmail.com> <5159FF12.8030702@gmail.com> <515B4E16.3050901@gmail.com> <515B76A6.7080804@gmail.com> Date: Tue, 2 Apr 2013 17:28:02 -0700 X-Google-Sender-Auth: UEA0h0DkroRseAET7Pc34cXbNt8 Message-ID: Subject: Re: ath not working after a motherboard and ram upgrade From: Adrian Chadd To: Joshua Isom 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: Wed, 03 Apr 2013 00:28:04 -0000 Nono, they're free. There's no active pages after an unload. Thus, they're fine. Ok, so now I need to go and audit things in more depth. Thanks! Adrian On 2 April 2013 17:24, Joshua Isom wrote: > hw.busdma.total_bpages: 8250 > hw.busdma.zone0.total_bpages: 8250 > hw.busdma.zone0.free_bpages: 8250 > hw.busdma.zone0.reserved_bpages: 0 > hw.busdma.zone0.active_bpages: 0 > hw.busdma.zone0.total_bounced: 3836 > hw.busdma.zone0.total_deferred: 0 > hw.busdma.zone0.lowaddr: 0xffffffff > hw.busdma.zone0.alignment: 4096 > > They'd not freed. > > > On 4/2/2013 5:33 PM, Adrian Chadd wrote: >> >> Ok, can you: >> >> * bring the interface down cleanly (ifconfig wlan0 down); >> * unload the ath driver (kldunload if_ath and kldunload if_ath_pci) >> * sysctl hw.busdma, and just add it to the list here? >> >> I'd like to make sure that it's freeing all the bounce buffer pages. >> >> Thanks, >> >> >> adrian >> > From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 3 00:34:30 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 99E081F5; Wed, 3 Apr 2013 00:34:30 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-qe0-f53.google.com (mail-qe0-f53.google.com [209.85.128.53]) by mx1.freebsd.org (Postfix) with ESMTP id 46CB778C; Wed, 3 Apr 2013 00:34:30 +0000 (UTC) Received: by mail-qe0-f53.google.com with SMTP id q19so598354qeb.12 for ; Tue, 02 Apr 2013 17:34:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=AnB9Avh4mHnXH18hlN08ykNWYU99I2CZUcrSIJUJr5A=; b=OmIftHK4/354v5Ob0MFoUADBfHrycRKGOhoJHaP3Fxmi5419XQX05txUAIE96eqGS4 cltGCEoZaN64meVvG2JwEwVwRlUz0v9z4Wtjw25GVBlQDu7A5FpBYxFeZ6ynk1u1whWA 9VcaAjElBnHMnvEbmHoGtp4zXcSJEb2YLY8Y84x5KG4kWw/hpF/wyeWJmGhfvfsOmxJ+ u+0MYt4zG0YOYSCDAv0SpS+HJr6QlEnzl2bAVYwcTOjlQ8AfrcMD0eGGBR6QHRZT2Dij DeAX3I4ZfcUTSuadTYJfa+FfGavZIhEkaFcp9NW24t/A4CejSi1pu7CcWpYqvbY+uCly P8hw== X-Received: by 10.224.72.148 with SMTP id m20mr22385qaj.24.1364949263755; Tue, 02 Apr 2013 17:34:23 -0700 (PDT) Received: from [192.168.1.34] (c-98-212-197-211.hsd1.il.comcast.net. [98.212.197.211]) by mx.google.com with ESMTPS id t3sm4510818qen.5.2013.04.02.17.34.22 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 02 Apr 2013 17:34:23 -0700 (PDT) Message-ID: <515B7907.80705@gmail.com> Date: Tue, 02 Apr 2013 19:34:15 -0500 From: Joshua Isom User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: ath not working after a motherboard and ram upgrade References: <515892C4.1060002@gmail.com> <5158b7db.897aec0a.42d0.ffffaac4@mx.google.com> <5159F66B.2040600@gmail.com> <5159FF12.8030702@gmail.com> <515B4E16.3050901@gmail.com> <515B76A6.7080804@gmail.com> In-Reply-To: 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.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: Wed, 03 Apr 2013 00:34:30 -0000 And it did cause problems with 8GB before IIRC. On 4/2/2013 7:28 PM, Adrian Chadd wrote: > Nono, they're free. There's no active pages after an unload. Thus, they're fine. > > Ok, so now I need to go and audit things in more depth. > > Thanks! > > > > Adrian > > On 2 April 2013 17:24, Joshua Isom wrote: >> hw.busdma.total_bpages: 8250 >> hw.busdma.zone0.total_bpages: 8250 >> hw.busdma.zone0.free_bpages: 8250 >> hw.busdma.zone0.reserved_bpages: 0 >> hw.busdma.zone0.active_bpages: 0 >> hw.busdma.zone0.total_bounced: 3836 >> hw.busdma.zone0.total_deferred: 0 >> hw.busdma.zone0.lowaddr: 0xffffffff >> hw.busdma.zone0.alignment: 4096 >> >> They'd not freed. >> >> >> On 4/2/2013 5:33 PM, Adrian Chadd wrote: >>> >>> Ok, can you: >>> >>> * bring the interface down cleanly (ifconfig wlan0 down); >>> * unload the ath driver (kldunload if_ath and kldunload if_ath_pci) >>> * sysctl hw.busdma, and just add it to the list here? >>> >>> I'd like to make sure that it's freeing all the bounce buffer pages. >>> >>> Thanks, >>> >>> >>> adrian >>> >> From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 3 00:37:00 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 5D52422E for ; Wed, 3 Apr 2013 00:37:00 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) by mx1.freebsd.org (Postfix) with ESMTP id E6CDB7A0 for ; Wed, 3 Apr 2013 00:36:59 +0000 (UTC) Received: by mail-wi0-f170.google.com with SMTP id hm11so3781153wib.3 for ; Tue, 02 Apr 2013 17:36:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=VDuVhcDGPeWeravEkLiRVGriy0OyE7YAa+lovfvidCg=; b=W/n/VQGCn+MqOqbIikBwCgJQq+BI+dlmKrr4/ZHdqtWiCKI7+pnGfAMeZ2pydlV9ul XzGBBCzFiGErwx8+ECNryFHcjGk9VCBzeY/AAEEmu06Dm4zZSjQZD3x3Rdcbs1TFpOIZ AYqCuJctCMxZmSJwZ3OcNlZvmEcKHO/kKX9GjR/G5s6wTEm3u/G7id5GJ6nC9Jrn87no M16tVmeZfKIuGas71rdPltmFVuIhFJx6NIle/CfS2nHihtp7iP8aSisDkS1Us8vtrq8N UqV+xoVvF42OD1UQp3eEJjAeQ0QZuZqnJenroW7YAHqgG3hnFmeasamVDhd3RmLjFSKx DnCg== MIME-Version: 1.0 X-Received: by 10.181.11.164 with SMTP id ej4mr19631650wid.29.1364949419149; Tue, 02 Apr 2013 17:36:59 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.108.130 with HTTP; Tue, 2 Apr 2013 17:36:59 -0700 (PDT) In-Reply-To: <515B7907.80705@gmail.com> References: <515892C4.1060002@gmail.com> <5158b7db.897aec0a.42d0.ffffaac4@mx.google.com> <5159F66B.2040600@gmail.com> <5159FF12.8030702@gmail.com> <515B4E16.3050901@gmail.com> <515B76A6.7080804@gmail.com> <515B7907.80705@gmail.com> Date: Tue, 2 Apr 2013 17:36:59 -0700 X-Google-Sender-Auth: ulU1q_HinuHOYKSbwPg6U55jPxM Message-ID: Subject: Re: ath not working after a motherboard and ram upgrade From: Adrian Chadd To: Joshua Isom 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: Wed, 03 Apr 2013 00:37:00 -0000 On 2 April 2013 17:34, Joshua Isom wrote: > And it did cause problems with 8GB before IIRC. Yeah. I need to acquire a machine with that much RAM. Maybe tomorrow. I've been meaning to buy a new PC for other wifi/radio hacking purposes. Adrian From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 3 00:44:30 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 5E2E12D6; Wed, 3 Apr 2013 00:44:30 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-qa0-f48.google.com (mail-qa0-f48.google.com [209.85.216.48]) by mx1.freebsd.org (Postfix) with ESMTP id 0920E7E2; Wed, 3 Apr 2013 00:44:29 +0000 (UTC) Received: by mail-qa0-f48.google.com with SMTP id hu16so595992qab.7 for ; Tue, 02 Apr 2013 17:44:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=3q9P2MLYp0pnaLPsST/MzJ/g8LVXXqRz1bQ0wZw9VrU=; b=bkRr6RAKGh/AVTpPfVtD7DE2NkDynnHIoVVyV6+/Mp0ttyDpB6yz03gOk0CFWAwk9/ HDT0qrzdgMoulo77XD0+HMryMCqIUtaZNKdppTxr7q+o9Q1pDAel906tBtjwvvzL7wqu J/m8HfZ9At1pHtG8xvJ1kRM3/ud/suLAFIOOrgAhbA2GuP5juTG7swEBI8w9aOPlpFeG 6lOaklPLKG3puyNrlpZ5Gidq/V7aP1S21dA/InXkJ9mUyb6zdbMWCU03YV7wuPn+Q36j R8lglQjObkGfBAauP+nmN70UjzJoHI0+RXdfe8kTtzHZO8mYrlsT2fd3byH33AFqhnX7 hl5g== X-Received: by 10.49.30.70 with SMTP id q6mr19740748qeh.28.1364949863401; Tue, 02 Apr 2013 17:44:23 -0700 (PDT) Received: from [192.168.1.34] (c-98-212-197-211.hsd1.il.comcast.net. [98.212.197.211]) by mx.google.com with ESMTPS id gw9sm5210996qab.10.2013.04.02.17.44.22 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 02 Apr 2013 17:44:22 -0700 (PDT) Message-ID: <515B7B5F.8080400@gmail.com> Date: Tue, 02 Apr 2013 19:44:15 -0500 From: Joshua Isom User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: ath not working after a motherboard and ram upgrade References: <515892C4.1060002@gmail.com> <5158b7db.897aec0a.42d0.ffffaac4@mx.google.com> <5159F66B.2040600@gmail.com> <5159FF12.8030702@gmail.com> <515B4E16.3050901@gmail.com> <515B76A6.7080804@gmail.com> <515B7907.80705@gmail.com> In-Reply-To: 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.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: Wed, 03 Apr 2013 00:44:30 -0000 I did get a couple bounced after pinging for a while via ssh, but only one ping packet dropped, so it should be good for anything tcp. For my system, network is more important than ram quantity, but it was nice doing a buildworld onto a ram backed file system. I just need to work out a framework to bring up a filesystem, and regularly synchronize it to disk for preservation. On 4/2/2013 7:36 PM, Adrian Chadd wrote: > On 2 April 2013 17:34, Joshua Isom wrote: >> And it did cause problems with 8GB before IIRC. > > Yeah. I need to acquire a machine with that much RAM. > > Maybe tomorrow. I've been meaning to buy a new PC for other wifi/radio > hacking purposes. > > > > Adrian > From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 3 00:46:07 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 424F92FA for ; Wed, 3 Apr 2013 00:46:07 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x22b.google.com (mail-we0-x22b.google.com [IPv6:2a00:1450:400c:c03::22b]) by mx1.freebsd.org (Postfix) with ESMTP id CB3467EC for ; Wed, 3 Apr 2013 00:46:06 +0000 (UTC) Received: by mail-we0-f171.google.com with SMTP id d46so791955wer.30 for ; Tue, 02 Apr 2013 17:46:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=SM/e3CBiz9Ln3QA6bxyjI0BDSbdokiqHGV2Egj/vQ+s=; b=Zaxi1FWFzGhzotkR0D+Y6YS2pN7O3g4sved7HPn38rVmiZImTa4tugD6slh0VP49VF CSIejdu3E/Wa9RgaqdkgRvLV4wkX8Ucf4d3em4ilFxyNr6F7j77hzHqimANASQ5azKrj 9cIfz0Xf1Us1w/4Rhl+loyudct0oXGxu7UaymwOrt0QJyRImgwW+JUr8cAOjdjWsijgr zuEgqDLunJAKKDR1r1swmwDlwJgMI54V377/VXeF/l7HQYyis0Ke3bSDaPfwzl+5W+jr k3BcnQTXFnOWGSrGkuJFBTWe2ohyyl/gSCKjBT0G3mvuUM8oMbkegMQgTIAmEPHMl0hR GD0w== MIME-Version: 1.0 X-Received: by 10.194.171.74 with SMTP id as10mr25444740wjc.0.1364949965899; Tue, 02 Apr 2013 17:46:05 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.108.130 with HTTP; Tue, 2 Apr 2013 17:46:05 -0700 (PDT) In-Reply-To: <515B7B5F.8080400@gmail.com> References: <515892C4.1060002@gmail.com> <5158b7db.897aec0a.42d0.ffffaac4@mx.google.com> <5159F66B.2040600@gmail.com> <5159FF12.8030702@gmail.com> <515B4E16.3050901@gmail.com> <515B76A6.7080804@gmail.com> <515B7907.80705@gmail.com> <515B7B5F.8080400@gmail.com> Date: Tue, 2 Apr 2013 17:46:05 -0700 X-Google-Sender-Auth: hBHvXM1QYOqcGezvZFsnix73l4U Message-ID: Subject: Re: ath not working after a motherboard and ram upgrade From: Adrian Chadd To: Joshua Isom 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: Wed, 03 Apr 2013 00:46:07 -0000 On 2 April 2013 17:44, Joshua Isom wrote: > I did get a couple bounced after pinging for a while via ssh, but only one > ping packet dropped, so it should be good for anything tcp. So what, 8GB almost-but-not-quite worked? How much RAM do I need to ensure that things will break quickly? :) Adrian From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 3 00:54:33 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 37AD4371; Wed, 3 Apr 2013 00:54:33 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-qc0-x233.google.com (mail-qc0-x233.google.com [IPv6:2607:f8b0:400d:c01::233]) by mx1.freebsd.org (Postfix) with ESMTP id D55C481A; Wed, 3 Apr 2013 00:54:32 +0000 (UTC) Received: by mail-qc0-f179.google.com with SMTP id v28so463448qcm.10 for ; Tue, 02 Apr 2013 17:54:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=JSwGRKhAQpbQPDCf1qhsvYNImcVmA7wBCwKQO6/oLCE=; b=OGv/Iv1E2fQYzHuD0v5CdWuidEGpAdZvOcArXluvAT8RlRCacUmLphmO93NrWIteiv WgbogAQ7qlowub5R6TP87AtFFm/23LCnWxLx4gNiUvh+G8nXFc01OZ3ucLTPEXflHOsJ T0QIkuIsoy7FUdDCzt+W/2Jy36QZAcnZ7794+2KERwxnLAu9KMgZXMkTKNaRsAbJGeWd cOe0Gi96l3mxeE61alHBkWZ1/jhUGZZS5pd/Wfv8Hc9UqmOwY7I67Qp+fpKD7EDW1Tt5 GE+UTEJvU/v2Bq+6rntQMTjUOR8b4qKLvGLTmmvTOgd8hSe2BHG7XmNiWbWydWvpC8oQ FUFg== X-Received: by 10.229.69.76 with SMTP id y12mr6930458qci.123.1364950471700; Tue, 02 Apr 2013 17:54:31 -0700 (PDT) Received: from [192.168.1.34] (c-98-212-197-211.hsd1.il.comcast.net. [98.212.197.211]) by mx.google.com with ESMTPS id k8sm4622782qej.2.2013.04.02.17.54.30 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 02 Apr 2013 17:54:31 -0700 (PDT) Message-ID: <515B7DBF.8070100@gmail.com> Date: Tue, 02 Apr 2013 19:54:23 -0500 From: Joshua Isom User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: ath not working after a motherboard and ram upgrade References: <515892C4.1060002@gmail.com> <5159F66B.2040600@gmail.com> <5159FF12.8030702@gmail.com> <515B4E16.3050901@gmail.com> <515B76A6.7080804@gmail.com> <515B7907.80705@gmail.com> <515B7B5F.8080400@gmail.com> In-Reply-To: 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.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: Wed, 03 Apr 2013 00:54:33 -0000 Right now I'm at 62 bpages bounced, with it running in a loop every second listing hw.busdma. Right now it's half an hour of uptime, and when I did 4500 pings, I lost one packet. Quickly's relative. I mainly use ssh to access my FreeBSD machine, I don't recall the last time I ran X, which kind of pissed me off that I had to buy a video card for a console when the monitor's always off. Twelve gigs lost pretty fast, I'll try 9 to see if 8's a magic number. On 4/2/2013 7:46 PM, Adrian Chadd wrote: > On 2 April 2013 17:44, Joshua Isom wrote: >> I did get a couple bounced after pinging for a while via ssh, but only one >> ping packet dropped, so it should be good for anything tcp. > > So what, 8GB almost-but-not-quite worked? > > How much RAM do I need to ensure that things will break quickly? :) > > > > Adrian > From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 3 00:55:09 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id BF145391; Wed, 3 Apr 2013 00:55:09 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-qe0-f52.google.com (mail-qe0-f52.google.com [209.85.128.52]) by mx1.freebsd.org (Postfix) with ESMTP id 6C594825; Wed, 3 Apr 2013 00:55:09 +0000 (UTC) Received: by mail-qe0-f52.google.com with SMTP id jy17so593447qeb.25 for ; Tue, 02 Apr 2013 17:55:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=TGIqKSFKmc7ONcUb04mn9kajywjba1Tfc0JdEbl2Y90=; b=rHDxgJAFspKmFXWS/UApAlLohf5HEtHW+/Y4aAcioHWetDAm2pJJpUbd1qxuqZNInP NwJlO5K08o4buR5oO4qw02LZGhWNWmtSCpdVWdmws6SpyHTYkZ8OQzgWifj6436er8RH iHRixPT8mpw4oSHkKyL5sla8NhdY2w6zssKeJBu6JzRdjWdh2irD4bFCLoREEp/1hvAG 3lQBJCpyOaW9F/a3ixVz8T65AUbNLid3PICgz7zAbVlRXZ1u1q1zGt2vbYvRTCyony7j 8Ph2T3kJm5mUf5n4UdXOb2388vp5/0AGR6iMbd6qYiIIBL4mzhXsey01f9YVP6LNpelz 7a+w== X-Received: by 10.229.63.195 with SMTP id c3mr6441645qci.139.1364949194091; Tue, 02 Apr 2013 17:33:14 -0700 (PDT) Received: from [192.168.1.34] (c-98-212-197-211.hsd1.il.comcast.net. [98.212.197.211]) by mx.google.com with ESMTPS id t3sm4507310qen.5.2013.04.02.17.33.13 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 02 Apr 2013 17:33:13 -0700 (PDT) Message-ID: <515B78C2.20609@gmail.com> Date: Tue, 02 Apr 2013 19:33:06 -0500 From: Joshua Isom User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: ath not working after a motherboard and ram upgrade References: <515892C4.1060002@gmail.com> <5158b7db.897aec0a.42d0.ffffaac4@mx.google.com> <5159F66B.2040600@gmail.com> <5159FF12.8030702@gmail.com> <515B4E16.3050901@gmail.com> <515B76A6.7080804@gmail.com> In-Reply-To: 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.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: Wed, 03 Apr 2013 00:55:09 -0000 But this really will be interesting. It seems to be fine at 8GB of ram, not just at 4GB. I'm not getting any dma issues or dropped packets so far. But booting with 12GB will cause problems. On 4/2/2013 7:28 PM, Adrian Chadd wrote: > Nono, they're free. There's no active pages after an unload. Thus, they're fine. > > Ok, so now I need to go and audit things in more depth. > > Thanks! > > > > Adrian > > On 2 April 2013 17:24, Joshua Isom wrote: >> hw.busdma.total_bpages: 8250 >> hw.busdma.zone0.total_bpages: 8250 >> hw.busdma.zone0.free_bpages: 8250 >> hw.busdma.zone0.reserved_bpages: 0 >> hw.busdma.zone0.active_bpages: 0 >> hw.busdma.zone0.total_bounced: 3836 >> hw.busdma.zone0.total_deferred: 0 >> hw.busdma.zone0.lowaddr: 0xffffffff >> hw.busdma.zone0.alignment: 4096 >> >> They'd not freed. >> >> >> On 4/2/2013 5:33 PM, Adrian Chadd wrote: >>> >>> Ok, can you: >>> >>> * bring the interface down cleanly (ifconfig wlan0 down); >>> * unload the ath driver (kldunload if_ath and kldunload if_ath_pci) >>> * sysctl hw.busdma, and just add it to the list here? >>> >>> I'd like to make sure that it's freeing all the bounce buffer pages. >>> >>> Thanks, >>> >>> >>> adrian >>> >> From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 3 00:56:17 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id CD5D43B6 for ; Wed, 3 Apr 2013 00:56:17 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x234.google.com (mail-wi0-x234.google.com [IPv6:2a00:1450:400c:c05::234]) by mx1.freebsd.org (Postfix) with ESMTP id 628C082E for ; Wed, 3 Apr 2013 00:56:17 +0000 (UTC) Received: by mail-wi0-f180.google.com with SMTP id c10so1009526wiw.7 for ; Tue, 02 Apr 2013 17:56:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=hsHNK4h+zyoK40Oa8AiAMH3qdmr+wefpbWLCVRO0lMc=; b=yy6cziha4XK4RvIhh40OBt3M9z4lz/lGIXFeZSDNuBprw9z89UoStijuwa7lc/0LVS 3yHXxKmBn/aKU0dGXHgqS/5eXUs0ccFJoehgGdUW83uD9vfRsZqhOvwkikID4dR2bMBM a8MQPKvaJCgmRcTetBtPn4To6U0TiAqJ0/btAJVmN3gNyEcOvsJvbEYesZg7dnIEOyOJ 2MvgwBGf6GXW9esrir08gIAKlPh9m35tRCAlYHm/D7CWG50eFfMRrCtTYPYpkZwFzLVf R6EUi9P6uZpo2WjB8B01oj90N9DUrTo4kHhAovOQnpKBMibHURcWwRx7a6aM5UPmklBv FMJA== MIME-Version: 1.0 X-Received: by 10.194.120.169 with SMTP id ld9mr25512783wjb.24.1364950576496; Tue, 02 Apr 2013 17:56:16 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.108.130 with HTTP; Tue, 2 Apr 2013 17:56:16 -0700 (PDT) In-Reply-To: <515B78C2.20609@gmail.com> References: <515892C4.1060002@gmail.com> <5158b7db.897aec0a.42d0.ffffaac4@mx.google.com> <5159F66B.2040600@gmail.com> <5159FF12.8030702@gmail.com> <515B4E16.3050901@gmail.com> <515B76A6.7080804@gmail.com> <515B78C2.20609@gmail.com> Date: Tue, 2 Apr 2013 17:56:16 -0700 X-Google-Sender-Auth: MhjdJEw4-Enm-0ibaiqQbdvvOG0 Message-ID: Subject: Re: ath not working after a motherboard and ram upgrade From: Adrian Chadd To: Joshua Isom 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: Wed, 03 Apr 2013 00:56:17 -0000 On 2 April 2013 17:33, Joshua Isom wrote: > But this really will be interesting. It seems to be fine at 8GB of ram, not > just at 4GB. I'm not getting any dma issues or dropped packets so far. But > booting with 12GB will cause problems. Chances are at 8GB of RAM it's just not bouncing a _lot_. Adrian From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 3 01:13:32 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E2365594; Wed, 3 Apr 2013 01:13:32 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-qe0-f41.google.com (mail-qe0-f41.google.com [209.85.128.41]) by mx1.freebsd.org (Postfix) with ESMTP id 8E85E902; Wed, 3 Apr 2013 01:13:32 +0000 (UTC) Received: by mail-qe0-f41.google.com with SMTP id 7so611130qeb.14 for ; Tue, 02 Apr 2013 18:13:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Lz0kB82QI35F8jAirrgl9AAUasLVLaam3YSte0u4TGs=; b=VVQHCN4osHk7ukaK67MnW5exwlb3NTO92DAHpRkyT8ynvaTIWESAi1Gv44T/USZi6c h7+C3Xc30VCa1JrmZfQr+GzxgWZojyw9FKbG2gj+zqTtxwVvhbQjlglPI4TB+zRqmzZ4 N6SkgfSRQkyX2PPgAbWnHYxFCFbd2Vf78h3DPtgaBj3seBtbZzW6POAVV2OKokOKa8KU C0AuiYRhFiEu9lldsP8FXEcoEpF5sjR+mzA8dUG5SSKCgvERXejRk/9qIz2hxI0nmLkK 9IUydQBiiQectmoKsOKP14S2UC66ILtf5csDp50cMzmgO4eVIYBh2l43YCJLpLORxbWR 7YDg== X-Received: by 10.229.164.3 with SMTP id c3mr7059914qcy.124.1364951611734; Tue, 02 Apr 2013 18:13:31 -0700 (PDT) Received: from [192.168.1.34] (c-98-212-197-211.hsd1.il.comcast.net. [98.212.197.211]) by mx.google.com with ESMTPS id he6sm5489905qab.1.2013.04.02.18.13.30 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 02 Apr 2013 18:13:31 -0700 (PDT) Message-ID: <515B8233.9000603@gmail.com> Date: Tue, 02 Apr 2013 20:13:23 -0500 From: Joshua Isom User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: ath not working after a motherboard and ram upgrade References: <515892C4.1060002@gmail.com> <5158b7db.897aec0a.42d0.ffffaac4@mx.google.com> <5159F66B.2040600@gmail.com> <5159FF12.8030702@gmail.com> <515B4E16.3050901@gmail.com> <515B76A6.7080804@gmail.com> <515B78C2.20609@gmail.com> In-Reply-To: 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.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: Wed, 03 Apr 2013 01:13:32 -0000 I went half an hour being ok, and 12GB was dropping TCP connections in five minutes. I'm estimating a little, but it was unusable in just a little time. Using 10GB seems fine, but get's a lot bounced. The connections stable and responsive with just occasional packet loss, but bounced is 6307 right now. On 4/2/2013 7:56 PM, Adrian Chadd wrote: > On 2 April 2013 17:33, Joshua Isom wrote: >> But this really will be interesting. It seems to be fine at 8GB of ram, not >> just at 4GB. I'm not getting any dma issues or dropped packets so far. But >> booting with 12GB will cause problems. > > Chances are at 8GB of RAM it's just not bouncing a _lot_. > > > > Adrian > From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 3 01:18:10 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 89E11748 for ; Wed, 3 Apr 2013 01:18:10 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x232.google.com (mail-we0-x232.google.com [IPv6:2a00:1450:400c:c03::232]) by mx1.freebsd.org (Postfix) with ESMTP id 1E0EA966 for ; Wed, 3 Apr 2013 01:18:09 +0000 (UTC) Received: by mail-we0-f178.google.com with SMTP id z53so832452wey.9 for ; Tue, 02 Apr 2013 18:18:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=NUTdwIFSAsryJHEubeQqHD3XMDrQ2iTJVFPHPvNYXKI=; b=NT/4hAwPfk2QyS5yjtEyDYsAAh041n0JrngU2detsdtK0WmlG/kB1LR2qTYdsDUfW2 +KVa4CSVkbq1gadqcFD1Qoej+n7JUuNraDHglhwiZeaMWMaii9n9hHeiA9mOjnwY+3D5 R3+tCVkQ23JX4fjpInKdT7uZGtogR+PTC4seoBeZwHMmG+xCE2QbllP/TzpK/y4pVbIc ugG0ojtasb0X4mvXnNLxxgDsim4cxdazA0CPU9VOHGqPyI1vuQnV2r4sdBPnxDunEvZj VNHtkgywfD9FdBfo/mAuJ7x+zjVg5pC7/8XkMD912x9DymiTigdAjpryw9PgKJ0NwOTc nMSQ== MIME-Version: 1.0 X-Received: by 10.180.13.34 with SMTP id e2mr19640386wic.29.1364951889245; Tue, 02 Apr 2013 18:18:09 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.108.130 with HTTP; Tue, 2 Apr 2013 18:18:09 -0700 (PDT) In-Reply-To: <515B8233.9000603@gmail.com> References: <515892C4.1060002@gmail.com> <5158b7db.897aec0a.42d0.ffffaac4@mx.google.com> <5159F66B.2040600@gmail.com> <5159FF12.8030702@gmail.com> <515B4E16.3050901@gmail.com> <515B76A6.7080804@gmail.com> <515B78C2.20609@gmail.com> <515B8233.9000603@gmail.com> Date: Tue, 2 Apr 2013 18:18:09 -0700 X-Google-Sender-Auth: szmnkdLGUBZiPPFyHclUSe9mhos Message-ID: Subject: Re: ath not working after a motherboard and ram upgrade From: Adrian Chadd To: Joshua Isom 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: Wed, 03 Apr 2013 01:18:10 -0000 On 2 April 2013 18:13, Joshua Isom wrote: > I went half an hour being ok, and 12GB was dropping TCP connections in five > minutes. I'm estimating a little, but it was unusable in just a little > time. > > Using 10GB seems fine, but get's a lot bounced. The connections stable and > responsive with just occasional packet loss, but bounced is 6307 right now. Bouncing is fine. Why bouncing is broken in the ath driver, I don't yet know. Sounds like I need to acquire a machine with 32GB RAM. Sigh. Adrian From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 3 01:42:59 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 33478E1F; Wed, 3 Apr 2013 01:42:59 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-qa0-f45.google.com (mail-qa0-f45.google.com [209.85.216.45]) by mx1.freebsd.org (Postfix) with ESMTP id D3391B33; Wed, 3 Apr 2013 01:42:58 +0000 (UTC) Received: by mail-qa0-f45.google.com with SMTP id hg5so1811644qab.18 for ; Tue, 02 Apr 2013 18:42:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=qSxJ5whp+26qXdHSLK4qB5fNIOKvEuGxougX85GyRCw=; b=gpijhA2Md24PtUUz8dRfYldycndLmDEeL9gFizxo+oYkUV9BYhKZB4PX8srx55CM9C ns/Cdp8F7Z1VLueN/QJvLZiTrIlmJmvoZGM/YXNecQD3SGOChZ8RHTRlVv/IJIJ1Ji2N M9/AsC3CG3VckL0dv7/Dmiyz+P7dKSgYdPHF3zEmR6y49zdDWJyrqPNXN0bJRTTT5oC0 gub9zD9rR90NNxxrbqrqkLnIAKQvsYtNDCLqFOOfP1QcX8ZjdNlbjRuaBXNwHIJjiVty PKSp1HKEu9rm9tSSVnXtLQZa1IlNa9VUw3wlZ3rUMEYRzfi77SihnFv9MfVtUDKBjTMP w/hg== X-Received: by 10.49.11.178 with SMTP id r18mr19717069qeb.56.1364953372043; Tue, 02 Apr 2013 18:42:52 -0700 (PDT) Received: from [192.168.1.34] (c-98-212-197-211.hsd1.il.comcast.net. [98.212.197.211]) by mx.google.com with ESMTPS id hm4sm5642255qab.2.2013.04.02.18.42.50 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 02 Apr 2013 18:42:51 -0700 (PDT) Message-ID: <515B8914.8030303@gmail.com> Date: Tue, 02 Apr 2013 20:42:44 -0500 From: Joshua Isom User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: ath not working after a motherboard and ram upgrade References: <515892C4.1060002@gmail.com> <5159F66B.2040600@gmail.com> <5159FF12.8030702@gmail.com> <515B4E16.3050901@gmail.com> <515B76A6.7080804@gmail.com> <515B78C2.20609@gmail.com> <515B8233.9000603@gmail.com> In-Reply-To: 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.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: Wed, 03 Apr 2013 01:42:59 -0000 I sent the sysctl booting with 12GB. 11GB + 1023MB is bad, 11GB + 512MB is fine. It failed within a couple minutes. I'd rather not split hairs and find out which amount of megs breaks it. But I noticed when it was failing, active_bpages was increasing, every other time it's zero. On 4/2/2013 8:18 PM, Adrian Chadd wrote: > On 2 April 2013 18:13, Joshua Isom wrote: >> I went half an hour being ok, and 12GB was dropping TCP connections in five >> minutes. I'm estimating a little, but it was unusable in just a little >> time. >> >> Using 10GB seems fine, but get's a lot bounced. The connections stable and >> responsive with just occasional packet loss, but bounced is 6307 right now. > > Bouncing is fine. Why bouncing is broken in the ath driver, I don't yet know. > > Sounds like I need to acquire a machine with 32GB RAM. Sigh. > > > > Adrian > From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 3 03:06:56 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 42F73A18 for ; Wed, 3 Apr 2013 03:06:56 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) by mx1.freebsd.org (Postfix) with ESMTP id C6E20F2F for ; Wed, 3 Apr 2013 03:06:55 +0000 (UTC) Received: by mail-wi0-f171.google.com with SMTP id hn17so3173183wib.4 for ; Tue, 02 Apr 2013 20:06:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=ZzrYos8RH9wOjIvE3PUTf/znCiTb0z/8Nol0ExRKmto=; b=e/ejpqf7ioVZsbZYu6I5AiIFPiRBaROaIQ9SZGGQRWyPoTROsSmPiHBktsqnPDe3bD axg2ALHJ5CXLwK/0exZ0WFeSJNtEqVbohRwf/smA3uPmnTswgNDfpEtqXvlp1ldUyJBj JpX1DWFqg5QFGk3neqUmQ4Fgs4sqjr/WYJdyGEk8t6IaMxn5djfU0y+Ou4VRRT9QLPlb Ora0jiM3aApMjPTL+3MsJy7FJbVZg7XNYG/Aay3e6nlkMnGhmhyvhqTQzC1VSuW2vzvA 0mPANz/smYYMuiwHSBKVMN3Jr5tJ8/iIhMm24vrHjDsWk7tBrst+eT0eJFRkZPM93ZGO waYw== MIME-Version: 1.0 X-Received: by 10.194.120.169 with SMTP id ld9mr25953897wjb.24.1364958414941; Tue, 02 Apr 2013 20:06:54 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.108.130 with HTTP; Tue, 2 Apr 2013 20:06:54 -0700 (PDT) In-Reply-To: <515B8914.8030303@gmail.com> References: <515892C4.1060002@gmail.com> <5159F66B.2040600@gmail.com> <5159FF12.8030702@gmail.com> <515B4E16.3050901@gmail.com> <515B76A6.7080804@gmail.com> <515B78C2.20609@gmail.com> <515B8233.9000603@gmail.com> <515B8914.8030303@gmail.com> Date: Tue, 2 Apr 2013 20:06:54 -0700 X-Google-Sender-Auth: lZ74XB8gpfJQ34y4aLAhWIMmT3I Message-ID: Subject: Re: ath not working after a motherboard and ram upgrade From: Adrian Chadd To: Joshua Isom 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: Wed, 03 Apr 2013 03:06:56 -0000 So, can you test end-to-end pings? With full memory booted up? What I'd like to try and do is narrow down whether it's a TX or RX (or both.) Do you have control over something on the other end? Can you tcpdump the wifi interface and see if it's pings, pongs, or both being disabled? Also, can you disable 11n and see if you end up with the same behaviour? ifconfig wlan0 -ampdu, before you run wpa_supplicant. Thanks, Adrian From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 3 03:12:25 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 32D2FB69; Wed, 3 Apr 2013 03:12:25 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 96BEEF6C; Wed, 3 Apr 2013 03:12:24 +0000 (UTC) Received: by mail-wg0-f50.google.com with SMTP id k13so1145615wgh.29 for ; Tue, 02 Apr 2013 20:12:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=FSN91XzTT9BMOVsBR6CCLyp545bmN0FCO1++CwLIp84=; b=RxGEVB37dYI2zhGslDmpuiD4rU89a+BbwxlSYgDVhSrdHqCjOpYY2owK4BTdhn4VmS TmqKNwPDiNy/u9cMre6gycKXadoExErEY1ckf+ZkFh5KMSDS5uoaSlzfjCY1Oz4BjZo/ tnAhULXQnQ1BmLtf1806DtxJtbMb6cICTsXy8Ef+uxJAdjQk2pI3/N7TaNI9pqZTsVd3 chz3Lcb+Mw22cAJeBu7wnic+aFlFppnVpRNqwhfWF6VZ0WBvJo6bu2mRhyDyGvkKF+wo 2lt5Tzr6pfnP9jF1IJz8JxnRBFFvftW+kpfrz64ymV3A/roY2GlZptTYjYZBjH1jfi/O 5nkw== MIME-Version: 1.0 X-Received: by 10.180.13.34 with SMTP id e2mr20025630wic.29.1364958743384; Tue, 02 Apr 2013 20:12:23 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.108.130 with HTTP; Tue, 2 Apr 2013 20:12:23 -0700 (PDT) In-Reply-To: <86k3om5k87.fsf@orwell.Elisa> References: <86sj3as31d.fsf@orwell.Elisa> <86k3oms2ra.fsf@orwell.Elisa> <86k3om5k87.fsf@orwell.Elisa> Date: Tue, 2 Apr 2013 20:12:23 -0700 X-Google-Sender-Auth: RsoYr4WcJ6fqrMnnvyWSLWOivno Message-ID: Subject: Re: [rft] ar9300 HAL updated From: Adrian Chadd To: Raphael Kubo da Costa 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: Wed, 03 Apr 2013 03:12:25 -0000 On 1 April 2013 08:44, Raphael Kubo da Costa wrote: > On a side note: this card is also supposed to provide Bluetooth support, > right? Is any of your work going to help with that as well? I forget what the deal is there. I think it'll work out of the box on AR9485, but the coexistence won't work. So you'll get packet loss form both sides. I have no ETA on including all the bluetooth coexistence, sorry. Adrian From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 3 17:53:53 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 66EEC6E0 for ; Wed, 3 Apr 2013 17:53:53 +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 EDD2D2F8 for ; Wed, 3 Apr 2013 17:53:52 +0000 (UTC) Received: by mail-wg0-f52.google.com with SMTP id n12so1931921wgh.7 for ; Wed, 03 Apr 2013 10:53:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=jTla/a4oW4b0dZzKngLi/nNkrvVZwTT627mzrPEukHI=; b=UhXSbi7RuDAOGWAJYLMJkFEWP+mJRa2MpaqehN31/lQeo1ReHlFuYAFmYOYyXI2uQE XBSqtTMga5zT1P2HPyMksdhOtaz0qaA/cNDKWdZnCtGqlF6U2wvzif9vyfyoNMadcnpa WVFSi7oz2ckMdBF2jqtqfcuIUmVdKMifOET9WrtfCTd5K3qxdz1hX1jLekczZOBNQIox dR9ow3qKhDL77G4pqw5eKlgSnn+J6m229uYL8iyyJWQti58Q5fpmCM8U4f/2YLNB2uTW WgdnmCE5SUs0n9GNzBS94w/PP9EQ1iSFIyQZQRabfv/HJVUEhwlzaNnYkwLRDbrQ6oJe gK+g== MIME-Version: 1.0 X-Received: by 10.180.73.212 with SMTP id n20mr4279514wiv.11.1365011626414; Wed, 03 Apr 2013 10:53:46 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.243.7 with HTTP; Wed, 3 Apr 2013 10:53:46 -0700 (PDT) In-Reply-To: References: <515892C4.1060002@gmail.com> <5159F66B.2040600@gmail.com> <5159FF12.8030702@gmail.com> <515B4E16.3050901@gmail.com> <515B76A6.7080804@gmail.com> <515B78C2.20609@gmail.com> <515B8233.9000603@gmail.com> <515B8914.8030303@gmail.com> Date: Wed, 3 Apr 2013 10:53:46 -0700 X-Google-Sender-Auth: 7Es_Jh_qr3WUsS2Zhakl0TrB-Cc Message-ID: Subject: Re: ath not working after a motherboard and ram upgrade From: Adrian Chadd To: Joshua Isom 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: Wed, 03 Apr 2013 17:53:53 -0000 ..Hi, Please try this patch against the latest -HEAD with the full amount of system RAM: http://people.freebsd.org/~adrian/ath/20130403-ath-rx-unmap-first.diff It may not fix issues (especially if there are TX issues I haven't picked up yet), but it shouldn't break anything. Thanks, Adrian From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 3 22:16:25 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 36987607; Wed, 3 Apr 2013 22:16:25 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) by mx1.freebsd.org (Postfix) with ESMTP id E397D2E4; Wed, 3 Apr 2013 22:16:24 +0000 (UTC) Received: by mail-ob0-f176.google.com with SMTP id er7so1890459obc.7 for ; Wed, 03 Apr 2013 15:16:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=qRpL/g0qpvcCReDbE/Vx8UruUQD0I6h3rb4LuTcq/Oo=; b=C9Gs1owGLROYqpJee3OmOq6Nsp//bYmPoRxcoOZEb6eWphnlLnL6mULgC0MJbClw/H s9EOFZZkZHQdmhF29lc4mWj6QYMQkZoZwGkqOvVBRySQF7jXNi8Y/8DnZTtV/PyETf64 0ep8uO3d7oOpV7yzcvc9ZNN0CLVPi0sh7ksZc9Ac2XTRYrmumWRh6Q+N3JXHqeDCu8v0 6HJ2CgYwAK5nJQ5fgfH/R5irjUePggdFHyeszr+/XiEk8s++WbIricrW9NHuOAVcXw4+ ozzmDJhXPKVs1nLpOrofj78PVSjSXbDUuJ2H1GfnKepJM02CJjeabK3ienjsm/fjZB3Q 1xvQ== X-Received: by 10.182.66.41 with SMTP id c9mr2303946obt.76.1365027384517; Wed, 03 Apr 2013 15:16:24 -0700 (PDT) Received: from [192.168.1.34] (c-98-212-197-211.hsd1.il.comcast.net. [98.212.197.211]) by mx.google.com with ESMTPS id l4sm3944159oek.3.2013.04.03.15.16.22 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 03 Apr 2013 15:16:23 -0700 (PDT) Message-ID: <515CAA36.70002@gmail.com> Date: Wed, 03 Apr 2013 17:16:22 -0500 From: Joshua Isom User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: ath not working after a motherboard and ram upgrade References: <515892C4.1060002@gmail.com> <5159FF12.8030702@gmail.com> <515B4E16.3050901@gmail.com> <515B76A6.7080804@gmail.com> <515B78C2.20609@gmail.com> <515B8233.9000603@gmail.com> <515B8914.8030303@gmail.com> In-Reply-To: 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.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: Wed, 03 Apr 2013 22:16:25 -0000 So far, with the patch, pings are sent but not recieved so it has to be on the rx side. I wasn't noticing any dropped from being sent, but maybe I needed to wait longer and paid closer attention. I can't seem to get a network connection with 32GB, but I think that's just dhcp failing. I still need to try a lower amount of ram. While trying with `ifconfig wlan0 -ampdu` I couldn't get it to work. It might have just been me bringing up the wireless network manually only once before. I did get some different kernel messages. They're not normally appearing without the -ampdu. > Apr 3 16:59:10 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0 > Apr 3 16:59:10 jri kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: i=112, nbufs=128? > Apr 3 16:59:10 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0 > Apr 3 16:59:16 jri last message repeated 26 times > Apr 3 16:59:16 jri kernel: wlan0: link state changed to UP > Apr 3 16:59:29 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 14 > Apr 3 16:59:30 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0 > Apr 3 16:59:33 jri last message repeated 2 times > Apr 3 16:59:33 jri kernel: wlan0: link state changed to DOWN > Apr 3 16:59:33 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0 > Apr 3 16:59:33 jri kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: i=112, nbufs=128? > Apr 3 16:59:33 jri kernel: wlan0: link state changed to UP > Apr 3 16:59:33 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 112 > Apr 3 16:59:38 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0 > Apr 3 16:59:38 jri kernel: wlan0: link state changed to DOWN > Apr 3 16:59:38 jri dhclient[1486]: send_packet: Network is down > Apr 3 16:59:38 jri kernel: wlan0: link state changed to UP > Apr 3 16:59:38 jri kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: i=112, nbufs=128? > Apr 3 16:59:38 jri kernel: ath0: ath_tx_tid_drain_print: norm: node 0xffffff800b179000: bf=0xffffff8000aee640: addbaw=0, dobaw=0, seqno=0, retry=0 > Apr 3 16:59:38 jri kernel: ath0: ath_tx_tid_drain_print: node 0xffffff800b179000: bf=0xffffff8000aee640: txq[3] axq_depth=0, axq_aggr_depth=0 > Apr 3 16:59:38 jri kernel: ath0: ath_tx_tid_drain_print: node 0xffffff800b179000: bf=0xffffff8000aee640: tid txq_depth=6 hwq_depth=2, bar_wait=0, isfiltered=0 > Apr 3 16:59:38 jri kernel: ath0: ath_tx_tid_drain_print: node 0xffffff800b179000: tid 16: sched=1, paused=0, incomp=0, baw_head=0, baw_tail=0 txa_start=-1, ni_txseqs=22 > Apr 3 16:59:38 jri kernel: NODS 64:70:02:18:6d:95->c0:c1:c0:35:19:88(c0:c1:c0:35:19:88) assoc_req 0M > Apr 3 16:59:38 jri kernel: 0000 0000 c0c1 c035 1988 6470 0218 6d95 c0c1 c035 1988 0001 1104 0100 0006 666f 6f62 6172 0108 8284 8b0c 1296 1824 3014 0100 000f ac04 0100 000f ac04 0100 000f ac02 0000 3204 3048 606c 2d1a ee01 1bff ffff 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 dd07 0050 f202 0001 00 > Apr 3 16:59:38 jri kernel: wlan0: link state changed to DOWN > Apr 3 16:59:38 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 112 > Apr 3 16:59:38 jri kernel: ath0: ath_tx_tid_drain_print: norm: node 0xffffff800b179000: bf=0xffffff8000aeec80: addbaw=0, dobaw=0, seqno=0, retry=0 > Apr 3 16:59:38 jri kernel: ath0: ath_tx_tid_drain_print: node 0xffffff800b179000: bf=0xffffff8000aeec80: txq[3] axq_depth=0, axq_aggr_depth=0 > Apr 3 16:59:38 jri kernel: ath0: ath_tx_tid_drain_print: node 0xffffff800b179000: bf=0xffffff8000aeec80: tid txq_depth=1 hwq_depth=2, bar_wait=0, isfiltered=0 > Apr 3 16:59:38 jri kernel: ath0: ath_tx_tid_drain_print: node 0xffffff800b179000: tid 16: sched=1, paused=0, incomp=0, baw_head=0, baw_tail=0 txa_start=-1, ni_txseqs=23 > Apr 3 16:59:38 jri kernel: NODS 64:70:02:18:6d:95->c0:c1:c0:35:19:88(c0:c1:c0:35:19:88) assoc_req 0M > Apr 3 16:59:38 jri kernel: 0000 0000 c0c1 c035 1988 6470 0218 6d95 c0c1 c035 1988 6001 1104 0100 0006 666f 6f62 > Apr 3 16:59:38 jri kernel: wlan0: link state changed to UP > Apr 3 16:59:38 jri kernel: 6172 0108 8284 8b0c 1296 1824 3014 0100 000f ac04 0100 000f ac04 0100 000f ac02 0000 3204 3048 606c 2d1a ee01 1bff ffff 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 dd07 0050 f202 0001 00 > Apr 3 16:59:38 jri kernel: wlan0: link state changed to DOWN > Apr 3 16:59:38 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0 > Apr 3 16:59:38 jri kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: i=112, nbufs=128? > Apr 3 16:59:38 jri kernel: wlan0: link state changed to UP > Apr 3 16:59:38 jri kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: i=0, nbufs=128? > Apr 3 16:59:38 jri kernel: ath0: ath_edma_recv_proc_queue: Q1: NULL bf? > Apr 3 16:59:38 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0 > Apr 3 16:59:38 jri kernel: ath0: ath_tx_tid_drain_print: norm: node 0xffffff800b179000: bf=0xffffff8000aeee10: addbaw=0, dobaw=0, seqno=0, retry=0 > Apr 3 16:59:38 jri kernel: ath0: ath_tx_tid_drain_print: node 0xffffff800b179000: bf=0xffffff8000aeee10: txq[3] axq_depth=0, axq_aggr_depth=0 > Apr 3 16:59:38 jri kernel: ath0: ath_tx_tid_drain_print: node 0xffffff800b179000: bf=0xffffff8000aeee10: tid txq_depth=5 hwq_depth=2, bar_wait=0, isfiltered=0 > Apr 3 16:59:38 jri kernel: ath0: ath_tx_tid_drain_print: node 0xffffff800b179000: tid 16: sched=1, paused=0, incomp=0, baw_head=0, baw_tail=0 txa_start=-1, ni_txseqs=30 > Apr 3 16:59:38 jri kernel: NODS 64:70:02:18:6d:95->c0:c1:c0:35:19:88(c0:c1:c0:35:19:88) assoc_req 0M > Apr 3 16:59:38 jri kernel: 0000 0000 c0c1 c035 1988 6470 0218 6d95 c0c1 c035 1988 7001 1104 0100 0006 666f 6f62 6172 0108 8284 8b0c 1296 1824 3014 0100 000f ac04 0100 000f ac04 0100 000f ac02 0000 3204 3048 606c 2d1a ee01 1bff ffff 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 dd07 0050 f202 0001 00 > Apr 3 16:59:38 jri kernel: wlan0: link state changed to DOWN > Apr 3 16:59:38 jri kernel: wlan0: link state changed to UP > Apr 3 16:59:38 jri kernel: wlan0: link state changed to DOWN > Apr 3 16:59:38 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 128 > Apr 3 16:59:38 jri kernel: wlan0: link state changed to UP > Apr 3 16:59:45 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0 > Apr 3 16:59:48 jri last message repeated 2 times > Apr 3 16:59:48 jri kernel: wlan0: link state changed to DOWN > Apr 3 16:59:48 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0 > Apr 3 16:59:51 jri last message repeated 13 times > Apr 3 16:59:51 jri kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: i=112, nbufs=128? > Apr 3 16:59:51 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0 > Apr 3 16:59:54 jri last message repeated 14 times > Apr 3 16:59:54 jri kernel: wlan0: ieee80211_new_state_locked: pending AUTH -> ASSOC transition lost > Apr 3 16:59:59 jri dhclient[1486]: send_packet: Network is down > Apr 3 17:00:03 jri dhclient: New IP Address (wlan0): 192.168.1.2 > Apr 3 17:00:03 jri dhclient: New Subnet Mask (wlan0): 255.255.255.0 > Apr 3 17:00:03 jri dhclient: New Broadcast Address (wlan0): 192.168.1.255 > Apr 3 17:00:03 jri dhclient: New Routers (wlan0): 192.168.1.1 > Apr 3 17:00:04 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0 > Apr 3 17:00:04 jri dhclient: New Routers (wlan0): 192.168.1.1 > Apr 3 17:00:04 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0 > Apr 3 17:00:07 jri last message repeated 11 times > Apr 3 17:00:07 jri kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: i=112, nbufs=128? > Apr 3 17:00:07 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0 > Apr 3 17:00:10 jri last message repeated 14 times > Apr 3 17:00:10 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 128 > Apr 3 17:00:10 jri kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: i=112, nbufs=128? > Apr 3 17:00:10 jri kernel: wlan0: link state changed to UP > Apr 3 17:00:10 jri kernel: ath0: ath_tx_tid_drain_print: norm: node 0xffffff8005ece000: bf=0xffffff8000aeeaf0: addbaw=0, dobaw=0, seqno=0, retry=0 > Apr 3 17:00:10 jri kernel: ath0: ath_tx_tid_drain_print: node 0xffffff8005ece000: bf=0xffffff8000aeeaf0: txq[3] axq_depth=0, axq_aggr_depth=0 > Apr 3 17:00:10 jri kernel: ath0: ath_tx_tid_drain_print: node 0xffffff8005ece000: bf=0xffffff8000aeeaf0: tid txq_depth=2 hwq_depth=2, bar_wait=0, isfiltered=0 > Apr 3 17:00:10 jri kernel: ath0: ath_tx_tid_drain_print: node 0xffffff8005ece000: tid 16: sched=1, paused=0, incomp=0, baw_head=0, baw_tail=0 txa_start=-1, ni_txseqs=5 > Apr 3 17:00:10 jri kernel: NODS 64:70:02:18:6d:95->c0:c1:c0:35:19:88(c0:c1:c0:35:19:88) action 0M > Apr 3 17:00:10 jri kernel: d000 0000 c0c1 c035 1988 6470 0218 6d95 c0c1 c035 1988 3000 0301 cc01 0002 0000 00 > Apr 3 17:00:10 jri kernel: wlan0: link state changed to DOWN > Apr 3 17:00:10 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 112 > Apr 3 17:00:10 jri kernel: wlan0: link state changed to UP > Apr 3 17:00:10 jri kernel: ath0: ath_tx_tid_drain_print: norm: node 0xffffff8005ece000: bf=0xffffff8000aee320: addbaw=0, dobaw=0, seqno=0, retry=0 > Apr 3 17:00:10 jri kernel: ath0: ath_tx_tid_drain_print: node 0xffffff8005ece000: bf=0xffffff8000aee320: txq[3] axq_depth=0, axq_aggr_depth=0 > Apr 3 17:00:10 jri kernel: ath0: ath_tx_tid_drain_print: node 0xffffff8005ece000: bf=0xffffff8000aee320: tid txq_depth=7 hwq_depth=2, bar_wait=0, isfiltered=0 > Apr 3 17:00:10 jri kernel: ath0: ath_tx_tid_drain_print: node 0xffffff8005ece000: tid 16: sched=1, paused=0, incomp=0, baw_head=0, baw_tail=0 txa_start=-1, ni_txseqs=12 > Apr 3 17:00:10 jri kernel: NODS 64:70:02:18:6d:95->c0:c1:c0:35:19:88(c0:c1:c0:35:19:88) assoc_req 0M > Apr 3 17:00:10 jri kernel: 0000 0000 c0c1 c035 1988 6470 0218 6d95 c0c1 c035 1988 5000 1104 0100 0006 666f 6f62 6172 0108 8284 8b0c 1296 1824 3014 0100 000f ac04 0100 000f ac04 0100 000f ac02 0000 3204 3048 606c 2d1a ee01 1bff ffff 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 dd07 0050 f202 0001 00 > Apr 3 17:00:10 jri kernel: wlan0: link state changed to DOWN > Apr 3 17:00:10 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0 > Apr 3 17:00:10 jri kernel: wlan0: ieee80211_new_state_locked: pending ASSOC -> AUTH transition lost > Apr 3 17:00:10 jri kernel: wlan0: ieee80211_new_state_locked: pending ASSOC -> RUN transition lost > Apr 3 17:00:10 jri last message repeated 2 times > Apr 3 17:00:10 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0 > Apr 3 17:00:11 jri last message repeated 3 times > Apr 3 17:00:11 jri kernel: wlan0: ieee80211_new_state_locked: pending ASSOC -> RUN transition lost > Apr 3 17:00:11 jri last message repeated 8 times > Apr 3 17:00:11 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0 > Apr 3 17:00:11 jri kernel: wlan0: ieee80211_new_state_locked: pending ASSOC -> AUTH transition lost > Apr 3 17:00:11 jri kernel: wlan0: ieee80211_new_state_locked: pending ASSOC -> AUTH transition lost > Apr 3 17:00:11 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0 > Apr 3 17:00:13 jri last message repeated 9 times > Apr 3 17:00:13 jri kernel: wlan0: ieee80211_new_state_locked: pending ASSOC -> RUN transition lost > Apr 3 17:00:13 jri last message repeated 3 times > Apr 3 17:00:14 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0 > Apr 3 17:00:16 jri last message repeated 12 times > Apr 3 17:00:16 jri kernel: wlan0: link state changed to UP > Apr 3 17:00:16 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0 > Apr 3 17:00:16 jri kernel: wlan0: link state changed to DOWN > Apr 3 17:00:16 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 128 > Apr 3 17:00:16 jri kernel: wlan0: link state changed to UP > Apr 3 17:00:16 jri kernel: ath0: ath_tx_tid_drain_print: norm: node 0xffffff8005ee7000: bf=0xffffff8000aee190: addbaw=0, dobaw=0, seqno=0, retry=0 > Apr 3 17:00:16 jri kernel: ath0: ath_tx_tid_drain_print: node 0xffffff8005ee7000: bf=0xffffff8000aee190: txq[3] axq_depth=0, axq_aggr_depth=0 > Apr 3 17:00:16 jri kernel: ath0: ath_tx_tid_drain_print: node 0xffffff8005ee7000: bf=0xffffff8000aee190: tid txq_depth=2 hwq_depth=2, bar_wait=0, isfiltered=0 > Apr 3 17:00:16 jri kernel: ath0: ath_tx_tid_drain_print: node 0xffffff8005ee7000: tid 16: sched=1, paused=0, incomp=0, baw_head=0, baw_tail=0 txa_start=-1, ni_txseqs=4 > Apr 3 17:00:16 jri kernel: NODS 64:70:02:18:6d:95->c0:c1:c0:35:19:88(c0:c1:c0:35:19:88) action 0M > Apr 3 17:00:16 jri kernel: d000 0000 c0c1 c035 1988 6470 0218 6d95 c0c1 c035 1988 2000 0301 cd01 0002 0000 00 > Apr 3 17:00:16 jri kernel: wlan0: link state changed to DOWN > Apr 3 17:00:16 jri kernel: wlan0: link state changed to UP > Apr 3 17:00:16 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0 > Apr 3 17:00:16 jri kernel: wlan0: link state changed to DOWN > Apr 3 17:00:16 jri kernel: wlan0: link state changed to UP > Apr 3 17:00:16 jri kernel: wlan0: link state changed to DOWN > Apr 3 17:00:16 jri kernel: wlan0: link state changed to UP > Apr 3 17:00:16 jri kernel: wlan0: link state changed to DOWN > Apr 3 17:00:17 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0 > Apr 3 17:00:17 jri kernel: wlan0: ieee80211_new_state_locked: pending ASSOC -> RUN transition lost > Apr 3 17:00:17 jri last message repeated 8 times > Apr 3 17:00:17 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0 > Apr 3 17:00:17 jri last message repeated 3 times > Apr 3 17:00:17 jri kernel: wlan0: ieee80211_new_state_locked: pending ASSOC -> RUN transition lost > Apr 3 17:00:17 jri last message repeated 2 times > Apr 3 17:00:17 jri kernel: wlan0: ieee80211_new_state_locked: pending ASSOC -> AUTH transition lost > Apr 3 17:00:18 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0 > Apr 3 17:00:20 jri last message repeated 9 times > Apr 3 17:00:20 jri kernel: wlan0: ieee80211_new_state_locked: pending ASSOC -> RUN transition lost > Apr 3 17:00:20 jri kernel: wlan0: ieee80211_new_state_locked: pending ASSOC -> AUTH transition lost > Apr 3 17:00:20 jri kernel: wlan0: ieee80211_new_state_locked: pending ASSOC -> RUN transition lost > Apr 3 17:00:20 jri kernel: wlan0: ieee80211_new_state_locked: pending ASSOC -> AUTH transition lost > Apr 3 17:00:20 jri kernel: wlan0: ieee80211_new_state_locked: pending ASSOC -> RUN transition lost > Apr 3 17:00:20 jri kernel: ifa_del_loopback_route: deletion failed: 48 > Apr 3 17:00:20 jri kernel: wlan0: ieee80211_new_state_locked: pending ASSOC -> RUN transition lost > Apr 3 17:00:20 jri last message repeated 8 times > Apr 3 17:00:20 jri kernel: wlan0: ieee80211_new_state_locked: pending ASSOC -> AUTH transition lost > Apr 3 17:00:20 jri kernel: wlan0: ieee80211_new_state_locked: pending ASSOC -> RUN transition lost > Apr 3 17:00:20 jri dhclient[1598]: Interface wlan0 is down, dhclient exiting > Apr 3 17:00:20 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0 > Apr 3 17:00:20 jri dhclient[1487]: connection closed > Apr 3 17:00:20 jri dhclient[1487]: exiting. > Apr 3 17:00:23 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0 > Apr 3 17:00:23 jri last message repeated 5 times > Apr 3 17:00:23 jri kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: i=112, nbufs=128? > Apr 3 17:00:23 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 128 > Apr 3 17:00:23 jri kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: i=0, nbufs=128? > Apr 3 17:00:23 jri kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: i=0, nbufs=128? > Apr 3 17:00:23 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0 > Apr 3 17:00:26 jri last message repeated 11 times > Apr 3 17:00:26 jri kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: i=112, nbufs=128? > Apr 3 17:00:26 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0 > Apr 3 17:00:29 jri last message repeated 12 times > Apr 3 17:00:29 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 63 > Apr 3 17:00:29 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0 > Apr 3 17:00:32 jri last message repeated 15 times > Apr 3 17:00:33 jri kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: i=112, nbufs=128? > Apr 3 17:00:33 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0 > Apr 3 17:00:35 jri last message repeated 9 times > Apr 3 17:00:35 jri kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: i=112, nbufs=128? > Apr 3 17:00:35 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0 > Apr 3 17:00:35 jri last message repeated 2 times > Apr 3 17:00:35 jri kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: i=112, nbufs=128? > Apr 3 17:00:35 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0 > Apr 3 17:00:35 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0 > Apr 3 17:00:35 jri kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: i=112, nbufs=128? > Apr 3 17:00:36 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0 > Apr 3 17:00:38 jri last message repeated 9 times > Apr 3 17:00:38 jri kernel: ifa_del_loopback_route: deletion failed: 48 > Apr 3 17:00:38 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0 > Apr 3 17:00:40 jri last message repeated 2 times > Apr 3 17:00:40 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 63 > Apr 3 17:00:41 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0 > Apr 3 17:00:41 jri last message repeated 3 times > Apr 3 17:00:41 jri kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: i=112, nbufs=128? > Apr 3 17:00:41 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 128 > Apr 3 17:00:41 jri kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: i=0, nbufs=128? > Apr 3 17:00:41 jri kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: i=0, nbufs=128? On 4/3/2013 12:53 PM, Adrian Chadd wrote: > ..Hi, > > Please try this patch against the latest -HEAD with the full amount of > system RAM: > > http://people.freebsd.org/~adrian/ath/20130403-ath-rx-unmap-first.diff > > It may not fix issues (especially if there are TX issues I haven't > picked up yet), but it shouldn't break anything. > > Thanks, > > > > Adrian > From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 3 23:16:11 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 5B890FDF for ; Wed, 3 Apr 2013 23:16:11 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) by mx1.freebsd.org (Postfix) with ESMTP id E2E3974D for ; Wed, 3 Apr 2013 23:16:10 +0000 (UTC) Received: by mail-wi0-f171.google.com with SMTP id hn17so4150099wib.16 for ; Wed, 03 Apr 2013 16:16:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=c+GKU/du5DeZ/ZjdcagGChPTSJjWdS7FLrvTyGD6GuY=; b=QcJ0uOBemSx+erdQnz5qcoJwm4kM2ohOtOXZtFsBPCMqTifqG/8+NPsOhi+bflxBf3 41R/KFOENgASkdv89fy/YXhzr4jPj+PyZWxQpeF8xG8prjjkaB5O7kpwZ9Hfg4kOyWQD 8FrijlHqjmdSWv8WfDWMKGuicxHn6dNnCZ5MER+phb+xGdYSfAk2YWIrxU2vXnHgijbr kHO3xid/QUvIobN5geRNP37Iqt8WPmliuo4aCYJhjm6kRVTsIYQ9yCOouWKWYvPJuT0/ GPEkWVB1qHguzdtoNLQ2pYyd+qlnS5SpFlRNLHlrC/nW2jBAG/e/2FElKUMsEMqQDvjL vKiA== MIME-Version: 1.0 X-Received: by 10.194.123.168 with SMTP id mb8mr5301988wjb.24.1365030970129; Wed, 03 Apr 2013 16:16:10 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.243.7 with HTTP; Wed, 3 Apr 2013 16:16:09 -0700 (PDT) In-Reply-To: <515CAA36.70002@gmail.com> References: <515892C4.1060002@gmail.com> <5159FF12.8030702@gmail.com> <515B4E16.3050901@gmail.com> <515B76A6.7080804@gmail.com> <515B78C2.20609@gmail.com> <515B8233.9000603@gmail.com> <515B8914.8030303@gmail.com> <515CAA36.70002@gmail.com> Date: Wed, 3 Apr 2013 16:16:09 -0700 X-Google-Sender-Auth: nPKk3EjQC7sD5OdE18cUQ1FT_zc Message-ID: Subject: Re: ath not working after a motherboard and ram upgrade From: Adrian Chadd To: Joshua Isom 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: Wed, 03 Apr 2013 23:16:11 -0000 Hi, Please try again, but tell me what the output of : sysctl hw.ath is. LEave ampdu on for now. The allocation failures are a bit odd; that only happens when you've compiled it without the 11n option enabled. Adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 4 00:22:30 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4A6B9F54; Thu, 4 Apr 2013 00:22:30 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-ob0-x22a.google.com (mail-ob0-x22a.google.com [IPv6:2607:f8b0:4003:c01::22a]) by mx1.freebsd.org (Postfix) with ESMTP id 029B8B28; Thu, 4 Apr 2013 00:22:29 +0000 (UTC) Received: by mail-ob0-f170.google.com with SMTP id wc20so2027108obb.15 for ; Wed, 03 Apr 2013 17:22:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=R7GIyRtGcR/08wCCaBqbvEuGVZyR82ypMLYfQj4HC+M=; b=QJF6xSQz7QDtvtzNOkMVQE0mah23adVRr8T7K3G3pKBUw1RRUfG1GhGdH70dRkLpzO 5xSEfaMjgmQGbzERq3FE7xE7JqsQx86WUy7qi2Kt3PFGhzAdG77okYXG+p5gmDitjJt4 nAzgsTbSLOPp0NQoYuLabIIlNL1oR7qWCnql88cO3GCWj+2SHCY5AtDJ61QHOjaxjThW cYU4gGsbzPwOce2R/ep7NdRJugny855/FPeYWlMFRdhmQW9pfoiRJ0XR7GUv11Ut8IS4 l6sQzlgtDV06LTjOzWB13tKXXzFkLe8+sQby9ZWP5Q5NdpJlgxLeIHYpyBbDmwl/5SUg ic9A== X-Received: by 10.182.169.103 with SMTP id ad7mr2588712obc.51.1365034949678; Wed, 03 Apr 2013 17:22:29 -0700 (PDT) Received: from [192.168.1.34] (c-98-212-197-211.hsd1.il.comcast.net. [98.212.197.211]) by mx.google.com with ESMTPS id a3sm4337886oee.8.2013.04.03.17.22.28 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 03 Apr 2013 17:22:29 -0700 (PDT) Message-ID: <515CC7C3.3070608@gmail.com> Date: Wed, 03 Apr 2013 19:22:27 -0500 From: Joshua Isom User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: ath not working after a motherboard and ram upgrade References: <515892C4.1060002@gmail.com> <515B4E16.3050901@gmail.com> <515B76A6.7080804@gmail.com> <515B78C2.20609@gmail.com> <515B8233.9000603@gmail.com> <515B8914.8030303@gmail.com> <515CAA36.70002@gmail.com> In-Reply-To: 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.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: Thu, 04 Apr 2013 00:22:30 -0000 I added -ampdu to rc.conf and it connected to the network, but still dropped packets. I'm not getting the network to work when I try it manually after boot. It could be me though, or something else wrong or not working properly. It's the same kernel as before except the patch, and that was the only time I was getting those messages. I checked hw.ath before, and after, there's no difference. hw.ath.longcal: 30 hw.ath.shortcal: 100 hw.ath.resetcal: 1200 hw.ath.anical: 100 hw.ath.rxbuf: 512 hw.ath.txbuf: 512 hw.ath.txbuf_mgmt: 32 hw.ath.bstuck: 4 hw.ath.debug: 0 hw.ath.hal.debug: 0 On 4/3/2013 6:16 PM, Adrian Chadd wrote: > Hi, > > Please try again, but tell me what the output of : > > sysctl hw.ath > > is. LEave ampdu on for now. > > The allocation failures are a bit odd; that only happens when you've > compiled it without the 11n option enabled. > > > > Adrian > From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 4 00:26:05 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 5282BFFB for ; Thu, 4 Apr 2013 00:26:05 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pd0-f180.google.com (mail-pd0-f180.google.com [209.85.192.180]) by mx1.freebsd.org (Postfix) with ESMTP id 296E0B6B for ; Thu, 4 Apr 2013 00:26:05 +0000 (UTC) Received: by mail-pd0-f180.google.com with SMTP id q11so1123234pdj.25 for ; Wed, 03 Apr 2013 17:26:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=9qzTm0ekd8E07WUeymGuuZ2SciZueGqFsEUEykO+Jlg=; b=QG6T0RJelV0N0ueFt6Fpff7lPKXmDDt9cRocfaxWPz2Jib4Z8JQYtntFkDAJgYuO/d +Vxbwbxzkvsra2w6yzaUh2I7qZyvezsd3lJ1tcAhja8IlMUIyGETTX1L9pWuKDpmBV5J oE5mc0RNvtqGJL0aFSsMbkjvTTazTMeSI9R0KKzJuMHVmE3SvxQpAyV9kgeM5vfmdMjj HA0mrTo3s+r5GAEauyMq4mIYJrpTvgY2W39RP9DsYDtB4slNIbL/TU3ofyurQCVUVTL8 k2G5XRo2f8wmJEyisxZlIVRHpSj2TMNY3JGRLAslKKI3K1s4n/clSv62UkBZX4PjgnT3 kbFw== MIME-Version: 1.0 X-Received: by 10.66.116.12 with SMTP id js12mr6385640pab.149.1365035164723; Wed, 03 Apr 2013 17:26:04 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.70.61.234 with HTTP; Wed, 3 Apr 2013 17:26:04 -0700 (PDT) In-Reply-To: <515CC7C3.3070608@gmail.com> References: <515892C4.1060002@gmail.com> <515B4E16.3050901@gmail.com> <515B76A6.7080804@gmail.com> <515B78C2.20609@gmail.com> <515B8233.9000603@gmail.com> <515B8914.8030303@gmail.com> <515CAA36.70002@gmail.com> <515CC7C3.3070608@gmail.com> Date: Wed, 3 Apr 2013 17:26:04 -0700 X-Google-Sender-Auth: A_RSMKGxKvKGw1weWJ3pOCVVzDE Message-ID: Subject: Re: ath not working after a motherboard and ram upgrade From: Adrian Chadd To: Joshua Isom 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: Thu, 04 Apr 2013 00:26:05 -0000 On 3 April 2013 17:22, Joshua Isom wrote: > I added -ampdu to rc.conf and it connected to the network, but still dropped > packets. I'm not getting the network to work when I try it manually after Ok. So it's not kooky stuff with aggregation handling. That said, you're already running a far-away network, so a lack of aggregation means that you're not doing software retried packets. :-) > boot. It could be me though, or something else wrong or not working > properly. It's the same kernel as before except the patch, and that was the CAn you please dump out the contents of hw.busdma after it's run and failed for a while? Then ifconfig wlan0 ; kldunload if_ath_pci ; kldload if_ath ; sysctl hw.busdma again. I'd like to see if it's leaking bounce buffers now. > only time I was getting those messages. I checked hw.ath before, and after, > there's no difference. So you're still seeing the FIFO allocation failures with this patch? The reason why RX FIFO allocations would fail here is because the bounce buffer allocation is failing. I doubt the mbuf allocation is failing. > hw.ath.longcal: 30 > hw.ath.shortcal: 100 > hw.ath.resetcal: 1200 > hw.ath.anical: 100 > hw.ath.rxbuf: 512 > hw.ath.txbuf: 512 > hw.ath.txbuf_mgmt: 32 > hw.ath.bstuck: 4 > hw.ath.debug: 0 > hw.ath.hal.debug: 0 Yup, that's correct. Adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 4 00:34:30 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B00FA223 for ; Thu, 4 Apr 2013 00:34:30 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f41.google.com (mail-pb0-f41.google.com [209.85.160.41]) by mx1.freebsd.org (Postfix) with ESMTP id 85120C0F for ; Thu, 4 Apr 2013 00:34:30 +0000 (UTC) Received: by mail-pb0-f41.google.com with SMTP id mc17so1142440pbc.14 for ; Wed, 03 Apr 2013 17:34:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=pkAu2e3f9+KZaI/2ojPI6VwgIIsaOIyu207WvTAdUjM=; b=rp2B0ZKbddwl/WZSFtV48rPrfe3xGYBZ/U2IHmEvxtwFvh8DcYVvBFJR13CRKNbv+Y nIyKh31WoDGFuLdCDr4DARe9XHTutAlNI4P3GA0oaroQQZXQ3uiO/KdcEH8/eb8Mex19 rtr69+OPaDjDsYGQUH3b/CjgkBnAV2POj7MYK5Of4/V7cFms1nSmu19VFC5LPYxt2v6q AckIwk4lsQzc0TXh30MaBm47iRTgAu5pmvI8DPx5sbX20yeWHgOR1fHwOVj4Rodqyxfc rMUwcomifNMCzw/FZtEkyOzkUQ4QxWDNQBHTT+DJbaNTcLe6mSPXGkafn1wThYuBm+oq dDiw== MIME-Version: 1.0 X-Received: by 10.68.233.74 with SMTP id tu10mr5789976pbc.57.1365035664717; Wed, 03 Apr 2013 17:34:24 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.70.61.234 with HTTP; Wed, 3 Apr 2013 17:34:24 -0700 (PDT) In-Reply-To: References: <515892C4.1060002@gmail.com> <515B4E16.3050901@gmail.com> <515B76A6.7080804@gmail.com> <515B78C2.20609@gmail.com> <515B8233.9000603@gmail.com> <515B8914.8030303@gmail.com> <515CAA36.70002@gmail.com> <515CC7C3.3070608@gmail.com> Date: Wed, 3 Apr 2013 17:34:24 -0700 X-Google-Sender-Auth: DYkUDO3gBSuE0mAnluDmEVMKxck Message-ID: Subject: Re: ath not working after a motherboard and ram upgrade From: Adrian Chadd To: Joshua Isom 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: Thu, 04 Apr 2013 00:34:30 -0000 .. ok, I finally can test it on an AR9580, and it's erroring out for me. It wasn't erroring out on an earlier NIC (AR5416) but that doesn't use EDMA. I'll go do some more debugging. Adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 4 00:45:03 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id BCEA8379 for ; Thu, 4 Apr 2013 00:45:03 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-da0-x22c.google.com (mail-da0-x22c.google.com [IPv6:2607:f8b0:400e:c00::22c]) by mx1.freebsd.org (Postfix) with ESMTP id 9279BCE0 for ; Thu, 4 Apr 2013 00:45:03 +0000 (UTC) Received: by mail-da0-f44.google.com with SMTP id z20so894289dae.17 for ; Wed, 03 Apr 2013 17:45:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=b4c9mok1RxO7LFesD4xY3H5qlLXYijq26sWuBqXqH9g=; b=TKpJ8xtYi7b35FWmSJKw465W5a8q228/ACpTT7et4mAiWKhUusVyzGsIBaX2hB+fWy tyMwSc0ZSe6CmOA8REI3U1qSrD0Vj4z239pJYfnCRR8fViwbFY5JzQ/VktutDrA+WMQD cdOyXUzLfzHNbSPQOwQ9b1nrELqUu7xOsQP481HPEP6/YWaG9fSLlgMf5E83tY7cof8J TEUKa4Pqb7CGqYyS/sL4EpF1w/nj0n/CfLXmLMeJiGrkRtlc2MKa2frqyM9Pq4kXOgQM boKaIxJ6kAksUL2Qih7kHF8zD5V58OND1MBSODl+q5mMGkFz3mz+nEZ9m1lvJNtl65a9 iLFQ== MIME-Version: 1.0 X-Received: by 10.66.150.198 with SMTP id uk6mr6528376pab.57.1365036303368; Wed, 03 Apr 2013 17:45:03 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.70.61.234 with HTTP; Wed, 3 Apr 2013 17:45:03 -0700 (PDT) In-Reply-To: References: <515892C4.1060002@gmail.com> <515B4E16.3050901@gmail.com> <515B76A6.7080804@gmail.com> <515B78C2.20609@gmail.com> <515B8233.9000603@gmail.com> <515B8914.8030303@gmail.com> <515CAA36.70002@gmail.com> <515CC7C3.3070608@gmail.com> Date: Wed, 3 Apr 2013 17:45:03 -0700 X-Google-Sender-Auth: i7_uQ8fB32MWBm8sXby7-rJ6uI0 Message-ID: Subject: Re: ath not working after a motherboard and ram upgrade From: Adrian Chadd To: Joshua Isom 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: Thu, 04 Apr 2013 00:45:03 -0000 On 3 April 2013 17:34, Adrian Chadd wrote: > .. ok, I finally can test it on an AR9580, and it's erroring out for me. > > It wasn't erroring out on an earlier NIC (AR5416) but that doesn't use EDMA. > > I'll go do some more debugging. Wow, there's some screwed up stuff right there. I don't get why it's failing at all. mbuf allocation shouldn't be failing at that point. NULL ath_buf entries shouldnt' be pushed onto the hardware. Wtf. Adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 4 01:00:22 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 6C1EA44B; Thu, 4 Apr 2013 01:00:22 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-oa0-f53.google.com (mail-oa0-f53.google.com [209.85.219.53]) by mx1.freebsd.org (Postfix) with ESMTP id 24A29D50; Thu, 4 Apr 2013 01:00:21 +0000 (UTC) Received: by mail-oa0-f53.google.com with SMTP id m17so2206998oag.26 for ; Wed, 03 Apr 2013 18:00:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=MJSR4X4ei5lDKRhfXCi+5htPKXjwr3/jUsESpdbVEwE=; b=rFf1a6c85/NO59R8pE1ZT3ELwxyp00ZSX8QDBEqSSBqn0NdIhOllhrMirmWnZI8gsa cYjlPKpLWj8cWckfA8ZOIkAmBtnUgv5r4v7XR6ZNAdv4XtKjMm3e+XhnY4gK72h9arXr QCSchX3GetUQmjAkLY7NqY4ORNleXlO/3cUxWsB7LN63Zc4F5Lfku1ZwOLFdtFEIs2LA TMQIHvlmk6cr4thV6ebW42BKDn+58Y6kU1caWPMSHOdnP3rfByuLcz5YNRAqNV9YMwDw kivHgN2U2bw0wWjKs3ZIJi5hLvAd5HKXzWo0VnjD6gBY0wd5s24YzXSew1bkf9msPe9q HmjA== X-Received: by 10.182.45.231 with SMTP id q7mr2650787obm.58.1365037221267; Wed, 03 Apr 2013 18:00:21 -0700 (PDT) Received: from [192.168.1.34] (c-98-212-197-211.hsd1.il.comcast.net. [98.212.197.211]) by mx.google.com with ESMTPS id be1sm4210611obb.11.2013.04.03.18.00.20 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 03 Apr 2013 18:00:20 -0700 (PDT) Message-ID: <515CD0A3.2020204@gmail.com> Date: Wed, 03 Apr 2013 20:00:19 -0500 From: Joshua Isom User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: ath not working after a motherboard and ram upgrade References: <515892C4.1060002@gmail.com> <515B4E16.3050901@gmail.com> <515B76A6.7080804@gmail.com> <515B78C2.20609@gmail.com> <515B8233.9000603@gmail.com> <515B8914.8030303@gmail.com> <515CAA36.70002@gmail.com> <515CC7C3.3070608@gmail.com> In-Reply-To: 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.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: Thu, 04 Apr 2013 01:00:22 -0000 It wasn't ran with -ampdu, but I guess that doesn't matter now. hw.busdma.total_bpages: 8250 hw.busdma.zone0.total_bpages: 8250 hw.busdma.zone0.free_bpages: 8213 hw.busdma.zone0.reserved_bpages: 0 hw.busdma.zone0.active_bpages: 37 hw.busdma.zone0.total_bounced: 3275 hw.busdma.zone0.total_deferred: 0 hw.busdma.zone0.lowaddr: 0xffffffff hw.busdma.zone0.alignment: 4096 wlan0: flags=8843 metric 0 mtu 1500 ether 64:70:02:18:6d:95 inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255 inet 192.168.1.6 netmask 0xffffff00 broadcast 192.168.1.255 nd6 options=29 media: IEEE 802.11 Wireless Ethernet MCS mode 11ng status: associated ssid foobar channel 1 (2412 MHz 11g ht/20) bssid c0:c1:c0:35:19:88 regdomain 33 indoor ecm authmode WPA2/802.11i privacy ON deftxkey UNDEF AES-CCM 3:128-bit txpower 20 bmiss 7 scanvalid 60 protmode CTS ampdulimit 64k ampdudensity 8 shortgi wme burst roaming MANUAL hw.busdma.total_bpages: 8250 hw.busdma.zone0.total_bpages: 8250 hw.busdma.zone0.free_bpages: 8250 hw.busdma.zone0.reserved_bpages: 0 hw.busdma.zone0.active_bpages: 0 hw.busdma.zone0.total_bounced: 3281 hw.busdma.zone0.total_deferred: 0 hw.busdma.zone0.lowaddr: 0xffffffff hw.busdma.zone0.alignment: 4096 The alloc errors were with the patch, when I was trying to get the network up and running manually after multiuser. I can't recall that I've ever gotten ath networking working after a boot without it in rc.conf. I've brought it down, unloaded it, and brought it back but it's worked. It might just be some random thing where if it doesn't have networking at boot I can't get it later. Whatever's going on, it's odd. And if you're going wtf, does that mean maybe a hardware issue? What's linux do? Whatever it's doing, the speed it fails is dependent on the amount of ram. From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 4 01:04:53 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 22EE4497 for ; Thu, 4 Apr 2013 01:04:53 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pd0-f172.google.com (mail-pd0-f172.google.com [209.85.192.172]) by mx1.freebsd.org (Postfix) with ESMTP id EDC6BD71 for ; Thu, 4 Apr 2013 01:04:52 +0000 (UTC) Received: by mail-pd0-f172.google.com with SMTP id 5so1136712pdd.31 for ; Wed, 03 Apr 2013 18:04:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=xNkZbG/QtYz2A7IE/qSJbHCoyIDuD69juQTTEP5TT8A=; b=yhAzgy/1Ia3CrgULE5Tvd169osaulhfKdVQrkdvcsqSKJ5NqIPwHD4bD8XZWW+uD23 iYZjjkh9Eu7qwApL6/uGzsXSNEFtyejZR8z3azsVIi6oR8R6qFlO8DZB0ZTubAPlxN9U QBFooOrOdug0TC6SChdY44jWB8Dw8cF48zrKf4hNxYlGYszOqLtsK20isqBK8TkL80LR rp+MZJYIUDPN65U7dmbjrpAQE57hJ4S4cTfp/NMzT3qHVWytxRP8CDVJPgk0TI/GLCjA D0i1U8COt9oeBKw0L148dnO/GZB4rREGjXqtDImvVF/D8Uu3Lu1mCkQ1GaE7mrlmo4oX RK9Q== MIME-Version: 1.0 X-Received: by 10.68.233.74 with SMTP id tu10mr5898460pbc.57.1365037486276; Wed, 03 Apr 2013 18:04:46 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.70.61.234 with HTTP; Wed, 3 Apr 2013 18:04:46 -0700 (PDT) In-Reply-To: <515CD0A3.2020204@gmail.com> References: <515892C4.1060002@gmail.com> <515B4E16.3050901@gmail.com> <515B76A6.7080804@gmail.com> <515B78C2.20609@gmail.com> <515B8233.9000603@gmail.com> <515B8914.8030303@gmail.com> <515CAA36.70002@gmail.com> <515CC7C3.3070608@gmail.com> <515CD0A3.2020204@gmail.com> Date: Wed, 3 Apr 2013 18:04:46 -0700 X-Google-Sender-Auth: MdhGGxroCcfoZ2BJ_BXwfC0raCU Message-ID: Subject: Re: ath not working after a motherboard and ram upgrade From: Adrian Chadd To: Joshua Isom 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: Thu, 04 Apr 2013 01:04:53 -0000 .. well, I can reproduce this particular nightmare on my i386 box. I'm running a kernel where I've reduced the bus size down quite signifcantly for ath(4). Adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 4 01:27:26 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id D0C556D8; Thu, 4 Apr 2013 01:27:26 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) by mx1.freebsd.org (Postfix) with ESMTP id 5BF16E1C; Thu, 4 Apr 2013 01:27:26 +0000 (UTC) Received: by mail-ob0-f174.google.com with SMTP id 16so2064356obc.33 for ; Wed, 03 Apr 2013 18:27:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=S4ypOuu8lCTEj89XPU19B3Pi2ZF0KAz7eA+OoH2c/3M=; b=K1/Wf6mXpd4ODU0BfR8KleaPHZ+2K4XtUDu58G8v+uuQ9xjO2eW0PEm9MeGex8bCpp 8hkTN2V7zKbyx0SGra8THbo0wnZ6hSUBV2H/8VbXKoMdfh0BB+V7p/KZf5Uk2K1FTUX+ E+Mh/EBQ3Q1/CQku5fF4YOQQyKO6TKToGVmPJWwyFFwF6vjVieZS0xRlCfz9TAAD+CG4 AdwuJ28IRFXu5I3etwPfSljquxWaDaYJdHvQmm9cGNjANFMU4F38wcsWEB66vKWsmO5i 5ADT1kfZrEMvozAm+F/z2m2jjV8ti0WOOZ45MZVWvvXQeSq70sctAdiseSjmDd8yyu1b wp/Q== X-Received: by 10.182.66.11 with SMTP id b11mr2630995obt.62.1365038845282; Wed, 03 Apr 2013 18:27:25 -0700 (PDT) Received: from [192.168.1.34] (c-98-212-197-211.hsd1.il.comcast.net. [98.212.197.211]) by mx.google.com with ESMTPS id t9sm4303414obk.13.2013.04.03.18.27.23 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 03 Apr 2013 18:27:24 -0700 (PDT) Message-ID: <515CD6FB.3080502@gmail.com> Date: Wed, 03 Apr 2013 20:27:23 -0500 From: Joshua Isom User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: ath not working after a motherboard and ram upgrade References: <515892C4.1060002@gmail.com> <515B4E16.3050901@gmail.com> <515B76A6.7080804@gmail.com> <515B78C2.20609@gmail.com> <515B8233.9000603@gmail.com> <515B8914.8030303@gmail.com> <515CAA36.70002@gmail.com> <515CC7C3.3070608@gmail.com> <515CD0A3.2020204@gmail.com> In-Reply-To: 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.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: Thu, 04 Apr 2013 01:27:26 -0000 I'm trying again at 11.5GB, and it's working fine so far. At 12GB it fails, but has an early period of tcp usability for ssh's needs. It used to failed at 6GB after I first started messing with hw.physmem. On 4/3/2013 8:04 PM, Adrian Chadd wrote: > .. well, I can reproduce this particular nightmare on my i386 box. I'm > running a kernel where I've reduced the bus size down quite > signifcantly for ath(4). > > > > Adrian > From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 4 01:31:50 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E467B739 for ; Thu, 4 Apr 2013 01:31:50 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pd0-f180.google.com (mail-pd0-f180.google.com [209.85.192.180]) by mx1.freebsd.org (Postfix) with ESMTP id BBD20E43 for ; Thu, 4 Apr 2013 01:31:50 +0000 (UTC) Received: by mail-pd0-f180.google.com with SMTP id q11so1151469pdj.39 for ; Wed, 03 Apr 2013 18:31:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Nhf4ozfHTDE1YL82kIvMBExtzOudYFWblhh1GwdRCVk=; b=eNJdSbMYKjX55Aib4wkRn1Mk4E/PKYJy9fDCx/VTCUMWbcaJjhRHVGtIyk/st20vj5 jKOYceQscDjx8deHLDfSejTBYLnSezh1WLU+N6Nreaa/oUcdLqvUQ2uF2aIRyrfZELlE tUTQyRraMbSPve3AFzWsai1It5279Ff5eKIh5hJIW7jPpSt/HKhiZJEiOarUB5nhIiMV HZ7qwCW9TGKR7bUTY6fkRwDWg6RdjJkljW98D69R+jI2buFh1rkcroyR66JJdGgOhhST 2eWrNtfj75yLnbwA2+U9NREEFiEClgEGyfSD6GtEaFVWNUeTBqgK/U/FMuFgVsGHBgPj N91Q== MIME-Version: 1.0 X-Received: by 10.66.25.13 with SMTP id y13mr6449995paf.208.1365039110294; Wed, 03 Apr 2013 18:31:50 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.70.61.234 with HTTP; Wed, 3 Apr 2013 18:31:50 -0700 (PDT) In-Reply-To: <515CD6FB.3080502@gmail.com> References: <515892C4.1060002@gmail.com> <515B4E16.3050901@gmail.com> <515B76A6.7080804@gmail.com> <515B78C2.20609@gmail.com> <515B8233.9000603@gmail.com> <515B8914.8030303@gmail.com> <515CAA36.70002@gmail.com> <515CC7C3.3070608@gmail.com> <515CD0A3.2020204@gmail.com> <515CD6FB.3080502@gmail.com> Date: Wed, 3 Apr 2013 18:31:50 -0700 X-Google-Sender-Auth: ebNKq3KnY9aN4NP7wLFMrguCwSA Message-ID: Subject: Re: ath not working after a motherboard and ram upgrade From: Adrian Chadd To: Joshua Isom 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: Thu, 04 Apr 2013 01:31:51 -0000 I know what the problem is on the RX side. I'm tinkering with it now. DAmn you bounce buffers, damn you! Adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 4 01:34:47 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 9452E761 for ; Thu, 4 Apr 2013 01:34:47 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pa0-f45.google.com (mail-pa0-f45.google.com [209.85.220.45]) by mx1.freebsd.org (Postfix) with ESMTP id 69CCAE4F for ; Thu, 4 Apr 2013 01:34:47 +0000 (UTC) Received: by mail-pa0-f45.google.com with SMTP id kl13so1201121pab.32 for ; Wed, 03 Apr 2013 18:34:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=e9eIip2MVtpOczbwF7g9EA7/jS1Gd453Avk4zUDRzHc=; b=VfkI/01s4kttHtyoo7vQRxse2xxgMISLhq459EFThWpXDMdGv/MFSAfEjW7IKUTwha LmWS7XWS9sjCgA8oUDYXq2u4kMjOq+ZyHlksDHASMXGZEiOoRcnODgTXD5MFLSA/g8qY qYLPwX7VARSiIEdGAGYLTM6avyBUG+kfLyGPaYNP1aS/Xi18iy0jJUUU4afDKCYSrd9J C/VKX90ueSeMV9Ui7hDxjOohn8J04AhvTWgq3MRciw0WdDf0mAx05GlIz9oF3cuvKLa5 FsjFU6GFY+REGPDvNlUSO1e/qVS9M3scMgzcBBmHnAxYIj4MPIiW7G1WShtN7OR3r3Iu 0unQ== MIME-Version: 1.0 X-Received: by 10.66.102.65 with SMTP id fm1mr6496589pab.164.1365039281111; Wed, 03 Apr 2013 18:34:41 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.70.61.234 with HTTP; Wed, 3 Apr 2013 18:34:40 -0700 (PDT) In-Reply-To: References: <515892C4.1060002@gmail.com> <515B4E16.3050901@gmail.com> <515B76A6.7080804@gmail.com> <515B78C2.20609@gmail.com> <515B8233.9000603@gmail.com> <515B8914.8030303@gmail.com> <515CAA36.70002@gmail.com> <515CC7C3.3070608@gmail.com> <515CD0A3.2020204@gmail.com> <515CD6FB.3080502@gmail.com> Date: Wed, 3 Apr 2013 18:34:40 -0700 X-Google-Sender-Auth: JU5FmAq_y5kdWi8MBzjiRG8yhAk Message-ID: Subject: Re: ath not working after a motherboard and ram upgrade From: Adrian Chadd To: Joshua Isom 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: Thu, 04 Apr 2013 01:34:47 -0000 Ok, grab this: http://people.freebsd.org/~adrian/ath/20130403-ath-rx-unmap-first-2.diff then patch this: cd /path/to/blah/sys/dev/ath/ svn revert *[ch] patch -p0 < patch I'm running this on an AR9580 with the above patch. No issues now. The problem? PREREAD doesn't do what I thought it does. Adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 4 02:02:11 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B9CF8987; Thu, 4 Apr 2013 02:02:11 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-oa0-f50.google.com (mail-oa0-f50.google.com [209.85.219.50]) by mx1.freebsd.org (Postfix) with ESMTP id 72C00F20; Thu, 4 Apr 2013 02:02:11 +0000 (UTC) Received: by mail-oa0-f50.google.com with SMTP id n1so2247071oag.37 for ; Wed, 03 Apr 2013 19:02:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=SPXBJLXIefOBH93sVrcMpkXhYwsrhtM/R5tPb0x9ADs=; b=DPY/mOcGY1V6atm3H+aN6uwjXC1RX7ea6LTx9d4HNGklbWgmRJouDgmnw8KAtdGR1v U0ploz/YU8fMTl0ZOJsevhEo0phWALDYh1FK87eAYdAIcSOIp09S9TwqZ6DkfF3rrsOC NNdwCoNgmZ5+pjePJwc6Vus9huB9ITdsPY0Z0kiv3irA06AYd/D/jB1PDuTMGvPioK43 uP6hvWLqVQOt7uh3AbZz8wZovRUYjOGgQiB91ZSe1LnqG17ak2VI1nTv++Au8/k77rct FW8hyjwrI3wZ76PboaYGw5+bxQiCLdtimTDOSoJ8b9fxB8xj9Dq8gaNu3Q38awqgznHq 7MRw== X-Received: by 10.182.118.105 with SMTP id kl9mr2736432obb.52.1365040925135; Wed, 03 Apr 2013 19:02:05 -0700 (PDT) Received: from [192.168.1.34] (c-98-212-197-211.hsd1.il.comcast.net. [98.212.197.211]) by mx.google.com with ESMTPS id zc8sm4405633obc.8.2013.04.03.19.02.03 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 03 Apr 2013 19:02:04 -0700 (PDT) Message-ID: <515CDF1B.10905@gmail.com> Date: Wed, 03 Apr 2013 21:02:03 -0500 From: Joshua Isom User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: ath not working after a motherboard and ram upgrade References: <515892C4.1060002@gmail.com> <515B76A6.7080804@gmail.com> <515B78C2.20609@gmail.com> <515B8233.9000603@gmail.com> <515B8914.8030303@gmail.com> <515CAA36.70002@gmail.com> <515CC7C3.3070608@gmail.com> <515CD0A3.2020204@gmail.com> <515CD6FB.3080502@gmail.com> In-Reply-To: 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.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: Thu, 04 Apr 2013 02:02:11 -0000 It seems to be working for me now at full memory. I did a search on the BUS_DMASYNC_PREREAD, one nic for freebsd had a patch full of replacing PREREAD with PREWRITE, so maybe a doc needs updated. On 4/3/2013 8:34 PM, Adrian Chadd wrote: > Ok, grab this: > > http://people.freebsd.org/~adrian/ath/20130403-ath-rx-unmap-first-2.diff > > then patch this: > > cd /path/to/blah/sys/dev/ath/ > svn revert *[ch] > patch -p0 < patch > > I'm running this on an AR9580 with the above patch. No issues now. > > The problem? PREREAD doesn't do what I thought it does. > > > Adrian > From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 4 02:11:06 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 87205C1E for ; Thu, 4 Apr 2013 02:11:06 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f45.google.com (mail-pb0-f45.google.com [209.85.160.45]) by mx1.freebsd.org (Postfix) with ESMTP id 5E991F78 for ; Thu, 4 Apr 2013 02:11:06 +0000 (UTC) Received: by mail-pb0-f45.google.com with SMTP id ro12so888779pbb.4 for ; Wed, 03 Apr 2013 19:11:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=f7TbBcJnf2HRMaFuig+A5CQaFUMPN/DZyiVbBYVgIz0=; b=IytOqg9exUKjtHireOSPpaRMa28jpP6hphlPwMHwNisCtnA72vv1YhrM1wMIc8Bmp9 SLfxRCsWsdtK8SC9zSEn84DSdRbw7TOtuNa7NCQPh/htwDYmqQx1UMEltCi9Hxsg4+Es tEN266vWLMoMIS7W9Ot0lUJt6ZKxiGrz/C2Zak46f/2cteU1kI7DhZxeHIho1dUZNaBa dSxygXS2g7toY/VgBdCeeKo20gbOvE+6HfAasjd+EL9ZvN1KPuIxL5yLA393jq61WrjZ +/i+FtTYCFaA0jbkcOCrmjNwqwzSxU2NXcfihyi4a+VHNkeTyhPOQK0SBCK9K+MY0Hr2 EN9g== MIME-Version: 1.0 X-Received: by 10.66.150.198 with SMTP id uk6mr6873355pab.57.1365041465753; Wed, 03 Apr 2013 19:11:05 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.70.61.234 with HTTP; Wed, 3 Apr 2013 19:11:05 -0700 (PDT) In-Reply-To: <515CDF1B.10905@gmail.com> References: <515892C4.1060002@gmail.com> <515B76A6.7080804@gmail.com> <515B78C2.20609@gmail.com> <515B8233.9000603@gmail.com> <515B8914.8030303@gmail.com> <515CAA36.70002@gmail.com> <515CC7C3.3070608@gmail.com> <515CD0A3.2020204@gmail.com> <515CD6FB.3080502@gmail.com> <515CDF1B.10905@gmail.com> Date: Wed, 3 Apr 2013 19:11:05 -0700 X-Google-Sender-Auth: xvYH5ZFRHCoRc_-G-DQVe-A9FSU Message-ID: Subject: Re: ath not working after a motherboard and ram upgrade From: Adrian Chadd To: Joshua Isom 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: Thu, 04 Apr 2013 02:11:06 -0000 On 3 April 2013 19:02, Joshua Isom wrote: > It seems to be working for me now at full memory. I did a search on the > BUS_DMASYNC_PREREAD, one nic for freebsd had a patch full of replacing > PREREAD with PREWRITE, so maybe a doc needs updated. Where'd you find that? Adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 4 08:30:01 2013 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B0AC768F for ; Thu, 4 Apr 2013 08:30:01 +0000 (UTC) (envelope-from gnats@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 A2246EA6 for ; Thu, 4 Apr 2013 08:30:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r348U1JM095171 for ; Thu, 4 Apr 2013 08:30:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r348U1E3095170; Thu, 4 Apr 2013 08:30:01 GMT (envelope-from gnats) Date: Thu, 4 Apr 2013 08:30:01 GMT Message-Id: <201304040830.r348U1E3095170@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org Cc: From: dfilter@FreeBSD.ORG (dfilter service) Subject: Re: kern/177530: commit references a PR X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: dfilter service List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Apr 2013 08:30:01 -0000 The following reply was made to PR kern/177530; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/177530: commit references a PR Date: Thu, 4 Apr 2013 08:22:10 +0000 (UTC) Author: adrian Date: Thu Apr 4 08:21:56 2013 New Revision: 249085 URL: http://svnweb.freebsd.org/changeset/base/249085 Log: Fix the busdma logic to work with EDMA chipsets when using bounce buffers (ie, >4GB on amd64.) The underlying problem was that PREREAD doesn't sync the mbuf with the DMA memory (ie, bounce buffer), so the bounce buffer may have had stale information. Thus it was always considering the buffer completed and things just went off the rails. This change does the following: * Make ath_rx_pkt() always consume the mbuf somehow; it no longer passes error mbufs (eg CRC errors, crypt errors, etc) back up to the RX path to recycle. This means that a new mbuf is always allocated each time, but it's cleaner. * Push the RX buffer map/unmap to occur in the RX path, not ath_rx_pkt(). Thus, ath_rx_pkt() now assumes (a) it has to consume the mbuf somehow, and (b) that it's already been unmapped and synced. * For the legacy path, the descriptor isn't mapped, it comes out of coherent, DMA memory anyway. So leave it there. * For the EDMA path, the RX descriptor has to be cleared before its passed to the hardware, so that when we check with a POSTREAD sync, we actually get either a blank (not finished) or a filled out descriptor (finished.) Otherwise we get stale data in the DMA memory. * .. so, for EDMA RX path, we need PREREAD|PREWRITE to sync the data -> DMA memory, then POSTREAD|POSTWRITE to finish syncing the DMA memory -> data. * Whilst we're here, make sure that in EDMA buffer setup (ie, bzero'ing the descriptor part) is done before the mbuf is map/synched. NOTE: there's been a lot of commits besides this one with regards to tidying up the busdma handling in ath(4). Please check the recent commit history. Discussed with and thanks to: scottl Tested: * AR5416 (non-EDMA) on i386, with the DMA tag for the driver set to 2^^30, not 2^^32, STA * AR9580 (EDMA) on i386, as above, STA * User - tested AR9380 on amd64 with 32GB RAM. PR: kern/177530 Modified: head/sys/dev/ath/if_ath_rx.c head/sys/dev/ath/if_ath_rx.h head/sys/dev/ath/if_ath_rx_edma.c Modified: head/sys/dev/ath/if_ath_rx.c ============================================================================== --- head/sys/dev/ath/if_ath_rx.c Thu Apr 4 07:57:32 2013 (r249084) +++ head/sys/dev/ath/if_ath_rx.c Thu Apr 4 08:21:56 2013 (r249085) @@ -502,12 +502,21 @@ ath_handle_micerror(struct ieee80211com } } +/* + * Process a single packet. + * + * The mbuf must already be synced, unmapped and removed from bf->bf_m + * by this stage. + * + * The mbuf must be consumed by this routine - either passed up the + * net80211 stack, put on the holding queue, or freed. + */ int ath_rx_pkt(struct ath_softc *sc, struct ath_rx_status *rs, HAL_STATUS status, - uint64_t tsf, int nf, HAL_RX_QUEUE qtype, struct ath_buf *bf) + uint64_t tsf, int nf, HAL_RX_QUEUE qtype, struct ath_buf *bf, + struct mbuf *m) { struct ath_hal *ah = sc->sc_ah; - struct mbuf *m = bf->bf_m; uint64_t rstamp; int len, type; struct ifnet *ifp = sc->sc_ifp; @@ -548,10 +557,6 @@ ath_rx_pkt(struct ath_softc *sc, struct /* Process DFS radar events */ if ((rs->rs_phyerr == HAL_PHYERR_RADAR) || (rs->rs_phyerr == HAL_PHYERR_FALSE_RADAR_EXT)) { - /* Since we're touching the frame data, sync it */ - bus_dmamap_sync(sc->sc_dmat, - bf->bf_dmamap, - BUS_DMASYNC_POSTREAD); /* Now pass it to the radar processing code */ ath_dfs_process_phy_err(sc, m, rstamp, rs); } @@ -593,9 +598,6 @@ ath_rx_pkt(struct ath_softc *sc, struct /* XXX frag's and qos frames */ len = rs->rs_datalen; if (len >= sizeof (struct ieee80211_frame)) { - bus_dmamap_sync(sc->sc_dmat, - bf->bf_dmamap, - BUS_DMASYNC_POSTREAD); ath_handle_micerror(ic, mtod(m, struct ieee80211_frame *), sc->sc_splitmic ? @@ -619,35 +621,20 @@ rx_error: */ if (ieee80211_radiotap_active(ic) && (rs->rs_status & sc->sc_monpass)) { - bus_dmamap_sync(sc->sc_dmat, bf->bf_dmamap, - BUS_DMASYNC_POSTREAD); - bus_dmamap_unload(sc->sc_dmat, bf->bf_dmamap); /* NB: bpf needs the mbuf length setup */ len = rs->rs_datalen; m->m_pkthdr.len = m->m_len = len; - bf->bf_m = NULL; ath_rx_tap(ifp, m, rs, rstamp, nf); #ifdef ATH_ENABLE_RADIOTAP_VENDOR_EXT ath_rx_tap_vendor(ifp, m, rs, rstamp, nf); #endif /* ATH_ENABLE_RADIOTAP_VENDOR_EXT */ ieee80211_radiotap_rx_all(ic, m); - m_freem(m); } /* XXX pass MIC errors up for s/w reclaculation */ + m_freem(m); m = NULL; goto rx_next; } rx_accept: - /* - * Sync and unmap the frame. At this point we're - * committed to passing the mbuf somewhere so clear - * bf_m; this means a new mbuf must be allocated - * when the rx descriptor is setup again to receive - * another frame. - */ - bus_dmamap_sync(sc->sc_dmat, bf->bf_dmamap, BUS_DMASYNC_POSTREAD); - bus_dmamap_unload(sc->sc_dmat, bf->bf_dmamap); - bf->bf_m = NULL; - len = rs->rs_datalen; m->m_len = len; @@ -665,6 +652,7 @@ rx_accept: m->m_pkthdr.rcvif = ifp; m->m_pkthdr.len = len; re->m_rxpending = m; + m = NULL; goto rx_next; } else if (re->m_rxpending != NULL) { /* @@ -744,7 +732,7 @@ rx_accept: /* NB: in particular this captures ack's */ ieee80211_radiotap_rx_all(ic, m); } - m_freem(m); + m_freem(m); m = NULL; goto rx_next; } @@ -788,6 +776,7 @@ rx_accept: */ type = ieee80211_input(ni, m, rs->rs_rssi, nf); ieee80211_free_node(ni); + m = NULL; /* * Arrange to update the last rx timestamp only for * frames from our ap when operating in station mode. @@ -799,7 +788,14 @@ rx_accept: is_good = 1; } else { type = ieee80211_input_all(ic, m, rs->rs_rssi, nf); + m = NULL; } + + /* + * At this point we have passed the frame up the stack; thus + * the mbuf is no longer ours. + */ + /* * Track rx rssi and do any rx antenna management. */ @@ -837,6 +833,16 @@ rx_accept: ath_led_event(sc, 0); } rx_next: + /* + * Debugging - complain if we didn't NULL the mbuf pointer + * here. + */ + if (m != NULL) { + device_printf(sc->sc_dev, + "%s: mbuf %p should've been freed!\n", + __func__, + m); + } return (is_good); } @@ -952,7 +958,10 @@ ath_rx_proc(struct ath_softc *sc, int re /* * Process a single frame. */ - if (ath_rx_pkt(sc, rs, status, tsf, nf, HAL_RX_QUEUE_HP, bf)) + bus_dmamap_sync(sc->sc_dmat, bf->bf_dmamap, BUS_DMASYNC_POSTREAD); + bus_dmamap_unload(sc->sc_dmat, bf->bf_dmamap); + bf->bf_m = NULL; + if (ath_rx_pkt(sc, rs, status, tsf, nf, HAL_RX_QUEUE_HP, bf, m)) ngood++; rx_proc_next: TAILQ_INSERT_TAIL(&sc->sc_rxbuf, bf, bf_list); Modified: head/sys/dev/ath/if_ath_rx.h ============================================================================== --- head/sys/dev/ath/if_ath_rx.h Thu Apr 4 07:57:32 2013 (r249084) +++ head/sys/dev/ath/if_ath_rx.h Thu Apr 4 08:21:56 2013 (r249085) @@ -58,7 +58,7 @@ extern int ath_startrecv(struct ath_soft extern int ath_rx_pkt(struct ath_softc *sc, struct ath_rx_status *rs, HAL_STATUS status, uint64_t tsf, int nf, HAL_RX_QUEUE qtype, - struct ath_buf *bf); + struct ath_buf *bf, struct mbuf *m); extern void ath_recv_setup_legacy(struct ath_softc *sc); Modified: head/sys/dev/ath/if_ath_rx_edma.c ============================================================================== --- head/sys/dev/ath/if_ath_rx_edma.c Thu Apr 4 07:57:32 2013 (r249084) +++ head/sys/dev/ath/if_ath_rx_edma.c Thu Apr 4 08:21:56 2013 (r249085) @@ -362,11 +362,10 @@ ath_edma_recv_proc_queue(struct ath_soft /* * Sync descriptor memory - this also syncs the buffer for us. - * * EDMA descriptors are in cached memory. */ bus_dmamap_sync(sc->sc_dmat, bf->bf_dmamap, - BUS_DMASYNC_POSTREAD); + BUS_DMASYNC_POSTREAD | BUS_DMASYNC_POSTWRITE); rs = &bf->bf_status.ds_rxstat; bf->bf_rxstatus = ath_hal_rxprocdesc(ah, ds, bf->bf_daddr, NULL, rs); @@ -384,16 +383,17 @@ ath_edma_recv_proc_queue(struct ath_soft /* * Completed descriptor. - * - * In the future we'll call ath_rx_pkt(), but it first - * has to be taught about EDMA RX queues (so it can - * access sc_rxpending correctly.) */ DPRINTF(sc, ATH_DEBUG_EDMA_RX, "%s: Q%d: completed!\n", __func__, qtype); npkts++; /* + * We've been synced already, so unmap. + */ + bus_dmamap_unload(sc->sc_dmat, bf->bf_dmamap); + + /* * Remove the FIFO entry and place it on the completion * queue. */ @@ -468,6 +468,7 @@ ath_edma_recv_proc_deferred_queue(struct struct ath_rx_status *rs; int16_t nf; ath_bufhead rxlist; + struct mbuf *m; TAILQ_INIT(&rxlist); @@ -492,12 +493,11 @@ ath_edma_recv_proc_deferred_queue(struct m_adj(bf->bf_m, sc->sc_rx_statuslen); /* Handle the frame */ - /* - * Note: this may or may not free bf->bf_m and sync/unmap - * the frame. - */ + rs = &bf->bf_status.ds_rxstat; - if (ath_rx_pkt(sc, rs, bf->bf_rxstatus, tsf, nf, qtype, bf)) + m = bf->bf_m; + bf->bf_m = NULL; + if (ath_rx_pkt(sc, rs, bf->bf_rxstatus, tsf, nf, qtype, bf, m)) ngood++; } @@ -605,10 +605,27 @@ ath_edma_rxbuf_init(struct ath_softc *sc m->m_pkthdr.len = m->m_len = m->m_ext.ext_size; /* + * Populate ath_buf fields. + */ + bf->bf_desc = mtod(m, struct ath_desc *); + bf->bf_lastds = bf->bf_desc; /* XXX only really for TX? */ + bf->bf_m = m; + + /* + * Zero the descriptor and ensure it makes it out to the + * bounce buffer if one is required. + * + * XXX PREWRITE will copy the whole buffer; we only needed it + * to sync the first 32 DWORDS. Oh well. + */ + memset(bf->bf_desc, '\0', sc->sc_rx_statuslen); + + /* * Create DMA mapping. */ error = bus_dmamap_load_mbuf_sg(sc->sc_dmat, bf->bf_dmamap, m, bf->bf_segs, &bf->bf_nseg, BUS_DMA_NOWAIT); + if (error != 0) { device_printf(sc->sc_dev, "%s: failed; error=%d\n", __func__, @@ -618,30 +635,27 @@ ath_edma_rxbuf_init(struct ath_softc *sc } /* - * Populate ath_buf fields. + * Set daddr to the physical mapping page. */ - - bf->bf_desc = mtod(m, struct ath_desc *); bf->bf_daddr = bf->bf_segs[0].ds_addr; - bf->bf_lastds = bf->bf_desc; /* XXX only really for TX? */ - bf->bf_m = m; - - /* Zero the descriptor */ - memset(bf->bf_desc, '\0', sc->sc_rx_statuslen); -#if 0 /* - * Adjust mbuf header and length/size to compensate for the - * descriptor size. + * Prepare for the upcoming read. + * + * We need to both sync some data into the buffer (the zero'ed + * descriptor payload) and also prepare for the read that's going + * to occur. */ - m_adj(m, sc->sc_rx_statuslen); -#endif + bus_dmamap_sync(sc->sc_dmat, bf->bf_dmamap, + BUS_DMASYNC_PREREAD | BUS_DMASYNC_PREWRITE); /* Finish! */ - return (0); } +/* + * Allocate a RX buffer. + */ static struct ath_buf * ath_edma_rxbuf_alloc(struct ath_softc *sc) { @@ -653,8 +667,11 @@ ath_edma_rxbuf_alloc(struct ath_softc *s /* Allocate buffer */ bf = TAILQ_FIRST(&sc->sc_rxbuf); /* XXX shouldn't happen upon startup? */ - if (bf == NULL) + if (bf == NULL) { + device_printf(sc->sc_dev, "%s: nothing on rxbuf?!\n", + __func__); return (NULL); + } /* Remove it from the free list */ TAILQ_REMOVE(&sc->sc_rxbuf, bf, bf_list); @@ -743,18 +760,13 @@ ath_edma_rxfifo_alloc(struct ath_softc * re->m_fifo[re->m_fifo_tail] = bf; - /* - * Flush the descriptor contents before it's handed to the - * hardware. - */ - bus_dmamap_sync(sc->sc_dmat, bf->bf_dmamap, - BUS_DMASYNC_PREREAD); - /* Write to the RX FIFO */ - DPRINTF(sc, ATH_DEBUG_EDMA_RX, "%s: Q%d: putrxbuf=%p\n", + DPRINTF(sc, ATH_DEBUG_EDMA_RX, + "%s: Q%d: putrxbuf=%p (0x%jx)\n", __func__, qtype, - bf->bf_desc); + bf->bf_desc, + (uintmax_t) bf->bf_daddr); ath_hal_putrxbuf(sc->sc_ah, bf->bf_daddr, qtype); re->m_fifo_depth++; _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 4 08:52:15 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 3F948BC2 for ; Thu, 4 Apr 2013 08:52:15 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c:c05::22d]) by mx1.freebsd.org (Postfix) with ESMTP id C6E6EF60 for ; Thu, 4 Apr 2013 08:52:14 +0000 (UTC) Received: by mail-wi0-f173.google.com with SMTP id ez12so4453007wid.0 for ; Thu, 04 Apr 2013 01:52:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=4qLMmG+odEyILw+1pSvO1MeE1/hxzbZuKU9ikPkVVLQ=; b=U/D+FJN3uRzCRdtXlljaWx+VnNpQEEqaiH8eKc2YYrHd+xS4WmmIhm6oyWkLpQ57sa 7iUzLE8QNi4fy6Os/g2MzAmTx6YQKCUm7pOJ87dokkpB1I9TnEqijK4jkKkSX2f2pBEo c/rcZtkLhiNxYx7/bTytylXxWQmY4LInS0vHB83jZkJ8vwWvq+w1uKGPfy2Dgc86nhJ8 LJ3akiu9S2XSjgm9E3rTb/Ti3QiuGi552or2GwtqndOMu17aONlkUjaiwNHYtG7vBqRl gM72GHWNn29w7Av67Z9p2Mrx5LzaduTWyFofB+O5Xg6TxkJbiWFMmnCzN25EGjkZDoql LzhQ== MIME-Version: 1.0 X-Received: by 10.180.94.135 with SMTP id dc7mr27852462wib.11.1365065534006; Thu, 04 Apr 2013 01:52:14 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.212.73 with HTTP; Thu, 4 Apr 2013 01:52:13 -0700 (PDT) In-Reply-To: References: <515892C4.1060002@gmail.com> <515B76A6.7080804@gmail.com> <515B78C2.20609@gmail.com> <515B8233.9000603@gmail.com> <515B8914.8030303@gmail.com> <515CAA36.70002@gmail.com> <515CC7C3.3070608@gmail.com> <515CD0A3.2020204@gmail.com> <515CD6FB.3080502@gmail.com> <515CDF1B.10905@gmail.com> Date: Thu, 4 Apr 2013 01:52:13 -0700 X-Google-Sender-Auth: BMjD1Im193P2ZGwQ-7j59QD-Mdw Message-ID: Subject: Re: ath not working after a motherboard and ram upgrade From: Adrian Chadd To: Joshua Isom 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: Thu, 04 Apr 2013 08:52:15 -0000 Pleas update to -HEAD w/ no patches and test. I think I've licked it! Thanks, Adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 4 09:28:40 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 86638537; Thu, 4 Apr 2013 09:28:40 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-oa0-f45.google.com (mail-oa0-f45.google.com [209.85.219.45]) by mx1.freebsd.org (Postfix) with ESMTP id 3FC9B13D; Thu, 4 Apr 2013 09:28:40 +0000 (UTC) Received: by mail-oa0-f45.google.com with SMTP id o6so2545163oag.32 for ; Thu, 04 Apr 2013 02:28:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=TFrCGFJeokeDq71QxfGGw8xIpVhrBdse6hWkXuj4/tY=; b=R5vOrmLv8mA/l0Jiua7u736LP2C3JxYxuk1cjmK6eMOWfMYvP6iWm0d/hQEhZUXOAo uFpHMy+lI+b+TjB9emJ9UY/JNkUbUeTkBhAcZywR9DGL/M7dkDERlgoLERprZounROpm puiTzQdQjAYTnfDXbl+lqa12sCYwOy1/lrCKe0vNDi9a93CokyXvwKCPHbEkVTmkSDqt e+MKeZCOhIvUUtojjgZOzviVcc3sPeGV+uhylVAilzyQNHgLga06RTrXhelUgb3gPntM VH5IWNzGYwpIwQI4snIDtEYhhmPob9YMjc52yPybx+ruyJjgcq0gIqcqPyZZFafn8CJv qv8Q== X-Received: by 10.60.142.230 with SMTP id rz6mr825327oeb.22.1365067719565; Thu, 04 Apr 2013 02:28:39 -0700 (PDT) Received: from [192.168.1.34] (c-98-212-197-211.hsd1.il.comcast.net. [98.212.197.211]) by mx.google.com with ESMTPS id w10sm5661177oed.2.2013.04.04.02.28.37 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 04 Apr 2013 02:28:38 -0700 (PDT) Message-ID: <515D47C3.8080405@gmail.com> Date: Thu, 04 Apr 2013 04:28:35 -0500 From: Joshua Isom User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: ath not working after a motherboard and ram upgrade References: <515892C4.1060002@gmail.com> <515B8233.9000603@gmail.com> <515B8914.8030303@gmail.com> <515CAA36.70002@gmail.com> <515CC7C3.3070608@gmail.com> <515CD0A3.2020204@gmail.com> <515CD6FB.3080502@gmail.com> <515CDF1B.10905@gmail.com> In-Reply-To: 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.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: Thu, 04 Apr 2013 09:28:40 -0000 So far so good. I found this patch, http://people.freebsd.org/~delphij/for_review/bce-dma.diff that changes a lot. It's a few years old. I can't seem to find where it's actually used instead of passed except for arm and mips, but I'm probably missing it. On 4/4/2013 3:52 AM, Adrian Chadd wrote: > Pleas update to -HEAD w/ no patches and test. > > I think I've licked it! > > Thanks, > > > > Adrian > From owner-freebsd-wireless@FreeBSD.ORG Fri Apr 5 04:44:49 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 926A6F54 for ; Fri, 5 Apr 2013 04:44:49 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x236.google.com (mail-we0-x236.google.com [IPv6:2a00:1450:400c:c03::236]) by mx1.freebsd.org (Postfix) with ESMTP id 31B52F92 for ; Fri, 5 Apr 2013 04:44:49 +0000 (UTC) Received: by mail-we0-f182.google.com with SMTP id k14so2601944wer.27 for ; Thu, 04 Apr 2013 21:44:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:date:x-google-sender-auth:message-id :subject:from:to:content-type; bh=FPtuyleIWRFu5lsmtjB85HFtB9Y5gP93mmXONYK3ECY=; b=mez6YPwvGQ0AVOQ14eA+0cccM41lpYxWp98l/j5lJlT7EjWQVEYNR9OiiSMxc2IJrJ fhRNBG9O/CL4Da8ILl+LG3cf0/14KLB8oevmqYOy6NWHPyGWC0gDgu14KygnJx0TjdHY omUSX42HxqX/NmMeDCHszy9MrX+rLnOhAaBWBZCUOjcOU/y19S2wPooksyjrFc0JQlh/ QX0iYaV6Gf7hwVak7V+5E/N5WRfBw7N9v7xVFIXYiqtt+FYHPyc9KuS9TcFOczilPZ/W i+HFBPkIWc/OXBLXGQBjFumPE6r2vH8iVnwHjMKUZAsjqqBTZdQ1vQmtPpmFBxeakkN6 juzw== MIME-Version: 1.0 X-Received: by 10.194.119.33 with SMTP id kr1mr13558378wjb.36.1365137088211; Thu, 04 Apr 2013 21:44:48 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.212.73 with HTTP; Thu, 4 Apr 2013 21:44:47 -0700 (PDT) Date: Thu, 4 Apr 2013 21:44:47 -0700 X-Google-Sender-Auth: IoU2cgUVUhPfOTOXMkbxU8EZiCE Message-ID: Subject: updates to ar9300_hal / driver, please test 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: Fri, 05 Apr 2013 04:44:49 -0000 Hi, I've done a bunch of changes! Driver: * lots of busdma related tidying up; * fixed the EDMA "Can't run on machines with >4GB" issue; ar9300 support: * updated to the latest internal HAL; * added ar9300 tx power configuration support, so you can configure lower tx power if you'd like. Thanks, Adrian From owner-freebsd-wireless@FreeBSD.ORG Fri Apr 5 17:39:30 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 23893EBD for ; Fri, 5 Apr 2013 17:39:30 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) by mx1.freebsd.org (Postfix) with ESMTP id B250864A for ; Fri, 5 Apr 2013 17:39:29 +0000 (UTC) Received: by mail-wi0-f169.google.com with SMTP id c10so2067349wiw.2 for ; Fri, 05 Apr 2013 10:39:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=leN90q3ndtXVo0fCLN3TM3CSuK4oE1NeXUrnW5YPoe0=; b=Oj/1Gq2eQGp3ko8v1Ce58iOcGULA6UF+MzzZ5TP9wcqZ9SeMAAedOxoQAnD12Qkjke HKkESLi31GXQ85hNsffKVdVHOzQfwWs/XIA29m0floR6TNzeBW0SFN12voqYUTfdStKS vP/9cqm87z+bdNRNwKNjuLQWWTFnX6aX7xMptSYKR5gA+OT5Br5bhOtWF5EF3Tt4Cev8 nvUAbS7Oy7pDsf0Sx9i4bDe8AiDrjjSksYdIEBm/7AkJ2vYcbaG1l1ZOwXWzK6tKX3NA SBUpOgUnj3xoQnXL7rZSXTHJJXi99ecsFUZWFptO6N0gwCtfCBwfwK7W59FOOMS9iipt 4gWg== MIME-Version: 1.0 X-Received: by 10.194.171.74 with SMTP id as10mr18281660wjc.0.1365183568937; Fri, 05 Apr 2013 10:39:28 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.212.73 with HTTP; Fri, 5 Apr 2013 10:39:28 -0700 (PDT) In-Reply-To: References: Date: Fri, 5 Apr 2013 10:39:28 -0700 X-Google-Sender-Auth: nAjnCQnDF5Byfm7NN_9Ns463D0M Message-ID: Subject: Re: updates to ar9300_hal / driver, please test 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: Fri, 05 Apr 2013 17:39:30 -0000 On 4 April 2013 21:44, Adrian Chadd wrote: > ar9300 support: > > * updated to the latest internal HAL; > * added ar9300 tx power configuration support, so you can configure > lower tx power if you'd like. I've added in the bluetooth coexistence code, the bluetooth MCI coexistence code and removed the SoC (ie, embedded inside SoCs, rather than standalone NIC) support. When it's time to build wifi for AR933x, AR934x, AR955x, I'll re-enable it for those builds. Now, if you have an AR9485 or AR946x, please test this latest driver. I haven't _enabled_ the bluetooth coexistence code so bluetooth either will run badly, or it won't run at all (on AR9462 and later.) But it shouldn't have broken anything. Thanks, Adrian