Re: [SOLVED] panic: kernel diagnostic assertion "gsi < NR_EVENT_CHANNELS" failed

[Chuck Zmudzinski <frchuckz%gmail.com@localhost>]

On 5/27/2025 12:08 AM, Chuck Zmudzinski wrote:
> Hi,
> 
> I have been trying to boot NetBSD/Xen Dom0 on an Intel i5-14500 Raptor Lake CPU.
> 
> Many problems discussed in previous thread on netbsd-users here: https://mail-index.netbsd.org/netbsd-users/2025/05/14/msg032601.html
> 
> I am moving the discussion here to port-xen and want to discuss the specific problem
> of a failed assertion I am getting on this hardware.
> 
> Snippet from the Dom0 messages on the serial console:
> 
> ---snip---
> [   1.0000030] nvme0 at pci2 dev 0 function 0: Western Digital (SanDisk) product 5041 (rev. 0x01)
> [   1.0000030] nvme0: NVMe 1.4
> [   1.0000030] panic: kernel diagnostic assertion "gsi < NR_EVENT_CHANNELS" failed: file "/usr/src/sys/arch/xen/x86/xen_intr.c", line 188 gsi 4159 >= NR_EVENT_CHANNELS 4096
> [   1.0000030] cpu0: Begin traceback...
> ---snip---
> 
> This is using a fairly recent -current daily build: NetBSD 10.99.14 (XEN3_DOM0) #0: Sun May 25 02:10:33 UTC 2025)
> 
> It looks like it will be impossible to successfully boot NetBSD/Xen Dom0 on
> this hardware until this failed assertion is fixed.
> 
> Is it possible to increase NR_EVENT_CHANNELS or decrease gsi? If so, how difficult is it?

I solved it by setting dom0_max_vcpus=4 on the command line (it is 20 by default with this CPU).
This reduces gsi so the assertion no longer fails. After this, I was able to boot the NetBSD 10.1
PV dom0 on this Intel i5-14500 CPU!

Thanks,

Chuck Zmudzinski