[SOLVED] Weird shutdown and reboot crashes on fresh installation

Gasp0de · 2016-12-27 21:54:16

Hi folks,
I have just installed Arch on my new Dell Latitude E7470, and I'm havin some Issues with it. When I shut down or reboot, it gets stuck at some point, and then takes a long time (30s or so) until it suddenly switches off (it doesn't reboot, it just shuts off, as in crashes). I checked journalctl, but it only shows this error:

Dec 27 22:37:16 gaspodelaptop systemd[1]: Reached target Shutdown.
Dec 27 22:37:16 gaspodelaptop systemd[1]: Reached target Final Step.
Dec 27 22:37:16 gaspodelaptop systemd[1]: Starting Reboot...
Dec 27 22:37:16 gaspodelaptop systemd[1]: Shutting down.
Dec 27 22:37:16 gaspodelaptop systemd[1]: Hardware watchdog 'iTCO_wdt', version 0
Dec 27 22:37:16 gaspodelaptop systemd[1]: Set hardware watchdog to 10min.
Dec 27 22:37:16 gaspodelaptop kernel: watchdog: watchdog0: watchdog did not stop!
Dec 27 22:37:16 gaspodelaptop kernel: systemd-shutdow: 46 output lines suppressed due to ratelimiting
Dec 27 22:37:16 gaspodelaptop systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Dec 27 22:37:16 gaspodelaptop systemd-journald[155]: Journal stopped
-- Reboot --
Dec 27 22:38:40 gaspodelaptop systemd-journald[159]: Time spent on flushing to /var is 966us for 0 entries.
Dec 27 22:38:40 gaspodelaptop kernel: Linux version 4.8.13-1-ARCH (builduser@tobias) (gcc version 6.2.1 20160830 (GCC) ) #1 SMP PREEMPT Fri Dec 9 07:24:34 CET 2016

As you can see, it doesn't really reboot (i waited about a minute before switching it back on), but the only error message is that the watchdog didn't stop. Can you give me tips on how to investigate further? Thank you for your help and patience with me

Gasp0de

Last edited by Gasp0de (2017-01-19 10:32:10)

jasonwryan · 2016-12-27 22:01:03

Not an Installation issue, moving to NC...

seth · 2016-12-28 09:34:50

blacklist the module of the watchdog, unload it, try to reboot, see what happens.

Gasp0de · 2016-12-29 22:11:07

How would I blacklist the watchdog module? I'm sorry for asking so many beginner questions, I did try to google but couldn't find anything helpful

kmod list

Does not give me a module that sounds related to watchdog...

seth · 2016-12-29 22:20:39

Add /etc/modprobe.d/bl_doggy.conf containing:

blacklist iTCO_wdt

This shall unload it:

sudo modprobe -r iTCO_wdt

Gasp0de · 2016-12-29 22:28:50

Ok, so now the watchdog error message is gone, but the laptop still gets stuck on reboot and then shuts down. The last thing it says on the shutdown screen is something like

intel:backlight......

seth · 2016-12-30 09:00:06

Dec 27 22:37:16 gaspodelaptop kernel: systemd-shutdow: 46 output lines suppressed due to ratelimiting

Set "RateLimitIntervalSec" and "RateLimitBurst" to zero in /etc/systemd/journald.conf (notice that this may not work?), reboot and check the journal again. "Something like" a part of a single isn't too helpful ;-)

Gasp0de · 2016-12-31 15:54:23

That doesn't seem to do anything, seems like I have the same problem as the person in the other post. Is there some other way to see shutdown logs? It prints about 5 lines directly before shutting down, but it is way too fast so I can't see more than that it has to do with some backlight...

Gasp0de · 2017-01-05 09:08:25

Something interesting that I found out: When the laptop hangs on reboot (or shutdown), the battery led starts flickering. I had a look in the dell owners manual, and apparently, the flicker code (2 times orange, one time white) means "CPU failure". As I'm relatively sure that my CPU is not broken (since it all works like a charm as long as I dont shut down), might that mean that the linux kernel is using the wrong commands to tell it to switch off, making it crash somehow? I have very little knowledge of all of this. I did do the microcode thing. My CPU is an Intel i-5 6300.

