Adding Inventory

Adding Inventory

[Oğuzhan ÇAĞLAR]

[-- Attachment #1: Type: text/plain, Size: 771 bytes --]

Hello,


I'm working on openbmc for ast2500 bmc. I want to add inventory such as CPU and DIMM etc. I added the chassis from .json file but I couldn't add the CPU and DIMM. I know this is to related with entity-manager. How can I add these inventory on WEBUI? Can you give some information about this issue?


Regards.

Oğuzhan Çağlar
Software Design Engineer



[X]





[X]

Pavo Tasarım Üretim Elektronik Tic. A.Ş.
Teknopark İstanbul, Kurtköy Pendik İSTANBUL


       [X] <http://pavotek.com.tr/>

Tel             : +90 (216) 354 72 86

Faks         : +90 (216) 354 76 77

Gsm          : +90 (507) 585 10 60

oguzhan.caglar@pavotek.com.tr<mailto:oguzhan.caglar@pavotek.com.tr>



www.pavotek.com.tr<http://www.pavotek.com.tr/>



[-- Attachment #2: Type: text/html, Size: 7559 bytes --]

Re: Adding Inventory

[Andrei Kartashev]

Hello Oguzhan,

This is a very common question for newcomers, I believe is was already
answered somewhere in the list.
BMC out of the box don't have any knowledge on host's equipment (CPU,
DIMM, Drive, AIC, etc) - it is up to you to deliver this information
from host to BMC. As for now the most common way to feed BMC the
information regarding CPU and DIMM is to transfer smbios tables via
ipmi. You can implement any other mechanism but any way, you need to
have some code in your BIOS.

As soon as you have the CPU/DIMM information on BMC it can be shown in
bmcweb by implementing corresponding dbus interfaces
(xyz.openbmc_project.Inventory.Item.Cpu and
xyz.openbmc_project.Inventory.Item.Dimm). smbiosmdrv2 daemon do this,
but you also can add EntityManager configuration files for this or
write your own daemon to expose the interfaces.

On Thu, 2022-08-04 at 08:07 +0000, Oğuzhan ÇAĞLAR wrote:
> Hello,
> 
> I'm working on openbmc for ast2500 bmc. I want to add inventory such
> as CPU and DIMM etc. I added the chassis from .json file but I
> couldn't add the CPU and DIMM. I know this is to related with entity-
> manager. How can I add these inventory on WEBUI? Can you give some
> information about this issue?
> 
> Regards.
> 
> Oğuzhan Çağlar
> Software Design Engineer
>  
>  
>  
> Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> Teknopark İstanbul, Kurtköy Pendik İSTANBUL
>  
>       
> Tel             : +90 (216) 354 72 86
> Faks         : +90 (216) 354 76 77
> Gsm          : +90 (507) 585 10 60
> oguzhan.caglar@pavotek.com.tr
>  
> www.pavotek.com.tr
> 
>  

-- 
Best regards,
Andrei Kartashev,
Lead BMC Developer

Re: Ynt: (External) Re: Adding Inventory

[Andrei Kartashev]

I have no idea on what do you mean saying "added the CPU and DIMM
configuration files within the .yaml files", but I guess you are trying
to hardcode this information, which I believe not what ou actually
expect to get.
You probably should learn how the OpenBMC works inside. You can use
busctl tool for that.

Regarding compilation error of smbios-mdr daemon, I can say nothing
without knowing the issue. There should not be any special
configuration files for this smbios-mdr recipe but probably you trying
to build CPUInfo part of the recipe without having PECI library. You
likely should disable cpuinfo app.

On Fri, 2022-08-12 at 06:50 +0000, Oğuzhan ÇAĞLAR wrote:
> Hi Andrei,
> 
> Thank you for your information. I have already added the CPU and DIMM
> configuration files within the .yaml files. When I added these
> files(related to the path: xyz.openbmc_project.Inventory.Item.Cpu
> and xyz.openbmc_project.Inventory.Item.Dimm), I see the CPU and DIMM
> entries over WebUI. However, In this way, I add the properties such
> as (PartNumber, SerialNumber, etc.) on my own. I have already
> generated a .bin file that has FRU information (chassis, board etc.)
> and I included this in BMC's image file. In addition, I see the
> properties related to Chassis, Board on WebUI.
> 
> I have already checked the smbios-mdr daemon in openbmc. However,
> when I include this daemon in my yocto image, the bitbake shows some
> errors that are related to smbios-mdr's .cpp files. I guess I have to
> create some configuration files before doing it. Is it wrong? What
> should I do?
> 
> I guess I have to need some code in BIOS. Is there any example to do
> this? I don't know where I should start. 
> 
> Thank you.
> 
> Oğuzhan Çağlar
> Software Design Engineer
>  
>  
>  
> Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> Teknopark İstanbul, Kurtköy Pendik İSTANBUL
>  
>       
> Tel             : +90 (216) 354 72 86
> Faks         : +90 (216) 354 76 77
> Gsm          : +90 (507) 585 10 60
> oguzhan.caglar@pavotek.com.tr
>  
> www.pavotek.com.tr
> 
>  
> Gönderen: Andrei Kartashev <a.kartashev@yadro.com>
> Gönderildi: 11 Ağustos 2022 Perşembe 22:28:16
> Kime: Oğuzhan ÇAĞLAR; openbmc@lists.ozlabs.org
> Konu: (External) Re: Adding Inventory
>  
> 
> Warning: This e-mail came from an external source. If you do not
> trust the sender or if there is anything suspicious in the content of
> the e-mail, please inform the IT department.
> 
> 
> 
> Hello Oguzhan,
> 
> This is a very common question for newcomers, I believe is was
> already
> answered somewhere in the list.
> BMC out of the box don't have any knowledge on host's equipment (CPU,
> DIMM, Drive, AIC, etc) - it is up to you to deliver this information
> from host to BMC. As for now the most common way to feed BMC the
> information regarding CPU and DIMM is to transfer smbios tables via
> ipmi. You can implement any other mechanism but any way, you need to
> have some code in your BIOS.
> 
> As soon as you have the CPU/DIMM information on BMC it can be shown
> in
> bmcweb by implementing corresponding dbus interfaces
> (xyz.openbmc_project.Inventory.Item.Cpu and
> xyz.openbmc_project.Inventory.Item.Dimm). smbiosmdrv2 daemon do this,
> but you also can add EntityManager configuration files for this or
> write your own daemon to expose the interfaces.
> 
> On Thu, 2022-08-04 at 08:07 +0000, Oğuzhan ÇAĞLAR wrote:
> > Hello,
> > 
> > I'm working on openbmc for ast2500 bmc. I want to add inventory
> > such
> > as CPU and DIMM etc. I added the chassis from .json file but I
> > couldn't add the CPU and DIMM. I know this is to related with
> > entity-
> > manager. How can I add these inventory on WEBUI? Can you give some
> > information about this issue?
> > 
> > Regards.
> > 
> > Oğuzhan Çağlar
> > Software Design Engineer
> > 
> > 
> > 
> > Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> > Teknopark İstanbul, Kurtköy Pendik İSTANBUL
> > 
> > 
> > Tel             : +90 (216) 354 72 86
> > Faks         : +90 (216) 354 76 77
> > Gsm          : +90 (507) 585 10 60
> > oguzhan.caglar@pavotek.com.tr
> > 
> > www.pavotek.com.tr
> > 
> > 
> 
> --
> Best regards,
> Andrei Kartashev,
> Lead BMC Developer
> 

-- 
Best regards,
Andrei Kartashev,
Lead BMC Developer

Ynt: Ynt: (External) Re: Adding Inventory

[Oğuzhan ÇAĞLAR]

[-- Attachment #1.1: Type: text/plain, Size: 5558 bytes --]

I'm sharing with you that my yocto errors are related to smbios-mdr in the .txt file.


I don't understand, How can the CPU information match with entity-manager configuration files? I saw your comment in openbmc list about PCIe. It probes only with xyz.openbmc_project.FruDevice.



Oğuzhan Çağlar

Software Design Engineer





[X]








[X]


Pavo Tasarım Üretim Elektronik Tic. A.Ş.

Teknopark İstanbul, Kurtköy Pendik İSTANBUL




       [X] <http://pavotek.com.tr/>


Tel             : +90 (216) 354 72 86


Faks         : +90 (216) 354 76 77


Gsm          : +90 (507) 585 10 60


oguzhan.caglar@pavotek.com.tr<mailto:oguzhan.caglar@pavotek.com.tr>





www.pavotek.com.tr<http://www.pavotek.com.tr/>




________________________________
Gönderen: Andrei Kartashev <a.kartashev@yadro.com>
Gönderildi: 12 Ağustos 2022 Cuma 22:14:38
Kime: Oğuzhan ÇAĞLAR; openbmc@lists.ozlabs.org
Konu: Re: Ynt: (External) Re: Adding Inventory


Warning: This e-mail came from an external source. If you do not trust the sender or if there is anything suspicious in the content of the e-mail, please inform the IT department.



I have no idea on what do you mean saying "added the CPU and DIMM
configuration files within the .yaml files", but I guess you are trying
to hardcode this information, which I believe not what ou actually
expect to get.
You probably should learn how the OpenBMC works inside. You can use
busctl tool for that.

Regarding compilation error of smbios-mdr daemon, I can say nothing
without knowing the issue. There should not be any special
configuration files for this smbios-mdr recipe but probably you trying
to build CPUInfo part of the recipe without having PECI library. You
likely should disable cpuinfo app.

On Fri, 2022-08-12 at 06:50 +0000, Oğuzhan ÇAĞLAR wrote:
> Hi Andrei,
>
> Thank you for your information. I have already added the CPU and DIMM
> configuration files within the .yaml files. When I added these
> files(related to the path: xyz.openbmc_project.Inventory.Item.Cpu
> and xyz.openbmc_project.Inventory.Item.Dimm), I see the CPU and DIMM
> entries over WebUI. However, In this way, I add the properties such
> as (PartNumber, SerialNumber, etc.) on my own. I have already
> generated a .bin file that has FRU information (chassis, board etc.)
> and I included this in BMC's image file. In addition, I see the
> properties related to Chassis, Board on WebUI.
>
> I have already checked the smbios-mdr daemon in openbmc. However,
> when I include this daemon in my yocto image, the bitbake shows some
> errors that are related to smbios-mdr's .cpp files. I guess I have to
> create some configuration files before doing it. Is it wrong? What
> should I do?
>
> I guess I have to need some code in BIOS. Is there any example to do
> this? I don't know where I should start.
>
> Thank you.
>
> Oğuzhan Çağlar
> Software Design Engineer
>
>
>
> Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> Teknopark İstanbul, Kurtköy Pendik İSTANBUL
>
>
> Tel             : +90 (216) 354 72 86
> Faks         : +90 (216) 354 76 77
> Gsm          : +90 (507) 585 10 60
> oguzhan.caglar@pavotek.com.tr
>
> www.pavotek.com.tr<http://www.pavotek.com.tr>
>
>
> Gönderen: Andrei Kartashev <a.kartashev@yadro.com>
> Gönderildi: 11 Ağustos 2022 Perşembe 22:28:16
> Kime: Oğuzhan ÇAĞLAR; openbmc@lists.ozlabs.org
> Konu: (External) Re: Adding Inventory
>
>
> Warning: This e-mail came from an external source. If you do not
> trust the sender or if there is anything suspicious in the content of
> the e-mail, please inform the IT department.
>
>
>
> Hello Oguzhan,
>
> This is a very common question for newcomers, I believe is was
> already
> answered somewhere in the list.
> BMC out of the box don't have any knowledge on host's equipment (CPU,
> DIMM, Drive, AIC, etc) - it is up to you to deliver this information
> from host to BMC. As for now the most common way to feed BMC the
> information regarding CPU and DIMM is to transfer smbios tables via
> ipmi. You can implement any other mechanism but any way, you need to
> have some code in your BIOS.
>
> As soon as you have the CPU/DIMM information on BMC it can be shown
> in
> bmcweb by implementing corresponding dbus interfaces
> (xyz.openbmc_project.Inventory.Item.Cpu and
> xyz.openbmc_project.Inventory.Item.Dimm). smbiosmdrv2 daemon do this,
> but you also can add EntityManager configuration files for this or
> write your own daemon to expose the interfaces.
>
> On Thu, 2022-08-04 at 08:07 +0000, Oğuzhan ÇAĞLAR wrote:
> > Hello,
> >
> > I'm working on openbmc for ast2500 bmc. I want to add inventory
> > such
> > as CPU and DIMM etc. I added the chassis from .json file but I
> > couldn't add the CPU and DIMM. I know this is to related with
> > entity-
> > manager. How can I add these inventory on WEBUI? Can you give some
> > information about this issue?
> >
> > Regards.
> >
> > Oğuzhan Çağlar
> > Software Design Engineer
> >
> >
> >
> > Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> > Teknopark İstanbul, Kurtköy Pendik İSTANBUL
> >
> >
> > Tel             : +90 (216) 354 72 86
> > Faks         : +90 (216) 354 76 77
> > Gsm          : +90 (507) 585 10 60
> > oguzhan.caglar@pavotek.com.tr
> >
> > www.pavotek.com.tr<http://www.pavotek.com.tr>
> >
> >
>
> --
> Best regards,
> Andrei Kartashev,
> Lead BMC Developer
>

--
Best regards,
Andrei Kartashev,
Lead BMC Developer


[-- Attachment #1.2: Type: text/html, Size: 14087 bytes --]

[-- Attachment #2: error.txt --]
[-- Type: text/plain, Size: 60420 bytes --]

ERROR: smbios-mdr-1.0+gitAUTOINC+e4ea37716d-r1 do_compile: ExecutionError('/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/temp/run.do_compile.18588', 1, None, None)
ERROR: Logfile of failure stored in: /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/temp/log.do_compile.18588
Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: VERBOSE=1 cmake --build /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/build --target all --
| [1/11] /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot-native/usr/bin/arm-openbmc-linux-gnueabi/arm-openbmc-linux-gnueabi-g++ -DBOOST_ALL_NO_LIB -DBOOST_ASIO_DISABLE_THREADS -DBOOST_ERROR_CODE_HEADER_ONLY -DBOOST_NO_RTTI -DBOOST_NO_TYPEID -DBOOST_SYSTEM_NO_DEPRECATED -DDIMM_DBUS -I/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/include -I/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/build -isystem /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/build/boost-src -marm -mcpu=arm1176jz-s -fstack-protector-strong  -O2 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security  --sysroot=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot  -O2 -pipe -g -feliminate-unused-debug-types -fmacro-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1=/usr/src/debug/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1                      -fdebug-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1=/usr/src/debug/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1                      -fdebug-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot=                      -fdebug-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot-native=  -fvisibility-inlines-hidden -std=gnu++20 -MD -MT CMakeFiles/smbiosmdrv2app.dir/src/cpu.cpp.o -MF CMakeFiles/smbiosmdrv2app.dir/src/cpu.cpp.o.d -o CMakeFiles/smbiosmdrv2app.dir/src/cpu.cpp.o -c /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/src/cpu.cpp
| [2/11] /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot-native/usr/bin/arm-openbmc-linux-gnueabi/arm-openbmc-linux-gnueabi-g++ -DBOOST_ALL_NO_LIB -DBOOST_ASIO_DISABLE_THREADS -DBOOST_ERROR_CODE_HEADER_ONLY -DBOOST_NO_RTTI -DBOOST_NO_TYPEID -DBOOST_SYSTEM_NO_DEPRECATED -DDIMM_DBUS -I/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/include -I/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/build -isystem /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/build/boost-src -marm -mcpu=arm1176jz-s -fstack-protector-strong  -O2 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security  --sysroot=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot  -O2 -pipe -g -feliminate-unused-debug-types -fmacro-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1=/usr/src/debug/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1                      -fdebug-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1=/usr/src/debug/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1                      -fdebug-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot=                      -fdebug-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot-native=  -fvisibility-inlines-hidden -std=gnu++20 -MD -MT CMakeFiles/smbiosmdrv2app.dir/src/pcieslot.cpp.o -MF CMakeFiles/smbiosmdrv2app.dir/src/pcieslot.cpp.o.d -o CMakeFiles/smbiosmdrv2app.dir/src/pcieslot.cpp.o -c /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/src/pcieslot.cpp
| [3/11] /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot-native/usr/bin/arm-openbmc-linux-gnueabi/arm-openbmc-linux-gnueabi-g++ -DBOOST_ALL_NO_LIB -DBOOST_ASIO_DISABLE_THREADS -DBOOST_ERROR_CODE_HEADER_ONLY -DBOOST_NO_RTTI -DBOOST_NO_TYPEID -DBOOST_SYSTEM_NO_DEPRECATED -I/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/include -I/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/build -isystem /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/build/boost-src -marm -mcpu=arm1176jz-s -fstack-protector-strong  -O2 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security  --sysroot=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot  -O2 -pipe -g -feliminate-unused-debug-types -fmacro-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1=/usr/src/debug/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1                      -fdebug-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1=/usr/src/debug/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1                      -fdebug-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot=                      -fdebug-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot-native=  -fvisibility-inlines-hidden -std=gnu++20 -MD -MT CMakeFiles/cpuinfoapp.dir/src/cpuinfo_main.cpp.o -MF CMakeFiles/cpuinfoapp.dir/src/cpuinfo_main.cpp.o.d -o CMakeFiles/cpuinfoapp.dir/src/cpuinfo_main.cpp.o -c /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/src/cpuinfo_main.cpp
| FAILED: CMakeFiles/cpuinfoapp.dir/src/cpuinfo_main.cpp.o
| /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot-native/usr/bin/arm-openbmc-linux-gnueabi/arm-openbmc-linux-gnueabi-g++ -DBOOST_ALL_NO_LIB -DBOOST_ASIO_DISABLE_THREADS -DBOOST_ERROR_CODE_HEADER_ONLY -DBOOST_NO_RTTI -DBOOST_NO_TYPEID -DBOOST_SYSTEM_NO_DEPRECATED -I/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/include -I/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/build -isystem /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/build/boost-src -marm -mcpu=arm1176jz-s -fstack-protector-strong  -O2 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security  --sysroot=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot  -O2 -pipe -g -feliminate-unused-debug-types -fmacro-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1=/usr/src/debug/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1                      -fdebug-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1=/usr/src/debug/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1                      -fdebug-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot=                      -fdebug-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot-native=  -fvisibility-inlines-hidden -std=gnu++20 -MD -MT CMakeFiles/cpuinfoapp.dir/src/cpuinfo_main.cpp.o -MF CMakeFiles/cpuinfoapp.dir/src/cpuinfo_main.cpp.o.d -o CMakeFiles/cpuinfoapp.dir/src/cpuinfo_main.cpp.o -c /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/src/cpuinfo_main.cpp
| /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/src/cpuinfo_main.cpp: In function 'void cpu_info::getProcessorInfo(boost::asio::io_service&, const std::shared_ptr<sdbusplus::asio::connection>&, const size_t&)':
| /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/src/cpuinfo_main.cpp:407:14: error: 'icxd' was not declared in this scope; did you mean 'icx'?
|   407 |         case icxd:
|       |              ^~~~
|       |              icx
| /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/src/cpuinfo_main.cpp:408:14: error: 'spr' was not declared in this scope
|   408 |         case spr:
|       |              ^~~
| [4/11] /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot-native/usr/bin/arm-openbmc-linux-gnueabi/arm-openbmc-linux-gnueabi-g++ -DBOOST_ALL_NO_LIB -DBOOST_ASIO_DISABLE_THREADS -DBOOST_ERROR_CODE_HEADER_ONLY -DBOOST_NO_RTTI -DBOOST_NO_TYPEID -DBOOST_SYSTEM_NO_DEPRECATED -I/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/include -I/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/build -isystem /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/build/boost-src -marm -mcpu=arm1176jz-s -fstack-protector-strong  -O2 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security  --sysroot=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot  -O2 -pipe -g -feliminate-unused-debug-types -fmacro-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1=/usr/src/debug/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1                      -fdebug-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1=/usr/src/debug/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1                      -fdebug-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot=                      -fdebug-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot-native=  -fvisibility-inlines-hidden -std=gnu++20 -MD -MT CMakeFiles/cpuinfoapp.dir/src/speed_select.cpp.o -MF CMakeFiles/cpuinfoapp.dir/src/speed_select.cpp.o.d -o CMakeFiles/cpuinfoapp.dir/src/speed_select.cpp.o -c /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/src/speed_select.cpp
| In file included from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/c++/11.2.0/vector:72,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/c++/11.2.0/functional:62,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/boost/asio/detail/functional.hpp:20,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/boost/asio/associated_allocator.hpp:21,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/boost/asio/detail/handler_alloc_helpers.hpp:23,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/boost/asio/detail/bind_handler.hpp:20,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/boost/asio/detail/wrapped_handler.hpp:18,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/boost/asio/io_context.hpp:24,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/include/speed_select.hpp:16,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/src/speed_select.cpp:15:
| /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/c++/11.2.0/bits/vector.tcc: In member function 'void std::vector<_Tp, _Alloc>::_M_realloc_insert(std::vector<_Tp, _Alloc>::iterator, _Args&& ...) [with _Args = {const boost::asio::detail::timer_queue<boost::asio::detail::chrono_time_traits<std::chrono::_V2::steady_clock, boost::asio::wait_traits<std::chrono::_V2::steady_clock> > >::heap_entry&}; _Tp = boost::asio::detail::timer_queue<boost::asio::detail::chrono_time_traits<std::chrono::_V2::steady_clock, boost::asio::wait_traits<std::chrono::_V2::steady_clock> > >::heap_entry; _Alloc = std::allocator<boost::asio::detail::timer_queue<boost::asio::detail::chrono_time_traits<std::chrono::_V2::steady_clock, boost::asio::wait_traits<std::chrono::_V2::steady_clock> > >::heap_entry>]':
| /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/c++/11.2.0/bits/vector.tcc:426:7: note: parameter passing for argument of type 'std::vector<boost::asio::detail::timer_queue<boost::asio::detail::chrono_time_traits<std::chrono::_V2::steady_clock, boost::asio::wait_traits<std::chrono::_V2::steady_clock> > >::heap_entry, std::allocator<boost::asio::detail::timer_queue<boost::asio::detail::chrono_time_traits<std::chrono::_V2::steady_clock, boost::asio::wait_traits<std::chrono::_V2::steady_clock> > >::heap_entry> >::iterator' changed in GCC 7.1
|   426 |       vector<_Tp, _Alloc>::
|       |       ^~~~~~~~~~~~~~~~~~~
| In file included from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/c++/11.2.0/vector:67,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/c++/11.2.0/functional:62,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/boost/asio/detail/functional.hpp:20,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/boost/asio/associated_allocator.hpp:21,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/boost/asio/detail/handler_alloc_helpers.hpp:23,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/boost/asio/detail/bind_handler.hpp:20,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/boost/asio/detail/wrapped_handler.hpp:18,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/boost/asio/io_context.hpp:24,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/include/speed_select.hpp:16,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/src/speed_select.cpp:15:
| /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/c++/11.2.0/bits/stl_vector.h: In member function 'void boost::asio::detail::epoll_reactor::schedule_timer(boost::asio::detail::timer_queue<Time_Traits>&, const typename Time_Traits::time_type&, typename boost::asio::detail::timer_queue<Time_Traits>::per_timer_data&, boost::asio::detail::wait_op*) [with Time_Traits = boost::asio::detail::chrono_time_traits<std::chrono::_V2::steady_clock, boost::asio::wait_traits<std::chrono::_V2::steady_clock> >]':
| /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/c++/11.2.0/bits/stl_vector.h:1198:28: note: parameter passing for argument of type '__gnu_cxx::__normal_iterator<boost::asio::detail::timer_queue<boost::asio::detail::chrono_time_traits<std::chrono::_V2::steady_clock, boost::asio::wait_traits<std::chrono::_V2::steady_clock> > >::heap_entry*, std::vector<boost::asio::detail::timer_queue<boost::asio::detail::chrono_time_traits<std::chrono::_V2::steady_clock, boost::asio::wait_traits<std::chrono::_V2::steady_clock> > >::heap_entry, std::allocator<boost::asio::detail::timer_queue<boost::asio::detail::chrono_time_traits<std::chrono::_V2::steady_clock, boost::asio::wait_traits<std::chrono::_V2::steady_clock> > >::heap_entry> > >' changed in GCC 7.1
|  1198 |           _M_realloc_insert(end(), __x);
|       |           ~~~~~~~~~~~~~~~~~^~~~~~~~~~~~
| [5/11] /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot-native/usr/bin/arm-openbmc-linux-gnueabi/arm-openbmc-linux-gnueabi-g++ -DBOOST_ALL_NO_LIB -DBOOST_ASIO_DISABLE_THREADS -DBOOST_ERROR_CODE_HEADER_ONLY -DBOOST_NO_RTTI -DBOOST_NO_TYPEID -DBOOST_SYSTEM_NO_DEPRECATED -DDIMM_DBUS -I/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/include -I/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/build -isystem /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/build/boost-src -marm -mcpu=arm1176jz-s -fstack-protector-strong  -O2 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security  --sysroot=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot  -O2 -pipe -g -feliminate-unused-debug-types -fmacro-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1=/usr/src/debug/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1                      -fdebug-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1=/usr/src/debug/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1                      -fdebug-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot=                      -fdebug-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot-native=  -fvisibility-inlines-hidden -std=gnu++20 -MD -MT CMakeFiles/smbiosmdrv2app.dir/src/system.cpp.o -MF CMakeFiles/smbiosmdrv2app.dir/src/system.cpp.o.d -o CMakeFiles/smbiosmdrv2app.dir/src/system.cpp.o -c /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/src/system.cpp
| [6/11] /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot-native/usr/bin/arm-openbmc-linux-gnueabi/arm-openbmc-linux-gnueabi-g++ -DBOOST_ALL_NO_LIB -DBOOST_ASIO_DISABLE_THREADS -DBOOST_ERROR_CODE_HEADER_ONLY -DBOOST_NO_RTTI -DBOOST_NO_TYPEID -DBOOST_SYSTEM_NO_DEPRECATED -DDIMM_DBUS -I/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/include -I/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/build -isystem /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/build/boost-src -marm -mcpu=arm1176jz-s -fstack-protector-strong  -O2 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security  --sysroot=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot  -O2 -pipe -g -feliminate-unused-debug-types -fmacro-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1=/usr/src/debug/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1                      -fdebug-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1=/usr/src/debug/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1                      -fdebug-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot=                      -fdebug-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot-native=  -fvisibility-inlines-hidden -std=gnu++20 -MD -MT CMakeFiles/smbiosmdrv2app.dir/src/dimm.cpp.o -MF CMakeFiles/smbiosmdrv2app.dir/src/dimm.cpp.o.d -o CMakeFiles/smbiosmdrv2app.dir/src/dimm.cpp.o -c /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/src/dimm.cpp
| [7/11] /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot-native/usr/bin/arm-openbmc-linux-gnueabi/arm-openbmc-linux-gnueabi-g++ -DBOOST_ALL_NO_LIB -DBOOST_ASIO_DISABLE_THREADS -DBOOST_ERROR_CODE_HEADER_ONLY -DBOOST_NO_RTTI -DBOOST_NO_TYPEID -DBOOST_SYSTEM_NO_DEPRECATED -DDIMM_DBUS -I/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/include -I/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/build -isystem /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/build/boost-src -marm -mcpu=arm1176jz-s -fstack-protector-strong  -O2 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security  --sysroot=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot  -O2 -pipe -g -feliminate-unused-debug-types -fmacro-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1=/usr/src/debug/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1                      -fdebug-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1=/usr/src/debug/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1                      -fdebug-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot=                      -fdebug-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot-native=  -fvisibility-inlines-hidden -std=gnu++20 -MD -MT CMakeFiles/smbiosmdrv2app.dir/src/mdrv2_main.cpp.o -MF CMakeFiles/smbiosmdrv2app.dir/src/mdrv2_main.cpp.o.d -o CMakeFiles/smbiosmdrv2app.dir/src/mdrv2_main.cpp.o -c /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/src/mdrv2_main.cpp
| In file included from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/c++/11.2.0/vector:72,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/sdbusplus/message/types.hpp:14,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/sdbusplus/message/append.hpp:5,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/sdbusplus/message.hpp:6,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/sdbusplus/bus.hpp:7,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/sdbusplus/server.hpp:3,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/xyz/openbmc_project/Logging/Entry/server.hpp:6,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/phosphor-logging/elog.hpp:2,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/phosphor-logging/elog-errors.hpp:5,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/include/smbios_mdrv2.hpp:19,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/include/cpu.hpp:18,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/include/mdrv2.hpp:18,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/src/mdrv2_main.cpp:17:
| /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/c++/11.2.0/bits/vector.tcc: In member function 'void std::vector<_Tp, _Alloc>::_M_realloc_insert(std::vector<_Tp, _Alloc>::iterator, _Args&& ...) [with _Args = {sd_bus_vtable}; _Tp = sd_bus_vtable; _Alloc = std::allocator<sd_bus_vtable>]':
| /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/c++/11.2.0/bits/vector.tcc:426:7: note: parameter passing for argument of type 'std::vector<sd_bus_vtable>::iterator' changed in GCC 7.1
|   426 |       vector<_Tp, _Alloc>::
|       |       ^~~~~~~~~~~~~~~~~~~
| /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/c++/11.2.0/bits/vector.tcc: In function 'std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>::emplace_back(_Args&& ...) [with _Args = {sd_bus_vtable}; _Tp = sd_bus_vtable; _Alloc = std::allocator<sd_bus_vtable>]':
| /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/c++/11.2.0/bits/vector.tcc:121:28: note: parameter passing for argument of type '__gnu_cxx::__normal_iterator<sd_bus_vtable*, std::vector<sd_bus_vtable> >' changed in GCC 7.1
|   121 |           _M_realloc_insert(end(), std::forward<_Args>(__args)...);
|       |           ~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| [8/11] /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot-native/usr/bin/arm-openbmc-linux-gnueabi/arm-openbmc-linux-gnueabi-g++ -DBOOST_ALL_NO_LIB -DBOOST_ASIO_DISABLE_THREADS -DBOOST_ERROR_CODE_HEADER_ONLY -DBOOST_NO_RTTI -DBOOST_NO_TYPEID -DBOOST_SYSTEM_NO_DEPRECATED -DDIMM_DBUS -I/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/include -I/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/build -isystem /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/build/boost-src -marm -mcpu=arm1176jz-s -fstack-protector-strong  -O2 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security  --sysroot=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot  -O2 -pipe -g -feliminate-unused-debug-types -fmacro-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1=/usr/src/debug/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1                      -fdebug-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1=/usr/src/debug/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1                      -fdebug-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot=                      -fdebug-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot-native=  -fvisibility-inlines-hidden -std=gnu++20 -MD -MT CMakeFiles/smbiosmdrv2app.dir/src/mdrv2.cpp.o -MF CMakeFiles/smbiosmdrv2app.dir/src/mdrv2.cpp.o.d -o CMakeFiles/smbiosmdrv2app.dir/src/mdrv2.cpp.o -c /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/src/mdrv2.cpp
| In file included from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/c++/11.2.0/vector:72,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/sdbusplus/message/types.hpp:14,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/sdbusplus/message/append.hpp:5,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/sdbusplus/message.hpp:6,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/sdbusplus/bus.hpp:7,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/sdbusplus/server.hpp:3,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/xyz/openbmc_project/Logging/Entry/server.hpp:6,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/phosphor-logging/elog.hpp:2,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/phosphor-logging/elog-errors.hpp:5,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/include/smbios_mdrv2.hpp:19,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/include/cpu.hpp:18,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/include/mdrv2.hpp:18,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/src/mdrv2.cpp:17:
| /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/c++/11.2.0/bits/vector.tcc: In member function 'void std::vector<_Tp, _Alloc>::_M_realloc_insert(std::vector<_Tp, _Alloc>::iterator, _Args&& ...) [with _Args = {const boost::asio::detail::timer_queue<boost::asio::detail::chrono_time_traits<std::chrono::_V2::steady_clock, boost::asio::wait_traits<std::chrono::_V2::steady_clock> > >::heap_entry&}; _Tp = boost::asio::detail::timer_queue<boost::asio::detail::chrono_time_traits<std::chrono::_V2::steady_clock, boost::asio::wait_traits<std::chrono::_V2::steady_clock> > >::heap_entry; _Alloc = std::allocator<boost::asio::detail::timer_queue<boost::asio::detail::chrono_time_traits<std::chrono::_V2::steady_clock, boost::asio::wait_traits<std::chrono::_V2::steady_clock> > >::heap_entry>]':
| /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/c++/11.2.0/bits/vector.tcc:426:7: note: parameter passing for argument of type 'std::vector<boost::asio::detail::timer_queue<boost::asio::detail::chrono_time_traits<std::chrono::_V2::steady_clock, boost::asio::wait_traits<std::chrono::_V2::steady_clock> > >::heap_entry, std::allocator<boost::asio::detail::timer_queue<boost::asio::detail::chrono_time_traits<std::chrono::_V2::steady_clock, boost::asio::wait_traits<std::chrono::_V2::steady_clock> > >::heap_entry> >::iterator' changed in GCC 7.1
|   426 |       vector<_Tp, _Alloc>::
|       |       ^~~~~~~~~~~~~~~~~~~
| In file included from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/c++/11.2.0/vector:67,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/sdbusplus/message/types.hpp:14,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/sdbusplus/message/append.hpp:5,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/sdbusplus/message.hpp:6,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/sdbusplus/bus.hpp:7,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/sdbusplus/server.hpp:3,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/xyz/openbmc_project/Logging/Entry/server.hpp:6,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/phosphor-logging/elog.hpp:2,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/phosphor-logging/elog-errors.hpp:5,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/include/smbios_mdrv2.hpp:19,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/include/cpu.hpp:18,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/include/mdrv2.hpp:18,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/src/mdrv2.cpp:17:
| /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/c++/11.2.0/bits/stl_vector.h: In member function 'void boost::asio::detail::epoll_reactor::schedule_timer(boost::asio::detail::timer_queue<Time_Traits>&, const typename Time_Traits::time_type&, typename boost::asio::detail::timer_queue<Time_Traits>::per_timer_data&, boost::asio::detail::wait_op*) [with Time_Traits = boost::asio::detail::chrono_time_traits<std::chrono::_V2::steady_clock, boost::asio::wait_traits<std::chrono::_V2::steady_clock> >]':
| /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/c++/11.2.0/bits/stl_vector.h:1198:28: note: parameter passing for argument of type '__gnu_cxx::__normal_iterator<boost::asio::detail::timer_queue<boost::asio::detail::chrono_time_traits<std::chrono::_V2::steady_clock, boost::asio::wait_traits<std::chrono::_V2::steady_clock> > >::heap_entry*, std::vector<boost::asio::detail::timer_queue<boost::asio::detail::chrono_time_traits<std::chrono::_V2::steady_clock, boost::asio::wait_traits<std::chrono::_V2::steady_clock> > >::heap_entry, std::allocator<boost::asio::detail::timer_queue<boost::asio::detail::chrono_time_traits<std::chrono::_V2::steady_clock, boost::asio::wait_traits<std::chrono::_V2::steady_clock> > >::heap_entry> > >' changed in GCC 7.1
|  1198 |           _M_realloc_insert(end(), __x);
|       |           ~~~~~~~~~~~~~~~~~^~~~~~~~~~~~
| [9/11] /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot-native/usr/bin/arm-openbmc-linux-gnueabi/arm-openbmc-linux-gnueabi-g++ -DBOOST_ALL_NO_LIB -DBOOST_ASIO_DISABLE_THREADS -DBOOST_ERROR_CODE_HEADER_ONLY -DBOOST_NO_RTTI -DBOOST_NO_TYPEID -DBOOST_SYSTEM_NO_DEPRECATED -I/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/include -I/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/build -isystem /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/build/boost-src -marm -mcpu=arm1176jz-s -fstack-protector-strong  -O2 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security  --sysroot=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot  -O2 -pipe -g -feliminate-unused-debug-types -fmacro-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1=/usr/src/debug/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1                      -fdebug-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1=/usr/src/debug/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1                      -fdebug-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot=                      -fdebug-prefix-map=/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot-native=  -fvisibility-inlines-hidden -std=gnu++20 -MD -MT CMakeFiles/cpuinfoapp.dir/src/cpuinfo_utils.cpp.o -MF CMakeFiles/cpuinfoapp.dir/src/cpuinfo_utils.cpp.o.d -o CMakeFiles/cpuinfoapp.dir/src/cpuinfo_utils.cpp.o -c /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/src/cpuinfo_utils.cpp
| In file included from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/c++/11.2.0/vector:72,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/c++/11.2.0/functional:62,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/boost/asio/detail/functional.hpp:20,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/boost/asio/associated_allocator.hpp:21,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/boost/asio/detail/handler_alloc_helpers.hpp:23,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/boost/asio/detail/bind_handler.hpp:20,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/boost/asio/detail/wrapped_handler.hpp:18,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/boost/asio/io_context.hpp:24,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/include/cpuinfo_utils.hpp:17,
|                  from /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/git/src/cpuinfo_utils.cpp:15:
| /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/c++/11.2.0/bits/vector.tcc: In member function 'void std::vector<_Tp, _Alloc>::_M_realloc_insert(std::vector<_Tp, _Alloc>::iterator, _Args&& ...) [with _Args = {std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::variant<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, bool, unsigned char, short unsigned int, short int, unsigned int, int, long long unsigned int, long long int, double, sdbusplus::message::details::string_path_wrapper> >}; _Tp = std::pair<std::__cxx11::basic_string<char>, std::variant<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, bool, unsigned char, short unsigned int, short int, unsigned int, int, long long unsigned int, long long int, double, sdbusplus::message::details::string_path_wrapper> >; _Alloc = std::allocator<std::pair<std::__cxx11::basic_string<char>, std::variant<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, bool, unsigned char, short unsigned int, short int, unsigned int, int, long long unsigned int, long long int, double, sdbusplus::message::details::string_path_wrapper> > >]':
| /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/c++/11.2.0/bits/vector.tcc:426:7: note: parameter passing for argument of type 'std::vector<std::pair<std::__cxx11::basic_string<char>, std::variant<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, bool, unsigned char, short unsigned int, short int, unsigned int, int, long long unsigned int, long long int, double, sdbusplus::message::details::string_path_wrapper> >, std::allocator<std::pair<std::__cxx11::basic_string<char>, std::variant<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, bool, unsigned char, short unsigned int, short int, unsigned int, int, long long unsigned int, long long int, double, sdbusplus::message::details::string_path_wrapper> > > >::iterator' changed in GCC 7.1
|   426 |       vector<_Tp, _Alloc>::
|       |       ^~~~~~~~~~~~~~~~~~~
| /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/c++/11.2.0/bits/vector.tcc: In member function 'void std::vector<_Tp, _Alloc>::_M_realloc_insert(std::vector<_Tp, _Alloc>::iterator, _Args&& ...) [with _Args = {std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::variant<bool, unsigned char, short unsigned int, short int, unsigned int, int, long long unsigned int, long long int, double, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, sdbusplus::message::details::string_path_wrapper> >}; _Tp = std::pair<std::__cxx11::basic_string<char>, std::variant<bool, unsigned char, short unsigned int, short int, unsigned int, int, long long unsigned int, long long int, double, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, sdbusplus::message::details::string_path_wrapper> >; _Alloc = std::allocator<std::pair<std::__cxx11::basic_string<char>, std::variant<bool, unsigned char, short unsigned int, short int, unsigned int, int, long long unsigned int, long long int, double, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, sdbusplus::message::details::string_path_wrapper> > >]':
| /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/c++/11.2.0/bits/vector.tcc:426:7: note: parameter passing for argument of type 'std::vector<std::pair<std::__cxx11::basic_string<char>, std::variant<bool, unsigned char, short unsigned int, short int, unsigned int, int, long long unsigned int, long long int, double, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, sdbusplus::message::details::string_path_wrapper> >, std::allocator<std::pair<std::__cxx11::basic_string<char>, std::variant<bool, unsigned char, short unsigned int, short int, unsigned int, int, long long unsigned int, long long int, double, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, sdbusplus::message::details::string_path_wrapper> > > >::iterator' changed in GCC 7.1
| /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/c++/11.2.0/bits/vector.tcc: In static member function 'static void sdbusplus::message::details::read_single<T, typename std::enable_if<has_emplace_back_method_v<T>, void>::type>::op(sdbusplus::SdBusInterface*, sd_bus_message*, S&&) [with S = std::vector<std::pair<std::__cxx11::basic_string<char>, std::variant<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, bool, unsigned char, short unsigned int, short int, unsigned int, int, long long unsigned int, long long int, double, sdbusplus::message::details::string_path_wrapper> >, std::allocator<std::pair<std::__cxx11::basic_string<char>, std::variant<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, bool, unsigned char, short unsigned int, short int, unsigned int, int, long long unsigned int, long long int, double, sdbusplus::message::details::string_path_wrapper> > > >&; T = std::vector<std::pair<std::__cxx11::basic_string<char>, std::variant<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, bool, unsigned char, short unsigned int, short int, unsigned int, int, long long unsigned int, long long int, double, sdbusplus::message::details::string_path_wrapper> >, std::allocator<std::pair<std::__cxx11::basic_string<char>, std::variant<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, bool, unsigned char, short unsigned int, short int, unsigned int, int, long long unsigned int, long long int, double, sdbusplus::message::details::string_path_wrapper> > > >]':
| /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/c++/11.2.0/bits/vector.tcc:121:28: note: parameter passing for argument of type '__gnu_cxx::__normal_iterator<std::pair<std::__cxx11::basic_string<char>, std::variant<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, bool, unsigned char, short unsigned int, short int, unsigned int, int, long long unsigned int, long long int, double, sdbusplus::message::details::string_path_wrapper> >*, std::vector<std::pair<std::__cxx11::basic_string<char>, std::variant<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, bool, unsigned char, short unsigned int, short int, unsigned int, int, long long unsigned int, long long int, double, sdbusplus::message::details::string_path_wrapper> >, std::allocator<std::pair<std::__cxx11::basic_string<char>, std::variant<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, bool, unsigned char, short unsigned int, short int, unsigned int, int, long long unsigned int, long long int, double, sdbusplus::message::details::string_path_wrapper> > > > >' changed in GCC 7.1
|   121 |           _M_realloc_insert(end(), std::forward<_Args>(__args)...);
|       |           ~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/c++/11.2.0/bits/vector.tcc: In static member function 'static void sdbusplus::message::details::read_single<T, typename std::enable_if<has_emplace_back_method_v<T>, void>::type>::op(sdbusplus::SdBusInterface*, sd_bus_message*, S&&) [with S = std::vector<std::pair<std::__cxx11::basic_string<char>, std::variant<bool, unsigned char, short unsigned int, short int, unsigned int, int, long long unsigned int, long long int, double, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, sdbusplus::message::details::string_path_wrapper> >, std::allocator<std::pair<std::__cxx11::basic_string<char>, std::variant<bool, unsigned char, short unsigned int, short int, unsigned int, int, long long unsigned int, long long int, double, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, sdbusplus::message::details::string_path_wrapper> > > >&; T = std::vector<std::pair<std::__cxx11::basic_string<char>, std::variant<bool, unsigned char, short unsigned int, short int, unsigned int, int, long long unsigned int, long long int, double, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, sdbusplus::message::details::string_path_wrapper> >, std::allocator<std::pair<std::__cxx11::basic_string<char>, std::variant<bool, unsigned char, short unsigned int, short int, unsigned int, int, long long unsigned int, long long int, double, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, sdbusplus::message::details::string_path_wrapper> > > >]':
| /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-r1/recipe-sysroot/usr/include/c++/11.2.0/bits/vector.tcc:121:28: note: parameter passing for argument of type '__gnu_cxx::__normal_iterator<std::pair<std::__cxx11::basic_string<char>, std::variant<bool, unsigned char, short unsigned int, short int, unsigned int, int, long long unsigned int, long long int, double, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, sdbusplus::message::details::string_path_wrapper> >*, std::vector<std::pair<std::__cxx11::basic_string<char>, std::variant<bool, unsigned char, short unsigned int, short int, unsigned int, int, long long unsigned int, long long int, double, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, sdbusplus::message::details::string_path_wrapper> >, std::allocator<std::pair<std::__cxx11::basic_string<char>, std::variant<bool, unsigned char, short unsigned int, short int, unsigned int, int, long long unsigned int, long long int, double, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, sdbusplus::message::details::string_path_wrapper> > > > >' changed in GCC 7.1
|   121 |           _M_realloc_insert(end(), std::forward<_Args>(__args)...);
|       |           ~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| ninja: build stopped: subcommand failed.
| WARNING: exit code 1 from a shell command.
ERROR: Task (/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/meta-phosphor/recipes-phosphor/smbios/smbios-mdr_git.bb:do_compile) failed with exit code '1'

Re: Ynt: Ynt: (External) Re: Adding Inventory

[Andrei Kartashev]

As I assumed, it is PCUInfo issue:

|
/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/a
rm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-
r1/git/src/cpuinfo_main.cpp:407:14: error: 'icxd' was not declared in
this scope; did you mean 'icx'?
|   407 |         case icxd:
|       |              ^~~~
|       |              icx
|
/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/a
rm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-
r1/git/src/cpuinfo_main.cpp:408:14: error: 'spr' was not declared in
this scope
|   408 |         case spr:
|       |              ^~~


Turn it off in you bbappend with `PACKAGECONFIG:remove = " cpuinfo"`

 

On Mon, 2022-08-15 at 07:25 +0000, Oğuzhan ÇAĞLAR wrote:
> 
> I'm sharing with you that my yocto errors are related to smbios-
> mdr in the .txt file. 
> 
> I don't understand, How can the CPU information match with entity-
> manager configuration files? I saw your comment in openbmc list about
> PCIe. It probes only with xyz.openbmc_project.FruDevice. 
> 
> 
> Oğuzhan Çağlar
> Software Design Engineer
>  
>  
>  
> Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> Teknopark İstanbul, Kurtköy Pendik İSTANBUL
>  
>       
> Tel             : +90 (216) 354 72 86
> Faks         : +90 (216) 354 76 77
> Gsm          : +90 (507) 585 10 60
> oguzhan.caglar@pavotek.com.tr
>  
> www.pavotek.com.tr
> 
>  
> Gönderen: Andrei Kartashev <a.kartashev@yadro.com>
> Gönderildi: 12 Ağustos 2022 Cuma 22:14:38
> Kime: Oğuzhan ÇAĞLAR; openbmc@lists.ozlabs.org
> Konu: Re: Ynt: (External) Re: Adding Inventory
>  
> 
> Warning: This e-mail came from an external source. If you do not
> trust the sender or if there is anything suspicious in the content of
> the e-mail, please inform the IT department.
> 
> 
> 
> I have no idea on what do you mean saying "added the CPU and DIMM
> configuration files within the .yaml files", but I guess you are
> trying
> to hardcode this information, which I believe not what ou actually
> expect to get.
> You probably should learn how the OpenBMC works inside. You can use
> busctl tool for that.
> 
> Regarding compilation error of smbios-mdr daemon, I can say nothing
> without knowing the issue. There should not be any special
> configuration files for this smbios-mdr recipe but probably you
> trying
> to build CPUInfo part of the recipe without having PECI library. You
> likely should disable cpuinfo app.
> 
> On Fri, 2022-08-12 at 06:50 +0000, Oğuzhan ÇAĞLAR wrote:
> > Hi Andrei,
> > 
> > Thank you for your information. I have already added the CPU and
> > DIMM
> > configuration files within the .yaml files. When I added these
> > files(related to the path: xyz.openbmc_project.Inventory.Item.Cpu
> > and xyz.openbmc_project.Inventory.Item.Dimm), I see the CPU and
> > DIMM
> > entries over WebUI. However, In this way, I add the properties such
> > as (PartNumber, SerialNumber, etc.) on my own. I have already
> > generated a .bin file that has FRU information (chassis, board
> > etc.)
> > and I included this in BMC's image file. In addition, I see the
> > properties related to Chassis, Board on WebUI.
> > 
> > I have already checked the smbios-mdr daemon in openbmc. However,
> > when I include this daemon in my yocto image, the bitbake shows
> > some
> > errors that are related to smbios-mdr's .cpp files. I guess I have
> > to
> > create some configuration files before doing it. Is it wrong? What
> > should I do?
> > 
> > I guess I have to need some code in BIOS. Is there any example to
> > do
> > this? I don't know where I should start.
> > 
> > Thank you.
> > 
> > Oğuzhan Çağlar
> > Software Design Engineer
> > 
> > 
> > 
> > Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> > Teknopark İstanbul, Kurtköy Pendik İSTANBUL
> > 
> > 
> > Tel             : +90 (216) 354 72 86
> > Faks         : +90 (216) 354 76 77
> > Gsm          : +90 (507) 585 10 60
> > oguzhan.caglar@pavotek.com.tr
> > 
> > www.pavotek.com.tr
> > 
> > 
> > Gönderen: Andrei Kartashev <a.kartashev@yadro.com>
> > Gönderildi: 11 Ağustos 2022 Perşembe 22:28:16
> > Kime: Oğuzhan ÇAĞLAR; openbmc@lists.ozlabs.org
> > Konu: (External) Re: Adding Inventory
> > 
> > 
> > Warning: This e-mail came from an external source. If you do not
> > trust the sender or if there is anything suspicious in the content
> > of
> > the e-mail, please inform the IT department.
> > 
> > 
> > 
> > Hello Oguzhan,
> > 
> > This is a very common question for newcomers, I believe is was
> > already
> > answered somewhere in the list.
> > BMC out of the box don't have any knowledge on host's equipment
> > (CPU,
> > DIMM, Drive, AIC, etc) - it is up to you to deliver this
> > information
> > from host to BMC. As for now the most common way to feed BMC the
> > information regarding CPU and DIMM is to transfer smbios tables via
> > ipmi. You can implement any other mechanism but any way, you need
> > to
> > have some code in your BIOS.
> > 
> > As soon as you have the CPU/DIMM information on BMC it can be shown
> > in
> > bmcweb by implementing corresponding dbus interfaces
> > (xyz.openbmc_project.Inventory.Item.Cpu and
> > xyz.openbmc_project.Inventory.Item.Dimm). smbiosmdrv2 daemon do
> > this,
> > but you also can add EntityManager configuration files for this or
> > write your own daemon to expose the interfaces.
> > 
> > On Thu, 2022-08-04 at 08:07 +0000, Oğuzhan ÇAĞLAR wrote:
> > > Hello,
> > > 
> > > I'm working on openbmc for ast2500 bmc. I want to add inventory
> > > such
> > > as CPU and DIMM etc. I added the chassis from .json file but I
> > > couldn't add the CPU and DIMM. I know this is to related with
> > > entity-
> > > manager. How can I add these inventory on WEBUI? Can you give
> > > some
> > > information about this issue?
> > > 
> > > Regards.
> > > 
> > > Oğuzhan Çağlar
> > > Software Design Engineer
> > > 
> > > 
> > > 
> > > Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> > > Teknopark İstanbul, Kurtköy Pendik İSTANBUL
> > > 
> > > 
> > > Tel             : +90 (216) 354 72 86
> > > Faks         : +90 (216) 354 76 77
> > > Gsm          : +90 (507) 585 10 60
> > > oguzhan.caglar@pavotek.com.tr
> > > 
> > > www.pavotek.com.tr
> > > 
> > > 
> > 
> > --
> > Best regards,
> > Andrei Kartashev,
> > Lead BMC Developer
> > 
> 
> --
> Best regards,
> Andrei Kartashev,
> Lead BMC Developer
> 

-- 
Best regards,
Andrei Kartashev,
Lead BMC Developer

Ynt: Ynt: Ynt: (External) Re: Adding Inventory

[Oğuzhan ÇAĞLAR]

[-- Attachment #1: Type: text/plain, Size: 7779 bytes --]

Thank you, Andrei,


I successfully built it now. Why do I get this error? In addition, I guess I have to dive into BIOS to get information about CPU and DIMM. Is it right? Is there any example to do that?

What exactly do the smbios-mdr daemon?


Oğuzhan Çağlar

Yazılım Mühendisi





[X]








[X]


Pavo Tasarım Üretim Elektronik Tic. A.Ş.

Teknopark İstanbul, Kurtköy Pendik İSTANBUL




       [X] <http://pavotek.com.tr/>


Tel             : +90 (216) 354 72 86


Faks         : +90 (216) 354 76 77


Gsm          : +90 (507) 585 10 60


oguzhan.caglar@pavotek.com.tr<mailto:oguzhan.caglar@pavotek.com.tr>





www.pavotek.com.tr<http://www.pavotek.com.tr/>




________________________________
Gönderen: Andrei Kartashev <a.kartashev@yadro.com>
Gönderildi: 15 Ağustos 2022 Pazartesi 13:23:33
Kime: Oğuzhan ÇAĞLAR; openbmc@lists.ozlabs.org
Konu: Re: Ynt: Ynt: (External) Re: Adding Inventory


Warning: This e-mail came from an external source. If you do not trust the sender or if there is anything suspicious in the content of the e-mail, please inform the IT department.



As I assumed, it is PCUInfo issue:

|
/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/a
rm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-
r1/git/src/cpuinfo_main.cpp:407:14: error: 'icxd' was not declared in
this scope; did you mean 'icx'?
|   407 |         case icxd:
|       |              ^~~~
|       |              icx
|
/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/a
rm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-
r1/git/src/cpuinfo_main.cpp:408:14: error: 'spr' was not declared in
this scope
|   408 |         case spr:
|       |              ^~~


Turn it off in you bbappend with `PACKAGECONFIG:remove = " cpuinfo"`



On Mon, 2022-08-15 at 07:25 +0000, Oğuzhan ÇAĞLAR wrote:
>
> I'm sharing with you that my yocto errors are related to smbios-
> mdr in the .txt file.
>
> I don't understand, How can the CPU information match with entity-
> manager configuration files? I saw your comment in openbmc list about
> PCIe. It probes only with xyz.openbmc_project.FruDevice.
>
>
> Oğuzhan Çağlar
> Software Design Engineer
>
>
>
> Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> Teknopark İstanbul, Kurtköy Pendik İSTANBUL
>
>
> Tel             : +90 (216) 354 72 86
> Faks         : +90 (216) 354 76 77
> Gsm          : +90 (507) 585 10 60
> oguzhan.caglar@pavotek.com.tr
>
> www.pavotek.com.tr<http://www.pavotek.com.tr>
>
>
> Gönderen: Andrei Kartashev <a.kartashev@yadro.com>
> Gönderildi: 12 Ağustos 2022 Cuma 22:14:38
> Kime: Oğuzhan ÇAĞLAR; openbmc@lists.ozlabs.org
> Konu: Re: Ynt: (External) Re: Adding Inventory
>
>
> Warning: This e-mail came from an external source. If you do not
> trust the sender or if there is anything suspicious in the content of
> the e-mail, please inform the IT department.
>
>
>
> I have no idea on what do you mean saying "added the CPU and DIMM
> configuration files within the .yaml files", but I guess you are
> trying
> to hardcode this information, which I believe not what ou actually
> expect to get.
> You probably should learn how the OpenBMC works inside. You can use
> busctl tool for that.
>
> Regarding compilation error of smbios-mdr daemon, I can say nothing
> without knowing the issue. There should not be any special
> configuration files for this smbios-mdr recipe but probably you
> trying
> to build CPUInfo part of the recipe without having PECI library. You
> likely should disable cpuinfo app.
>
> On Fri, 2022-08-12 at 06:50 +0000, Oğuzhan ÇAĞLAR wrote:
> > Hi Andrei,
> >
> > Thank you for your information. I have already added the CPU and
> > DIMM
> > configuration files within the .yaml files. When I added these
> > files(related to the path: xyz.openbmc_project.Inventory.Item.Cpu
> > and xyz.openbmc_project.Inventory.Item.Dimm), I see the CPU and
> > DIMM
> > entries over WebUI. However, In this way, I add the properties such
> > as (PartNumber, SerialNumber, etc.) on my own. I have already
> > generated a .bin file that has FRU information (chassis, board
> > etc.)
> > and I included this in BMC's image file. In addition, I see the
> > properties related to Chassis, Board on WebUI.
> >
> > I have already checked the smbios-mdr daemon in openbmc. However,
> > when I include this daemon in my yocto image, the bitbake shows
> > some
> > errors that are related to smbios-mdr's .cpp files. I guess I have
> > to
> > create some configuration files before doing it. Is it wrong? What
> > should I do?
> >
> > I guess I have to need some code in BIOS. Is there any example to
> > do
> > this? I don't know where I should start.
> >
> > Thank you.
> >
> > Oğuzhan Çağlar
> > Software Design Engineer
> >
> >
> >
> > Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> > Teknopark İstanbul, Kurtköy Pendik İSTANBUL
> >
> >
> > Tel             : +90 (216) 354 72 86
> > Faks         : +90 (216) 354 76 77
> > Gsm          : +90 (507) 585 10 60
> > oguzhan.caglar@pavotek.com.tr
> >
> > www.pavotek.com.tr<http://www.pavotek.com.tr>
> >
> >
> > Gönderen: Andrei Kartashev <a.kartashev@yadro.com>
> > Gönderildi: 11 Ağustos 2022 Perşembe 22:28:16
> > Kime: Oğuzhan ÇAĞLAR; openbmc@lists.ozlabs.org
> > Konu: (External) Re: Adding Inventory
> >
> >
> > Warning: This e-mail came from an external source. If you do not
> > trust the sender or if there is anything suspicious in the content
> > of
> > the e-mail, please inform the IT department.
> >
> >
> >
> > Hello Oguzhan,
> >
> > This is a very common question for newcomers, I believe is was
> > already
> > answered somewhere in the list.
> > BMC out of the box don't have any knowledge on host's equipment
> > (CPU,
> > DIMM, Drive, AIC, etc) - it is up to you to deliver this
> > information
> > from host to BMC. As for now the most common way to feed BMC the
> > information regarding CPU and DIMM is to transfer smbios tables via
> > ipmi. You can implement any other mechanism but any way, you need
> > to
> > have some code in your BIOS.
> >
> > As soon as you have the CPU/DIMM information on BMC it can be shown
> > in
> > bmcweb by implementing corresponding dbus interfaces
> > (xyz.openbmc_project.Inventory.Item.Cpu and
> > xyz.openbmc_project.Inventory.Item.Dimm). smbiosmdrv2 daemon do
> > this,
> > but you also can add EntityManager configuration files for this or
> > write your own daemon to expose the interfaces.
> >
> > On Thu, 2022-08-04 at 08:07 +0000, Oğuzhan ÇAĞLAR wrote:
> > > Hello,
> > >
> > > I'm working on openbmc for ast2500 bmc. I want to add inventory
> > > such
> > > as CPU and DIMM etc. I added the chassis from .json file but I
> > > couldn't add the CPU and DIMM. I know this is to related with
> > > entity-
> > > manager. How can I add these inventory on WEBUI? Can you give
> > > some
> > > information about this issue?
> > >
> > > Regards.
> > >
> > > Oğuzhan Çağlar
> > > Software Design Engineer
> > >
> > >
> > >
> > > Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> > > Teknopark İstanbul, Kurtköy Pendik İSTANBUL
> > >
> > >
> > > Tel             : +90 (216) 354 72 86
> > > Faks         : +90 (216) 354 76 77
> > > Gsm          : +90 (507) 585 10 60
> > > oguzhan.caglar@pavotek.com.tr
> > >
> > > www.pavotek.com.tr<http://www.pavotek.com.tr>
> > >
> > >
> >
> > --
> > Best regards,
> > Andrei Kartashev,
> > Lead BMC Developer
> >
>
> --
> Best regards,
> Andrei Kartashev,
> Lead BMC Developer
>

--
Best regards,
Andrei Kartashev,
Lead BMC Developer


[-- Attachment #2: Type: text/html, Size: 17854 bytes --]

Re: Ynt: Ynt: Ynt: (External) Re: Adding Inventory

[Andrei Kartashev]

On Mon, 2022-08-15 at 12:36 +0000, Oğuzhan ÇAĞLAR wrote:
> 
> Thank you, Andrei,
> 
> I successfully built it now. Why do I get this error? 

cpuinfo is additional daemon, that actually do nothing with smbios, but
it can get some CPU-related information by using PECI interface. For
about couple of years PECI wasn't supported by upstream OpenBMC, the
implementation was only in Intel's fork.
I don't know actual situation, but I guess you just miss some libraries
for PECI support.
Anyway, you don't need this at this stage.

> In addition, I guess I have to dive into BIOS to get information
> about CPU and DIMM. Is it right? 

Yes, smbiosmdrv2 daemon reads SMBIOS information from the file
/var/lib/smbios/smbios2 and you have to somehow deliver it to the BMC
filesystem.

> Is there any example to do that?

Not sure. I think I saw somewhere in the Internet example of delivering
it using phosphor-ipmi-blobs.

> What exactly do the smbios-mdr daemon?
> 

Well, it just parse SMBIOS tables from binary file and expose extracted
information to dbus for other daemons use.

> Oğuzhan Çağlar
> Yazılım Mühendisi
>  
>  
>  
> Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> Teknopark İstanbul, Kurtköy Pendik İSTANBUL
>  
>       
> Tel             : +90 (216) 354 72 86
> Faks         : +90 (216) 354 76 77
> Gsm          : +90 (507) 585 10 60
> oguzhan.caglar@pavotek.com.tr
>  
> www.pavotek.com.tr
> 
>  
> Gönderen: Andrei Kartashev <a.kartashev@yadro.com>
> Gönderildi: 15 Ağustos 2022 Pazartesi 13:23:33
> Kime: Oğuzhan ÇAĞLAR; openbmc@lists.ozlabs.org
> Konu: Re: Ynt: Ynt: (External) Re: Adding Inventory
>  
> 
> Warning: This e-mail came from an external source. If you do not
> trust the sender or if there is anything suspicious in the content of
> the e-mail, please inform the IT department.
> 
> 
> 
> As I assumed, it is PCUInfo issue:
> 
> |
> /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work
> /a
> rm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-
> r1/git/src/cpuinfo_main.cpp:407:14: error: 'icxd' was not declared in
> this scope; did you mean 'icx'?
> |   407 |         case icxd:
> |       |              ^~~~
> |       |              icx
> |
> /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work
> /a
> rm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-
> r1/git/src/cpuinfo_main.cpp:408:14: error: 'spr' was not declared in
> this scope
> |   408 |         case spr:
> |       |              ^~~
> 
> 
> Turn it off in you bbappend with `PACKAGECONFIG:remove = " cpuinfo"`
> 
> 
> 
> On Mon, 2022-08-15 at 07:25 +0000, Oğuzhan ÇAĞLAR wrote:
> > 
> > I'm sharing with you that my yocto errors are related to smbios-
> > mdr in the .txt file.
> > 
> > I don't understand, How can the CPU information match with entity-
> > manager configuration files? I saw your comment in openbmc list
> > about
> > PCIe. It probes only with xyz.openbmc_project.FruDevice.
> > 
> > 
> > Oğuzhan Çağlar
> > Software Design Engineer
> > 
> > 
> > 
> > Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> > Teknopark İstanbul, Kurtköy Pendik İSTANBUL
> > 
> > 
> > Tel             : +90 (216) 354 72 86
> > Faks         : +90 (216) 354 76 77
> > Gsm          : +90 (507) 585 10 60
> > oguzhan.caglar@pavotek.com.tr
> > 
> > www.pavotek.com.tr
> > 
> > 
> > Gönderen: Andrei Kartashev <a.kartashev@yadro.com>
> > Gönderildi: 12 Ağustos 2022 Cuma 22:14:38
> > Kime: Oğuzhan ÇAĞLAR; openbmc@lists.ozlabs.org
> > Konu: Re: Ynt: (External) Re: Adding Inventory
> > 
> > 
> > Warning: This e-mail came from an external source. If you do not
> > trust the sender or if there is anything suspicious in the content
> > of
> > the e-mail, please inform the IT department.
> > 
> > 
> > 
> > I have no idea on what do you mean saying "added the CPU and DIMM
> > configuration files within the .yaml files", but I guess you are
> > trying
> > to hardcode this information, which I believe not what ou actually
> > expect to get.
> > You probably should learn how the OpenBMC works inside. You can use
> > busctl tool for that.
> > 
> > Regarding compilation error of smbios-mdr daemon, I can say nothing
> > without knowing the issue. There should not be any special
> > configuration files for this smbios-mdr recipe but probably you
> > trying
> > to build CPUInfo part of the recipe without having PECI library.
> > You
> > likely should disable cpuinfo app.
> > 
> > On Fri, 2022-08-12 at 06:50 +0000, Oğuzhan ÇAĞLAR wrote:
> > > Hi Andrei,
> > > 
> > > Thank you for your information. I have already added the CPU and
> > > DIMM
> > > configuration files within the .yaml files. When I added these
> > > files(related to the path: xyz.openbmc_project.Inventory.Item.Cpu
> > > and xyz.openbmc_project.Inventory.Item.Dimm), I see the CPU and
> > > DIMM
> > > entries over WebUI. However, In this way, I add the properties
> > > such
> > > as (PartNumber, SerialNumber, etc.) on my own. I have already
> > > generated a .bin file that has FRU information (chassis, board
> > > etc.)
> > > and I included this in BMC's image file. In addition, I see the
> > > properties related to Chassis, Board on WebUI.
> > > 
> > > I have already checked the smbios-mdr daemon in openbmc. However,
> > > when I include this daemon in my yocto image, the bitbake shows
> > > some
> > > errors that are related to smbios-mdr's .cpp files. I guess I
> > > have
> > > to
> > > create some configuration files before doing it. Is it wrong?
> > > What
> > > should I do?
> > > 
> > > I guess I have to need some code in BIOS. Is there any example to
> > > do
> > > this? I don't know where I should start.
> > > 
> > > Thank you.
> > > 
> > > Oğuzhan Çağlar
> > > Software Design Engineer
> > > 
> > > 
> > > 
> > > Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> > > Teknopark İstanbul, Kurtköy Pendik İSTANBUL
> > > 
> > > 
> > > Tel             : +90 (216) 354 72 86
> > > Faks         : +90 (216) 354 76 77
> > > Gsm          : +90 (507) 585 10 60
> > > oguzhan.caglar@pavotek.com.tr
> > > 
> > > www.pavotek.com.tr
> > > 
> > > 
> > > Gönderen: Andrei Kartashev <a.kartashev@yadro.com>
> > > Gönderildi: 11 Ağustos 2022 Perşembe 22:28:16
> > > Kime: Oğuzhan ÇAĞLAR; openbmc@lists.ozlabs.org
> > > Konu: (External) Re: Adding Inventory
> > > 
> > > 
> > > Warning: This e-mail came from an external source. If you do not
> > > trust the sender or if there is anything suspicious in the
> > > content
> > > of
> > > the e-mail, please inform the IT department.
> > > 
> > > 
> > > 
> > > Hello Oguzhan,
> > > 
> > > This is a very common question for newcomers, I believe is was
> > > already
> > > answered somewhere in the list.
> > > BMC out of the box don't have any knowledge on host's equipment
> > > (CPU,
> > > DIMM, Drive, AIC, etc) - it is up to you to deliver this
> > > information
> > > from host to BMC. As for now the most common way to feed BMC the
> > > information regarding CPU and DIMM is to transfer smbios tables
> > > via
> > > ipmi. You can implement any other mechanism but any way, you need
> > > to
> > > have some code in your BIOS.
> > > 
> > > As soon as you have the CPU/DIMM information on BMC it can be
> > > shown
> > > in
> > > bmcweb by implementing corresponding dbus interfaces
> > > (xyz.openbmc_project.Inventory.Item.Cpu and
> > > xyz.openbmc_project.Inventory.Item.Dimm). smbiosmdrv2 daemon do
> > > this,
> > > but you also can add EntityManager configuration files for this
> > > or
> > > write your own daemon to expose the interfaces.
> > > 
> > > On Thu, 2022-08-04 at 08:07 +0000, Oğuzhan ÇAĞLAR wrote:
> > > > Hello,
> > > > 
> > > > I'm working on openbmc for ast2500 bmc. I want to add inventory
> > > > such
> > > > as CPU and DIMM etc. I added the chassis from .json file but I
> > > > couldn't add the CPU and DIMM. I know this is to related with
> > > > entity-
> > > > manager. How can I add these inventory on WEBUI? Can you give
> > > > some
> > > > information about this issue?
> > > > 
> > > > Regards.
> > > > 
> > > > Oğuzhan Çağlar
> > > > Software Design Engineer
> > > > 
> > > > 
> > > > 
> > > > Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> > > > Teknopark İstanbul, Kurtköy Pendik İSTANBUL
> > > > 
> > > > 
> > > > Tel             : +90 (216) 354 72 86
> > > > Faks         : +90 (216) 354 76 77
> > > > Gsm          : +90 (507) 585 10 60
> > > > oguzhan.caglar@pavotek.com.tr
> > > > 
> > > > www.pavotek.com.tr
> > > > 
> > > > 
> > > 
> > > --
> > > Best regards,
> > > Andrei Kartashev,
> > > Lead BMC Developer
> > > 
> > 
> > --
> > Best regards,
> > Andrei Kartashev,
> > Lead BMC Developer
> > 
> 
> --
> Best regards,
> Andrei Kartashev,
> Lead BMC Developer
> 

-- 
Best regards,
Andrei Kartashev,
Lead BMC Developer

Ynt: Ynt: Ynt: Ynt: (External) Re: Adding Inventory

[Oğuzhan ÇAĞLAR]

[-- Attachment #1: Type: text/plain, Size: 10833 bytes --]


Thank you, It is too helpful!


1) What is the interface over which the Intel x86 CPU sends data to the BMC? KCS or something?

2) I see /var/lib/smbios but don't see /var/lib/smbios/smbios2 in my system. It will be created when the file is received?

3) When the file arrives from the CPU to the BMC, Can I see the information in webui? Do I have to create any configuration files in entity-manager or phosphor-inventory-manager to do this?

4) Besides the CPU and DIMM information, How can I see the information of the chassis and board? I think the only way to do this is FRU? I mean, this information is kept in any EEPROM as binary in the production process of boards. If I think wrong, Is there any way to see the information of the chassis or board?


Regards.


Oğuzhan Çağlar

Software Design Engineer





[https://posta.pavotek.com.tr/owa/]








[https://posta.pavotek.com.tr/owa/]


Pavo Tasarım Üretim Elektronik Tic. A.Ş.

Teknopark İstanbul, Kurtköy Pendik İSTANBUL




       [https://posta.pavotek.com.tr/owa/] <http://pavotek.com.tr/>


Tel             : +90 (216) 354 72 86


Faks         : +90 (216) 354 76 77


Gsm          : +90 (507) 585 10 60


oguzhan.caglar@pavotek.com.tr<mailto:oguzhan.caglar@pavotek.com.tr>





www.pavotek.com.tr<http://www.pavotek.com.tr/>




________________________________
Gönderen: Andrei Kartashev <a.kartashev@yadro.com>
Gönderildi: 17 Ağustos 2022 Çarşamba 12:02:39
Kime: Oğuzhan ÇAĞLAR; openbmc@lists.ozlabs.org
Konu: Re: Ynt: Ynt: Ynt: (External) Re: Adding Inventory


Warning: This e-mail came from an external source. If you do not trust the sender or if there is anything suspicious in the content of the e-mail, please inform the IT department.



On Mon, 2022-08-15 at 12:36 +0000, Oğuzhan ÇAĞLAR wrote:
>
> Thank you, Andrei,
>
> I successfully built it now. Why do I get this error?

cpuinfo is additional daemon, that actually do nothing with smbios, but
it can get some CPU-related information by using PECI interface. For
about couple of years PECI wasn't supported by upstream OpenBMC, the
implementation was only in Intel's fork.
I don't know actual situation, but I guess you just miss some libraries
for PECI support.
Anyway, you don't need this at this stage.

> In addition, I guess I have to dive into BIOS to get information
> about CPU and DIMM. Is it right?

Yes, smbiosmdrv2 daemon reads SMBIOS information from the file
/var/lib/smbios/smbios2 and you have to somehow deliver it to the BMC
filesystem.

> Is there any example to do that?

Not sure. I think I saw somewhere in the Internet example of delivering
it using phosphor-ipmi-blobs.

> What exactly do the smbios-mdr daemon?
>

Well, it just parse SMBIOS tables from binary file and expose extracted
information to dbus for other daemons use.

> Oğuzhan Çağlar
> Yazılım Mühendisi
>
>
>
> Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> Teknopark İstanbul, Kurtköy Pendik İSTANBUL
>
>
> Tel             : +90 (216) 354 72 86
> Faks         : +90 (216) 354 76 77
> Gsm          : +90 (507) 585 10 60
> oguzhan.caglar@pavotek.com.tr
>
> www.pavotek.com.tr<http://www.pavotek.com.tr>
>
>
> Gönderen: Andrei Kartashev <a.kartashev@yadro.com>
> Gönderildi: 15 Ağustos 2022 Pazartesi 13:23:33
> Kime: Oğuzhan ÇAĞLAR; openbmc@lists.ozlabs.org
> Konu: Re: Ynt: Ynt: (External) Re: Adding Inventory
>
>
> Warning: This e-mail came from an external source. If you do not
> trust the sender or if there is anything suspicious in the content of
> the e-mail, please inform the IT department.
>
>
>
> As I assumed, it is PCUInfo issue:
>
> |
> /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work
> /a
> rm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-
> r1/git/src/cpuinfo_main.cpp:407:14: error: 'icxd' was not declared in
> this scope; did you mean 'icx'?
> |   407 |         case icxd:
> |       |              ^~~~
> |       |              icx
> |
> /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work
> /a
> rm1176jzs-openbmc-linux-gnueabi/smbios-mdr/1.0+gitAUTOINC+e4ea37716d-
> r1/git/src/cpuinfo_main.cpp:408:14: error: 'spr' was not declared in
> this scope
> |   408 |         case spr:
> |       |              ^~~
>
>
> Turn it off in you bbappend with `PACKAGECONFIG:remove = " cpuinfo"`
>
>
>
> On Mon, 2022-08-15 at 07:25 +0000, Oğuzhan ÇAĞLAR wrote:
> >
> > I'm sharing with you that my yocto errors are related to smbios-
> > mdr in the .txt file.
> >
> > I don't understand, How can the CPU information match with entity-
> > manager configuration files? I saw your comment in openbmc list
> > about
> > PCIe. It probes only with xyz.openbmc_project.FruDevice.
> >
> >
> > Oğuzhan Çağlar
> > Software Design Engineer
> >
> >
> >
> > Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> > Teknopark İstanbul, Kurtköy Pendik İSTANBUL
> >
> >
> > Tel             : +90 (216) 354 72 86
> > Faks         : +90 (216) 354 76 77
> > Gsm          : +90 (507) 585 10 60
> > oguzhan.caglar@pavotek.com.tr
> >
> > www.pavotek.com.tr<http://www.pavotek.com.tr>
> >
> >
> > Gönderen: Andrei Kartashev <a.kartashev@yadro.com>
> > Gönderildi: 12 Ağustos 2022 Cuma 22:14:38
> > Kime: Oğuzhan ÇAĞLAR; openbmc@lists.ozlabs.org
> > Konu: Re: Ynt: (External) Re: Adding Inventory
> >
> >
> > Warning: This e-mail came from an external source. If you do not
> > trust the sender or if there is anything suspicious in the content
> > of
> > the e-mail, please inform the IT department.
> >
> >
> >
> > I have no idea on what do you mean saying "added the CPU and DIMM
> > configuration files within the .yaml files", but I guess you are
> > trying
> > to hardcode this information, which I believe not what ou actually
> > expect to get.
> > You probably should learn how the OpenBMC works inside. You can use
> > busctl tool for that.
> >
> > Regarding compilation error of smbios-mdr daemon, I can say nothing
> > without knowing the issue. There should not be any special
> > configuration files for this smbios-mdr recipe but probably you
> > trying
> > to build CPUInfo part of the recipe without having PECI library.
> > You
> > likely should disable cpuinfo app.
> >
> > On Fri, 2022-08-12 at 06:50 +0000, Oğuzhan ÇAĞLAR wrote:
> > > Hi Andrei,
> > >
> > > Thank you for your information. I have already added the CPU and
> > > DIMM
> > > configuration files within the .yaml files. When I added these
> > > files(related to the path: xyz.openbmc_project.Inventory.Item.Cpu
> > > and xyz.openbmc_project.Inventory.Item.Dimm), I see the CPU and
> > > DIMM
> > > entries over WebUI. However, In this way, I add the properties
> > > such
> > > as (PartNumber, SerialNumber, etc.) on my own. I have already
> > > generated a .bin file that has FRU information (chassis, board
> > > etc.)
> > > and I included this in BMC's image file. In addition, I see the
> > > properties related to Chassis, Board on WebUI.
> > >
> > > I have already checked the smbios-mdr daemon in openbmc. However,
> > > when I include this daemon in my yocto image, the bitbake shows
> > > some
> > > errors that are related to smbios-mdr's .cpp files. I guess I
> > > have
> > > to
> > > create some configuration files before doing it. Is it wrong?
> > > What
> > > should I do?
> > >
> > > I guess I have to need some code in BIOS. Is there any example to
> > > do
> > > this? I don't know where I should start.
> > >
> > > Thank you.
> > >
> > > Oğuzhan Çağlar
> > > Software Design Engineer
> > >
> > >
> > >
> > > Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> > > Teknopark İstanbul, Kurtköy Pendik İSTANBUL
> > >
> > >
> > > Tel             : +90 (216) 354 72 86
> > > Faks         : +90 (216) 354 76 77
> > > Gsm          : +90 (507) 585 10 60
> > > oguzhan.caglar@pavotek.com.tr
> > >
> > > www.pavotek.com.tr<http://www.pavotek.com.tr>
> > >
> > >
> > > Gönderen: Andrei Kartashev <a.kartashev@yadro.com>
> > > Gönderildi: 11 Ağustos 2022 Perşembe 22:28:16
> > > Kime: Oğuzhan ÇAĞLAR; openbmc@lists.ozlabs.org
> > > Konu: (External) Re: Adding Inventory
> > >
> > >
> > > Warning: This e-mail came from an external source. If you do not
> > > trust the sender or if there is anything suspicious in the
> > > content
> > > of
> > > the e-mail, please inform the IT department.
> > >
> > >
> > >
> > > Hello Oguzhan,
> > >
> > > This is a very common question for newcomers, I believe is was
> > > already
> > > answered somewhere in the list.
> > > BMC out of the box don't have any knowledge on host's equipment
> > > (CPU,
> > > DIMM, Drive, AIC, etc) - it is up to you to deliver this
> > > information
> > > from host to BMC. As for now the most common way to feed BMC the
> > > information regarding CPU and DIMM is to transfer smbios tables
> > > via
> > > ipmi. You can implement any other mechanism but any way, you need
> > > to
> > > have some code in your BIOS.
> > >
> > > As soon as you have the CPU/DIMM information on BMC it can be
> > > shown
> > > in
> > > bmcweb by implementing corresponding dbus interfaces
> > > (xyz.openbmc_project.Inventory.Item.Cpu and
> > > xyz.openbmc_project.Inventory.Item.Dimm). smbiosmdrv2 daemon do
> > > this,
> > > but you also can add EntityManager configuration files for this
> > > or
> > > write your own daemon to expose the interfaces.
> > >
> > > On Thu, 2022-08-04 at 08:07 +0000, Oğuzhan ÇAĞLAR wrote:
> > > > Hello,
> > > >
> > > > I'm working on openbmc for ast2500 bmc. I want to add inventory
> > > > such
> > > > as CPU and DIMM etc. I added the chassis from .json file but I
> > > > couldn't add the CPU and DIMM. I know this is to related with
> > > > entity-
> > > > manager. How can I add these inventory on WEBUI? Can you give
> > > > some
> > > > information about this issue?
> > > >
> > > > Regards.
> > > >
> > > > Oğuzhan Çağlar
> > > > Software Design Engineer
> > > >
> > > >
> > > >
> > > > Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> > > > Teknopark İstanbul, Kurtköy Pendik İSTANBUL
> > > >
> > > >
> > > > Tel             : +90 (216) 354 72 86
> > > > Faks         : +90 (216) 354 76 77
> > > > Gsm          : +90 (507) 585 10 60
> > > > oguzhan.caglar@pavotek.com.tr
> > > >
> > > > www.pavotek.com.tr<http://www.pavotek.com.tr>
> > > >
> > > >
> > >
> > > --
> > > Best regards,
> > > Andrei Kartashev,
> > > Lead BMC Developer
> > >
> >
> > --
> > Best regards,
> > Andrei Kartashev,
> > Lead BMC Developer
> >
>
> --
> Best regards,
> Andrei Kartashev,
> Lead BMC Developer
>

--
Best regards,
Andrei Kartashev,
Lead BMC Developer


[-- Attachment #2: Type: text/html, Size: 22213 bytes --]

Re: Ynt: Ynt: Ynt: Ynt: (External) Re: Adding Inventory

[Andrei Kartashev]

1) It depends on your board, you should know better. If you don't know,
then it is likely KCS.
2) Yes
3) Yes, you don't need to have to create any additional configs
4) Yes, the common way is to program VPD/FRU to eeprom during
production stage. But this can vary depending on your board design and
manufacturing workflow.

Brad, I feel this questions rises each time when newcomers start
porting OBMC on their new board. Seems like we should have this
information in somewhere beginners guide.

On Thu, 2022-08-18 at 07:31 +0000, Oğuzhan ÇAĞLAR wrote:
> «Внимание! Данное письмо от внешнего адресата!» 
> 
> Thank you, It is too helpful!
> 
> 1) What is the interface over which the Intel x86 CPU sends data to
> the BMC? KCS or something?
> 2) I see /var/lib/smbios but don't see /var/lib/smbios/smbios2 in my
> system. It will be created when the file is received?
> 3) When the file arrives from the CPU to the BMC, Can I see the
> information in webui? Do I have to create any configuration files in
> entity-manager or phosphor-inventory-manager to do this? 
> 4) Besides the CPU and DIMM information, How can I see the
> information of the chassis and board? I think the only way to do this
> is FRU? I mean, this information is kept in any EEPROM as binary in
> the production process of boards. If I think wrong, Is there any way
> to see the information of the chassis or board?
> 
> Regards.
> 
> Oğuzhan Çağlar
> Software Design Engineer
>  
>  
>  
> Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> Teknopark İstanbul, Kurtköy Pendik İSTANBUL
>  
>       
> Tel             : +90 (216) 354 72 86
> Faks         : +90 (216) 354 76 77
> Gsm          : +90 (507) 585 10 60
> oguzhan.caglar@pavotek.com.tr
>  
> www.pavotek.com.tr
> 
>  
> Gönderen: Andrei Kartashev <a.kartashev@yadro.com>
> Gönderildi: 17 Ağustos 2022 Çarşamba 12:02:39
> Kime: Oğuzhan ÇAĞLAR; openbmc@lists.ozlabs.org
> Konu: Re: Ynt: Ynt: Ynt: (External) Re: Adding Inventory
>  
> 
> Warning: This e-mail came from an external source. If you do not
> trust the sender or if there is anything suspicious in the content of
> the e-mail, please inform the IT department.
> 
> 
> 
> On Mon, 2022-08-15 at 12:36 +0000, Oğuzhan ÇAĞLAR wrote:
> > 
> > Thank you, Andrei,
> > 
> > I successfully built it now. Why do I get this error?
> 
> cpuinfo is additional daemon, that actually do nothing with smbios,
> but
> it can get some CPU-related information by using PECI interface. For
> about couple of years PECI wasn't supported by upstream OpenBMC, the
> implementation was only in Intel's fork.
> I don't know actual situation, but I guess you just miss some
> libraries
> for PECI support.
> Anyway, you don't need this at this stage.
> 
> > In addition, I guess I have to dive into BIOS to get information
> > about CPU and DIMM. Is it right?
> 
> Yes, smbiosmdrv2 daemon reads SMBIOS information from the file
> /var/lib/smbios/smbios2 and you have to somehow deliver it to the BMC
> filesystem.
> 
> > Is there any example to do that?
> 
> Not sure. I think I saw somewhere in the Internet example of
> delivering
> it using phosphor-ipmi-blobs.
> 
> > What exactly do the smbios-mdr daemon?
> > 
> 
> Well, it just parse SMBIOS tables from binary file and expose
> extracted
> information to dbus for other daemons use.
> 
> > Oğuzhan Çağlar
> > Yazılım Mühendisi
> > 
> > 
> > 
> > Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> > Teknopark İstanbul, Kurtköy Pendik İSTANBUL
> > 
> > 
> > Tel             : +90 (216) 354 72 86
> > Faks         : +90 (216) 354 76 77
> > Gsm          : +90 (507) 585 10 60
> > oguzhan.caglar@pavotek.com.tr
> > 
> > www.pavotek.com.tr
> > 
> > 
> > Gönderen: Andrei Kartashev <a.kartashev@yadro.com>
> > Gönderildi: 15 Ağustos 2022 Pazartesi 13:23:33
> > Kime: Oğuzhan ÇAĞLAR; openbmc@lists.ozlabs.org
> > Konu: Re: Ynt: Ynt: (External) Re: Adding Inventory
> > 
> > 
> > Warning: This e-mail came from an external source. If you do not
> > trust the sender or if there is anything suspicious in the content
> > of
> > the e-mail, please inform the IT department.
> > 
> > 
> > 
> > As I assumed, it is PCUInfo issue:
> > 
> > |
> > /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/wo
> > rk
> > /a
> > rm1176jzs-openbmc-linux-gnueabi/smbios-
> > mdr/1.0+gitAUTOINC+e4ea37716d-
> > r1/git/src/cpuinfo_main.cpp:407:14: error: 'icxd' was not declared
> > in
> > this scope; did you mean 'icx'?
> > |   407 |         case icxd:
> > |       |              ^~~~
> > |       |              icx
> > |
> > /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/wo
> > rk
> > /a
> > rm1176jzs-openbmc-linux-gnueabi/smbios-
> > mdr/1.0+gitAUTOINC+e4ea37716d-
> > r1/git/src/cpuinfo_main.cpp:408:14: error: 'spr' was not declared
> > in
> > this scope
> > |   408 |         case spr:
> > |       |              ^~~
> > 
> > 
> > Turn it off in you bbappend with `PACKAGECONFIG:remove = "
> > cpuinfo"`
> > 
> > 
> > 
> > On Mon, 2022-08-15 at 07:25 +0000, Oğuzhan ÇAĞLAR wrote:
> > > 
> > > I'm sharing with you that my yocto errors are related to smbios-
> > > mdr in the .txt file.
> > > 
> > > I don't understand, How can the CPU information match with
> > > entity-
> > > manager configuration files? I saw your comment in openbmc list
> > > about
> > > PCIe. It probes only with xyz.openbmc_project.FruDevice.
> > > 
> > > 
> > > Oğuzhan Çağlar
> > > Software Design Engineer
> > > 
> > > 
> > > 
> > > Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> > > Teknopark İstanbul, Kurtköy Pendik İSTANBUL
> > > 
> > > 
> > > Tel             : +90 (216) 354 72 86
> > > Faks         : +90 (216) 354 76 77
> > > Gsm          : +90 (507) 585 10 60
> > > oguzhan.caglar@pavotek.com.tr
> > > 
> > > www.pavotek.com.tr
> > > 
> > > 
> > > Gönderen: Andrei Kartashev <a.kartashev@yadro.com>
> > > Gönderildi: 12 Ağustos 2022 Cuma 22:14:38
> > > Kime: Oğuzhan ÇAĞLAR; openbmc@lists.ozlabs.org
> > > Konu: Re: Ynt: (External) Re: Adding Inventory
> > > 
> > > 
> > > Warning: This e-mail came from an external source. If you do not
> > > trust the sender or if there is anything suspicious in the
> > > content
> > > of
> > > the e-mail, please inform the IT department.
> > > 
> > > 
> > > 
> > > I have no idea on what do you mean saying "added the CPU and DIMM
> > > configuration files within the .yaml files", but I guess you are
> > > trying
> > > to hardcode this information, which I believe not what ou
> > > actually
> > > expect to get.
> > > You probably should learn how the OpenBMC works inside. You can
> > > use
> > > busctl tool for that.
> > > 
> > > Regarding compilation error of smbios-mdr daemon, I can say
> > > nothing
> > > without knowing the issue. There should not be any special
> > > configuration files for this smbios-mdr recipe but probably you
> > > trying
> > > to build CPUInfo part of the recipe without having PECI library.
> > > You
> > > likely should disable cpuinfo app.
> > > 
> > > On Fri, 2022-08-12 at 06:50 +0000, Oğuzhan ÇAĞLAR wrote:
> > > > Hi Andrei,
> > > > 
> > > > Thank you for your information. I have already added the CPU
> > > > and
> > > > DIMM
> > > > configuration files within the .yaml files. When I added these
> > > > files(related to the path:
> > > > xyz.openbmc_project.Inventory.Item.Cpu
> > > > and xyz.openbmc_project.Inventory.Item.Dimm), I see the CPU and
> > > > DIMM
> > > > entries over WebUI. However, In this way, I add the properties
> > > > such
> > > > as (PartNumber, SerialNumber, etc.) on my own. I have already
> > > > generated a .bin file that has FRU information (chassis, board
> > > > etc.)
> > > > and I included this in BMC's image file. In addition, I see the
> > > > properties related to Chassis, Board on WebUI.
> > > > 
> > > > I have already checked the smbios-mdr daemon in openbmc.
> > > > However,
> > > > when I include this daemon in my yocto image, the bitbake shows
> > > > some
> > > > errors that are related to smbios-mdr's .cpp files. I guess I
> > > > have
> > > > to
> > > > create some configuration files before doing it. Is it wrong?
> > > > What
> > > > should I do?
> > > > 
> > > > I guess I have to need some code in BIOS. Is there any example
> > > > to
> > > > do
> > > > this? I don't know where I should start.
> > > > 
> > > > Thank you.
> > > > 
> > > > Oğuzhan Çağlar
> > > > Software Design Engineer
> > > > 
> > > > 
> > > > 
> > > > Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> > > > Teknopark İstanbul, Kurtköy Pendik İSTANBUL
> > > > 
> > > > 
> > > > Tel             : +90 (216) 354 72 86
> > > > Faks         : +90 (216) 354 76 77
> > > > Gsm          : +90 (507) 585 10 60
> > > > oguzhan.caglar@pavotek.com.tr
> > > > 
> > > > www.pavotek.com.tr
> > > > 
> > > > 
> > > > Gönderen: Andrei Kartashev <a.kartashev@yadro.com>
> > > > Gönderildi: 11 Ağustos 2022 Perşembe 22:28:16
> > > > Kime: Oğuzhan ÇAĞLAR; openbmc@lists.ozlabs.org
> > > > Konu: (External) Re: Adding Inventory
> > > > 
> > > > 
> > > > Warning: This e-mail came from an external source. If you do
> > > > not
> > > > trust the sender or if there is anything suspicious in the
> > > > content
> > > > of
> > > > the e-mail, please inform the IT department.
> > > > 
> > > > 
> > > > 
> > > > Hello Oguzhan,
> > > > 
> > > > This is a very common question for newcomers, I believe is was
> > > > already
> > > > answered somewhere in the list.
> > > > BMC out of the box don't have any knowledge on host's equipment
> > > > (CPU,
> > > > DIMM, Drive, AIC, etc) - it is up to you to deliver this
> > > > information
> > > > from host to BMC. As for now the most common way to feed BMC
> > > > the
> > > > information regarding CPU and DIMM is to transfer smbios tables
> > > > via
> > > > ipmi. You can implement any other mechanism but any way, you
> > > > need
> > > > to
> > > > have some code in your BIOS.
> > > > 
> > > > As soon as you have the CPU/DIMM information on BMC it can be
> > > > shown
> > > > in
> > > > bmcweb by implementing corresponding dbus interfaces
> > > > (xyz.openbmc_project.Inventory.Item.Cpu and
> > > > xyz.openbmc_project.Inventory.Item.Dimm). smbiosmdrv2 daemon do
> > > > this,
> > > > but you also can add EntityManager configuration files for this
> > > > or
> > > > write your own daemon to expose the interfaces.
> > > > 
> > > > On Thu, 2022-08-04 at 08:07 +0000, Oğuzhan ÇAĞLAR wrote:
> > > > > Hello,
> > > > > 
> > > > > I'm working on openbmc for ast2500 bmc. I want to add
> > > > > inventory
> > > > > such
> > > > > as CPU and DIMM etc. I added the chassis from .json file but
> > > > > I
> > > > > couldn't add the CPU and DIMM. I know this is to related with
> > > > > entity-
> > > > > manager. How can I add these inventory on WEBUI? Can you give
> > > > > some
> > > > > information about this issue?
> > > > > 
> > > > > Regards.
> > > > > 
> > > > > Oğuzhan Çağlar
> > > > > Software Design Engineer
> > > > > 
> > > > > 
> > > > > 
> > > > > Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> > > > > Teknopark İstanbul, Kurtköy Pendik İSTANBUL
> > > > > 
> > > > > 
> > > > > Tel             : +90 (216) 354 72 86
> > > > > Faks         : +90 (216) 354 76 77
> > > > > Gsm          : +90 (507) 585 10 60
> > > > > oguzhan.caglar@pavotek.com.tr
> > > > > 
> > > > > www.pavotek.com.tr
> > > > > 
> > > > > 
> > > > 
> > > > --
> > > > Best regards,
> > > > Andrei Kartashev,
> > > > Lead BMC Developer
> > > > 
> > > 
> > > --
> > > Best regards,
> > > Andrei Kartashev,
> > > Lead BMC Developer
> > > 
> > 
> > --
> > Best regards,
> > Andrei Kartashev,
> > Lead BMC Developer
> > 
> 
> --
> Best regards,
> Andrei Kartashev,
> Lead BMC Developer
> 

