server 3.0: aspeed: enable ramoops and kdump

* ramoops worked and kdump can produce kcore
* There is one issue left when running crash tool against the kcore file

no fusion link for server 3.0

Tested:

```
root@fdtp183-nfd01:~# kdumpctl list
kcore-2025_04_08_04_59_47

root@fdtp183-nfd01:~# journalctl -b -u gbmc-dump-ramoops
Apr 08 04:59:47 fdtp183-nfd01.ntc.corp.google.com gbmc-dump-ramoops.sh[378]: [   44.488036] sysrq: Trigger a crash
Apr 08 04:59:47 fdtp183-nfd01.ntc.corp.google.com gbmc-dump-ramoops.sh[378]: [   44.491863] Kernel panic - not syncing: sysrq triggered crash
Apr 08 04:59:47 fdtp183-nfd01.ntc.corp.google.com gbmc-dump-ramoops.sh[378]: [   44.498277] SMP: stopping secondary CPUs
Apr 08 04:59:47 fdtp183-nfd01.ntc.corp.google.com gbmc-dump-ramoops.sh[378]: [   44.502770] Starting crashdump kernel...
Apr 08 04:59:47 fdtp183-nfd01.ntc.corp.google.com gbmc-dump-ramoops.sh[378]: [   44.507142] Bye!
Apr 08 04:59:47 fdtp183-nfd01.ntc.corp.google.com gbmc-dump-ramoops.sh[378]: The kernel version is not supported.
Apr 08 04:59:47 fdtp183-nfd01.ntc.corp.google.com gbmc-dump-ramoops.sh[378]: The makedumpfile operation may be incomplete.
Apr 08 04:59:47 fdtp183-nfd01.ntc.corp.google.com gbmc-dump-ramoops.sh[378]: [820B blob data]
Apr 08 04:59:47 fdtp183-nfd01.ntc.corp.google.com gbmc-dump-ramoops.sh[378]: The dumpfile is saved to STDOUT.
Apr 08 04:59:47 fdtp183-nfd01.ntc.corp.google.com gbmc-dump-ramoops.sh[378]: makedumpfile Completed.
Apr 08 04:59:47 fdtp183-nfd01.ntc.corp.google.com gbmc-dump-ramoops.sh[378]: 51780+0 records in
Apr 08 04:59:47 fdtp183-nfd01.ntc.corp.google.com gbmc-dump-ramoops.sh[378]: 51780+0 records out
Apr 08 04:59:47 fdtp183-nfd01.ntc.corp.google.com gbmc-dump-ramoops.sh[434]: 11+0 records in
Apr 08 04:59:47 fdtp183-nfd01.ntc.corp.google.com gbmc-dump-ramoops.sh[434]: 11+0 records out
Apr 08 04:59:50 fdtp183-nfd01.ntc.corp.google.com gbmc-dump-ramoops.sh[437]: 429+1 records in
Apr 08 04:59:50 fdtp183-nfd01.ntc.corp.google.com gbmc-dump-ramoops.sh[437]: 429+1 records out
Apr 08 04:59:50 fdtp183-nfd01.ntc.corp.google.com gbmc-dump-ramoops.sh[438]: The dumpfile is saved to /run/log/kdump/kcore-2025_04_08_04_59_47.
Apr 08 04:59:50 fdtp183-nfd01.ntc.corp.google.com gbmc-dump-ramoops.sh[438]: makedumpfile Completed.
Apr 08 04:59:50 fdtp183-nfd01.ntc.corp.google.com gbmc-dump-ramoops.sh[323]: removing pmsg file /sys/fs/pstore/pmsg-ramoops-0
Apr 08 04:59:51 fdtp183-nfd01.ntc.corp.google.com systemd[1]: gbmc-dump-ramoops.service: Deactivated successfully.
Apr 08 04:59:51 fdtp183-nfd01.ntc.corp.google.com systemd[1]: Finished gbmc-dump-ramoops.service.
Apr 08 04:59:51 fdtp183-nfd01.ntc.corp.google.com systemd[1]: gbmc-dump-ramoops.service: Consumed 1.526s CPU time, 23.4M memory peak.
```

Google-Bug-Id: 373416015
Change-Id: I3670ed294e2899be59b27d0eaaf4c8ee5159b66a
Signed-off-by: Anh Phan <anhphan@google.com>
7 files changed
tree: cbf98d4208c151df1034fe95b078ce92ed5085ba
  1. classes/
  2. conf/
  3. dynamic-layers/
  4. recipes-bsp/
  5. recipes-connectivity/
  6. recipes-core/
  7. recipes-devtools/
  8. recipes-extended/
  9. recipes-google/
  10. recipes-kernel/
  11. recipes-phosphor/
  12. recipes-support/
  13. recipes-tpm1/
  14. recipes-tpm2/
  15. LICENSE
  16. README.md
README.md

meta-gbmc-staging

This repository contains additions to the openbmc/meta-google layer that are not yet ready for OpenBMC inclusion.

How to use this layer

  1. Clone openbmc/openbmc from GitHub.
  2. Clone this layer from GitHub into a subdirectory of openbmc.