I'm having freezing problems with my Debian 12 install on a Dell Latitude 7490 laptop. The screen will freeze and become unresponsive. Moving the mouse during the freeze will cause the keyboard backlight to turn back on if it's off, but nothing happens on the screen. This happens both mid-use and before login, whether in TTY or GUI, and whether in normal mode or recovery mode. I have LUKS, and I haven't noticed it happening before I enter encryption key, though. The only way around seems to be a force shutdown -> reboot, but the problem will almost always just happen again shortly after next boot. My system is honestly more or less unusable right now because of this. At first, I didn't see this happening when I was plugged into AC at work or at home, but since some of the changes that I've tried (below), freezing now seems to happen regardless of battery or AC. I've tried a number of things: 1) Update kernel from 6.1.* -> 6.12.33 via backports. 2) Update firmware drivers similarly. 3) Change BIOS settings (disabled C-States, disabled Intel SpeedShift, disabled SpeedStep, disabled TurboBoost; basically disabled every intel performance option besides multi core and hyper threading). I also have secure boot turned disabled, but that was to solve a different problem. 4) Set intel_idle.max_cstate=0 also tried setting to 1) and intel_iommu=off in GRUB_CMDLINE_LINUX_DEFAULT. Right now, I'm using bookworm with the 6.12.33 kernel from backports, Wayland, and iwd + Network manager. Here's a link to a journalctl dump from a hang: [https://paste.c-net.org/GoldbergLined](https://paste.c-net.org/GoldbergLined) The problem in [this Mint forum thread](https://forums.linuxmint.com/viewtopic.php?t=432757) seems to be quite similar to mine, but no resolution. Thanks for your help!

I have a Lenovo Ideapad 320-15ABR, (I found the exact model name with dmidecode). I'm having trouble getting the touchpad to work. It's not showing up in xinput --list or cat /proc/bus/input/devices. I'm using Linux 4.13.2, compiled with some extra debugging messages. Here's some relevant dmesg output when booted with i8042.nopnp. Without this option, I get the message: i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp $ dmesg|grep psm [ 2.595815] bus: 'serio': add driver psmouse [ 2.627475] bus: 'serio': driver_probe_device: matched device serio1 with driver psmouse [ 2.627477] bus: 'serio': really_probe: probing driver psmouse with device serio1 [ 2.627482] psmouse serio1: no default pinctrl state [ 2.651584] psmouse: probe of serio1 rejects match -19 $ dmesg|grep i8042 [ 2.577522] i8042: PNP detection disabled [ 2.578648] Registering platform device 'i8042'. Parent at platform [ 2.578650] device: 'i8042': device_add [ 2.578655] bus: 'platform': add device i8042 [ 2.578668] PM: Adding info for platform:i8042 [ 2.578682] bus: 'platform': add driver i8042 [ 2.578692] bus: 'platform': driver_probe_device: matched device i8042 with driver i8042 [ 2.578694] bus: 'platform': really_probe: probing driver i8042 with device i8042 [ 2.578699] i8042 i8042: no default pinctrl state [ 2.578702] devices_kset: Moving i8042 to end of list [ 2.595059] serio: i8042 KBD port at 0x60,0x64 irq 1 [ 2.595070] serio: i8042 AUX port at 0x60,0x64 irq 12 [ 2.595125] driver: 'i8042': driver_bound: bound to device 'i8042' [ 2.595150] bus: 'platform': really_probe: bound device i8042 to driver i8042 [ 2.604184] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0 **edit:** I've opened a ticket here in case anyone is interested in following this problem: https://bugzilla.kernel.org/show_bug.cgi?id=196985

This is Gentoo Linux with OpenRC (updated to systemd later on), and ACPI + some power management features in the kernel for Intel. ACPId is up and running. I can suspend to ram using : echo -n "mem" > /sys/power/state This works, but I need to use the power button to wake up. Is there a way to wake up from keyboard events like pressing the space bar? The keyboard is a wireless USB keyboard. I've looked at the content of the script in /etc/acpi and it offers no insight into doing this. Most of the information I find is usually geared at laptop users. Do I really need something like the old pm-utils to accomplish this and is there anything wrong with just using acpid? cat /proc/acpi/wakeup Device S-state Status Sysfs node P0P2 S4 *disabled P0P3 S4 *disabled pci:0000:00:06.0 P0P1 S4 *disabled pci:0000:00:1e.0 PS2K S4 *enabled pnp:00:0b EUSB S4 *enabled pci:0000:00:1d.7 USBE S4 *enabled pci:0000:00:1a.7 P0P4 S4 *disabled pci:0000:00:1c.0 P0P5 S4 *disabled P0P6 S4 *disabled pci:0000:00:1c.2 P0P7 S4 *disabled P0P8 S4 *disabled P0P9 S4 *disabled GBEC S4 *disabled USB0 S4 *enabled pci:0000:00:1d.0 USB1 S4 *enabled pci:0000:00:1d.1 USB2 S4 *enabled pci:0000:00:1d.2 USB3 S4 *disabled USB4 S4 *enabled pci:0000:00:1a.0 USB5 S4 *enabled pci:0000:00:1a.1 USB6 S4 *enabled pci:0000:00:1a.2 MBT4 S4 *disabled Seemingly relevant kernel options used (3.10.25-gentoo SMP, 64bit, IA32emul=off, no-multilib): - CONFIG_HOTPLUG_CPU=y and with cpu0_hotplug by default - Suspend to ram and standby Hibernation - Power mgmt debug support - Suspend/resume event tracing - ACPI support - CPU idle PM support - Cpuidle Driver for Intel Processors - Support for systemd through Gentoo option in kernel was enabled BIOS setup is pretty standard: - I've enabled ACPI2.0 extra tables - Not seeing any wake events for USB but I've tried wake up events from PCI/PCIe/PS2 etc but indeed this is a wireless usb keyboard - Board is old school winner Maximus Formula with Q6600 Core2quad OpenRC was updated to systemd and the kernel was recompiled to support that. Configuration was also updated like so . With systemd, apcid is not required in all instances. For instance without running you can issue systemctl suspend and the behavior is... the same as before i.e. wake up only from power button... pstree output: systemd ├─acpid -f ├─at-spi-bus-laun │ ├─dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork--print-addres │ └─2*[{at-spi-bus-laun}] ├─at-spi2-registr --use-gnome-session │ └─{at-spi2-registr} ├─dbus-daemon --system --address=systemd: --nofork --nopidfile--systemd-activation ├─dbus-daemon --fork --print-pid 5 --print-address 7 --session ├─dbus-launch --sh-syntax --exit-with-session ├─dhcpcd -q --nobackground ├─login -- │ └─bash │ └─startx /usr/bin/startx │ └─xinit /etc/X11/xinit/xinitrc -- /etc/X11/xinit/xserverrc :0 -auth... │ ├─X -nolisten tcp :0 -auth /home/user/.serverauth.3329 │ └─openbox --startup /usr/libexec/openbox-autostart OPENBOX │ ├─firefox │ │ ├─plugin-containe ... │ │ │ └─6*[{plugin-containe}] │ │ └─35*[{firefox}] │ └─vlc │ └─4*[{vlc}] ├─lxterminal │ ├─bash │ │ └─htop │ ├─bash │ │ └─su │ │ └─bash │ │ └─grc /usr/lib/python-exec/python2.7/grc tail -f ... │ │ ├─grcat /usr/lib/python-exec/python2.7/grcat conf.log │ │ └─tail -f /var/log/emerge.log │ ├─bash │ ├─gnome-pty-helpe │ └─{lxterminal} ├─mount.ntfs /dev/sdb1 /mnt/div -o rw ├─roxterm │ ├─bash │ │ └─su │ │ └─bash │ │ └─pstree -a │ ├─gnome-pty-helpe │ └─{roxterm} ├─systemd --user │ └─(sd-pam) ├─systemd-journal ├─systemd-logind ├─systemd-udevd ├─wbar --pos bot-right --taskbar --isize 24 └─xcompmgr -c -C -t-5 -l-5 -r4.2 -o.55

I’ve installed antiX 19.3 recently on a 16-yro (or older), laptop. One issue I’ve been having is that the thing keeps going to sleep! Every 30-45 seconds or so, it goes into sleep mode; and comes back up on a keypress. This includes even the boot sequence: While running the init scripts for runlevel 5, this already happens once. It continues after my desktop environment (IceWM) has loaded. I've read this highly related question , and found a workaround: Completely disable ACPI and APM on the grub2 boot line for the kernel: acpi=off apm=off. But that’s not a good solution, because it is important for the laptop to go to sleep when unused; and you want fan speed control etc. Another suggestion there involve systemd facilities - but my distribution doesn't use systemd. What else can I do? Also, what could be the cause of this? Here's the repeating segment of my dmesg:

[Wed May 12 17:11:00 2021] VFS: busy inodes on changed media or resized disk sr0
[Wed May 12 17:11:26 2021] PM: suspend entry (deep)
[Wed May 12 17:11:26 2021] PM: Syncing filesystems ... done.
[Wed May 12 17:11:26 2021] Freezing user space processes ... (elapsed 0.001 seconds) done.
[Wed May 12 17:11:26 2021] OOM killer disabled.
[Wed May 12 17:11:26 2021] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[Wed May 12 17:11:26 2021] Suspending console(s) (use no_console_suspend to debug)
[Wed May 12 17:11:26 2021] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[Wed May 12 17:11:26 2021] sd 0:0:0:0: [sda] Stopping disk
[Wed May 12 17:11:28 2021] ACPI: EC: interrupt blocked
[Wed May 12 17:11:28 2021] ACPI: Preparing to enter system sleep state S3
[Wed May 12 17:11:28 2021] ACPI: EC: event blocked
[Wed May 12 17:11:28 2021] ACPI: EC: EC stopped
[Wed May 12 17:11:28 2021] PM: Saving platform NVS memory
[Wed May 12 17:11:28 2021] Disabling non-boot CPUs ...
[Wed May 12 17:11:28 2021] ACPI: Low-level resume complete
[Wed May 12 17:11:28 2021] ACPI: EC: EC started
[Wed May 12 17:11:28 2021] PM: Restoring platform NVS memory
[Wed May 12 17:11:28 2021] ACPI: Waking up from system sleep state S3
[Wed May 12 17:11:28 2021] ACPI: EC: interrupt unblocked
[Wed May 12 17:11:28 2021] usb usb2: root hub lost power or was reset
[Wed May 12 17:11:28 2021] usb usb3: root hub lost power or was reset
[Wed May 12 17:11:28 2021] usb usb4: root hub lost power or was reset
[Wed May 12 17:11:28 2021] 8139too 0000:01:00.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
[Wed May 12 17:11:28 2021] sd 0:0:0:0: [sda] Starting disk
[Wed May 12 17:11:28 2021] ACPI: EC: event unblocked
[Wed May 12 17:11:28 2021] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
[Wed May 12 17:11:28 2021] ata1.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out
[Wed May 12 17:11:28 2021] ata2.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
[Wed May 12 17:11:28 2021] ata2.00: ACPI cmd ef/03:42:00:00:00:a0 (SET FEATURES) filtered out
[Wed May 12 17:11:29 2021] usb 3-2: reset full-speed USB device number 2 using uhci_hcd
[Wed May 12 17:11:29 2021] firewire_core 0000:01:02.0: rediscovered device fw0
[Wed May 12 17:11:30 2021] OOM killer enabled.
[Wed May 12 17:11:30 2021] Restarting tasks ... done.
[Wed May 12 17:11:30 2021] PM: suspend exit
[Wed May 12 17:11:35 2021] VFS: busy inodes on changed media or resized disk sr0
[Wed May 12 17:12:01 2021] PM: suspend entry (deep)

Notes: * I should mention that this did not happen with the Windows XP installation which the laptop used to have. * The laptop’s battery is almost dead, so I only run it with mains power plugged in. * I tried switching the kernel version from 4.9.something to 4.19.something (antix-packaged images); no effect. * Laptop info: Clevo M3CW, Pentium M 1.6GHz, 1 GB memory, 40GB HDD. Has a built-in CD which is giving me another kind of trouble that's probably unrelated.

I just purchased this laptop used and installed Fedora 42 on it. It’s a Dell Latitude 5420 with an i5-1145G7 processor. The laptop does not support S3 sleep, only s2idle. It successfully enters and resumes sleep when the lid is closed, but the battery drains rapidly. I have not done any proper benchmarks but I was at around ~60% battery life last night, and when I opened it this afternoon it was completely dead. After running the S0ix self test tool , I got the following output:

...
Your system supports S0ix substates, but did not achieve the shallowest s0i2.0
    
Here is the S0ix substates status: 
Substate   Residency      
S0i2.0     0              
S0i3.0     0     
...
Below are the deeper S0ix substate required IPs did not show YES:
    pmc0:            USB2PLL_OFF_STS    Required               
    pmc0:            OPIOPLL_OFF_STS    Required               
    pmc0:                CSME_PG_STS    Required               
    pmc0:                xHCI_PG_STS    Required               
    pmc0:                 GBE_PG_STS    Required               
    pmc0:               xHCI0_D3_STS    Required               
    pmc0:          CPU_C10_REQ_STS_0    Required               
    pmc0:    MPHY_Core_DL_REQ_STS_16    Required

Full output here . Unfortunately I have no idea what this means.

I have a problem with ACPI event in Linux. rtcwake is not working because alarm was not handled by kernel. This is the snippet of dmesg output:

[    1.102322] ACPI Error: Result stack is empty! State=00000000413b8c7a (20240827/dswstate-64)
[    1.102331] ACPI Error: AE_AML_NO_RETURN_VALUE, Missing or null operand (20240827/dsutils-609)
[    1.102336] ACPI Error: AE_AML_NO_RETURN_VALUE, While creating Arg 1 (20240827/dsutils-725)

[    1.102345] 
               Initialized Local Variables for Method [_EVT]:
[    1.102347]   Local3: 00000000b30bc4f6            Integer 0000000000000000

[    1.102359] Initialized Arguments for Method [_EVT]:  (1 arguments defined for method invocation)
[    1.102361]   Arg0:   0000000030350e68            Integer 0000000000000018

[    1.102374] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_AML_NO_RETURN_VALUE) (20240827/psparse-529)

