meta-phosphor: initrdscripts: Fix broken PS1 assignments

Commit 51d6af4e64f0 ("meta-phosphor: initrdscripts: fix shellcheck
issues") fixed some shellcheck trailing-space errors the wrong way,
removi

meta-phosphor: initrdscripts: Fix broken PS1 assignments

Commit 51d6af4e64f0 ("meta-phosphor: initrdscripts: fix shellcheck
issues") fixed some shellcheck trailing-space errors the wrong way,
removing the trailing space instead of removing the backslash and
quoting it. This caused the following lines to be gobbled up into the
variable assignment instead of being executed as their own commands,
which in these particular cases led to kernel panics due to pid 1
exiting (insteading of dropping into an interactive shell as intended).

Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: I8bda0efe825b34abc5219f17fdddc6d7fc57d74f

show more ...

meta-phosphor: initrdscripts: fix multi-word variable expansion

The 'files' variable is a list of (currently two) paths, which 'find'
needs to see as separate arguments.

Signed-off-by: Zev Weiss <z

meta-phosphor: initrdscripts: fix multi-word variable expansion

The 'files' variable is a list of (currently two) paths, which 'find'
needs to see as separate arguments.

Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: I31c6e8e77ed21936b8425cd7d656f1ad8a5de94a

show more ...

meta-phosphor: initrdscripts: fix shellcheck issues

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Iab07f5079bad00f3cb821f60329e5ad88e45ef4b

meta-phosphor: initrdscript: Monotonic date setting

This change intends to make the BMC date monotonic with respect to each
powercycle or reboot. It's not a perfect mechanism for maintaining
accurat

meta-phosphor: initrdscript: Monotonic date setting

This change intends to make the BMC date monotonic with respect to each
powercycle or reboot. It's not a perfect mechanism for maintaining
accurate time, but it's better than resetting to the epoch every single
reboot.

Change-Id: I76ecc49d9a77fc4846b71f1f1ce5398ca3873d72
Signed-off-by: William A. Kennington III <wak@google.com>

show more ...

initrdscripts: exec switch_root(8) instead of chroot(1)

This should address for NOR-flash systems the same problem that was
fixed for MMC-based systems in commit b5cbe9bbba67 ("phosphor-mmc-init:
ex

initrdscripts: exec switch_root(8) instead of chroot(1)

This should address for NOR-flash systems the same problem that was
fixed for MMC-based systems in commit b5cbe9bbba67 ("phosphor-mmc-init:
exec switch_root(8) rather than chroot(1)").

By virtue of switch_root(8) wiping out everything in the old root it
also avoids wasting a few megabytes of memory keeping that filesystem
around without any way of reaching it.

Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: Ib87c7dcacca45aff3fb2c3fbc288dbb80160a427

show more ...

meta-phosphor/obmc-init.sh: fix panic when rwfs is full

mkdir -p $work will fail if rwfs partition is full, and then it will
cause overlayfs mount fail as well. Finally it cause kernel panic and
bmc

meta-phosphor/obmc-init.sh: fix panic when rwfs is full

mkdir -p $work will fail if rwfs partition is full, and then it will
cause overlayfs mount fail as well. Finally it cause kernel panic and
bmc fails to boot:

rofs = mtd4 squashfs rwfs = mtd5 jffs2
[ 3.841846] jffs2: notice: (103) jffs2_build_xattr_subsystem: complete building xattr subsystem, 21 of xdatum (19 unchecked, 2 orphan) and 45 of xref (1 dead, 1 orphan) found.
mkdir: can't create directory 'run/initramfs/rw/work': No space left on device
[ 9.022304] overlayfs: failed to resolve 'run/initramfs/rw/work': -2
mount: mounting cow on /root failed: No such file or directory
chroot: can't execute '/bin/sh': No such file or directory

Unable to confirm /sbin/init is an executable non-empty file
in merged file system mounted at /root.

Change Root test failed!
Fatal error, triggering kernel panic!
[ 9.141777] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
[ 9.142489] CPU: 0 PID: 1 Comm: init Not tainted 5.10.36-60b3c9d #1
[ 9.142667] Hardware name: Generic DT based system
[ 9.142949] Backtrace:
[ 9.144308] [<80915100>] (dump_backtrace) from [<809153a4>] (show_stack+0x20/0x24)
[ 9.144623] r7:80b08ed4 r6:60000093 r5:00000000 r4:80d71c9c
[ 9.144816] [<80915384>] (show_stack) from [<80919b54>] (dump_stack+0x9c/0xb0)
[ 9.144982] [<80919ab8>] (dump_stack) from [<80915824>] (panic+0x114/0x33c)
[ 9.145136] r7:80b08ed4 r6:80d0a970 r5:00000000 r4:80dbe378
[ 9.145271] [<80915710>] (panic) from [<80126c14>] (do_exit+0x99c/0xa0c)
[ 9.145426] r3:00000001 r2:00000000 r1:00000100 r0:80b08ed4
[ 9.145552] r7:ffffe000
[ 9.145632] [<80126278>] (do_exit) from [<80127cf0>] (do_group_exit+0x50/0xc8)
[ 9.145787] r7:000000f8
[ 9.145863] [<80127ca0>] (do_group_exit) from [<80127d88>] (__wake_up_parent+0x0/0x30)
[ 9.146034] r7:000000f8 r6:00000004 r5:00000004 r4:010fd190
[ 9.146185] [<80127d68>] (sys_exit_group) from [<80100060>] (ret_fast_syscall+0x0/0x54)
[ 9.146425] Exception stack(0x810c5fa8 to 0x810c5ff0)
[ 9.146745] 5fa0: 010fd190 00000004 00000001 00000000 00000001 010fd190
[ 9.147049] 5fc0: 010fd190 00000004 00000004 000000f8 00000000 00000000 004e4a84 00000000
[ 9.147295] 5fe0: 004e4b40 7ec93a04 00474048 76df4a54
[ 9.147959] CPU1: stopping
[ 9.148650] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.10.36-60b3c9d #1
[ 9.148957] Hardware name: Generic DT based system
[ 9.149264] Backtrace:
[ 9.150182] [<80915100>] (dump_backtrace) from [<809153a4>] (show_stack+0x20/0x24)
[ 9.150598] r7:00000001 r6:60070193 r5:00000000 r4:80d71c9c
[ 9.150878] [<80915384>] (show_stack) from [<80919b54>] (dump_stack+0x9c/0xb0)
[ 9.151149] [<80919ab8>] (dump_stack) from [<8010f1f4>] (do_handle_IPI+0x2f8/0x32c)
[ 9.151430] r7:00000001 r6:0d15a000 r5:00000001 r4:80dbe278
[ 9.151649] [<8010eefc>] (do_handle_IPI) from [<8010f250>] (ipi_handler+0x28/0x30)
[ 9.151925] r9:810f6000 r8:81080800 r7:00000001 r6:0d15a000 r5:81084b80 r4:00000014
[ 9.152205] [<8010f228>] (ipi_handler) from [<80184754>] (handle_percpu_devid_fasteoi_ipi+0x80/0x154)
[ 9.152536] [<801846d4>] (handle_percpu_devid_fasteoi_ipi) from [<8017dce4>] (__handle_domain_irq+0x8c/0xe0)
[ 9.152911] r7:00000001 r6:00000000 r5:00000000 r4:80c6fbdc
[ 9.153147] [<8017dc58>] (__handle_domain_irq) from [<80101348>] (gic_handle_irq+0x7c/0x90)
[ 9.153508] r9:810f6000 r8:8f80200c r7:80c6fbe8 r6:8f802000 r5:810f7f38 r4:80d0541c
[ 9.153819] [<801012cc>] (gic_handle_irq) from [<80100b0c>] (__irq_svc+0x6c/0x90)
[ 9.154168] Exception stack(0x810f7f38 to 0x810f7f80)
[ 9.154541] 7f20: 00000000 000195e0
[ 9.154993] 7f40: 8ddcb144 8011ba00 810f6000 00000001 80d04d10 80d04d4c 80d9dfdc 80b0b4f0
[ 9.155402] 7f60: 00000000 810f7f94 810f7f98 810f7f88 80108fd4 80108fd8 60070013 ffffffff
[ 9.155762] r9:810f6000 r8:80d9dfdc r7:810f7f6c r6:ffffffff r5:60070013 r4:80108fd8
[ 9.156070] [<80108f90>] (arch_cpu_idle) from [<80926c68>] (default_idle_call+0x38/0x108)
[ 9.156382] [<80926c30>] (default_idle_call) from [<80159894>] (do_idle+0xdc/0x148)
[ 9.156676] [<801597b8>] (do_idle) from [<80159bd0>] (cpu_startup_entry+0x28/0x2c)
[ 9.156974] r9:410fc075 r8:8000406a r7:80dbe280 r6:10c0387d r5:00000001 r4:00000091
[ 9.157275] [<80159ba8>] (cpu_startup_entry) from [<8010f7c0>] (secondary_start_kernel+0x15c/0x180)
[ 9.157614] [<8010f664>] (secondary_start_kernel) from [<8010182c>] (__enable_mmu+0x0/0x14)
[ 9.157919] r5:00000051 r4:810e006a

Fix this by not removing workdir directly, but keeping the directory
and removing all entires under it. We will still get below warning,
but it can boot to shell and provide ssh access to give a chance of
recovery.

[ 9.519053] overlayfs: failed to create directory run/initramfs/rw/work/work (errno: 28); mounting read-only

Also update related patch file in meta-google to avoid build failure.

Signed-off-by: Heyi Guo <guoheyi@linux.alibaba.com>
Change-Id: I69c640c70ee3e9d1133b7d61d391501616c229d6

show more ...

obmc-init.sh: Use u-boot env instead of password for emergency console

The password prompt doesn't work anymore. Since it relied on the
default password, remove the password prompt and j

obmc-init.sh: Use u-boot env instead of password for emergency console

The password prompt doesn't work anymore. Since it relied on the
default password, remove the password prompt and just drop into
a shell if a new enable-initrd-debug-sh u-boot environment value is set.
The security implications are the same since the default
password is public and there is a need to have access to u-boot
to set the environment value.

If the environment value is not set, kernel panic the system.

Closes openbmc/openbmc#3649

Tested: Verified kernel panic if environment value was not set, and
if it was set the emergency console dropped into a shell and basic
linux commands worked:

Mounting read-write /dev/mtdblock5 filesystem failed. Please fix and run
mount /dev/mtdblock5 run/initramfs/rw -t jffs2 -o rw
or perform a factory reset with the clean-rwfs-filesystem option.
Try to manually fix.
After fixing run exit to continue this script, or reboot -f to retry, or
touch /takeover and exit to become PID 1 allowing editing of this script.
/bin/sh: can't access tty; job control turned off
/ #

(From meta-phosphor rev: 368550b2d259ac8d08c993b0d695f38aec8992fa)

Change-Id: I0431690b3b4facadbe224fc822d6bd06f35b51f5
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>

show more ...

meta-phosphor: Move layer content from common/

Adopt a more conventional directory hierarchy. meta-phosphor is still
a _long_ way from suitable for hosting on yoctoproject.org but thing

meta-phosphor: Move layer content from common/

Adopt a more conventional directory hierarchy. meta-phosphor is still
a _long_ way from suitable for hosting on yoctoproject.org but things
like this don't help.

(From meta-phosphor rev: 471cfcefa74b8c7ceb704cb670e6d915cf27c63b)

Change-Id: I3f106b2f6cdc6cec734be28a6090800546f362eb
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>

show more ...