Org_kde_powerdevil, ddcutil errors in journalctl -f

Support KDE Plasma
1

Hello,
I keep seeing this error message in journalctl.

org_kde_powerdevil[1350]: [468290] Emitting DDCA_Display_Status_Event[343031.409:  DDCA_EVENT_DDC_ENABLED, card1-HDMI-A-1, dref: DDCA_Display_Ref[24], io_path:/dev/i2c-5, ddc working: false]
org_kde_powerdevil[1350]: [468290] libddcutil callback thread 0x700418005b50 started
org_kde_powerdevil[1350]: [468290] Started 1 event callback thread(s)
org_kde_powerdevil[1350]: [468290] recheck thread terminating because watch thread terminated
org_kde_powerdevil[1350]: [  1350] Watch thread terminated.
org_kde_powerdevil[1350]: [  1350] busno=5, sleep-multiplier= 2,00, Testing for unsupported feature 0xdd returned Error_Info[DDCRC_RETRIES in ddc_write_read_with_retry, causes: DDCRC_DDC_DATA(10)]
org_kde_powerdevil[1350]: [  1350] Turning off dynamic sleep and retrying
org_kde_powerdevil[1350]: [  1350] busno=5, sleep-multiplier = 1,00, Retesting for unsupported feature 0xdd returned Error_Info[DDCRC_RETRIES in ddc_write_read_with_retry, causes: DDCRC_DDC_DATA(10)]
org_kde_powerdevil[1350]: [  1350] busno=5, sleep-multiplier= 2,00, Testing for unsupported feature 0x41 returned Error_Info[DDCRC_RETRIES in ddc_write_read_with_retry, causes: DDCRC_DDC_DATA(10)]
org_kde_powerdevil[1350]: [  1350] Turning off dynamic sleep and retrying
org_kde_powerdevil[1350]: [  1350] busno=5, sleep-multiplier = 1,00, Retesting for unsupported feature 0x41 returned Error_Info[DDCRC_RETRIES in ddc_write_read_with_retry, causes: DDCRC_DDC_DATA(10)]
org_kde_powerdevil[1350]: [  1350] Watching for display connection changes, resolved watch mode = Watch_Mode_Xevent, poll loop interval = 100 millisec
org_kde_powerdevil[1350]: [  1350]                                          extra_stabilization_millisec: 0,  stabilization_poll_millisec: 100

Is there something I should do to solve this? Is it a configuration problem?

Hope this feedback can be usefull!
Cheers

2

I’m counting 8 unique error messages. Which one do you keep seeing?

3

What command created this output?
Where all of these consecutive or was there … lines in between, edited out ?
If you don’t have an actual problem I would not worry …

4

https://bbs.archlinux.org/viewtopic.php?pid=2145550#p2145550

5

I copied the messages from a Konsole running sudo journalctl -f.
Those were consecutive lines.
I want to try to be ahead of the problems instead of getting caught up by them. I’m not necessarily worried, but I’m paying attention, and I defer to more knowledgeable persons to determine if something should be done.

Those, precisely. I was under the impression that they are related this part DDCRC_RETRIES in ddc_write_read_with_retry, causes: DDCRC_DDC_DATA(10), but I won’t dispute you, it is indeed multiple lines.

6

I just got the same lines, but from ddcutil :

ddcutil[4707]: [  4707] busno=5, sleep-multiplier= 2.00, Testing for unsupported feature 0xdd returned Error_Info[DDCRC_RETRIES in ddc_write_read_with_retry, causes: DDCRC_DDC_DATA(10)]
ddcutil[4707]: [  4707] Turning off dynamic sleep and retrying
ddcutil[4707]: [  4707] busno=5, sleep-multiplier = 1.00, Retesting for unsupported feature 0xdd returned Error_Info[DDCRC_RETRIES in ddc_write_read_with_retry, causes: DDCRC_DDC_DATA(10)]
ddcutil[4707]: [  4707] busno=5, sleep-multiplier= 2.00, Testing for unsupported feature 0x41 returned Error_Info[DDCRC_RETRIES in ddc_write_read_with_retry, causes: DDCRC_DDC_DATA(10)]
ddcutil[4707]: [  4707] Turning off dynamic sleep and retrying
ddcutil[4707]: [  4707] busno=5, sleep-multiplier = 1.00, Retesting for unsupported feature 0x41 returned Error_Info[DDCRC_RETRIES in ddc_write_read_with_retry, causes: DDCRC_DDC_DATA(10)]