Then I dumped the ACPI table and _SB.GPIO._EVT is located somewhere in SSDT15:

DefinitionBlock ("", "SSDT", 1, "HPQOEM", "85DE    ", 0x00000001)
{
    External (_SB_.G006, FieldUnitObj)
    External (_SB_.GPIO, DeviceObj)
    External (_SB_.PCI0.GP17.AZAL, UnknownObj)
    External (_SB_.PCI0.GP17.XHC0, UnknownObj)
    External (_SB_.PCI0.GP17.XHC1, UnknownObj)
    External (_SB_.PCI0.GP17.XHC1.RHUB.PRT1.WCAM, UnknownObj)
    External (_SB_.PCI0.GPP3.DEV0, UnknownObj)
    External (_SB_.PCI0.GPP4.XPDV, UnknownObj)
    External (_SB_.PCI0.REDM, FieldUnitObj)
    External (_SB_.PWRB, UnknownObj)
    External (_SB_.WFDE.PDAT, IntObj)
    External (_SB_.WFTE.WMDE, MethodObj)    // 3 Arguments
    External (_SB_.WMID.GWET, MethodObj)    // 2 Arguments
    External (M000, MethodObj)    // 1 Arguments
    External (M014, MethodObj)    // 5 Arguments
    External (M249, MethodObj)    // 4 Arguments

    Method (MSTP, 1, Serialized)
    {
        Local0 = (Arg0 - 0x0C00)
        M000 (Local0)
    }

    Scope (\_SB.GPIO)
    {
        Method (_AEI, 0, NotSerialized)  // _AEI: ACPI Event Interrupts
        {
            Name (BUF0, ResourceTemplate ()
            {
                GpioInt (Edge, ActiveHigh, ExclusiveAndWake, PullDefault, 0x1388,
                    "\\_SB.GPIO", 0x00, ResourceConsumer, ,
                    )
                    {   // Pin list
                        0x0000
                    }
                GpioInt (Edge, ActiveLow, ExclusiveAndWake, PullNone, 0x0000,
                    "\\_SB.GPIO", 0x00, ResourceConsumer, ,
                    )
                    {   // Pin list
                        0x0002
                    }
                GpioInt (Edge, ActiveLow, ExclusiveAndWake, PullNone, 0x0000,
                    "\\_SB.GPIO", 0x00, ResourceConsumer, ,
                    )
                    {   // Pin list
                        0x0004
                    }
                GpioInt (Edge, ActiveBoth, Exclusive, PullNone, 0x0000,
                    "\\_SB.GPIO", 0x00, ResourceConsumer, ,
                    )
                    {   // Pin list
                        0x0006
                    }
                GpioInt (Edge, ActiveBoth, Exclusive, PullUp, 0x0000,
                    "\\_SB.GPIO", 0x00, ResourceConsumer, ,
                    )
                    {   // Pin list
                        0x0018
                    }
                GpioInt (Edge, ActiveHigh, ExclusiveAndWake, PullNone, 0x0000,
                    "\\_SB.GPIO", 0x00, ResourceConsumer, ,
                    )
                    {   // Pin list
                        0x002C
                    }
                GpioInt (Level, ActiveHigh, ExclusiveAndWake, PullNone, 0x0000,
                    "\\_SB.GPIO", 0x00, ResourceConsumer, ,
                    )
                    {   // Pin list
                        0x003A
                    }
                GpioInt (Level, ActiveHigh, ExclusiveAndWake, PullNone, 0x0000,
                    "\\_SB.GPIO", 0x00, ResourceConsumer, ,
                    )
                    {   // Pin list
                        0x003B
                    }
                GpioInt (Level, ActiveHigh, ExclusiveAndWake, PullNone, 0x0000,
                    "\\_SB.GPIO", 0x00, ResourceConsumer, ,
                    )
                    {   // Pin list
                        0x003D
                    }
            })
            Return (BUF0) /* \_SB_.GPIO._AEI.BUF0 */
        }

        // Somewhere below here
        Method (_EVT, 1, Serialized)  // _EVT: Event
        {
            Switch (ToInteger (Arg0))
            {
                Case (Zero)
                {
                    MSTP (0x3900)
                    Notify (\_SB.PWRB, 0x80) // Status Change
                }
                Case (0x02)
                {
                    MSTP (0x3902)
                    Notify (\_SB.PCI0.GPP4.XPDV, 0x02) // Device Wake
                }
                Case (0x04)
                {
                    MSTP (0x3904)
                    Notify (\_SB.PCI0.GPP3.DEV0, 0x02) // Device Wake
                }
                Case (0x06)
                {
                    MSTP (0x3906)
                    If (G006)
                    {
                        \_SB.WMID.GWET (0x1A, 0xFF)
                    }
                    Else
                    {
                        Notify (\_SB.PCI0.GP17.XHC1.RHUB.PRT1.WCAM, One) // Device Check
                        \_SB.WMID.GWET (0x1A, 0xFE)
                    }
                }
                Case (0x18)
                {
                    Name (SDAA, Zero)
                    Name (SDAB, Zero)
                    If ((Local3 >= 0x82))
                        {
                            \_SB.PCI0.REDM = One
                            SDAA = 0x03
                            SDAB = 0x03
                        } = M249 (Zero, Zero, 0x03E1051C, Local3)
                    Else
                    {
                        \_SB.PCI0.REDM = Zero
                        SDAA = 0x02
                        SDAB = 0x02
                    }

                    \_SB.WFDE.PDAT = SDAB /* \_SB_.GPIO._EVT.SDAB */
                    \_SB.WFDE.PDAT <<= 0x10
                    \_SB.WFDE.PDAT |= SDAA /* External reference */
                    \_SB.WFTE.WMDE (Zero, One, Zero)
                    M014 (0xFED80200, Zero, 0x0F, One, One)
                }
                Case (0x3A)
                {
                    MSTP (0x3958)
                    Notify (\_SB.PCI0.GP17.XHC0, 0x02) // Device Wake
                }
                Case (0x3B)
                {
                    MSTP (0x3959)
                    Notify (\_SB.PCI0.GP17.XHC1, 0x02) // Device Wake
                }
                Case (0x3D)
                {
                    MSTP (0x3961)
                    Notify (\_SB.PCI0.GP17.AZAL, 0x02) // Device Wake
                }

            }
        }
    }
}

