From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755388Ab3ANCss (ORCPT ); Sun, 13 Jan 2013 21:48:48 -0500 Received: from smtp.nue.novell.com ([195.135.221.5]:48823 "EHLO smtp.nue.novell.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753305Ab3ANCsr (ORCPT ); Sun, 13 Jan 2013 21:48:47 -0500 Subject: Re: rf kill button not working on hp folio 9470m - bisected From: joeyli To: Fabio Coatti Cc: linux-kernel@vger.kernel.org, Bob Moore , Greg Kroah-Hartman , Feng Tang , Len Brown , MaChen@suse.com In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Date: Mon, 14 Jan 2013 10:45:27 +0800 Message-ID: <1358131527.6113.428.camel@linux-s257.site> Mime-Version: 1.0 X-Mailer: Evolution 2.28.2 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Fabio, 於 日，2013-01-13 於 23:11 +0100，Fabio Coatti 提到： > Hi all, > on my laptop (hp folio 9470m), the rfkill button works fine on 3.6.10 Does rfkill button means Fn+F12 key on your machine? > and 11 (don't know about older kernels), but is not working on 3.7.X > (latest tested is 3.7.2). > On non working kernel, log shows the following messages: > > Jan 13 17:34:33 calvin kernel: atkbd serio0: Unknown key pressed > (translated set 2, code 0xf8 on isa0060/serio0). > Jan 13 17:34:33 calvin kernel: atkbd serio0: Use 'setkeycodes e078 > ' to make it known. Looks your machine emit e078 code when it switch to Windows 8 code path. Please tail your log and press Fn key for make sure it emit e078 code. I didn't see e078 code in hewlett-packard keymap file in udev, currently it define 0xD7 to be the wlan key. > Jan 13 17:34:33 calvin kernel: atkbd serio0: Unknown key released > (translated set 2, code 0xf8 on isa0060/serio0). > Jan 13 17:34:33 calvin kernel: atkbd serio0: Use 'setkeycodes e078 > ' to make it known. > Jan 13 17:34:34 calvin kernel: atkbd serio0: Unknown key pressed > (translated set 2, code 0xf8 on isa0060/serio0). > Jan 13 17:34:34 calvin kernel: atkbd serio0: Use 'setkeycodes e078 > ' to make it known. > Jan 13 17:34:35 calvin kernel: atkbd serio0: Unknown key released > (translated set 2, code 0xf8 on isa0060/serio0). > Jan 13 17:34:35 calvin kernel: atkbd serio0: Use 'setkeycodes e078 > ' to make it known. > > On working kernels, same logs shows the following lines: > > Jan 13 22:55:59 calvin kernel: atkbd serio0: Unknown key pressed > (translated set 2, code 0xf8 on isa0060/serio0). > Jan 13 22:55:59 calvin kernel: atkbd serio0: Use 'setkeycodes e078 > ' to make it known. > Jan 13 22:55:59 calvin NetworkManager[4823]: WiFi now enabled > by radio killswitch > Jan 13 22:55:59 calvin NetworkManager[4823]: (wlan0): bringing up device. > Jan 13 22:55:59 calvin kernel: iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S > Jan 13 22:55:59 calvin kernel: iwlwifi 0000:03:00.0: Radio type=0x2-0x1-0x0 > Jan 13 22:55:59 calvin kernel: atkbd serio0: Unknown key released > (translated set 2, code 0xf8 on isa0060/serio0). hmm... this machine changed wlan0 status on working kernel and also emit e078 code like on Windows 8 mode. Then I think your machine control RF power by different way but BIOS, maybe wmi or other ways. Please attached on your DSDT, hope OEM do those things through ACPI. > Jan 13 22:55:59 calvin kernel: atkbd serio0: Use 'setkeycodes e078 > ' to make it known. > > I've tried to bisect the regression, and I've got this: > > a57f7f9175b8ccbc9df83ac13860488913115de4 is the first bad commit > commit a57f7f9175b8ccbc9df83ac13860488913115de4 > Author: Bob Moore > Date: Fri Aug 17 10:55:02 2012 +0800 > > ACPICA: Add Windows8/Server2012 string for _OSI method. > This change adds a new _OSI string, "Windows 2012" for both Windows 8 > and Windows Server 2012. > >From Microsoft document "How to Identify the Windows Version in ACPI > by Using _OSI", July 13, 2012. > > Signed-off-by: Bob Moore > Signed-off-by: Feng Tang > Signed-off-by: Len Brown > > :040000 040000 55311ce2f9fed66501b06f93f67fa99b54d46e86 > 998889c21c3b68f8072ad131b643c592a4cbe423 M drivers > > I've reverted this commit in 3.7.2 and now the rfkill button is > working just fine, so it seems the real culprit (well, I have no > knowledge about acpi so I say so only because reverting it fixes the > issue) > Please forgive me If I'm completely wrong :) > > -- > Fabio Please try acpi_osi="!Windows 2012", it will switch back to Windows 2009 mode. Then look at does things better than before? Thanks a lot! Joey Lee