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

2018-04-18 Thread Vitalij Satanivskij
JB> > If you need any aditional information please tell me about. JB> JB> Can you perhaps turn off the stack trace on boot to not lose the panic messages JB> (remove KDB_TRACE from kernel config) and maybe modify the panic message to JB> include the IRQ number passed to nexus_add_irq? Hm

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

2018-04-18 Thread John Baldwin
On Wednesday, April 18, 2018 01:56:49 PM Vitalij Satanivskij wrote: > JB> > If you need any aditional information please tell me about. > JB> > JB> Can you perhaps turn off the stack trace on boot to not lose the panic > messages > JB> (remove KDB_TRACE from kernel config) and maybe modify the

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

2018-04-18 Thread Vitalij Satanivskij
JB> O, this is a different issue. Sorry. As a hack, try changing JB> 'FIRST_MSI_INT' to 512 in sys/amd64/include/intr_machdep.h. The issue JB> is that some systems now include more than 256 interrupt pins on I/O JB> APICs, so IRQ 256 is already reserved for use by one of those JB> interrupt

/usr/src/contrib/llvm/tools/clang/lib/Frontend/SerializedDiagnosticReader.cpp:5:1: error: expected unqualified-id

2018-04-18 Thread KIRIYAMA Kazuhiko
Hi, r332743 make builworld failed: c++ -O2 -pipe -I/usr/obj/usr/src/amd64.amd64/tmp/obj-tools/lib/clang/libclang -I/usr/obj/usr/src/amd64.amd64/tmp/obj-tools/lib/clang/libllvm -I/usr/src/contrib/llvm/tools/clang/lib/Basic -I/usr/src/contrib/llvm/tools/clang/lib/Driver