**The question is:** How can I spot which line of code is causing AE_AML_NO_RETURN_VALUE?

Yocto System taking more time to resume from S3 sleep, it should take 2sec, but taking 12sec: Suspend entry: [ 244.086061] PM: suspend entry (deep) Low-level resume complete: [ 246.900251] Suspend exit: [ 247.970167] Display usable (login/dmesg): [ 257.556554] sshd or ACP logs visible Stage Time (sec) Suspend → Low-level resume ~2.81s Suspend → Suspend exit ~3.88s Suspend → Usable system ~13.5s How do I diagnose this and identify the part where it gets stuck for so long?

This was run while unplugged ➜ ~ upower -i /org/freedesktop/UPower/devices/line_power_AC native-path: AC power supply: yes updated: Sa 10 Mai 2025 11:06:43 CEST (1041 seconds ago) has history: no has statistics: no line-power warning-level: none online: yes icon-name: 'ac-adapter-symbolic' ➜ ~ and this is acpi_listen, starting unplugged ➜ ~ sudo acpi_listen battery PNP0C0A:00 00000080 00000001 battery PNP0C0A:00 00000080 00000001 #These two lines show up when I plug it in battery PNP0C0A:00 00000080 00000001 battery PNP0C0A:00 00000080 00000001 #These two lines when I plug back out battery PNP0C0A:00 00000080 00000001 battery PNP0C0A:00 00000080 00000001 #These two when plugging back in ^C ➜ ~ I also have these ACPI errors, over and over [ 65.313102] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.EC.HKEY.DEVT.PEGS], AE_NOT_FOUND (20240827/psargs-332) [ 65.313138] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC.HKEY.DEVT due to previous error (AE_NOT_FOUND) (20240827/psparse-529) [ 65.313162] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC._Q27 due to previous error (AE_NOT_FOUND) (20240827/psparse-529) Has anyone come across this issue? I've found some threads that look similar but I haven't been able to implement some working solution. This is somewhat beyond my knowledge so please let me know if there's any other useful information I might add.