{Ic|cat /proc/cpuinfo} gives me:

[lasse@gaspodelaptop ~]$ cat /proc/cpuinfo
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 78
model name	: Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz
stepping	: 3
microcode	: 0x9e
cpu MHz		: 399.932
cache size	: 3072 KB
physical id	: 0
siblings	: 4
core id		: 0
cpu cores	: 2
apicid		: 0
initial apicid	: 0
fpu		: yes
fpu_exception	: yes
cpuid level	: 22
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch epb intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp
bugs		:
bogomips	: 4993.00
clflush size	: 64
cache_alignment	: 64
address sizes	: 39 bits physical, 48 bits virtual
power management:

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 6
model		: 78
model name	: Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz
stepping	: 3
microcode	: 0x9e
cpu MHz		: 399.932
cache size	: 3072 KB
physical id	: 0
siblings	: 4
core id		: 1
cpu cores	: 2
apicid		: 2
initial apicid	: 2
fpu		: yes
fpu_exception	: yes
cpuid level	: 22
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch epb intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp
bugs		:
bogomips	: 4995.37
clflush size	: 64
cache_alignment	: 64
address sizes	: 39 bits physical, 48 bits virtual
power management:

processor	: 2
vendor_id	: GenuineIntel
cpu family	: 6
model		: 78
model name	: Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz
stepping	: 3
microcode	: 0x9e
cpu MHz		: 399.932
cache size	: 3072 KB
physical id	: 0
siblings	: 4
core id		: 0
cpu cores	: 2
apicid		: 1
initial apicid	: 1
fpu		: yes
fpu_exception	: yes
cpuid level	: 22
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch epb intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp
bugs		:
bogomips	: 4995.01
clflush size	: 64
cache_alignment	: 64
address sizes	: 39 bits physical, 48 bits virtual
power management:

processor	: 3
vendor_id	: GenuineIntel
cpu family	: 6
model		: 78
model name	: Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz
stepping	: 3
microcode	: 0x9e
cpu MHz		: 399.932
cache size	: 3072 KB
physical id	: 0
siblings	: 4
core id		: 1
cpu cores	: 2
apicid		: 3
initial apicid	: 3
fpu		: yes
fpu_exception	: yes
cpuid level	: 22
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch epb intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp
bugs		:
bogomips	: 4995.52
clflush size	: 64
cache_alignment	: 64
address sizes	: 39 bits physical, 48 bits virtual
power management:

binch31 · 2017-01-09 16:39:11

Hi,
I have the same issue with my precision 5510 for few weeks (same crash on reboot and shutdown, same LED flickering plus fans running like crazy) .. However I'm able to read at the 5 lines it prints just before to crash, and these lines are the same as the ones printed in this issue: https://bbs.archlinux.org/viewtopic.php?id=209111
I did some tests on my SSD, and it seems to work pretty well.
As I'm not experiencing this issue with linux-lts, I suspect a kernel bug.
I'm now using the lts kernel until the 4.9 goes out in core hoping the issue will be solved with this new version.

seth · 2017-01-09 16:50:48

I did some tests on my SSD, and it seems to work pretty well.

... famous last words ;-)

check "smartctl -a" and run a self test. The other thread looks horribly like a failing disk (though there the problem remains w/ the lts kernel)

binch31 · 2017-01-10 17:57:35

hehe, yes, these are the tests I did (short, and long), and they both completed without error. Moreover, most of the SMART values are closed to 100.
I should have been more specific but did not want to speak much about these disks issues since I was not totally sure the OP had the same error message.
Just wanted to point out that lts kernel "solved" my issue.

Gasp0de · 2017-01-14 15:28:20

Hi, sorry for the long abscence, i was pretty busy. It seems to be this Bug: https://bugzilla.kernel.org/show_bug.cgi?id=187061. How long will it probably take for Kernel 4.9 to move from testing to stable? Will 4.9-rc7 already be included? Sorry I'm terribly inexperienced with kernel stuff. Is there a (relatively easy) way to use a custom kernel for a while (with the buggy commit reverted)?

