From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Special keys not working after installing newest kernel
Date: Fri, 4 Apr 2014 08:47:46 -0700 [thread overview]
Message-ID: <20140404154746.GB13419@kroah.com> (raw)
In-Reply-To: <533E7EDD.3060608@gmail.com>
On Fri, Apr 04, 2014 at 11:43:57AM +0200, Riemer van der Zee wrote:
> Hello all,
>
> I always build a custom kernel from torvalds/linux.git as a training
> exercise, however since today a few of the special keys are not working.
> (As in/de-creasing and muting sound). I get the following errors after
> pressing one of these buttons:
>
> [ 47.976253] ACPI: \_SB_.ATKD: Unsupported event type 0x32
> [ 50.846828] ACPI: \_SB_.ATKD: Unsupported event type 0x31
> [ 51.209026] ACPI: \_SB_.ATKD: Unsupported event type 0x30
>
>
> I also find the following messages worrying:
>
> [ 1.290958] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042f conflicts with OpRegion 0x0000000000000400-0x000000000000047f (\PMIO) (20140214/utaddress-258)
> [ 1.290968] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
> [ 1.290974] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054f conflicts with OpRegion 0x0000000000000500-0x0000000000000549 (\SBGP) (20140214/utaddress-258)
> [ 1.290981] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20140214/utaddress-258)
> [ 1.290988] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
> [ 1.290992] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053f conflicts with OpRegion 0x0000000000000500-0x0000000000000549 (\SBGP) (20140214/utaddress-258)
> [ 1.290997] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20140214/utaddress-258)
> [ 1.291001] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
> [ 1.291003] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052f conflicts with OpRegion 0x0000000000000500-0x0000000000000549 (\SBGP) (20140214/utaddress-258)
> [ 1.291008] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20140214/utaddress-258)
> [ 1.291013] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
>
>
> The laptop is an Asus n61j and a version where the keys did work is:
> 01d5f3b598b18a5035426c30801adf65822dbd0c
>
> my .config : http://pastebin.com/cwar1Hk7
> the whole dmesg : http://pastebin.com/9jmhLskD
>
>
> Any pointers in how to fix this or if you require any more information
> I'm glad to listen/supply. Are there any recent commits to the ACPI
> system I can take a look at?
Can you run 'git bisect' to track down the patch that broke this for
you? After doing that, please email the developers who wrote the patch
and their mailing list (found using get_maintainer.pl) and they will
work to resolve the issue.
thanks,
greg k-h
prev parent reply other threads:[~2014-04-04 15:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 9:43 Special keys not working after installing newest kernel Riemer van der Zee
2014-04-04 15:47 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140404154746.GB13419@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).