When I boot up my Debian 11.2 live USB stick it gives me these errors: ACPI BIOS Error(bug) : Failure creating named object[\ADBG], AE_ALREADY_EXISTS ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog and after these errors Debian doesn't run. I tested it with two different USB sticks made with Rufus.

On my machine, i have power savings disable on the BIOS. When I run Ubuntu on this machine, the CPU's are running maximum at 2100 MHz. However, when I'm running CentOS 7, even with the scaling governor set to "performance", the CPU's are not running full at 2100 MHz. cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor performance performance performance performance grep -i mhz /proc/cpuinfo cpu MHz : 1688.285 cpu MHz : 2058.656 cpu MHz : 1622.988 cpu MHz : 2070.632 My application is a network processing application, so the CPU clock difference is resulting a performance difference. I do not have cpuspeed,powerd, or any other power regulating services running. So my question is, is this expected behavior given the cpupower is set to "perform"? It seems CentOS is override the BIOS setting. When I boot to Ubuntu, it just takes the BIOS settings and all the CPU's are running max.

I noticed recently that shutting down my Linux (Ubuntu 20.04) desktop does not power it down once everything has come to a halt. It states Power down but the led is still glowing and the fan is still moving etc. which it shouldn't! The result is a terminal stating as showin in the picture: I assumed something might be configured wrong in the BIOS but when I tried with Windows (I'm sorry!) it worked as usual so the problem seems to come from the linux side. Of course I searched and tried other solutions like: https://unix.stackexchange.com/questions/457967/shutdown-does-not-power-off-why However neither the KDE shutdown option nor the terminal call seem to work. Another thing I tried was https://askubuntu.com/questions/125844/shutdown-does-not-power-off-computer or https://www.unixmen.com/fix-shutdown-power-computer-ubuntu-14-04/ but the answer seems outdated and does not work (anymore?). So even with the option GRUB_CMDLINE_LINUX_DEFAULT="noplymouth intel_iommu=on acpi=force apm=power_off" nothing happens (tried acpi=force and apm=power_off separately, too) and the computer still stays powered-on after shutting down. One hint might be the output of acpi -V -i > No support for device type: power_supply So is this the problem? Is there a way of configuring acpi correctly? Or did I miss something else? Thanks