-- 
Best regards,
Andrei Kartashev,
Lead BMC Developer

Ynt: Ynt: Ynt: Ynt: Ynt: (External) Re: Adding Inventory

[Oğuzhan ÇAĞLAR]

[-- Attachment #1.1: Type: text/plain, Size: 13681 bytes --]

Thanks,


1) I'm confused about this. I didn't connect any BMC's i2c buses to the CPU. Is that any problem for me? I mean, I have to BMC's i2c buses to CPU? Because these pins were not connected to any CPU's pins. It is empty. May it be my problem? I mean, If I connect these buses to CPU, Can I get the information?


2) When I build the "intel-oem-ipmi", It shows me an error. I guess The "intel-oem-ipmi" is required for the x86 CPU. I start to think that the openbmc doesn't support this. I attached the error file.


Regards.


Oğuzhan Çağlar

Software Design Engineer




[X]








[X]


Pavo Tasarım Üretim Elektronik Tic. A.Ş.

Teknopark İstanbul, Kurtköy Pendik İSTANBUL




       [X] <http://pavotek.com.tr/>


Tel             : +90 (216) 354 72 86


Faks         : +90 (216) 354 76 77


Gsm          : +90 (507) 585 10 60


oguzhan.caglar@pavotek.com.tr<mailto:oguzhan.caglar@pavotek.com.tr>





