linux-kernel - Re: eeepc-wmi loaded on Asus desktop board

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] [day] [month] [year] [list]

Date:   Fri, 16 Feb 2018 11:12:16 -0800
From:   Darren Hart <dvhart@...radead.org>
To:     Andy Shevchenko <andy.shevchenko@...il.com>
Cc:     Paul Menzel <pmenzel+linux-platform-driver-x86@...gen.mpg.de>,
        Corentin Chary <corentin.chary@...il.com>,
        acpi4asus-user <acpi4asus-user@...ts.sourceforge.net>,
        Platform Driver <platform-driver-x86@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: eeepc-wmi loaded on Asus desktop board

On Fri, Feb 16, 2018 at 06:45:20PM +0200, Andy Shevchenko wrote:
> +Cc: Darren (for sure)
> 
> On Fri, Feb 16, 2018 at 12:42 AM, Paul Menzel
> <pmenzel+linux-platform-driver-x86@...gen.mpg.de> wrote:
> > Dear Linux folks,
> >
> >
> > Debugging an ACPI suspend problem on the desktop board Asus F285-M PRO with
> > Linux 4.14, I noticed, the module *eeepc_wmi* is loaded, and an input device
> > is created.
> >

Does this driver impact your suspend problem?

> > ```
> > Feb 15 18:49:01 asusf2a85mpro kernel: calling  eeepc_wmi_init+0x0/0x1000
> > [eeepc_wmi] @ 285
> > Feb 15 18:49:01 asusf2a85mpro kernel: asus_wmi: Initialization: 0x0
> > Feb 15 18:49:01 asusf2a85mpro kernel: asus_wmi: BIOS WMI version: 0.9
> > Feb 15 18:49:01 asusf2a85mpro kernel: asus_wmi: SFUN value: 0x0
> > Feb 15 18:49:01 asusf2a85mpro kernel: input: Eee PC WMI hotkeys as
> > /devices/platform/eeepc-wmi/input/input7
> > Feb 15 18:49:01 asusf2a85mpro kernel: asus_wmi: Number of fans: 1
> > Feb 15 18:49:01 asusf2a85mpro kernel: initcall eeepc_wmi_init+0x0/0x1000
> > [eeepc_wmi] returned 0 after 12130 usecs
> > ```
> >
> > Please find the full log attached.
> >
> > Is that expected, or should the module not load at all on desktop boards?

The eeepc_wmi driver loads when the EEEPC_ACPI_HID or WMI_EVENT_GUID is
presented by the platform firmware. It is tightly coupled with the Asus wmi
driver, so this isn't surprising that it loads on an Asus board as it isn't
uncommon to use the same GUIDs across platforms. This may suggest a need to
rename this driver to something less specific - assuming of course that it is
performing a necessary function.

-- 
Darren Hart
VMware Open Source Technology Center