I recently managed to make fingerprint authentication work on my laptop, thanks to the Goodix Linux [Development](https://discord.com/invite/6xZ6k34Vqg) Discord community and the GitHub users Infinytum and Michael Teuscher on the driver/538d branch . But after enabling fingerprint for login with fprintd-enroll and for sudo access with sudo pam-auth-update I noticed a problem: Whenever I am using an external monitor to work, and the lid is closed, I have to wait for the fingerprint authentication to time out, before being able to type the sudo password, which causes a delay of several seconds:

username@host:~/ron/libfprint$ sudo ls
Place your finger on the fingerprint reader
Place your finger on the reader again
Place your finger on the reader again
Place your finger on the reader again
Verification timed out
[sudo] password for username:

How can I disable fingerprint authentication when the laptop lid is closed, so I can type the sudo password without waiting for the fingerprint to time out?

I want to hibernate on low battery:

SUBSYSTEM=="power_supply", \
    ATTR{status}=="Discharging", \
    ATTR{capacity}=="[0-5]", \
    RUN+="/usr/bin/systemctl hibernate", \

This works well if the system is awake. If suspended however, it doesn't hibernate until I wake it, then instead of allowing me to unlock it immediately hibernates. How can I make this event either work while suspended, or trigger a wakeup (and then hibernate) itself, without me opening the lid? --- I have tried adding:

ATTR{power/wakeup}="enabled"

without success. Indeed there is no wakeup currently in /sys/class/power_supply/BAT1/power/ - actually though /sys/class/power_supply/BAT1/device/power/wakeup exists and is already enabled. I gather I can't make the udev rule run while suspended, I need to trigger it to wake on low battery separately (then the udev rule can run and hibernate). This seems already implemented in [drivers/acpi/battery.c](https://github.com/torvalds/linux/blob/22da5264abf497a10a4ed629f07f4ba28a7ed5eb/drivers/acpi/battery.c#L994-L1001) :

/*
	 * Wakeup the system if battery is critical low
	 * or lower than the alarm level
	 */
	if ((battery->state & ACPI_BATTERY_STATE_CRITICAL) ||
	    (test_bit(ACPI_BATTERY_ALARM_PRESENT, &battery->flags) &&
	     (battery->capacity_now alarm)))
		acpi_pm_wakeup_event(&battery->device->dev);

But that has not worked for me, I don't know if 'critical low' is another textual capacity level, I've only seen as low as 'Low', but it was at the time lower than the /sys/class/power_supply/BAT1/alarm. --- NB: I am aware of hybrid-sleep, but that is not what I want, firstly since I would like to conserve _some_ battery; but also so that I can use suspend-then-hibernate such that it hibernates on either low battery _or_ time delay.

I have been struggling for over a month with a new Lenovo Thinkpad P16 Gen2 laptop running Ubuntu 22.04 LTS, that **would not successfully suspend**. Maybe 90% of the time it worked okay, the other 10% reboot was necessary. This was unacceptable to me. Eventually, I decided it would be worthwhile to hibernate the machine instead of suspending it. I had to disable Secure Boot to do so. As this is a home computer I thought the risk was small. *I have started four or five posts here looking for a solution with nothing found. Sorry if the admins of this page have a problem with this, but each post interrogated a different aspect of the problem.* However, the sudo systemctl hibernate command did not work. The computer would save its state and immediately wake up. Not what I wanted. It was suggested that I disable wakeup on the devices listed as enabled in the output of acpitool -w |grep enabled. But one of these devices would not disable wakeup with the acpitool -W command. So still no acceptable hibernation. Then, by chance, I looked at the man page of acpitool where I came upon > **-S, --suspend to disk** ? > Put the machine into sleep state S4, if possible. Requires write access to /proc/acpi/sleep (kernel 2.4.x) or /sys/power/state (kernel > 2.6.x) **This proved to be a solution to my problem.** Unlike sudo systemctl hibernate, sudo acpitool -S achieves hibernation and successfully returns from it when the power is turned on. The only problem here is I'm not sure how to enable it in the Ubuntu Gnome GUI. But I can't find anything about this on the internet other than the man page. I still have these questions: **I am not sure what the difference between the two commands is internally and would like to know.** **I'd also like to know if there are any bad side effects I might encounter in using this command.** **UPDATE:** In response to the request of @waltinator I have the following data: 1. journal after sudo acpitool -S: $ sudo journalctl --since="-5 minutes" | pastebinit https://paste.ubuntu.com/p/CJq9YFKmbB/ 2. journal after sudo systemctl hibernate: $ sudo journalctl --since="-5 minutes" | pastebinit https://paste.ubuntu.com/p/432vmz2xqJ/ 3. here is a pastebin from a week ago when I still was trying to use suspend: $ journalctl --boot=-1 | tail -n 2000 | pastebinit https://paste.ubuntu.com/p/QdDYcKGNGw/ **UPDATE 2:** Having now looked at the first and second pastebins, I can see that acpitool takes a much simpler and more direct (close to the metal) approach than does systemctl hibernate. It gets right down to business and by Line 21 is attempting to put the system into sleep state S4, which succeeds. systemctl hibernate on the other hand, does a lot of messing about with the network interface, eventually deciding to wake back up at line 101. I am not sure why it would do this since the point of hibernate is described as turning the machine off once the state is saved. It seems to me that systemctl is sharing code between suspend and hibernate. I am not sure what the intention of the developers was but this seems like a bug to me. The use case of a single user wanting to just save state and then turn the machine off is not properly supported.

I am trying to enable hibernation on a laptop because suspend is too undependable. I have gotten the hibernate command to turn the computer off but it starts back up immediately in something like a suspend mode. It has been suggested to me that I could fix this by disabling the wake-up capability of ACPI devices using the acpitool -W command. But one ACPI device, labeled PXSX, will not be disabled by this command. It continues to show “enabled”. What is PXSX and why would it behave this way? **UPDATE:** Here is the unique part of this question. I did indeed see the other question that this one is said to be a duplicate of. It didn't answer my question and it still doesn't. Here is the list of wakeup-capable devices returned by acpitool: $ acpitool -w | grep enabled 3. PEG1 S4 *enabled pci:0000:00:01.0 7. XHCI S3 *enabled pci:0000:00:14.0 19. RP05 S4 *enabled pci:0000:00:1c.4 27. RP09 S4 *enabled pci:0000:00:1d.0 28. PXSX S4 *enabled pci:0000:20:00.0 35. RP13 S4 *enabled pci:0000:00:1d.4 67. AWAC S4 *enabled platform:ACPI000E:00 68. SLPB S3 *enabled platform:PNP0C0E:00 69. LID S4 *enabled platform:PNP0C0D:00 As can be seen, there are six pci devices listed as enabled for wakeup capability. Of these, only #28 is unable to be disabled by acpitool -W. The rest can be diabled. It's not just a question of what PXSX refers to. **It's also about why this particular device cannot be disabled.** **Update2:** Looking further into this, I can run lscpi against the problematic device. $ lspci | grep 20:00.0 20:00.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Maple Ridge 4C 2020] (rev 02) So, This is an "Intel Corporation Thunderbolt 4 Bridge." Googling that, I find that Thunderbolt is a new super-duper Intel iteration on USB connection technology. It isn't clear to me why such a device needs to resist attempts to deactivate its ability to provide a wakeup functionality. My ultimate goal here is to use hibernation to turn the computer off.

This doesn't happen every time, but sometimes when watching a video, my computer seems to (almost) freeze. The screen changes every few seconds or so. Rebooting fixes the issue until the next time it happens. I noticed that the logs contain the same line every 2 seconds.

Feb 07 09:50:47 spoon kernel: xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot
Feb 07 09:50:44 spoon kernel: xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot
Feb 07 09:50:42 spoon kernel: xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot
Feb 07 09:50:40 spoon kernel: xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot
Feb 07 09:50:38 spoon kernel: xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot

This makes me think it's something to do with overheating, but the computer doesn't even feel warm. On boot, I see the following logs:

Feb 07 09:28:21 spoon kernel: ACPI: thermal: [Firmware Bug]: No valid trip points!
Feb 07 09:28:21 spoon kernel: ACPI: thermal: [Firmware Bug]: Invalid critical threshold (-274000)
Feb 07 09:28:21 spoon kernel: ACPI: thermal: [Firmware Bug]: No valid trip points!
Feb 07 09:28:21 spoon kernel: ACPI: thermal: [Firmware Bug]: Invalid critical threshold (-274000)
Feb 07 09:28:21 spoon kernel: ACPI: thermal: [Firmware Bug]: No valid trip points!
Feb 07 09:28:21 spoon kernel: ACPI: thermal: [Firmware Bug]: Invalid critical threshold (-274000)
Feb 07 09:28:21 spoon kernel: ACPI: thermal: [Firmware Bug]: No valid trip points!
Feb 07 09:28:21 spoon kernel: ACPI: thermal: [Firmware Bug]: Invalid critical threshold (-274000)

Not sure if this is related to the issue. My computer is new, so it shouldn't be because of old parts. Any advice on how I can further debug this? Thanks in advance!

Running Mint 14. Sometimes I can suspend fine, but after my computer is on for a while, it no longer suspends. It wakes up after a second or so without any external inputs. My guess is that I'm monitoring something I don't need to monitor: >cat /proc/acpi/wakeup Device S-state Status Sysfs node LID S4 *enabled SLPB S3 *enabled IGBE S4 *enabled pci:0000:00:19.0 EXP3 S4 *disabled XHCI S3 *enabled pci:0000:00:14.0 EHC1 S3 *enabled pci:0000:00:1d.0 EHC2 S3 *enabled pci:0000:00:1a.0 HDEF S4 *disabled pci:0000:00:1b.0 These devices are rather cryptic. Although it might be interesting to know what the devices are, all I really care about is the one that is causing my computer to wake up (so I can disable monitoring of that device). Is there a log file somewhere that keeps track of ACPI events that would tell me which device woke up my computer?

My Linux laptop (openSUSE Tumbleweed) should hibernate but won't and I do not understand why. I have had similar systems (Arch Linux) hibernate under the same circumstances (LVM on LUKS). Here is my config: - EFI-GRUB boot - LVM on LUKS; LVM has root, home and swap partitions - Swap enabled and mounted by UUID in /etc/fstab, swapon -s shows it being active. It is 32GB in size with 16GB RAM installed. - GRUB has resume statements in the default config and /boot/grub2/grub.cfg (see below). Here are a few commands to check hibernation capabilities of kernel and system: # zgrep HIBERN /proc/config.gz CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_ARCH_HIBERNATION_HEADER=y CONFIG_HIBERNATE_CALLBACKS=y CONFIG_HIBERNATION=y CONFIG_HIBERNATION_SNAPSHOT_DEV=y CONFIG_HIBERNATION_COMP_LZO=y # CONFIG_HIBERNATION_COMP_LZ4 is not set CONFIG_HIBERNATION_DEF_COMP="lzo" So the kernel *is* configured to support hibernation. This boot (by GRUB) has: # cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-6.11.6-2-default root=/dev/mapper/cryptolvm-opensuse splash=silent resume=/dev/mapper/cryptolvm-swap mem_sleep_default=deep security=selinux selinux=1 enforcing=1 mitigations=auto I tried varying resume= using UUID=.... with the swap's UUID with no effect. # cat /sys/power/state freeze mem Here disk is missing but I do not know why. Of course this will not work now: # systemctl hibernate Call to Hibernate failed: Sleep verb 'hibernate' is not configured or configuration is not supported by kernel Exit 1 Does the kernel depend on the BIOS to enable hibernation? (Not to my knowledge.) In this case, can I check something there?

During boot, my Linux system displays the following error messages: [ 0.129513][ T1] ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCO0.1200.TPDO], AE_NOT_FOUND (20230628/dswload2-162) [ 0.129521][ T1] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20230628/psobject-220) [ 0.129543][ T1] ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCO0.1200.TPL1], AE_NOT_FOUND (20230628/dswload2-162) [ 0.129546][ T1] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20230628/psobject-220) These error messages seem to be related to the Advanced Configuration and Power Interface (ACPI) BIOS implementation on my system. ---------- Question 1: What is the cause of this ACPI BIOS error during boot? Question 2: How can I resolve this issue and successfully boot my Linux system without encountering the ACPI BIOS error? Question 3: What are the potential consequences or limitations of the workarounds or solutions suggested for this problem? Question 4: Are there any specific hardware configurations or system setups that are more prone to this type of ACPI BIOS error? Question 5: Is there a way to identify the root cause of the ACPI BIOS issue, such as a specific hardware component or BIOS implementation, to help troubleshoot the problem more effectively? ---------- Please provide a detailed explanation of the ACPI BIOS error, its potential causes, and step-by-step solutions or workarounds to resolve the issue, taking into account the potential trade-offs or limitations of each approach.

