linux-kernel - Re: ACPI regression in 2.6.25-rc6 (function keys stop working)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47E055EA.5000300@suse.de>
Date:	Wed, 19 Mar 2008 02:53:14 +0300
From:	Alexey Starikovskiy <astarikovskiy@...e.de>
To:	Guillaume Chazarain <guichaz@...il.com>
CC:	linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org,
	lenb@...nel.org, Tim Elliott <tle@...ymonkey.com>
Subject: Re: ACPI regression in 2.6.25-rc6 (function keys stop working)

Hi Guilaume,

May I ask you for one more favor?
Could you please uncomment DEBUG at the beginning of drivers/acpi/ec.c
and send me dmesg (or, better, attach it to bugzilla.kernel.org #9998) with
the reverted offender patch?

Thanks,
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.
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/