Bug 208703
Summary: | boot performance: PnP ACPI init has 100 ms delay until quirk message - Acer TravelMate 5735Z | ||
---|---|---|---|
Product: | Power Management | Reporter: | Paul Menzel (pmenzel+bugzilla.kernel.org) |
Component: | Other | Assignee: | Zhang Rui (rui.zhang) |
Status: | REOPENED --- | ||
Severity: | normal | CC: | pmenzel+bugzilla.kernel.org, rui.zhang |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 5.7.6 | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: |
Linux 5.7.6 messages (output of `dmesg`)
Output of `acpidump` Linux 5.15.5 messages (output of `dmesg`) |
Description
Paul Menzel
2020-07-27 09:13:47 UTC
Created attachment 290605 [details]
Output of `acpidump`
By the way, I found the Linux kernel parameter `pnpacpi=` [1]. Unfortunately, it’s not well documented. > pnpacpi= [ACPI] > { off } Would that help? Otherwise, any acpi debug line I could add for more insight? [1]: https://www.kernel.org/doc/html/v5.10/admin-guide/kernel-parameters.html I think this is because we need to walk ACPI namespace to find all the matched PNP devices. Thus this is probably a generic problem. Are you aware of this on other platforms? pnpacpi=off stops ACPI from enumerating these devices but I'm not sure if this is a good idea. Paul, as mentioned in bug #208705, as this is an pretty old machine, we won't look at it unless it is a kernel regression. So I'd like to close this bug report. Please feel free to re-open it if you have any different opinions. This is still present in Linux 5.15.5: [ 0.000000] microcode: microcode updated early to revision 0xa0b, date = 2010-09-28 [ 0.000000] Linux version 5.15.0-2-amd64 (debian-kernel@lists.debian.org) (gcc-11 (Debian 11.2.0-13) 11.2.0, GNU ld (GNU Binutils for Debian) 2.37) #1 SMP Debian 5.15.5-2 (2021-12-18) […] [ 0.000000] DMI: Acer TravelMate 5735Z/BA51_MV, BIOS V1.14 07/26/2011 […] [ 0.565625] pnp: PnP ACPI init [ 0.675076] pnp 00:00: disabling [io 0x164e-0x164f] because it overlaps 0000:00:1c.2 BAR 13 [io 0x1000-0x1fff] […] In my opinion, this is a bug, and it’d be great if it’d be analyzed despite the age of the hardware. Could you please point me, how to at least figure out, where the delay is happening? ftrace? Something with `acpi.debug_layer=` or `acpi.debug_level=`? Created attachment 300139 [details]
Linux 5.15.5 messages (output of `dmesg`)
For the record, I am attaching the Linux 5.15.5 messages.
PS: They also contain another regression compared to Linux 5.7.6, where duration increased from 8 ms to 113 ms:
Linux 5.7.6:
[ 0.184442] ACPI: Enabled 15 GPEs in block 00 to 3F
[ 0.192301] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
Linux 5.15.5:
[ 0.264773] ACPI: Enabled 15 GPEs in block 00 to 3F
[ 0.377958] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
For the problem reported in the postscript, I created bug #215419 [1]. [1]: https://bugzilla.kernel.org/show_bug.cgi?id=215419 |