From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 5 07:45:48 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 36F62B11; Sun, 5 Jan 2014 07:45:48 +0000 (UTC) Received: from mail-qc0-x22c.google.com (mail-qc0-x22c.google.com [IPv6:2607:f8b0:400d:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C0ACE190B; Sun, 5 Jan 2014 07:45:47 +0000 (UTC) Received: by mail-qc0-f172.google.com with SMTP id e16so16477598qcx.3 for ; Sat, 04 Jan 2014 23:45:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=k7KVFlWV2PIwj41NzdokN9kN4Zu1zyjoH1qmQHiGWTQ=; b=Iu+zFFw4Kt0sBneXTrmBMaIDuHFepL1U0nQtO+++yldXqGmet7utquk5qVXwxTGw0+ XrqqovHgn/PLszOuF3GyYQDdevLxLOdofbnXfIJVAm2zXHGWJ42nk9tBArAhR8kMLi73 Hs8BVnp7W6eekpbiPywp8Gyhbd1p9UdvVh9VwCHiHdYvr4qEyngvNKYFmK9RUCH+BLzf MUBGX+925yigAUKgMtY1hey5CZ3NORM50LbLf6f8PH9NEvuZLhcz5iCxmrb9THd5LAoQ Oy7N2PHXJKrseIX5yzVN3sAid8fW2/V63FEp9YQRHpjDjASdzx+PJxd/883DeUJ41mxo xKvQ== MIME-Version: 1.0 X-Received: by 10.224.127.131 with SMTP id g3mr135806774qas.98.1388907946558; Sat, 04 Jan 2014 23:45:46 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.52.8 with HTTP; Sat, 4 Jan 2014 23:45:46 -0800 (PST) In-Reply-To: References: <51C8AE67.7040801@unsane.co.uk> Date: Sat, 4 Jan 2014 23:45:46 -0800 X-Google-Sender-Auth: WCjuv9AitMuBMLUXRJdieZfukBY Message-ID: Subject: Re: Thinkpad T60 with Atheros working only after restart from Windows From: Adrian Chadd To: Lyubomir Yotov Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "freebsd-wireless@freebsd.org" , "freebsd-mobile@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Jan 2014 07:45:48 -0000 Have you tried -11? -a On 30 December 2013 09:25, Lyubomir Yotov wrote: > Hi Andrian, > > Merry Christmas and all the best for the New Year! > I would like to ask if there is something on the horizon with the Atheros > time outs? Is there any chance in getting it working without restart to > Windows (in my case)? Is there anything else I can try? Currently I am with > 9.2-RELEASE #0 r255898. > > All the best, > > Lyubomir > > > On 17 July 2013 23:06, Lyubomir Yotov wrote: > >> Hi, >> No problem, I fully understand you. If you manage to find something I >> will be more than grateful. Anyway thanks for your time! I think you are >> doing quite a god job! >> >> >> >> Regards, >> >> Lyubo >> >> >> >> On 16 July 2013 11:51, Adrian Chadd wrote: >> >>> Hi, >>> >>> I'm sorry, I don't have the time to try and debug this issue. If I had a >>> T60 here that demonstrated this behaviour then I could try to fix it. But I >>> unfortunately don't; all my T60 hardware has intel wifi. :( >>> >>> I can try putting an AR5418 in a T60 in a few weeks and see if it >>> exhibits this behaviour. But don't hold your breath. >>> >>> Sorry :( >>> >>> >>> >>> -adrian >>> >>> >>> On 15 July 2013 13:30, Lyubomir Yotov wrote: >>> >>>> Hi Adrian, >>>> I tried with -HEAD liveCD as proposed by Vincent and ghostbsd live cd >>>> but the situation is the same. I feel like I am missing something. On one >>>> hand I can scan the wireless networks and the wifi card seems to be >>>> working. On the other hand I cannot attach as the ath device times out >>>> (which according to the ath man pages should not occur). I also tried to >>>> encrypt the psk phrase with pwa_passphrase but with no success either. I >>>> tested with Kali linux live cd and the wireless was working fine. I also >>>> noticed that if I shutdown Windows and then start FreeBSD then the wifi >>>> also behaves the same way - ath0: device timed out. Only restart from >>>> Windows or restart from FreeBSD with working wifi can make the wifi work >>>> again. >>>> Do you have any other proposals? >>>> >>>> Regards, >>>> >>>> Lyubomir >>>> >>>> >>>> On 24 June 2013 23:39, Vincent Hoffman wrote: >>>> >>>>> As an easy test if you arent keen on making the leap just yet I'd >>>>> suggest getting a snapshot CD and just boot it as a liveCD to test. >>>>> either a snapshot >>>>> http://www.freebsd.org/snapshots/ >>>>> or one of the daily builds from >>>>> https://pub.allbsd.org/FreeBSD-snapshots/ >>>>> (for example >>>>> >>>>> https://pub.allbsd.org/FreeBSD-snapshots/amd64-amd64/10.0-HEAD-r252115-JPSNAP/iso/FreeBSD-10.0-HEAD-r252115-JPSNAP-amd64-amd64-release.iso >>>>> ) >>>>> >>>>> That said I run -CURRENT on my server at home (for the atheros driver) >>>>> and dont have any problems with it. >>>>> >>>>> Vince >>>>> >>>>> >>>>> On 24/06/2013 21:01, Lyubomir Yotov wrote: >>>>> > Hi Adrian, >>>>> > >>>>> > I will try to get -HEAD on my T60 and will report back. >>>>> > >>>>> > Regards, >>>>> > >>>>> > Lyubomir >>>>> > >>>>> > >>>>> > On 24 June 2013 20:21, Adrian Chadd wrote: >>>>> > >>>>> >> Hi, >>>>> >> >>>>> >> Would you be willing to try a -HEAD snapshot on your laptop? >>>>> >> >>>>> >> Maybe I've fixed it as part of the other driver work that I've done >>>>> as >>>>> >> part of development in -HEAD. >>>>> >> >>>>> >> But right now I really have no idea. I don't have a T60 here that >>>>> has >>>>> >> that chip in it. If all the T60 BIOSes allow AR5418 NICs then I can >>>>> >> try it out, but all of the T60's I've played with thus far have the >>>>> >> intel hardware in it. >>>>> >> >>>>> >> >>>>> >> >>>>> >> Adrian >>>>> >> >>>>> >> >>>>> >> On 21 June 2013 02:02, Lyubomir Yotov wrote: >>>>> >>> Hello Adrian, >>>>> >>> >>>>> >>> Do you have any feedback on the matter? >>>>> >>> >>>>> >>> Regards, >>>>> >>> >>>>> >>> Lyubomir >>>>> >>> >>>>> >>> >>>>> >>> On 13 June 2013 10:09, Lyubomir Yotov wrote: >>>>> >>>> Hello Adrian, >>>>> >>>> >>>>> >>>> I enabled acpi_ibm.ko but this didn't help and after "halt" the >>>>> wifi is >>>>> >>>> not working again. >>>>> >>>> >>>>> >>>> Regards, >>>>> >>>> >>>>> >>>> Lyubomir >>>>> >>>> >>>>> >>>> >>>>> >>>> On 13 June 2013 08:03, Lyubomir Yotov wrote: >>>>> >>>>> Hello Adrian, >>>>> >>>>> I did some tests and discovered that the problem is related to >>>>> >>>>> "halt"/"shutdown" of system. If "reboot" is carried out than >>>>> there is >>>>> >> no >>>>> >>>>> problem and the wifi works properly (even if done from Gnome - >>>>> Gnome >>>>> >> seems >>>>> >>>>> to have no relation to the problem). So what could lead to >>>>> "ath0: time >>>>> >> out" >>>>> >>>>> after shutting down or halting the system? I noticed that there >>>>> are irq >>>>> >>>>> storms on irq 17 which is the wifi irq (interrupt storm detected >>>>> on >>>>> >>>>> "irq17:"; throttling interrupt source). Something else that I am >>>>> not >>>>> >> sure to >>>>> >>>>> have relevance - after shutdown during the start-up ath0 is >>>>> reported >>>>> >> to use >>>>> >>>>> autoselect mode 11g: >>>>> >>>>> (below is from dmesg) >>>>> >>>>> >>>>> >>>>> ath0: flags=8843 metric >>>>> 0 mtu >>>>> >>>>> 2290 >>>>> >>>>> >>>>> >>>>> ether 00:19:7e:91:xx:xx >>>>> >>>>> nd6 options=29 >>>>> >>>>> media: IEEE 802.11 Wireless Ethernet autoselect mode 11g >>>>> >>>>> status: associated >>>>> >>>>> >>>>> >>>>> After the boot has finished the mode changes to 11a: >>>>> >>>>> >>>>> >>>>> #ifconfig ath0 >>>>> >>>>> >>>>> >>>>> ath0: flags=8843 metric >>>>> 0 mtu >>>>> >>>>> 2290 >>>>> >>>>> ether 00:19:7e:91:xx:xx >>>>> >>>>> nd6 options=29 >>>>> >>>>> media: IEEE 802.11 Wireless Ethernet autoselect mode 11a >>>>> >>>>> status: associated >>>>> >>>>> >>>>> >>>>> Do you have any idea where to look for now? >>>>> >>>>> >>>>> >>>>> Regards, >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Lyubomir >>>>> >>>>> P.S. I will try to play with acpi_ibm.ko and see if things >>>>> change if I >>>>> >>>>> make it auto-load. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On 10 June 2013 16:06, Lyubomir Yotov wrote: >>>>> >>>>>> Hello Adrian, >>>>> >>>>>> >>>>> >>>>>> Attached are files with consecutive vmstat -i when the wlan is >>>>> working >>>>> >>>>>> (vmstat-i_working.txt) and when the wlan is not working >>>>> >>>>>> (vmstat-i_not_working.txt). There is also output from ifconfig >>>>> when >>>>> >> the wlan >>>>> >>>>>> is not working (ifconfig.txt). >>>>> >>>>>> After some more deeper investigation it seems to me that the >>>>> problem >>>>> >>>>>> appears after starting X with Gnome. I will continue >>>>> investigating >>>>> >> with >>>>> >>>>>> "reboot"/"halt -p" and inform you. >>>>> >>>>>> BTW do you think that starting Gnome session (using startx, as I >>>>> >> haven't >>>>> >>>>>> set auto start of X if this is of any importance) can cause >>>>> problems >>>>> >> - in >>>>> >>>>>> Gnome I have no settings for the network in the >>>>> "System->Network" >>>>> >>>>>> application and I start it with normal user? >>>>> >>>>>> >>>>> >>>>>> Regards, >>>>> >>>>>> >>>>> >>>>>> Lyubo >>>>> >>>>>> >>>>> >>>>>> >>>>> >>>>>> On 9 June 2013 18:28, Adrian Chadd wrote: >>>>> >>>>>>> Can you please paste the vmstat -i output? >>>>> >>>>>>> >>>>> >>>>>>> >>>>> >>>>>>> >>>>> >>>>>>> adrian >>>>> >>>>>>> >>>>> >>>>>>> On 9 June 2013 06:53, Lyubomir Yotov >>>>> wrote: >>>>> >>>>>>>> Hi, >>>>> >>>>>>>> >>>>> >>>>>>>> After restart from Windows and working wireless the number of >>>>> >>>>>>>> interrupts >>>>> >>>>>>>> increases and the rate increases. After next restart (the ath0 >>>>> >> times >>>>> >>>>>>>> out) >>>>> >>>>>>>> the interrupts increase but the rate is going down. >>>>> >>>>>>>> I noticed that after restart from Windows and working wifi if >>>>> I >>>>> >>>>>>>> restart >>>>> >>>>>>>> /etc/rc.d/netif the wifi is working again. If I shutdown >>>>> wlan0 and >>>>> >>>>>>>> bring it >>>>> >>>>>>>> up again then I wlan0 doesn't get address but ath0 is not >>>>> timing >>>>> >> out. >>>>> >>>>>>>> I can >>>>> >>>>>>>> still get a list with the available APs around. >>>>> >>>>>>>> >>>>> >>>>>>>> Regards, >>>>> >>>>>>>> >>>>> >>>>>>>> Lyubo >>>>> >>>>>>>> >>>>> >>>>>>>> >>>>> >>>>>>>> >>>>> >>>>>>>> >>>>> >>>>>>>> >>>>> >>>>>>>> >>>>> >>>>>>>> On 8 June 2013 18:28, Adrian Chadd >>>>> wrote: >>>>> >>>>>>>>> Hm! >>>>> >>>>>>>>> >>>>> >>>>>>>>> Ok, this should be working. I frequently test (read: every >>>>> other >>>>> >>>>>>>>> day) >>>>> >>>>>>>>> with the AR5416. But you're not the first person to report >>>>> this >>>>> >> bug. >>>>> >>>>>>>>> >>>>> >>>>>>>>> Unfortunately when this happens, the interrupts aren't >>>>> actually >>>>> >>>>>>>>> making >>>>> >>>>>>>>> it to the OS. >>>>> >>>>>>>>> >>>>> >>>>>>>>> Can you check the output of vmstat -i whilst you're doing >>>>> it? The >>>>> >>>>>>>>> ath0 >>>>> >>>>>>>>> counter should be increasing. >>>>> >>>>>>>>> >>>>> >>>>>>>>> >>>>> >>>>>>>>> >>>>> >>>>>>>>> adrian >>>>> >>>>>>>>> >>>>> >>>>>>>>> On 8 June 2013 06:49, Lyubomir Yotov >>>>> wrote: >>>>> >>>>>>>>>> Hello, >>>>> >>>>>>>>>> I have a Thinkpad T60 with dual boot between Windows XP and >>>>> >>>>>>>>>> FreeBSD >>>>> >>>>>>>>>> 9.1-Release: >>>>> >>>>>>>>>> >>>>> >>>>>>>>>> uname -a >>>>> >>>>>>>>>> FreeBSD T60.workgroup 9.1-RELEASE FreeBSD 9.1-RELEASE #0 >>>>> >> r243826: >>>>> >>>>>>>>>> Tue >>>>> >>>>>>>>>> Dec >>>>> >>>>>>>>>> 4 06:55:39 UTC 2012 >>>>> >>>>>>>>>> root@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC >>>>> >>>>>>>>>> i386 >>>>> >>>>>>>>>> >>>>> >>>>>>>>>> I am trying to use my wifi card which is: >>>>> >>>>>>>>>> >>>>> >>>>>>>>>> dmesg >>>>> >>>>>>>>>> .... >>>>> >>>>>>>>>> ath0: mem 0xedf00000-0xedf0ffff irq 17 at >>>>> device >>>>> >>>>>>>>>> 0.0 on >>>>> >>>>>>>>>> pci3 >>>>> >>>>>>>>>> ath0: AR5418 mac 12.10 RF5133 phy 8.1 >>>>> >>>>>>>>>> .... >>>>> >>>>>>>>>> >>>>> >>>>>>>>>> pciconf -lv >>>>> >>>>>>>>>> .... >>>>> >>>>>>>>>> ath0@pci0:3:0:0: class=0x028000 card=0x0033168c >>>>> >>>>>>>>>> chip=0x0024168c >>>>> >>>>>>>>>> rev=0x01 hdr=0x00 >>>>> >>>>>>>>>> vendor = 'Atheros Communications Inc.' >>>>> >>>>>>>>>> device = 'AR5008 Wireless Network Adapter' >>>>> >>>>>>>>>> class = network >>>>> >>>>>>>>>> ..... >>>>> >>>>>>>>>> >>>>> >>>>>>>>>> I followed several HOW-TOs in order to make it work. >>>>> >> Unfortunately >>>>> >>>>>>>>>> I it >>>>> >>>>>>>>>> is >>>>> >>>>>>>>>> working only after I reboot from my Windows installation >>>>> >>>>>>>>>> (regardless of >>>>> >>>>>>>>>> the >>>>> >>>>>>>>>> position of the wifi switch on the front panel of the >>>>> notebook). >>>>> >>>>>>>>>> After >>>>> >>>>>>>>>> restart from Windows everything is fine - the wifi >>>>> associates >>>>> >> with >>>>> >>>>>>>>>> the >>>>> >>>>>>>>>> AP >>>>> >>>>>>>>>> and I can use it. If I reboot the system during the boot and >>>>> >>>>>>>>>> afterwards >>>>> >>>>>>>>>> I >>>>> >>>>>>>>>> constantly get: >>>>> >>>>>>>>>> >>>>> >>>>>>>>>> ath0: device timeout >>>>> >>>>>>>>>> >>>>> >>>>>>>>>> When I get the device status through ifconfig I can see that >>>>> >> ath0 >>>>> >>>>>>>>>> is >>>>> >>>>>>>>>> associated but wlan0 is not associated. >>>>> >>>>>>>>>> >>>>> >>>>>>>>>> ifconfig ath0 >>>>> >>>>>>>>>> ath0: flags=8843 >>>>> metric >>>>> >> 0 >>>>> >>>>>>>>>> mtu >>>>> >>>>>>>>>> 2290 >>>>> >>>>>>>>>> ether 00:19:7e:91:xx:xx >>>>> >>>>>>>>>> nd6 options=29 >>>>> >>>>>>>>>> media: IEEE 802.11 Wireless Ethernet autoselect >>>>> mode 11g >>>>> >>>>>>>>>> status: associated >>>>> >>>>>>>>>> >>>>> >>>>>>>>>> ifconfig wlan0 >>>>> >>>>>>>>>> wlan0: flags=8843 >>>>> >> metric 0 >>>>> >>>>>>>>>> mtu >>>>> >>>>>>>>>> 1500 >>>>> >>>>>>>>>> ether 00:19:7e:91:xx:xx >>>>> >>>>>>>>>> nd6 options=29 >>>>> >>>>>>>>>> media: IEEE 802.11 Wireless Ethernet autoselect >>>>> >>>>>>>>>> (autoselect) >>>>> >>>>>>>>>> status: no carrier >>>>> >>>>>>>>>> ssid "" channel 5 (2432 MHz 11g) >>>>> >>>>>>>>>> regdomain 98 indoor ecm authmode WPA privacy ON >>>>> deftxkey >>>>> >>>>>>>>>> UNDEF >>>>> >>>>>>>>>> txpower 20 bmiss 7 scanvalid 450 bgscan bgscanintvl >>>>> 300 >>>>> >>>>>>>>>> bgscanidle >>>>> >>>>>>>>>> 250 >>>>> >>>>>>>>>> roam:rssi 7 roam:rate 5 protmode CTS wme burst >>>>> roaming >>>>> >>>>>>>>>> MANUAL >>>>> >>>>>>>>>> >>>>> >>>>>>>>>> >>>>> >>>>>>>>>> In /var/log/messages I get: >>>>> >>>>>>>>>> >>>>> >>>>>>>>>> Jun 8 16:39:16 PC wpa_supplicant[3463]: Trying to associate >>>>> >> with >>>>> >>>>>>>>>> 54:e6:fc:ae:xx:xx (SSID='access1' freq=2432 MHz) >>>>> >>>>>>>>>> Jun 8 16:39:20 PC kernel: ath0: device timeout >>>>> >>>>>>>>>> Jun 8 16:39:26 PC wpa_supplicant[3463]: Authentication with >>>>> >>>>>>>>>> 54:e6:fc:ae:xx:xx timed out. >>>>> >>>>>>>>>> >>>>> >>>>>>>>>> If I scan for wireless networks I get a list and my ap is >>>>> in the >>>>> >>>>>>>>>> list >>>>> >>>>>>>>>> >>>>> >>>>>>>>>> ifconfig wlan0 scan >>>>> >>>>>>>>>> SSID/MESH ID BSSID CHAN RATE S:N INT >>>>> CAPS >>>>> >>>>>>>>>> net1 00:11:11:01:xx:xx 6 54M -68:-96 100 EP >>>>> >>>>>>>>>> 5edf9c 70:71:bc:26:xx:xx 11 54M -68:-96 100 EP >>>>> >> WPS >>>>> >>>>>>>>>> WPA >>>>> >>>>>>>>>> WME >>>>> >>>>>>>>>> access1 54:e6:fc:ae:xx:xx 5 54M -66:-96 100 EP >>>>> WPA >>>>> >>>>>>>>>> HTCAP >>>>> >>>>>>>>>> WME >>>>> >>>>>>>>>> >>>>> >>>>>>>>>> >>>>> >>>>>>>>>> In rc.local I have: >>>>> >>>>>>>>>> >>>>> >>>>>>>>>> wlans_ath0="wlan0" >>>>> >>>>>>>>>> ifconfig_wlan0="WPA DHCP" >>>>> >>>>>>>>>> >>>>> >>>>>>>>>> In wpa_supplicant I have: >>>>> >>>>>>>>>> >>>>> >>>>>>>>>> ctrl_interface=/var/run/wpa_supplicant >>>>> >>>>>>>>>> eapol_version=2 >>>>> >>>>>>>>>> ap_scan=1 >>>>> >>>>>>>>>> fast_reauth=1 >>>>> >>>>>>>>>> >>>>> >>>>>>>>>> network={ >>>>> >>>>>>>>>> ssid="access1" >>>>> >>>>>>>>>> psk="secret1" >>>>> >>>>>>>>>> priority=5 >>>>> >>>>>>>>>> } >>>>> >>>>>>>>>> network={ >>>>> >>>>>>>>>> ssid="access2" >>>>> >>>>>>>>>> psk="secret2" >>>>> >>>>>>>>>> priority=5 >>>>> >>>>>>>>>> } >>>>> >>>>>>>>>> >>>>> >>>>>>>>>> I searched the net for solution to my problem but I couldn't >>>>> >> find >>>>> >>>>>>>>>> one. >>>>> >>>>>>>>>> Can >>>>> >>>>>>>>>> you help me with this? >>>>> >>>>>>>>>> >>>>> >>>>>>>>>> >>>>> >>>>>>>>>> Regards, >>>>> >>>>>>>>>> >>>>> >>>>>>>>>> Lyubomir >>>>> >>>>>>>>>> _______________________________________________ >>>>> >>>>>>>>>> freebsd-mobile@freebsd.org mailing list >>>>> >>>>>>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-mobile >>>>> >>>>>>>>>> To unsubscribe, send any mail to >>>>> >>>>>>>>>> "freebsd-mobile-unsubscribe@freebsd.org" >>>>> >>>>>>>> >>>>> >>>>>> >>>>> > _______________________________________________ >>>>> > 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" >>>>> > >>>>> >>>>> >>>> >>> >> >