I am stuck at "_common_interrupt " screen. Help…
what were you doing prior? updating/installing/uninstalling something?
Just booting my computer. Tried to attach picture here but it won’t allow to do it.
so everything was working prior?
Yes, everything was working normal.
so the best option is to chroot… boot into manjaro live usb, connect to internet, chroot:
manjaro-chroot -a
rerun update:
pacman-mirrors -f 5 && pacman -Syyu
if there are no errors, and you are up to date, post output from:
mhwd-kernel -li
mhwd -l -li
and logs from the failed boot:
journalctl -b-1 -p4 --no-pager
1 Like
::INFO Mirror list generated and saved to: /etc/pacman.d/mirrorlist
:: Synchronizing package databases...
core
extra 161.7 KiB 284 KiB/s 00:01 [###############################] 100%
community 1857.5 KiB 821 KiB/s 00:02 [###############################] 100%
multiliby 7.5 MiB 597 KiB/s 00:13 [###############################] 100%
:: Starting full system upgrade....6 KiB 621 KiB/s 00:00 [###############################] 100%
there is nothing to do
[manjaro /]# mhwd-kernel -li
Currently running: 5.4.23-1-MANJARO (linux54)
The following kernels are installed in your system:
* linux515
[manjaro /]# mhwd -l -li
> Installed PCI configs:
--------------------------------------------------------------------------------
NAME VERSION FREEDRIVER TYPE
--------------------------------------------------------------------------------
video-linux 2018.05.04 true PCI
Warning: No installed USB configs!
> 0000:00:01.0 (0300:1002:9903) Display controller ATI Technologies Inc:
--------------------------------------------------------------------------------
NAME VERSION FREEDRIVER TYPE
--------------------------------------------------------------------------------
video-linux 2018.05.04 true PCI
video-modesetting 2020.01.13 true PCI
video-vesa 2017.03.12 true PCI
> 0000:01:00.0 (0300:1002:6840) Display controller ATI Technologies Inc:
--------------------------------------------------------------------------------
NAME VERSION FREEDRIVER TYPE
--------------------------------------------------------------------------------
video-linux 2018.05.04 true PCI
video-modesetting 2020.01.13 true PCI
video-vesa 2017.03.12 true PCI
[manjaro /]# journalctl -b-1 -p4 --no-pager
Jan 30 19:29:14 raamivalmennus-hppaviliong7notebookpc kernel: __common_interrupt: 1.55 No irq handler for vector
Jan 30 19:29:14 raamivalmennus-hppaviliong7notebookpc kernel: #2
Jan 30 19:29:14 raamivalmennus-hppaviliong7notebookpc kernel: __common_interrupt: 2.55 No irq handler for vector
Jan 30 19:29:14 raamivalmennus-hppaviliong7notebookpc kernel: #3
Jan 30 19:29:14 raamivalmennus-hppaviliong7notebookpc kernel: __common_interrupt: 3.55 No irq handler for vector
Jan 30 19:29:14 raamivalmennus-hppaviliong7notebookpc kernel: mtrr: your CPUs had inconsistent variable MTRR settings
Jan 30 19:29:15 raamivalmennus-hppaviliong7notebookpc systemd-journald[228]: File /var/log/journal/f75d70dc23714911999a5c81bbbd9880/system.journal corrupted or uncleanly shut down, renaming and replacing.
Jan 30 19:29:16 raamivalmennus-hppaviliong7notebookpc kernel: wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found
Jan 30 19:29:16 raamivalmennus-hppaviliong7notebookpc kernel: wmi_bus wmi_bus-PNP0C14:00: WQBD data block query control method not found
Jan 30 19:29:16 raamivalmennus-hppaviliong7notebookpc kernel: wmi_bus wmi_bus-PNP0C14:00: WQBE data block query control method not found
Jan 30 19:29:16 raamivalmennus-hppaviliong7notebookpc kernel: wmi_bus wmi_bus-PNP0C14:00: WQBG data block query control method not found
Jan 30 19:29:16 raamivalmennus-hppaviliong7notebookpc kernel: wmi_bus wmi_bus-PNP0C14:00: WQBJ data block query control method not found
Jan 30 19:29:16 raamivalmennus-hppaviliong7notebookpc kernel: ACPI Warning: SystemIO range 0x0000000000000B00-0x0000000000000B08 conflicts with OpRegion 0x0000000000000B00-0x0000000000000B0F (\_SB.PCI0.SMBS.SMB0) (20210730/utaddress-204)
Jan 30 19:29:16 raamivalmennus-hppaviliong7notebookpc kernel: wdat_wdt wdat_wdt: can't request region for resource [mem 0xfec000f0-0xfec000f3]
Jan 30 19:29:16 raamivalmennus-hppaviliong7notebookpc kernel: wdat_wdt: probe of wdat_wdt failed with error -16
Jan 30 19:29:17 raamivalmennus-hppaviliong7notebookpc kernel: ATPX version 1, functions 0x00000003
Jan 30 19:29:17 raamivalmennus-hppaviliong7notebookpc kernel: resource sanity check: requesting [mem 0x000c0000-0x000dffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000c3fff window]
Jan 30 19:29:17 raamivalmennus-hppaviliong7notebookpc kernel: caller pci_map_rom+0x65/0x180 mapping multiple BARs
Jan 30 19:29:18 raamivalmennus-hppaviliong7notebookpc kernel: kvm: disabled by bios
Jan 30 19:29:18 raamivalmennus-hppaviliong7notebookpc kernel: kvm: disabled by bios
Jan 30 19:29:18 raamivalmennus-hppaviliong7notebookpc kernel: kvm: disabled by bios
Jan 30 19:29:18 raamivalmennus-hppaviliong7notebookpc kernel: kvm: disabled by bios
Jan 30 19:29:19 raamivalmennus-hppaviliong7notebookpc kernel: kauditd_printk_skb: 249 callbacks suppressed
Jan 30 19:29:27 raamivalmennus-hppaviliong7notebookpc tlp[902]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
Jan 30 19:29:27 raamivalmennus-hppaviliong7notebookpc tlp[902]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
Jan 30 19:29:27 raamivalmennus-hppaviliong7notebookpc tlp[902]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
Jan 30 19:29:27 raamivalmennus-hppaviliong7notebookpc tlp[902]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.
Jan 30 19:29:30 raamivalmennus-hppaviliong7notebookpc sddm-helper[937]: pam_kwallet5(sddm-autologin:auth): pam_kwallet5: Couldn't get user info (passwd) info
Jan 30 19:29:32 raamivalmennus-hppaviliong7notebookpc sddm-helper[937]: [PAM] authenticate: Tunnistautumisvirhe
Jan 30 19:29:32 raamivalmennus-hppaviliong7notebookpc sddm[653]: Authentication error: "Tunnistautumisvirhe"
Jan 30 19:29:32 raamivalmennus-hppaviliong7notebookpc sddm[653]: Auth: sddm-helper exited with 1
well it looks ok…
so enter (if you can) in the stuck screen into TTY - ctrl + alt + f2 or f1-f6, enter your credentials, and type:
startx
and post picture of the output
Looks like I do not remember my credentails, oh boy. 
I have to google that first.
If I remember right, some Python update went wrong over and over again. Then I removed it. And after that I changed my username, but I am pretty sure that password is the same. So maybe that Python was thing I should not touch? I though it is not related to run the system but I think I was wrong.
You can boot a live system and then mount the system disk and list the contents of your $HOME directory - the user accounts there usually are the different user names.
The user that needs admin rights has to be in the “wheel” group - if you simply created a new user, that is usually not the case for the new user - hopefully you still have the old one also.
Thank you. How I find this directory? Looks familiar but I do not remember.
I described as best (and short) as I could.
search … look …
Funny. I found them and I guessed right.
But, now I found my files! Maybe I just move them to safe and re-install. It is quite mess to deal with this otherwise.
I think my problem is THIS:
"The error message “_common_interrupt: 1.55 No irq handler for vector” is related to the handling of hardware interrupts in the Linux kernel. To resolve this issue, the following steps:
Boot into single user mode: During boot, when the boot menu appears, select “Mageia 8” and then press the “e” key to edit the boot parameters. Add “single” to the end of the line starting with “linux”. Then press “Ctrl + X” to boot into single user mode.
Modify the GRUB configuration: Once you have logged in as root in single user mode, run the following command: “nano /etc/default/grub”. In the GRUB configuration file, find the line starting with “GRUB_CMDLINE_LINUX_DEFAULT” and add “noapic” to the end of the line. Save and exit the file.
Update the GRUB boot loader: Run the following command to update the GRUB boot loader: “grub2-mkconfig -o /boot/grub2/grub.cfg”.
Reboot: Run the command “reboot” to restart the system. The system should now boot without the error message."
But I figure to find my boot parameter, but I haven’t understood most of that text.
I let you guys know if I do clean install.
looking at the logs, i highly doubt that this is the reason for your issue, since the last log is related to sddm, which is the display manager…