I’ve recently got my PC up and running again but today it’s rebooted randomly twice. What could this be a sign of? All advice is welcomed and appreciated. Thanks in advance.
I’ve recently got my PC up and running again but today it’s rebooted randomly twice. What could this be a sign of? All advice is welcomed and appreciated. Thanks in advance.
It show this:
Feb 13 18:40:29.912947 [user] kernel: iommu ivhd0: AMD-Vi: Event logged [INVALID_DEVICE_REQUEST device=0000:00:00.0 pasid=0x00000 address=0xfffffffdf8000000 flags=0x0a00]And this:
Feb 13 18:40:34.855192 [user] kernel: nvidia-gpu 0000:24:00.3: i2c timeout error e0000000Feb 13 18:40:34.855523 [user] kernel: ucsi_ccg 6-0008: i2c_transfer failed -110Feb 13 18:40:34.856313 [user] kernel: ucsi_ccg 6-0008: ucsi_ccg_init failed - -110Feb 13 18:40:34.857464 [user] kernel: ucsi_ccg 6-0008: probe with driver ucsi_ccg failed with error -110Edit: And this:
Feb 13 18:40:34.855192 sam-ms7b93 kernel: nvidia-gpu 0000:24:00.3: i2c timeout error e0000000Feb 13 18:40:34.855523 sam-ms7b93 kernel: ucsi_ccg 6-0008: i2c_transfer failed -110Feb 13 18:40:34.857464 sam-ms7b93 kernel: ucsi_ccg 6-0008: probe with driver ucsi_ccg failed with error -110Feb 13 18:40:35.256841 sam-ms7b93 kernel: iwlwifi 0000:28:00.0: Registered PHC clock: iwlwifi-PTP, with index: 1Feb 13 18:40:37.136726 sam-ms7b93 systemd-journald[596]: File /var/log/journal/347a826f389a4d8f832a34bd1283f6a3/ user-1000.journal corrupted or uncleanly shut down, renaming and replacing.Feb 13 18:40:37.774864 sam-ms7b93 kernel: nvme nvme0: using unchecked data bufferFeb 13 18:40:40.538835 sam-ms7b93 kernel: wlan0: VHT information is missing, disabling VHTFeb 13 18:40:40.542833 sam-ms7b93 kernel: wlan0: authenticate with 54:be:f7:d3:d0:98 (local address=ac:67:5d:fd:29:d8)Feb 13 18:40:40.542853 sam-ms7b93 kernel: wlan0: send auth to 54:be:f7:d3:d0:98 (try 1/3)Feb 13 18:40:40.610840 sam-ms7b93 kernel: warning:kdeconnectd’ uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211`Feb 13 18:40:40.672835 sam-ms7b93 kernel: wlan0: send auth to 54:be:f7:d3:d0:98 (try 2/3)Feb 13 18:40:40.675837 sam-ms7b93 kernel: wlan0: authenticatedFeb 13 18:40:40.675864 sam-ms7b93 kernel: wlan0: associate with 54:be:f7:d3:d0:98 (try 1/3)Feb 13 18:40:40.696831 sam-ms7b93 kernel: wlan0: RX AssocResp from 54:be:f7:d3:d0:98 (capab=0x411 status=0 aid=1)Feb 13 18:40:40.700846 sam-ms7b93 kernel: wlan0: associatedFeb 13 18:40:40.749843 sam-ms7b93 kernel: wlan0: Limiting TX power to 27 (30 - 3) dBm as advertised by 54:be:f7:d3:d0:98Feb 13 18:41:18.320172 sam-ms7b93 kernel: ntfs3: Enabled Linux POSIX ACLs supportFeb 13 18:41:18.320369 sam-ms7b93 kernel: ntfs3: Read-only LZX/Xpress compression includedFeb 13 18:41:19.837143 sam-ms7b93 kernel: ntfs3(nvme1n1p2): It is recommened to use chkdsk.Feb 13 18:41:19.839148 sam-ms7b93 kernel: ntfs3(nvme1n1p2): volume is dirty and "force" flag is not set!lines 1327-1350/1350 (END)Huh, nothing super jumps out to me as an obvious tell, but the last bit is talking about some weird stuff with NTFS. Do you have a drive with Windows or formatted by Windows mounted maybe? Something could be up with that drive, or if you’re using it for something important to the system that could be a problem. You can just follow the recommendation in the log and use
chkdskon it but that could potentially be destructive to the data on the drive so be careful and make backups if needed.