Hi all,
currently I experience a sudden shutdown with a restart on my box.
One time this happened again and again in a loop.
Today this happened once, while I was just reading a website (no interaction in that moment).
Which logs do I have to inspect first in order to finding out whether this is a HW problem and which component is the root cause?
Can this also be a SW related problem?
This could be many things
power supply - bad/going bad
memory - bad/going bad
heat - bad/going bad - fans on cpu/video/case going bad
memory timings were accidentally changed in bios
cpu settings were accidentally changed in bios
Zitat von: mylo in 2013/11/02, 12:37:36
Which logs do I have to inspect first in order to finding out whether this is a HW problem and which component is the root cause?
I would inspect
/var/log/dmesg*
/var/log/messages*
Zitat von: mylo in 2013/11/02, 12:37:36Can this also be a SW related problem?
Maybe. If you have watchdog or something like that installed, it might be rebooting your computer for some reason.
Hi all,
/var/log/messages provides me:
Nov 15 21:38:49 tuap kernel: [ 23.978377] Bluetooth: BNEP filters: protocol multicast
Nov 15 21:38:49 tuap kernel: [ 23.978387] Bluetooth: BNEP socket layer initialized
Nov 15 21:38:49 tuap kernel: [ 23.978501] Bluetooth: RFCOMM TTY layer initialized
Nov 15 21:38:49 tuap kernel: [ 23.978508] Bluetooth: RFCOMM socket layer initialized
Nov 15 21:38:49 tuap kernel: [ 23.978510] Bluetooth: RFCOMM ver 1.11
Nov 15 21:38:50 tuap kernel: [ 24.959457] lp0: using parport0 (interrupt-driven).
Nov 15 21:38:50 tuap kernel: [ 24.959461] lp0: console ready
Nov 15 21:38:50 tuap kernel: [ 25.006908] ppdev: user-space parallel port driver
Nov 15 21:38:51 tuap /usr/sbin/gpm[2622]: *** info [daemon/startup.c(131)]:
Nov 15 21:38:51 tuap /usr/sbin/gpm[2622]: Started gpm successfully. Entered daemon mode.
Nov 15 21:38:53 tuap kernel: [ 27.158307] r8169 0000:03:00.0 eth0: link down
Nov 15 21:38:53 tuap kernel: [ 27.158315] r8169 0000:03:00.0 eth0: link down
Nov 15 21:38:53 tuap kernel: [ 27.158340] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Nov 15 21:38:54 tuap kernel: [ 28.802612] r8169 0000:03:00.0 eth0: link up
Nov 15 21:38:54 tuap kernel: [ 28.802625] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Nov 15 21:38:54 tuap kernel: [ 29.125887] NET: Registered protocol family 17
Nov 15 21:39:08 tuap org.kde.powerdevil.backlighthelper: QDBusConnection: system D-Bus connection created before QCoreApplication. Application may misbehave.
Nov 15 21:44:11 tuap kernel: [ 346.965438] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
The sudden shutdown was 21:39 h.
/var/log/dmesg does not show any irregularities.
Is it the power supply? Temperatures seem ok, so there cannot be a fan problem.
Zitat von: mylo in 2013/11/15, 21:59:08
Is it the power supply?
It could be. When a PSU develops an intermittent "open", it is like pulling the plug from the wall -- there is no electricity so there is no ability for the system to record a message.
ZitatTemperatures seem ok, so there cannot be a fan problem.
You are able to see the CPU internal temp? And it is not going way up over 75C or anything like that?
Hi dibl,
the temperatures for the two cores, the motherboard and the cpu are all below 50 °C.
Try to run memtest. Maybe a mem problem, but when the computer suddenly shuts down during memtest, i'd think it is an hardware problem.