Those lines appeared in journalctl -f when I ran ddcutil detect :

ddcutil detect                                                                                                              ✔ 
Display 1
   I2C bus:  /dev/i2c-5
   DRM connector:           card1-HDMI-A-1
   EDID synopsis:
      Mfg id:               IVM - Iiyama North America
      Model:                PLE2607WS
      Product code:         22024  (0x5608)
      Serial number:        
      Binary serial number: 50056 (0x0000c388)
      Manufacture year:     2008,  Week: 48
   VCP version:         2.0

Display 2
   I2C bus:  /dev/i2c-6
   DRM connector:           card1-DP-1
   EDID synopsis:
      Mfg id:               GSM - Goldstar Company Ltd (LG)
      Model:                27GN950
      Product code:         23450  (0x5b9a)
      Serial number:        101NTCZ5D803
      Binary serial number: 183803 (0x0002cdfb)
      Manufacture year:     2021,  Week: 1
   VCP version:         2.1
7

o.k. - thank you

fine motivation
can lead to identifying and chasing problems which don’t exist, though

If there are no actual problems
and there are no people identifying these messages as indicators of such
and one still thinks that there might be a problem …

then there is a problem … which no one can solve

because it is not a problem …

you could then still ask:

What do these messages mean?
Why are they even there?

…

8

it makes sense. I was not sure it was a problem, but I opted to ask to see if it was something that should be dealt with.

After this little exercise, I think I understand where those messages come from, though. My house’s electrical circuit regularly has brown outs, and one of my monitors isn’t protected from that, so it goes out and on again when the brown out has passed. I suppose ddcutil does a routine feature detection or whatever on the screen when it happens, hence the error messages that stem from (ab)normal disconnect/reconnect of a screen.

9

I just in about the same second in which you marked the topic solved added to my last post.

Just out of interest/curiosity:
might I ask where you are in the world?

I’m in Europe - Germany to be more precise.

Cheers!

10

It isn’t where I’m from (Portugal). It’s due to a big maritime container being connected to the circuit, and it draws a lot of power when the compressor goes on for its AC - a mighty momentary peak (3 to 5 seconds). It’s too much for the cable that brings the electricity to my house from the electricity meter. The electrical installation did not anticipate the capacity to accommodate a maritime container.

1 Like
11

Thank you for clarifying.
I’m now in the process of trying to understand the scenario which you just described.

Why would such a container draw so much peak power as to bring down the grid
and subsequently the power to your house, which is connected to it?

It’s something thankfully still unheard of here.

But it might become more common with the “transition to renewables” …

I’d rather live there than here, btw.
I’m currently working on learning the language. :wink:
Spanish and Portuguese …

Who would have thunk?

once upon a time:
English … was all that you needed :wink:

and we still can talk to each other by using it …
very good! amazing!

Cheers, my “potential” friend! :sunglasses:

12

How nice! I hope you gain proficiency and have some fun learning the languages.

The grid can withstand it, but the lengthy cable that run from the electrical meter to the house does not have the specs (the diameter) to accommodate this peak drawing from the container. It asks some brutal amperage when the compressor begins its rotations, and subsequently, during that phase, the tension drops - a brown out. There was no plan to connect a maritime container the the circuit, and hopefully it won’t stay there permanently.

1 Like
13

Aha - some rather unusual configuration is “the culprit”.

It’s not just fun - and it rarely is :wink:

I’ll need to talk, to communicate.

Not just rely on people knowing english …

14

Ok, so I’ve looked more into it and it doesn’t happen when I have those brown outs, I payed attention to those and was looking at the journalctl terminal, and there is no concomitance.

15

