# \[SOLVED\]Analysing sudo journalctl -p err -e **URL:** \ **Category:** Newbie\ **Created:** [November 1, 2020, 4:40pm UTC](https://forum.endeavouros.com/t/solved-analysing-sudo-journalctl-p-err-e/9405 "2020-11-01T16:40:15Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![muj](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/muj/32/94382_2.png) [@muj](https://forum.endeavouros.com/u/muj)\ **Post date:** [November 1, 2020, 4:40pm UTC](https://forum.endeavouros.com/t/solved-analysing-sudo-journalctl-p-err-e/9405/1 "2020-11-01T16:40:15Z")
Hello, I’m just trying to clarify if some of the errors I’ve noticed in the `journalctl` need action or not. `sudo journalctl -p err -e` ```auto [muj@Blackstone ~]$ sudo journalctl -p err -e Nov 01 12:36:22 Blackstone kernel: i801_smbus 0000:00:1f.4: SMBus is busy, can't use it! Nov 01 12:36:31 Blackstone pulseaudio[930]: GetManagedObjects() failed: org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.service not found. -- Reboot -- Nov 01 13:25:31 Blackstone systemd-modules-load[242]: Failed to find module 'platform-integrity' Nov 01 13:25:32 Blackstone kernel: i801_smbus 0000:00:1f.4: Transaction timeout Nov 01 13:25:32 Blackstone kernel: i801_smbus 0000:00:1f.4: Failed terminating the transaction Nov 01 13:25:32 Blackstone kernel: i801_smbus 0000:00:1f.4: SMBus is busy, can't use it! Nov 01 13:25:38 Blackstone pulseaudio[899]: GetManagedObjects() failed: org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.service not found. -- Reboot -- Nov 01 14:16:30 Blackstone systemd-modules-load[245]: Failed to find module 'platform-integrity' Nov 01 14:16:31 Blackstone kernel: i801_smbus 0000:00:1f.4: Transaction timeout Nov 01 14:16:31 Blackstone kernel: i801_smbus 0000:00:1f.4: Failed terminating the transaction Nov 01 14:16:31 Blackstone kernel: i801_smbus 0000:00:1f.4: SMBus is busy, can't use it! Nov 01 14:16:38 Blackstone pulseaudio[891]: GetManagedObjects() failed: org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.service not found. Nov 01 14:34:53 Blackstone xfce4-screensaver-dialog[3057]: PAM unable to dlopen(/usr/lib/security/pam_gnome_keyring.so): /usr/lib/security/pam_gnome_keyring.so: cannot open shared object fi> Nov 01 14:34:53 Blackstone xfce4-screensaver-dialog[3057]: PAM adding faulty module: /usr/lib/security/pam_gnome_keyring.so Nov 01 15:44:59 Blackstone xfce4-screensaver-dialog[6230]: PAM unable to dlopen(/usr/lib/security/pam_gnome_keyring.so): /usr/lib/security/pam_gnome_keyring.so: cannot open shared object fi> Nov 01 15:44:59 Blackstone xfce4-screensaver-dialog[6230]: PAM adding faulty module: /usr/lib/security/pam_gnome_keyring.so Nov 01 15:46:15 Blackstone kernel: watchdog: watchdog0: watchdog did not stop! -- Reboot -- Nov 01 15:46:38 Blackstone systemd-modules-load[245]: Failed to find module 'platform-integrity' Nov 01 15:46:38 Blackstone kernel: i801_smbus 0000:00:1f.4: Transaction timeout Nov 01 15:46:38 Blackstone kernel: i801_smbus 0000:00:1f.4: Failed terminating the transaction Nov 01 15:46:38 Blackstone kernel: i801_smbus 0000:00:1f.4: SMBus is busy, can't use it! Nov 01 15:46:47 Blackstone pulseaudio[997]: GetManagedObjects() failed: org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.service not found. Nov 01 15:48:51 Blackstone kernel: watchdog: watchdog0: watchdog did not stop! -- Reboot -- Nov 01 15:49:11 Blackstone systemd-modules-load[244]: Failed to find module 'platform-integrity' Nov 01 15:49:11 Blackstone kernel: i801_smbus 0000:00:1f.4: Transaction timeout Nov 01 15:49:11 Blackstone kernel: i801_smbus 0000:00:1f.4: Failed terminating the transaction Nov 01 15:49:11 Blackstone kernel: i801_smbus 0000:00:1f.4: SMBus is busy, can't use it! Nov 01 15:49:20 Blackstone pulseaudio[991]: GetManagedObjects() failed: org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.service not found. Nov 01 16:11:02 Blackstone kernel: watchdog: watchdog0: watchdog did not stop! -- Reboot -- Nov 01 16:11:20 Blackstone systemd-modules-load[244]: Failed to find module 'platform-integrity' Nov 01 16:11:20 Blackstone kernel: i801_smbus 0000:00:1f.4: Transaction timeout Nov 01 16:11:20 Blackstone kernel: i801_smbus 0000:00:1f.4: Failed terminating the transaction Nov 01 16:11:20 Blackstone kernel: i801_smbus 0000:00:1f.4: SMBus is busy, can't use it! Nov 01 16:11:29 Blackstone pulseaudio[995]: GetManagedObjects() failed: org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.service not found. Nov 01 16:18:09 Blackstone kernel: watchdog: watchdog0: watchdog did not stop! -- Reboot -- Nov 01 16:18:29 Blackstone systemd-modules-load[230]: Failed to find module 'platform-integrity' Nov 01 16:18:35 Blackstone kernel: Bluetooth: hci0: setting interface failed (71) Nov 01 16:18:38 Blackstone systemd[1]: Failed to start Refresh Pacman mirrorlist with Reflector.. Nov 01 16:18:48 Blackstone kernel: watchdog: watchdog0: watchdog did not stop! -- Reboot -- Nov 01 16:19:09 Blackstone systemd-modules-load[246]: Failed to find module 'platform-integrity' Nov 01 16:19:09 Blackstone kernel: i801_smbus 0000:00:1f.4: Transaction timeout Nov 01 16:19:09 Blackstone kernel: i801_smbus 0000:00:1f.4: Failed terminating the transaction Nov 01 16:19:09 Blackstone kernel: i801_smbus 0000:00:1f.4: SMBus is busy, can't use it! Nov 01 16:19:18 Blackstone pulseaudio[1011]: GetManagedObjects() failed: org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.service not found. lines 92-142/142 (END) ``` regarding `Nov 01 16:18:09 Blackstone kernel: watchdog: watchdog0: watchdog did not stop!` I found this post and in post #7 it seems to say it’s a non-issue, well that is if it is the same as my issue. The post is like 4yrs old. [https://bbs.archlinux.org/viewtopic.php?id=153205](https://bbs.archlinux.org/viewtopic.php?id=153205) regarding `Failed to find module 'platform-integrity'` I found [https://forum.endeavouros.com/t/failed-to-find-module-platform-integrity-after-update/9279/8](https://forum.endeavouros.com/t/failed-to-find-module-platform-integrity-after-update/9279/9) from our site (lol that sounded nice) at the end of the post @torvic seems to me to be saying it can be ignored. I think the main difficulty I’m having is knowing whether the issue (when I find a fix) actually pertains to my issue. thanks in advance for any insight given into analysing the `journctl` output. I won’t edit/delete my first thoughts even though looking back I think both the issues obviously pertain to what I found in my logs. I think I probably just need to build some confidence in the matter of troubleshooting. I haven’t been concerned with the pulse audio log since I added this `snd_hda_intel.dmic_detect=0` to my kernel parameters my sound has been fine. @dalto already explained to me a bit about DNS and DNS errors so I wasn’t concerned with `systemd[1]: Failed to start Refresh Pacman mirrorlist with Reflector..` regarding ```auto Nov 01 16:11:20 Blackstone kernel: i801_smbus 0000:00:1f.4: Failed terminating the transaction Nov 01 16:11:20 Blackstone kernel: i801_smbus 0000:00:1f.4: SMBus is busy, can't use it! ``` I found this site which mentions the issue something to do with a kernel module which monitors temperatures I think. If anyone knows about the issue, if it needs action etc or solution pls let me know. I don’t know much about kernel modules. I’ve only ever loaded i915, lol not even sure if I was loading it. [https://forums.unraid.net/topic/71918-i801\_smbus-0000001f3-smbus-is-busy-cant-use-it/](https://forums.unraid.net/topic/71918-i801_smbus-0000001f3-smbus-is-busy-cant-use-it/) ---
**Author:** ![dalto](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/dalto/32/5577_2.png) [@dalto](https://forum.endeavouros.com/u/dalto)\ **Post date:** [November 1, 2020, 6:09pm UTC](https://forum.endeavouros.com/t/solved-analysing-sudo-journalctl-p-err-e/9405/2 "2020-11-01T18:09:40Z")
To me, if we focus on the errors that are recurring with every boot, it looks like most of them are not harmful errors. If you want to make them go away, you will need to research them one at a time and take appropriate actions. This will most commonly be blacklisting modules or setting kernel parameters. For example, for the watchdog error see: [https://wiki.archlinux.org/index.php/Improving\_performance#Watchdogs](https://wiki.archlinux.org/index.php/Improving_performance#Watchdogs) ---
**Author:** ![muj](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/muj/32/94382_2.png) [@muj](https://forum.endeavouros.com/u/muj)\ **Post date:** [November 1, 2020, 6:14pm UTC](https://forum.endeavouros.com/t/solved-analysing-sudo-journalctl-p-err-e/9405/3 "2020-11-01T18:14:48Z")
Thank you, I’ll check the link you pasted soon. You said > [@dalto](#): > > If you want to make them go away To be honest I don’t want to make them go away and have to spend the extra time etc lol. But how does a person know if they need to do something as a result of the errors. Are most errors harmless? > [@dalto](#): > > it looks like most of them are not harmful errors. Is there a way I can tell they are harmless? Is it just to do with if I see whilst using my computer eg the Wifi stops working or some blatant problem, then I know I need to find a fix to the errors? ---
**Author:** ![dalto](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/dalto/32/5577_2.png) [@dalto](https://forum.endeavouros.com/u/dalto)\ **Post date:** [November 1, 2020, 6:21pm UTC](https://forum.endeavouros.com/t/solved-analysing-sudo-journalctl-p-err-e/9405/4 "2020-11-01T18:21:36Z")
> [@muj](#): > > Is there a way I can tell they are harmless? You can do what you have been doing already. Researching them one at a time and finding other people with the same problem and see what the solutions were. 🤓 I know the answers sometimes seem less than understandable given where you are at in your linux learning curve but over time it will become easier as your base knowledge continues to grow. > [@muj](#): > > Are most errors harmless? The errors that appear at the beginning of the boot process are frequently harmless. I generally research errors only when I am having problems but many people take the opposite approach and work to keep their logs clean. ---
**Author:** ![muj](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/muj/32/94382_2.png) [@muj](https://forum.endeavouros.com/u/muj)\ **Post date:** [November 1, 2020, 6:24pm UTC](https://forum.endeavouros.com/t/solved-analysing-sudo-journalctl-p-err-e/9405/5 "2020-11-01T18:24:49Z")
Thank you for your replies they are very beneficial. After reading the wiki I just wanted to check my understanding. Am I correct in thinking to blacklist a kernel module all I need to do is create a file (any name of my choice) here `/etc/modprobe.d/nobeep.conf` in place of the `nobeep.conf` then edit that new file and paste the module name after blacklist like so `blacklist pcspkr` then run `sudo mkinitcpio -P` to regenerate the `initramfs`? If that is correct is there a way to find out the name of the kernel module? I know the command `lsmod`. Will it normally be the case that I’ll know the name from a fix I’ve found then I could just do something like `lsmod | grep [name-of-module]? I mean to check if I’ve got it loaded I suppose and need to blacklist it. lol sorry just thinking and realising whilst writing ---
**Author:** ![dalto](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/dalto/32/5577_2.png) [@dalto](https://forum.endeavouros.com/u/dalto)\ **Post date:** [November 1, 2020, 7:11pm UTC](https://forum.endeavouros.com/t/solved-analysing-sudo-journalctl-p-err-e/9405/6 "2020-11-01T19:11:10Z")
> [@muj](#): > > Am I correct in thinking to blacklist a kernel module all I need to do is create a file (any name of my choice) here `/etc/modprobe.d/nobeep.conf` in place of the `nobeep.conf` then edit that new file and paste the module name after blacklist like so `blacklist pcspkr` Yes. That is one way to do it. > [@muj](#): > > then run `sudo mkinitcpio -P` to regenerate the `initramfs`? You won’t always have to do this. You only need to rebuild the initramfs if the module is being loaded/detected by the initramfs. That being said, it won’t hurt anything to do so. > [@muj](#): > > Will it normally be the case that I’ll know the name from a fix I’ve found then I could just do something like `lsmod | grep [name-of-module]? I mean to check if I’ve got it loaded I suppose and need to blacklist it. Yes, that is pretty accurate. ---
**Author:** ![muj](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/muj/32/94382_2.png) [@muj](https://forum.endeavouros.com/u/muj)\ **Post date:** [November 1, 2020, 7:31pm UTC](https://forum.endeavouros.com/t/solved-analysing-sudo-journalctl-p-err-e/9405/7 "2020-11-01T19:31:27Z")
Thank you very much for confirming my understanding.