jammy failed to deploy to Hisilicon D06 with MAAS

[Taihsiang Ho]

= Description =
Platforms: Hisilicon D06 (d06-1 and d06-3 in our lab)
Image: Jammy

= Steps to Reproduce =
1. Deploy the system with MAAS webUI
2. Wait until everything is ready

= Expected Results =
After the system is installed at the ephemeral stage of MAAS installation and restarts, the system boots and ready to login and use.

= Actual Results =
The system is never ready to be at the login prompt stage, and MAAS deployment timeouts.

The console log of the system (see the attachment d06-1.log for the full log):

[ 366.412548] INFO: task kworker/31:1:624 blocked for more than 241 seconds.
[ 366.412566] Tainted: G L 5.15.0-25-generic #25-Ubuntu
[ 366.412577] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 366.412826] INFO: task kworker/u196:1:1107 blocked for more than 120 seconds.
[ 366.412833] Tainted: G L 5.15.0-25-generic #25-Ubuntu
[ 366.412840] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
** 2167 printk messages dropped **
[ 387.007501] watchdog: BUG: soft lockup - CPU#9 stuck for 272s! [swapper/9:0]
[ 387.037902] watchdog: BUG: soft lockup - CPU#7 stuck for 272s! [swapper/7:0]
[ 411.004684] watchdog: BUG: soft lockup - CPU#9 stuck for 294s! [swapper/9:0]
[ 411.025400] watchdog: BUG: soft lockup - CPU#7 stuck for 294s! [swapper/7:0]
[ 435.005493] watchdog: BUG: soft lockup - CPU#7 stuck for 317s! [swapper/7:0]
[ 435.019191] watchdog: BUG: soft lockup - CPU#9 stuck for 317s! [swapper/9:0]
[*** [ 455.581303] systemd[1]: sysinit.target: Unable to break cycle starting with sysinit.target/start
[ **] (6 of 7) A start job is running for…d Directories (6min 4s / no limit)

[Taihsiang Ho (tai271828)]

Please note focal and impish deployment of MAAS do not reproduce this issue.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1967961

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Taihsiang Ho (tai271828)]

Tried to deploy d06-3 with jammy again today. I was dropped to the root username after the ephemeral environment installation reboot[1]. See the attachment "d06-3-maas-220406-01.log" for the full console log.

[1]

[ OK ] Finished Availability of block devices.

root@d06-3:~#
root@d06-3:~#

[Taihsiang Ho (tai271828)]

d06-3-maas-220406-02.log is the console log for maas deployment timeout with d06-3.

[Taihsiang Ho (tai271828)]

In our lab, a production level taishan2280v2 (scobee) and x6000 (saenger) could be deployed by MAAS successfully.