Those lines appear when the displays were idle, shut off, and I resume using the computer.

Configuration :

  • screen locks automatically after 5 minutes, delay before password is required is set to 5 seconds.
  • in the Power Management section, Suspend Session is set to do nothing when inactive.
  • in the Power Management section, Display and Brightness is set to dim automatically after 5 minutes, and the screen to turn off after 10 minutes or to one minute when locked.
  • in the Power Management section, the Other settings are set to leave unchanged for Switch to power profile, and to Run after 15 minutes for When Inactive.

Below, I think I’ve captured the sequence more comprehensively :

org_kde_powerdevil[1354]: [156340] Emitting DDCA_Display_Status_Event[144284.090:  DDCA_EVENT_DISPLAY_CONNECTED, card1-DP-1, dref: DDCA_Display_Ref[21], io_path:/dev/i2c-6, ddc working: true]
org_kde_powerdevil[1354]: [156340] libddcutil callback thread 0x77f20400c670 started
org_kde_powerdevil[1354]: [156340] Started 1 event callback thread(s)
org_kde_powerdevil[1354]: [  1354] Quiescing libddcutil API...
org_kde_powerdevil[1354]: [  1354] Quiesce libddcutil API complete
org_kde_powerdevil[1354]: [  1354] Display redetection starting.
org_kde_powerdevil[1354]: [156339] recheck thread terminating because watch thread terminated
org_kde_powerdevil[1354]: [  1354] Watch thread terminated.
org_kde_powerdevil[1354]: [  1354] busno=5, sleep-multiplier= 2,00, Testing for unsupported feature 0xdd returned Error_Info[DDCRC_RETRIES in ddc_write_read_with_retry, causes: DDCRC_DDC_DATA(10)]
org_kde_powerdevil[1354]: [  1354] Turning off dynamic sleep and retrying
org_kde_powerdevil[1354]: [  1354] busno=5, sleep-multiplier = 1,00, Retesting for unsupported feature 0xdd returned Error_Info[DDCRC_RETRIES in ddc_write_read_with_retry, causes: DDCRC_DDC_DATA(10)]
org_kde_powerdevil[1354]: [  1354] busno=5, sleep-multiplier= 2,00, Testing for unsupported feature 0x41 returned Error_Info[DDCRC_RETRIES in ddc_write_read_with_retry, causes: DDCRC_DDC_DATA(10)]
org_kde_powerdevil[1354]: [  1354] Turning off dynamic sleep and retrying
org_kde_powerdevil[1354]: [  1354] busno=5, sleep-multiplier = 1,00, Retesting for unsupported feature 0x41 returned Error_Info[DDCRC_RETRIES in ddc_write_read_with_retry, causes: DDCRC_DDC_DATA(10)]
org_kde_powerdevil[1354]: [  1354] Watching for display connection changes, resolved watch mode = Watch_Mode_Xevent, poll loop interval = 100 millisec
org_kde_powerdevil[1354]: [  1354]                                          extra_stabilization_millisec: 0,  stabilization_poll_millisec: 100
org_kde_powerdevil[1354]: [  1354] libddcutil recheck thread (nil) started
org_kde_powerdevil[1354]: [  1354] libddcutil watch thread 0x5a73a7a00f40 started
org_kde_powerdevil[1354]: [  1354] Display redetection finished.
org_kde_powerdevil[1354]: [  1354] Unquiescing libddcutil API...
org_kde_powerdevil[1354]: [178122] (dw_recheck_displays_func) Recheck interval: Slept for 200 millisec
kscreenlocker_greet[161040]: qt.qpa.wayland: Could not create EGL surface (EGL error 0x3000)
kscreenlocker_greet[161040]: qt.qpa.wayland: Could not create EGL surface (EGL error 0x3000)
kscreenlocker_greet[161040]: Failed to write to the pipe: Bad file descriptor.
16

Y’know…I also get these kind of errors:

qt.qpa.wayland: Could not create EGL surface (EGL error 0x3000)