www.pavotek.com.tr<http://www.pavotek.com.tr/>




________________________________
Gönderen: Andrei Kartashev <a.kartashev@yadro.com>
Gönderildi: 18 Ağustos 2022 Perşembe 11:38:44
Kime: Oğuzhan ÇAĞLAR; Brad Bishop
Bilgi: <openbmc@lists.ozlabs.org>
Konu: Re: Ynt: Ynt: Ynt: Ynt: (External) Re: Adding Inventory


Warning: This e-mail came from an external source. If you do not trust the sender or if there is anything suspicious in the content of the e-mail, please inform the IT department.



1) It depends on your board, you should know better. If you don't know,
then it is likely KCS.
2) Yes
3) Yes, you don't need to have to create any additional configs
4) Yes, the common way is to program VPD/FRU to eeprom during
production stage. But this can vary depending on your board design and
manufacturing workflow.

Brad, I feel this questions rises each time when newcomers start
porting OBMC on their new board. Seems like we should have this
information in somewhere beginners guide.

On Thu, 2022-08-18 at 07:31 +0000, Oğuzhan ÇAĞLAR wrote:
> «Внимание! Данное письмо от внешнего адресата!»
>
> Thank you, It is too helpful!
>
> 1) What is the interface over which the Intel x86 CPU sends data to
> the BMC? KCS or something?
> 2) I see /var/lib/smbios but don't see /var/lib/smbios/smbios2 in my
> system. It will be created when the file is received?
> 3) When the file arrives from the CPU to the BMC, Can I see the
> information in webui? Do I have to create any configuration files in
> entity-manager or phosphor-inventory-manager to do this?
> 4) Besides the CPU and DIMM information, How can I see the
> information of the chassis and board? I think the only way to do this
> is FRU? I mean, this information is kept in any EEPROM as binary in
> the production process of boards. If I think wrong, Is there any way
> to see the information of the chassis or board?
>
> Regards.
>
> Oğuzhan Çağlar
> Software Design Engineer
>
>
>
> Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> Teknopark İstanbul, Kurtköy Pendik İSTANBUL
>
>
> Tel             : +90 (216) 354 72 86
> Faks         : +90 (216) 354 76 77
> Gsm          : +90 (507) 585 10 60
> oguzhan.caglar@pavotek.com.tr
>
> www.pavotek.com.tr<http://www.pavotek.com.tr>
>
>
> Gönderen: Andrei Kartashev <a.kartashev@yadro.com>
> Gönderildi: 17 Ağustos 2022 Çarşamba 12:02:39
> Kime: Oğuzhan ÇAĞLAR; openbmc@lists.ozlabs.org
> Konu: Re: Ynt: Ynt: Ynt: (External) Re: Adding Inventory
>
>
> Warning: This e-mail came from an external source. If you do not
> trust the sender or if there is anything suspicious in the content of
> the e-mail, please inform the IT department.
>
>
>
> On Mon, 2022-08-15 at 12:36 +0000, Oğuzhan ÇAĞLAR wrote:
> >
> > Thank you, Andrei,
> >
> > I successfully built it now. Why do I get this error?
>
> cpuinfo is additional daemon, that actually do nothing with smbios,
> but
> it can get some CPU-related information by using PECI interface. For
> about couple of years PECI wasn't supported by upstream OpenBMC, the
> implementation was only in Intel's fork.
> I don't know actual situation, but I guess you just miss some
> libraries
> for PECI support.
> Anyway, you don't need this at this stage.
>
> > In addition, I guess I have to dive into BIOS to get information
> > about CPU and DIMM. Is it right?
>
> Yes, smbiosmdrv2 daemon reads SMBIOS information from the file
> /var/lib/smbios/smbios2 and you have to somehow deliver it to the BMC
> filesystem.
>
> > Is there any example to do that?
>
> Not sure. I think I saw somewhere in the Internet example of
> delivering
> it using phosphor-ipmi-blobs.
>
> > What exactly do the smbios-mdr daemon?
> >
>
> Well, it just parse SMBIOS tables from binary file and expose
> extracted
> information to dbus for other daemons use.
>
> > Oğuzhan Çağlar
> > Yazılım Mühendisi
> >
> >
> >
> > Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> > Teknopark İstanbul, Kurtköy Pendik İSTANBUL
> >
> >
> > Tel             : +90 (216) 354 72 86
> > Faks         : +90 (216) 354 76 77
> > Gsm          : +90 (507) 585 10 60
> > oguzhan.caglar@pavotek.com.tr
> >
> > www.pavotek.com.tr<http://www.pavotek.com.tr>
> >
> >
> > Gönderen: Andrei Kartashev <a.kartashev@yadro.com>
> > Gönderildi: 15 Ağustos 2022 Pazartesi 13:23:33
> > Kime: Oğuzhan ÇAĞLAR; openbmc@lists.ozlabs.org
> > Konu: Re: Ynt: Ynt: (External) Re: Adding Inventory
> >
> >
> > Warning: This e-mail came from an external source. If you do not
> > trust the sender or if there is anything suspicious in the content
> > of
> > the e-mail, please inform the IT department.
> >
> >
> >
> > As I assumed, it is PCUInfo issue:
> >
> > |
> > /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/wo
> > rk
> > /a
> > rm1176jzs-openbmc-linux-gnueabi/smbios-
> > mdr/1.0+gitAUTOINC+e4ea37716d-
> > r1/git/src/cpuinfo_main.cpp:407:14: error: 'icxd' was not declared
> > in
> > this scope; did you mean 'icx'?
> > |   407 |         case icxd:
> > |       |              ^~~~
> > |       |              icx
> > |
> > /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/wo
> > rk
> > /a
> > rm1176jzs-openbmc-linux-gnueabi/smbios-
> > mdr/1.0+gitAUTOINC+e4ea37716d-
> > r1/git/src/cpuinfo_main.cpp:408:14: error: 'spr' was not declared
> > in
> > this scope
> > |   408 |         case spr:
> > |       |              ^~~
> >
> >
> > Turn it off in you bbappend with `PACKAGECONFIG:remove = "
> > cpuinfo"`
> >
> >
> >
> > On Mon, 2022-08-15 at 07:25 +0000, Oğuzhan ÇAĞLAR wrote:
> > >
> > > I'm sharing with you that my yocto errors are related to smbios-
> > > mdr in the .txt file.
> > >
> > > I don't understand, How can the CPU information match with
> > > entity-
> > > manager configuration files? I saw your comment in openbmc list
> > > about
> > > PCIe. It probes only with xyz.openbmc_project.FruDevice.
> > >
> > >
> > > Oğuzhan Çağlar
> > > Software Design Engineer
> > >
> > >
> > >
> > > Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> > > Teknopark İstanbul, Kurtköy Pendik İSTANBUL
> > >
> > >
> > > Tel             : +90 (216) 354 72 86
> > > Faks         : +90 (216) 354 76 77
> > > Gsm          : +90 (507) 585 10 60
> > > oguzhan.caglar@pavotek.com.tr
> > >
> > > www.pavotek.com.tr<http://www.pavotek.com.tr>
> > >
> > >
> > > Gönderen: Andrei Kartashev <a.kartashev@yadro.com>
> > > Gönderildi: 12 Ağustos 2022 Cuma 22:14:38
> > > Kime: Oğuzhan ÇAĞLAR; openbmc@lists.ozlabs.org
> > > Konu: Re: Ynt: (External) Re: Adding Inventory
> > >
> > >
> > > Warning: This e-mail came from an external source. If you do not
> > > trust the sender or if there is anything suspicious in the
> > > content
> > > of
> > > the e-mail, please inform the IT department.
> > >
> > >
> > >
> > > I have no idea on what do you mean saying "added the CPU and DIMM
> > > configuration files within the .yaml files", but I guess you are
> > > trying
> > > to hardcode this information, which I believe not what ou
> > > actually
> > > expect to get.
> > > You probably should learn how the OpenBMC works inside. You can
> > > use
> > > busctl tool for that.
> > >
> > > Regarding compilation error of smbios-mdr daemon, I can say
> > > nothing
> > > without knowing the issue. There should not be any special
> > > configuration files for this smbios-mdr recipe but probably you
> > > trying
> > > to build CPUInfo part of the recipe without having PECI library.
> > > You
> > > likely should disable cpuinfo app.
> > >
> > > On Fri, 2022-08-12 at 06:50 +0000, Oğuzhan ÇAĞLAR wrote:
> > > > Hi Andrei,
> > > >
> > > > Thank you for your information. I have already added the CPU
> > > > and
> > > > DIMM
> > > > configuration files within the .yaml files. When I added these
> > > > files(related to the path:
> > > > xyz.openbmc_project.Inventory.Item.Cpu
> > > > and xyz.openbmc_project.Inventory.Item.Dimm), I see the CPU and
> > > > DIMM
> > > > entries over WebUI. However, In this way, I add the properties
> > > > such
> > > > as (PartNumber, SerialNumber, etc.) on my own. I have already
> > > > generated a .bin file that has FRU information (chassis, board
> > > > etc.)
> > > > and I included this in BMC's image file. In addition, I see the
> > > > properties related to Chassis, Board on WebUI.
> > > >
> > > > I have already checked the smbios-mdr daemon in openbmc.
> > > > However,
> > > > when I include this daemon in my yocto image, the bitbake shows
> > > > some
> > > > errors that are related to smbios-mdr's .cpp files. I guess I
> > > > have
> > > > to
> > > > create some configuration files before doing it. Is it wrong?
> > > > What
> > > > should I do?
> > > >
> > > > I guess I have to need some code in BIOS. Is there any example
> > > > to
> > > > do
> > > > this? I don't know where I should start.
> > > >
> > > > Thank you.
> > > >
> > > > Oğuzhan Çağlar
> > > > Software Design Engineer
> > > >
> > > >
> > > >
> > > > Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> > > > Teknopark İstanbul, Kurtköy Pendik İSTANBUL
> > > >
> > > >
> > > > Tel             : +90 (216) 354 72 86
> > > > Faks         : +90 (216) 354 76 77
> > > > Gsm          : +90 (507) 585 10 60
> > > > oguzhan.caglar@pavotek.com.tr
> > > >
> > > > www.pavotek.com.tr<http://www.pavotek.com.tr>
> > > >
> > > >
> > > > Gönderen: Andrei Kartashev <a.kartashev@yadro.com>
> > > > Gönderildi: 11 Ağustos 2022 Perşembe 22:28:16
> > > > Kime: Oğuzhan ÇAĞLAR; openbmc@lists.ozlabs.org
> > > > Konu: (External) Re: Adding Inventory
> > > >
> > > >
> > > > Warning: This e-mail came from an external source. If you do
> > > > not
> > > > trust the sender or if there is anything suspicious in the
> > > > content
> > > > of
> > > > the e-mail, please inform the IT department.
> > > >
> > > >
> > > >
> > > > Hello Oguzhan,
> > > >
> > > > This is a very common question for newcomers, I believe is was
> > > > already
> > > > answered somewhere in the list.
> > > > BMC out of the box don't have any knowledge on host's equipment
> > > > (CPU,
> > > > DIMM, Drive, AIC, etc) - it is up to you to deliver this
> > > > information
> > > > from host to BMC. As for now the most common way to feed BMC
> > > > the
> > > > information regarding CPU and DIMM is to transfer smbios tables
> > > > via
> > > > ipmi. You can implement any other mechanism but any way, you
> > > > need
> > > > to
> > > > have some code in your BIOS.
> > > >
> > > > As soon as you have the CPU/DIMM information on BMC it can be
> > > > shown
> > > > in
> > > > bmcweb by implementing corresponding dbus interfaces
> > > > (xyz.openbmc_project.Inventory.Item.Cpu and
> > > > xyz.openbmc_project.Inventory.Item.Dimm). smbiosmdrv2 daemon do
> > > > this,
> > > > but you also can add EntityManager configuration files for this
> > > > or
> > > > write your own daemon to expose the interfaces.
> > > >
> > > > On Thu, 2022-08-04 at 08:07 +0000, Oğuzhan ÇAĞLAR wrote:
> > > > > Hello,
> > > > >
> > > > > I'm working on openbmc for ast2500 bmc. I want to add
> > > > > inventory
> > > > > such
> > > > > as CPU and DIMM etc. I added the chassis from .json file but
> > > > > I
> > > > > couldn't add the CPU and DIMM. I know this is to related with
> > > > > entity-
> > > > > manager. How can I add these inventory on WEBUI? Can you give
> > > > > some
> > > > > information about this issue?
> > > > >
> > > > > Regards.
> > > > >
> > > > > Oğuzhan Çağlar
> > > > > Software Design Engineer
> > > > >
> > > > >
> > > > >
> > > > > Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> > > > > Teknopark İstanbul, Kurtköy Pendik İSTANBUL
> > > > >
> > > > >
> > > > > Tel             : +90 (216) 354 72 86
> > > > > Faks         : +90 (216) 354 76 77
> > > > > Gsm          : +90 (507) 585 10 60
> > > > > oguzhan.caglar@pavotek.com.tr
> > > > >
> > > > > www.pavotek.com.tr<http://www.pavotek.com.tr>
> > > > >
> > > > >
> > > >
> > > > --
> > > > Best regards,
> > > > Andrei Kartashev,
> > > > Lead BMC Developer
> > > >
> > >
> > > --
> > > Best regards,
> > > Andrei Kartashev,
> > > Lead BMC Developer
> > >
> >
> > --
> > Best regards,
> > Andrei Kartashev,
> > Lead BMC Developer
> >
>
> --
> Best regards,
> Andrei Kartashev,
> Lead BMC Developer
>

