[SRU] Duplicate Device_dax ids Created and hence Probing is Failing.
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
linux (Ubuntu) | Status tracked in Mantic | |||||
Jammy |
In Progress
|
Medium
|
Michael Reed | |||
Lunar |
Fix Released
|
Undecided
|
Unassigned | |||
Mantic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[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: 22.04.2, 22.10
[Test Case]
Steps to Reproduce:
1. Set HBM cpu to flat mode in memory settings in BIOS.
2. Boot to the OS.
3. Perform OS warm boot cycle test.
4. Observe the dax2.0/
Actual results:
Observed device_dax related errors in dmesg, device Dax is creating dummy/duplicate devices and probe failing.
Expected results:
Dummy/duplicate devices should not create.
[Fix]
Upstream Fix
https:/
By default this is enabled, but it is causing an issue reconfiguring device dax memory, thus
it is being disabled.
Disable CONFIG_
Set CONFIG_
[Where problems could occur]
[Other Info]
Additional info:
SUT is having 2*32C HBM cpus. Eligible system-ram mode change devices should be only 2[dax0.0, dax1.0], but under "daxctl list -u" is showing 1st time 4 devices [dax0.0, 1.0, 2.0, 3.0], 2 is "state":"disabled" and 2 more devices is "mode":"devdax" which are actuall devadax to system-ram convertible devices. After reconfigure-device dax0.0, dax1.0 when you list the devices couple of more dummy/dumplicate devices are creating with "state"
root@ubuntu:
[
{
"chardev"
"size":"64.00 GiB (68.72 GB)",
"target_
"align"
"mode"
},
{
"chardev"
"size":"64.00 GiB (68.72 GB)",
"target_
"align"
"mode"
"state"
},
{
"chardev"
"size":"64.00 GiB (68.72 GB)",
"target_
"align"
"mode"
"state"
},
{
"chardev"
"size":"64.00 GiB (68.72 GB)",
"target_
"align"
"mode":"devdax" ---------------> HBM CPU 1, This we can change the devdax to
}
]
root@ubuntu:
[ 12.748884] device_dax: probe of dax2.0 failed with error -16
[ 12.748902] device_dax: probe of dax3.0 failed with error -16
After reconfig-device devdax to system-ram below are the results:
-------
root@ubuntu:
{
"chardev"
"size":"64.00 GiB (68.72 GB)",
"target_node":2,
"align":2097152,
"mode"
"online_
"total_
"movable":true
}
reconfigured 1 device
root@ubuntu:
{
"chardev"
"size":"64.00 GiB (68.72 GB)",
"target_node":3,
"align":2097152,
"mode"
"online_
"total_
"movable":true
}
reconfigured 1 device
root@ubuntu:
[
{
"chardev"
"size":"64.00 GiB (68.72 GB)",
"target_
"align"
"mode"
"state"
},
{
"chardev"
"size":"64.00 GiB (68.72 GB)",
"target_
"align"
"mode"
"online_
"total_
"movable":true
},
{
"chardev"
"size":"64.00 GiB (68.72 GB)",
"target_
"align"
"mode"
"state"
},
{
"chardev"
"size":"64.00 GiB (68.72 GB)",
"target_
"align"
"mode"
"state"
},
{
"chardev"
"size":"64.00 GiB (68.72 GB)",
"target_
"align"
"mode"
"state"
},
{
"chardev"
"size":"64.00 GiB (68.72 GB)",
"target_
"align"
"mode"
"online_
"total_
"movable":true
}
]
root@ubuntu:
[ 12.748880] device_dax dax2.0: mapping0: 0x2080000000-
[ 12.748884] device_dax: probe of dax2.0 failed with error -16
[ 12.748901] device_dax dax3.0: mapping0: 0x5080000000-
[ 12.748902] device_dax: probe of dax3.0 failed with error -16
[ 812.677056] device_dax dax4.0: mapping0: 0x2080000000-
[ 812.677070] device_dax: probe of dax4.0 failed with error -16
[ 821.092762] device_dax dax5.0: mapping0: 0x5080000000-
[ 821.092774] device_dax: probe of dax5.0 failed with error -16
information type: | Public → Private |
description: | updated |
Changed in linux (Ubuntu Lunar): | |
status: | New → Fix Released |
description: | updated |
summary: |
- 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: |
- [SRU] Duplicate device_dax ids created and hence probing is failing. + [SRU] Duplicate Device_dax ids Created and hence Probing is Failing. |
description: | updated |
information type: | Private → Public |
Changed in linux (Ubuntu Jammy): | |
assignee: | nobody → Michael Reed (mreed8855) |
importance: | Undecided → Medium |
description: | updated |
description: | updated |
Found Upstream kernel patch for hmem duplicate dax_device creation, applied on top of ubuntu 22.04.2& 22.10 working as expected, not observed any dax related errors on dmesg and no duplicate dax_device creations. /lore.kernel<email address hidden>/T/
https:/
Please consider the above patch to pull into ubuntu release.
After applied patch test results: ------- ------- ------- --- /home/ubuntu# daxctl list -u :"dax1. 0", node":3, :2097152, :"dax0. 0", node":2, :2097152,
-------
root@ubuntu:
[
{
"chardev"
"size":"64.00 GiB (68.72 GB)",
"target_
"align"
"mode":"devdax"
},
{
"chardev"
"size":"64.00 GiB (68.72 GB)",
"target_
"align"
"mode":"devdax"
}
]
ubuntu@ubuntu:~$ lsmem 000-0x000000007 fffffff 2G online yes 0 000-0x000000607 fffffff 382G online yes 2-192
RANGE SIZE STATE REMOVABLE BLOCK
0x0000000000000
0x0000000100000
Memory block size: 2G
Total online memory: 384G
Total offline memory: 0B