linux-kernel - Re: ACPI quirks - acpi_osi="!Windows 2006" required on FSC Amilo notebooks to enable brightness keys

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: <1263073701.6497.75.camel@rechenknecht2k7>
Date:	Sat, 09 Jan 2010 22:48:21 +0100
From:	Peter Paul <abnominales@....de>
To:	Matthew Garrett <mjg59@...f.ucam.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: ACPI quirks - acpi_osi="!Windows 2006" required on FSC Amilo
 notebooks to enable brightness keys

On Sat, 09.01.2010, 20:26 +0000 Matthew Garrett wrote:
> On Sat, Jan 09, 2010 at 08:14:59PM +0100, Peter Paul wrote:
> 
> &gt; Nope, neither with nor without acpi_osi="!Windows 2006", there is nothing in dmesg, no output in acpi_listen and no event in xev.
> &gt; I've compared the ACPI messages in dmesg with and without the parameter, the only change is the rather obvious 
> &gt; ACPI: Deleted _OSI(Windows 2006)
> 
> And /proc/interrupts doesn't change when you hit those keys?
> 

/proc/interrupts does change all the time
The only backlight related interrupt seems to be IO-APIC-fasteoi (9) - I
get 5-7 interrupts there when pressing either Fn+F8 (brightness down) or
Fn+F7 (brightness up), but only when brightness has not reached a
maximim level in the direction I want to go.
Brightness changes not.
When adding the acpi_osi parameter, I get 10 interrupts for brightness
every key press as long as brighness has not reached it's maximum resp.
minimum.
Brightness changes.

When using a userspace application like brightness-applet, I get >100
interrupts, brightness changes.

Every once in a while I also get some interrupts there without touching
anything (but brightness does not change)


           CPU0       CPU1       
  0:     149418          0   IO-APIC-edge      timer
  1:        200          0   IO-APIC-edge      i8042
  8:        174          0   IO-APIC-edge      rtc0
  9:       3066          0   IO-APIC-fasteoi   acpi
 12:       7712          0   IO-APIC-edge      i8042
 14:      34368          0   IO-APIC-edge      ata_piix
 15:          0          0   IO-APIC-edge      ata_piix
 16:          0          0   IO-APIC-fasteoi   uhci_hcd:usb2
 18:          0          0   IO-APIC-fasteoi   ehci_hcd:usb1,
uhci_hcd:usb6
 19:          0          0   IO-APIC-fasteoi   uhci_hcd:usb5
 21:          0          0   IO-APIC-fasteoi   uhci_hcd:usb3
 22:        280          0   IO-APIC-fasteoi   HDA Intel
 23:          0          0   IO-APIC-fasteoi   uhci_hcd:usb4,
ehci_hcd:usb7
 27:       6472          0   PCI-MSI-edge      i915
 28:       8369          0   PCI-MSI-edge      ahci
 29:       2852          0   PCI-MSI-edge      eth0
 30:      47238          0   PCI-MSI-edge      iwl3945
NMI:          0          0   Non-maskable interrupts
LOC:      30854      62124   Local timer interrupts
SPU:          0          0   Spurious interrupts
PMI:          0          0   Performance monitoring interrupts
PND:          0          0   Performance pending work
RES:      51052      49567   Rescheduling interrupts
CAL:         18         27   Function call interrupts
TLB:       3098       3001   TLB shootdowns
TRM:          0          0   Thermal event interrupts
THR:          0          0   Threshold APIC interrupts
MCE:          0          0   Machine check exceptions
MCP:          8          8   Machine check polls
ERR:          0
MIS:          0


--
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/