--
Best regards,
Andrei Kartashev,
Lead BMC Developer


[-- Attachment #1.2: Type: text/html, Size: 26824 bytes --]

[-- Attachment #2: error.txt --]
[-- Type: text/plain, Size: 5777 bytes --]

ERROR: intel-ipmi-oem-0.1+gitAUTOINC+6346e98cd5-r0 do_configure: ExecutionError('/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/intel-ipmi-oem/0.1+gitAUTOINC+6346e98cd5-r0/temp/run.do_configure.22661', 1, None, None)
ERROR: Logfile of failure stored in: /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/intel-ipmi-oem/0.1+gitAUTOINC+6346e98cd5-r0/temp/log.do_configure.22661
Log data follows:
| DEBUG: Executing python function extend_recipe_sysroot
| NOTE: Direct dependencies are ['/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/meta/recipes-devtools/cmake/cmake-native_3.22.3.bb:do_populate_sysroot', '/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/meta/recipes-support/boost/boost_1.78.0.bb:do_populate_sysroot', 'virtual:native:/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/meta/recipes-devtools/pseudo/pseudo_git.bb:do_populate_sysroot', '/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/meta-phosphor/recipes-phosphor/logging/phosphor-logging_git.bb:do_populate_sysroot', '/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/meta-phosphor/recipes-phosphor/ipmi/phosphor-ipmi-host_git.bb:do_populate_sysroot', '/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/meta/recipes-devtools/gcc/gcc-runtime_11.2.bb:do_populate_sysroot', '/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/meta/recipes-core/systemd/systemd_250.4.bb:do_populate_sysroot', 'virtual:native:/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/meta/recipes-devtools/patch/patch_2.7.6.bb:do_populate_sysroot', 'virtual:native:/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/meta/recipes-devtools/ninja/ninja_1.10.2.bb:do_populate_sysroot', '/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/meta/recipes-devtools/quilt/quilt-native_0.67.bb:do_populate_sysroot', '/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/meta-openembedded/meta-oe/recipes-support/libgpiod/libgpiod_1.6.3.bb:do_populate_sysroot', '/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/meta/recipes-core/glibc/glibc_2.35.bb:do_populate_sysroot', '/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/meta-intel-openbmc/meta-common/recipes-phosphor/dbus/intel-dbus-interfaces_git.bb:do_populate_sysroot', '/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/meta/recipes-devtools/gcc/gcc-cross_11.2.bb:do_populate_sysroot']
| NOTE: Installed into sysroot: []
| NOTE: Skipping as already exists in sysroot: ['cmake-native', 'boost', 'pseudo-native', 'phosphor-logging', 'phosphor-ipmi-host', 'gcc-runtime', 'systemd', 'patch-native', 'ninja-native', 'quilt-native', 'libgpiod', 'glibc', 'intel-dbus-interfaces', 'gcc-cross-arm', 'zstd-native', 'curl-native', 'zlib-native', 'xz-native', 'ncurses-native', 'bzip2-native', 'icu', 'python3', 'zlib', 'bzip2', 'libmpc-native', 'linux-libc-headers', 'gnu-config-native', 'flex-native', 'texinfo-dummy-native', 'libtool-native', 'gmp-native', 'mpfr-native', 'binutils-cross-arm', 'phosphor-dbus-interfaces', 'shadow-sysroot', 'phosphor-mapper', 'shadow-native', 'shadow', 'base-passwd', 'sdeventplus', 'base-files', 'sdbusplus', 'nlohmann-json', 'phosphor-state-manager', 'libgcc', 'kmod', 'libseccomp', 'libpam', 'zstd', 'bash-completion', 'libcap', 'util-linux', 'opkg-utils', 'attr-native', 're2c-native', 'packagegroup-obmc-yaml-providers', 'libcereal', 'openssl-native', 'gettext-minimal-native', 'autoconf-archive', 'sqlite3', 'ncurses', 'xz', 'libtirpc', 'util-linux-libuuid', 'readline', 'libxcrypt', 'openssl', 'libnsl2', 'gdbm', 'libffi', 'm4-native', 'libtinyxml2', 'function2', 'stdplus', 'cli11', 'cracklib', 'flex', 'libcap-ng', 'phosphor-led-manager-yaml-provider', 'phosphor-software-manager-yaml-provider', 'cryptodev', 'liburing', 'span-lite', 'fmt', 'linux-aspeed']
| DEBUG: Python function extend_recipe_sysroot finished
| DEBUG: Executing shell function do_configure
| -- The CXX compiler identification is GNU 11.2.0
| -- Detecting CXX compiler ABI info
| -- Detecting CXX compiler ABI info - done
| -- Check for working CXX compiler: /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/intel-ipmi-oem/0.1+gitAUTOINC+6346e98cd5-r0/recipe-sysroot-native/usr/bin/arm-openbmc-linux-gnueabi/arm-openbmc-linux-gnueabi-g++ - skipped
| -- Detecting CXX compile features
| -- Detecting CXX compile features - done
| CMake Error at /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/intel-ipmi-oem/0.1+gitAUTOINC+6346e98cd5-r0/recipe-sysroot-native/usr/share/cmake-3.22/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
|   Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
| Call Stack (most recent call first):
|   /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/intel-ipmi-oem/0.1+gitAUTOINC+6346e98cd5-r0/recipe-sysroot-native/usr/share/cmake-3.22/Modules/FindPackageHandleStandardArgs.cmake:594 (_FPHSA_FAILURE_MESSAGE)
|   /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/intel-ipmi-oem/0.1+gitAUTOINC+6346e98cd5-r0/recipe-sysroot-native/usr/share/cmake-3.22/Modules/FindPkgConfig.cmake:99 (find_package_handle_standard_args)
|   CMakeLists.txt:61 (find_package)
| 
| 
| -- Configuring incomplete, errors occurred!
| See also "/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/work/arm1176jzs-openbmc-linux-gnueabi/intel-ipmi-oem/0.1+gitAUTOINC+6346e98cd5-r0/build/CMakeFiles/CMakeOutput.log".
| WARNING: exit code 1 from a shell command.
ERROR: Task (/home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/meta-intel-openbmc/meta-common/recipes-intel/ipmi/intel-ipmi-oem_git.bb:do_configure) failed with exit code '1'

Ynt: Ynt: Ynt: Ynt: Ynt: (External) Re: Adding Inventory

[Oğuzhan ÇAĞLAR]

[-- Attachment #1: Type: text/plain, Size: 14744 bytes --]

Hello again,


I haven't received any response since I sent the e-mail to you. I'm waiting for your answer. I successfully built the "Intel-oem-ipmi" but I'm still confused about the first question that is related to getting SMBIOS info.



Thank you.


Saygılarımla / Best Regards,



Oğuzhan Çağlar

Yazılım Tasarım Mühendisi












Pavo Tasarım Üretim Elektronik Tic. A.Ş.

Sanayi Mah. Teknopark İstanbul Yerleşkesi Ar-Ge Binaları 4C Kat:1-2

Pendik / İstanbul / TÜRKİYE


PɅVOTEK<http://pavotek.com.tr/>




Tel           : +90 (216) 354 72 86


Faks        : +90 (216) 354 76 77





www.pavotek.com.tr<http://www.pavotek.com.tr/>

________________________________
Gönderen: Oğuzhan ÇAĞLAR
Gönderildi: 18 Ağustos 2022 Perşembe 14:21:17
Kime: Andrei Kartashev; Brad Bishop
Bilgi: <openbmc@lists.ozlabs.org>
Konu: Ynt: Ynt: Ynt: Ynt: Ynt: (External) Re: Adding Inventory


Thanks,


1) I'm confused about this. I didn't connect any BMC's i2c buses to the CPU. Is that any problem for me? I mean, I have to BMC's i2c buses to CPU? Because these pins were not connected to any CPU's pins. It is empty. May it be my problem? I mean, If I connect these buses to CPU, Can I get the information?


2) When I build the "intel-oem-ipmi", It shows me an error. I guess The "intel-oem-ipmi" is required for the x86 CPU. I start to think that the openbmc doesn't support this. I attached the error file.


Regards.


Oğuzhan Çağlar

Software Design Engineer




[https://posta.pavotek.com.tr/owa/]








[https://posta.pavotek.com.tr/owa/]


Pavo Tasarım Üretim Elektronik Tic. A.Ş.

Teknopark İstanbul, Kurtköy Pendik İSTANBUL




       [https://posta.pavotek.com.tr/owa/] <http://pavotek.com.tr/>


Tel             : +90 (216) 354 72 86


Faks         : +90 (216) 354 76 77


Gsm          : +90 (507) 585 10 60


oguzhan.caglar@pavotek.com.tr<mailto:oguzhan.caglar@pavotek.com.tr>





www.pavotek.com.tr<http://www.pavotek.com.tr/>




________________________________
Gönderen: Andrei Kartashev <a.kartashev@yadro.com>
Gönderildi: 18 Ağustos 2022 Perşembe 11:38:44
Kime: Oğuzhan ÇAĞLAR; Brad Bishop
Bilgi: <openbmc@lists.ozlabs.org>
Konu: Re: Ynt: Ynt: Ynt: Ynt: (External) Re: Adding Inventory


Warning: This e-mail came from an external source. If you do not trust the sender or if there is anything suspicious in the content of the e-mail, please inform the IT department.



1) It depends on your board, you should know better. If you don't know,
then it is likely KCS.
2) Yes
3) Yes, you don't need to have to create any additional configs
4) Yes, the common way is to program VPD/FRU to eeprom during
production stage. But this can vary depending on your board design and
manufacturing workflow.

