linux-azure: Set CONFIG_CMA=n for arm64
Bug #1956762 reported by
Tim Gardner
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| linux-azure (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
| Hirsute |
Invalid
|
Medium
|
Tim Gardner | ||
Bug Description
SRU Justification
[Impact]
CONFIG_CMA was inadvertently enabled during arm64 development. It should be set the same as amd64.
[Test Case]
Check the config file from buildinfo for CONFIG_CMA=n
[Where things could go wrong]
Attempts to allocate large chunks of contiguous RAM could fail.
[Other Info]
SF: #00310705
| Changed in linux-azure (Ubuntu Hirsute): | |
| status: | New → In Progress |
| importance: | Undecided → Medium |
| assignee: | nobody → Tim Gardner (timg-tpi) |
Revision history for this message
| Tim Gardner (timg-tpi) wrote | #1 |
| Changed in linux-azure (Ubuntu Hirsute): | |
| status: | In Progress → Invalid |
| Changed in linux-azure (Ubuntu): | |
| status: | New → Invalid |
To post a comment you must log in.
Marking Invalid as this setting requires more research.