linux-kernel - Re: pinctrl_cherryview: massive error messages (handle_bad

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]

Date:   Mon, 24 Oct 2016 11:14:17 +0300
From:   Mika Westerberg <mika.westerberg@...ux.intel.com>
To:     Linus Walleij <linus.walleij@...aro.org>
Cc:     Christian Steiner <christian.steiner@...look.de>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: pinctrl_cherryview: massive error messages (handle_bad_irq)

On Mon, Oct 24, 2016 at 01:34:05AM +0200, Linus Walleij wrote:
> On Thu, Oct 20, 2016 at 5:36 PM, Christian Steiner
> <christian.steiner@...look.de> wrote:
> 
> >>> Currently I am using BIOS v1.22. Recently Acer released v1.23. I could
> >>> test if the BIOS update solves the problem.
> >>
> >> Please try that first.
> >
> > Updating the BIOS to v1.23 solved the problem. Thank you very much for
> > your advice!
> 
> Not that I know how the Intel ecosystem works wrt this.
> 
> Do you detect elder BIOS and display a warning? Are regular
> users updating their BIOSes? Or was this some kind of development
> Intel in-house BIOS?

People do upgrade their BIOSes but for Linux users it has some extra
pain if the OEM only provides you a .exe file which you need to run
under Windows.

It is possible to detect the BIOS version using DMI strings and issue a
warning in the driver, if that's what you mean, but currently we don't
do that.