You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current fire and forget approach doesn't work reliably in all corner
cases for various reasons, like for example serial console bitflip or
lost byte issues due to RX fifo overruns. Those issues mostly happen
frequently during early boot process, where there is a lot of output
going on.
So let's make it more reliable by actually checking the kernel log level
setting via /proc/sys/kernel/printk and retry if it's not set to desired
log level.
Following example is from GL.iNet GL-B1300 device:
root@(none):/# mg-
/bin/ash: mg-: not found
root@(none):/# coRC;ct/rcsy/kerne/rnk;eh QZE[ 6.365640] kmodloader:
loading kernel modules from /etc/modules.d/*
...
dmesg -n 1
/bin/ash: coRC: not found
/bin/ash: ct/rcsy/kerne/rnk: not found
/bin/ash: eh: not found
root@(none):/# echo BZXI; cat /proc/sys/kernel/printk ; echo AUTHSA
BZXI
7 4 1 7
AUTHSA
root@(none):/# dmesg -n 1
root@(none):/# echo XYTH; cat /proc/sys/kernel/printk ; echo PNCWGM
XYTH
1 4 1 7
PNCWGM
Signed-off-by: Petr Štetiar <[email protected]>
0 commit comments