I don’t see the required inxi output, but I bet you have an Nvidia DPU. And while I’m no expert, I’m putting my money on that as to the reason for your troubles. (I won’t buy an Nvidia card again, but in my defense this one was a gift when I was still Winblows-crippled.)

17 
System:
  Kernel: 6.14.0-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.14-x86_64
    root=UUID=41fd8083-4e6d-43c6-b78e-8c11b36d8410 rw quiet splash
    udev.log_priority=3
  Desktop: KDE Plasma v: 6.3.4 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
    Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: N/A
  Mobo: ASUSTeK model: ROG CROSSHAIR VIII FORMULA v: Rev X.0x
    serial: <filter> part-nu: SKU uuid: 45b5c92c-34fc-b797-6ece-fc3497b76ecd
    UEFI: American Megatrends v: 4201 date: 04/26/2022
Battery:
  ID-1: hidpp_battery_1 charge: 60% condition: N/A volts: 3.9 min: N/A
    model: Logitech G502 LIGHTSPEED Wireless Gaming Mouse type: N/A
    serial: <filter> status: discharging
Memory:
  System RAM: total: 32 GiB available: 31.25 GiB used: 10.65 GiB (34.1%)
  Array-1: capacity: 128 GiB slots: 4 modules: 4 EC: None
    max-module-size: 32 GiB note: est.
  Device-1: DIMM_A1 type: DDR4 detail: synchronous unbuffered (unregistered)
    size: 8 GiB speed: 3200 MT/s volts: curr: 1.2 min: 1.2 max: 1.2
    width (bits): data: 64 total: 64 manufacturer: G Skill Intl
    part-no: F4-3200C14-8GFX serial: N/A
  Device-2: DIMM_A2 type: DDR4 detail: synchronous unbuffered (unregistered)
    size: 8 GiB speed: 3200 MT/s volts: curr: 1.2 min: 1.2 max: 1.2
    width (bits): data: 64 total: 64 manufacturer: G Skill Intl
    part-no: F4-3200C14-8GFX serial: N/A
  Device-3: DIMM_B1 type: DDR4 detail: synchronous unbuffered (unregistered)
    size: 8 GiB speed: 3200 MT/s volts: curr: 1.2 min: 1.2 max: 1.2
    width (bits): data: 64 total: 64 manufacturer: G Skill Intl
    part-no: F4-3200C14-8GFX serial: N/A
  Device-4: DIMM_B2 type: DDR4 detail: synchronous unbuffered (unregistered)
    size: 8 GiB speed: 3200 MT/s volts: curr: 1.2 min: 1.2 max: 1.2
    width (bits): data: 64 total: 64 manufacturer: G Skill Intl
    part-no: F4-3200C14-8GFX serial: N/A
PCI Slots:
  Slot: 0 type: PCIe status: in use length: long volts: 3.3 bus-ID: 00:03.1
    children: 1: 09:00.0 class-ID: 0604 type: bridge children: 1: 0a:00.0
    class-ID: 0604 type: bridge children: 1: 0b:00.0 class-ID: 0300
    type: display 2: 0b:00.1 class-ID: 0403 type: audio
  Slot: 1 type: PCIe status: available length: long volts: 3.3
    bus-ID: 00:1f.7
  Slot: 2 type: PCIe status: available length: short volts: 3.3
    bus-ID: 00:1f.7
  Slot: 3 type: PCIe status: available length: short volts: 3.3
    bus-ID: 00:1f.7
