From owner-freebsd-mobile@FreeBSD.ORG Mon Dec 21 01:37:16 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B3E2106566B for ; Mon, 21 Dec 2009 01:37:16 +0000 (UTC) (envelope-from service@noreply.bebo.com) Received: from vmta04.bebo.com (vmta04.bebo.com [208.75.184.157]) by mx1.freebsd.org (Postfix) with ESMTP id 4D33C8FC0A for ; Mon, 21 Dec 2009 01:37:16 +0000 (UTC) Received: by vmta04.bebo.com id h5r8kk0c8b08 for ; Mon, 21 Dec 2009 01:07:05 +0000 (envelope-from ) From: Bebo Service Sender: service@noreply.bebo.com To: Vampier Faethor Message-ID: <1017005538.1362211261357626361.JavaMail.resin@bebo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Date: Mon, 21 Dec 2009 01:37:16 +0000 (UTC) Subject: Important: Please verify your email address X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Dec 2009 01:37:16 -0000 IMPORTANT: Please click on the link below to verify your email address: http://www.bebo.com/T/4.fd8A5eFdS2a5uUtjTj5uEg/verify/10240484795a865203806 If you did not enter your email address and are not a member of Bebo please click below: http://www.bebo.com/T/4.fd8A5eFdS2a5uUtjTj5uEg/notmine/10240484795a865203806 ...................................................................... Please do not reply directly to this email. Questions? Contact us - http://www.bebo.com/T/4.fd8A5eFdS2a5uUtjTj5uEg/contactus Bebo, Inc., 795 Folsom St, #250, San Francisco, CA 94107, USA. From owner-freebsd-mobile@FreeBSD.ORG Mon Dec 21 15:34:57 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 28AF5106566C; Mon, 21 Dec 2009 15:34:57 +0000 (UTC) (envelope-from frank@exit.com) Received: from tinker.exit.com (tinker.exit.com [IPv6:2001:470:80f4:0:2e0:81ff:fe2b:acbc]) by mx1.freebsd.org (Postfix) with ESMTP id E5E518FC16; Mon, 21 Dec 2009 15:34:56 +0000 (UTC) Received: from jill.exit.com (jill.exit.com [IPv6:2001:470:80f4:0:2e0:81ff:fe33:7e9a]) by tinker.exit.com (8.14.3/8.14.3) with ESMTP id nBLFYtbB011009; Mon, 21 Dec 2009 07:34:55 -0800 (PST) (envelope-from frank@exit.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=exit.com; s=tinker; t=1261409695; bh=2JPkR3dRSJcKi3cyJlPj9LkhfcUpqDcHjilRtvIlAyE=; h=Subject:From:Reply-To:To:Cc:Content-Type: Content-Transfer-Encoding:Date:Message-Id:Mime-Version; b=lEOa69+p b6LE6AirDVP1GpqpV6ckD8s3/a1+LV6XXZx29YYsA4M7yX5j/7gwi6JsIKKHln7Ws2U ypApgCwkZ7D6jfwkOAppHjg7fQ8UciENq/jPZLx698kLCuJyP3XkGRq7RwA07nfsstF 308RV9JtLDQeAx9v102+gBRvh7KWI= Received: from jill.exit.com (localhost [127.0.0.1]) by jill.exit.com (8.14.3/8.14.2) with ESMTP id nBLFYtqf072238; Mon, 21 Dec 2009 07:34:55 -0800 (PST) (envelope-from frank@exit.com) Received: (from frank@localhost) by jill.exit.com (8.14.3/8.14.3/Submit) id nBLFYt3g072237; Mon, 21 Dec 2009 07:34:55 -0800 (PST) (envelope-from frank@exit.com) X-Authentication-Warning: jill.exit.com: frank set sender to frank@exit.com using -f From: Frank Mayhar To: freebsd-hackers Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Exit Consulting Date: Mon, 21 Dec 2009 07:34:54 -0800 Message-Id: <1261409694.72019.6.camel@jill.exit.com> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 FreeBSD GNOME Team Port Cc: freebsd-mobile Subject: Atheros AR9281 still not supported? X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: frank@exit.com List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Dec 2009 15:34:57 -0000 So I take it that the newer Atheros chipsets are still not supported in FreeBSD 8? I thought I saw a rumor a while ago that they would be but now I can't track it down and of course the BugBusting page shows this series as still unsupported. Unfortunately I'm having a problem with my formerly trusty ar5212 interface since I upgraded (hangs, can't reset, error "ath_chan_set: unable to reset channel 36 (5180 Mhz, flags 0x140), hal status 3") so I was hoping to use the builtin interface, but it appears that's out. Please correct me if I'm wrong. Thanks. -- Frank Mayhar frank@exit.com http://www.exit.com/ http://www.exit.com/blog/frank/ http://www.zazzle.com/fmayhar* From owner-freebsd-mobile@FreeBSD.ORG Tue Dec 22 17:31:34 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C1F061065693 for ; Tue, 22 Dec 2009 17:31:34 +0000 (UTC) (envelope-from frank@fstaals.net) Received: from edu-smtp-01.edutel.nl (edu-smtp-01.edutel.nl [88.159.1.221]) by mx1.freebsd.org (Postfix) with ESMTP id 81E9A8FC18 for ; Tue, 22 Dec 2009 17:31:34 +0000 (UTC) Received: from FStaals.net (unknown [88.159.208.104]) by edu-smtp-01.edutel.nl (Postfix) with ESMTP id A6D2D67A5A for ; Tue, 22 Dec 2009 18:14:43 +0100 (CET) Received: from FStaals.net (localhost.FStaals.LAN [127.0.0.1]) by filter.fstaals.local (Postfix) with ESMTP id AF98498141 for ; Tue, 22 Dec 2009 18:14:49 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on FStaals.net X-Spam-Level: X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.2.5 Received: from Rena.FStaals.LAN (localhost.FStaals.LAN [127.0.0.1]) (Authenticated sender: frank) by FStaals.net (Postfix) with ESMTPA id A87C598140 for ; Tue, 22 Dec 2009 18:14:49 +0100 (CET) Message-ID: <4B30FE4E.9050801@fstaals.net> Date: Tue, 22 Dec 2009 18:13:50 +0100 From: Frank Staals User-Agent: Thunderbird 2.0.0.23 (X11/20090928) MIME-Version: 1.0 To: freebsd-mobile@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: wpi and suspend/resume X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Dec 2009 17:31:34 -0000 Hey everyone, Is anyone running a system with a wireless card using the wpi driver that can successfully suspend/resume ? I have a Dell Latitude D630 running FreeBSD 8-STABLE on amd64, the system suspends and resumes fine ( acpiconf -s3 ). However after bringing it back up wpi0 refuses to reconnect to a network: frank@Rena# uname -a FreeBSD Rena.FStaals.LAN 8.0-STABLE FreeBSD 8.0-STABLE #0: Thu Dec 10 21:06:05 CET 2009 frank@Rena.FStaals.LAN:/home/obj/usr/src/sys/RENAKERNEL amd64 When I resume the system the following error message is printed to dmesg: Dec 18 21:34:29 Rena kernel: wpi0: fatal firmware error Dec 18 21:34:29 Rena kernel: wpi0: timeout resetting Rx ring I tried bringing the interface down and up again (ifconfig wpi0 down up ) and reassociate with wpa_cli. Unfortunately after resuming wpi simply won't reconnect again. It is very nice that my system actually successfully suspends and resumes for the rest, but without networking connectivity ( if_bge is also dead after a suspend ) uses are rather limited. So is anyone successfully resuming with a system using the wpi driver ? -- - Frankn From owner-freebsd-mobile@FreeBSD.ORG Tue Dec 22 23:21:33 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D9EBA106566C for ; Tue, 22 Dec 2009 23:21:33 +0000 (UTC) (envelope-from freebsd-mobile@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 92F3B8FC1E for ; Tue, 22 Dec 2009 23:21:33 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.50) id 1NNDvo-0000g9-DO for freebsd-mobile@freebsd.org; Wed, 23 Dec 2009 00:14:20 +0100 Received: from 200.41.broadband11.iol.cz ([90.178.41.200]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 23 Dec 2009 00:14:20 +0100 Received: from gamato by 200.41.broadband11.iol.cz with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 23 Dec 2009 00:14:20 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-mobile@freebsd.org From: martinko Date: Wed, 23 Dec 2009 00:13:56 +0100 Lines: 36 Message-ID: References: <3a142e750911222316m7b7b374ajd087fd28581a7256@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 200.41.broadband11.iol.cz User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.6) Gecko/20091220 SeaMonkey/2.0.1 In-Reply-To: <3a142e750911222316m7b7b374ajd087fd28581a7256@mail.gmail.com> Sender: news Subject: Re: iwi connect problems in 9.0-CURRENT X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Dec 2009 23:21:33 -0000 Paul B Mahol wrote: > On 11/23/09, Rui Paulo wrote: >> On 22 Nov 2009, at 23:39, michael brindle wrote: >>> >>> So, my questions are: >>> Why is txpower set to 0, what does that mean? That it can't transmit at >>> all? >> >> No, it could just be that the driver is providing wrong tx power >> information. > > No, because regdomain is not set txpower is always reported to be 0. > > iwi driver doesn't have TXPMGT cap (looks to be bug), so you can not set > txpower at all because net80211 thinks it is not supported. I can confirm that "the bug" is also in 8.0-RELEASE and that on 6.x txpower was non-zero (100 IIRC). Also, I'm seeing other issues ... 1) During boot wireless interface is too slow to associate and I'm seeing connection errors from other programs (e.g. ntpd). This was not the case with 6.x releases. 2) The following began appearing in the system log: kernel: iwi0: need multicast update callback Also wpa_supplicant(8) generates quite a lot of messages (it did none before). Some of them seems interesting while others not (to me). I hope someone will fix the issues (although they're not critical). With regards, Martin From owner-freebsd-mobile@FreeBSD.ORG Tue Dec 22 23:21:34 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5C0961065670 for ; Tue, 22 Dec 2009 23:21:34 +0000 (UTC) (envelope-from freebsd-mobile@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 167AC8FC19 for ; Tue, 22 Dec 2009 23:21:34 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.50) id 1NNDiK-0003wY-6o for freebsd-mobile@freebsd.org; Wed, 23 Dec 2009 00:00:24 +0100 Received: from 200.41.broadband11.iol.cz ([90.178.41.200]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 23 Dec 2009 00:00:24 +0100 Received: from gamato by 200.41.broadband11.iol.cz with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 23 Dec 2009 00:00:24 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-mobile@freebsd.org From: martinko Date: Tue, 22 Dec 2009 23:59:57 +0100 Lines: 73 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 200.41.broadband11.iol.cz User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.6) Gecko/20091220 SeaMonkey/2.0.1 In-Reply-To: Sender: news Subject: Re: iwi connect problems in 9.0-CURRENT X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Dec 2009 23:21:34 -0000 michael brindle wrote: > Hey all. > I recently upgraded to 9.0-CURRENT from 7.2-RELEASE, to help test and debug > it. > The only problem I've encountered so far that I've not yet been able to fix > is that I have yet to get my wireless card (Intel IPW 2200 b/g) to connect > to my wireless network (which has an Apple Airport as the wireless router). > Hallo, I've just upgraded to 8.0-release and I'm seeing some issues too. > my /etc/rc.conf file (with unrelated parts deleted): > wlans_iwi0="wlan0" > defaultroute=192.168.1.1 > ifconfig_wlan0="up" > ifconfig_wlan0="DHCP" > > my /etc/start_if.wlan0 file: > ifconfig wlan0 ssid BrinNet channel 1 authmode shared wepmode on wepkey PASS > weptxkey 1 > First, off-topic, I'm wondering why you do it as above .. ? These 2 lines are IMHO unnecessary: defaultroute=192.168.1.1 ifconfig_wlan0="up" Also, you could get rid off of /etc/start_if.wlan0 and use wpa_supplicant(8) that is very convenient and powerful. > with the license agreed to, as stated in the iwi(4) man page. > > dhclient will discover my network. However, it won't get any offers from it. > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5 > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7 > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10 > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11 > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15 > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13 > No DHCPOFFERS received. > No working leases in persistent database - sleeping > > Another thing I noticed, the output of ifconfig wlan0 > wlan0: flags=8843 metric 0 mtu 1500 > ether 00:0e:35:20:37:0a > inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11b > status: associated > ssid BrinNet channel 1 (2412 Mhz 11b) bssid 00:60:1d:f1:51:1b > country US authmode OPEN privacy ON deftxkey 1 wepkey 1:40-bit > txpower 0 bmiss 24 scanvalid 60 wme > > most importantly, the txpower being set to 0, because I cannot change it at > all, or even reconfirm that it's at 0: > younata# ifconfig wlan0 txpower 1 > ifconfig: SIOCS80211: Operation not supported > younata# ifconfig wlan0 txpower 0 > ifconfig: SIOCS80211: Operation not supported > > So, my questions are: > Why is txpower set to 0, what does that mean? That it can't transmit at all? > Why can I not manually change it? > Which leads to the ultimate question of: > How do I get it to connect? > The same here -- txpower is zero while it used to be non-zero before (on 6.x). Seems like a bug or something. Regards, Martin From owner-freebsd-mobile@FreeBSD.ORG Wed Dec 23 10:50:47 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 69AEA106568D for ; Wed, 23 Dec 2009 10:50:47 +0000 (UTC) (envelope-from lars.engels@0x20.net) Received: from mail.0x20.net (mail.0x20.net [217.69.67.217]) by mx1.freebsd.org (Postfix) with ESMTP id 299E78FC13 for ; Wed, 23 Dec 2009 10:50:47 +0000 (UTC) Received: from mail.0x20.net (mail.0x20.net [217.69.67.217]) by mail.0x20.net (Postfix) with ESMTP id 2AED8398B1; Wed, 23 Dec 2009 11:50:46 +0100 (CET) Received: from i011-63.fin-nrw.de (i011-63.fin-nrw.de [193.109.238.130]) by 0x20.net (Horde MIME library) with HTTP; Wed, 23 Dec 2009 11:50:46 +0100 Message-ID: <20091223115046.cs98224exsgw00ok@0x20.net> X-Priority: 3 (Normal) Date: Wed, 23 Dec 2009 11:50:46 +0100 From: Lars Engels To: Frank Staals References: <4B30FE4E.9050801@fstaals.net> In-Reply-To: <4B30FE4E.9050801@fstaals.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=_qddbuao45q8"; protocol="application/pgp-signature"; micalg="pgp-sha1" Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.1.3) Cc: freebsd-mobile@freebsd.org Subject: Re: wpi and suspend/resume X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Dec 2009 10:50:47 -0000 This message is in MIME format and has been PGP signed. --=_qddbuao45q8 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoting Frank Staals : > Hey everyone, > > Is anyone running a system with a wireless card using the wpi driver > that can successfully suspend/resume ? I have a Dell Latitude D630 > running FreeBSD 8-STABLE on amd64, the system suspends and resumes fine > ( acpiconf -s3 ). However after bringing it back up wpi0 refuses to > reconnect to a network: > > frank@Rena# uname -a > FreeBSD Rena.FStaals.LAN 8.0-STABLE FreeBSD 8.0-STABLE #0: Thu Dec 10 > 21:06:05 CET 2009 > frank@Rena.FStaals.LAN:/home/obj/usr/src/sys/RENAKERNEL amd64 > > When I resume the system the following error message is printed to dmesg: > > Dec 18 21:34:29 Rena kernel: wpi0: fatal firmware error > Dec 18 21:34:29 Rena kernel: wpi0: timeout resetting Rx ring > > I tried bringing the interface down and up again (ifconfig wpi0 down up > ) and reassociate with wpa_cli. Unfortunately after resuming wpi simply > won't reconnect again. It is very nice that my system actually > successfully suspends and resumes for the rest, but without networking > connectivity ( if_bge is also dead after a suspend ) uses are rather > limited. So is anyone successfully resuming with a system using the wpi > driver ? > > You could try to unload the module before you go to standby and reload =20 it after resuming. --=_qddbuao45q8 Content-Type: application/pgp-signature Content-Description: PGP Digital Signature Content-Disposition: inline Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEABECAAYFAksx9gYACgkQKc512sD3afhXcgCgjbWkoswhsOuHmSys3eQMojnW CgoAn0elQ9DVzVRlHI2jX3bXYfU0BDac =LAM0 -----END PGP SIGNATURE----- --=_qddbuao45q8-- From owner-freebsd-mobile@FreeBSD.ORG Wed Dec 23 19:00:21 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 15B551065693 for ; Wed, 23 Dec 2009 19:00:21 +0000 (UTC) (envelope-from frank@fstaals.net) Received: from edu-smtp-01.edutel.nl (edu-smtp-01.edutel.nl [88.159.1.221]) by mx1.freebsd.org (Postfix) with ESMTP id C7A388FC16 for ; Wed, 23 Dec 2009 19:00:20 +0000 (UTC) Received: from FStaals.net (unknown [88.159.208.104]) by edu-smtp-01.edutel.nl (Postfix) with ESMTP id 28F3C175D0E; Wed, 23 Dec 2009 20:00:19 +0100 (CET) Received: from FStaals.net (localhost.FStaals.LAN [127.0.0.1]) by filter.fstaals.local (Postfix) with ESMTP id 2200298141; Wed, 23 Dec 2009 20:00:28 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on FStaals.net X-Spam-Level: X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.2.5 Received: from Rena.FStaals.LAN (localhost.FStaals.LAN [127.0.0.1]) (Authenticated sender: frank) by FStaals.net (Postfix) with ESMTPA id 501FA98140; Wed, 23 Dec 2009 20:00:27 +0100 (CET) Message-ID: <4B32688A.3030602@fstaals.net> Date: Wed, 23 Dec 2009 19:59:22 +0100 From: Frank Staals User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.5) Gecko/20091222 Thunderbird/3.0 MIME-Version: 1.0 To: Lars Engels References: <4B30FE4E.9050801@fstaals.net> <20091223115046.cs98224exsgw00ok@0x20.net> In-Reply-To: <20091223115046.cs98224exsgw00ok@0x20.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-mobile@freebsd.org Subject: Re: wpi and suspend/resume X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Dec 2009 19:00:21 -0000 On 12/23/09 11:50, Lars Engels wrote: > > > You could try to unload the module before you go to standby and reload > it after resuming. Ah I forgot to mention that: I actually also tried that unfortunately that resulted in wpi completely hanging my system when I try to reload it after resuming. It again gives a bunch of 'wpi0: could not lock memory' errors. Then something what I believe to be initializing/scanning? channels and then: wpi0: SKU does support 802.11a panic: ieee8021_get_ratetable: no rate table for channel: freq 0 flags 0x0 -- - Frank From owner-freebsd-mobile@FreeBSD.ORG Wed Dec 23 20:47:54 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BE819106568D for ; Wed, 23 Dec 2009 20:47:54 +0000 (UTC) (envelope-from gav@bmstu.ru) Received: from imp03.mtu.ru (imp03.mtu.ru [62.5.255.20]) by mx1.freebsd.org (Postfix) with ESMTP id 365E98FC1F for ; Wed, 23 Dec 2009 20:47:53 +0000 (UTC) Received: from imp02.mtu.ru ([62.5.255.19]) by imp03.mtu.ru with bizsmtp id Lkfk1d00d0Rt8vS01kh9nE; Wed, 23 Dec 2009 23:41:09 +0300 Received: from ss27-so01.mtu.ru ([195.34.34.249]) by imp02.mtu.ru with bizsmtp id LkbA1d00x5NWlXn01kbB7p; Wed, 23 Dec 2009 23:35:11 +0300 Received: from imp02.mtu.ru (alt-proxy-1.mtu.ru [62.5.255.74]) by ss27-so01.mtu.ru (Postfix) with ESMTP id 2509A31FDFF; Wed, 23 Dec 2009 23:35:11 +0300 (MSK) Received: from sony.bmstu.ru ([91.76.111.20]) by imp02.mtu.ru with bizsmtp id LkbA1d0190STCsj01kbA57; Wed, 23 Dec 2009 23:35:11 +0300 Date: Wed, 23 Dec 2009 23:35:11 +0300 From: Alexey To: Frank Staals Message-Id: <20091223233511.78d9dd7e.gav@bmstu.ru> In-Reply-To: <4B32688A.3030602@fstaals.net> References: <4B30FE4E.9050801@fstaals.net> <20091223115046.cs98224exsgw00ok@0x20.net> <4B32688A.3030602@fstaals.net> Organization: BMSTU X-Mailer: Sylpheed 2.7.1 (GTK+ 2.18.5; amd64-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Flag: NO X-Spam-Yversion: Spamooborona-3.0 Cc: Lars Engels , freebsd-mobile@freebsd.org Subject: Re: wpi and suspend/resume X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Dec 2009 20:47:54 -0000 Try /etc/rc.d/netif restart From owner-freebsd-mobile@FreeBSD.ORG Thu Dec 24 10:33:56 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DEB5C106566C for ; Thu, 24 Dec 2009 10:33:56 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from mail-fx0-f227.google.com (mail-fx0-f227.google.com [209.85.220.227]) by mx1.freebsd.org (Postfix) with ESMTP id 762248FC08 for ; Thu, 24 Dec 2009 10:33:56 +0000 (UTC) Received: by fxm27 with SMTP id 27so8218366fxm.3 for ; Thu, 24 Dec 2009 02:33:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=YmVFCSI6EB8heHkj6FetpRHYmvbBw4eq4/Wd4OmyIyE=; b=w7BwboCVa17oDnZjuH+TW7MWYUNAnuAgXiQWmfC/RFKe7f4EiZUxuWeL54WzXQqGGQ M03y6uee1Jm1YGDq5Py+bw97CoGyOH6tq+6+wndCrvCKl5sp6E3E+n2JuFg9k1eQ0oUY X/Vo+4v97Vvv8n/QTHibd/KmxiouqEJnWsFxQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=V2ioWQHPvWAgZOssVcEU/FVCgI9dUG3JXMYcFK6nmY4ZMVFsnVMghYLNwcaqdOdJ7Z 64i9iiKxM+dizFIsv+kI/5OiEHe300o0eV5XNSq0Yktnd7nea7iVB9yjZ07WqfNXLn/k 5+2JsKKEJNtyzKZfejGcHEmGcg90f1aN4YzIk= MIME-Version: 1.0 Received: by 10.102.211.28 with SMTP id j28mr5337292mug.125.1261650835233; Thu, 24 Dec 2009 02:33:55 -0800 (PST) In-Reply-To: <4B32688A.3030602@fstaals.net> References: <4B30FE4E.9050801@fstaals.net> <20091223115046.cs98224exsgw00ok@0x20.net> <4B32688A.3030602@fstaals.net> Date: Thu, 24 Dec 2009 11:33:55 +0100 Message-ID: <3a142e750912240233y1799ba2bw3f58d0bef74495c4@mail.gmail.com> From: Paul B Mahol To: Frank Staals Content-Type: text/plain; charset=ISO-8859-1 Cc: Lars Engels , freebsd-mobile@freebsd.org Subject: Re: wpi and suspend/resume X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Dec 2009 10:33:56 -0000 On 12/23/09, Frank Staals wrote: > On 12/23/09 11:50, Lars Engels wrote: >> >> >> You could try to unload the module before you go to standby and reload >> it after resuming. > Ah I forgot to mention that: I actually also tried that unfortunately > that resulted in wpi completely hanging my system when I try to reload > it after resuming. It again gives a bunch of 'wpi0: could not lock > memory' errors. Then something what I believe to be > initializing/scanning? channels and then: > > wpi0: SKU does support 802.11a > panic: ieee8021_get_ratetable: no rate table for channel: freq 0 flags 0x0 This is bug, it doesnt exits nicely if attach fail ... You could try, when unloading wpi module to unload another pci driver and load same one again while using hw.pci.do_power_nodriver="3" hw.pci.do_power_resume="0" in loader.conf, maybe device doesnt get to D3 state in 'right way'. -- Paul B Mahol From owner-freebsd-mobile@FreeBSD.ORG Thu Dec 24 19:38:18 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E643A1065670; Thu, 24 Dec 2009 19:38:18 +0000 (UTC) (envelope-from nate@root.org) Received: from nlpi129.prodigy.net (nlpi129.sbcis.sbc.com [207.115.36.143]) by mx1.freebsd.org (Postfix) with ESMTP id A93988FC16; Thu, 24 Dec 2009 19:38:18 +0000 (UTC) Received: from [10.0.5.41] (ppp-71-139-5-80.dsl.snfc21.pacbell.net [71.139.5.80]) (authenticated bits=0) by nlpi129.prodigy.net (8.13.8 smtpauth/dk/map_regex/8.13.8) with ESMTP id nBOJcCZq020273; Thu, 24 Dec 2009 13:38:14 -0600 Message-ID: <4B33C325.9030202@root.org> Date: Thu, 24 Dec 2009 11:38:13 -0800 From: Nate Lawson User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Ian Smith References: <20091213204201.A12012@sola.nimnet.asn.au> <4B284A1A.4090909@root.org> <20091219014856.H12012@sola.nimnet.asn.au> In-Reply-To: <20091219014856.H12012@sola.nimnet.asn.au> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: Thinkpad T23 60 second stall on resuming 8.0-RELEASE/i386 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Dec 2009 19:38:19 -0000 Ian Smith wrote: > On Tue, 15 Dec 2009, Nate Lawson wrote: > > Ian Smith wrote: > > > -wakeup from sleeping state (slept 00:00:07) > > > +t_delta 15.f9ad99f01204edd8 too short <<<<<<< > > > +t_delta 16.07bb5b66ef900000 too long <<<<<<< > > > +t_delta 15.f9ad90918acc0000 too short <<<<<<< > > > +ct_to_ts([2009-12-13 17:10:39]) = 1260724239.000000000 > > > +wakeup from sleeping state (slept 00:01:07) > > > ata0: reiniting channel .. > > > ata0: reset tp1 mask=03 ostat0=50 ostat1=00 > > > ata0: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 > > > ata0: stat1=0x00 err=0x01 lsb=0x00 msb=0x00 > > > -ata0: reset tp2 stat0=50 stat1=00 devices=0x1 > > > +ata0: reset tp2 stat0=50 stat1=00 devices=0x1 > > > ad0: setting PIO4 on ICH3 chip > > > ad0: setting UDMA100 on ICH3 chip > > > ata0: reinit done .. > > > @@ -36,7 +37,7 @@ > > > ata1: reset tp1 mask=03 ostat0=00 ostat1=00 > > > ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb > > > ata1: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 > > > -ata1: reset tp2 stat0=00 stat1=00 devices=0x4 > > > +ata1: reset tp2 stat0=00 stat1=00 devices=0x10000 > > > > I think it's ATA timing out for some reason. > > Thanks Nate. I nearly clipped that part of the diff, figuring only the > <*_MASTER> messages had changed, but I now see ata1 devices differ too. > > Have similar regressions re ATA been turning up elsewere, do you know? > > I've been digging, still on the trail of those t_delta messages, but now > figure these might be spurious, some timecounter missing/gaining a tick > or something, if ATA is maybe what's hanging meanwhile? > > There's no HD light activity at all from resume button/switch through > that 60 second wait, when 15? seconds after the third t_delta line is > written to console, the HD light flashes while apparently simultaneously > writing the rest of the resume messages, and it comes alive. > > Guess I should next upgrade the 7.0-R slice to 7.2-STABLE to find out if > this problem has been mfc'd :) I'd try to revert or move ATA forward some to see if that fixes things. Usually that can be done without too many other changes to the kernel. -- Nate From owner-freebsd-mobile@FreeBSD.ORG Fri Dec 25 19:31:35 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D1223106566B for ; Fri, 25 Dec 2009 19:31:35 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id A97AB8FC08 for ; Fri, 25 Dec 2009 19:31:35 +0000 (UTC) Received: from ice.local ([10.0.0.115]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id nBPJVV4F024134 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Dec 2009 11:31:31 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <4B351313.4000506@errno.com> Date: Fri, 25 Dec 2009 11:31:31 -0800 From: Sam Leffler User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Frank Staals References: <4B30FE4E.9050801@fstaals.net> <20091223115046.cs98224exsgw00ok@0x20.net> <4B32688A.3030602@fstaals.net> In-Reply-To: <4B32688A.3030602@fstaals.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC-sonic.net-Metrics: ebb.errno.com; whitelist Cc: Lars Engels , freebsd-mobile@freebsd.org Subject: Re: wpi and suspend/resume X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Dec 2009 19:31:35 -0000 Frank Staals wrote: > On 12/23/09 11:50, Lars Engels wrote: >> >> >> You could try to unload the module before you go to standby and reload >> it after resuming. > Ah I forgot to mention that: I actually also tried that unfortunately > that resulted in wpi completely hanging my system when I try to reload > it after resuming. It again gives a bunch of 'wpi0: could not lock > memory' errors. Then something what I believe to be > initializing/scanning? channels and then: > > wpi0: SKU does support 802.11a > panic: ieee8021_get_ratetable: no rate table for channel: freq 0 flags 0x0 > > > This sounds like wpi didn't read data properly from the eeprom on resume. The panic is because no channels were registered by the driver. There look to be debug msgs in the driver that can help track that issue down. Sam From owner-freebsd-mobile@FreeBSD.ORG Sat Dec 26 09:28:38 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 320B9106568B for ; Sat, 26 Dec 2009 09:28:38 +0000 (UTC) (envelope-from reminder+freebsd-mobile=freebsd.org@grouply.com) Received: from mail2.grouply.com (mail2.grouply.com [72.20.121.14]) by mx1.freebsd.org (Postfix) with ESMTP id 0FA738FC0A for ; Sat, 26 Dec 2009 09:28:37 +0000 (UTC) Received: from localhost.localdomain (mail1.grouply.com [10.3.0.1]) by mail2.grouply.com (Postfix) with ESMTP id DFEC416C625 for ; Sat, 26 Dec 2009 01:01:50 -0800 (PST) Received: from dkim0.grouply.com (localhost.localdomain [127.0.0.1]) by dkim0.grouply.com (Postfix) with ESMTP id 7BF15E001A; Sat, 26 Dec 2009 01:05:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=grouply.com; s=ca; h=date:to:from :subject:message-id:mime-version:content-type; bh=6U6uBjbwB+RRSeojA0e2oW UegpQ=; b=DzD4tuR61Up/UGksZx5g9EETWw2RkMPqU3MgapmtzezoyGc50L/+bWYgrME0M5 fPYh6wRNwqfGvuswn3sVlXLUFLOCMZqW7uharP2cKptMyD85dB2xMgHLYkjD9qjvFEm2JuhI 79fGv/xjhO2fzU37YrsfhGx7F2eixOD+rdHeo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=grouply.com; q=dns; s=ca; h=date:to:from :subject:message-id:mime-version:content-type; b=j2mI9RUvkspzYQ3EKWAP3UJ doPlaQRcXtcjjD+LDL6PDm9t9BcHUQUaT5LR+Uvsxpm6I7EtdikKczC2XrCi9MK4AyD1WVvb 1ts90PPSZR2aEJQIN0lBv8sbyj71/oPWcXLCAfJQmXMVlJIgw/0ZMWKgQRy8Pw913DDnd/ZN JqJM= Received: from localhost.localdomain (bg13.grouply.com [10.9.0.13]) by dkim0.grouply.com (Postfix) with ESMTP id 4F2CEF68044; Sat, 26 Dec 2009 01:05:57 -0800 (PST) Date: Sat, 26 Dec 2009 00:59:40 -0800 To: freebsd-mobile@freebsd.org From: Grouply Message-ID: X-Priority: 3 X-Mailer: PHPMailer [version 1.72] X-Grouply-Class: viral MIME-Version: 1.0 Content-Type: text/plain; charset = "ISO-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Your invitation from Mohd Zulfadzly Mohd Tumari is about to expire X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Dec 2009 09:28:38 -0000 On December 22, Mohd Zulfadzly Mohd Tumari sent you an invitation to join Grouply so you can see their profile, friends, and list of groups. On Saturday (January 2), this invitation will expire. Follow this link t= o accept Mohd Zulfadzly Mohd Tumari's invitation. http://www.grouply.com/register?rem=3D95690468 Signing up is free and takes less than a minute. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Block Grouply Invites | Mark as SPAM =20 This reminder email is sent by an automatic process triggered by system maintenance. This is the only email message you will receive from Grouply= about the expiration of this invitation from Mohd Zulfadzly Mohd Tumari. To blo= ck all emails from Grouply, click here or send an email to blocklist@grouply.c= om with subject "unsubscribe-eV1DthQ%2FlCLCX4NumgWbxqTgHOd2uNCL%2B6o%3D". =20 Grouply, 495 Seaport Court, Suite 103, Redwood City, CA 94063 =20 From owner-freebsd-mobile@FreeBSD.ORG Sat Dec 26 11:13:36 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2E639106566C for ; Sat, 26 Dec 2009 11:13:36 +0000 (UTC) (envelope-from frank@fstaals.net) Received: from edu-smtp-02.edutel.nl (edu-smtp-02.edutel.nl [88.159.1.222]) by mx1.freebsd.org (Postfix) with ESMTP id DEE038FC12 for ; Sat, 26 Dec 2009 11:13:35 +0000 (UTC) Received: from FStaals.net (unknown [88.159.208.104]) by edu-smtp-02.edutel.nl (Postfix) with ESMTP id 0F5CD121C77; Sat, 26 Dec 2009 12:13:34 +0100 (CET) Received: from FStaals.net (localhost.FStaals.LAN [127.0.0.1]) by filter.fstaals.local (Postfix) with ESMTP id 5321198141; Sat, 26 Dec 2009 12:13:31 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on FStaals.net X-Spam-Level: X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.2.5 Received: from Rena.FStaals.LAN (localhost.FStaals.LAN [127.0.0.1]) (Authenticated sender: frank) by FStaals.net (Postfix) with ESMTPA id 3645998140; Sat, 26 Dec 2009 12:13:28 +0100 (CET) Message-ID: <4B35EF8D.5040603@fstaals.net> Date: Sat, 26 Dec 2009 12:12:13 +0100 From: Frank Staals User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.5) Gecko/20091222 Thunderbird/3.0 MIME-Version: 1.0 To: Paul B Mahol References: <4B30FE4E.9050801@fstaals.net> <20091223115046.cs98224exsgw00ok@0x20.net> <4B32688A.3030602@fstaals.net> <3a142e750912240233y1799ba2bw3f58d0bef74495c4@mail.gmail.com> In-Reply-To: <3a142e750912240233y1799ba2bw3f58d0bef74495c4@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Lars Engels , freebsd-mobile@freebsd.org Subject: Re: wpi and suspend/resume X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Dec 2009 11:13:36 -0000 On 12/24/09 11:33, Paul B Mahol wrote: > > This is bug, it doesnt exits nicely if attach fail ... > > You could try, when unloading wpi module to unload another pci driver and load > same one again while using > > hw.pci.do_power_nodriver="3" > hw.pci.do_power_resume="0" > > in loader.conf, maybe device doesnt get to D3 state in 'right way'. > I'm not sure I understand what you meant by that. First I added the both hw.pci lines to /boot/loader.conf and rebooted. Then I tried the following two scenarios: 1: kldunload if_wpi 2: kldunload snd_hda 3: acpiconf -s3 4: resume 5: kldload snd_hda 6: kldload if_wpi However when I load if_wpi in step 6 it will not recognize the hardware. The other scenario: 1: kldunload if_wpi 2: kldunload snd_hda 3: kldload snd_hda 4: acpiconf -s3 5: kldload if_wpi This scenario again results in a panic when loading if_wpi in step 5. When loading if_wpi again the following message popped up in particular: wpi0: chip is in D3 power mode -- setting to d0 Allthough when I checked the second scenario again without the hw.pci lines in /boot/loader.conf the this message also appears when re-enabling wpi. Is one of these scenarios what you had in mind ? Or can/should I try something else ? Thanks for the help so far -- - Frank From owner-freebsd-mobile@FreeBSD.ORG Sat Dec 26 15:56:55 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7626D106566B for ; Sat, 26 Dec 2009 15:56:55 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from mail-ew0-f226.google.com (mail-ew0-f226.google.com [209.85.219.226]) by mx1.freebsd.org (Postfix) with ESMTP id 095A28FC16 for ; Sat, 26 Dec 2009 15:56:54 +0000 (UTC) Received: by ewy26 with SMTP id 26so6140346ewy.3 for ; Sat, 26 Dec 2009 07:56:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=NbFMn0t/gBx15Gehj/iJM/qKANd0YmKOePj85/XGF9A=; b=JZRPZyXGhkMCkp1n8uMYt0Zkoicm8ynMw7gUQ2hdQ2Ax0j2r/POYarXw7xzHvXELa7 sVCaLUeaG/rncMN/taH0vNVvr6yw4UJ5w/2QCJBkoytgy6sPOt34k/fagpRIFDCs/1fK L8AuGNE3xC0aaD/6Tf0lkZPklqV+MLEZTwuXY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=URGGARbm0r8tkrU8Zs4EhFpk+hxBmu0TjNMnj0q2k1Qh9GBO2F8uN4eNAsmjgp+wS4 sBMnmU2EWqJ53+fcEmWnlfZS7BeBRceTARy+OxHfmmcfdJZgl4Xhv7vN29Cq+t/U8c49 TDkRQNYlRflFUtKpWcnu5LR/LJFgXApvuezJo= MIME-Version: 1.0 Received: by 10.213.99.212 with SMTP id v20mr12362595ebn.7.1261843013924; Sat, 26 Dec 2009 07:56:53 -0800 (PST) In-Reply-To: <4B35EF8D.5040603@fstaals.net> References: <4B30FE4E.9050801@fstaals.net> <20091223115046.cs98224exsgw00ok@0x20.net> <4B32688A.3030602@fstaals.net> <3a142e750912240233y1799ba2bw3f58d0bef74495c4@mail.gmail.com> <4B35EF8D.5040603@fstaals.net> Date: Sat, 26 Dec 2009 16:56:53 +0100 Message-ID: <3a142e750912260756g76befe61v6847736e6d30b4df@mail.gmail.com> From: Paul B Mahol To: Frank Staals Content-Type: text/plain; charset=ISO-8859-1 Cc: Lars Engels , freebsd-mobile@freebsd.org Subject: Re: wpi and suspend/resume X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Dec 2009 15:56:55 -0000 On 12/26/09, Frank Staals wrote: > On 12/24/09 11:33, Paul B Mahol wrote: >> >> This is bug, it doesnt exits nicely if attach fail ... >> >> You could try, when unloading wpi module to unload another pci driver and >> load >> same one again while using >> >> hw.pci.do_power_nodriver="3" >> hw.pci.do_power_resume="0" >> >> in loader.conf, maybe device doesnt get to D3 state in 'right way'. >> > I'm not sure I understand what you meant by that. First I added the > both hw.pci lines to /boot/loader.conf and rebooted. Then I tried the > following two scenarios: > > 1: kldunload if_wpi > 2: kldunload snd_hda > 3: acpiconf -s3 > 4: resume > 5: kldload snd_hda > 6: kldload if_wpi > > However when I load if_wpi in step 6 it will not recognize the hardware. > > The other scenario: > > 1: kldunload if_wpi > 2: kldunload snd_hda > 3: kldload snd_hda > 4: acpiconf -s3 > 5: kldload if_wpi > > This scenario again results in a panic when loading if_wpi in step 5. > When loading if_wpi again the following message popped up in particular: > > wpi0: chip is in D3 power mode -- setting to d0 > > Allthough when I checked the second scenario again without the hw.pci > lines in /boot/loader.conf the this message also appears when > re-enabling wpi. > > Is one of these scenarios what you had in mind ? Or can/should I try > something else ? I'm out of ideas :( -- Paul B Mahol