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