tree 6e18b96a1c214fc3052dfafbae44fd75eefe8fa5
parent de0c27ed80e102b14d4e8dbec9020380fb0b4369
author Andrew Geissler <geissonator@yahoo.com> 1707931973 -0600
committer Andrew Geissler <geissonator@yahoo.com> 1707936495 -0600

mmc-init.sh: ensure only one udevd running

Recently the following error started popping up in the journal:
```
Jan 04 07:53:25 p10bmc systemd-coredump[174]: Due to PID 1 having crashed coredump collection will now be turned off.
Jan 04 07:53:25 p10bmc systemd-coredump[174]: Resource limits disable core dumping for process 76 (udevd).
Jan 04 07:53:25 p10bmc systemd-coredump[174]: Process 76 (udevd) of user 0 dumped core.
```

This error during boot was disabling all coredump generation and
collection on the system.

After a lot of digging, it was found that we were actually running 2
instances of udevd on the system. One started by this script, and
another by systemd-udevd.service. The one failing was the first one we
started. It's safe to assume that running 2 instances of udevd has
undefined behavior and something in more recent openbmc (or systemd) has
caused this fail to start.

Tested:
- Confirmed BMC still boots fine and coredumps now work

Change-Id: I3e4aaa82b18181f1bba62d76ff13af29437c9bb8
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>