------- Comment From <email address hidden> 2018-04-10 21:32 EDT-------
According to test they have another bostonLC (boslcp4) and they did update to this kernel and system is booting up normally.
root@boslcp4:~# uname -a
Linux boslcp4 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux
root@boslcp4:~# date
Tue Apr 10 16:37:37 CDT 2018
root@boslcp4:~# uptime
16:37:38 up 40 min, 2 users, load average: 0.00, 0.03, 0.12
Additionally, I rebooted the system a third time to add the slub_debug=FZ kernel option and system booted to the login and I logged in successfully. I did it a fourth time and it succeeded again.
root@boslcp3:~# uname -a
Linux boslcp3 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux
root@boslcp3:~# cat /proc/cmdline
root=UUID=bab108a0-d0a6-4609-87f1-6e33d0ad633c ro xmon=on splash quiet slub_debug=FZ
------- Comment From <email address hidden> 2018-04-10 21:32 EDT-------
According to test they have another bostonLC (boslcp4) and they did update to this kernel and system is booting up normally.
root@boslcp4:~# uname -a
Linux boslcp4 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux
root@boslcp4:~# date
Tue Apr 10 16:37:37 CDT 2018
root@boslcp4:~# uptime
16:37:38 up 40 min, 2 users, load average: 0.00, 0.03, 0.12
Additionally, I rebooted the system a third time to add the slub_debug=FZ kernel option and system booted to the login and I logged in successfully. I did it a fourth time and it succeeded again.
root@boslcp3:~# uname -a bab108a0- d0a6-4609- 87f1-6e33d0ad63 3c ro xmon=on splash quiet slub_debug=FZ
Linux boslcp3 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux
root@boslcp3:~# cat /proc/cmdline
root=UUID=
Strange.