/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 
-I/usr/src/contrib/llvm/tools/clang/include -I/usr/src/lib/clang/include 
-I/usr/src/contrib/llvm/include -DLLVM_BUILD_GLOBAL_ISEL -D__STDC_LIMIT_MACROS 
-D__STDC_CONSTANT_MACROS 
-DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd12.0\" 
-DLLVM_HOST_TRIPLE=\"x86_64-unknown-freebsd12.0\" 
-DDEFAULT_SYSROOT=\"/usr/obj/usr/src/amd64.amd64/tmp\" -ffunction-sections 
-fdata-sections -gline-tables-only -MD 
-MF.depend.Frontend_SerializedDiagnosticReader.o 
-MTFrontend/SerializedDiagnosticReader.o -Qunused-arguments 
-I/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/include  -std=c++11 
-fno-exceptions -fno-rtti -gline-tables-only -stdlib=libc++ 
-Wno-c++11-extensions  -c 
/usr/src/contrib/llvm/tools/clang/lib/Frontend/SerializedDiagnosticReader.cpp 
-o Frontend/Se!
 rializedDiagnosticReader.o
/usr/src/contrib/llvm/tools/clang/lib/Frontend/SerializedDiagnosticReader.cpp:5:1:
 error: expected unqualified-id
/7 This fi!is dW0<8B>ibut[d<8C>nder ,<9C> 
University of IllinEV<90>Open Source
^
/usr/src/contrib/llvm/tools/clang/lib/Frontend/SerializedDiagnosticReader.cpp:5:13:
 error: source file is not valid UTF-8
/7 This fi!is dW0<8B>ibut[d<8C>nder ,<9C> 
University of IllinEV<90>Open Source
   ^
/usr/src/contrib/llvm/tools/clang/lib/Frontend/SerializedDiagnosticReader.cpp:5:21:
 error: source file is not valid UTF-8
/7 This fi!is dW0<8B>ibut[d<8C>nder ,<9C> 
University of IllinEV<90>Open Source
 ^
/usr/src/contrib/llvm/tools/clang/lib/Frontend/SerializedDiagnosticReader.cpp:5:29:
 error: source file is not valid UTF-8
/7 This fi!is dW0<8B>ibut[d<8C>nder ,<9C> 
University of IllinEV<90>Open Source
   ^
/usr/src/contrib/llvm/tools/clang/lib/Frontend/SerializedDiagnosticReader.cpp:5:37:
 error: source file is not valid UTF-8
/7 This fi!is dW0<8B>ibut[d<8C>nder ,<9C> 
University of IllinEV<90>Open Source
 ^
/usr/src/contrib/llvm/tools/clang/lib/Frontend/SerializedDiagnosticReader.cpp:5:60:
 error: source file is not valid UTF-8
/7 This fi!is dW0<8B>ibut[d<8C>nder ,<9C> 
University of IllinEV<90>Open Source

   ^
/usr/src/contrib/llvm/tools/clang/lib/Frontend/SerializedDiagnosticReader.cpp:5:61:
 error: source file is not valid UTF-8
/7 This fi!is dW0<8B>ibut[d<8C>nder ,<9C> 
University of IllinEV<90>Open Source

   ^
/usr/src/contrib/llvm/tools/clang/lib/Frontend/SerializedDiagnosticReader.cpp:10:10:
 fatal error: 'qlang/Frontend/SerializeNagnosticReader(h' file not found
#include "qlang/Frontend/SerializeN<87>oagnosticReader(h"
 ^~~~
8 errors generated.
*** Error code 1

Stop.
make[5]: stopped in /usr/src/lib/clang/libclang
*** Error code 1

Stop.
make[4]: stopped in /usr/src/lib/clang
*** Error code 1

Stop.
make[3]: stopped in /usr/src
*** Error code 1

Stop.
make[2]: stopped in /usr/src
*** Error code 1

Stop.
make[1]: stopped in /usr/src

---
KIRIYAMA Kazuhiko
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


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 pins.  The real fix is that I need to make FIRST_MSI_INT
JB> dynamic instead of a constant and just define it as the first free IRQ
JB> after the I/O APICs have probed.
JB> 

Yep. That it.

But just one note 

irq585: ccp14:721 @cpu0(domain0): 0
irq586: ccp14:723 @cpu0(domain0): 0
irq587: ccp15:725 @cpu0(domain0): 0

If I understand correctly number of irq's even more then 512, so better to 
change to real number in system ?

Or this is another case ?

Any way thank you for help. Now I can use system with msix and msi enabled.

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


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 panic message 
> to
> JB> include the IRQ number passed to nexus_add_irq?
> 
> 
> Hm looks like it's always irq with number 256
> eg hpet - 256 
> igb - 256 
> 
> Chenged made for it was
> 
> Index: sys/x86/x86/nexus.c
> ===
> --- sys/x86/x86/nexus.c (revision 332663)
> +++ sys/x86/x86/nexus.c (working copy)
> @@ -698,7 +698,7 @@
>  {
>  
> if (rman_manage_region(&irq_rman, irq, irq) != 0)
> -   panic("%s: failed", __func__);
> +   panic("%s: failed irq is: %lu", __func__, irq);
>  }

O, this is a different issue.  Sorry.  As a hack, try changing
'FIRST_MSI_INT' to 512 in sys/amd64/include/intr_machdep.h.  The issue
is that some systems now include more than 256 interrupt pins on I/O
APICs, so IRQ 256 is already reserved for use by one of those
interrupt pins.  The real fix is that I need to make FIRST_MSI_INT
dynamic instead of a constant and just define it as the first free IRQ
after the I/O APICs have probed.

-- 
John Baldwin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


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 looks like it's always irq with number 256
eg hpet - 256 
igb - 256 

Chenged made for it was

Index: sys/x86/x86/nexus.c
===
--- sys/x86/x86/nexus.c (revision 332663)
+++ sys/x86/x86/nexus.c (working copy)
@@ -698,7 +698,7 @@
 {
 
if (rman_manage_region(&irq_rman, irq, irq) != 0)
-   panic("%s: failed", __func__);
+   panic("%s: failed irq is: %lu", __func__, irq);
 }



___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"