Age | Commit message (Collapse) | Author | Files | Lines |
|
IBM systems do not always configure both eth0 and eth1 ports. This
causes this service to fail and hold up the boot of the BMC by the 2
minute timeout.
Override this service file to have IBM systems only wait for eth0 OR
eth1 to become active.
Change-Id: I59b118bc7261bda76b88707426fd216359e08c44
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
IBM systems do not always configure both eth0 and eth1 ports. This
causes this service to fail and hold up the boot of the BMC by the 2
minute timeout.
Override this service file to have IBM systems only wait for eth0 OR
eth1 to become active.
The SBP1 BMC has two NICs. Be happy with a link up on one of them.
TEST=Build for SBP1 & make sure with waits for either of the two
NIC to be active.
Change-Id: I2ed633805f7e71021c010b9bc53e076f2c55732e
Signed-off-by: Patrick Rudolph <patrick.rudolph@9elements.com>
|
|
IBM systems do not always configure both eth0 and eth1 ports. This
causes this service to fail and hold up the boot of the BMC by the 2
minute timeout.
Override this service file to have IBM systems only wait for eth0 OR
eth1 to become active.
The Genesis3 BMC has two NICs. Be happy with a link up on one of them.
TEST=Build for Genesis3 & make sure with waits for either of the two
NIC to be active.
Signed-off-by: Patrick Rudolph <patrick.rudolph@9elements.com>
Change-Id: I0ffd652fabd5e998b14e23621d89046a9eed5455
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Currently same subnet IPv4 configuration on both ethernet interfaces
does not work.
This commit sets kernel ARP settings which allow same subnet routes on
both ethernet interfaces at the same time.
Tested by:
Configure same subnet IP addresses on both interfaces and network
configuration works
Change-Id: I01962b8bf066ccf7006915e77f07287b6e5544d4
Signed-off-by: Ravi Teja <raviteja28031990@gmail.com>
|
|
The hardware watchdog config was disabled with commit [1] because the
fan-watchdog.bb in meta-ibm uses the /dev/watchdog already, which
according to the kernel documentation[2] it's the same device as
/dev/watchdog0.
```
[1]: https://gerrit.openbmc.org/c/openbmc/openbmc/+/60829
[2]: https://www.kernel.org/doc/Documentation/watchdog/watchdog-kernel-api.txt
```
Update the hardware watchdog config to use the currently unused
watchdog1 device to be able to recover from systemd hangs.
Verified that all IBM and OpenPower device trees contain a wdt2 device.
Tested:
- With the change, the BMC reboots after 2 min from injecting a systemd
error:
Mar 09 20:53:30 witherspoon systemd[1]: Caught <ILL> from PID 552.
Mar 09 20:53:30 witherspoon systemd-coredump[562]: Due to PID 1 having
crashed coredump collection will now be turned off.
Mar 09 20:54:25 witherspoon kernel: watchdog: watchdog1: watchdog did
not stop!
Mar 09 20:54:22 witherspoon systemd[1]: Freezing execution.
Mar 09 20:55:57 witherspoon systemd-journald[132]: Failed to send
WATCHDOG=1 notification message: Connection refused
client_loop: send disconnect: Broken pipe
- Without the change, the BMC just hangs, it stops pinging, and never
reboots:
Mar 09 21:07:23 witherspoon systemd[1]: Caught <ILL> from PID 433.
Mar 09 21:07:24 witherspoon systemd-coredump[687]: Due to PID 1 having
crashed coredump collection will now be turned off.
Mar 09 21:08:07 witherspoon systemd[1]: Freezing execution.
Mar 09 21:08:41 witherspoon systemd-journald[120]: Failed to send
WATCHDOG=1 notification message: Connection refused
Mar 09 21:10:11 witherspoon systemd-journald[120]: Failed to send
WATCHDOG=1 notification message: Transport endpoint is not connected
Mar 09 21:11:41 witherspoon systemd-journald[120]: Failed to send
WATCHDOG=1 notification message: Transport endpoint is not connected
Mar 09 21:13:12 witherspoon systemd-journald[120]: Failed to send
WATCHDOG=1 notification message: Transport endpoint is not connected
Change-Id: I7850d23805c1cb5c0b84cac4add28df16fe648f5
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
Change Ic46bcd9b8576530be7dcdda51384e1052d4a78f1 added hardware
watchdog support to all platforms but this conflicts with meta-ibm
support provided by fan-watchdog.bb. For the time being, supply a
disabled config file which will override the meta-phosphor version
so that systemd does not interact with the watchdog.
Change-Id: Ic6a587d8bab217cee8fbd421a8b6d6e3bd026631
|
|
Add a sysctl configuration file to direct sysctl to enable the
Linux kernel's panic on OOM option.
Tested on Everest hardware:
root@ever10bmc:~# cat /proc/sys/vm/panic_on_oom
2
Signed-off-by: Eddie James <eajames@linux.ibm.com>
Change-Id: Iaf6462c8911ee15deafe5a4fc4bc51f9db864afd
|
|
Upstream supports zstd compression now as an alternative to zlib or xz.
zstd is only slightly larger than xz but is significantly faster. This
makes it a better candidate for the journal. Enable it in systemd
instead of xz.
Add an exemption for witherspoon to continue using xz instead. Having
both zstd and xz support built into the image puts us over the flash
limit and we currently need xz for phosphor-debug-collector.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I6fb55b96776aeeea1c544743b08bdbbc2853e7b7
|
|
Change-Id: I9116ed7260e369136acb39eec15075db2d4dbeba
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
The p10bmc system uses a MMC flash chip with much larger storage than
a NOR chip. Increase the current journal size allocation from 2MB to 16MB
so that p1bmc saves more data for debug.
Tested: Verified that a witherspoon and p10bmc image had the expected
journal size file (2MB for witherspoon and 16MB for p10bmc) under
rootfs/lib/systemd/journald.conf.d/
Change-Id: Idcdb01bbf017c411c7b97406191e90774e8a8753
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
The IBM rainier machine name is being replaced with the generic p10bmc.
Tested: Built a rainier image and verified the journal config files were
present under:
rainier-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/rootfs/lib/systemd/
Change-Id: Ia5c1de23fdbf7b8aeed70bd450cb72254542eb41
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
The metadata common to all IBM systems is confusingly split between
meta-ibm and meta-witherspoon. Move everything to meta-ibm.
The meta-ibm README is re-written to more accurately reflect the scope
of the layer.
Allow the configuration samples (bblayers.conf.sample,
local.conf.sample) to be sourced from either meta-ibm or
meta-witherspoon until such a time that any workflows and tooling have
had the opportunity to move to meta-ibm.
(From meta-ibm rev: 6e05ef2e90b214eaf4e43ee7027bbbb1d8d09442)
Change-Id: I3ec890d5300f9649c974ea6b9dca93a2e8a889ab
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|