The Manjaro ARM is used on the GT-King box.
Mysterious errors are constantly flashing through the magazine when working:
What do they mean and how to eliminate them?
I just wanted you to see these mistakes in color 
I’m correcting it:
# journalctl -f
мар 24 19:49:21 manjaro kernel: audit: type=1103 audit(1711302561.287:173): pid=1398 uid=1000 auid=1000 ses=2 subj=unconfined msg='op=PAM:setcred grantors=pam_unix acct="root" exe="/usr/bin/su" hostname=? addr=? terminal=/dev/pts/0 res=success'
мар 24 19:49:21 manjaro kernel: audit: type=1105 audit(1711302561.287:174): pid=1398 uid=1000 auid=1000 ses=2 subj=unconfined msg='op=PAM:session_open grantors=pam_unix acct="root" exe="/usr/bin/su" hostname=? addr=? terminal=/dev/pts/0 res=success'
мар 24 19:49:21 manjaro kernel: panfrost ffe40000.gpu: shader power transition timeout
мар 24 19:49:21 manjaro kernel: panfrost ffe40000.gpu: l2 power transition timeout
мар 24 19:49:21 manjaro kernel: panfrost ffe40000.gpu: shader power transition timeout
мар 24 19:49:21 manjaro kernel: panfrost ffe40000.gpu: l2 power transition timeout
мар 24 19:49:21 manjaro kernel: panfrost ffe40000.gpu: shader power transition timeout
мар 24 19:49:21 manjaro kernel: panfrost ffe40000.gpu: l2 power transition timeout
мар 24 19:49:23 manjaro kernel: panfrost ffe40000.gpu: shader power transition timeout
мар 24 19:49:23 manjaro kernel: panfrost ffe40000.gpu: l2 power transition timeout
мар 24 19:49:23 manjaro kernel: panfrost ffe40000.gpu: shader power transition timeout
мар 24 19:49:23 manjaro kernel: panfrost ffe40000.gpu: l2 power transition timeout
мар 24 19:49:24 manjaro kernel: panfrost ffe40000.gpu: shader power transition timeout
мар 24 19:49:24 manjaro kernel: panfrost ffe40000.gpu: l2 power transition timeout
мар 24 19:49:24 manjaro kernel: panfrost ffe40000.gpu: shader power transition timeout
мар 24 19:49:24 manjaro kernel: panfrost ffe40000.gpu: l2 power transition timeout
мар 24 19:49:24 manjaro kernel: panfrost ffe40000.gpu: shader power transition timeout
мар 24 19:49:24 manjaro kernel: panfrost ffe40000.gpu: l2 power transition timeout
мар 24 19:49:25 manjaro kernel: panfrost ffe40000.gpu: shader power transition timeout
мар 24 19:49:25 manjaro kernel: panfrost ffe40000.gpu: l2 power transition timeout
мар 24 19:49:27 manjaro kernel: panfrost ffe40000.gpu: shader power transition timeout
мар 24 19:49:27 manjaro kernel: panfrost ffe40000.gpu: l2 power transition timeout
мар 24 19:49:28 manjaro kernel: panfrost ffe40000.gpu: shader power transition timeout
мар 24 19:49:28 manjaro kernel: panfrost ffe40000.gpu: l2 power transition timeout
^C
I trained myself to not even look at images of text, so I couldn’t care less for any colors. 
Anyway, throwing it into search engine gives me:
https://lore.kernel.org/lkml/20240322164525.2617508-1-christianshewitt@gmail.com/
1 Like
what is that ? may you post the output of
inxi --admin --verbosity=7 --filter --no-host --width
@zbe already posted the link. there is an issue with the irq-handler and the gpu (mali-chipset ?)
if you search a little bit more you’ll find that it’s related to the power-management. maybe disabling some power-saving features can prevent the timeout.
Yes, I have already seen this page, but I did not understand what needs to be done to fix these errors.
Please:
$ inxi --admin --verbosity=7 --filter --no-host --width
System:
Kernel: 6.1.79-1-MANJARO-ARM-AML arch: aarch64 bits: 64 compiler: gcc
v: 12.1.0 clocksource: arch_sys_counter parameters: root=PARTUUID=5aaeeb41-02
rootdelay=5 rootflags=data=writeback rw console=ttyAML0,115200n8
console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes
fsck.repair=yes net.ifnames=0
Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 wm: xfwm4 v: 4.18.0
with: xfce4-panel tools: avail: xfce4-screensaver vt: 7 dm: LightDM v: 1.32.0
Distro: Manjaro ARM base: Arch Linux
Machine:
Type: ARM System: Beelink GT-King Pro details: N/A
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M185/M225
serial: <filter> charge: 100% (should be ignored) rechargeable: yes
status: discharging
Memory:
System RAM: total: N/A available: 3.58 GiB used: 2.49 GiB (69.7%)
RAM Report: message: No RAM data found using udevadm.
CPU:
Info: model: ARMv8 v8l variant-1: cortex-a73 variant-2: cortex-a53 bits: 64
type: MST AMCP arch: v8l family: 8 model-id: 0 stepping: 4
Topology: cpus: 1x cores: 4 mt: 2 tpc: 2 st: 2 threads: 6
smt: <unsupported> cache: N/A
Speed (MHz): avg: 1936 high: 1992 min/max: 1000/1992:1908 scaling:
driver: cpufreq-dt governor: performance cores: 1: 1992 2: 1992 3: 1908
4: 1908 5: 1908 6: 1908 bogomips: N/A
Features: aes asimd cpuid crc32 evtstrm fp pmull sha1 sha2
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: retbleed status: Not affected
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass status: Vulnerable
Type: spectre_v1 mitigation: __user pointer sanitization
Type: spectre_v2 status: Vulnerable
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: meson-g12a-vpu driver: meson_drm v: kernel bus-ID: N/A
chip-ID: amlogic:ff900000 class-ID: vpu
Device-2: meson-g12a-mali driver: panfrost v: kernel bus-ID: N/A
chip-ID: amlogic:ffe40000 class-ID: gpu
Device-3: meson-g12a-dw-hdmi driver: meson_dw_hdmi v: kernel bus-ID: N/A
chip-ID: amlogic:ff600000 class-ID: hdmi-tx
Display: x11 server: X.Org v: 21.1.11 compositor: xfwm4 v: 4.18.0 driver:
X: loaded: modesetting dri: meson gpu: meson-drm display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93") monitors: <missing: xrandr>
Monitor-1: HDMI-A-1 model: LG (GoldStar) E2750 built: 2009 res: 1920x1080
dpi: 81 gamma: 1.2 size: 510x290mm (20.08x11.42") diag: 690mm (27.2")
ratio: 16:9 modes: max: 1920x1080 min: 720x480
API: EGL v: 1.5 hw: drv: mali/bifrost panfrost platforms: device: 0
egl: 1.4 drv: panfrost device: 1 drv: swrast gbm: egl: 1.4 drv: meson
surfaceless: egl: 1.4 drv: panfrost x11: egl: 1.4 drv: meson
inactive: wayland
API: OpenGL v: 4.5 compat-v: 3.1 vendor: mesa v: 24.0.2-arch.1 glx-v: 1.4
direct-render: yes renderer: Mali-G52 (Panfrost) device-ID: ffffffff:ffffffff
memory: 3.5 GiB unified: yes
Audio:
Device-1: meson-g12a-dw-hdmi driver: meson_dw_hdmi v: kernel bus-ID: N/A
chip-ID: amlogic:ff600000 class-ID: hdmi-tx
Device-2: axg-sound-card driver: axg_sound_card bus-ID: N/A
chip-ID: amlogic:sound class-ID: sound
API: ALSA v: k6.1.79-1-MANJARO-ARM-AML status: kernel-api
tools: alsactl,alsamixer,amixer
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: PipeWire v: 1.0.3 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: meson-g12a-dwmac driver: meson8b_dwmac v: N/A port: N/A bus-ID: N/A
chip-ID: amlogic:ff3f0000 class-ID: ethernet
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IP v4: <filter> type: noprefixroute scope: global broadcast: <filter>
Device-2: ethernet-phy-id0180.3301 driver: Meson G12A Internal PHY v: N/A
port: N/A bus-ID: N/A chip-ID: ethernet-phy-id0180.3301:consumer
class-ID: ethernet-phy
Device-3: pwm-clock driver: pwm_clock v: N/A port: N/A bus-ID: N/A
chip-ID: pwm-clock:wifi32k class-ID: wifi32k
Info: services: NetworkManager, sshd, systemd-networkd, systemd-timesyncd
WAN IP: <filter>
Bluetooth:
Device-1: meson-gx-uart driver: meson_uart bus-ID: N/A
chip-ID: amlogic:ffd24000 class-ID: serial
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.1
lmp-v: 7 status: discoverable: no pairing: no class-ID: 6c0000
Logical:
Message: No logical block device data found.
RAID:
Message: No RAID data found.
Drives:
Local Storage: total: 1.2 TiB used: 58.66 GiB (4.8%)
ID-1: /dev/mmcblk1 maj-min: 179:0 vendor: Generic model: SLD64G
size: 57.62 GiB block-size: physical: 512 B logical: 512 B tech: SSD
serial: <filter> fw-rev: 0x8
SMART Message: Unknown smartctl error. Unable to generate data.
SMART Message: Unable to run smartctl. Root privileges required.
ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 PRO 256GB
size: 238.47 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 3.0 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: SSD serial: <filter>
scheme: MBR
ID-3: /dev/sdb maj-min: 8:16 vendor: Western Digital
model: WD10JMVW-11AJGS3 size: 931.48 GiB block-size: physical: 512 B
logical: 512 B type: USB rev: 3.0 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1
tech: HDD rpm: 5400 serial: <filter> fw-rev: 1056 scheme: MBR
Message: No optical or floppy data found.
Partition:
ID-1: / raw-size: 229.49 GiB size: 225.89 GiB (98.43%)
used: 58.59 GiB (25.9%) fs: ext4 dev: /dev/sda2 maj-min: 8:2
label: ROOT_MNJRO uuid: c1dd93b0-17ac-4885-941f-c74c34fb8166
ID-2: /boot raw-size: 457.8 MiB size: 457.5 MiB (99.94%)
used: 76.1 MiB (16.6%) fs: vfat dev: /dev/sda1 maj-min: 8:1 label: BOOT_MNJRO
uuid: 27D2-8767
Swap:
Kernel: swappiness: 60 (default) cache-pressure: 80 (default 100) zswap: no
ID-1: swap-1 type: partition size: 8.51 GiB used: 0 KiB (0.0%) priority: 10
dev: /dev/sda3 maj-min: 8:3 label: swap
uuid: 184ef8b7-e61c-4ff1-82eb-f0a20a496964
ID-2: swap-2 type: zram size: 5.37 GiB used: 2 MiB (0.0%) priority: 100
comp: lzo-rle avail: lzo,lz4,lz4hc,842,zstd max-streams: 6 dev: /dev/zram0
Unmounted:
ID-1: /dev/mmcblk1boot0 maj-min: 179:32 size: 4 MiB fs: <superuser required>
label: N/A uuid: N/A
ID-2: /dev/mmcblk1boot1 maj-min: 179:64 size: 4 MiB
fs: <superuser required> label: N/A uuid: N/A
ID-3: /dev/sdb1 maj-min: 8:17 size: 931.48 GiB fs: ext4 label: ARCHIVE
uuid: 50ba63e8-ed86-43b4-a4c8-e6436c10adeb
USB:
Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Hub-2: 1-1:3 info: Realtek RTS5411 Hub ports: 4 rev: 2.1
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 0bda:5411
class-ID: 0900
Hub-3: 1-2:2 info: NEC HighSpeed Hub ports: 4 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
chip-ID: 0409:005a class-ID: 0900
Device-1: 1-2.2:4 info: OpenMoko Airspy type: <vendor specific>
driver: usbfs interfaces: 1 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1
mode: 2.0 power: 500mA chip-ID: 1d50:60a1 class-ID: 0000 serial: <filter>
Device-2: 1-2.3:5 info: Logitech Unifying Receiver type: mouse,HID
driver: logitech-djreceiver,usbhid interfaces: 2 rev: 2.0
speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 98mA
chip-ID: 046d:c52f class-ID: 0300
Device-3: 1-2.4:6 info: Holtek PS/2 keyboard + mouse controller
type: keyboard,mouse driver: hid-generic,usbhid interfaces: 2 rev: 1.1
speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0 power: 100mA
chip-ID: 04d9:1400 class-ID: 0301
Hub-4: 2-0:1 info: super-speed hub ports: 1 rev: 3.0
speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 1d6b:0003
class-ID: 0900
Hub-5: 2-1:2 info: Realtek Hub ports: 4 rev: 3.0
speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 0bda:0411
class-ID: 0900
Device-1: 2-1.1:3 info: Transcend Information StoreJet 25H3
type: mass storage driver: uas interfaces: 1 rev: 3.0
speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 8564:7000
class-ID: 0806 serial: <filter>
Device-2: 2-1.2:4 info: Western Digital Elements Portable (WDBUZG)
type: mass storage driver: usb-storage interfaces: 1 rev: 3.0
speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 power: 896mA
chip-ID: 1058:1078 class-ID: 0806 serial: <filter>
Sensors:
System Temperatures: cpu: 60.9 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Processes: 223 Power: uptime: 43m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: shutdown
avail: reboot,suspend,test_resume image: 1.08 GiB
services: power-profiles-daemon Init: systemd v: 255 default: graphical
tool: systemctl
Packages: 1173 pm: pacman pkgs: 1162 libs: 312 tools: pamac pm: flatpak
pkgs: 11 Compilers: gcc: 12.1.0 Shell: Bash v: 5.2.26
running-in: xfce4-terminal inxi: 3.3.33
Kernel (or that kernel module at least) needs to be recompiled with that patch. Or you’ll have to wait till it gets merged upstream, etc.
Ok, Please explain what this module is called and where can I get this patch?
Is this the patch? [PATCH] drm/panfrost: fix power transition timeout warnings - Christian Hewitt
Yes. It’s in the name: drm/panfrost