I bought a Dell Latitude e7470 recently. I immediately removed the preinstalled Windows 10, and installed Arch Linux.
It works fine, except for one thing: On shutdown or reboot, at the point where the pc would usually switch off (all processes ended, etc.), the laptop just hangs for around 30-60 secs. While it hangs, the battery led flickers in a pattern that, according to Dell's owners manual, signals "CPU failure". After the 30-60 secs, the fan spins up to max rpm, and then the system crashes (just shuts off, doesn't reboot until I press the power button again).
I suspect that somehow, the linux kernel issues the wrong shutdown command to the cpu, but I have very little knowledge on how to figure this out. Can anyone give me any tips on this? The cpu is an i-5 6300.
journalctl -p err
gives me
-- Reboot --
Jan 07 21:11:13 gaspodelaptop systemd-udevd[207]: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument
Jan 07 21:11:13 gaspodelaptop kernel: dell_laptop: Setting old previous keyboard state failed
Jan 07 21:11:14 gaspodelaptop kernel: Bluetooth: hci0: Setting Intel event mask failed (-16)
Jan 08 01:49:19 gaspodelaptop gnome-session-binary[569]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jan 08 01:49:19 gaspodelaptop gnome-session-binary[569]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jan 08 01:49:19 gaspodelaptop gnome-session-binary[569]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jan 08 01:49:19 gaspodelaptop gnome-session-binary[569]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jan 08 01:49:19 gaspodelaptop gnome-session-binary[569]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jan 08 01:49:20 gaspodelaptop gnome-session-binary[569]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jan 08 01:49:20 gaspodelaptop gnome-session-binary[569]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jan 08 01:49:20 gaspodelaptop gnome-session-binary[569]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jan 08 01:49:20 gaspodelaptop gnome-session-binary[569]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jan 08 01:49:20 gaspodelaptop gnome-session-binary[569]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jan 08 01:49:22 gaspodelaptop gdm[357]: GLib: g_hash_table_find: assertion 'version == hash_table->version' failed
-- Reboot --
Output of dmesg | grep microcode
:
[ 0.878621] microcode: sig=0x406e3, pf=0x80, revision=0x9e
[ 0.878759] microcode: Microcode Update Driver: v2.01 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
UPDATE: It seems to be a kernel issue. After investigating my suspicion of the SSD, I stumbled upon this forum post. In there it is mentioned that it's a kernel Bug that is already being fixed. According to this Bugreport, it's going to be fixed in Kernel 4.9-rc7. I guess i will have to wait a while, but since I am on Arch Linux, it shouldn't take too long. I know I could also compile my own kernel, but I'm too lazy (or better: too busy with other things) for that. Guess I'll just use standby a lot.
journalctl -p err
? – Michael D. Jan 7 '17 at 22:44