22.10 doesn't boot on arm64 ThunderX2 system
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
After upgrading my arm64 ThunderX2 Workstation (aka Gigabyte W281-T90) from Ubuntu 22.04 to 22.10 I've noticed that the new 5.19.0-23 kernel (linux-
[ 82.701311] watchdog: BUG: soft lockup - CPU#16 stuck for 27s! [fsck:3371]
[ 82.957315] watchdog: BUG: soft lockup - CPU#20 stuck for 26s! [fsck:3373]
[ 106.701311] watchdog: BUG: soft lockup - CPU#16 stuck for 49s! [fsck:3371]
[ 106.957315] watchdog: BUG: soft lockup - CPU#20 stuck for 48s! [fsck:3373]
[ 115.201313] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
[ 115.207401] rcu: 152-...0: (1 GPs behind) idle=1db/
[ 130.701311] watchdog: BUG: soft lockup - CPU#16 stuck for 71s! [fsck:3371]
[ 130.957314] watchdog: BUG: soft lockup - CPU#20 stuck for 70s! [fsck:3373]
[ 154.701311] watchdog: BUG: soft lockup - CPU#16 stuck for 94s! [fsck:3371]
[ 154.957314] watchdog: BUG: soft lockup - CPU#20 stuck for 93s! [fsck:3373]
[ 178.701311] watchdog: BUG: soft lockup - CPU#16 stuck for 116s! [fsck:3371]
[ 178.957314] watchdog: BUG: soft lockup - CPU#20 stuck for 115s! [fsck:3373]
messages in the console. Full log attached. Booting with:
$ uname -a
Linux tx2 5.15.0-52-generic #58-Ubuntu SMP Thu Oct 13 08:04:57 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux
makes everything work again.
| Paweł Moll (pawel-moll) wrote | #1 |
| Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote Missing required logs. | #2 |
| Changed in linux (Ubuntu): | |
| status: | New → Incomplete |
| Paweł Moll (pawel-moll) wrote | #3 |
| Changed in linux (Ubuntu): | |
| status: | Incomplete → Confirmed |
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 1995710
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.