Brad, I feel this questions rises each time when newcomers start
porting OBMC on their new board. Seems like we should have this
information in somewhere beginners guide.

On Thu, 2022-08-18 at 07:31 +0000, Oğuzhan ÇAĞLAR wrote:
> «Внимание! Данное письмо от внешнего адресата!»
>
> Thank you, It is too helpful!
>
> 1) What is the interface over which the Intel x86 CPU sends data to
> the BMC? KCS or something?
> 2) I see /var/lib/smbios but don't see /var/lib/smbios/smbios2 in my
> system. It will be created when the file is received?
> 3) When the file arrives from the CPU to the BMC, Can I see the
> information in webui? Do I have to create any configuration files in
> entity-manager or phosphor-inventory-manager to do this?
> 4) Besides the CPU and DIMM information, How can I see the
> information of the chassis and board? I think the only way to do this
> is FRU? I mean, this information is kept in any EEPROM as binary in
> the production process of boards. If I think wrong, Is there any way
> to see the information of the chassis or board?
>
> Regards.
>
> Oğuzhan Çağlar
> Software Design Engineer
>
>
>
> Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> Teknopark İstanbul, Kurtköy Pendik İSTANBUL
>
>
> Tel             : +90 (216) 354 72 86
> Faks         : +90 (216) 354 76 77
> Gsm          : +90 (507) 585 10 60
> oguzhan.caglar@pavotek.com.tr
>
> www.pavotek.com.tr<http://www.pavotek.com.tr>
>
>
> Gönderen: Andrei Kartashev <a.kartashev@yadro.com>
> Gönderildi: 17 Ağustos 2022 Çarşamba 12:02:39
> Kime: Oğuzhan ÇAĞLAR; openbmc@lists.ozlabs.org
> Konu: Re: Ynt: Ynt: Ynt: (External) Re: Adding Inventory
>
>
> Warning: This e-mail came from an external source. If you do not
> trust the sender or if there is anything suspicious in the content of
> the e-mail, please inform the IT department.
>
>
>
> On Mon, 2022-08-15 at 12:36 +0000, Oğuzhan ÇAĞLAR wrote:
> >
> > Thank you, Andrei,
> >
> > I successfully built it now. Why do I get this error?
>
> cpuinfo is additional daemon, that actually do nothing with smbios,
> but
> it can get some CPU-related information by using PECI interface. For
> about couple of years PECI wasn't supported by upstream OpenBMC, the
> implementation was only in Intel's fork.
> I don't know actual situation, but I guess you just miss some
> libraries
> for PECI support.
> Anyway, you don't need this at this stage.
>
> > In addition, I guess I have to dive into BIOS to get information
> > about CPU and DIMM. Is it right?
>
> Yes, smbiosmdrv2 daemon reads SMBIOS information from the file
> /var/lib/smbios/smbios2 and you have to somehow deliver it to the BMC
> filesystem.
>
> > Is there any example to do that?
>
> Not sure. I think I saw somewhere in the Internet example of
> delivering
> it using phosphor-ipmi-blobs.
>
> > What exactly do the smbios-mdr daemon?
> >
>
> Well, it just parse SMBIOS tables from binary file and expose
> extracted
> information to dbus for other daemons use.
>
> > Oğuzhan Çağlar
> > Yazılım Mühendisi
> >
> >
> >
> > Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> > Teknopark İstanbul, Kurtköy Pendik İSTANBUL
> >
> >
> > Tel             : +90 (216) 354 72 86
> > Faks         : +90 (216) 354 76 77
> > Gsm          : +90 (507) 585 10 60
> > oguzhan.caglar@pavotek.com.tr
> >
> > www.pavotek.com.tr<http://www.pavotek.com.tr>
> >
> >
> > Gönderen: Andrei Kartashev <a.kartashev@yadro.com>
> > Gönderildi: 15 Ağustos 2022 Pazartesi 13:23:33
> > Kime: Oğuzhan ÇAĞLAR; openbmc@lists.ozlabs.org
> > Konu: Re: Ynt: Ynt: (External) Re: Adding Inventory
> >
> >
> > Warning: This e-mail came from an external source. If you do not
> > trust the sender or if there is anything suspicious in the content
> > of
> > the e-mail, please inform the IT department.
> >
> >
> >
> > As I assumed, it is PCUInfo issue:
> >
> > |
> > /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/wo
> > rk
> > /a
> > rm1176jzs-openbmc-linux-gnueabi/smbios-
> > mdr/1.0+gitAUTOINC+e4ea37716d-
> > r1/git/src/cpuinfo_main.cpp:407:14: error: 'icxd' was not declared
> > in
> > this scope; did you mean 'icx'?
> > |   407 |         case icxd:
> > |       |              ^~~~
> > |       |              icx
> > |
> > /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/wo
> > rk
> > /a
> > rm1176jzs-openbmc-linux-gnueabi/smbios-
> > mdr/1.0+gitAUTOINC+e4ea37716d-
> > r1/git/src/cpuinfo_main.cpp:408:14: error: 'spr' was not declared
> > in
> > this scope
> > |   408 |         case spr:
> > |       |              ^~~
> >
> >
> > Turn it off in you bbappend with `PACKAGECONFIG:remove = "
> > cpuinfo"`
> >
> >
> >
> > On Mon, 2022-08-15 at 07:25 +0000, Oğuzhan ÇAĞLAR wrote:
> > >
> > > I'm sharing with you that my yocto errors are related to smbios-
> > > mdr in the .txt file.
> > >
> > > I don't understand, How can the CPU information match with
> > > entity-
> > > manager configuration files? I saw your comment in openbmc list
> > > about
> > > PCIe. It probes only with xyz.openbmc_project.FruDevice.
> > >
> > >
> > > Oğuzhan Çağlar
> > > Software Design Engineer
> > >
> > >
> > >
> > > Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> > > Teknopark İstanbul, Kurtköy Pendik İSTANBUL
> > >
> > >
> > > Tel             : +90 (216) 354 72 86
> > > Faks         : +90 (216) 354 76 77
> > > Gsm          : +90 (507) 585 10 60
> > > oguzhan.caglar@pavotek.com.tr
> > >
> > > www.pavotek.com.tr<http://www.pavotek.com.tr>
> > >
> > >
> > > Gönderen: Andrei Kartashev <a.kartashev@yadro.com>
> > > Gönderildi: 12 Ağustos 2022 Cuma 22:14:38
> > > Kime: Oğuzhan ÇAĞLAR; openbmc@lists.ozlabs.org
> > > Konu: Re: Ynt: (External) Re: Adding Inventory
> > >
> > >
> > > Warning: This e-mail came from an external source. If you do not
> > > trust the sender or if there is anything suspicious in the
> > > content
> > > of
> > > the e-mail, please inform the IT department.
> > >
> > >
> > >
> > > I have no idea on what do you mean saying "added the CPU and DIMM
> > > configuration files within the .yaml files", but I guess you are
> > > trying
> > > to hardcode this information, which I believe not what ou
> > > actually
> > > expect to get.
> > > You probably should learn how the OpenBMC works inside. You can
> > > use
> > > busctl tool for that.
> > >
> > > Regarding compilation error of smbios-mdr daemon, I can say
> > > nothing
> > > without knowing the issue. There should not be any special
> > > configuration files for this smbios-mdr recipe but probably you
> > > trying
> > > to build CPUInfo part of the recipe without having PECI library.
> > > You
> > > likely should disable cpuinfo app.
> > >
> > > On Fri, 2022-08-12 at 06:50 +0000, Oğuzhan ÇAĞLAR wrote:
> > > > Hi Andrei,
> > > >
> > > > Thank you for your information. I have already added the CPU
> > > > and
> > > > DIMM
> > > > configuration files within the .yaml files. When I added these
> > > > files(related to the path:
> > > > xyz.openbmc_project.Inventory.Item.Cpu
> > > > and xyz.openbmc_project.Inventory.Item.Dimm), I see the CPU and
> > > > DIMM
> > > > entries over WebUI. However, In this way, I add the properties
> > > > such
> > > > as (PartNumber, SerialNumber, etc.) on my own. I have already
> > > > generated a .bin file that has FRU information (chassis, board
> > > > etc.)
> > > > and I included this in BMC's image file. In addition, I see the
> > > > properties related to Chassis, Board on WebUI.
> > > >
> > > > I have already checked the smbios-mdr daemon in openbmc.
> > > > However,
> > > > when I include this daemon in my yocto image, the bitbake shows
> > > > some
> > > > errors that are related to smbios-mdr's .cpp files. I guess I
> > > > have
> > > > to
> > > > create some configuration files before doing it. Is it wrong?
> > > > What
> > > > should I do?
> > > >
> > > > I guess I have to need some code in BIOS. Is there any example
> > > > to
> > > > do
> > > > this? I don't know where I should start.
> > > >
> > > > Thank you.
> > > >
> > > > Oğuzhan Çağlar
> > > > Software Design Engineer
> > > >
> > > >
> > > >
> > > > Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> > > > Teknopark İstanbul, Kurtköy Pendik İSTANBUL
> > > >
> > > >
> > > > Tel             : +90 (216) 354 72 86
> > > > Faks         : +90 (216) 354 76 77
> > > > Gsm          : +90 (507) 585 10 60
> > > > oguzhan.caglar@pavotek.com.tr
> > > >
> > > > www.pavotek.com.tr<http://www.pavotek.com.tr>
> > > >
> > > >
> > > > Gönderen: Andrei Kartashev <a.kartashev@yadro.com>
> > > > Gönderildi: 11 Ağustos 2022 Perşembe 22:28:16
> > > > Kime: Oğuzhan ÇAĞLAR; openbmc@lists.ozlabs.org
> > > > Konu: (External) Re: Adding Inventory
> > > >
> > > >
> > > > Warning: This e-mail came from an external source. If you do
> > > > not
> > > > trust the sender or if there is anything suspicious in the
> > > > content
> > > > of
> > > > the e-mail, please inform the IT department.
> > > >
> > > >
> > > >
> > > > Hello Oguzhan,
> > > >
> > > > This is a very common question for newcomers, I believe is was
> > > > already
> > > > answered somewhere in the list.
> > > > BMC out of the box don't have any knowledge on host's equipment
> > > > (CPU,
> > > > DIMM, Drive, AIC, etc) - it is up to you to deliver this
> > > > information
> > > > from host to BMC. As for now the most common way to feed BMC
> > > > the
> > > > information regarding CPU and DIMM is to transfer smbios tables
> > > > via
> > > > ipmi. You can implement any other mechanism but any way, you
> > > > need
> > > > to
> > > > have some code in your BIOS.
> > > >
> > > > As soon as you have the CPU/DIMM information on BMC it can be
> > > > shown
> > > > in
> > > > bmcweb by implementing corresponding dbus interfaces
> > > > (xyz.openbmc_project.Inventory.Item.Cpu and
> > > > xyz.openbmc_project.Inventory.Item.Dimm). smbiosmdrv2 daemon do
> > > > this,
> > > > but you also can add EntityManager configuration files for this
> > > > or
> > > > write your own daemon to expose the interfaces.
> > > >
> > > > On Thu, 2022-08-04 at 08:07 +0000, Oğuzhan ÇAĞLAR wrote:
> > > > > Hello,
> > > > >
> > > > > I'm working on openbmc for ast2500 bmc. I want to add
> > > > > inventory
> > > > > such
> > > > > as CPU and DIMM etc. I added the chassis from .json file but
> > > > > I
> > > > > couldn't add the CPU and DIMM. I know this is to related with
> > > > > entity-
> > > > > manager. How can I add these inventory on WEBUI? Can you give
> > > > > some
> > > > > information about this issue?
> > > > >
> > > > > Regards.
> > > > >
> > > > > Oğuzhan Çağlar
> > > > > Software Design Engineer
> > > > >
> > > > >
> > > > >
> > > > > Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> > > > > Teknopark İstanbul, Kurtköy Pendik İSTANBUL
> > > > >
> > > > >
> > > > > Tel             : +90 (216) 354 72 86
> > > > > Faks         : +90 (216) 354 76 77
> > > > > Gsm          : +90 (507) 585 10 60
> > > > > oguzhan.caglar@pavotek.com.tr
> > > > >
> > > > > www.pavotek.com.tr<http://www.pavotek.com.tr>
> > > > >
> > > > >
> > > >
> > > > --
> > > > Best regards,
> > > > Andrei Kartashev,
> > > > Lead BMC Developer
> > > >
> > >
> > > --
> > > Best regards,
> > > Andrei Kartashev,
> > > Lead BMC Developer
> > >
> >
> > --
> > Best regards,
> > Andrei Kartashev,
> > Lead BMC Developer
> >
>
> --
> Best regards,
> Andrei Kartashev,
> Lead BMC Developer
>

