You are not logged in.
Pages: 1
Recently (say from a week or so), it happened 3-4 times that my t460s freezes while doing simple tasks, becoming unresponsive with the caps lock key blinking, and I had to power it off by hand. I cannot see anything with
journalctl -p 3 -b -2 Where should I look for hints?
Last edited by olocin (2018-04-07 15:16:52)
Offline
Drop the -p3 relevant errors might not always have the priority flags set
Offline
Even w/out, the command
journalctl -b -2 does not have entries for today (when the issue happened), most recent one is from yesterday.
Last edited by olocin (2018-04-07 15:49:15)
Offline
Well that -b switch shows the two previous boots, so if it froze and you are now in your second boot after the freeze you will want to use -b -1
Last edited by V1del (2018-04-07 15:56:20)
Offline
Thanks. Here's the output of the correct command: can you see anything relevant?
Apr 07 16:46:40 kernel: Freezing user space processes ... (elapsed 0.002 seconds) done.
Apr 07 16:46:40 kernel: OOM killer disabled.
Apr 07 16:46:40 kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Apr 07 16:46:40 kernel: Suspending console(s) (use no_console_suspend to debug)
Apr 07 16:46:40 kernel: ipheth 1-4:4.2: Apple iPhone USB Ethernet now disconnected
Apr 07 16:46:40 kernel: e1000e: EEE TX LPI TIMER: 00000011
Apr 07 16:46:40 kernel: ACPI: Preparing to enter system sleep state S3
Apr 07 16:46:40 kernel: ACPI: EC: event blocked
Apr 07 16:46:40 kernel: ACPI: EC: EC stopped
Apr 07 16:46:40 kernel: PM: Saving platform NVS memory
Apr 07 16:46:40 kernel: Disabling non-boot CPUs ...
Apr 07 16:46:40 kernel: smpboot: CPU 1 is now offline
Apr 07 16:46:40 kernel: smpboot: CPU 2 is now offline
Apr 07 16:46:40 kernel: smpboot: CPU 3 is now offline
Apr 07 16:46:40 kernel: ACPI: Low-level resume complete
Apr 07 16:46:40 kernel: ACPI: EC: EC started
Apr 07 16:46:40 kernel: PM: Restoring platform NVS memory
Apr 07 16:46:40 kernel: Enabling non-boot CPUs ...
Apr 07 16:46:40 kernel: x86: Booting SMP configuration:
Apr 07 16:46:40 kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Apr 07 16:46:40 kernel: cache: parent cpu1 should not be sleeping
Apr 07 16:46:40 kernel: CPU1 is up
Apr 07 16:46:40 kernel: smpboot: Booting Node 0 Processor 2 APIC 0x1
Apr 07 16:46:40 kernel: cache: parent cpu2 should not be sleeping
Apr 07 16:46:40 kernel: CPU2 is up
Apr 07 16:46:40 kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
Apr 07 16:46:40 kernel: cache: parent cpu3 should not be sleeping
Apr 07 16:46:40 kernel: CPU3 is up
Apr 07 16:46:40 kernel: ACPI: Waking up from system sleep state S3
Apr 07 16:46:40 kernel: ACPI: EC: event unblocked
Apr 07 16:46:40 kernel: usb 1-5: reset full-speed USB device number 3 using xhci_hcd
Apr 07 16:46:40 kernel: usb 1-7: reset full-speed USB device number 4 using xhci_hcd
Apr 07 16:46:40 kernel: thinkpad_acpi: EC reports that Thermal Table has changed
Apr 07 16:46:40 kernel: thinkpad_acpi: EC reports that Thermal Table has changed
Apr 07 16:46:40 kernel: usb 1-8: reset high-speed USB device number 5 using xhci_hcd
Apr 07 16:46:40 kernel: psmouse serio1: synaptics: queried max coordinates: x [..5676], y [..4762]
Apr 07 16:46:40 kernel: psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1094..]
Apr 07 16:46:40 kernel: usb 1-7:1.0: rebind failed: -517
Apr 07 16:46:40 kernel: usb 1-7:1.1: rebind failed: -517
Apr 07 16:46:40 kernel: usb 1-4:4.2: rebind failed: -517
Apr 07 16:46:40 kernel: OOM killer enabled.
Apr 07 16:46:40 kernel: Restarting tasks ...
Apr 07 16:46:40 kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
Apr 07 16:46:40 kernel: done.
Apr 07 16:46:40 kernel: ipheth 1-4:4.2: Apple iPhone USB Ethernet device attached
Apr 07 16:46:40 kernel: Bluetooth: hci0: Device revision is 5
Apr 07 16:46:40 kernel: Bluetooth: hci0: Secure boot is enabled
Apr 07 16:46:40 kernel: Bluetooth: hci0: OTP lock is enabled
Apr 07 16:46:40 kernel: Bluetooth: hci0: API lock is enabled
Apr 07 16:46:40 kernel: Bluetooth: hci0: Debug lock is disabled
Apr 07 16:46:40 kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Apr 07 16:46:40 kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
Apr 07 16:46:40 systemd-logind[415]: Lid opened.
Apr 07 16:46:40 NetworkManager[416]: <info> [1523112400.1752] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/12)
Apr 07 16:46:40 kernel: thermal thermal_zone3: failed to read out thermal zone (-61)
Apr 07 16:46:40 upowerd[6585]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:4.2
Apr 07 16:46:40 systemd[1]: bluetooth.target: Unit not needed anymore. Stopping.
Apr 07 16:46:40 systemd[1]: Stopped target Bluetooth.
Apr 07 16:46:40 upowerd[6585]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.1
Apr 07 16:46:40 upowerd[6585]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.1
Apr 07 16:46:40 upowerd[6585]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0
Apr 07 16:46:40 systemd-udevd[28429]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Apr 07 16:46:40 kernel: ipheth 1-4:4.2 enp0s20f0u4c4i2: renamed from eth0
Apr 07 16:46:40 systemd[1]: Reached target Bluetooth.
Apr 07 16:46:40 upowerd[6585]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0
Apr 07 16:46:40 upowerd[6585]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:4.2
Apr 07 16:46:40 systemd-sleep[28416]: System resumed.
Apr 07 16:46:40 kernel: PM: suspend exit
Apr 07 16:46:40 systemd[1]: Started Suspend.
Apr 07 16:46:40 systemd[1]: sleep.target: Unit not needed anymore. Stopping.
Apr 07 16:46:40 systemd[1]: Stopped target Sleep.
Apr 07 16:46:40 systemd[1]: tlp-sleep.service: Unit not needed anymore. Stopping.
Apr 07 16:46:40 systemd[1]: Stopping TLP suspend/resume...
Apr 07 16:46:40 systemd[1]: Reached target Suspend.
Apr 07 16:46:40 systemd[1]: suspend.target: Unit not needed anymore. Stopping.
Apr 07 16:46:40 systemd[1]: Stopped target Suspend.
Apr 07 16:46:40 systemd-logind[415]: Operation 'sleep' finished.
Apr 07 16:46:40 kernel: IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready
Apr 07 16:46:40 NetworkManager[416]: <info> [1523112400.2130] manager: sleep: wake requested (sleeping: yes enabled: yes)
Apr 07 16:46:40 NetworkManager[416]: <info> [1523112400.2131] device (enp0s31f6): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed')
Apr 07 16:46:40 systemd-udevd[28430]: Process '/usr/bin/tlp auto' failed with exit code 4.
Apr 07 16:46:40 kernel: IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready
Apr 07 16:46:40 NetworkManager[416]: <info> [1523112400.4121] device (wlp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed')
Apr 07 16:46:40 kernel: IPv6: ADDRCONF(NETDEV_UP): wlp4s0: link is not ready
Apr 07 16:46:40 NetworkManager[416]: <info> [1523112400.4137] device (wlp4s0): set-hw-addr: set MAC address to 5A:8B:3E:58:17:75 (scanning)
Apr 07 16:46:40 NetworkManager[416]: <info> [1523112400.4146] device (enp0s20f0u4c4i2): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Apr 07 16:46:40 kernel: IPv6: ADDRCONF(NETDEV_UP): enp0s20f0u4c4i2: link is not ready
Apr 07 16:46:40 kernel: IPv6: ADDRCONF(NETDEV_UP): enp0s20f0u4c4i2: link is not ready
Apr 07 16:46:40 NetworkManager[416]: <info> [1523112400.4177] manager: NetworkManager state is now DISCONNECTED
Apr 07 16:46:40 systemd[1]: Stopped TLP suspend/resume.
Apr 07 16:46:40 kernel: [drm] RC6 on
Apr 07 16:46:41 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp0s20f0u4c4i2: link becomes ready
Apr 07 16:46:41 NetworkManager[416]: <info> [1523112401.7234] device (enp0s20f0u4c4i2): carrier: link connected
Apr 07 16:46:41 NetworkManager[416]: <info> [1523112401.7249] device (enp0s20f0u4c4i2): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Apr 07 16:46:41 NetworkManager[416]: <info> [1523112401.7268] policy: auto-activating connection 'ethernet'
Apr 07 16:46:41 NetworkManager[416]: <info> [1523112401.7294] device (enp0s20f0u4c4i2): Activation: starting connection 'ethernet' (f8617ee6-8f3d-4457-b6c4-668172164a72)
Apr 07 16:46:41 NetworkManager[416]: <info> [1523112401.7301] device (enp0s20f0u4c4i2): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Apr 07 16:46:41 NetworkManager[416]: <info> [1523112401.7307] manager: NetworkManager state is now CONNECTING
Apr 07 16:46:41 NetworkManager[416]: <info> [1523112401.7320] device (enp0s20f0u4c4i2): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Apr 07 16:46:41 NetworkManager[416]: <info> [1523112401.7337] device (enp0s20f0u4c4i2): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Apr 07 16:46:41 NetworkManager[416]: <info> [1523112401.7346] dhcp4 (enp0s20f0u4c4i2): activation: beginning transaction (timeout in 45 seconds)
Apr 07 16:46:41 kernel: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS.
Apr 07 16:46:41 kernel: Bluetooth: hci0: Waiting for firmware download to complete
Apr 07 16:46:41 kernel: Bluetooth: hci0: Firmware loaded in 1776767 usecs
Apr 07 16:46:41 kernel: Bluetooth: hci0: Waiting for device to boot
Apr 07 16:46:42 kernel: Bluetooth: hci0: Device booted in 15699 usecs
Apr 07 16:46:42 kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
Apr 07 16:46:42 kernel: Bluetooth: hci0: Applying Intel DDC parameters completed
Apr 07 16:46:43 NetworkManager[416]: <info> [1523112403.5158] dhcp4 (enp0s20f0u4c4i2): address 172.20.10.3
Apr 07 16:46:43 NetworkManager[416]: <info> [1523112403.5159] dhcp4 (enp0s20f0u4c4i2): plen 28
Apr 07 16:46:43 NetworkManager[416]: <info> [1523112403.5159] dhcp4 (enp0s20f0u4c4i2): expires in 85536 seconds
Apr 07 16:46:43 NetworkManager[416]: <info> [1523112403.5160] dhcp4 (enp0s20f0u4c4i2): nameserver '172.20.10.1'
Apr 07 16:46:43 NetworkManager[416]: <info> [1523112403.5160] dhcp4 (enp0s20f0u4c4i2): gateway 172.20.10.1
Apr 07 16:46:43 NetworkManager[416]: <info> [1523112403.5495] dhcp4 (enp0s20f0u4c4i2): state changed unknown -> bound
Apr 07 16:46:43 NetworkManager[416]: <info> [1523112403.5520] device (enp0s20f0u4c4i2): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Apr 07 16:46:43 NetworkManager[416]: <info> [1523112403.5541] device (enp0s20f0u4c4i2): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Apr 07 16:46:43 NetworkManager[416]: <info> [1523112403.5546] device (enp0s20f0u4c4i2): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Apr 07 16:46:43 NetworkManager[416]: <info> [1523112403.5547] manager: NetworkManager state is now CONNECTED_LOCAL
Apr 07 16:46:43 NetworkManager[416]: <info> [1523112403.5602] manager: NetworkManager state is now CONNECTED_SITE
Apr 07 16:46:43 NetworkManager[416]: <info> [1523112403.5605] policy: set 'ethernet' (enp0s20f0u4c4i2) as default for IPv4 routing and DNS
Apr 07 16:46:43 NetworkManager[416]: <info> [1523112403.5666] device (enp0s20f0u4c4i2): Activation: successful, device activated.
Apr 07 16:46:43 nm-dispatcher[28295]: req:3 'up' [enp0s20f0u4c4i2]: new request (1 scripts)
Apr 07 16:46:43 nm-dispatcher[28295]: req:3 'up' [enp0s20f0u4c4i2]: start running ordered scripts...
Apr 07 16:46:46 NetworkManager[416]: <info> [1523112406.6589] manager: NetworkManager state is now CONNECTED_GLOBAL
Apr 07 16:46:46 nm-dispatcher[28295]: req:4 'connectivity-change': new request (1 scripts)
Apr 07 16:46:46 nm-dispatcher[28295]: req:4 'connectivity-change': start running ordered scripts...
Apr 07 16:46:48 sudo[28621]: redc : TTY=unknown ; PWD=/home/redc ; USER=root ; COMMAND=/usr/local/bin/brightness up
Apr 07 16:46:48 sudo[28621]: pam_unix(sudo:session): session opened for user root by (uid=0)
Apr 07 16:46:48 sudo[28621]: pam_unix(sudo:session): session closed for user root
Apr 07 16:46:48 sudo[28626]: redc : TTY=unknown ; PWD=/home/redc ; USER=root ; COMMAND=/usr/local/bin/brightness up
Apr 07 16:46:48 sudo[28626]: pam_unix(sudo:session): session opened for user root by (uid=0)
Apr 07 16:46:48 sudo[28626]: pam_unix(sudo:session): session closed for user root
Apr 07 16:46:49 sudo[28631]: redc : TTY=unknown ; PWD=/home/redc ; USER=root ; COMMAND=/usr/local/bin/brightness up
Apr 07 16:46:49 sudo[28631]: pam_unix(sudo:session): session opened for user root by (uid=0)
Apr 07 16:46:49 sudo[28631]: pam_unix(sudo:session): session closed for user root
Apr 07 16:46:51 sudo[28644]: redc : TTY=pts/1 ; PWD=/home/redc ; USER=root ; COMMAND=/usr/bin/pacman -Syu
Apr 07 16:46:51 sudo[28644]: pam_unix(sudo:session): session opened for user root by redc(uid=0)
Apr 07 16:47:07 gnome-keyring-daemon[851]: asked to register item /org/freedesktop/secrets/collection/login/13, but it's already registered
Apr 07 16:47:07 gnome-keyring-daemon[851]: asked to register item /org/freedesktop/secrets/collection/login/13, but it's already registeredOffline
What kind of thinkpad and how many times does capslock blink?
Offline
it's a t460s, and when it becomes unresponsive, capslock just blinks indefinitely, until I force restart.
Offline
Sounds like a halted kernel - you won't get output in the logs in that case. Did it happen right after the S3 cycle?
What changed about the time this started (check your pacman log for kernel? updates in the relevant time frame)
Also TLP is probably prone to cause this, try to disable it and watch whether the problem remains.
Offline
it's a t460s, and when it becomes unresponsive, capslock just blinks indefinitely, until I force restart.
I agree with Seth. It is almost certainly a kernel panic https://en.wikipedia.org/wiki/Kernel_panic#Linux
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
Right, it's likely to be a kernel panic. TLP has been running ever since, but I cannot see its upgrades in the relevant time frame, while there are a few kernel upgrades.
Is there a way to pin down the forced reboots in the journal, so that I can try to match the first kernel panic with kernel upgrade?
Offline
I forgot to mention that the image of whatever I am doing persists frozen on the screen.
Offline
A clean reboot will usually end with some "systemd-journald[123]: Journal stopped" entry.
So every "-- Reboot --" line that does not follow such entry is suspicious for a hard reboot.
Offline
it's a t460s, and when it becomes unresponsive, capslock just blinks indefinitely, until I force restart.
Does the freezing and unresponsiveness come after you closing your lid or let the computer go to sleep?
Last edited by obrienanthonyt (2018-04-09 15:58:45)
Offline
it came (in 3-4 occasions) after resuming from s3, say 10 seconds after.
Offline
it came (in 3-4 occasions) after resuming from s3, say 10 seconds after.
Can you check to make sure you ram and hard drive is okay ? You can make a usb with
Hiren's boot cd and it has memtest and partedmagic with software to check error logs.
That's if you don't want to install new software for the hard drive testing.
Offline
If S3 half-wise reliably triggers this, I'd suggest to switch to TTY1 everytime before going S3 and briefly wait there after a resume - in "hope" that the kernel halts and you get some error messages on screen.
https://wiki.archlinux.org/index.php/Ge … nel_panics
You could also try whether the problem can be reproduced w/ the LTS kernel.
Unfortunately, debugging this kind of thing is pretty much a PITA (https://wiki.archlinux.org/index.php/Kdump)
Offline
it came (in 3-4 occasions) after resuming from s3, say 10 seconds after.
Since your laptop comes with an opal ssd, do you have acpid installed? Also are you encrypting
your drives?
Offline
I didn't know about it, now it is installed. I'm not encrypting at present.
Offline
I didn't know about it, now it is installed. I'm not encrypting at present.
You're ssd can probably self encrypt, depending on the model. You can check to see if it self
encrypts, the kernel may not be able to handle the self encrypting feature correctly.
From what I have read, opal and sleep function do not work correctly. This link still shows
that there is an issue with sleep and opal as well as self encrypting.
https://github.com/Drive-Trust-Alliance … /issues/90
Last edited by obrienanthonyt (2018-04-10 00:20:11)
Offline
It actually self encrypts, but I think the kernel can handle both sleep and self encrypt well, at least until a few weeks ago ![]()
Now they have updated again the kernel, and I stopped connecting my iphone to the laptop via usb, and had no more kernel panics.
I will wait to see if it happens again.
Offline
Pages: 1