Finally gave up on windows and running manjaro as my goto. But Journalctl has errors

Hello,
So i’m finally at the point i’m giving up on Windows and I’m going to run Manjaro KDE then work on a windows VM for gaming. I went through 30 things to do after installing manjaro and got to the sudo journalctl -p 3 -xb and i get

-- Journal begins at Mon 2021-04-05 16:48:18 EDT, ends at Mon 2021-04-05 22:04:04 EDT. --
Apr 05 21:29:18 john-systemproductname kernel: __common_interrupt: 1.55 No irq handler for vector
Apr 05 21:29:18 john-systemproductname kernel: __common_interrupt: 2.55 No irq handler for vector
Apr 05 21:29:18 john-systemproductname kernel: __common_interrupt: 3.55 No irq handler for vector
Apr 05 21:29:18 john-systemproductname kernel: __common_interrupt: 4.55 No irq handler for vector
Apr 05 21:29:18 john-systemproductname kernel: __common_interrupt: 5.55 No irq handler for vector
Apr 05 21:29:18 john-systemproductname kernel: __common_interrupt: 6.55 No irq handler for vector
Apr 05 21:29:18 john-systemproductname kernel: __common_interrupt: 7.55 No irq handler for vector
Apr 05 21:29:18 john-systemproductname kernel: __common_interrupt: 8.55 No irq handler for vector
Apr 05 21:29:18 john-systemproductname kernel: __common_interrupt: 9.55 No irq handler for vector
Apr 05 21:29:18 john-systemproductname kernel: __common_interrupt: 10.55 No irq handler for vector
Apr 05 21:29:18 john-systemproductname kernel: 
Apr 05 21:29:19 john-systemproductname kernel: nvidia-gpu 0000:09:00.3: i2c timeout error e0000000
Apr 05 21:29:19 john-systemproductname kernel: ucsi_ccg 0-0008: i2c_transfer failed -110
Apr 05 21:29:19 john-systemproductname kernel: ucsi_ccg 0-0008: ucsi_ccg_init failed - -110
Apr 05 21:29:20 john-systemproductname kernel: hid-generic 0003:1532:024E.0009: No inputs registered, leaving
Apr 05 21:29:21 john-systemproductname kwin_x11[1181]: kwin_xkbcommon: XKB: Couldn't process include statement for 'us(\0)'
Apr 05 21:29:21 john-systemproductname kwin_x11[1181]: kwin_xkbcommon: XKB: Abandoning symbols file "(unnamed)"
Apr 05 21:29:21 john-systemproductname kwin_x11[1181]: kwin_xkbcommon: XKB: Failed to compile xkb_symbols
Apr 05 21:29:21 john-systemproductname kwin_x11[1181]: kwin_xkbcommon: XKB: Failed to compile keymap
Apr 05 21:29:24 john-systemproductname systemd-coredump[2155]: Process 1327 (org_kde_powerde) of user 1000 dumped core.
                                                               
                                                               Stack trace of thread 1327:
                                                               #0  0x00007fac73902ef5 raise (libc.so.6 + 0x3cef5)
                                                               #1  0x00007fac73902f80 __restore_rt (libc.so.6 + 0x3cf80)
                                                               #2  0x00007fac73a27505 __strlen_avx2 (libc.so.6 + 0x161505)
                                                               #3  0x00007fac6c22edbd n/a (libddcutil.so.4 + 0x3cdbd)
                                                               #4  0x00007fac6c23c864 n/a (libddcutil.so.4 + 0x4a864)
                                                               #5  0x00007fac6c23ca3c n/a (libddcutil.so.4 + 0x4aa3c)
                                                               #6  0x00007fac6c23d377 n/a (libddcutil.so.4 + 0x4b377)
                                                               #7  0x00007fac6c205f98 n/a (libddcutil.so.4 + 0x13f98)
                                                               #8  0x00007fac6c206ea4 n/a (libddcutil.so.4 + 0x14ea4)
                                                               #9  0x00007fac6c201c3d ddca_get_display_info_list2 (libddcutil.so.4 + 0xfc3d)
                                                               #10 0x00007fac6d5b3752 n/a (powerdevilupowerbackend.so + 0x17752)
                                                               #11 0x00007fac6d5aa207 _ZN23PowerDevilUPowerBackend4initEv (powerdevilupowerbackend.so + 0xe207)
                                                               #12 0x000055d830d868af n/a (org_kde_powerdevil + 0x78af)
                                                               #13 0x000055d830d851e5 n/a (org_kde_powerdevil + 0x61e5)
                                                               #14 0x00007fac738edb25 __libc_start_main (libc.so.6 + 0x27b25)
                                                               #15 0x000055d830d8525e _start (org_kde_powerdevil + 0x625e)
                                                               
                                                               Stack trace of thread 1414:
                                                               #0  0x00007fac739ba37f __poll (libc.so.6 + 0xf437f)
                                                               #1  0x00007fac71f9fbaf n/a (libglib-2.0.so.0 + 0xa7baf)
                                                               #2  0x00007fac71f4a3b1 g_main_context_iteration (libglib-2.0.so.0 + 0x523b1)
                                                               #3  0x00007fac71f4a402 n/a (libglib-2.0.so.0 + 0x52402)
                                                               #4  0x00007fac71f78fc1 n/a (libglib-2.0.so.0 + 0x80fc1)
                                                               #5  0x00007fac729b0299 start_thread (libpthread.so.0 + 0x9299)
                                                               #6  0x00007fac739c5053 __clone (libc.so.6 + 0xff053)
                                                               
                                                               Stack trace of thread 1361:
                                                               #0  0x00007fac739ba37f __poll (libc.so.6 + 0xf437f)
                                                               #1  0x00007fac7320863b n/a (libxcb.so.1 + 0xc63b)
                                                               #2  0x00007fac7320a37b xcb_wait_for_event (libxcb.so.1 + 0xe37b)
                                                               #3  0x00007fac6e708131 n/a (libQt5XcbQpa.so.5 + 0x5e131)
                                                               #4  0x00007fac73d3deff n/a (libQt5Core.so.5 + 0xcdeff)

