From owner-freebsd-mobile@FreeBSD.ORG Mon Jun 24 16:14:50 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 00ADC897; Mon, 24 Jun 2013 16:14:49 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qa0-x235.google.com (mail-qa0-x235.google.com [IPv6:2607:f8b0:400d:c00::235]) by mx1.freebsd.org (Postfix) with ESMTP id 993691FFE; Mon, 24 Jun 2013 16:14:49 +0000 (UTC) Received: by mail-qa0-f53.google.com with SMTP id g10so2321880qah.5 for ; Mon, 24 Jun 2013 09:14:49 -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=QaWLr/bSMCFS9sA15IGQ5JQc5UMgG9SNSMHF6U3O2EM=; b=ydg8vvJEtgfdVQ56w16Hjyv2m17NPW+9rzwqqcJF7h9mJ5WljZLOTVZ9p2WIGi91uv GtiQdTFjwT7jyaXCr/7thV/R1mBusvTBi/rEaA/SL99QDDalm3sivC6oHB6vZ6URiCdh NKiHe/h5I4PI9IipNJYng9fSpfGTZNmIkg6nKi0E8Rqmn4aGvvbLskPn0WtPHiBrwnKd 8kM22fPcEWtvxpwtVw7xH0RWezi3UljROEHjYssCnWCAk1ax+p21AQPi7s/fW/xKwgmK ZL1UuXe67rf0+pv+oz6KfIt1MyDAzO+WWPNwx+Z66allgR9R5OarfnqZsXI79VnLkKGR HnLA== MIME-Version: 1.0 X-Received: by 10.49.98.196 with SMTP id ek4mr28331656qeb.8.1372090489177; Mon, 24 Jun 2013 09:14:49 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.5.65 with HTTP; Mon, 24 Jun 2013 09:14:49 -0700 (PDT) In-Reply-To: <51C41E03.6060205@FreeBSD.org> References: <51C41E03.6060205@FreeBSD.org> Date: Mon, 24 Jun 2013 09:14:49 -0700 X-Google-Sender-Auth: a4XzqGRxA23CVnsf7zVAl6Bokr4 Message-ID: Subject: Re: Atom N450 + C3 + HPET == bad timer behaviour From: Adrian Chadd To: Alexander Motin Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current , 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, 24 Jun 2013 16:14:50 -0000 Hi, It's (transcribed): kern.timecounter.hardware: TSC kern.timecounter.choice: TSC(1000) ACPI-fast (900) HPET (950) i8254 (0) dummy(-1000) kern.timecounter.tick: 1 kern.timecounter.fast_gettime: 1 kern.timecounter.invariant_tsc: 1 kern.timecounter.smp_tsc: 1 kern.timecounter.smp_tsc_adjust: 0 kern.timecounter.tsc_shift: 1 Thanks, Adrian From owner-freebsd-mobile@FreeBSD.ORG Mon Jun 24 17:21:06 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 ACA49AB9; Mon, 24 Jun 2013 17:21:06 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qa0-x22c.google.com (mail-qa0-x22c.google.com [IPv6:2607:f8b0:400d:c00::22c]) by mx1.freebsd.org (Postfix) with ESMTP id 5D4E11338; Mon, 24 Jun 2013 17:21:06 +0000 (UTC) Received: by mail-qa0-f44.google.com with SMTP id j8so2416086qah.3 for ; Mon, 24 Jun 2013 10:21:05 -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=PElbK9rmZB1sEnuTijV8wQ2UMEyRpffbhmN5BzQSchE=; b=nTpFDyMeazSLPJ+bdIh4VMP4s0n478tdTM2koTaZ3h078kLeCugUKc0Ba33TZubM1M ntecuYNnH2CB82q5DVazbQqFzbs704ggNTDthU3T/7wSOMP8KY+7EFSsKYg6g5EeeEm9 A//FBo3BXEBvR1CAxfdf+r3ua0pqZ9itGX28IY7zkhGpsqw+EPVvF5s+byg8evDcqKMC GheGCKVklzwHHmfX84iIYO74IRGpv3BpX+H5O+B5YGYRaydQZqWGBKWNg6Ax/jhlO+c/ /mlKDldPi/xe6qy3WIhTkiYOv6kGfobZMfvYuLIi0umL91hq0RnuOyxDbkc6EXX/JM5e AKcQ== MIME-Version: 1.0 X-Received: by 10.229.204.131 with SMTP id fm3mr4522406qcb.15.1372094465785; Mon, 24 Jun 2013 10:21:05 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.5.65 with HTTP; Mon, 24 Jun 2013 10:21:05 -0700 (PDT) In-Reply-To: References: Date: Mon, 24 Jun 2013 10:21:05 -0700 X-Google-Sender-Auth: RbrKpWix3koI2MHJAchviyixSRI 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 Cc: freebsd-wireless@freebsd.org, 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, 24 Jun 2013 17:21:06 -0000 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" >>>>> > >>>>> > >>>> >>>> >>> >> > From owner-freebsd-mobile@FreeBSD.ORG Mon Jun 24 20:01:37 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 A76AF640; Mon, 24 Jun 2013 20:01:37 +0000 (UTC) (envelope-from l.yotov@gmail.com) Received: from mail-qa0-x231.google.com (mail-qa0-x231.google.com [IPv6:2607:f8b0:400d:c00::231]) by mx1.freebsd.org (Postfix) with ESMTP id 44A9F1CD1; Mon, 24 Jun 2013 20:01:37 +0000 (UTC) Received: by mail-qa0-f49.google.com with SMTP id hu16so35803qab.15 for ; Mon, 24 Jun 2013 13:01:36 -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=gSJwCmIephgnIyKacWZ0jCwln4QMS6y0KrBY12ahTEc=; b=XUpElSvlLc0sxhr10sVtUe4VAemCTTc8yk5FzIUwnmUcdXuIpALHwMYmyGgjc/IMNo RjxXNmIt3RPpAuRo+4Q8/4KbXU+X58XW41j6ODqnx7OCptuLqgk5GIFOdXLkpyrY0Oqa /Wjaz2HuSO91TNIke7d1nCLnoJsTRV9BAmdHRotXmcG7MO3qKvPvUp+S/zL4S0zao2oE UUIQo8d1JY1hy/trKUyQjda5sIZ2dxCLBalUOHzdccmxJRXsHIRzs8MOn/Aah4GFpkvb KgaxHKcSMdKoy4o5jLlEvREvX79ihwYIr4ONkL283MI/UedOP5HB/R+fSm6n3CUQ57/L 3RiA== MIME-Version: 1.0 X-Received: by 10.224.148.19 with SMTP id n19mr28369806qav.66.1372104096150; Mon, 24 Jun 2013 13:01:36 -0700 (PDT) Received: by 10.224.98.147 with HTTP; Mon, 24 Jun 2013 13:01:36 -0700 (PDT) In-Reply-To: References: Date: Mon, 24 Jun 2013 23:01:36 +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, 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, 24 Jun 2013 20:01:37 -0000 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" > >>>>> > > >>>>> > > >>>> > >>>> > >>> > >> > > > From owner-freebsd-mobile@FreeBSD.ORG Mon Jun 24 20:39:06 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 E1ABDB06; Mon, 24 Jun 2013 20:39:06 +0000 (UTC) (envelope-from vince@unsane.co.uk) Received: from unsane.co.uk (unsane-pt.tunnel.tserv5.lon1.ipv6.he.net [IPv6:2001:470:1f08:110::2]) by mx1.freebsd.org (Postfix) with ESMTP id 665251EB9; Mon, 24 Jun 2013 20:39:06 +0000 (UTC) Received: from vincemacbook.unsane.co.uk (vincemacbook.unsane.co.uk [10.10.10.20]) (authenticated bits=0) by unsane.co.uk (8.14.7/8.14.6) with ESMTP id r5OKd3sM007083 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 24 Jun 2013 21:39:04 +0100 (BST) (envelope-from vince@unsane.co.uk) Message-ID: <51C8AE67.7040801@unsane.co.uk> Date: Mon, 24 Jun 2013 21:39:03 +0100 From: Vincent Hoffman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: Lyubomir Yotov Subject: Re: Thinkpad T60 with Atheros working only after restart from Windows References: In-Reply-To: X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Adrian Chadd , freebsd-wireless@freebsd.org, 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, 24 Jun 2013 20:39:07 -0000 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 Fri Jun 28 18:35:48 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 96C226FA; Fri, 28 Jun 2013 18:35:48 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qc0-x22f.google.com (mail-qc0-x22f.google.com [IPv6:2607:f8b0:400d:c01::22f]) by mx1.freebsd.org (Postfix) with ESMTP id 25C521E42; Fri, 28 Jun 2013 18:35:48 +0000 (UTC) Received: by mail-qc0-f175.google.com with SMTP id k14so1572469qcv.34 for ; Fri, 28 Jun 2013 11:35:47 -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=NZYGbbhw6Mv7pQCBjKoqQel3abzYqo2SaUUthfUPRDo=; b=XPZQ1S/xIJatMUrZhPVT+0Cvv8H0FePkDvv1cA3kSkK8Ioo8Nc2DFfDUnZeBqZuEtA 1LIv6uKgopzZoX4uZJsdbkIhoNOH9YSeozljKi7eRc5YJ12ZAHeti8i8uV7ADvEA9vWY bDsKoOPgBKBZq1SaP0yvOQcgyZyAobQLkN1BYrOEsSK70MxdoNc5wtfhK4BZCepT/PtU tprtbi0uehGyl8RlyWOWajUYG3S3T81a4YlF9FyKYOTCsGENymu10g6h2pPkjcFAvDgw 4HpuctzndFdPUN36rb9+0l4YK6d6u+QwqybvezgsvBp/C0cDlIMx9V8nWx9E7LyOMgvU 1CqA== MIME-Version: 1.0 X-Received: by 10.224.190.137 with SMTP id di9mr19113039qab.95.1372444547670; Fri, 28 Jun 2013 11:35:47 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.214.7 with HTTP; Fri, 28 Jun 2013 11:35:47 -0700 (PDT) In-Reply-To: References: <20120624.022452.67408510.iwasaki@jp.FreeBSD.org> <20120625.225430.106438166.iwasaki@jp.FreeBSD.org> Date: Fri, 28 Jun 2013 11:35:47 -0700 X-Google-Sender-Auth: ZQypW5bpD6aga3Z-gAGQeX9i7e8 Message-ID: Subject: Re: STABLE/9 SMP ACPI suspend/resume - video mode not being restored From: Adrian Chadd To: Mitsuru IWASAKI Content-Type: text/plain; charset=ISO-8859-1 Cc: iwasaki@freebsd.org, freebsd-stable@freebsd.org, jkim@freebsd.org, 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: Fri, 28 Jun 2013 18:35:48 -0000 hi! Just as a note - this is still a problem on _all_ hardware I have running -9 or -HEAD. If you resume in text mode and it's a non-default mode (ie, it's not VGA 80x25), it comes back corrupted. Would someone please try it out? It's pretty easy to try out: * set a non-default VGA Mode (say, 80x50) * go through an ACPI suspend/resume cycle * See the VGA display be corrupt. On 21 July 2012 17:28, Adrian Chadd wrote: > Hi! > > I just tried it. It worked: > > * resume occured and the video mode was corrupt; > * then shortly after it went through all the reattaching, and the > video mode was fixed. > > Why's the video mode starting off corrupted? > > > Adrian