You are not logged in.
I have been getting quite a lot of boot errors on my ThinkPad for a few months now. Found this small script somewhere to filter them out
booterrors() {
local boot=0
if [ ! -z $1 ]
then
boot=$1
fi
printf "\nEmergency level:\n"
journalctl -b "$boot" -p emerg | grep --color=auto --exclude-dir={.bzr,CVS,.git,.hg,.svn,.idea,.tox} -v "Journal begins"
printf "\n\nAlert level:\n"
journalctl -b "$boot" -p alert | grep --color=auto --exclude-dir={.bzr,CVS,.git,.hg,.svn,.idea,.tox} -v "Journal begins"
printf "\n\nCritical level:\n"
journalctl -b "$boot" -p crit | grep --color=auto --exclude-dir={.bzr,CVS,.git,.hg,.svn,.idea,.tox} -v "Journal begins"
printf "\nError level:\n"
journalctl -b "$boot" -p err | grep --color=auto --exclude-dir={.bzr,CVS,.git,.hg,.svn,.idea,.tox} -v "Journal begins"
}
This is from my last boot.
Emergency level:
-- No entries --
Alert level:
-- No entries --
Critical level:
Apr 03 16:39:23 x1-yoga kwin_wayland[972]: kwin_libinput: Libinput: event11 - SYNA8006:00 06CB:CD8B Touchpad: kernel bug: Touch jump detected and discarded.
See https://wayland.freedesktop.org/libinput/doc/1.25.0/touchpad-jumping-cursors.html for details
Apr 04 15:21:19 x1-yoga kwin_wayland[972]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Apr 04 15:21:19 x1-yoga kwin_wayland[972]: kwin_scene_opengl: Can't enable invalid framebuffer object!
Apr 04 15:39:52 x1-yoga kwin_wayland[972]: kwin_libinput: Libinput: event11 - SYNA8006:00 06CB:CD8B Touchpad: kernel bug: Touch jump detected and discarded.
See https://wayland.freedesktop.org/libinput/doc/1.25.0/touchpad-jumping-cursors.html for details
Apr 04 15:53:02 x1-yoga kwin_wayland[972]: kwin_libinput: Libinput: event11 - SYNA8006:00 06CB:CD8B Touchpad: kernel bug: Touch jump detected and discarded.
See https://wayland.freedesktop.org/libinput/doc/1.25.0/touchpad-jumping-cursors.html for details
Apr 04 16:29:08 x1-yoga kwin_wayland[972]: kwin_libinput: Libinput: event11 - SYNA8006:00 06CB:CD8B Touchpad: kernel bug: Touch jump detected and discarded.
See https://wayland.freedesktop.org/libinput/doc/1.25.0/touchpad-jumping-cursors.html for details
Apr 04 23:18:20 x1-yoga kwin_wayland[972]: kwin_libinput: Libinput: event11 - SYNA8006:00 06CB:CD8B Touchpad: kernel bug: Touch jump detected and discarded.
See https://wayland.freedesktop.org/libinput/doc/1.25.0/touchpad-jumping-cursors.html for details
Apr 04 23:18:20 x1-yoga kwin_wayland[972]: kwin_libinput: Libinput: event11 - SYNA8006:00 06CB:CD8B Touchpad: WARNING: log rate limit exceeded (5 msgs per 24h). Discarding future messages.
Apr 04 23:21:50 x1-yoga kwin_wayland[972]: kwin_libinput: Libinput: event20 - Sony Interactive Entertainment DualSense Wireless Controller Touchpad: kernel bug: Touch jump detected and discarded.
See https://wayland.freedesktop.org/libinput/doc/1.25.0/touchpad-jumping-cursors.html for details
Apr 05 21:46:54 x1-yoga kernel: watchdog: watchdog0: watchdog did not stop!
Error level:
Apr 03 00:18:11 x1-yoga kernel: ACPI Error: Needed [Integer/String/Buffer], found [Package] 0000000092912a69 (20230628/exresop-469)
Apr 03 00:18:11 x1-yoga kernel: ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [ToHexString] (20230628/dswexec-433)
Apr 03 00:18:11 x1-yoga kernel: ACPI Error: Aborting method \ADBG due to previous error (AE_AML_OPERAND_TYPE) (20230628/psparse-529)
Apr 03 00:18:11 x1-yoga kernel: ACPI Error: Aborting method \_SB.HIDD._DSM due to previous error (AE_AML_OPERAND_TYPE) (20230628/psparse-529)
Apr 03 00:18:11 x1-yoga kernel: i801_smbus 0000:00:1f.4: Transaction timeout
Apr 03 00:18:11 x1-yoga kernel: i801_smbus 0000:00:1f.4: Failed terminating the transaction
Apr 03 00:18:11 x1-yoga kernel: i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!
Apr 03 00:18:13 x1-yoga kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Apr 03 00:18:21 x1-yoga sddm-helper[887]: gkr-pam: unable to locate daemon control file
Apr 03 16:25:02 x1-yoga kernel: hid-sensor-hub 001F:8087:0AC2.0004: timeout waiting for response from ISHTP device
Apr 03 16:39:23 x1-yoga kwin_wayland[972]: kwin_libinput: Libinput: event11 - SYNA8006:00 06CB:CD8B Touchpad: kernel bug: Touch jump detected and discarded.
See https://wayland.freedesktop.org/libinput/doc/1.25.0/touchpad-jumping-cursors.html for details
Apr 04 15:21:17 x1-yoga kernel: hid-sensor-hub 001F:8087:0AC2.0004: timeout waiting for response from ISHTP device
Apr 04 15:21:19 x1-yoga kwin_wayland[972]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Apr 04 15:21:19 x1-yoga kwin_wayland[972]: kwin_scene_opengl: Can't enable invalid framebuffer object!
Apr 04 15:27:43 x1-yoga kernel: hid-sensor-hub 001F:8087:0AC2.0004: timeout waiting for response from ISHTP device
Apr 04 15:39:52 x1-yoga kwin_wayland[972]: kwin_libinput: Libinput: event11 - SYNA8006:00 06CB:CD8B Touchpad: kernel bug: Touch jump detected and discarded.
See https://wayland.freedesktop.org/libinput/doc/1.25.0/touchpad-jumping-cursors.html for details
Apr 04 15:53:02 x1-yoga kwin_wayland[972]: kwin_libinput: Libinput: event11 - SYNA8006:00 06CB:CD8B Touchpad: kernel bug: Touch jump detected and discarded.
See https://wayland.freedesktop.org/libinput/doc/1.25.0/touchpad-jumping-cursors.html for details
Apr 04 16:29:08 x1-yoga kwin_wayland[972]: kwin_libinput: Libinput: event11 - SYNA8006:00 06CB:CD8B Touchpad: kernel bug: Touch jump detected and discarded.
See https://wayland.freedesktop.org/libinput/doc/1.25.0/touchpad-jumping-cursors.html for details
Apr 04 23:18:20 x1-yoga kwin_wayland[972]: kwin_libinput: Libinput: event11 - SYNA8006:00 06CB:CD8B Touchpad: kernel bug: Touch jump detected and discarded.
See https://wayland.freedesktop.org/libinput/doc/1.25.0/touchpad-jumping-cursors.html for details
Apr 04 23:18:20 x1-yoga kwin_wayland[972]: kwin_libinput: Libinput: event11 - SYNA8006:00 06CB:CD8B Touchpad: WARNING: log rate limit exceeded (5 msgs per 24h). Discarding future messages.
Apr 04 23:19:11 x1-yoga kernel: hid-sensor-hub 001F:8087:0AC2.0004: timeout waiting for response from ISHTP device
Apr 04 23:21:50 x1-yoga kwin_wayland[972]: kwin_libinput: Libinput: event20 - Sony Interactive Entertainment DualSense Wireless Controller Touchpad: kernel bug: Touch jump detected and discarded.
See https://wayland.freedesktop.org/libinput/doc/1.25.0/touchpad-jumping-cursors.html for details
Apr 05 16:49:42 x1-yoga kernel: hid-sensor-hub 001F:8087:0AC2.0004: timeout waiting for response from ISHTP device
Apr 05 21:46:53 x1-yoga dbus-broker-launch[495]: Activation request for 'org.bluez' failed.
Apr 05 21:46:53 x1-yoga dbus-broker-launch[495]: Activation request for 'org.freedesktop.UDisks2' failed.
Apr 05 21:46:53 x1-yoga dbus-broker-launch[495]: Activation request for 'org.freedesktop.UDisks2' failed.
Apr 05 21:46:53 x1-yoga dbus-broker-launch[495]: Activation request for 'org.freedesktop.UDisks2' failed.
Apr 05 21:46:53 x1-yoga dbus-broker-launch[495]: Activation request for 'org.freedesktop.UDisks2' failed.
Apr 05 21:46:53 x1-yoga dbus-broker-launch[495]: Activation request for 'org.freedesktop.UDisks2' failed.
Apr 05 21:46:53 x1-yoga dbus-broker-launch[495]: Activation request for 'org.freedesktop.UDisks2' failed.
Apr 05 21:46:53 x1-yoga dbus-broker-launch[495]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Apr 05 21:46:54 x1-yoga dbus-broker-launch[495]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Apr 05 21:46:54 x1-yoga kernel: watchdog: watchdog0: watchdog did not stop!
I see them every time systemd loads. Quite of a lot of blue messages in between the boot log. The only issue I am really experiencing is that my touchpad sometimes doesn't react after waking up from sleep. Then I have to swipe with the whole finger over the touchpad, as if I would wipe it clean and then it works again. Not sure if this is a hardware issue or caused by the libinput bugs shown in the journal.
I still have half year of warranty on the laptop, so if it is a hardware issue, I would like to find out and get it fixed. I have compared it to my old Dell Precision 5810 desktop, which is showing my a lot more errors when I am using the script. It doesn't show me any errors when booting Arch though like the laptop. It is hard to judge what to ignore.
Last edited by jclsn (2024-04-10 13:28:24)
Offline
Did you read https://wayland.freedesktop.org/libinpu … rsors.html? Seems like it might be relevant.
"It's impossible for a white person to believe in capitalism and not believe in racism. You can't have capitalism without racism."
— Malcolm X
Offline
Yes, I did. My ThinkPad does not have the mentioned touchpad model though and I did not find anything about the touchpad not reacting at all at times.
Apart from that I am also curious about those blue boot error messages. Could it be that they are shown like this in blue to warn about this?
https://docs.kernel.org/admin-guide/hw- … _data.html
https://i.ibb.co/XY3HTTf/IMG-1670.jpg
Last edited by jclsn (2024-04-10 13:23:42)
Offline
The only issue I am really experiencing is that my touchpad sometimes doesn't react after waking up from sleep.
https://wiki.archlinux.org/title/Laptop … nkpad_E440
It doesn't show me any errors when booting Arch though like the laptop
https://wiki.archlinux.org/title/Silent_boot
It is hard to judge what to ignore.
You experience problems => you look up the logs what might have caused them
You look up the logs for errors and warning and try to remove them all
* ACPI errors are common because the firmware is sloppily implemted
* Touchpad jumps are common because it's touchpads - there's no coherent state to track
* dbus-broker is more chatty than dbus-daemon
* You've not installed wireless-regdb and are not https://wiki.archlinux.org/title/Networ … ory_domain - I've already recorded that with the Bundesnetzagentur, they're going to seize your device.
But maybe I can convince them otherwise if you replace the oversized image there w/ a link/thumbnail
Online
I set up the systemd unit and will see if it helps!
So seems the issue with the blue text is just caused by me using systemd-boot now instead of grub2. Grub2 does add quiet and log_level=3 by default. I added those now, but the stale data CPU bug is still there, because it is conisdered quite critical I think. I have another work machine, which is a Dell, where I don't have these issues. I guess Lenovo is really fudging around when it comes to firmware. Was never a fan of Dell, but I have to admit this got me more interested in their product now.
I took care of the wireless regulatory domain and the image.
Thanks!
Offline
https://docs.kernel.org/admin-guide/hw- … _data.html
Because most of the vulnerabilities require the attacker to have access to MMIO, many environments are not affected. System environments using virtualization where MMIO access is provided to untrusted guests may need mitigation.
Otherwise you can issue
mmio_stale_data=off
Online
Thanks for clearing that up.
I just experienced the touchpad not reacting again after waking up. Swiping over the touchpad, makes it work again. Really weird.
Offline
Did you see the link in #4?
lsmod | grep rmi_smbus
Online
Yes, I did and I created the unit proposed. The module is not loaded though.
Ah, there we have it
❯ systemctl status touchpad-after-wake-fix.service
× touchpad-after-wake-fix.service - Run command on resume
Loaded: loaded (/etc/systemd/system/touchpad-after-wake-fix.service; enabled; preset: disabled)
Active: failed (Result: exit-code) since Wed 2024-04-10 23:41:17 CEST; 12min ago
Duration: 22ms
Process: 25546 ExecStart=/bin/bash -c rmmod rmi_smbus && modprobe rmi_smbus (code=exited, status=1/FAILURE)
Main PID: 25546 (code=exited, status=1/FAILURE)
CPU: 13ms
Apr 10 23:41:17 x1-yoga systemd[1]: Started Run command on resume.
Apr 10 23:41:17 x1-yoga bash[25551]: rmmod: ERROR: Module rmi_smbus is not currently loaded
Apr 10 23:41:17 x1-yoga systemd[1]: touchpad-after-wake-fix.service: Main process exited, code=exited, status=1/FAILURE
Apr 10 23:41:17 x1-yoga systemd[1]: touchpad-after-wake-fix.service: Failed with result 'exit-code'.
It wasn't loaded in the first place. I exchanged the && with a ;
Last edited by jclsn (2024-04-10 21:55:26)
Offline
This is some wacom device, right?
lsmod | grep wacom
and you could try to reload those.
Online