Arch Linux

marq13

Member

Registered: 2024-10-10

Posts: 24

Kernel panic - Fatal exception in interrupt - 6.18.9-arch1-2

Hello everyone, hope you’re all doing well.

I experienced a kernel panic around an hour ago, only once. My system hasn’t panicked at all in ~1.5 years, so I’m not sure how seriously to take this.

Here’s the link to the panic report generated.

From what I can see, the trace seems to point to a kernel driver issue in the audio stack. It may just be a coincidence, but I wanted to ask for advice, since I've never dealt with something like this.

A few additional notes:
   - I did a full system update today.
   - The panic seemed to occur right after unplugging the laptop.
   - I noticed a couple of sound-related errors in the TTY after closing X11 over the past few days — not sure if related.

Thanks in advance for any guidance!

All the best.

gromit

Administrator

From: Germany

Registered: 2024-02-10

Posts: 1,490

Website

Re: Kernel panic - Fatal exception in interrupt - 6.18.9-arch1-2

Do you also get the issue without the out of tree nvidia modules loaded?

loqs

Member

Registered: 2014-03-06

Posts: 18,788

Re: Kernel panic - Fatal exception in interrupt - 6.18.9-arch1-2

The backtrace from panic could well be corrupted. Assuming your system is not using xen then early_xen_iret_patch should never be called. Similar suspect backtrace with early_xen_iret_patch.

marq13

Member

Registered: 2024-10-10

Posts: 24

Re: Kernel panic - Fatal exception in interrupt - 6.18.9-arch1-2

Thanks for the replies.

The backtrace from panic could well be corrupted. Assuming your system is not using xen then early_xen_iret_patch should never be called.

I was not familiar with Xen before this. As far as I know my system is not using Xen at all - this is a normal Arch install on bare metal with only occasional VirtualBox use. From what I understand Xen is a separate type-1 hypervisor that requires explicit setup, so it shouldn’t be active accidentally.

That makes me think the backtrace may indeed be corrupted, but then it's hard to tell what actually triggered the panic.

Do you also get the issue without the out of tree nvidia modules loaded?

Since the panic happened only once and I cannot reproduce it (or at least I don't know how), I’ll keep monitoring the system. If it happens again I will try booting without the out-of-tree NVIDIA modules loaded.

Thanks again for the help. If there are any other recommendations or things I should check, please let me know so I can troubleshoot this as thoroughly as possible.
Is there any indication this could be hardware-related?