I have access to a server and want to check its HMAT table. However, the HMAT table is not present (the SRAT and SLIT are though). I checked the Linux kernel config and the HMAT is enabled (CONFIG_ACPI_HMAT=y and CONFIG_ACPI=y). So probably the issue is with the hardware and firmware. Can I enable the HMAT, and if so, how? Here's the server spec (let me know if more information is needed): $ uname -a Linux node0.acpi-tinkering-0.prismgt-pg0.clemson.cloudlab.us 5.15.0-122-generic #132-Ubuntu SMP Thu Aug 29 13:45:52 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux $ sudo dmidecode -t 2 # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 3.3 present. Handle 0x0200, DMI type 2, 8 bytes Base Board Information Manufacturer: Dell Inc. Product Name: 024PW1 Version: A00 Serial Number: .13D52G3.CNIVC001610605. $ sudo dmidecode -t 0 # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 3.3 present. Handle 0x0000, DMI type 0, 26 bytes BIOS Information Vendor: Dell Inc. Version: 2.8.4 Release Date: 06/23/2022 Address: 0xF0000 Runtime Size: 64 kB ROM Size: 32 MB Characteristics: ISA is supported PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported Japanese floppy for Toshiba 1.2 MB is supported (int 13h) 5.25"/360 kB floppy services are supported (int 13h) 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) CGA/mono video services are supported (int 10h) ACPI is supported USB legacy is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 2.8 sudo dmidecode -t 4 # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 3.3 present. Handle 0x0400, DMI type 4, 48 bytes Processor Information Socket Designation: CPU1 Type: Central Processor Family: Zen Manufacturer: AMD ID: 11 0F A0 00 FF FB 8B 17 Signature: Family 25, Model 1, Stepping 1 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical address extension) MCE (Machine check exception) CX8 (CMPXCHG8 instruction supported) APIC (On-chip APIC hardware supported) SEP (Fast system call) MTRR (Memory type range registers) PGE (Page global enable) MCA (Machine check architecture) CMOV (Conditional move instruction supported) PAT (Page attribute table) PSE-36 (36-bit page size extension) CLFSH (CLFLUSH instruction supported) MMX (MMX technology supported) FXSR (FXSAVE and FXSTOR instructions supported) SSE (Streaming SIMD extensions) SSE2 (Streaming SIMD extensions 2) HTT (Multi-threading) Version: AMD EPYC 7543 32-Core Processor Voltage: 1.8 V External Clock: 16000 MHz Max Speed: 3900 MHz Current Speed: 2800 MHz Status: Populated, Enabled Upgrade: Socket SP3 L1 Cache Handle: 0x0700 L2 Cache Handle: 0x0701 L3 Cache Handle: 0x0702 Serial Number: Not Specified Asset Tag: Not Specified Part Number: Not Specified Core Count: 32 Core Enabled: 32 Thread Count: 64 Characteristics: 64-bit capable Multi-Core Hardware Thread Execute Protection Enhanced Virtualization Handle 0x0401, DMI type 4, 48 bytes Processor Information Socket Designation: CPU2 Type: Central Processor Family: Zen Manufacturer: AMD ID: 11 0F A0 00 FF FB 8B 17 Signature: Family 25, Model 1, Stepping 1 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical address extension) MCE (Machine check exception) CX8 (CMPXCHG8 instruction supported) APIC (On-chip APIC hardware supported) SEP (Fast system call) MTRR (Memory type range registers) PGE (Page global enable) MCA (Machine check architecture) CMOV (Conditional move instruction supported) PAT (Page attribute table) PSE-36 (36-bit page size extension) CLFSH (CLFLUSH instruction supported) MMX (MMX technology supported) FXSR (FXSAVE and FXSTOR instructions supported) SSE (Streaming SIMD extensions) SSE2 (Streaming SIMD extensions 2) HTT (Multi-threading) Version: AMD EPYC 7543 32-Core Processor Voltage: 1.8 V External Clock: 16000 MHz Max Speed: 3900 MHz Current Speed: 2800 MHz Status: Populated, Enabled Upgrade: Socket SP3 L1 Cache Handle: 0x0703 L2 Cache Handle: 0x0704 L3 Cache Handle: 0x0705 Serial Number: Not Specified Asset Tag: Not Specified Part Number: Not Specified Core Count: 32 Core Enabled: 32 Thread Count: 64 Characteristics: 64-bit capable Multi-Core Hardware Thread Execute Protection Enhanced Virtualization