| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
The documentation for CONFIG_PSTORE_CONSOLE indicates the following:
"pstore will log all kernel messages, even if no oops or panic happened"
This causes a console-ramoops-0 to appear in /var/lib/systemd/pstore/ on
any BMC reboot. This in turn causes phosphor-debug-collector, which
monitors for any files in this directory, to generate a BMC dump with
the file. This is not what we want.
What we really need are the dmesg-ramoops-* files which are generated
when a kernel panic or oops occur. Remove the CONSOLE setting so we only
get dumps when an actual BMC failure occurs.
Tested:
- Verified that console-ramoops-0 file no longer appears in
/var/lib/systemd/pstore/ after a BMC reboot.
- Verified we still get needed dmesg-ramoops-* files when a kernel panic
occurs.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I6b48a8715946b193257bcc4892e07f87c13c95e6
|
|
This sensor on the Op_Panel, one of them being a SI7020 type sensor
which needed to be enabled.
Signed-off-by: Bruce Mitchell <bruce.mitchell@linux.vnet.ibm.com>
Change-Id: Ib6a86a6fae52414ad9c6901e5f6f8aa8c8a383c3
|
|
Currently /proc/sysrq-trigger is the only supported backend for
debug-trigger. Once we have kdump support, we'll add a kexec backend and
drop the magic sysrq.
Change-Id: I07dfa50474d9f6333428b6fb38020c7b7fd0adec
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
The IBM rainier system is being replaced with the generic p10bmc name.
Since the rainier.conf file will be renamed p10bmc.conf, add the device
tree files for all p10 systems that will be supported with the p10bmc
name (rainier, everest).
Change-Id: I10983b913d8a2ae98ed4d327131b864f2df96a0c
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