--
Best regards,
Andrei Kartashev,
Lead BMC Developer


[-- Attachment #2: Type: text/html, Size: 36248 bytes --]

Ynt: Ynt: Ynt: Ynt: Ynt: (External) Re: Adding Inventory

[Oğuzhan ÇAĞLAR]

[-- Attachment #1: Type: text/plain, Size: 16032 bytes --]

Hello,


I successfully got the SMBIOS table over the BT interface by using the smbios_transfer.go command that LinuxBoot provides. I want to ask some things about BIOS:


1) I see an option whose name is "BMC Network Configuration" in BIOS but I can't enter it. Do I have to do any configuration in my BMC build system? How can I access it?


2) I get the SMBIOS table from HOST OS but this process depends on OS. How can I get this information when BIOS is booting? I mean Is there any mechanism that BIOS sends the SMBIOS table to BMC when it is booting?


Thank you.


Saygılarımla / Best Regards,



Oğuzhan Çağlar

Yazılım Tasarım Mühendisi












Pavo Tasarım Üretim Elektronik Tic. A.Ş.

Sanayi Mah. Teknopark İstanbul Yerleşkesi Ar-Ge Binaları 4C Kat:1-2

Pendik / İstanbul / TÜRKİYE


PɅVOTEK<http://pavotek.com.tr/>




