Bug 216481 - boot performance: 250 ms spent in `ACPI: PM: Power Resource [D3C]`
Summary: boot performance: 250 ms spent in `ACPI: PM: Power Resource [D3C]`
Status: NEW
Alias: None
Product: ACPI
Classification: Unclassified
Component: BIOS (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: acpi_bios
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-09-13 13:54 UTC by Paul Menzel
Modified: 2022-09-13 13:54 UTC (History)
0 users

See Also:
Kernel Version: 5.19
Subsystem:
Regression: No
Bisected commit-id:


Attachments
Linux 5.19 messages (output of `dmesg`) (59.27 KB, text/plain)
2022-09-13 13:54 UTC, Paul Menzel
Details

Description Paul Menzel 2022-09-13 13:54:40 UTC
Created attachment 301801 [details]
Linux 5.19 messages (output of `dmesg`)

On a Dell XPS 9315/02GGG1, BIOS 1.1.3 05/11/2022, Linux 5.19 shows that 250 ms are spent in ACPI power resource initialization(?):

    [    0.000000] microcode: microcode updated early to revision 0x41c, date = 2022-03-24
    [    0.000000] Linux version 5.19.0-trunk-amd64 (debian-kernel@lists.debian.org) (gcc-11 (Debian 11.3.0-5) 11.3.0, GNU ld (GNU Binutils for Debian) 2.38.90.20220713) #1 SMP PREEMPT_DYNAMIC Debian 5.19-1~exp1 (20
22-08-02)
    [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-5.19.0-trunk-amd64 root=UUID=ebbb839d-ba09-4c1a-9fef-e88a4eb2dad5 ro quiet
    […]
    [    0.220268] ACPI: PM: Power Resource [D3C]
    [    0.472079] ACPI: PM: Power Resource [PIN]
    […]
    [    1.491029] evm: HMAC attrs: 0x1
    [    1.543661] Freeing unused decrypted memory: 2036K
    [    1.543976] Freeing unused kernel image (initmem) memory: 2728K
    [    1.564222] Write protecting the kernel read-only data: 24576k
    [    1.564898] Freeing unused kernel image (text/rodata gap) memory: 2040K
    [    1.565257] Freeing unused kernel image (rodata/data gap) memory: 1540K
    [    1.572779] x86/mm: Checked W+X mappings: passed, no W+X pages found.
    [    1.572783] Run /init as init process
    […]

250 ms are considerable part of the whole boot time.

Note You need to log in before you can comment on or make changes to this bug.