Source: https://www.kernel.org/doc/Documentation/memory-hotplug.txt
How to online memory
When the memory is hot-added, the kernel decides whether or not to "online"
it according to the policy which can be read from "auto_online_blocks" file::
% cat
This bug is awaiting verification that the linux-gcp-
fips/5.15.0-1055.63+fips2 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-gcp-fips' to
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the
This bug is awaiting verification that the linux-azure-
fips/5.15.0-1058.66+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-azure-fips' to
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1027.31 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp'
to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
This bug is awaiting verification that the linux-azure/5.15.0-1056.64
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-azure' to 'verification-done-jammy-
linux-azure'. If
This bug is awaiting verification that the linux-
bluefield/5.15.0-1035.37 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-bluefield' to
This bug is awaiting verification that the linux-raspi/5.15.0-1046.49
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy-
linux-raspi'. If
This bug was fixed in the package linux - 5.15.0-94.104
---
linux (5.15.0-94.104) jammy; urgency=medium
* jammy/linux: 5.15.0-94.104 -proposed tracker (LP: #2048777)
* [SRU] Duplicate Device_dax ids Created and hence Probing is Failing.
(LP: #2028158)
- device-dax: Fix
This bug is awaiting verification that the linux-ibm-gt-
fips/5.15.0-1052.55+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-ibm-gt-fips' to
Hi Michael,
There were actually 2 issues reported in this bug
1.duplicate dax id devices
2.CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE=y
1st issue is got resolved, and 2nd issue you have mentioned in Bugzilla
is no longer disabled.
To reconfigure dax-devices we have to make offline/disable online
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1047.53 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to
This bug is awaiting verification that the linux/5.15.0-94.104 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-jammy-linux' to 'verification-done-jammy-linux'. If
the problem still
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2028158
Title:
[SRU] Duplicate Device_dax ids Created and
In the latest branch CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE is no longer
disabled
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2028158_device_dax_2
** Description changed:
[Impact]
Description of problem:
Observed device_dax related probe errors in dmesg
** Description changed:
[Impact]
Description of problem:
Observed device_dax related probe errors in dmesg when HBM CPU is set to
flat mode. Duplicate device_dax ids were created and hence probing is
failing.
How reproducible:
Frequently
Version-Release
Release:
** Summary changed:
- Observed device_dax related probe errors in dmesg when HBM CPU is set to flat
mode and creating duplicate device_dax ids and hence probe is failing.
+ [SRU] Duplicate device_dax ids created and hence probing is failing.
** Summary changed:
- [SRU] Duplicate device_dax ids
18 matches
Mail list logo
