From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Mario 'BitKoenig' Holbe" Subject: Re: [PATCH 0/8] [Resend] ideapad: using EC command to control rf/camera power Date: Wed, 1 Sep 2010 21:56:17 +0200 Message-ID: <20100901195617.GD32589@darkside.kls.lan> References: <1282120564-11324-1-git-send-email-ike.pan@canonical.com> <1282127719.2747.211.camel@localhost> <20100818155128.GA24363@darkside.kls.lan> <4C6CA31D.6030407@canonical.com> <20100819193146.GB32665@darkside.kls.lan> <4C6E2833.6080407@canonical.com> <20100820090824.GA23186@darkside.kls.lan> <4C7505A2.3000402@canonical.com> <20100830181954.GE31068@darkside.kls.lan> <4C7E3DE0.7030209@canonical.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2JFBq9zoW8cOFH7v" Return-path: Received: from piggy.rz.tu-ilmenau.de ([141.24.4.8]:35745 "EHLO piggy.rz.tu-ilmenau.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752841Ab0IAT5z (ORCPT ); Wed, 1 Sep 2010 15:57:55 -0400 Content-Disposition: inline In-Reply-To: <4C7E3DE0.7030209@canonical.com> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Ike Panhc Cc: David Woodhouse , "platform-driver-x86@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-acpi@vger.kernel.org" , Thomas Renninger , Alan Cox , Andrew Morton , Corentin Chary , Randy Dunlap , "Brown, Len" , Matthew Garrett --2JFBq9zoW8cOFH7v Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 01, 2010 at 07:49:52PM +0800, Ike Panhc wrote: > Your log tells a lot. It tells me if the bluetooth init failed. Then we > have to turning off and power on again by hw switch to make it alive agai= n. >=20 > So, I believe we have two issue here. > * when rfkill unblock, sometimes bluetooth init failed. Yes. > * power up system after rfkill block bluetooth, sometimes the cfgbit =3D = 0xc0000 > Am I correct? Not completely. * reboot system after rfkill block bluetooth, sometimes the cfgbit =3D 0xc0= 000 I never had cfgbit =3D 0xc0000 when I power-cycled the system, only when I rebooted it. This is why I belive the second point has virtually the same reason as the first point: bluetooth device initialization fails and thus its detection by BIOS fails and thus ACPI returns 0xc0000 cfg. Hence, I belive chances are high that solving the first point does also solve the second. While thinking about it... the init problems persisting a reboot could also mean that not the unblock operation is the real issue but the block operation - which probably leaves the bluetooth device in kind of a semi-disabled state or something like that. regards Mario --=20 Do I contradict myself? Very well, then I contradict myself, I am large, I contain multitudes. -- Walt Whitman --2JFBq9zoW8cOFH7v Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEVAwUBTH6v4RS+e2HeSPbpAQJcIgf9Fb9gg0wHorstDFb2khVF9kDP0CKfv8JJ 7AY+qGgz0Mk3TJhAb0p6mCb3YqUIWxnWfILGmamgyLOvTy/4l0BA7JH4FJxv6VK1 9gBMtPSU8DL7VlsKCv+8TwDbEyCtyIjTf1KpBOBF4AY1ojpAQVhTbh6TqsKYuWXn qk/hopjtY5t1Y3ipcWsGrDdJMw9zgHHMh0KfUjQpWR3USDVi3wXYSieWPCOpy95f iC/ja+9w/CGnQGyM+ZL3K60sgm1uoWl77Ti4g3eTkiK0XojmX6a0qjg/cs1kP4/L oBJkhFcZgmI63UCufVFvozbJhl/RpYFkmrmqNsFHR5g4Z4PAAQcusw== =sdGT -----END PGP SIGNATURE----- --2JFBq9zoW8cOFH7v--