Sometimes (frequently) when I power off my laptop it shutdowns normally but the fan does not turn off. To exit this state I have to long-press the power button to turn it off and then I can reboot normally.
Pressing a [Esc] while shutdown it displays
poweroff.target
and turn off. But the fan keeps on running.
Perhaps it’s a hardware feature? I know cars often do this if they’re shut down hot, especially if they have a turbo charger. Does it happen consistently or do you only notice it after shutting down from doing some heavy tasks? Does it eventually shut off after a couple of minutes?
Hello, that might require BIOS update. Post here output of inxi -SsMGaz and last few lines from sudo journalctl -eb-1 from the next boot after it happens.
Are you sure that no power, disk or network activity LEDs are on?
Can you reproduce this issue after shutting down with shutdown now?
Also check temperatures before every shutdown (with sensors or xsensors) to see if it happens only above some thermal threshold.
shutdown now or systemctl poweroff both results in the same output.
And I think it’s not the temperature issue as I have waited for 40+min but the fan does not turn off.
Result of sudo journalctl -eb -1
Aug 21 23:09:50 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4>
Aug 21 23:09:50 fedora systemd[1]: Reached target poweroff.target - System Powe>
Aug 21 23:09:50 fedora systemd[1]: Shutting down.
Aug 21 23:09:50 fedora audit: BPF prog-id=0 op=UNLOAD
Aug 21 23:09:50 fedora audit: BPF prog-id=0 op=UNLOAD
Aug 21 23:09:50 fedora audit: BPF prog-id=0 op=UNLOAD
Aug 21 23:09:50 fedora audit: BPF prog-id=0 op=UNLOAD
Aug 21 23:09:50 fedora audit: BPF prog-id=0 op=UNLOAD
Aug 21 23:09:50 fedora audit: BPF prog-id=0 op=UNLOAD
Aug 21 23:09:50 fedora audit: BPF prog-id=0 op=UNLOAD
Aug 21 23:09:50 fedora audit: BPF prog-id=0 op=UNLOAD
Aug 21 23:09:50 fedora audit: BPF prog-id=0 op=UNLOAD
Aug 21 23:09:50 fedora audit: BPF prog-id=0 op=UNLOAD
Aug 21 23:09:50 fedora audit: BPF prog-id=0 op=UNLOAD
Aug 21 23:09:50 fedora audit: BPF prog-id=0 op=UNLOAD
Aug 21 23:09:50 fedora audit: BPF prog-id=0 op=UNLOAD
Aug 21 23:09:50 fedora audit: BPF prog-id=0 op=UNLOAD
Aug 21 23:09:50 fedora audit: BPF prog-id=0 op=UNLOAD
Aug 21 23:09:50 fedora audit: BPF prog-id=0 op=UNLOAD
Aug 21 23:09:50 fedora systemd-shutdown[1]: Syncing filesystems and block devic>
Aug 21 23:09:52 fedora systemd-shutdown[1]: Sending SIGTERM to remaining proces>
Aug 21 23:09:52 fedora systemd-journald[552]: Received SIGTERM from PID 1 (syst>
Aug 21 23:09:52 fedora systemd-journald[552]: Journal stopped
lines 978-1000/1000 (END)
Aug 21 23:09:50 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-poweroff comm=“systemd” exe>
Aug 21 23:09:50 fedora systemd[1]: Reached target poweroff.target - System Power Off.
Aug 21 23:09:50 fedora systemd[1]: Shutting down.
Aug 21 23:09:50 fedora audit: BPF prog-id=0 op=UNLOAD
Aug 21 23:09:50 fedora audit: BPF prog-id=0 op=UNLOAD
Aug 21 23:09:50 fedora audit: BPF prog-id=0 op=UNLOAD
Aug 21 23:09:50 fedora audit: BPF prog-id=0 op=UNLOAD
Aug 21 23:09:50 fedora audit: BPF prog-id=0 op=UNLOAD
Aug 21 23:09:50 fedora audit: BPF prog-id=0 op=UNLOAD
Aug 21 23:09:50 fedora audit: BPF prog-id=0 op=UNLOAD
Aug 21 23:09:50 fedora audit: BPF prog-id=0 op=UNLOAD
Aug 21 23:09:50 fedora audit: BPF prog-id=0 op=UNLOAD
Aug 21 23:09:50 fedora audit: BPF prog-id=0 op=UNLOAD
Aug 21 23:09:50 fedora audit: BPF prog-id=0 op=UNLOAD
Aug 21 23:09:50 fedora audit: BPF prog-id=0 op=UNLOAD
Aug 21 23:09:50 fedora audit: BPF prog-id=0 op=UNLOAD
Aug 21 23:09:50 fedora audit: BPF prog-id=0 op=UNLOAD
Aug 21 23:09:50 fedora audit: BPF prog-id=0 op=UNLOAD
Aug 21 23:09:50 fedora audit: BPF prog-id=0 op=UNLOAD
Aug 21 23:09:50 fedora systemd-shutdown[1]: Syncing filesystems and block devices.
Aug 21 23:09:52 fedora systemd-shutdown[1]: Sending SIGTERM to remaining processes…
Aug 21 23:09:52 fedora systemd-journald[552]: Received SIGTERM from PID 1 (systemd-shutdow).
Aug 21 23:09:52 fedora systemd-journald[552]: Journal stopped
Result of inxi -SsMGaz
System:
Kernel: 5.18.18-200.fc36.x86_64 arch: x86_64 bits: 64 compiler: gcc
v: 2.37-27.fc36
parameters: BOOT_IMAGE=(hd0,gpt5)/vmlinuz-5.18.18-200.fc36.x86_64
root=UUID=19b4537a-5359-462d-be21-d10c6c20cd7f ro rootflags=subvol=root
rhgb quiet
Desktop: GNOME v: 42.4 tk: GTK v: 3.24.34 wm: gnome-shell dm: GDM v: 42.0
Distro: Fedora release 36 (Thirty Six)
Machine:
Type: Portable System: Dell product: Inspiron 3542 v: N/A
serial: Chassis: type: 8 serial:
Mobo: Dell model: 0926J6 v: A14 serial: UEFI: Dell
v: A14 date: 05/23/2018
Graphics:
Device-1: Intel Haswell-ULT Integrated Graphics vendor: Dell driver: i915
v: kernel arch: Gen7.5 process: Intel 22nm built: 2013 ports:
active: HDMI-A-1 off: eDP-1 empty: none bus-ID: 00:02.0
chip-ID: 8086:0a16 class-ID: 0300
Device-2: NVIDIA GF117M [GeForce 610M/710M/810M/820M / GT
620M/625M/630M/720M]
vendor: Dell driver: nouveau v: kernel non-free: 390.xx+
status: legacy-active (EOL~late 2022) arch: Fermi process: 40/28nm
built: 2010-16 pcie: gen: 1 speed: 2.5 GT/s lanes: 4 link-max: lanes: 8
bus-ID: 08:00.0 chip-ID: 10de:1140 class-ID: 0302
Device-3: Suyin Integrated_Webcam_HD type: USB driver: uvcvideo
bus-ID: 1-1.5:4 chip-ID: 064e:9205 class-ID: 0e02 serial:
Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 22.1.3
compositor: gnome-shell driver: gpu: i915 display-ID: 0
Monitor-1: HDMI-A-1 model: Dell D1920 serial: built: 2011
res: 1366x768 dpi: 85 gamma: 1.2 size: 410x230mm (16.14x9.06")
diag: 470mm (18.5") ratio: 16:9 modes: max: 1366x768 min: 720x400
Monitor-2: eDP-1 model: LG Display 0x0456 built: 2014 res: 1366x768
dpi: 101 gamma: 1.2 size: 344x194mm (13.54x7.64") diag: 395mm (15.5")
ratio: 16:9 modes: 1366x768
OpenGL: renderer: Mesa Intel HD Graphics 4400 (HSW GT2)
v: 4.6 Mesa 22.1.7 direct render: Yes
Sensors:
System Temperatures: cpu: 42.0 C mobo: 42.0 C
Fan Speeds (RPM): cpu: 0
The problem is completely random, but it happens often (maybe 1 out of 3) shutdowns.
I have waited for < 40 min without any result, and had to kill the power.
Looks like it’s related to Intel ME spyware™ https://www.dell.com/community/Laptops-General-Read-Only/Fan-still-works-after-shut-down-Windows-10/td-p/4650438
Downgrading ME firmware to V9.5 or V10 solves the issue.
Do you have Windows installed on this laptop? There you could use official Dell installer.
Try fwupd, maybe it supports ME controller on your device:
fwupdmgr refresh && fwupdmgr get-devices
No i have just Fedora 36, will fwupdmgr refresh && fwupdmgr get-devices do the task or i need to do something else.
This is what i got after running the command
WARNING: UEFI capsule updates not available or enabled in firmware setup
See PluginFlag:capsules unsupported · fwupd/fwupd Wiki · GitHub for more information.
Updating lvfs
Downloading… []
Downloading… []
Successfully downloaded new metadata: 0 local devices supported
WARNING: UEFI capsule updates not available or enabled in firmware setup
See PluginFlag:capsules unsupported · fwupd/fwupd Wiki · GitHub for more information.
Dell Inc. Inspiron 3542
│
├─MQ01ABD100:
│ Device ID: 602b0a6cc821d155208724f0e22f8d111542b74c
│ Summary: ATA drive
│ Current version: AX0P2D
│ Vendor: Toshiba (ATA:0x1179, OUI:000039)
│ Serial Number: 74D6S4WXS
│ GUIDs: 7ac9c029-850d-52b9-a72d-7a8661c4db0d ← IDE\TOSHIBA_MQ01ABD100______________________AX0P2D
│ 17628727-4832-5b2c-af2b-f408e0d99ff7 ← IDE\0TOSHIBA_MQ01ABD100______________________
│ 539bd28f-704f-5906-81b1-08eef8cdd97f ← TOSHIBA MQ01ABD100
│ Device Flags: • Internal device
│ • Updatable
│ • System requires external power source
│ • Needs a reboot after installation
│ • Device is usable for the duration of the update
│
└─UEFI dbx:
Device ID: 362301da643102b9f38477387e2193e57abaa590
Summary: UEFI revocation database
Current version: 85
Minimum Version: 85
Vendor: UEFI:Linux Foundation
Install Duration: 1 second
GUIDs: c6682ade-b5ec-57c4-b687-676351208742 ← UEFI\CRT_A1117F516A32CEFCBA3F2D1ACE10A87972FD6BBE8FE0D0B996E09E65D802A503
f8ba2887-9411-5c36-9cee-88995bb39731 ← UEFI\CRT_A1117F516A32CEFCBA3F2D1ACE10A87972FD6BBE8FE0D0B996E09E65D802A503&ARCH_X64
Device Flags: • Internal device
• Updatable
• Needs a reboot after installation
• Only version upgrades are allowed
• Signed Payload
By the way thanks for the research and time spend by you 