[SOLVED]System freezing and possibly having heat sensor issue.[SOLVED]

Questions about hardware and drivers
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
KingdomB
Level 1
Level 1
Posts: 47
Joined: Sat Jun 22, 2019 12:22 pm

[SOLVED]System freezing and possibly having heat sensor issue.[SOLVED]

Post by KingdomB »

LAPTOP: Lenovo Legion Y540 17
I am relatively new to Linux despite using it for four years now. Recently after updating, my system has started to freeze and I am not sure about the cause. Someone suggested that there may be a temperature issue based on some of the info in my Syslog. Once the system freezes I have to reboot via the power button.
I switched to Ubuntu for a while, thinking that that might solve the issue, but it seemed to have gotten worse. Now I reinstalled Mint 21 and it is still happening.
Below is a Google doc link to my most recent syslog in text format. The freeze happened around 7/25 11:06 PM but I am not certain that high temp was the cause. All help is greatly appreciated.

7-25_full_syslog

Adding a small snippet below of the syslog since no one has responded. I have no idea what I am looking at but hopefully, this snippet will pique someone's interest. There is a section about temp sensors that are missing or malfunctioning? The entire log is in the linked file, but I guess maybe no one wants to download a file into their system from an unknown source. Hope this helps.

I am also attaching the file here. Something that I wasn't aware that I could do when I originally posted.

Thanks

Code: Select all

