Description of problem: System became terrible unresponsible during swap process You can quickly reproduce this if open in Google Chrome this link: http://ec2-54-229-117-209.eu-west-1.compute.amazonaws.com/party.html
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs. Fedora 19 has now been rebased to 3.11.1-200.fc19. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
$ uname -a Linux localhost.localdomain 3.11.1-200.fc19.x86_64 #1 SMP Sat Sep 14 15:04:51 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux update not hepls
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs. Fedora 19 has now been rebased to 3.12.6-200.fc19. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 20, and are still experiencing this issue, please change the version to Fedora 20. If you experience different issues, please open a new bug report for those.
Created attachment 845125 [details] html for demonstrate system freeze
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.13.4-200.fc20. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
update not hepls
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.14.4-200.fc20. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
Problem still not fixed
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.17.2-200.fc20. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21. If you experience different issues, please open a new bug report for those.
Created attachment 957404 [details] kernel awfully slow when occurs this
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 21 kernel bugs. Fedora 21 has now been rebased to 3.18.3-201.fc21. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
issue not fixed please open omhed.html in firefox for investigate it
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 21 kernel bugs. Fedora 21 has now been rebased to 3.19.5-200.fc21. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 22, and are still experiencing this issue, please change the version to Fedora 22. If you experience different issues, please open a new bug report for those.
of course problem still persists
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 22 kernel bugs. Fedora 22 has now been rebased to 4.2.3-200.fc22. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 23, and are still experiencing this issue, please change the version to Fedora 23. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 23 kernel bugs. Fedora 23 has now been rebased to 4.7.4-100.fc23. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 24 or 25, and are still experiencing this issue, please change the version to Fedora 24 or 25. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 25 kernel bugs. Fedora 25 has now been rebased to 4.9.3-200.fc25. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26. If you experience different issues, please open a new bug report for those.
Nothing changed here still have worse experience than on Windows (GUI freeze, switching between application so hard)
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 25 kernel bugs. Fedora 25 has now been rebased to 4.10.9-200.fc25. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26. If you experience different issues, please open a new bug report for those.
Still not fixed: $ uname -r 4.11.0-0.rc6.git0.1.fc26.x86_64+debug # vmstat procs -----------memory---------- ---swap-- -----io---- -system-- ------cpu----- r b swpd free buff cache si so bi bo in cs us sy id wa st 1 4 0 227764 39240 6941580 0 0 1687 1601 1619 1269 32 11 16 41 0
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. The kernel moves very fast so bugs may get fixed as part of a kernel update. Due to this, we are doing a mass bug update across all of the Fedora 26 kernel bugs. Fedora 26 has now been rebased to 4.15.4-200.fc26. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 27, and are still experiencing this issue, please change the version to Fedora 27. If you experience different issues, please open a new bug report for those.
still not fixed $ uname -a Linux localhost.localdomain 4.15.7-300.fc27.x86_64+debug #1 SMP Wed Feb 28 17:32:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 27 kernel bugs. Fedora 27 has now been rebased to 4.17.7-100.fc27. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 28, and are still experiencing this issue, please change the version to Fedora 28. If you experience different issues, please open a new bug report for those.
$ uname -r 4.18.0-0.rc7.git1.1.fc29.x86_64 First I want noted huge progress in this question. But interface still suck especially in Wayland session. How to reproduce: 1) Please, move /home directory to HDD. 2) After system boot click to Activities and then try click "Show application". Until application data is not read from the hard disk, the mouse pointer stuck and not move.
Another good reproduction case: On machine with 2Gb RAM run $ stress --vm 1 --vm-bytes 1G
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs. Fedora 28 has now been rebased to 4.18.10-300.fc28. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 29, and are still experiencing this issue, please change the version to Fedora 29. If you experience different issues, please open a new bug report for those.
I am wrote simple python utility for finding most long system calls in strace log from which arise interface freezes. Here is top 10 long system calls for gnome-shell: ########### line: 86657 time 4.929490 86655: ioctl(13, DRM_IOCTL_AMDGPU_GEM_CREATE or DRM_IOCTL_VIA_ALLOCMEM, 0x7ffe2b3df6f0) = 0 <0.000159> 86656: ioctl(13, _IOC(_IOC_READ|_IOC_WRITE, 0x64, 0x48, 0x28), 0x7ffe2b3df700) = 0 <0.000064> 86657: ioctl(13, DRM_IOCTL_AMDGPU_GEM_CREATE or DRM_IOCTL_VIA_ALLOCMEM, 0x7ffe2b3df6c0) = 0 <4.929490> 86658: ioctl(13, _IOC(_IOC_READ|_IOC_WRITE, 0x64, 0x48, 0x28), 0x7ffe2b3df6d0) = 0 <0.000101> 86659: futex(0x563ed5decb9c, FUTEX_WAKE_PRIVATE, 1) = 1 <0.000030> 86660: futex(0x563ed5decb48, FUTEX_WAKE_PRIVATE, 1) = 1 <0.000016> 86661: futex(0x563ed630c0d8, FUTEX_WAIT_BITSET, 2, NULL, 0xffffffff) = 0 <0.000074> ########### line: 1053189 time 4.339326 1053187: recvmsg(42, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable) <0.000018> 1053188: poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=10, events=POLLIN}, {fd=11, events=POLLIN}, {fd=16, events=POLLIN}, {fd=42, events=POLLIN}, {fd=45, events=POLLIN}, {fd=55, events=POLLIN}, {fd=61, events=POLLIN}, {fd=64, events=POLLIN}, {fd=71, events=POLLIN}, {fd=75, events=POLLIN}, {fd=91, events=POLLIN}, {fd=94, events=POLLIN}], 14, 1) = 0 (Timeout) <0.001120> 1053189: ioctl(11, DRM_IOCTL_MODE_CURSOR, 0x7ffe2b3e6550) = 0 <4.339326> 1053190: getpid() = 1927 <0.000043> 1053191: ioctl(13, _IOC(_IOC_READ|_IOC_WRITE, 0x64, 0x48, 0x28), 0x7ffe2b3e5fc0) = 0 <0.000101> 1053192: munmap(0x7f9ceac6d000, 131072) = 0 <0.000048> 1053193: ioctl(13, DRM_IOCTL_GEM_CLOSE, 0x7ffe2b3e6010) = 0 <0.000067> ########### line: 1182022 time 2.286893 1182020: read(4, "\1\0\0\0\0\0\0\0", 16) = 8 <0.000026> 1182021: recvmsg(42, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable) <0.000033> 1182022: poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=10, events=POLLIN}, {fd=11, events=POLLIN}, {fd=16, events=POLLIN}, {fd=42, events=POLLIN}, {fd=45, events=POLLIN}, {fd=55, events=POLLIN}, {fd=61, events=POLLIN}, {fd=64, events=POLLIN}, {fd=71, events=POLLIN}, {fd=75, events=POLLIN}, {fd=94, events=POLLIN}, {fd=96, events=POLLIN}], 14, 25) = 4 ([{fd=5, revents=POLLIN}, {fd=11, revents=POLLIN}, {fd=16, revents=POLLIN}, {fd=42, revents=POLLIN}]) <2.286893> 1182023: recvmsg(42, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="\34\0-DA\0`\3\"\1\0\0\230\267\21\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0", iov_len=4096}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 32 <0.000217> 1182024: recvmsg(42, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable) <0.000019> 1182025: write(4, "\1\0\0\0\0\0\0\0", 8) = 8 <0.000067> 1182026: read(11, "\2\0\0\0 \0\0\0\20\365\233\331>V\0\0\210\4\0\0Zq\f\0\f\17\1\0+\0\0\0", 1024) = 32 <0.000026> ########### line: 1053237 time 2.048399 1053235: mmap(NULL, 90112, PROT_READ|PROT_WRITE, MAP_SHARED, 13, 0x3842a2000) = 0x7f9cead24000 <0.000049> 1053236: recvmsg(56, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="\33\0\0\0\1\0\24\0 \0\0\0\0\0\0\0\0\0\0\0\33\0\0\0\10\0\f\0\2\0\0\0"..., iov_len=1912}, {iov_base="", iov_len=2184}], msg_iovlen=2, msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_DONTWAIT|MSG_CMSG_CLOEXEC) = 188 <0.000031> 1053237: ioctl(13, DRM_IOCTL_AMDGPU_GEM_CREATE or DRM_IOCTL_VIA_ALLOCMEM, 0x7ffe2b3e5640) = 0 <2.048399> 1053238: ioctl(13, _IOC(_IOC_READ|_IOC_WRITE, 0x64, 0x48, 0x28), 0x7ffe2b3e5650) = 0 <0.000144> 1053239: ioctl(13, DRM_IOCTL_AMDGPU_GEM_MMAP, 0x7ffe2b3e5b10) = 0 <0.000033> 1053240: mmap(NULL, 4435968, PROT_READ|PROT_WRITE, MAP_SHARED, 13, 0x30c814000) = 0x7f9c48cf1000 <0.000054> 1053241: recvmsg(87, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="\4\0\0\0\0\0\f\0U\1\0\0\4\0\0\0\0\0\f\0V\1\0\0U\1\0\0\0\0\10\0"..., iov_len=412}, {iov_base="", iov_len=3684}], msg_iovlen=2, msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_DONTWAIT|MSG_CMSG_CLOEXEC) = 80 <0.000041> ########### line: 1513586 time 1.820970 1513584: futex(0x563ed63322e8, FUTEX_WAIT_BITSET, 2, NULL, 0xffffffff) = 0 <0.000355> 1513585: ioctl(11, DRM_IOCTL_MODE_ADDFB2, 0x7ffe2b3e63a0) = 0 <0.000031> 1513586: ioctl(11, DRM_IOCTL_MODE_PAGE_FLIP, 0x7ffe2b3e6340) = 0 <1.820970> 1513587: recvmsg(42, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable) <0.000043> 1513588: recvmsg(42, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable) <0.000030> 1513589: poll([{fd=4, events=POLLIN}, {fd=10, events=POLLIN}, {fd=11, events=POLLIN}, {fd=16, events=POLLIN}, {fd=42, events=POLLIN}, {fd=45, events=POLLIN}, {fd=55, events=POLLIN}, {fd=61, events=POLLIN}, {fd=64, events=POLLIN}, {fd=71, events=POLLIN}, {fd=74, events=POLLIN}, {fd=91, events=POLLIN}, {fd=92, events=POLLIN}], 13, 0) = 1 ([{fd=16, revents=POLLIN}]) <0.000049> 1513590: write(4, "\1\0\0\0\0\0\0\0", 8) = 8 <0.000042> ########### line: 663229 time 1.750186 663227: mprotect(0x282913225000, 4096, PROT_READ|PROT_WRITE) = 0 <0.000013> 663228: mprotect(0x282913225000, 4096, PROT_READ|PROT_EXEC) = 0 <0.000012> 663229: ioctl(13, DRM_IOCTL_AMDGPU_GEM_CREATE or DRM_IOCTL_VIA_ALLOCMEM, 0x7ffe2b3e0790) = 0 <1.750186> 663230: ioctl(13, _IOC(_IOC_READ|_IOC_WRITE, 0x64, 0x48, 0x28), 0x7ffe2b3e07a0) = 0 <0.000112> 663231: futex(0x563ed5decb98, FUTEX_WAKE_PRIVATE, 1) = 1 <0.000026> 663232: futex(0x563ed630c0d8, FUTEX_WAIT_BITSET, 2, NULL, 0xffffffff) = 0 <0.000170> 663233: ioctl(13, DRM_IOCTL_AMDGPU_WAIT_CS, 0x7ffe2b3e07f0) = 0 <0.001006> ########### line: 1229915 time 1.623886 1229913: recvmsg(39, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="V\0\0\0\1\0\24\0\250\0\0\0\0\0\0\0\0\0\0\0V\0\0\0\2\0\30\0\0\0\0\0"..., iov_len=3540}, {iov_base="", iov_len=556}], msg_iovlen=2, msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_DONTWAIT|MSG_CMSG_CLOEXEC) = 192 <0.000039> 1229914: recvmsg(83, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="\34\0\0\0\1\0\24\0*\0\0\0\0\0\0\0\0\0\0\0\34\0\0\0\10\0\f\0\2\0\0\0"..., iov_len=932}, {iov_base="", iov_len=3164}], msg_iovlen=2, msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_DONTWAIT|MSG_CMSG_CLOEXEC) = 188 <0.000030> 1229915: ioctl(13, DRM_IOCTL_AMDGPU_GEM_CREATE or DRM_IOCTL_VIA_ALLOCMEM, 0x7ffe2b3e55b0) = 0 <1.623886> 1229916: ioctl(13, _IOC(_IOC_READ|_IOC_WRITE, 0x64, 0x48, 0x28), 0x7ffe2b3e55c0) = 0 <0.000453> 1229917: ioctl(13, DRM_IOCTL_AMDGPU_GEM_MMAP, 0x7ffe2b3e5a80) = 0 <0.000072> 1229918: mmap(NULL, 32317440, PROT_READ|PROT_WRITE, MAP_SHARED, 13, 0x41dc0f000) = 0x7f9c314e9000 <0.000043> 1229919: write(4, "\1\0\0\0\0\0\0\0", 8) = 8 <0.000027> ########### line: 45209 time 1.497750 45207: futex(0x563ed63322e8, FUTEX_WAIT_BITSET, 2, NULL, 0xffffffff) = 0 <0.000391> 45208: ioctl(11, DRM_IOCTL_MODE_ADDFB2, 0x7ffe2b3e63a0) = 0 <0.000022> 45209: ioctl(11, DRM_IOCTL_MODE_PAGE_FLIP, 0x7ffe2b3e6340) = 0 <1.497750> 45210: recvmsg(42, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable) <0.000025> 45211: sendmsg(39, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="\0214\3\0\0\0\f\0\3040\r\0\1\0\0\0\1\0\f\0\0214\3\0\0174\3\0\0\0\f\0"..., iov_len=144}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, MSG_DONTWAIT|MSG_NOSIGNAL) = 144 <0.000041> 45212: sendmsg(83, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="\10\0\0\0\2\0\24\0\3020\r\0h\211\1\0\"\225\0\0\10\0\0\0\5\0\10\0", iov_len=28}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, MSG_DONTWAIT|MSG_NOSIGNAL) = 28 <0.000037> 45213: sendmsg(59, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="%\0\0\0\0\0\f\0\3050\r\0\1\0\0\0\1\0\f\0%\0\0\0", iov_len=24}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, MSG_DONTWAIT|MSG_NOSIGNAL) = 24 <0.000033> ########### line: 86456 time 1.111580 86454: recvmsg(42, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable) <0.000032> 86455: poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=10, events=POLLIN}, {fd=11, events=POLLIN}, {fd=16, events=POLLIN}, {fd=42, events=POLLIN}, {fd=45, events=POLLIN}, {fd=55, events=POLLIN}, {fd=61, events=POLLIN}, {fd=64, events=POLLIN}, {fd=71, events=POLLIN}, {fd=74, events=POLLIN}, {fd=75, events=POLLIN}, {fd=92, events=POLLIN}], 14, 0) = 0 (Timeout) <0.000054> 86456: ioctl(13, DRM_IOCTL_AMDGPU_GEM_CREATE or DRM_IOCTL_VIA_ALLOCMEM, 0x7ffe2b3e0c40) = 0 <1.111580> 86457: ioctl(13, _IOC(_IOC_READ|_IOC_WRITE, 0x64, 0x48, 0x28), 0x7ffe2b3e0c50) = 0 <0.000143> 86458: futex(0x563ed5decb98, FUTEX_WAKE_PRIVATE, 1) = 1 <0.000028> 86459: futex(0x563ed5decb48, FUTEX_WAKE_PRIVATE, 1) = 1 <0.000022> 86460: futex(0x563ed630c0d8, FUTEX_WAIT_BITSET, 2, NULL, 0xffffffff) = 0 <0.000301> ########### line: 1218110 time 1.094502 1218108: recvmsg(42, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable) <0.000020> 1218109: recvmsg(42, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable) <0.000017> 1218110: poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=10, events=POLLIN}, {fd=11, events=POLLIN}, {fd=16, events=POLLIN}, {fd=42, events=POLLIN}, {fd=45, events=POLLIN}, {fd=55, events=POLLIN}, {fd=61, events=POLLIN}, {fd=64, events=POLLIN}, {fd=71, events=POLLIN}, {fd=75, events=POLLIN}, {fd=94, events=POLLIN}, {fd=96, events=POLLIN}], 14, 256) = 3 ([{fd=5, revents=POLLIN}, {fd=11, revents=POLLIN}, {fd=16, revents=POLLIN}]) <1.094502> 1218111: write(4, "\1\0\0\0\0\0\0\0", 8) = 8 <0.000029> 1218112: read(11, "\2\0\0\0 \0\0\0\200\257#\332>V\0\0\223\4\0\0\264\322\4\0\202\21\1\0+\0\0\0", 1024) = 32 <0.000164> 1218113: ioctl(11, DRM_IOCTL_MODE_RMFB, 0x7ffe2b3e62ec) = 0 <0.000043> 1218114: write(4, "\1\0\0\0\0\0\0\0", 8) = 8 <0.000031>
Created attachment 1491709 [details] python utility for find top long system calls
Created attachment 1491710 [details] full strace dump
Created attachment 1491711 [details] top 100 longest system calls