How to get the logs from a certain severity level#
There are 8 severity levels for the logs:
Severity level
Severity level number
emerg
0
alert
1
crit
2
err
3
warning
4
notice
5
info
6
debug
7
Logs from a severity level for a service:#
It is possible to get the logs for a service from a certain severity level using this command:
journalctl -u <service_name> -p <severity_level>
For example, the logs of the service hello_world from error level can be retrieved using:
root@sm2s-imx8nano:~# journalctl -u hello_world.service -p err
-- No entries --
For example, the logs of the service pipewire from error level can be retrieved using:
root@sm2s-imx8nano:~# journalctl -u pipewire.service -p err
Nov 28 07:43:06 sm2s-imx8nano pipewire[558]: spa.dbus: Failed to connect to session bus: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
Nov 28 07:43:06 sm2s-imx8nano pipewire[558]: mod.portal: Failed to connect to session bus: Input/output error
Nov 28 07:43:06 sm2s-imx8nano pipewire[558]: spa.dbus: Failed to connect to session bus: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
Nov 28 07:43:06 sm2s-imx8nano pipewire[558]: mod.jackdbus-detect: Failed to connect to session bus: Input/output error
For example, the logs of the service wireplumber from warning level can be retrieved using:
root@sm2s-imx8nano:~# journalctl -u wireplumber.service -p 4
Nov 28 07:43:06 sm2s-imx8nano wireplumber[571]: 0xaaaaed849680: no modules loaded from context.modules
Nov 28 07:43:12 sm2s-imx8nano wireplumber[571]: Failed to get percentage from UPower: org.freedesktop.DBus.Error.NameHasNoOwner
Nov 28 07:43:12 sm2s-imx8nano wireplumber[571]: BlueZ system service is not available
For example, the logs of the service hello_world from info level can be retrieved using:
root@sm2s-imx8nano:~# journalctl -u hello_world.service -p 6
Nov 28 07:56:58 sm2s-imx8nano systemd[1]: Started Hello World.
Nov 28 07:56:58 sm2s-imx8nano echo[1194]: Hello World
Nov 28 07:56:58 sm2s-imx8nano systemd[1]: hello_world.service: Deactivated successfully.
Nov 28 07:58:01 sm2s-imx8nano systemd[1]: Started Hello World.
Nov 28 07:58:01 sm2s-imx8nano echo[1203]: Hello World
Nov 28 07:58:01 sm2s-imx8nano systemd[1]: hello_world.service: Deactivated successfully.
Nov 28 07:59:07 sm2s-imx8nano systemd[1]: Started Hello World.
Nov 28 07:59:07 sm2s-imx8nano echo[1217]: Hello World
Nov 28 07:59:07 sm2s-imx8nano systemd[1]: hello_world.service: Deactivated successfully.
For example, the logs of the service hello_world from debug level can be retrieved using:
root@sm2s-imx8nano:~# journalctl -u hello_world.service -p debug
Nov 28 07:56:58 sm2s-imx8nano systemd[1]: Started Hello World.
Nov 28 07:56:58 sm2s-imx8nano echo[1194]: Hello World
Nov 28 07:56:58 sm2s-imx8nano systemd[1]: hello_world.service: Deactivated successfully.
Nov 28 07:58:01 sm2s-imx8nano systemd[1]: Started Hello World.
Nov 28 07:58:01 sm2s-imx8nano echo[1203]: Hello World
Nov 28 07:58:01 sm2s-imx8nano systemd[1]: hello_world.service: Deactivated successfully.
Nov 28 07:59:07 sm2s-imx8nano systemd[1]: Started Hello World.
Nov 28 07:59:07 sm2s-imx8nano echo[1217]: Hello World
Nov 28 07:59:07 sm2s-imx8nano systemd[1]: hello_world.service: Deactivated successfully.
Logs from a severity level for the kernel:#
It is possible to get the kernel logs from a certain severity level using this command:
journalctl -k -p <severity_level>
Here is an example of the kernel logs from error level:
root@sm2s-imx8nano:~# journalctl -k -p 3
Nov 28 07:42:58 sm2s-imx8nano kernel: [drm:drm_bridge_attach] *ERROR* failed to attach bridge /soc@0/bus@32c00000/dsi_controller@32e10000 to encoder DSI-34: -517
Nov 28 07:42:58 sm2s-imx8nano kernel: imx_sec_dsim_drv 32e10000.dsi_controller: Failed to attach bridge: 32e10000.dsi_controller
Nov 28 07:42:58 sm2s-imx8nano kernel: imx_sec_dsim_drv 32e10000.dsi_controller: failed to bind sec dsim bridge: -517
Nov 28 07:42:58 sm2s-imx8nano kernel: spi-nor spi3.0: unrecognized JEDEC id bytes: 00 00 00 00 00 00
Nov 28 07:42:58 sm2s-imx8nano kernel: imx-da7213 da7213-sound: failed to find codec platform device now. retrying....
Nov 28 07:42:58 sm2s-imx8nano kernel: [drm:drm_bridge_attach] *ERROR* failed to attach bridge /soc@0/bus@32c00000/dsi_controller@32e10000 to encoder DSI-34: -517
Nov 28 07:42:58 sm2s-imx8nano kernel: imx_sec_dsim_drv 32e10000.dsi_controller: Failed to attach bridge: 32e10000.dsi_controller
Nov 28 07:42:58 sm2s-imx8nano kernel: imx_sec_dsim_drv 32e10000.dsi_controller: failed to bind sec dsim bridge: -517
Nov 28 07:43:12 sm2s-imx8nano kernel: gcmkONERROR: status=-1(gcvSTATUS_INVALID_ARGUMENT) @ gckOS_UnmapMemoryEx(1243)
Here is an example of the kernel logs from warning level:
root@sm2s-imx8nano:~# journalctl -k -p warning
Nov 28 07:42:58 sm2s-imx8nano kernel: ITS: No ITS available, not enabling LPIs
Nov 28 07:42:58 sm2s-imx8nano kernel: imx-sdma 302b0000.dma-controller: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2
Nov 28 07:42:58 sm2s-imx8nano kernel: imx-sdma 302b0000.dma-controller: Falling back to sysfs fallback for: imx/sdma/sdma-imx7d.bin
Nov 28 07:42:58 sm2s-imx8nano kernel: [drm:drm_bridge_attach] *ERROR* failed to attach bridge /soc@0/bus@32c00000/dsi_controller@32e10000 to encoder DSI-34: -517
Nov 28 07:42:58 sm2s-imx8nano kernel: imx_sec_dsim_drv 32e10000.dsi_controller: Failed to attach bridge: 32e10000.dsi_controller
Nov 28 07:42:58 sm2s-imx8nano kernel: imx_sec_dsim_drv 32e10000.dsi_controller: failed to bind sec dsim bridge: -517
Nov 28 07:42:58 sm2s-imx8nano kernel: spi-nor spi3.0: unrecognized JEDEC id bytes: 00 00 00 00 00 00
Nov 28 07:42:58 sm2s-imx8nano kernel: galcore: clk_get 2d core clock failed, disable 2d/vg!
Nov 28 07:42:58 sm2s-imx8nano kernel: imx-da7213 da7213-sound: failed to find codec platform device now. retrying....
Nov 28 07:42:58 sm2s-imx8nano kernel: gpio gpiochip0: Static allocation of GPIO base is deprecated, use dynamic allocation.
...
Logs from a severity level for the system:#
It is possible to get the system logs from a certain severity level using this command:
journalctl --system -p <severity_level>
Here is an example of the system logs from critical level:
root@sm2s-imx8nano:~# journalctl --system -p 2
-- No entries --
Here is an example of the system logs from notice level:
root@sm2s-imx8nano:~# journalctl --system -p notice
Nov 28 07:42:58 sm2s-imx8nano kernel: Linux version 6.6.23 (oe-user@oe-host) (aarch64-simplecoredistro-linux-gcc (GCC) 13.4.0, GNU ld (GNU Binutils) 2.42.0.20240723) #1 SMP PREEMPT Fri Mar 21 12:43:10 UTC 2025
Nov 28 07:42:58 sm2s-imx8nano kernel: Kernel command line: console=ttymxc0,115200 earlycon=ec_imx6q,0x30860000,115200 root=/dev/mmcblk1p2 rootwait rw dtb-module=msc-sm2s-imx8mlc-nano-03N0220I-module.dtb dtb-overlay=overlay-baseboard-ep5.dtb overlay-lvds-ama-070a04.dtb overlay-extra-smarc-pins.dtb ${optargs} fbcon=rotate:0
Nov 28 07:42:58 sm2s-imx8nano kernel: Unknown kernel command line parameters "${optargs} dtb-module=msc-sm2s-imx8mlc-nano-03N0220I-module.dtb dtb-overlay=overlay-baseboard-ep5.dtb", will be passed to user space.
Nov 28 07:42:58 sm2s-imx8nano kernel: ITS: No ITS available, not enabling LPIs
Nov 28 07:42:58 sm2s-imx8nano kernel: audit: type=2000 audit(0.192:1): state=initialized audit_enabled=0 res=1
Nov 28 07:42:58 sm2s-imx8nano kernel: SCSI subsystem initialized
Nov 28 07:42:58 sm2s-imx8nano kernel: VFS: Disk quotas dquot_6.6.0
Nov 28 07:42:58 sm2s-imx8nano kernel: Initialise system trusted keyrings
Nov 28 07:42:58 sm2s-imx8nano kernel: NFS: Registering the id_resolver key type
Nov 28 07:42:58 sm2s-imx8nano kernel: Key type id_resolver registered
...
Nov 28 07:42:58 sm2s-imx8nano systemd[1]: /etc/systemd/system/weston.socket.d/weston-socket-simplecore.conf:4: Failed to parse mode value, ignoring:
Nov 28 07:42:59 sm2s-imx8nano systemd-sysctl[213]: Couldn't write '1' to 'net/netfilter/nf_conntrack_helper', ignoring: No such file or directory
Nov 28 07:42:59 sm2s-imx8nano kernel: audit: type=1334 audit(1764315779.656:2): prog-id=6 op=LOAD
Nov 28 07:42:59 sm2s-imx8nano kernel: audit: type=1334 audit(1764315779.656:3): prog-id=7 op=LOAD
Nov 28 07:42:59 sm2s-imx8nano systemd-random-seed[231]: Kernel entropy pool is not initialized yet, waiting until it is.
Nov 28 07:42:59 sm2s-imx8nano kernel: audit: type=1334 audit(1764315779.888:4): prog-id=8 op=LOAD
Nov 28 07:42:59 sm2s-imx8nano kernel: audit: type=1334 audit(1764315779.976:5): prog-id=9 op=LOAD
Nov 28 07:42:59 sm2s-imx8nano kernel: audit: type=1334 audit(1764315779.976:6): prog-id=10 op=LOAD
Nov 28 07:42:59 sm2s-imx8nano kernel: audit: type=1334 audit(1764315779.980:7): prog-id=11 op=LOAD
Nov 28 07:43:01 sm2s-imx8nano systemd[1]: boot.mount: Directory /boot to mount over is not empty, mounting anyway.
...