wily: arm64: warning in numa_init() during booting
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Wily |
Fix Committed
|
Undecided
|
dann frazier |
Bug Description
[Impact]
A kernel WARNING is printed on boot on arm64:
[ 0.000000] ------------[ cut here ]------------
[ 0.000000] WARNING: CPU: 0 PID: 0 at /build/
[ 0.000000] Modules linked in:
[ 0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 4.2.0-16-generic #19-Ubuntu
[ 0.000000] Hardware name: APM X-Gene Merlin board (DT)
[ 0.000000] Call trace:
[ 0.000000] [<ffffffc00008a
[ 0.000000] [<ffffffc00008a
[ 0.000000] [<ffffffc0008a4
[ 0.000000] [<ffffffc0000bf
[ 0.000000] [<ffffffc0000bf
[ 0.000000] [<ffffffc000c3d
[ 0.000000] [<ffffffc000c3e
[ 0.000000] [<ffffffc000c3c
[ 0.000000] [<ffffffc000c3d
[ 0.000000] [<ffffffc000c3a
[ 0.000000] [<ffffffc000c36
[ 0.000000] ---[ end trace f24b6c88ae00fa9a ]---
Though it is believed to be innocuous, it isn't obviously so, and will likely scare users.
[Test Case]
Boot wily on an arm64 system and look for the above trace in dmesg.
[Regression Risk]
The NUMA patches for arm64 were merged in in preparation for a hardware enablement project that was later postponed. I'm very confident that there are no systems out there that can boot wily's kernel and benefit from these patches.
Changed in linux (Ubuntu): | |
status: | Incomplete → New |
Changed in linux (Ubuntu): | |
status: | New → Incomplete |
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
description: | updated |
Changed in linux (Ubuntu Wily): | |
status: | New → In Progress |
assignee: | nobody → dann frazier (dannf) |
Changed in linux (Ubuntu): | |
status: | Confirmed → Invalid |
Changed in linux (Ubuntu Wily): | |
status: | In Progress → Fix Committed |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1509221
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.