[Bug 1967961] Re: jammy beta (220330) live server arm64 iso failed to deploy with MAAS
Taihsiang Ho
1967961 at bugs.launchpad.net
Tue Apr 5 23:17:50 UTC 2022
Please note focal and impish deployment of MAAS do not reproduce this
issue.
** Summary changed:
- jammy beta (220330) live server arm64 iso failed to deploy with MAAS
+ jammy failed to deploy with MAAS
** Description changed:
= Description =
Platforms: Hisilicon D06 (d06-1 and d06-3 in our lab)
- Image: Jammy Beta (220330)
+ 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)
** Summary changed:
- jammy failed to deploy with MAAS
+ jammy failed to deploy to d06 with MAAS
** Summary changed:
- jammy failed to deploy to d06 with MAAS
+ jammy failed to deploy to Hisilicon D06 with MAAS
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to subiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1967961
Title:
jammy failed to deploy to Hisilicon D06 with MAAS
Status in linux package in Ubuntu:
New
Status in subiquity package in Ubuntu:
New
Bug description:
= 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)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967961/+subscriptions
More information about the foundations-bugs
mailing list