CPU:
  Info: model: AMD Ryzen 7 5800X socket: AM4 bits: 64 type: MT MCP
    arch: Zen 3+ gen: 3 level: v3 note: check built: 2022 process: TSMC n6 (7nm)
    family: 0x19 (25) model-id: 0x21 (33) stepping: 0 microcode: 0xA20102D
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 threads: 16 tpc: 2
    smt: enabled cache: L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB
    desc: 8x512 KiB L3: 32 MiB desc: 1x32 MiB
  Speed (MHz): avg: 3599 min/max: 550/3801 boost: enabled
    base/boost: 3800/4850 scaling: driver: amd-pstate-epp governor: powersave
    volts: 1.1 V ext-clock: 100 MHz cores: 1: 3599 2: 3599 3: 3599 4: 3599
    5: 3599 6: 3599 7: 3599 8: 3599 9: 3599 10: 3599 11: 3599 12: 3599
    13: 3599 14: 3599 15: 3599 16: 3599 bogomips: 121599
  Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1
    bmi2 bpext cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy
    constant_tsc cpb cpuid cqm cqm_llc cqm_mbm_local cqm_mbm_total
    cqm_occup_llc cr8_legacy cx16 cx8 de debug_swap decodeassists erms
    extapic extd_apicid f16c flushbyasid fma fpu fsgsbase fsrm fxsr fxsr_opt
    ht hw_pstate ibpb ibrs ibs invpcid irperf lahf_lm lbrv lm mba mca mce
    misalignsse mmx mmxext monitor movbe msr mtrr mwaitx nonstop_tsc nopl npt
    nrip_save nx ospke osvw overflow_recov pae pat pausefilter pclmulqdq
    pdpe1gb perfctr_core perfctr_llc perfctr_nb pfthreshold pge pku pni
    popcnt pse pse36 rapl rdpid rdpru rdrand rdseed rdt_a rdtscp rep_good sep
    sha_ni skinit smap smca smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3
    stibp succor svm svm_lock syscall tce topoext tsc tsc_scale umip
    user_shstk v_spec_ctrl v_vmsave_vmload vaes vgif vmcb_clean vme vmmcall
    vpclmulqdq wbnoinvd wdt x2apic xgetbv1 xsave xsavec xsaveerptr xsaveopt
    xsaves xtopology
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: ghostwrite 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: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow mitigation: Safe RET
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW;
    STIBP: always-on; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not
    affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 14 [Radeon RX 5500/5500M /
    Pro 5500M] vendor: ASRock driver: amdgpu v: kernel arch: RDNA-1
    code: Navi-1x process: TSMC n7 (7nm) built: 2019-20 pcie: gen: 4
    speed: 16 GT/s lanes: 16 ports: active: DP-1,HDMI-A-1 empty: DP-2,DP-3
    bus-ID: 0b:00.0 chip-ID: 1002:7340 class-ID: 0300
  Display: unspecified server: X.Org v: 24.1.6 with: Xwayland v: 24.1.6
    compositor: kwin_wayland driver: X: loaded: amdgpu
    unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
    gpu: amdgpu display-ID: :1 screens: 1
  Screen-1: 0 s-res: 6080x2160 s-dpi: 96 s-size: 1608x571mm (63.31x22.48")
    s-diag: 1706mm (67.18")
  Monitor-1: DP-1 pos: primary,right model: LG (GoldStar) 27GN950
    serial: <filter> built: 2021 res: mode: 3840x2160 hz: 144 scale: 100% (1)
    dpi: 163 gamma: 1.2 chroma: red: x: 0.682 y: 0.314 green: x: 0.267
    y: 0.686 blue: x: 0.149 y: 0.055 white: x: 0.314 y: 0.329
    size: 600x340mm (23.62x13.39") diag: 690mm (27.2") ratio: 16:9
    modes: 3840x2160, 1920x1200, 1920x1080, 1600x1200, 1680x1050, 1280x1024,
    1440x900, 1280x800, 1280x720, 1024x768, 800x600, 720x480, 640x480
  EDID-Warnings: 1: parse_edid: unknown tag 112
  Monitor-2: HDMI-A-1 pos: left model: Idek Iiyama PLE2607WS
    serial: <filter> built: 2008 res: mode: 2240x1400 hz: 60 scale: 100% (1)
    dpi: 103 gamma: 1.2 chroma: red: x: 0.647 y: 0.333 green: x: 0.282
    y: 0.600 blue: x: 0.149 y: 0.071 white: x: 0.314 y: 0.329
    size: 550x344mm (21.65x13.54") diag: 649mm (25.5") ratio: 16:10
    modes: 1920x1200, 1920x1080, 1600x1200, 1680x1050, 1280x1024, 1440x900,
    1280x800, 1152x864, 1280x720, 1024x768, 832x624, 800x600, 720x576,
    720x480, 640x480, 720x400
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast gbm: drv: radeonsi surfaceless: drv: radeonsi x11:
    drv: radeonsi inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.0.3-arch1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 5500 XT (radeonsi
    navi14 LLVM 19.1.7 DRM 3.61 6.14.0-1-MANJARO) device-ID: 1002:7340
    memory: 7.81 GiB unified: no
  API: Vulkan v: 1.4.309 layers: N/A device: 0 type: discrete-gpu name: AMD
    Radeon RX 5500 XT (RADV NAVI14) driver: mesa radv v: 25.0.3-arch1.1
    device-ID: 1002:7340 surfaces: xcb,xlib
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info
    x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 HDMI Audio vendor: ASRock
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 0b:00.1 chip-ID: 1002:ab38 class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
    vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
    lanes: 16 bus-ID: 0d:00.4 chip-ID: 1022:1487 class-ID: 0403
  API: ALSA v: k6.14.0-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.4.1 status: n/a (root, process)
    with: pipewire-media-session status: active tools: pw-cli
  Server-3: PulseAudio v: 17.0-43-g3e2bb status: active (root, process)
    with: pulseaudio-alsa type: plugin tools: pacat,pactl
Network:
  Device-1: Aquantia AQC111 NBase-T/IEEE 802.3bz Ethernet [AQtion]
    vendor: ASUSTeK driver: atlantic v: kernel pcie: gen: 3 speed: 8 GT/s
    lanes: 1 link-max: lanes: 4 port: N/A bus-ID: 03:00.0 chip-ID: 1d6a:11b1
    class-ID: 0200
  IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  Device-2: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 04:00.0
    chip-ID: 8086:1539 class-ID: 0200
  IF: enp4s0 state: down mac: <filter>
  Device-3: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 05:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlp5s0 state: down mac: <filter>
  IF-ID-1: wg0-mullvad state: unknown speed: 10000 Mbps duplex: full
    mac: N/A
  IP v4: <filter> scope: global
  IP v6: <filter> scope: global
  IP v6: <filter> virtual: stable-privacy proto kernel_ll scope: link
  Info: services: NetworkManager,wpa_supplicant
  WAN IP: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-6:3 chip-ID: 8087:0029
    class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
  Device-2: Microsoft Nano Transceiver v1.0 for Bluetooth
    driver: hid-generic,usbhid type: USB rev: 2.0 speed: 12 Mb/s lanes: 1
    mode: 1.1 bus-ID: 3-3.1:5 chip-ID: 045e:0745 class-ID: 0300
  Report: This feature requires one of these tools: hciconfig/bt-adapter
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 1.26 TiB used: 923.2 GiB (71.6%)
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 830 Series
    family: based SSDs size: 119.24 GiB block-size: physical: 512 B
    logical: 512 B sata: 3.0 speed: 6.0 Gb/s tech: SSD serial: <filter>
    fw-rev: 3B1Q temp: 37 C scheme: MBR
  SMART: yes state: enabled health: PASSED on: 9y 314d 1h cycles: 4982
    written: 37.39 TiB
  ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 860 QVO 1TB
    family: based SSDs size: 931.51 GiB block-size: physical: 512 B
    logical: 512 B sata: 3.2 speed: 6.0 Gb/s tech: SSD serial: <filter>
    fw-rev: 1B6Q temp: 42 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 4y 309d 2h cycles: 1297
    written: 34.96 TiB
  ID-3: /dev/sdc maj-min: 8:32 vendor: Lexar model: 256GB SSD
    size: 238.47 GiB block-size: physical: 512 B logical: 512 B sata: 3.2
    speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: .0 temp: 38 C
    scheme: GPT
  SMART: yes state: enabled health: PASSED on: 3y 116d 20h cycles: 687
    read: 41 KiB written: 93 KiB
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 117.19 GiB size: 114.79 GiB (97.95%)
    used: 50.97 GiB (44.4%) fs: ext4 block-size: 4096 B dev: /dev/sda1
    maj-min: 8:1 label: N/A uuid: 41fd8083-4e6d-43c6-b78e-8c11b36d8410
  ID-2: /boot/efi raw-size: 2.05 GiB size: 2.05 GiB (99.80%)
    used: 288 KiB (0.0%) fs: vfat block-size: 512 B dev: /dev/sda2 maj-min: 8:2
    label: N/A uuid: B6FE-6408
  ID-3: /home raw-size: 930.66 GiB size: 914.98 GiB (98.31%)
    used: 829.28 GiB (90.6%) fs: ext4 block-size: 4096 B dev: /dev/sdb2
    maj-min: 8:18 label: N/A uuid: f18e7382-b9e7-4ab1-84ec-8fc5127f31d3
  ID-4: /run/media/jorgecpd/root raw-size: 238.33 GiB
    size: 233.53 GiB (97.99%) used: 42.95 GiB (18.4%) fs: ext4
    block-size: 4096 B dev: /dev/sdc2 maj-min: 8:34 label: root
    uuid: 6c260c5f-0db1-468c-bf06-2b3c928b1a0d
Swap:
  Alert: No swap data was found.
Unmounted:
  ID-1: /dev/sdb1 maj-min: 8:17 size: 868 MiB fs: vfat label: N/A
    uuid: A567-7EF7
  ID-2: /dev/sdc1 maj-min: 8:33 size: 149 MiB fs: vfat label: boot
    uuid: 128E-E778
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 6 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-5:2 info: Genesys Logic Hub ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 05e3:0610 class-ID: 0900
  Device-1: 1-5.3:4 info: ASUSTek AURA LED Controller type: HID
    driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 16mA chip-ID: 0b05:18f3 class-ID: 0300
    serial: <filter>
  Device-2: 1-5.4:5 info: ASUSTek AURA LED Controller type: HID
    driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 100mA chip-ID: 0b05:1872 class-ID: 0300
    serial: <filter>
  Device-3: 1-6:3 info: Intel AX200 Bluetooth type: bluetooth driver: btusb
    interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1
    power: 100mA chip-ID: 8087:0029 class-ID: e001
  Hub-3: 2-0:1 info: super-speed hub ports: 4 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-4: 3-0:1 info: hi-speed hub with single TT ports: 6 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-5: 3-2:2 info: ASMedia ASM1074 High-Speed hub ports: 4 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 174c:2074 class-ID: 0900
  Hub-6: 3-2.2:4 info: Texas Instruments TUSB8041 4-Port Hub ports: 4
    rev: 2.1 speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 0451:8142
    class-ID: 0900
  Hub-7: 3-2.2.2:30 info: VIA Labs VL812 Hub ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 2109:0812 class-ID: 0900
  Device-1: 3-2.2.2.2:31 info: Logitech Lightspeed Receiver
    type: keyboard,mouse,HID driver: logitech-djreceiver,usbhid interfaces: 3
    rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 98mA
    chip-ID: 046d:c539 class-ID: 0300
  Device-2: 3-2.2.4:51 info: LG USA Monitor Controls
    type: HID,abstract (modem),CDC-data driver: cdc_acm,hid-generic,usbhid
    interfaces: 4 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1
    chip-ID: 043e:9a8a class-ID: 0a00 serial: <filter>
  Hub-8: 3-3:3 info: ASMedia ASM1074 High-Speed hub ports: 4 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 174c:2074 class-ID: 0900
  Device-1: 3-3.1:5 info: Microsoft Nano Transceiver v1.0 for Bluetooth
    type: keyboard,mouse,HID driver: hid-generic,usbhid interfaces: 3 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
    chip-ID: 045e:0745 class-ID: 0300
  Device-2: 3-3.2:7 info: HP HP Color LaserJet Pro M478f-9f type: printer
    driver: usblp interfaces: 5 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1
    mode: 2.0 power: 2mA chip-ID: 03f0:c52a class-ID: 0701 serial: <filter>
  Hub-9: 4-0:1 info: super-speed hub ports: 4 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-10: 4-2:2 info: ASMedia ASM1074 SuperSpeed hub ports: 4 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 power: 8mA
    chip-ID: 174c:3074 class-ID: 0900
  Hub-11: 4-2.2:4 info: Texas Instruments TUSB8041 4-Port Hub ports: 4
    rev: 3.0 speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1
    chip-ID: 0451:8140 class-ID: 0900
  Hub-12: 4-2.2.2:6 info: VIA Labs VL812 Hub ports: 4 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 power: 8mA
    chip-ID: 2109:0812 class-ID: 0900
  Hub-13: 4-3:3 info: ASMedia ASM1074 SuperSpeed hub ports: 4 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 power: 8mA
    chip-ID: 174c:3074 class-ID: 0900
  Hub-14: 5-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-15: 6-0:1 info: super-speed hub ports: 4 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 48.0 C mobo: 43.0 C gpu: amdgpu temp: 52.0 C
    mem: 0.0 C
  Fan Speeds (rpm): cpu: 817 gpu: amdgpu fan: 1481
Repos:
  Packages: 1741 pm: pacman pkgs: 1731 libs: 463 tools: pamac pm: flatpak
    pkgs: 10
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://manjaro.kurdy.org/stable/$repo/$arch
    2: http://ftp.uni-kl.de/pub/linux/manjaro/stable/$repo/$arch
    3: https://mirror.alpix.eu/manjaro/stable/$repo/$arch
    4: https://mirror.23m.com/manjaro/stable/$repo/$arch
    5: https://ftp.halifax.rwth-aachen.de/manjaro/stable/$repo/$arch
    6: https://mirror.netcologne.de/manjaro/stable/$repo/$arch
    7: https://ftp.gwdg.de/pub/linux/manjaro/stable/$repo/$arch
    8: http://ftp.rz.tu-bs.de/pub/mirror/manjaro.org/repos/stable/$repo/$arch
Processes:
  CPU top: 5 of 424
  1: cpu: 6.7% command: firefox pid: 184549 mem: 702.4 MiB (2.1%)
  2: cpu: 6.2% command: firefox pid: 185860 mem: 373.2 MiB (1.1%)
  3: cpu: 6.0% command: mullvad-daemon pid: 823 mem: 51.4 MiB (0.1%)
  4: cpu: 5.1% command: firefox pid: 2854 mem: 1368.4 MiB (4.2%)
  5: cpu: 3.6% command: firefox pid: 181347 mem: 678.6 MiB (2.1%)
  Memory top: 5 of 424
  1: mem: 2288.7 MiB (7.1%) command: qbittorrent pid: 1840 cpu: 2.1%
  2: mem: 1368.4 MiB (4.2%) command: firefox pid: 2854 cpu: 5.1%
  3: mem: 829.2 MiB (2.5%) command: firefox pid: 154150 cpu: 0.9%
  4: mem: 797.2 MiB (2.4%) command: firefox pid: 3022 cpu: 1.4%
  5: mem: 739.4 MiB (2.3%) command: firefox pid: 116219 cpu: 0.3%
Info:
  Processes: 424 Power: uptime: 1d 17h 11m states: freeze,mem,disk
    suspend: deep avail: s2idle wakeups: 0 hibernate: platform avail: shutdown,
    reboot, suspend, test_resume image: 12.49 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
    tool: systemctl
  Compilers: clang: 19.1.7 gcc: 14.2.1 Shell: Sudo (sudo) v: 1.9.16p2
    default: Bash v: 5.2.37 running-in: konsole inxi: 3.3.38
18

Hmmm

OK then, it doesn’t seem like you’re using Nvidia, so I lost that bet.

But in that case, I still

:man_shrugging:

19

I get it, and it’s not creating any issue that I’m aware of. But does it only appear on my system or is it the same for everybody?
is it a manjaro problem or a KDE problem? should I report this to them? is it a hardware problem?

20

That’s good.

:man_shrugging:

:man_shrugging:

:man_shrugging:

I don’t think it’s a problem. (Or at least not something to be concerned about.)

1 Like