Current panic on boot on H11DSI motherboard with epyc cpu (nexus_add_irq: failed)

[John Baldwin]

On Tuesday, April 17, 2018 10:15:53 PM Vitalij Satanivskij wrote:
> Dear John
> 
> I'm try patch with no success
> 
> http://hell.ukr.net/panic/recorder_patch165.webm
> 
> Also I'm enable verbose boot and record boot process (hpet was disabled so crash in another driver atach)
> http://hell.ukr.net/panic/recorder_patch_verbose.webm
> 
> root at test:/usr/src # svnlite diff
> Index: sys/x86/x86/msi.c
> ===================================================================
> --- sys/x86/x86/msi.c   (revision 332650)
> +++ sys/x86/x86/msi.c   (working copy)
> @@ -404,7 +404,7 @@
>         /* Do we need to create some new sources? */
>         if (cnt < count) {
>                 /* If we would exceed the max, give up. */
> -               if (i + (count - cnt) > FIRST_MSI_INT + NUM_MSI_INTS) {
> +               if (i + (count - cnt) >= FIRST_MSI_INT + NUM_MSI_INTS) {
>                         mtx_unlock(&msi_lock);
>                         free(mirqs, M_MSI);
>                         return (ENXIO);
> @@ -645,7 +645,7 @@
>         /* Do we need to create a new source? */
>         if (msi == NULL) {
>                 /* If we would exceed the max, give up. */
> -               if (i + 1 > FIRST_MSI_INT + NUM_MSI_INTS) {
> +               if (i + 1 >= FIRST_MSI_INT + NUM_MSI_INTS) {
>                         mtx_unlock(&msi_lock);
>                         return (ENXIO);
>                 }
> root at test:/usr/src
> 
> If you need any aditional information please tell me about. 

Can you perhaps turn off the stack trace on boot to not lose the panic messages
(remove KDB_TRACE from kernel config) and maybe modify the panic message to
include the IRQ number passed to nexus_add_irq?

-- 
John Baldwin