From: Alexey Starikovskiy <astarikovskiy@suse.de>
To: Guillaume Chazarain <guichaz@gmail.com>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
lenb@kernel.org, Tim Elliott <tle@holymonkey.com>
Subject: Re: ACPI regression in 2.6.25-rc6 (function keys stop working)
Date: Wed, 19 Mar 2008 02:40:19 +0300 [thread overview]
Message-ID: <47E052E3.4000107@suse.de> (raw)
In-Reply-To: <3d8471ca0803181629h63530825k6087b2a838484dca@mail.gmail.com>
Hi Guillaume,
Thanks for tests, it looks like call_psw_on_capable_devices.patch does not
help at all, and we should just revert the offending patch.
Sorry for the toruble,
Alex.
Guillaume Chazarain wrote:
> Hi Alexey,
>
> Thanks for your assistance. Here are the results of various tests:
>
> === vanilla:
> CPU0
> 0: 14637 IO-APIC-edge timer
> 1: 213 IO-APIC-edge i8042
> 3: 2 IO-APIC-edge
> 8: 1 IO-APIC-edge rtc
> 9: 318 IO-APIC-fasteoi acpi
> 12: 3534 IO-APIC-edge i8042
> 14: 12481 IO-APIC-edge ata_piix
> 15: 0 IO-APIC-edge ata_piix
> 16: 14609 IO-APIC-fasteoi uhci_hcd:usb5, firewire_ohci,
> radeon@pci:0000:01:00.0
> 17: 5681 IO-APIC-fasteoi yenta, ipw2200, Intel ICH6
> 18: 0 IO-APIC-fasteoi uhci_hcd:usb4, sdhc0:slot0, eth0
> 19: 0 IO-APIC-fasteoi uhci_hcd:usb3
> 20: 0 IO-APIC-fasteoi Intel ICH6 Modem
> 23: 4 IO-APIC-fasteoi ehci_hcd:usb1, uhci_hcd:usb2
> NMI: 0 Non-maskable interrupts
> LOC: 22742 Local timer interrupts
> TRM: 0 Thermal event interrupts
> SPU: 0 Spurious interrupts
> ERR: 0
> MIS: 0
>
> ACPI keys don't work at all
>
> === 2c81ce4c9c3 reverted:
>
> CPU0
> 0: 13379 IO-APIC-edge timer
> 1: 205 IO-APIC-edge i8042
> 3: 2 IO-APIC-edge
> 8: 1 IO-APIC-edge rtc
> 9: 3599 IO-APIC-fasteoi acpi
> 12: 3654 IO-APIC-edge i8042
> 14: 13034 IO-APIC-edge ata_piix
> 15: 0 IO-APIC-edge ata_piix
> 16: 14073 IO-APIC-fasteoi uhci_hcd:usb5, firewire_ohci,
> radeon@pci:0000:01:00.0
> 17: 7855 IO-APIC-fasteoi yenta, ipw2200, Intel ICH6
> 18: 0 IO-APIC-fasteoi uhci_hcd:usb4, eth0, sdhc0:slot0
> 19: 0 IO-APIC-fasteoi uhci_hcd:usb3
> 20: 0 IO-APIC-fasteoi Intel ICH6 Modem
> 23: 4 IO-APIC-fasteoi ehci_hcd:usb1, uhci_hcd:usb2
> NMI: 0 Non-maskable interrupts
> LOC: 22153 Local timer interrupts
> TRM: 0 Thermal event interrupts
> SPU: 0 Spurious interrupts
> ERR: 0
> MIS: 0
>
> ACPI keys work fine.
>
> === 2c81ce4c9c3 reverted + call_psw_on_capable_devices.patch
>
> CPU0
> 0: 12372 IO-APIC-edge timer
> 1: 195 IO-APIC-edge i8042
> 3: 2 IO-APIC-edge
> 8: 1 IO-APIC-edge rtc
> 9: 7976 IO-APIC-fasteoi acpi
> 12: 1824 IO-APIC-edge i8042
> 14: 12168 IO-APIC-edge ata_piix
> 15: 0 IO-APIC-edge ata_piix
> 16: 11829 IO-APIC-fasteoi uhci_hcd:usb5, firewire_ohci,
> radeon@pci:0000:01:00.0
> 17: 4803 IO-APIC-fasteoi yenta, ipw2200, Intel ICH6
> 18: 0 IO-APIC-fasteoi uhci_hcd:usb4, sdhc0:slot0, eth0
> 19: 0 IO-APIC-fasteoi uhci_hcd:usb3
> 20: 0 IO-APIC-fasteoi Intel ICH6 Modem
> 23: 58 IO-APIC-fasteoi ehci_hcd:usb1, uhci_hcd:usb2
> NMI: 0 Non-maskable interrupts
> LOC: 21962 Local timer interrupts
> TRM: 0 Thermal event interrupts
> SPU: 0 Spurious interrupts
> ERR: 0
> MIS: 0
>
> ACPI keys work fine.
>
> === dont_disable_ec_gpe_completely_at_storm.patch
>
> CPU0
> 0: 19657 IO-APIC-edge timer
> 1: 434 IO-APIC-edge i8042
> 3: 2 IO-APIC-edge
> 8: 1 IO-APIC-edge rtc
> 9: 3310 IO-APIC-fasteoi acpi
> 12: 7224 IO-APIC-edge i8042
> 14: 13055 IO-APIC-edge ata_piix
> 15: 0 IO-APIC-edge ata_piix
> 16: 18637 IO-APIC-fasteoi uhci_hcd:usb5, firewire_ohci,
> radeon@pci:0000:01:00.0
> 17: 7281 IO-APIC-fasteoi yenta, ipw2200, Intel ICH6
> 18: 0 IO-APIC-fasteoi uhci_hcd:usb4, eth0, sdhc0:slot0
> 19: 0 IO-APIC-fasteoi uhci_hcd:usb3
> 20: 0 IO-APIC-fasteoi Intel ICH6 Modem
> 23: 4 IO-APIC-fasteoi ehci_hcd:usb1, uhci_hcd:usb2
> NMI: 0 Non-maskable interrupts
> LOC: 26645 Local timer interrupts
> TRM: 0 Thermal event interrupts
> SPU: 0 Spurious interrupts
> ERR: 0
> MIS: 0
>
> dmesg contains:
> ACPI: EC: GPE storm detected, throttle EC GPE
> ACPI: EC: missing write data confirmation, don't expect it any longer.
>
> ACPI keys quite work but are very laggy (in the order of seconds).
>
>
> Conclusion: I never experienced acpi interrupts flood in any case, in
> vanilla the interrupt count is much lower but then there are no
> interrupts even when I press acpi keys.
> dont_disable_ec_gpe_completely_at_storm.patch does not correctly fix
> the problem for me. When 2c81ce4c9c3 is reverted,
> call_psw_on_capable_devices.patch makes no difference as it still
> works well.
>
> Thanks.
>
next prev parent reply other threads:[~2008-03-19 21:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-18 0:13 ACPI regression in 2.6.25-rc6 (function keys stop working) Guillaume Chazarain
2008-03-18 10:22 ` Alexey Starikovskiy
2008-03-18 13:17 ` Alexey Starikovskiy
2008-03-18 17:23 ` Tim Elliott
2008-03-18 19:48 ` Alexey Starikovskiy
2008-03-19 22:10 ` Rafael J. Wysocki
2008-03-18 23:29 ` Guillaume Chazarain
2008-03-18 23:40 ` Alexey Starikovskiy [this message]
2008-03-18 23:53 ` Alexey Starikovskiy
2008-03-19 1:14 ` Alexey Starikovskiy
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=47E052E3.4000107@suse.de \
--to=astarikovskiy@suse.de \
--cc=guichaz@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tle@holymonkey.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.