Gasp0de · 2017-01-14 15:48:40

I tried linux-lts but it wouldn't boot. It crashed with some CPU-related errors, maybe kernel 4.4 is too old for my CPU? Or is it related to the microcode update? I guess I'll just have to wait until 4.9 becomes the stable kernel.

binch31 · 2017-01-14 17:58:55

Indeed, this seems to be this bug (I have also a samsung SSD as most of impacted people and symptoms seems very close). If lts kernel is not working for you, you could try the mainline kernel in AUR..

seth · 2017-01-14 20:11:11

Gasp0de wrote:

It crashed with some CPU-related errors, maybe kernel 4.4 is too old for my CPU? Or is it related to the microcode update?

"Some" error is related to some™ problem :-P
If you want to know or just assistnace on figuring details, you got to share the actual error message.

loqs · 2017-01-14 22:43:00

Gasp0de wrote:

How long will it probably take for Kernel 4.9 to move from testing to stable?

No timetable is ever provided for such moves

Gasp0de wrote:

Will 4.9-rc7 already be included?

rc is the abbreviation for "release candidate" so any fix from a release candidate should be in the release itself unless it was changed again.

Gasp0de wrote:

Is there a (relatively easy) way to use a custom kernel for a while (with the buggy commit reverted)?

$ git clone https://aur.archlinux.org/linux-git.git
$ cd linux-git

make the following changes in PKGBUILD

_srcname=linux-stable
source=('git+https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git#tag=v4.9.3'

$ makepkg  #see man makepkg for options you may need such as -rs

edit:
spelling

Last edited by loqs (2017-01-14 22:43:31)

Gasp0de · 2017-01-19 10:31:35

Thank you. I installed the kernel 4.9.3 and it solved the problem. Now I just have to remember to use the kernel from core again when it's updated.

Arch Linux

#1 2016-12-27 21:54:16

[SOLVED] Weird shutdown and reboot crashes on fresh installation

#2 2016-12-27 22:01:03

Re: [SOLVED] Weird shutdown and reboot crashes on fresh installation

#3 2016-12-28 09:34:50

Re: [SOLVED] Weird shutdown and reboot crashes on fresh installation

#4 2016-12-29 22:11:07

Re: [SOLVED] Weird shutdown and reboot crashes on fresh installation

#5 2016-12-29 22:20:39

Re: [SOLVED] Weird shutdown and reboot crashes on fresh installation

#6 2016-12-29 22:28:50

Re: [SOLVED] Weird shutdown and reboot crashes on fresh installation

#7 2016-12-30 09:00:06

Re: [SOLVED] Weird shutdown and reboot crashes on fresh installation

#8 2016-12-31 15:54:23

Re: [SOLVED] Weird shutdown and reboot crashes on fresh installation

#9 2017-01-05 09:08:25

Re: [SOLVED] Weird shutdown and reboot crashes on fresh installation

#10 2017-01-09 16:39:11

Re: [SOLVED] Weird shutdown and reboot crashes on fresh installation

#11 2017-01-09 16:50:48

Re: [SOLVED] Weird shutdown and reboot crashes on fresh installation

#12 2017-01-10 17:57:35

Re: [SOLVED] Weird shutdown and reboot crashes on fresh installation

#13 2017-01-14 15:28:20

Re: [SOLVED] Weird shutdown and reboot crashes on fresh installation

#14 2017-01-14 15:48:40

Re: [SOLVED] Weird shutdown and reboot crashes on fresh installation

#15 2017-01-14 17:58:55

Re: [SOLVED] Weird shutdown and reboot crashes on fresh installation

#16 2017-01-14 20:11:11

Re: [SOLVED] Weird shutdown and reboot crashes on fresh installation

#17 2017-01-14 22:43:00

Re: [SOLVED] Weird shutdown and reboot crashes on fresh installation

#18 2017-01-19 10:31:35

Re: [SOLVED] Weird shutdown and reboot crashes on fresh installation

Board footer