Zorin Randomly stopped working

Hardware Support
1

Hello, I have a seemingly critical error and have zero idea what to do about it, have been using zorin since the End of support for w10 and am by no means a tech expert. as of 12hrs ago whenever I try to boot my laptop I get the same error "[0.121416] No irq handler for 0.110"

Hardware is an HP envy x360 convertible 15m-bq1xx.
CPU: ryzen 5 2500u
16gb ram

Bios was updated last week

2

Hello Neil. Welcome to the forum.

This sort of error can occur as a result of firmware (BIOS/UEFI) inconsistencies, possibly resulting from your recent BIOS update. Most of the time it is fairly harmless, but if your system freezes or fails to boot, then it indicates a resource conflict where a piece of vital hardware (like your drive controller) can't talk to the CPU. Looking at the numbers....

  • [0.121416]: The timestamp (seconds since boot). This happened very early.
  • 0.110: This represents the specific hardware vector or pin that sent the signal.
    On the HP Envy x360 with the Ryzen 5 2500U, this specific error is a known "quirk" that can occur because of that generation's APU and motherboard pairing.

On Raven Ridge systems (like your 2500U), the 0.110 vector usually refers to a GPIO (General Purpose Input/Output) pin managed by the AMD Promontory/PCH chipset.

The "No irq handler" message is almost certainly related to the HP-specific implementation of the touchpad or the touchscreen. During the very early stages of the boot process (at 0.12 seconds), the Linux kernel is initializing the I/O drivers. The hardware sends an interrupt—essentially tapping the CPU on the shoulder to say "I'm here"—but the specific AMD GPIO driver hasn't finished loading yet. Because the kernel doesn't have the driver active at that microsecond, it reports that it doesn't know what to do with the signal.

Since this is an ACPI/Interrupt routing mismatch between HP's firmware and the Linux kernel, you can try "quieting" it with a specific kernel parameter.

When a computer boots to a frozen login page, you can often still switch over to a text-only terminal. So, the next time you reboot (actually try powering off completely this time, wait a minute, and power back on) if/when your login fails:

  1. While the computer is stuck, press Ctrl + Alt + F3 (or F4, F5, etc.).
  2. The screen should go black and show an (often tiny) login prompt in the upper right corner: zorin-os login:.
  3. Type your username and press Enter.
  4. Type your password (it will hide the characters as you type) and press Enter.
  5. Open the grub file by running: sudo nano /etc/default/grub
  6. Find the line starting with GRUB_CMDLINE_LINUX_DEFAULT.
  7. To this line add either pci=noaer or ivrs_ioapic[32]=00:14.0 If one doesn't do the trick, repeat the process and try the other. (The second one is a common fix for Ryzen 2000-series mobile laptops to correctly map those "stray" interrupts).
  8. Save the file with a Ctrl-O plus Enter, then Ctrl-X to exit.
  9. Run sudo update-grub, followed by a reboot.