linux-kernel - Re: [REGRESSION] 4.17 failed to probe ACPI PnP

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <s5hy3fac6ao.wl-tiwai@suse.de>
Date:   Wed, 20 Jun 2018 08:37:19 +0200
From:   Takashi Iwai <tiwai@...e.de>
To:     "Rafael J. Wysocki" <rafael@...nel.org>
Cc:     Noah Davis <noahadvs@...il.com>,
        ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [REGRESSION] 4.17 failed to probe ACPI PnP

On Tue, 19 Jun 2018 10:38:50 +0200,
Takashi Iwai wrote:
> 
> On Tue, 19 Jun 2018 10:28:42 +0200,
> Rafael J. Wysocki wrote:
> > 
> > On Tue, Jun 19, 2018 at 8:12 AM, Takashi Iwai <tiwai@...e.de> wrote:
> > > Hi,
> > >
> > > there seems a regression regarding the probe of ACPI PnP devices.
> > > The detailed logs are found in openSUSE bugzilla:
> > >   https://bugzilla.opensuse.org/show_bug.cgi?id=1098074
> > 
> > But that's on this particular machine, not in general, right?
> > 
> > At least I don't see this on any of the systems in my office.
> 
> Yes, it looks so.  4.17 and later works on my several machines, too.
> 
> > 
> > > In short, since 4.17, the laptop keyboard is lost on ASUS K501UW.
> > > Comparing the kernel messages and other logs indicates that the
> > > complete lost of ACPI PnP devices:
> > >
> > > On 4.16:
> > > [    0.390244] pnp: PnP ACPI: found 9 devices
> > >
> > > On 4.17:
> > > [    0.263266] pnp: PnP ACPI: found 0 devices
> > >
> > > ... and this leads to the failure of PS/2 keyboard detection due to
> > > the missing PNP030b entry as a result.
> > >
> > > Any hints for debugging this are appreciated.
> > 
> > It looks like this may be related to the ACPICA changes that went in
> > during the 4.17 cycle.
> > 
> > I would try 4.18-rc1 as there is an ACPICA fix in it that may be
> > related to this in theory.  If that doesn't help, I'd focus on the
> > ACPICA changes.
> 
> OK, Noah, could you test later the kernel in OBS Kernel:HEAD repo?
> Now 4.18-rc1 kernel is being built there, and hopefully will finish
> soon later.

4.18-rc1 was confirmed to work, so something had fixed it.

Also, the symptom appears not only on a single machine but on another
(ASUS?) machine, according to the bug report.


thanks,

Takashi