80448380e6
Why I did it On certain routers with baud rate 9600, crash kernel is taking a long time , close to ~5mins, to complete kernel dump and reload the box. On contrast to routers with baud rate 115200, crash kernel dump process is observed to be completed under 35s-60s (depending on the platform). Currently, all debug and informational messages are printed on the console which also factors in for the delay seen. Unless the router is monitored on console in real time, these messages are not very useful. Setting the loglevel to warning will help reduce the verbosity of logs on console, in turn allow crash kernel dump process to be completed in a reasonable time which will also help in overall router recovery time. How I did it Setting loglevel attribute in crashkernel cmdline How to verify it Install SONiC image with crashkernel cmdline with loglevel set to warning and initiate an induced a crash (sysrq-trigger) crashkernel boot and dump process will be completed in 20s-30s depending on the platform |
||
|---|---|---|
| .. | ||
| Aboot | ||
| apparmor | ||
| apt | ||
| build/versions | ||
| build_scripts | ||
| build_templates | ||
| dhcp | ||
| docker | ||
| dsc | ||
| image_config | ||
| initramfs-tools | ||
| scripts | ||
| sshd | ||