All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	Noah Davis <noahadvs@gmail.com>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [REGRESSION] 4.17 failed to probe ACPI PnP
Date: Tue, 19 Jun 2018 10:28:42 +0200	[thread overview]
Message-ID: <CAJZ5v0hidPav5kvTW05e0k5mouFyiUiyUW50=fDqVphbEBjQaA@mail.gmail.com> (raw)
In-Reply-To: <s5h8t7bfgnq.wl-tiwai@suse.de>

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

  reply	other threads:[~2018-06-19  8:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-19  6:12 [REGRESSION] 4.17 failed to probe ACPI PnP Takashi Iwai
2018-06-19  8:28 ` Rafael J. Wysocki [this message]
2018-06-19  8:38   ` Takashi Iwai
2018-06-20  6:37     ` Takashi Iwai
2018-06-20  7:28       ` Rafael J. Wysocki
2018-06-20  9:11         ` Takashi Iwai
2018-06-20 20:20           ` Takashi Iwai
2018-06-20 22:12             ` Rafael J. Wysocki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJZ5v0hidPav5kvTW05e0k5mouFyiUiyUW50=fDqVphbEBjQaA@mail.gmail.com' \
    --to=rafael@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=noahadvs@gmail.com \
    --cc=tiwai@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.