Thanks, all the interrupts look like I would expect.
> Likely unrelated, but maybe worth noting: the display was blank with this
> kernel (although I could see the desktop fine over VNC). I suspect it's
> caused by me using the kernel from:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git. If I understand
> correctly, this is the tree we're supposed to use for submitting patches to
> the IRQ subsystem.
Yeah that should be unrelated; it's because the x86 tree didn't pick up other stuff in 6.6-rcs. I see the UCSI NULL pointer bug too which got fixed in later RCs.
> I'll also try the patch series against 6.6.0-rc6, which I've been using so
> far, to make sure the blank screen is not caused by the patch.
Thanks, hopefully everything should be good there. If you pair it with your NVME suspend fix patch (or iommu=pt) I'd expect you're in good shape.
Thanks, all the interrupts look like I would expect.
> Likely unrelated, but maybe worth noting: the display was blank with this kernel. org/pub/ scm/linux/ kernel/ git/tip/ tip.git. If I understand
> kernel (although I could see the desktop fine over VNC). I suspect it's
> caused by me using the kernel from:
> git://git.
> correctly, this is the tree we're supposed to use for submitting patches to
> the IRQ subsystem.
Yeah that should be unrelated; it's because the x86 tree didn't pick up other stuff in 6.6-rcs. I see the UCSI NULL pointer bug too which got fixed in later RCs.
> I'll also try the patch series against 6.6.0-rc6, which I've been using so
> far, to make sure the blank screen is not caused by the patch.
Thanks, hopefully everything should be good there. If you pair it with your NVME suspend fix patch (or iommu=pt) I'd expect you're in good shape.