------- Comment From [email protected] 2019-01-04 06:12 EDT-------
I have tried the following test in order to reproduce the bug:
##
root@localhost:~# uname -a
Linux localhost 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018
ppc64le ppc64le ppc64le GNU/Linux
root@localhost:~# cat /sys/kernel/mm/transparent_hugepage/enabled
[always] madvise never
##
dd if=/dev/urandom of=/dev/shm/img bs=2M count=2000
md5sum /dev/shm/img > test.md5
After the migration, i did:
md5sum -c test.md5
And the result was OK. (memory not corrupted).
I also modified the above test allocating chunks of 2M, this way:
for i in {0001..2000} ; do dd if=/dev/urandom of=/dev/shm/img_${i} bs=2M
count=1 ; done
md5sum /dev/shm/* > test.md5
After the migration, i did:
md5sum -c test.md5
And the result was OK for every file. (memory not corrupted).
Conclusion:
- I have found no difference between patched and unpatched kernel during the
tests.
- The memory after the migration seems fine, returning the same memory block
(tested with md5sum)
Is there any other suggestion about how to reproduce the bug?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788098
Title:
Avoid migration issues with aligned 2MB THB
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
