[Bug 1177541] New: System freezes under high disk I/O usage
http://bugzilla.opensuse.org/show_bug.cgi?id=1177541 Bug ID: 1177541 Summary: System freezes under high disk I/O usage Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: HP OS: openSUSE Leap 15.2 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: Abdulrhman.Ied@Gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.75 Safari/537.36 Build Identifier: My system freezes for few seconds when there is high disk usage, like copying large files, or when opening a demanding chrome web pages (due to swaping?). It happens on Ext4, Btrfs and XFS, so file system doesn't matter. It happens on both Gnome and Xfce, so that also doesn't matter. Windows 10, Fedora and Ubuntu works almost fine on the same device, it's a problem with Leap 15.2 only. So I upgraded my system from Leap 15.2 to TW, and everything works almost fine now. I booted my device to TW but with Leap kernel (5.3.18-lp152.44-default), and the freezes happen again. So it seems to me that's a kernel issue. My search lead me to multiple cases with the same issue (different distros). See: https://askubuntu.com/questions/1212736/system-freezes-on-disk-i-o And: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861359 It seems like newer kernel have this issue fixed, maybe version 5.5.6 (as stated in the link), and it seems that Ubuntu backported successfully a fix to kernel 5.4. This issue is very annoying, I hope openSUSE can backport a fix from upstream. Reproducible: Always Steps to Reproduce: 1. Start a disk demanding process, like copying large files Actual Results: Freezes and a laggy mouse cursor Expected Results: Smooth system Maybe it could be more obvious in devices with low ram, but Ubuntu 20.04 and Windows 10 work perfectly on the same device. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1177541 http://bugzilla.opensuse.org/show_bug.cgi?id=1177541#c1 Wolfgang Bauer <wbauer@tmo.at> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wbauer@tmo.at --- Comment #1 from Wolfgang Bauer <wbauer@tmo.at> --- Might be related to/the same as bug#1159882... Btw, I experienced similar problems here after upgrading to 15.2. I then installed the latest kernel from http://download.opensuse.org/repositories/Kernel:/stable/standard and things are *much* improved now. (I'd say it wokrs even better than previous Leap kernels...) ;-) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1177541 http://bugzilla.opensuse.org/show_bug.cgi?id=1177541#c2 --- Comment #2 from Abdulrhman Ied <Abdulrhman.Ied@Gmail.com> --- (In reply to Wolfgang Bauer from comment #1)
Might be related to/the same as bug#1159882...
Btw, I experienced similar problems here after upgrading to 15.2. I then installed the latest kernel from http://download.opensuse.org/repositories/Kernel:/stable/standard and things are *much* improved now. (I'd say it wokrs even better than previous Leap kernels...) ;-)
Probably it's the same. So I will continue there. It is reliable to run bleeding edge kernel on Leap? I will do it as it seems to work in my test, and as it's just a temporary situation (hopefully). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1177541 http://bugzilla.opensuse.org/show_bug.cgi?id=1177541#c3 --- Comment #3 from Wolfgang Bauer <wbauer@tmo.at> --- (In reply to Abdulrhman Ied from comment #2)
It is reliable to run bleeding edge kernel on Leap? Sure, unless you rely on the ABI stability on kernel updates. I.e. if you use 3rd party modules you may have to recompile them yourself after each update, precompiled KMP packages for Leap won't work either.
It's basically the same kernel as in Tumbleweed btw. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1177541 http://bugzilla.opensuse.org/show_bug.cgi?id=1177541#c4 --- Comment #4 from Wolfgang Bauer <wbauer@tmo.at> --- And just in case: I'm not sure if the kernel from that repo would work with Secure Boot though. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1177541 http://bugzilla.opensuse.org/show_bug.cgi?id=1177541#c5 --- Comment #5 from Abdulrhman Ied <Abdulrhman.Ied@Gmail.com> --- (In reply to Wolfgang Bauer from comment #3)
(In reply to Abdulrhman Ied from comment #2)
It is reliable to run bleeding edge kernel on Leap? Sure, unless you rely on the ABI stability on kernel updates. I.e. if you use 3rd party modules you may have to recompile them yourself after each update, precompiled KMP packages for Leap won't work either.
It's basically the same kernel as in Tumbleweed btw.
Thanks for the information, It seems that I don't use any of these fancy stuff, and I use the legacy bios too. That lets me wondering, if someone has to use a bleeding edge kernel, then what's the point of using an LTS distro rather than a bleeding edge one, or what the point of using Leap rather than another LTS distro. Anyway, I hope that this is a temporary situation, and fixes will be backported soon, so we can go back to a higher standard stability. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1177541 http://bugzilla.opensuse.org/show_bug.cgi?id=1177541#c6 --- Comment #6 from Wolfgang Bauer <wbauer@tmo.at> --- (In reply to Abdulrhman Ied from comment #5)
That lets me wondering, if someone has to use a bleeding edge kernel, then what's the point of using an LTS distro rather than a bleeding edge one, or what the point of using Leap rather than another LTS distro. Well, you don't *have* to use a bleeding edge kernel, but you *can* if you want or have problems with the standard one. And it doesn't change the rest of the system.
This of course apparently is a general problem with the 5.3 and 5.4 kernels and not specific to openSUSE Leap, other than that kernel 5.3 has been picked as base for Leap 15.2 and SLE 15 SP2...
Anyway, I hope that this is a temporary situation, and fixes will be backported soon, so we can go back to a higher standard stability. Yes, I hope so too.
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1177541 http://bugzilla.opensuse.org/show_bug.cgi?id=1177541#c7 --- Comment #7 from Abdulrhman Ied <Abdulrhman.Ied@Gmail.com> --- (In reply to Wolfgang Bauer from comment #6)
Well, you don't *have* to use a bleeding edge kernel, but you *can* if you want or have problems with the standard one. And it doesn't change the rest of the system.
I see. I didn't mean to be rude, I'm sorry if it sounded that way. I'm a new Linux user, I did some did some tests to see what works for me so I can stick with. Some people say that bleeding edge distros make more sense for regular desktop use. For my use case, I disagree with that statement. But using a newer kernel, brought that idea to my mind. Anyway, you are right, it doesn't change the rest of the system, and it's a general kernel issue. So sticking with openSUSE is the right decision to make, especially that I can workaround this only issue I have with it. Thank you for your time, that was really helpful, and I would thank openSUSE team for this quality product. I will continue with this bug at bug#1159882. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1177541 Abdulrhman Ied <Abdulrhman.Ied@Gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Abdulrhman.Ied@Gmail.com -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com