Tel           : +90 (216) 354 72 86


Faks        : +90 (216) 354 76 77





www.pavotek.com.tr<http://www.pavotek.com.tr/>

________________________________
Gönderen: Oğuzhan ÇAĞLAR
Gönderildi: 1 Eylül 2022 Perşembe 09:25:29
Kime: Andrei Kartashev; Brad Bishop
Bilgi: <openbmc@lists.ozlabs.org>
Konu: Ynt: Ynt: Ynt: Ynt: Ynt: (External) Re: Adding Inventory


Hello again,


I haven't received any response since I sent the e-mail to you. I'm waiting for your answer. I successfully built the "Intel-oem-ipmi" but I'm still confused about the first question that is related to getting SMBIOS info.



Thank you.


Saygılarımla / Best Regards,



Oğuzhan Çağlar

Yazılım Tasarım Mühendisi












Pavo Tasarım Üretim Elektronik Tic. A.Ş.

Sanayi Mah. Teknopark İstanbul Yerleşkesi Ar-Ge Binaları 4C Kat:1-2

Pendik / İstanbul / TÜRKİYE


PɅVOTEK<http://pavotek.com.tr/>




Tel           : +90 (216) 354 72 86


Faks        : +90 (216) 354 76 77





www.pavotek.com.tr<http://www.pavotek.com.tr/>

