this post was submitted on 31 Mar 2024
31 points (94.3% liked)
Linux 101 stuff. Questions are encouraged, noobs are welcome!
1086 readers
1 users here now
Linux introductions, tips and tutorials. Questions are encouraged. Any distro, any platform! Explicitly noob-friendly.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I also had the same thing, don't worry too much about it.
One thing is worth checking though, which happened on my laptop: After your computer is booted up normally, open a terminal and run dmesg. Is it still spamming these errors?
What happened with mine was that it was still spamming these errors and writing them to the log file(both the log file and the journald database), causing unnecessary wear on the SSD. I filtered out the logs to the file (don't remember how, but can probably find it again), but couldn't find how to filter out the logs to the Journald journal.
In my case the spamming was triggered / stopped by unplugging/plugging in the charging cable. If you run 'dmesg --wall' it will keep showing you the latest kernel-messages untill you abort with Ctrl+C
Thanks a lot for this.
Running dmesg I'm not sure what to look for in terms of checking if it keeps spamming them. And 'dmesg --wall' doesn't seem to be a valid command.
Oops, sorry, I meant 'dmesg --follow' (or 'dmesg -w' )
Normally the dmesg kernel log will be quiet after boot, and only give new messages when there's hardware related changes, like pluging in or out a USB device, or the charger cable.
In my case the log was spamming several messages every second non-stop so it was very obvious