From owner-freebsd-mobile@FreeBSD.ORG Mon Jul 15 20:30:04 2013 Return-Path: Delivered-To: freebsd-mobile@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 9A7657E9; Mon, 15 Jul 2013 20:30:04 +0000 (UTC) (envelope-from l.yotov@gmail.com) Received: from mail-qc0-x22d.google.com (mail-qc0-x22d.google.com [IPv6:2607:f8b0:400d:c01::22d]) by mx1.freebsd.org (Postfix) with ESMTP id 31116945; Mon, 15 Jul 2013 20:30:04 +0000 (UTC) Received: by mail-qc0-f173.google.com with SMTP id l10so6520264qcy.4 for ; Mon, 15 Jul 2013 13:30:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ry19AyIDr+nXEB/rbW6df68TP9I+6mAuIcBWltp+EkM=; b=dwumhrL0sSCr2pXKc2MHYYQPvzr0KVsH3rH+KnbG0tanx7vyR0rXtXJn6etS81oyKE Z4kQ9W5ny/vNKmlMpIxQlVjwkxLnuqPrELxcnqdaP+QwW8tDoaTRBd5UQ0ROsXnz/hgW xyEAhQ1EOH3693lTPbpQFAl4/MjmuonX1NvOh1SzcBzXHQsoLHu5rSEYKo/JHyutzDKO 26oD/PcUqy81utZL/Y+k9oR3K/XeGkYW8Q5zbZn5siU+dK0zF4FbwW676dH9kxjVr292 YrTq/9cgvjvfqGwnJFocVvz6goc3ixePbATbQUt3TtdZX4wAw0A43CsfE2hnOMaOz1/T CbvQ== MIME-Version: 1.0 X-Received: by 10.224.13.202 with SMTP id d10mr56255629qaa.19.1373920203731; Mon, 15 Jul 2013 13:30:03 -0700 (PDT) Received: by 10.224.58.143 with HTTP; Mon, 15 Jul 2013 13:30:03 -0700 (PDT) In-Reply-To: <51C8AE67.7040801@unsane.co.uk> References: <51C8AE67.7040801@unsane.co.uk> Date: Mon, 15 Jul 2013 23:30:03 +0300 Message-ID: Subject: Re: Thinkpad T60 with Atheros working only after restart from Windows From: Lyubomir Yotov To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-wireless@freebsd.org, Vincent Hoffman , freebsd-mobile@freebsd.org X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jul 2013 20:30:04 -0000 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" > > > > From owner-freebsd-mobile@FreeBSD.ORG Tue Jul 16 08:51:25 2013 Return-Path: Delivered-To: freebsd-mobile@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 56AE5AB4; Tue, 16 Jul 2013 08:51:25 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com [IPv6:2a00:1450:400c:c00::234]) by mx1.freebsd.org (Postfix) with ESMTP id 9266782D; Tue, 16 Jul 2013 08:51:24 +0000 (UTC) Received: by mail-wg0-f52.google.com with SMTP id b12so349482wgh.19 for ; Tue, 16 Jul 2013 01:51:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=nvU0OzUb4c99+KNDCmNLU2CObQVHBaRRlPPa6Qk0hy0=; b=X03fbpKv7GtNfNaeFi8k0MXcMsG1vsc5PvFZEEcYumzMwabvl0gLiV2CchoaMCeSTk 2K/8T9n2uatETo8xFwiaRJqYe7DLH8IGMFJRoYkvyLd+cGoCTwTVUqdRhJ9SnY483yhf i7C20nJQk8y4NzODMAVup+5B55czI79KV3To528ujU5uavXr/jhDUwwHGSc5ypjR27Cm SSRK52AiDBLmJx/ttFz9jZZA+fArSwvRK0vmcocJlRNxDRZACqydwrVSbeJCfiRQGBVg UbhqHH1sVvvdmgXGRMZeOPA1vjMt95llK+6RldkeCWvGnwfPff9jPq5sXq/F3bi+cVnp NcBw== MIME-Version: 1.0 X-Received: by 10.194.11.72 with SMTP id o8mr436273wjb.0.1373964683620; Tue, 16 Jul 2013 01:51:23 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.94.132 with HTTP; Tue, 16 Jul 2013 01:51:23 -0700 (PDT) In-Reply-To: References: <51C8AE67.7040801@unsane.co.uk> Date: Tue, 16 Jul 2013 01:51:23 -0700 X-Google-Sender-Auth: TDV1w6qlHUyst-INzUfNqaRYiBw 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.14 Cc: freebsd-wireless@freebsd.org, Vincent Hoffman , freebsd-mobile@freebsd.org X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jul 2013 08:51:25 -0000 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" >> > >> >> > From owner-freebsd-mobile@FreeBSD.ORG Wed Jul 17 15:29:28 2013 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1332476B; Wed, 17 Jul 2013 15:29:28 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) by mx1.freebsd.org (Postfix) with ESMTP id 826F68BC; Wed, 17 Jul 2013 15:29:27 +0000 (UTC) Received: from park.js.berklix.net (pD9FBEF06.dip0.t-ipconnect.de [217.251.239.6]) (authenticated bits=128) by land.berklix.org (8.14.5/8.14.5) with ESMTP id r6HFTPls089574; Wed, 17 Jul 2013 15:29:26 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by park.js.berklix.net (8.14.3/8.14.3) with ESMTP id r6HFTHjA004066; Wed, 17 Jul 2013 17:29:17 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id r6HFTBIZ063855; Wed, 17 Jul 2013 17:29:17 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <201307171529.r6HFTBIZ063855@fire.js.berklix.net> To: John Baldwin Subject: Re: Adding a hook to shutdown.c & halt (reboot.c) to call a script. From: "Julian H. Stacey" Organization: http://berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Wed, 10 Jul 2013 14:35:56 EDT." <201307101435.56193.jhb@freebsd.org> Date: Wed, 17 Jul 2013 17:29:11 +0200 Sender: jhs@berklix.com Cc: freebsd-mobile@freebsd.org X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jul 2013 15:29:28 -0000 Hi, Reference: > From: John Baldwin > Date: Wed, 10 Jul 2013 14:35:56 -0400 John Baldwin wrote: > On Friday, July 05, 2013 6:35:02 pm Julian H. Stacey wrote: > > > shutdown(8) signals init (unless -o is given), which will run > > > /etc/rc.shutdown from multi-user mode. The same applies to ctrl+alt+del, > > > kernel-controlled overheating shutdown, etc. > > > > Thanks Jilles, So I appended to my rc.shutdown > > # -x not -f below to also allow a symbolic link to work. > > if [ -x "/etc/rc.shutmedia" ]; then > > /etc/rc.shutmedia > > & renamed my URL to http://www.berklix.com/~jhs/bin/.sh/rc.shutmedia > > > > > > > reboot(8) and halt(8) do not involve init and do not run any shutdown > > > scripts. I think they should be changed to signal init (except reboot > > > -q, halt -q) and should not be used until then. However, there are > > > apparently some problems with that. > > > > > > The incorrect umount order should perhaps be fixed in the kernel. > > > > Yes, bad enough for a local laptop to hang, > > if it was a remote server, very nasty. > > You can just put a script in /usr/local/etc/rc.d. If it has the > 'shutdown' keyword it gets run with a 'stop' command during shutdown. > > (Just grep for "shutdown" in /etc/rc.d to find example scripts) Thanks John, I tried, it works :-) This thread also includes USB shutdowns so I'm cross referencing: http://lists.freebsd.org/pipermail/freebsd-stable/2013-July/074280.html Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Reply below not above, like a play script. Indent old text with "> ". Send plain text. No quoted-printable, HTML, base64, multipart/alternative. From owner-freebsd-mobile@FreeBSD.ORG Wed Jul 17 20:06:52 2013 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E8BDC289; Wed, 17 Jul 2013 20:06:52 +0000 (UTC) (envelope-from l.yotov@gmail.com) Received: from mail-qe0-x234.google.com (mail-qe0-x234.google.com [IPv6:2607:f8b0:400d:c02::234]) by mx1.freebsd.org (Postfix) with ESMTP id 7EC7C898; Wed, 17 Jul 2013 20:06:52 +0000 (UTC) Received: by mail-qe0-f52.google.com with SMTP id i11so1387236qej.11 for ; Wed, 17 Jul 2013 13:06:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=s4tXHb9ThARXcnZh5c4+oMDOCGgKbh9mwQZ7oWvX0NI=; b=GsPbz2+DjNOrp7/pAqALwg1wlfzmSIgJstc5GazkfDJUt0JkexzJJGYfU+dm9HUm8u hI20J2M8CUyxHAz/9fCMIhE06/tboEAuFjB3FMkFPBp5mVfrA4b9ZpQhNMVx3gwp3iaQ pBzoMWwZXJtRyK29sZpVlTRFtVr9j381uEKrty+yP+phebysaJlqZMuKg8dyzyIzUrXb CjmniVjwp2mdvo8vOvMYMdHA+DhgxbDefest4bY7M33b2Q6bxwan7IkKb1tC4iYnD0JQ KOaArn5Dt9wRChHaqgVUUcoApEXPLSgfVpt/uqFdEoaxpeCl74uewkBcP7M6bEg9KvkO XflQ== MIME-Version: 1.0 X-Received: by 10.224.67.202 with SMTP id s10mr10459934qai.66.1374091612040; Wed, 17 Jul 2013 13:06:52 -0700 (PDT) Received: by 10.224.58.143 with HTTP; Wed, 17 Jul 2013 13:06:51 -0700 (PDT) In-Reply-To: References: <51C8AE67.7040801@unsane.co.uk> Date: Wed, 17 Jul 2013 23:06:51 +0300 Message-ID: Subject: Re: Thinkpad T60 with Atheros working only after restart from Windows From: Lyubomir Yotov To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-wireless@freebsd.org, Vincent Hoffman , freebsd-mobile@freebsd.org X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jul 2013 20:06:53 -0000 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" >>> > >>> >>> >> > From owner-freebsd-mobile@FreeBSD.ORG Sat Jul 20 20:36:46 2013 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 49FEB877 for ; Sat, 20 Jul 2013 20:36:46 +0000 (UTC) (envelope-from holyfathersaintbruno@gmail.com) Received: from mail-oa0-x22a.google.com (mail-oa0-x22a.google.com [IPv6:2607:f8b0:4003:c02::22a]) by mx1.freebsd.org (Postfix) with ESMTP id 1A3612CE for ; Sat, 20 Jul 2013 20:36:46 +0000 (UTC) Received: by mail-oa0-f42.google.com with SMTP id j6so7609201oag.29 for ; Sat, 20 Jul 2013 13:36:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=K+tIwk/xxxIGmx9DByK973givL1N58U8CtgjJGFjzI8=; b=rIQilERgSW8Qkcm/zNMiPWMRqQ4ydyCbgzA/h+v7RgruK2KcwqUpn5eMrrKiuRjgMi PW+1A7yWhrc2HwTU0Qn+TM65WH1SAQzDxyPr16ADj70k9+UbdK0uX66sgx1sIZZSVr7d ljl1JtSuqqo4gvS8wIV6zOnu6iUzJEr61oIpDVDnf1foGWDdnvJHKLbO5rzfDpHoqVzd lSTCj2Spi0oL11QWId+o2Q4kVS/7imRFV3XPBzjRouC2p5s/LRxy1f0B9GDO9iFvZwbm NSxu2TOqikAj87kC6K/IwV959VT9fpGAfKoFXjVKMPsFAzA+JON9UbxuGlNr6buT/XUN bRdQ== X-Received: by 10.182.165.232 with SMTP id zb8mr16297399obb.101.1374352605645; Sat, 20 Jul 2013 13:36:45 -0700 (PDT) Received: from [192.168.0.11] (cpe-72-183-246-29.elp.res.rr.com. [72.183.246.29]) by mx.google.com with ESMTPSA id el16sm27785076oeb.2.2013.07.20.13.36.44 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 20 Jul 2013 13:36:45 -0700 (PDT) Message-ID: <51EAF4D0.2030800@gmail.com> Date: Sat, 20 Jul 2013 14:36:32 -0600 From: Bruno Cartusia User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130630 Thunderbird/17.0.7 MIME-Version: 1.0 To: freebsd-mobile@freebsd.org Subject: Developing for Android on FreeBSD Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Jul 2013 20:36:46 -0000 I have read an older post, but unfortunately the links were not working for me. Any of these things would satisfy me: 1) Virtualizing Android on FreeBSD. 2) Emulating it. 3) Some sort of SDK download would be nice. Some were mentioning using Eclipse. http://freebsd.1045724.n5.nabble.com/Android-SDK-td4292027.html (This is the thread I was talking about). I apologize if this is something that might be asked frequently (if it has been answered can someone provide a link?). Any tips advice, would be nice. Take care. Greatly appreciated and thanks in advance.