Jul 25 23:06:49 kby540 systemd[1]: Mounted Arbitrary Executable File Formats File System.
Jul 25 23:06:49 kby540 NetworkManager[791]: <info>  [1690340809.5310] modem-manager: ModemManager available
Jul 25 23:06:49 kby540 snapd[805]: overlord.go:272: Acquiring state lock file
Jul 25 23:06:49 kby540 snapd[805]: overlord.go:277: Acquired state lock file
Jul 25 23:06:49 kby540 NetworkManager[791]: <info>  [1690340809.6512] device (wlp0s20f3): supplicant interface state: internal-starting -> disconnected
Jul 25 23:06:49 kby540 NetworkManager[791]: <info>  [1690340809.6513] Wi-Fi P2P device controlled by interface wlp0s20f3 created
Jul 25 23:06:49 kby540 NetworkManager[791]: <info>  [1690340809.6515] manager: (p2p-dev-wlp0s20f3): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/4)
Jul 25 23:06:49 kby540 NetworkManager[791]: <info>  [1690340809.6517] device (p2p-dev-wlp0s20f3): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jul 25 23:06:49 kby540 NetworkManager[791]: <info>  [1690340809.6522] device (wlp0s20f3): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Jul 25 23:06:49 kby540 NetworkManager[791]: <info>  [1690340809.6526] device (p2p-dev-wlp0s20f3): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Jul 25 23:06:49 kby540 NetworkManager[791]: <warn>  [1690340809.6532] sup-iface[68db1ea26644c8e2,0,wlp0s20f3]: call-p2p-cancel: failed with P2P cancel failed
Jul 25 23:06:49 kby540 snapd[805]: daemon.go:247: started snapd/2.59.5 (series 16; classic; devmode) linuxmint/5 (amd64) linux/5.10.0-23-amd64.
Jul 25 23:06:49 kby540 systemd[1]: tmp-syscheck\x2dmountpoint\x2d193657252.mount: Succeeded.
Jul 25 23:06:49 kby540 snapd[805]: daemon.go:340: adjusting startup timeout by 40s (pessimistic estimate of 30s plus 5s per snap)
Jul 25 23:06:49 kby540 snapd[805]: backends.go:58: AppArmor status: apparmor is enabled but some kernel features are missing: dbus, network
Jul 25 23:06:49 kby540 systemd[1]: snapd.service: Got notification message from PID 1012, but reception only permitted for main PID 805
Jul 25 23:06:49 kby540 systemd[1]: Started Snap Daemon.
Jul 25 23:06:49 kby540 systemd[1]: Starting Wait until snapd is fully seeded...
Jul 25 23:06:49 kby540 dbus-daemon[789]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.21' (uid=0 pid=805 comm="/usr/lib/snapd/snapd ")
Jul 25 23:06:49 kby540 systemd[1]: Starting Time & Date Service...
Jul 25 23:06:49 kby540 dbus-daemon[789]: [system] Successfully activated service 'org.freedesktop.timedate1'
Jul 25 23:06:49 kby540 systemd[1]: Started Time & Date Service.
Jul 25 23:06:49 kby540 avahi-daemon[782]: Server startup complete. Host name is kby540.local. Local service cookie is 4049853335.
Jul 25 23:06:49 kby540 dbus-daemon[789]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service' requested by ':1.23' (uid=0 pid=820 comm="/usr/sbin/thermald --systemd --dbus-enable --adapt")
Jul 25 23:06:49 kby540 systemd[1]: Starting Daemon for power management...
Jul 25 23:06:50 kby540 dbus-daemon[789]: [system] Successfully activated service 'org.freedesktop.UPower'
Jul 25 23:06:50 kby540 systemd[1]: Started Daemon for power management.
Jul 25 23:06:50 kby540 thermald[820]: 22 CPUID levels; family:model:stepping 0x6:9e:a (6:158:10)
Jul 25 23:06:50 kby540 thermald[820]: Polling mode is enabled: 4
Jul 25 23:06:50 kby540 thermald[820]: sensor id 13 : No temp sysfs for reading raw temp
Jul 25 23:06:50 kby540 thermald[820]: sensor id 13 : No temp sysfs for reading raw temp
Jul 25 23:06:50 kby540 thermald[820]: sensor id 13 : No temp sysfs for reading raw temp
Jul 25 23:06:50 kby540 systemd[1]: Finished Wait until snapd is fully seeded.
Jul 25 23:06:50 kby540 systemd[1]: Created slice User Slice of UID 122.
Jul 25 23:06:50 kby540 systemd[1]: Starting User Runtime Directory /run/user/122...
Jul 25 23:06:50 kby540 systemd[1]: Finished User Runtime Directory /run/user/122.
Jul 25 23:06:50 kby540 systemd[1]: Starting User Manager for UID 122...
Jul 25 23:06:50 kby540 systemd[1070]: Queued start job for default target Main User Target.
Jul 25 23:06:50 kby540 systemd[1070]: Created slice User Application Slice.
Jul 25 23:06:50 kby540 systemd[1070]: Reached target Paths.
Jul 25 23:06:50 kby540 systemd[1070]: Reached target Timers.
Jul 25 23:06:50 kby540 systemd[1070]: Starting D-Bus User Message Bus Socket.
Jul 25 23:06:50 kby540 systemd[1070]: Listening on GnuPG network certificate management daemon.
Jul 25 23:06:50 kby540 systemd[1070]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jul 25 23:06:50 kby540 systemd[1070]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Jul 25 23:06:50 kby540 systemd[1070]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Jul 25 23:06:50 kby540 systemd[1070]: Listening on GnuPG cryptographic agent and passphrase cache.
Jul 25 23:06:50 kby540 systemd[1070]: Listening on Multimedia System.
Jul 25 23:06:50 kby540 systemd[1070]: Listening on debconf communication socket.
Jul 25 23:06:50 kby540 systemd[1070]: Listening on Sound System.
Jul 25 23:06:50 kby540 systemd[1070]: Listening on REST API socket for snapd user session agent.
Jul 25 23:06:50 kby540 systemd[1070]: Listening on D-Bus User Message Bus Socket.
Jul 25 23:06:50 kby540 systemd[1070]: Reached target Sockets.
Jul 25 23:06:50 kby540 systemd[1070]: Reached target Basic System.
Jul 25 23:06:50 kby540 systemd[1]: Started User Manager for UID 122.
Jul 25 23:06:50 kby540 systemd[1070]: Started Multimedia Service.
Jul 25 23:06:50 kby540 systemd[1]: Started Session c1 of user lightdm.
Jul 25 23:06:50 kby540 systemd[1070]: Starting Sound Service...
Jul 25 23:06:50 kby540 dbus-daemon[789]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.29' (uid=122 pid=1086 comm="/usr/bin/pipewire ")
Jul 25 23:06:50 kby540 systemd[1]: Starting RealtimeKit Scheduling Policy Service...
Jul 25 23:06:50 kby540 dbus-daemon[789]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Jul 25 23:06:50 kby540 systemd[1]: Started RealtimeKit Scheduling Policy Service.
Jul 25 23:06:50 kby540 rtkit-daemon[1089]: Successfully called chroot.
Jul 25 23:06:50 kby540 rtkit-daemon[1089]: Successfully dropped privileges.
Jul 25 23:06:50 kby540 rtkit-daemon[1089]: Successfully limited resources.
Jul 25 23:06:50 kby540 rtkit-daemon[1089]: Running.
Jul 25 23:06:50 kby540 rtkit-daemon[1089]: Canary thread running.
Jul 25 23:06:50 kby540 rtkit-daemon[1089]: Watchdog thread running.
Jul 25 23:06:50 kby540 rtkit-daemon[1089]: Successfully made thread 1086 of process 1086 owned by '122' high priority at nice level -11.
Jul 25 23:06:50 kby540 rtkit-daemon[1089]: Supervising 1 threads of 1 processes of 1 users.
Jul 25 23:06:50 kby540 rtkit-daemon[1089]: Supervising 1 threads of 1 processes of 1 users.
Jul 25 23:06:50 kby540 rtkit-daemon[1089]: Supervising 1 threads of 1 processes of 1 users.
Jul 25 23:06:50 kby540 rtkit-daemon[1089]: Successfully made thread 1088 of process 1086 owned by '122' RT at priority 20.
Jul 25 23:06:50 kby540 rtkit-daemon[1089]: Supervising 2 threads of 1 processes of 1 users.
Jul 25 23:06:50 kby540 systemd[1070]: Started D-Bus User Message Bus.
Jul 25 23:06:50 kby540 rtkit-daemon[1089]: Successfully made thread 1087 of process 1087 owned by '122' high priority at nice level -11.
Jul 25 23:06:50 kby540 rtkit-daemon[1089]: Supervising 3 threads of 2 processes of 1 users.
Jul 25 23:06:50 kby540 pipewire[1086]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name
Jul 25 23:06:50 kby540 dbus-daemon[1093]: [session uid=122 pid=1093] Activating service name='ca.desrt.dconf' requested by ':1.3' (uid=122 pid=1090 comm="/usr/sbin/slick-greeter ")
Jul 25 23:06:50 kby540 rtkit-daemon[1089]: Successfully made thread 1094 of process 1094 owned by '122' high priority at nice level -11.
Jul 25 23:06:50 kby540 rtkit-daemon[1089]: Supervising 4 threads of 3 processes of 1 users.
Jul 25 23:06:50 kby540 rtkit-daemon[1089]: Supervising 4 threads of 3 processes of 1 users.
Jul 25 23:06:50 kby540 rtkit-daemon[1089]: Supervising 4 threads of 3 processes of 1 users.
Jul 25 23:06:50 kby540 dbus-daemon[1093]: [session uid=122 pid=1093] Successfully activated service 'ca.desrt.dconf'
Jul 25 23:06:50 kby540 rtkit-daemon[1089]: Successfully made thread 1097 of process 1094 owned by '122' RT at priority 20.
Jul 25 23:06:50 kby540 rtkit-daemon[1089]: Supervising 5 threads of 3 processes of 1 users.
Jul 25 23:06:50 kby540 slick-greeter-check-hidpi: Window scale: 1
Jul 25 23:06:50 kby540 slick-greeter-set-keyboard-layout: Current keyboard configuration: rules:      evdev#012model:      pc105#012layout:     us#012options:    grp:win_space_toggle
Jul 25 23:06:50 kby540 slick-greeter-set-keyboard-layout: Applying keyboard configuration: ['setxkbmap', '-model', 'pc105', '-layout', 'us', '-variant', '', '-option', 'grp:win_space_toggle', '-v']
Jul 25 23:06:50 kby540 slick-greeter-set-keyboard-layout: Result: Warning! Multiple definitions of keyboard model#012         Using command line, ignoring X server#012Warning! Multiple definitions of keyboard layout#012         Using command line, ignoring X server#012Trying to build keymap using the following components:#012keycodes:   evdev+aliases(qwerty)#012types:      complete#012compat:     complete#012symbols:    pc+us+inet(evdev)+group(win_space_toggle)#012geometry:   pc(pc105)
Jul 25 23:06:50 kby540 slick-greeter-set-keyboard-layout: New keyboard configuration: rules:      evdev#012model:      pc105#012layout:     us#012options:    grp:win_space_toggle
Jul 25 23:06:50 kby540 dbus-daemon[1093]: [session uid=122 pid=1093] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.6' (uid=122 pid=1090 comm="/usr/sbin/slick-greeter ")
Jul 25 23:06:50 kby540 systemd[1070]: Starting Accessibility services bus...
Jul 25 23:06:50 kby540 dbus-daemon[1093]: [session uid=122 pid=1093] Successfully activated service 'org.a11y.Bus'
Jul 25 23:06:50 kby540 systemd[1070]: Started Accessibility services bus.
Jul 25 23:06:50 kby540 dbus-daemon[1093]: [session uid=122 pid=1093] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.3' (uid=122 pid=1090 comm="/usr/sbin/slick-greeter ")
Jul 25 23:06:50 kby540 systemd[1070]: Starting Virtual filesystem service...
Jul 25 23:06:50 kby540 dbus-daemon[1093]: [session uid=122 pid=1093] Successfully activated service 'org.gtk.vfs.Daemon'
Jul 25 23:06:50 kby540 systemd[1070]: Started Virtual filesystem service.
Jul 25 23:06:50 kby540 rtkit-daemon[1089]: Supervising 5 threads of 3 processes of 1 users.
Jul 25 23:06:50 kby540 rtkit-daemon[1089]: Successfully made thread 1132 of process 1087 owned by '122' RT at priority 5.
Jul 25 23:06:50 kby540 rtkit-daemon[1089]: Supervising 6 threads of 3 processes of 1 users.
Jul 25 23:06:51 kby540 at-spi-bus-launcher[1119]: dbus-daemon[1119]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=122 pid=1090 comm="/usr/sbin/slick-greeter ")
Jul 25 23:06:51 kby540 at-spi-bus-launcher[1119]: dbus-daemon[1119]: Successfully activated service 'org.a11y.atspi.Registry'
Jul 25 23:06:51 kby540 at-spi-bus-launcher[1136]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Jul 25 23:06:51 kby540 rtkit-daemon[1089]: Supervising 6 threads of 3 processes of 1 users.
Jul 25 23:06:51 kby540 rtkit-daemon[1089]: Successfully made thread 1141 of process 1087 owned by '122' RT at priority 5.
Jul 25 23:06:51 kby540 rtkit-daemon[1089]: Supervising 7 threads of 3 processes of 1 users.
Jul 25 23:06:51 kby540 rtkit-daemon[1089]: Supervising 7 threads of 3 processes of 1 users.
Jul 25 23:06:51 kby540 rtkit-daemon[1089]: Successfully made thread 1142 of process 1087 owned by '122' RT at priority 5.
Jul 25 23:06:51 kby540 rtkit-daemon[1089]: Supervising 8 threads of 3 processes of 1 users.
Jul 25 23:06:51 kby540 systemd[1070]: Started Sound Service.
Jul 25 23:06:51 kby540 systemd[1070]: Reached target Main User Target.
Jul 25 23:06:51 kby540 systemd[1070]: Startup finished in 793ms.
Jul 25 23:06:51 kby540 bluetoothd[783]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSink/sbc
Jul 25 23:06:51 kby540 bluetoothd[783]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSource/sbc
Jul 25 23:06:51 kby540 kernel: [   13.508706] Bluetooth: RFCOMM TTY layer initialized
Jul 25 23:06:51 kby540 kernel: [   13.508709] Bluetooth: RFCOMM socket layer initialized
Jul 25 23:06:51 kby540 kernel: [   13.508712] Bluetooth: RFCOMM ver 1.11
Jul 25 23:06:51 kby540 ModemManager[872]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:14.3': not supported by any plugin
Jul 25 23:06:51 kby540 ModemManager[872]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1d.5/0000:07:00.0': not supported by any plugin
Jul 25 23:06:52 kby540 systemd[1]: systemd-rfkill.service: Succeeded.
Jul 25 23:06:52 kby540 wpa_supplicant[824]: wlp0s20f3: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=US
Jul 25 23:06:52 kby540 NetworkManager[791]: <info>  [1690340812.6620] device (enp7s0): carrier: link connected
Jul 25 23:06:52 kby540 NetworkManager[791]: <info>  [1690340812.6627] device (enp7s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Jul 25 23:06:52 kby540 NetworkManager[791]: <info>  [1690340812.6645] policy: auto-activating connection 'Wired connection 1' (7c7192ee-b33d-3f10-b682-2f711fbbdcfc)
Jul 25 23:06:52 kby540 kernel: [   14.918786] r8169 0000:07:00.0 enp7s0: Link is Up - 1Gbps/Full - flow control rx/tx
Jul 25 23:06:52 kby540 kernel: [   14.918804] IPv6: ADDRCONF(NETDEV_CHANGE): enp7s0: link becomes ready
Jul 25 23:06:52 kby540 NetworkManager[791]: <info>  [1690340812.6659] device (enp7s0): Activation: starting connection 'Wired connection 1' (7c7192ee-b33d-3f10-b682-2f711fbbdcfc)
Jul 25 23:06:52 kby540 NetworkManager[791]: <info>  [1690340812.6661] device (enp7s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jul 25 23:06:52 kby540 NetworkManager[791]: <info>  [1690340812.6670] manager: NetworkManager state is now CONNECTING
Jul 25 23:06:52 kby540 NetworkManager[791]: <info>  [1690340812.6675] device (enp7s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jul 25 23:06:52 kby540 NetworkManager[791]: <info>  [1690340812.6679] device (enp7s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jul 25 23:06:52 kby540 NetworkManager[791]: <info>  [1690340812.6682] dhcp4 (enp7s0): activation: beginning transaction (timeout in 45 seconds)
Jul 25 23:06:52 kby540 avahi-daemon[782]: Joining mDNS multicast group on interface enp7s0.IPv6 with address fe80::12f:ffbd:133a:9d9d.
Jul 25 23:06:52 kby540 avahi-daemon[782]: New relevant interface enp7s0.IPv6 for mDNS.
Jul 25 23:06:52 kby540 avahi-daemon[782]: Registering new address record for fe80::12f:ffbd:133a:9d9d on enp7s0.*.
Jul 25 23:06:53 kby540 kernel: [   16.024688] logitech-hidpp-device 0003:046D:405E.0006: HID++ 4.5 device connected.
Jul 25 23:06:54 kby540 upowerd[1028]: treating change event as add on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.2/0003:046D:C52B.0004/0003:046D:405E.0006/power_supply/hidpp_battery_0
Jul 25 23:06:54 kby540 thermald[820]: Unable to find a zone for SEN1
Jul 25 23:06:54 kby540 thermald[820]: Adaptive policy couldn't create any zones
Jul 25 23:06:54 kby540 thermald[820]: Possibly some sensors in the PSVT are missing
Jul 25 23:06:54 kby540 thermald[820]: Restart in non adaptive mode via systemd
Jul 25 23:06:54 kby540 systemd[1]: thermald.service: Main process exited, code=exited, status=1/FAILURE
Jul 25 23:06:54 kby540 systemd[1]: thermald.service: Failed with result 'exit-code'.
Jul 25 23:06:54 kby540 NetworkManager[791]: <info>  [1690340814.4802] dhcp6 (enp7s0): activation: beginning transaction (timeout in 45 seconds)
Jul 25 23:06:54 kby540 avahi-daemon[782]: Leaving mDNS multicast group on interface enp7s0.IPv6 with address fe80::12f:ffbd:133a:9d9d.
Jul 25 23:06:54 kby540 avahi-daemon[782]: Joining mDNS multicast group on interface enp7s0.IPv6 with address 2601:c9:281:8e50:2b8c:601c:a465:849a.
Jul 25 23:06:54 kby540 avahi-daemon[782]: Registering new address record for 2601:c9:281:8e50:2b8c:601c:a465:849a on enp7s0.*.
Jul 25 23:06:54 kby540 avahi-daemon[782]: Withdrawing address record for fe80::12f:ffbd:133a:9d9d on enp7s0.
Jul 25 23:06:54 kby540 NetworkManager[791]: <info>  [1690340814.4821] dhcp6 (enp7s0): state changed unknown -> bound, address=2601:c9:281:8e50::2b
Jul 25 23:06:54 kby540 avahi-daemon[782]: Registering new address record for 2601:c9:281:8e50::2b on enp7s0.*.
Jul 25 23:06:54 kby540 systemd[1]: thermald.service: Scheduled restart job, restart counter is at 1.
Jul 25 23:06:54 kby540 systemd[1]: Stopped Thermal Daemon Service.
Jul 25 23:06:54 kby540 systemd[1]: Starting Thermal Daemon Service...
Jul 25 23:06:54 kby540 systemd[1]: Started Thermal Daemon Service.
Jul 25 23:06:54 kby540 thermald[1146]: 22 CPUID levels; family:model:stepping 0x6:9e:a (6:158:10)
Jul 25 23:06:54 kby540 thermald[1146]: 22 CPUID levels; family:model:stepping 0x6:9e:a (6:158:10)
Jul 25 23:06:54 kby540 thermald[1146]: Polling mode is enabled: 4
Jul 25 23:06:54 kby540 thermald[1146]: sensor id 13 : No temp sysfs for reading raw temp
Jul 25 23:06:54 kby540 thermald[1146]: sensor id 13 : No temp sysfs for reading raw temp
Jul 25 23:06:54 kby540 thermald[1146]: sensor id 13 : No temp sysfs for reading raw temp
Jul 25 23:06:54 kby540 thermald[1146]: Config file /etc/thermald/thermal-conf.xml does not exist
Jul 25 23:06:54 kby540 thermald[1146]: Config file /etc/thermald/thermal-conf.xml does not exist
Jul 25 23:06:54 kby540 thermald[1146]: Config file /etc/thermald/thermal-conf.xml does not exist
Jul 25 23:06:54 kby540 dbus-daemon[789]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.9' (uid=0 pid=791 comm="/usr/sbin/NetworkManager --no-daemon ")
Jul 25 23:06:54 kby540 dbus-daemon[789]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
Jul 25 23:06:55 kby540 NetworkManager[791]: <info>  [1690340815.7071] dhcp4 (enp7s0): state changed unknown -> bound, address=192.168.6.19
Jul 25 23:06:55 kby540 avahi-daemon[782]: Joining mDNS multicast group on interface enp7s0.IPv4 with address 192.168.6.19.
Jul 25 23:06:55 kby540 avahi-daemon[782]: New relevant interface enp7s0.IPv4 for mDNS.
Jul 25 23:06:55 kby540 avahi-daemon[782]: Registering new address record for 192.168.6.19 on enp7s0.IPv4.
Jul 25 23:06:55 kby540 NetworkManager[791]: <info>  [1690340815.7111] device (enp7s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jul 25 23:06:55 kby540 NetworkManager[791]: <info>  [1690340815.7143] device (enp7s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jul 25 23:06:55 kby540 NetworkManager[791]: <info>  [1690340815.7146] device (enp7s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jul 25 23:06:55 kby540 NetworkManager[791]: <info>  [1690340815.7150] manager: NetworkManager state is now CONNECTED_LOCAL
Jul 25 23:06:55 kby540 NetworkManager[791]: <info>  [1690340815.7158] manager: NetworkManager state is now CONNECTED_SITE
Jul 25 23:06:55 kby540 NetworkManager[791]: <info>  [1690340815.7160] policy: set 'Wired connection 1' (enp7s0) as default for IPv4 routing and DNS
Jul 25 23:06:55 kby540 NetworkManager[791]: <info>  [1690340815.7162] policy: set 'Wired connection 1' (enp7s0) as default for IPv6 routing and DNS
Jul 25 23:06:55 kby540 dbus-daemon[789]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.9' (uid=0 pid=791 comm="/usr/sbin/NetworkManager --no-daemon ")
Jul 25 23:06:55 kby540 dbus-daemon[789]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
Jul 25 23:06:55 kby540 NetworkManager[791]: <info>  [1690340815.7257] device (enp7s0): Activation: successful, device activated.[attachment=0]full_syslog_7-25-23-Mint.txt.zip[/attachment]

UPDATE 7/28:
Decided to apply some fresh thermal paste to the heatsync plate. I hope that helps.
Attachments
full_syslog_7-25-23-Mint.txt.zip
Full Log File Attachment
(126.45 KiB) Downloaded 77 times
Last edited by LockBot on Fri Jan 26, 2024 11:00 pm, edited 3 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
kancolle386
Level 1
Level 1
Posts: 9
Joined: Thu May 13, 2021 7:31 am
Location: Japan

Re: System freezing and possibly having heat sensor issue.

Post by kancolle386 »

Hello.

What is "after updating" mean? You changed some hardware or upgrade software?
KingdomB wrote: Tue Jul 25, 2023 11:54 pm I am relatively new to Linux despite using it for four years now. Recently after updating, my system has started to freeze and I am not sure about the cause. Someone suggested that there may be a temperature issue based on some of the info in my Syslog. Once the system
User avatar
SMG
Level 25
Level 25
Posts: 32007
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: System freezing and possibly having heat sensor issue.

Post by SMG »

KingdomB wrote: Tue Jul 25, 2023 11:54 pm I am relatively new to Linux despite using it for four years now. Recently after updating, my system has started to freeze and I am not sure about the cause.
Here is where things started having problems.

Code: Select all

Jul 25 23:01:55 kby540 kernel: [ 6237.715993] nouveau 0000:01:00.0: fifo: fault 01 [VIRT_WRITE] at 000000000de02000 engine 40 [GR] client 13 [GPC1/PROP_0] reason 00 [PDE] on channel 2 [017f454000 Xorg[834]]
Jul 25 23:01:55 kby540 kernel: [ 6237.715999] nouveau 0000:01:00.0: fifo: channel 2: killed
Jul 25 23:01:55 kby540 kernel: [ 6237.716001] nouveau 0000:01:00.0: fifo: runlist 0: scheduled for recovery
Jul 25 23:01:55 kby540 kernel: [ 6239.716016] ------------[ cut here ]------------
Jul 25 23:01:55 kby540 kernel: [ 6239.716019] nouveau 0000:01:00.0: timeout
Jul 25 23:01:55 kby540 kernel: [ 6239.716127] WARNING: CPU: 3 PID: 18916 at drivers/gpu/drm/nouveau/nvkm/engine/fifo/gk104.c:447 gk104_fifo_recover_engn+0x20e/0x220 [nouveau]
Then it crashed repeatedly. And, based on the timestamps of the messages, my guess is you killed power to the computer and restarted it.
KingdomB wrote: Tue Jul 25, 2023 11:54 pmNow I reinstalled Mint 21 and it is still happening.
The log you posted indicates you are running kernel 5.10.0-23-amd64 which is LMDE, but it's fine if you now have Mint 21 installed.

Please open the System Reports app and click the System Information tab on the left. Your computer's information should come up in the right pane. Then click the Copy button in the lower right and paste the results into a reply window here so we can see how Linux Mint views your hardware. Perhaps your system would be more stable with a proprietary Nvidia driver, if that is an option for your GPU.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
KingdomB
Level 1
Level 1
Posts: 47
Joined: Sat Jun 22, 2019 12:22 pm

Re: System freezing and possibly having heat sensor issue.

Post by KingdomB »

SMG wrote: Fri Jul 28, 2023 10:39 pm
KingdomB wrote: Tue Jul 25, 2023 11:54 pm I am relatively new to Linux despite using it for four years now. Recently after updating, my system has started to freeze and I am not sure about the cause.
Here is where things started having problems.

Code: Select all

Jul 25 23:01:55 kby540 kernel: [ 6237.715993] nouveau 0000:01:00.0: fifo: fault 01 [VIRT_WRITE] at 000000000de02000 engine 40 [GR] client 13 [GPC1/PROP_0] reason 00 [PDE] on channel 2 [017f454000 Xorg[834]]
Jul 25 23:01:55 kby540 kernel: [ 6237.715999] nouveau 0000:01:00.0: fifo: channel 2: killed
Jul 25 23:01:55 kby540 kernel: [ 6237.716001] nouveau 0000:01:00.0: fifo: runlist 0: scheduled for recovery
Jul 25 23:01:55 kby540 kernel: [ 6239.716016] ------------[ cut here ]------------
Jul 25 23:01:55 kby540 kernel: [ 6239.716019] nouveau 0000:01:00.0: timeout
Jul 25 23:01:55 kby540 kernel: [ 6239.716127] WARNING: CPU: 3 PID: 18916 at drivers/gpu/drm/nouveau/nvkm/engine/fifo/gk104.c:447 gk104_fifo_recover_engn+0x20e/0x220 [nouveau]
Then it crashed repeatedly. And, based on the timestamps of the messages, my guess is you killed power to the computer and restarted it.
KingdomB wrote: Tue Jul 25, 2023 11:54 pmNow I reinstalled Mint 21 and it is still happening.
The log you posted indicates you are running kernel 5.10.0-23-amd64 which is LMDE, but it's fine if you now have Mint 21 installed.

Please open the System Reports app and click the System Information tab on the left. Your computer's information should come up in the right pane. Then click the Copy button in the lower right and paste the results into a reply window here so we can see how Linux Mint views your hardware. Perhaps your system would be more stable with a proprietary Nvidia driver, if that is an option for your GPU.
Thanks for taking the time to answer my question. After throwing different solutions up against the wall I identified and solved two issues.

1. Thermal paste needed repairing.
- This was not the cause of the crashing but once I changed it, the internal temps decreased and the crashing decreased for about a week.

2. SSD was faulty [REPLACED]
- This ultimately was the problem and since I replaced this, I haven't had any more issues.

Also during this ordeal, I purchased another laptop of the same age and model, and it had the exact same problem which is how I was able to determine that there was an issue since it had purchase protection, and when I sent it in for repairs the tech identified the problem.
Locked

Return to “Hardware Support”