Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / owners-plugin-test / 092f506b45d5e3108902b8f01784eb9ac6bab5b7
commit092f506b45d5e3108902b8f01784eb9ac6bab5b7[log] [tgz]
authorAndrew Jeffery <andrew@aj.id.au>Mon Feb 06 13:00:57 2017 +1030
committerPatrick Williams <patrick@stwcx.xyz>Thu Feb 09 17:32:13 2017 +0000
treefc43eac104df9deca0dadc86ba63e6eb6dc929f9
parent0fbda6cd06a553ad2a4896066002d2eae9cc8e65 [diff]
mboxd: Use escaped unit names for device dependencies

Inspecting the journal showed that the device units that mboxd depends
on were timing out:

    Jan 30 02:48:29 witherspoon systemd[1]: Timed out waiting for device dev-aspeed-lpc-ctrl.device.
    Jan 30 02:48:29 witherspoon systemd[1]: dev-aspeed-lpc-ctrl.device: Job dev-aspeed-lpc-ctrl.device/start failed with result 'timeout'.
    Jan 30 02:48:29 witherspoon systemd[1]: dev-aspeed-mbox.device: Job dev-aspeed-mbox.device/start timed out.
    Jan 30 02:48:29 witherspoon systemd[1]: Timed out waiting for device dev-aspeed-mbox.device.
    Jan 30 02:48:29 witherspoon systemd[1]: dev-aspeed-mbox.device: Job dev-aspeed-mbox.device/start failed with result 'timeout'

As it turns out, systemd wants escaped strings to cope with e.g. paths
with dashes in the filename. Update the Wants/After lines to use the
escaped strings. The escaped values were created running
`systemd-escape`[1] on a Zaius image under QEMU:

    root@zaius:~# systemd-escape -p /dev/aspeed-*
    dev-aspeed\x2dlpc\x2dctrl dev-aspeed\x2dmbox

This leaves us with the happy result of no timeouts:

    # journalctl | grep aspeed
    ...
    Feb 06 02:25:22 zaius systemd[1]: Found device /dev/aspeed-mbox.
    Feb 06 02:25:25 zaius systemd[1]: Found device /dev/aspeed-lpc-ctrl.
    ...

[1] https://www.freedesktop.org/software/systemd/man/systemd-escape.html#

Change-Id: I4770026842757768b20b919125af47ae499d1667
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
1 file changed
tree: fc43eac104df9deca0dadc86ba63e6eb6dc929f9
  1. import-layers/
  2. meta-openbmc-bsp/
  3. meta-openbmc-machines/
  4. meta-phosphor/
  5. bitbake ⇨ import-layers/yocto-poky/bitbake
  6. documentation ⇨ import-layers/yocto-poky/documentation
  7. LICENSE ⇨ import-layers/yocto-poky/LICENSE
  8. meta ⇨ import-layers/yocto-poky/meta
  9. meta-poky ⇨ import-layers/yocto-poky/meta-poky
  10. meta-selftest ⇨ import-layers/yocto-poky/meta-selftest
  11. meta-skeleton ⇨ import-layers/yocto-poky/meta-skeleton
  12. meta-yocto-bsp ⇨ import-layers/yocto-poky/meta-yocto-bsp
  13. oe-init-build-env ⇨ import-layers/yocto-poky/oe-init-build-env
  14. oe-init-build-env-memres ⇨ import-layers/yocto-poky/oe-init-build-env-memres
  15. scripts ⇨ import-layers/yocto-poky/scripts
  16. .gitignore
  17. .gitreview
  18. .templateconf
  19. openbmc-env
  20. README.md
README.md

OpenBMC

Build Status

The OpenBMC project can be described as a Linux distribution for embedded devices that have a BMC; typically, but not limited to, things like servers, top of rack switches or RAID appliances. The OpenBMC stack uses technologies such as Yocto, Open-Embedded, Systemd and DBus to allow easy customization for your server platform.

Setting up your OpenBMC project

1) Prerequisite

  • Ubuntu 14.04
sudo apt-get install -y git build-essential libsdl1.2-dev texinfo gawk chrpath diffstat
  • Fedora 23
sudo dnf install -y git patch diffstat texinfo chrpath SDL-devel bitbake
sudo dnf groupinstall "C Development Tools and Libraries"

2) Download the source

git clone git@github.com:openbmc/openbmc.git
cd openbmc

3) Target your hardware

Any build requires an environment variable known as TEMPLATECONF to be set to a hardware target. OpenBMC has placed all known hardware targets in a standard directory structure meta-openbmc-machines/meta-openpower/[company]/[target]. You can see all of the known targets with find meta-openbmc-machines -type d -name conf. Choose the hardware target and then move to the next step. Additional examples can be found in the [OpenBMC Cheatsheet] (https://github.com/openbmc/docs/blob/master/cheatsheet.md)

MachineTEMPLATECONF
Palmettometa-openbmc-machines/meta-openpower/meta-ibm/meta-palmetto/conf
Barreleyemeta-openbmc-machines/meta-openpower/meta-rackspace/meta-barreleye/conf
Zaiusmeta-openbmc-machines/meta-openpower/meta-ingrasys/meta-zaius/conf
Witherspoonmeta-openbmc-machines/meta-openpower/meta-ibm/meta-witherspoon/conf

As an example target Palmetto

export TEMPLATECONF=meta-openbmc-machines/meta-openpower/meta-ibm/meta-palmetto/conf

3) Build

. openbmc-env
bitbake obmc-phosphor-image

Additional details can be found in the docs repository.

Build Validation and Testing

Commits submitted by members of the OpenBMC Github community are compiled and tested via our Jenkins server. Commits are run through two levels of testing. At the repository level the makefile make check directive is run. At the system level, the commit is built into a firmware image and run with a arm-softmmu QEMU model against a barrage of CI tests.

Commits submitted by non-members do not automatically proceed through CI testing. After visual inspection of the commit, a CI run can be manually performed by the reviewer.

Automated testing against the QEMU model along with supported systems are performed. The OpenBMC project uses the [Robot Framework] (http://robotframework.org/) for all automation. Our complete test repository can be found here.

Submitting Patches

Support of additional hardware and software packages is always welcome. Please follow the contributing guidelines when making a submission. It is expected that contributions contain test cases.

Bug Reporting

Issues are managed on Github. It is recommended you search through the issues before opening a new one.

Finding out more

Dive deeper in to OpenBMC by opening the docs repository

Contact