I started to try and google one by one the issues, and everyone I’ve come by people seem to say its a normal issue, not to worry about it. So I wanted to come buy here, see if anyone spots anything I should worry about and/or how to fix it

I’m running the latest version of Manjaro KDE Currently on 5.10.23-1
I have a AMD Ryzen 9 3900x 12 core processer
I have a Nvidia RTX 2060
and I’m running 32 gig of ram on a 970 1tb evo m.2

Any other info I can provide please let me know. Just want to make sure I fix anything that needs to be fixed

When pasting terminal output, highlight it and use the Preformatted text </> button.

Alternatively, add three backticks ` above and below the text:

```
text
```

Please edit your post accordingly.

I think that worked!

Hi, hopefully some of this is of use:

  1. The “No irq handler for vector” I think is a bug with some motherboards that I have seen being solved by adding acpi=noirq or acpi=backlight_vendor as a kernel parameter, also sometimes with a BIOS update.
  2. There are issues with Nvidia graphics in Linux that I have read about, and this “i2c timeout error” I think is due to this bug: i2c nvidia gpu and you could blacklist i2c_nvidia_gpu kernel module to get rid of the error (see Kernel Module Blacklisting)
  3. I had this kwin keyboard error show with a KDE update fairly recently, got rid of the error from log by editing ~/.config/kxkbrc and changing VariantList=\\0 to VariantList=basic
  4. KDE Power Devil is crashing on your system, not sure why this is happening. Perhaps if the one or both of the first two issues are cleared it may stop this happening - but if not, this looks like something you may want to contact the upstream KDE developers about.

Some of these errors may be harmless, it is the Power Devil crashing that I would personally be most keen to fix. That said, it could be a symptom of one of the other issues. Are you noticing any issues in functionality as well?

Honestly not really. I’m fighting with openrazer now to work. Some times on Manjaro it works and sometimes it doesnt. But alot of reboots. It seems like every so often it gets hung up on a reboot and i have to force reboot. It usually shows the No irq handler, then it has another command i’ll have to write down next time it shows up. But I can look into letting the KDE devs know and see what they say

Apr 06 11:04:14 john-systemproductname kernel: AMD-Vi: [Firmware Bug]: : No southbridge IOAPIC found
Apr 06 11:04:14 john-systemproductname kernel: AMD-Vi: Disabling interrupt remapping
Apr 06 11:04:14 john-systemproductname kernel: 
Apr 06 11:04:16 john-systemproductname kernel: hid-generic 0003:1532:024E.0009: No inputs registered, leaving
Apr 06 11:04:20 john-systemproductname systemd-coredump[2052]: Process 1332 (org_kde_powerde) of user 1000 dumped core.
                                                               
                                                               Stack trace of thread 1332:
                                                               #0  0x00007f393b83aef5 raise (libc.so.6 + 0x3cef5)
                                                               #1  0x00007f393b83af80 __restore_rt (libc.so.6 + 0x3cf80)
                                                               #2  0x00007f393b95f505 __strlen_avx2 (libc.so.6 + 0x161505)
                                                               #3  0x00007f3934166dbd n/a (libddcutil.so.4 + 0x3cdbd)
                                                               #4  0x00007f3934174864 n/a (libddcutil.so.4 + 0x4a864)
                                                               #5  0x00007f3934174a3c n/a (libddcutil.so.4 + 0x4aa3c)
                                                               #6  0x00007f3934175377 n/a (libddcutil.so.4 + 0x4b377)
                                                               #7  0x00007f393413df98 n/a (libddcutil.so.4 + 0x13f98)
                                                               #8  0x00007f393413eea4 n/a (libddcutil.so.4 + 0x14ea4)
                                                               #9  0x00007f3934139c3d ddca_get_display_info_list2 (libddcutil.so.4 + 0xfc3d)
                                                               #10 0x00007f39354eb752 n/a (powerdevilupowerbackend.so + 0x17752)
                                                               #11 0x00007f39354e2207 _ZN23PowerDevilUPowerBackend4initEv (powerdevilupowerbackend.so + 0xe207)
                                                               #12 0x000055d20ad558af n/a (org_kde_powerdevil + 0x78af)
                                                               #13 0x000055d20ad541e5 n/a (org_kde_powerdevil + 0x61e5)
                                                               #14 0x00007f393b825b25 __libc_start_main (libc.so.6 + 0x27b25)
                                                               #15 0x000055d20ad5425e _start (org_kde_powerdevil + 0x625e)
                                                               
                                                               Stack trace of thread 1384:
                                                               #0  0x00007f393b8fe60d recvmsg (libc.so.6 + 0x10060d)
                                                               #1  0x00007f3939dce257 n/a (libudev.so.1 + 0x10257)
                                                               #2  0x00007f3939dcec8b udev_monitor_receive_device (libudev.so.1 + 0x10c8b)
                                                               #3  0x00007f39341475f2 n/a (libddcutil.so.4 + 0x1d5f2)
                                                               #4  0x00007f3939eb0fc1 n/a (libglib-2.0.so.0 + 0x80fc1)
                                                               #5  0x00007f393a8e8299 start_thread (libpthread.so.0 + 0x9299)
                                                               #6  0x00007f393b8fd053 __clone (libc.so.6 + 0xff053)
                                                               
                                                               Stack trace of thread 1378:
                                                               #0  0x00007f393b8f237f __poll (libc.so.6 + 0xf437f)
                                                               #1  0x00007f3939ed7baf n/a (libglib-2.0.so.0 + 0xa7baf)
                                                               #2  0x00007f3939e823b1 g_main_context_iteration (libglib-2.0.so.0 + 0x523b1)
                                                               #3  0x00007f3939e82402 n/a (libglib-2.0.so.0 + 0x52402)
                                                               #4  0x00007f3939eb0fc1 n/a (libglib-2.0.so.0 + 0x80fc1)
                                                               #5  0x00007f393a8e8299 start_thread (libpthread.so.0 + 0x9299)
                                                               #6  0x00007f393b8fd053 __clone (libc.so.6 + 0xff053)
                                                               
                                                               Stack trace of thread 1358:
                                                               #0  0x00007f393b8f237f __poll (libc.so.6 + 0xf437f)
                                                               #1  0x00007f393b14063b n/a (libxcb.so.1 + 0xc63b)
                                                               #2  0x00007f393b14237b xcb_wait_for_event (libxcb.so.1 + 0xe37b)
                                                               #3  0x00007f3936640131 n/a (libQt5XcbQpa.so.5 + 0x5e131)
                                                               #4  0x00007f393bc75eff n/a (libQt5Core.so.5 + 0xcdeff)
                                                               #5  0x00007f393a8e8299 start_thread (libpthread.so.0 + 0x9299)
                                                               #6  0x00007f393b8fd053 __clone (libc.so.6 + 0xff053)
                                                               
                                                               Stack trace of thread 1372:

After making those changing this is in my sudo journalctl -p3 -xb

Ok, so that has appeared to have cleared your log a bit.

The “AMD-Vi Firmware Bug” I think might require a UEFI firmware update; it might also be possible to add the amd_iommu_dump=1 kernel parameter to get some more information, then use the information from that to add ivrs_ioapic kernel parameter option(s). Are you on the latest firmware for your motherboard? I would probably look to update if there is a newer version.

The hid-generic issue I guess is to do with an input device - do you have any problems getting your mouse to work?

With regards to KDE Power Devil, I would recommend taking a look at the upstream KDE bug reports and see if anyone else has a similar issue and subscribe to it if so; if not, perhaps post a bug report there.

I would also try using the very latest stable kernel (5.11 as of now), as you have new hardware and there might be some relevant fixes for you. Keep 5.10 installed as well, so you can swap back if any issues :slight_smile:

the only issue i have now is the bootup gets hung up on /dev/nme0n1p1: clean 274117/61054976 files, 6295243/244189752 blocks from what ive read is thats normal but it gets stuck there on bootup

-- Journal begins at Wed 2021-04-07 01:05:55 EDT, ends at Wed 2021-04-07 01:20:31 EDT. --
Apr 07 01:17:16 john-systemproductname kernel: AMD-Vi: [Firmware Bug]: : No southbridge IOAPIC found
Apr 07 01:17:16 john-systemproductname kernel: AMD-Vi: Disabling interrupt remapping
Apr 07 01:17:16 john-systemproductname kernel: 
Apr 07 01:17:18 john-systemproductname kernel: hid-generic 0003:1532:024E.0009: No inputs registered, leaving
Apr 07 01:17:21 john-systemproductname pulseaudio[1461]: Found duplicated D-Bus path for adapter /org/bluez/hci0

After tons of reinstall’s today learning my lesson on things these are the last of the errors I got. And honestly don’t think i’m gonna screw with them unless they are bad lol

Absolutely, if there are no actual issues for you it’s generally not much of a problem. I think those errors listed in your last post are linked to virtualisation, input and bluetooth audio; if you have no problems with any of these things (or don’t use them), then they can be safely ignored.

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.