________________________________
Gönderen: Oğuzhan ÇAĞLAR
Gönderildi: 18 Ağustos 2022 Perşembe 14:21:17
Kime: Andrei Kartashev; Brad Bishop
Bilgi: <openbmc@lists.ozlabs.org>
Konu: Ynt: Ynt: Ynt: Ynt: Ynt: (External) Re: Adding Inventory


Thanks,


1) I'm confused about this. I didn't connect any BMC's i2c buses to the CPU. Is that any problem for me? I mean, I have to BMC's i2c buses to CPU? Because these pins were not connected to any CPU's pins. It is empty. May it be my problem? I mean, If I connect these buses to CPU, Can I get the information?


2) When I build the "intel-oem-ipmi", It shows me an error. I guess The "intel-oem-ipmi" is required for the x86 CPU. I start to think that the openbmc doesn't support this. I attached the error file.


Regards.


Oğuzhan Çağlar

Software Design Engineer




[https://posta.pavotek.com.tr/owa/]








[https://posta.pavotek.com.tr/owa/]


Pavo Tasarım Üretim Elektronik Tic. A.Ş.

Teknopark İstanbul, Kurtköy Pendik İSTANBUL




       [https://posta.pavotek.com.tr/owa/] <http://pavotek.com.tr/>


Tel             : +90 (216) 354 72 86


Faks         : +90 (216) 354 76 77


Gsm          : +90 (507) 585 10 60


oguzhan.caglar@pavotek.com.tr<mailto:oguzhan.caglar@pavotek.com.tr>





www.pavotek.com.tr<http://www.pavotek.com.tr/>




________________________________
Gönderen: Andrei Kartashev <a.kartashev@yadro.com>
Gönderildi: 18 Ağustos 2022 Perşembe 11:38:44
Kime: Oğuzhan ÇAĞLAR; Brad Bishop
Bilgi: <openbmc@lists.ozlabs.org>
Konu: Re: Ynt: Ynt: Ynt: Ynt: (External) Re: Adding Inventory


Warning: This e-mail came from an external source. If you do not trust the sender or if there is anything suspicious in the content of the e-mail, please inform the IT department.



1) It depends on your board, you should know better. If you don't know,
then it is likely KCS.
2) Yes
3) Yes, you don't need to have to create any additional configs
4) Yes, the common way is to program VPD/FRU to eeprom during
production stage. But this can vary depending on your board design and
manufacturing workflow.

Brad, I feel this questions rises each time when newcomers start
porting OBMC on their new board. Seems like we should have this
information in somewhere beginners guide.

On Thu, 2022-08-18 at 07:31 +0000, Oğuzhan ÇAĞLAR wrote:
> «Внимание! Данное письмо от внешнего адресата!»
>
> Thank you, It is too helpful!
>
> 1) What is the interface over which the Intel x86 CPU sends data to
> the BMC? KCS or something?
> 2) I see /var/lib/smbios but don't see /var/lib/smbios/smbios2 in my
> system. It will be created when the file is received?
> 3) When the file arrives from the CPU to the BMC, Can I see the
> information in webui? Do I have to create any configuration files in
> entity-manager or phosphor-inventory-manager to do this?
> 4) Besides the CPU and DIMM information, How can I see the
> information of the chassis and board? I think the only way to do this
> is FRU? I mean, this information is kept in any EEPROM as binary in
> the production process of boards. If I think wrong, Is there any way
> to see the information of the chassis or board?
>
> Regards.
>
> Oğuzhan Çağlar
> Software Design Engineer
>
>
>
> Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> Teknopark İstanbul, Kurtköy Pendik İSTANBUL
>
>
> Tel             : +90 (216) 354 72 86
> Faks         : +90 (216) 354 76 77
> Gsm          : +90 (507) 585 10 60
> oguzhan.caglar@pavotek.com.tr
>
> www.pavotek.com.tr<http://www.pavotek.com.tr>
>
>
> Gönderen: Andrei Kartashev <a.kartashev@yadro.com>
> Gönderildi: 17 Ağustos 2022 Çarşamba 12:02:39
> Kime: Oğuzhan ÇAĞLAR; openbmc@lists.ozlabs.org
> Konu: Re: Ynt: Ynt: Ynt: (External) Re: Adding Inventory
>
>
> Warning: This e-mail came from an external source. If you do not
> trust the sender or if there is anything suspicious in the content of
> the e-mail, please inform the IT department.
>
>
>
> On Mon, 2022-08-15 at 12:36 +0000, Oğuzhan ÇAĞLAR wrote:
> >
> > Thank you, Andrei,
> >
> > I successfully built it now. Why do I get this error?
>
> cpuinfo is additional daemon, that actually do nothing with smbios,
> but
> it can get some CPU-related information by using PECI interface. For
> about couple of years PECI wasn't supported by upstream OpenBMC, the
> implementation was only in Intel's fork.
> I don't know actual situation, but I guess you just miss some
> libraries
> for PECI support.
> Anyway, you don't need this at this stage.
>
> > In addition, I guess I have to dive into BIOS to get information
> > about CPU and DIMM. Is it right?
>
> Yes, smbiosmdrv2 daemon reads SMBIOS information from the file
> /var/lib/smbios/smbios2 and you have to somehow deliver it to the BMC
> filesystem.
>
> > Is there any example to do that?
>
> Not sure. I think I saw somewhere in the Internet example of
> delivering
> it using phosphor-ipmi-blobs.
>
> > What exactly do the smbios-mdr daemon?
> >
>
> Well, it just parse SMBIOS tables from binary file and expose
> extracted
> information to dbus for other daemons use.
>
> > Oğuzhan Çağlar
> > Yazılım Mühendisi
> >
> >
> >
> > Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> > Teknopark İstanbul, Kurtköy Pendik İSTANBUL
> >
> >
> > Tel             : +90 (216) 354 72 86
> > Faks         : +90 (216) 354 76 77
> > Gsm          : +90 (507) 585 10 60
> > oguzhan.caglar@pavotek.com.tr
> >
> > www.pavotek.com.tr<http://www.pavotek.com.tr>
> >
> >
> > Gönderen: Andrei Kartashev <a.kartashev@yadro.com>
> > Gönderildi: 15 Ağustos 2022 Pazartesi 13:23:33
> > Kime: Oğuzhan ÇAĞLAR; openbmc@lists.ozlabs.org
> > Konu: Re: Ynt: Ynt: (External) Re: Adding Inventory
> >
> >
> > Warning: This e-mail came from an external source. If you do not
> > trust the sender or if there is anything suspicious in the content
> > of
> > the e-mail, please inform the IT department.
> >
> >
> >
> > As I assumed, it is PCUInfo issue:
> >
> > |
> > /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/wo
> > rk
> > /a
> > rm1176jzs-openbmc-linux-gnueabi/smbios-
> > mdr/1.0+gitAUTOINC+e4ea37716d-
> > r1/git/src/cpuinfo_main.cpp:407:14: error: 'icxd' was not declared
> > in
> > this scope; did you mean 'icx'?
> > |   407 |         case icxd:
> > |       |              ^~~~
> > |       |              icx
> > |
> > /home/pavo/oguz/pavoopenbmc/aspeedopenbmc/openbmc/build/epca/tmp/wo
> > rk
> > /a
> > rm1176jzs-openbmc-linux-gnueabi/smbios-
> > mdr/1.0+gitAUTOINC+e4ea37716d-
> > r1/git/src/cpuinfo_main.cpp:408:14: error: 'spr' was not declared
> > in
> > this scope
> > |   408 |         case spr:
> > |       |              ^~~
> >
> >
> > Turn it off in you bbappend with `PACKAGECONFIG:remove = "
> > cpuinfo"`
> >
> >
> >
> > On Mon, 2022-08-15 at 07:25 +0000, Oğuzhan ÇAĞLAR wrote:
> > >
> > > I'm sharing with you that my yocto errors are related to smbios-
> > > mdr in the .txt file.
> > >
> > > I don't understand, How can the CPU information match with
> > > entity-
> > > manager configuration files? I saw your comment in openbmc list
> > > about
> > > PCIe. It probes only with xyz.openbmc_project.FruDevice.
> > >
> > >
> > > Oğuzhan Çağlar
> > > Software Design Engineer
> > >
> > >
> > >
> > > Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> > > Teknopark İstanbul, Kurtköy Pendik İSTANBUL
> > >
> > >
> > > Tel             : +90 (216) 354 72 86
> > > Faks         : +90 (216) 354 76 77
> > > Gsm          : +90 (507) 585 10 60
> > > oguzhan.caglar@pavotek.com.tr
> > >
> > > www.pavotek.com.tr<http://www.pavotek.com.tr>
> > >
> > >
> > > Gönderen: Andrei Kartashev <a.kartashev@yadro.com>
> > > Gönderildi: 12 Ağustos 2022 Cuma 22:14:38
> > > Kime: Oğuzhan ÇAĞLAR; openbmc@lists.ozlabs.org
> > > Konu: Re: Ynt: (External) Re: Adding Inventory
> > >
> > >
> > > Warning: This e-mail came from an external source. If you do not
> > > trust the sender or if there is anything suspicious in the
> > > content
> > > of
> > > the e-mail, please inform the IT department.
> > >
> > >
> > >
> > > I have no idea on what do you mean saying "added the CPU and DIMM
> > > configuration files within the .yaml files", but I guess you are
> > > trying
> > > to hardcode this information, which I believe not what ou
> > > actually
> > > expect to get.
> > > You probably should learn how the OpenBMC works inside. You can
> > > use
> > > busctl tool for that.
> > >
> > > Regarding compilation error of smbios-mdr daemon, I can say
> > > nothing
> > > without knowing the issue. There should not be any special
> > > configuration files for this smbios-mdr recipe but probably you
> > > trying
> > > to build CPUInfo part of the recipe without having PECI library.
> > > You
> > > likely should disable cpuinfo app.
> > >
> > > On Fri, 2022-08-12 at 06:50 +0000, Oğuzhan ÇAĞLAR wrote:
> > > > Hi Andrei,
> > > >
> > > > Thank you for your information. I have already added the CPU
> > > > and
> > > > DIMM
> > > > configuration files within the .yaml files. When I added these
> > > > files(related to the path:
> > > > xyz.openbmc_project.Inventory.Item.Cpu
> > > > and xyz.openbmc_project.Inventory.Item.Dimm), I see the CPU and
> > > > DIMM
> > > > entries over WebUI. However, In this way, I add the properties
> > > > such
> > > > as (PartNumber, SerialNumber, etc.) on my own. I have already
> > > > generated a .bin file that has FRU information (chassis, board
> > > > etc.)
> > > > and I included this in BMC's image file. In addition, I see the
> > > > properties related to Chassis, Board on WebUI.
> > > >
> > > > I have already checked the smbios-mdr daemon in openbmc.
> > > > However,
> > > > when I include this daemon in my yocto image, the bitbake shows
> > > > some
> > > > errors that are related to smbios-mdr's .cpp files. I guess I
> > > > have
> > > > to
> > > > create some configuration files before doing it. Is it wrong?
> > > > What
> > > > should I do?
> > > >
> > > > I guess I have to need some code in BIOS. Is there any example
> > > > to
> > > > do
> > > > this? I don't know where I should start.
> > > >
> > > > Thank you.
> > > >
> > > > Oğuzhan Çağlar
> > > > Software Design Engineer
> > > >
> > > >
> > > >
> > > > Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> > > > Teknopark İstanbul, Kurtköy Pendik İSTANBUL
> > > >
> > > >
> > > > Tel             : +90 (216) 354 72 86
> > > > Faks         : +90 (216) 354 76 77
> > > > Gsm          : +90 (507) 585 10 60
> > > > oguzhan.caglar@pavotek.com.tr
> > > >
> > > > www.pavotek.com.tr<http://www.pavotek.com.tr>
> > > >
> > > >
> > > > Gönderen: Andrei Kartashev <a.kartashev@yadro.com>
> > > > Gönderildi: 11 Ağustos 2022 Perşembe 22:28:16
> > > > Kime: Oğuzhan ÇAĞLAR; openbmc@lists.ozlabs.org
> > > > Konu: (External) Re: Adding Inventory
> > > >
> > > >
> > > > Warning: This e-mail came from an external source. If you do
> > > > not
> > > > trust the sender or if there is anything suspicious in the
> > > > content
> > > > of
> > > > the e-mail, please inform the IT department.
> > > >
> > > >
> > > >
> > > > Hello Oguzhan,
> > > >
> > > > This is a very common question for newcomers, I believe is was
> > > > already
> > > > answered somewhere in the list.
> > > > BMC out of the box don't have any knowledge on host's equipment
> > > > (CPU,
> > > > DIMM, Drive, AIC, etc) - it is up to you to deliver this
> > > > information
> > > > from host to BMC. As for now the most common way to feed BMC
> > > > the
> > > > information regarding CPU and DIMM is to transfer smbios tables
> > > > via
> > > > ipmi. You can implement any other mechanism but any way, you
> > > > need
> > > > to
> > > > have some code in your BIOS.
> > > >
> > > > As soon as you have the CPU/DIMM information on BMC it can be
> > > > shown
> > > > in
> > > > bmcweb by implementing corresponding dbus interfaces
> > > > (xyz.openbmc_project.Inventory.Item.Cpu and
> > > > xyz.openbmc_project.Inventory.Item.Dimm). smbiosmdrv2 daemon do
> > > > this,
> > > > but you also can add EntityManager configuration files for this
> > > > or
> > > > write your own daemon to expose the interfaces.
> > > >
> > > > On Thu, 2022-08-04 at 08:07 +0000, Oğuzhan ÇAĞLAR wrote:
> > > > > Hello,
> > > > >
> > > > > I'm working on openbmc for ast2500 bmc. I want to add
> > > > > inventory
> > > > > such
> > > > > as CPU and DIMM etc. I added the chassis from .json file but
> > > > > I
> > > > > couldn't add the CPU and DIMM. I know this is to related with
> > > > > entity-
> > > > > manager. How can I add these inventory on WEBUI? Can you give
> > > > > some
> > > > > information about this issue?
> > > > >
> > > > > Regards.
> > > > >
> > > > > Oğuzhan Çağlar
> > > > > Software Design Engineer
> > > > >
> > > > >
> > > > >
> > > > > Pavo Tasarım Üretim Elektronik Tic. A.Ş.
> > > > > Teknopark İstanbul, Kurtköy Pendik İSTANBUL
> > > > >
> > > > >
> > > > > Tel             : +90 (216) 354 72 86
> > > > > Faks         : +90 (216) 354 76 77
> > > > > Gsm          : +90 (507) 585 10 60
> > > > > oguzhan.caglar@pavotek.com.tr
> > > > >
> > > > > www.pavotek.com.tr<http://www.pavotek.com.tr>
> > > > >
> > > > >
> > > >
> > > > --
> > > > Best regards,
> > > > Andrei Kartashev,
> > > > Lead BMC Developer
> > > >
> > >
> > > --
> > > Best regards,
> > > Andrei Kartashev,
> > > Lead BMC Developer
> > >
> >
> > --
> > Best regards,
> > Andrei Kartashev,
> > Lead BMC Developer
> >
>
> --
> Best regards,
> Andrei Kartashev,
> Lead BMC Developer
>

--
Best regards,
Andrei Kartashev,
Lead BMC Developer


[-- Attachment #2: Type: text/html, Size: 45473 bytes --]