[REGRESSION] 4.17 failed to probe ACPI PnP

[REGRESSION] 4.17 failed to probe ACPI PnP

[Takashi Iwai]

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

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.


Thanks!

Takashi

Re: [REGRESSION] 4.17 failed to probe ACPI PnP

[Rafael J. Wysocki]

On Tue, Jun 19, 2018 at 8:12 AM, Takashi Iwai <tiwai@suse.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.

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

Thanks,
Rafael

Re: [REGRESSION] 4.17 failed to probe ACPI PnP

[Takashi Iwai]

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@suse.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.


thanks,

Takashi

Re: [REGRESSION] 4.17 failed to probe ACPI PnP

[Takashi Iwai]

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@suse.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

Re: [REGRESSION] 4.17 failed to probe ACPI PnP

[Rafael J. Wysocki]

On Wed, Jun 20, 2018 at 8:37 AM, Takashi Iwai <tiwai@suse.de> wrote:
> 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@suse.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.

Please check this commit

5088814a6e93 ACPICA: AML parser: attempt to continue loading table after error

None of the other ACPICA commits that have gone in since 4.17 should
affect the behavior at hand.

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

OK

Thanks,
Rafael

Re: [REGRESSION] 4.17 failed to probe ACPI PnP

[Takashi Iwai]

On Wed, 20 Jun 2018 09:28:40 +0200,
Rafael J. Wysocki wrote:
> 
> On Wed, Jun 20, 2018 at 8:37 AM, Takashi Iwai <tiwai@suse.de> wrote:
> > 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@suse.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.
> 
> Please check this commit
> 
> 5088814a6e93 ACPICA: AML parser: attempt to continue loading table after error
> 
> None of the other ACPICA commits that have gone in since 4.17 should
> affect the behavior at hand.

OK, I'm building a test kernel with this backport.  Stay tuned.


thanks,

Takashi

Re: [REGRESSION] 4.17 failed to probe ACPI PnP

[Takashi Iwai]

On Wed, 20 Jun 2018 11:11:17 +0200,
Takashi Iwai wrote:
> 
> On Wed, 20 Jun 2018 09:28:40 +0200,
> Rafael J. Wysocki wrote:
> > 
> > On Wed, Jun 20, 2018 at 8:37 AM, Takashi Iwai <tiwai@suse.de> wrote:
> > > 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@suse.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.
> > 
> > Please check this commit
> > 
> > 5088814a6e93 ACPICA: AML parser: attempt to continue loading table after error
> > 
> > None of the other ACPICA commits that have gone in since 4.17 should
> > affect the behavior at hand.
> 
> OK, I'm building a test kernel with this backport.  Stay tuned.

The result looks positive, things seem working with the backport.

Care to send it to Greg for 4.17.x stable?  Thanks!


Takashi

Re: [REGRESSION] 4.17 failed to probe ACPI PnP

[Rafael J. Wysocki]

On Wed, Jun 20, 2018 at 10:20 PM, Takashi Iwai <tiwai@suse.de> wrote:
> On Wed, 20 Jun 2018 11:11:17 +0200,
> Takashi Iwai wrote:
>>
>> On Wed, 20 Jun 2018 09:28:40 +0200,
>> Rafael J. Wysocki wrote:
>> >
>> > On Wed, Jun 20, 2018 at 8:37 AM, Takashi Iwai <tiwai@suse.de> wrote:
>> > > 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@suse.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.
>> >
>> > Please check this commit
>> >
>> > 5088814a6e93 ACPICA: AML parser: attempt to continue loading table after error
>> >
>> > None of the other ACPICA commits that have gone in since 4.17 should
>> > affect the behavior at hand.
>>
>> OK, I'm building a test kernel with this backport.  Stay tuned.
>
> The result looks positive, things seem working with the backport.
>
> Care to send it to Greg for 4.17.x stable?  Thanks!

Will do tomorrow, thanks!