[Bug 1139325] New: rPi installer OOM crash
http://bugzilla.suse.com/show_bug.cgi?id=1139325 Bug ID: 1139325 Summary: rPi installer OOM crash Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers@suse.de Reporter: msuchanek@suse.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- Created attachment 808442 --> http://bugzilla.suse.com/attachment.cgi?id=808442&action=edit yast log When installing on Raspberry Pi the installer is killed by OOM killer. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1139325 http://bugzilla.suse.com/show_bug.cgi?id=1139325#c1 --- Comment #1 from Michal Suchanek <msuchanek@suse.com> --- Workaround: enable swap from another medium. I install from USB stick so added a swap partition after the partition containing the ISO image data. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1139325 http://bugzilla.suse.com/show_bug.cgi?id=1139325#c2 Steffen Winterfeldt <snwint@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low Status|NEW |CONFIRMED URL| |https://trello.com/c/KGWfeO | |ts Assignee|yast2-maintainers@suse.de |yast-internal@suse.de --- Comment #2 from Steffen Winterfeldt <snwint@suse.com> --- Tracking in YaST Scrum board. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1139325 Steffen Winterfeldt <snwint@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P4 - Low |P2 - High Summary|rPi installer OOM crash |installation failing with | |1GB memory -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1139325 http://bugzilla.suse.com/show_bug.cgi?id=1139325#c3 Steffen Winterfeldt <snwint@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt@suse.com --- Comment #3 from Steffen Winterfeldt <snwint@suse.com> --- *** Bug 1140037 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1139325 http://bugzilla.suse.com/show_bug.cgi?id=1139325#c4 --- Comment #4 from Steffen Winterfeldt <snwint@suse.com> --- We have now two reports of this kind, on aarch64 and x86 - raising priority. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1139325 http://bugzilla.suse.com/show_bug.cgi?id=1139325#c5 --- Comment #5 from Ladislav Slezák <lslezak@suse.com> --- The last line in the log is: 2019-06-25 14:58:32 <1> dhcp128(3262) [Ruby] modules/InstExtensionImage.rb:386 Calling: /bin/extend 'cracklib-dict-full.rpm' Which means YaST wants to extend the inst-sys with the cracklib data, that unpacks about 10MB data... But the problem probably happens earlier: 2019-05-20 09:01:59 <1> dhcp128(3262) [Ruby] modules/Progress.rb:344 Progress::New(Writing List of Online Repositories, 5, ["Add repository: Main Repository (DEBUG)", "Add repository: Main Repository (Sources)", "Add repository: Main Repository (NON-OSS)", "Add repository: Main Repository (OSS)", "Add repository: Main Update Repository"]) So quite a lot of online repositories were used, these take quite a lot of RAM. We actually display a warning (https://github.com/yast/yast-packager/blob/master/src/lib/y2packager/clients...) when we detect a low memory system But in this case the memory size *exactly* matches the limit when the warning is not yet displayed. So in this case it would be enough to change the condition from if detected < limit to if detected <= limit (https://github.com/yast/yast-packager/blob/master/src/lib/y2packager/clients...) But IIRC with only OSS, NonOSS and Updates (without Debug and Sources) it should work fine... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1139325 http://bugzilla.suse.com/show_bug.cgi?id=1139325#c6 --- Comment #6 from Michal Suchanek <msuchanek@suse.com> --- (In reply to Ladislav Slezák from comment #5)
We actually display a warning (https://github.com/yast/yast-packager/blob/master/src/lib/y2packager/ clients/inst_productsources.rb#L1699) when we detect a low memory system
But in this case the memory size *exactly* matches the limit when the warning is not yet displayed.
This is probably no accident. rPi 3 is a supported platform so the installer is supposed to work on it.
But IIRC with only OSS, NonOSS and Updates (without Debug and Sources) it should work fine...
It also works fine offline without any online repositories. The problem is you can select these repositories and then the installer crashes. It could disable some with low memory, it could detect oom before it's too late, it could add swap. Whatever it is it should not rely on user not checking a checkbox which does not have "Don't use, this will crash your system" written next to it. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1139325 https://bugzilla.suse.com/show_bug.cgi?id=1139325#c7 Ladislav Slez�k <lslezak@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #7 from Ladislav Slez�k <lslezak@suse.com> --- I have adjusted the memory check as mentioned in comment #5, https://github.com/yast/yast-packager/pull/576 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1139325 https://bugzilla.suse.com/show_bug.cgi?id=1139325#c10 Fabian Vogt <fvogt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #10 from Fabian Vogt <fvogt@suse.com> --- The openQA tests in TW stagings run with exactly 1024MiB of RAM, so YaST runs into this condition there. It actually found a (minor) bug: https://openqa.opensuse.org/tests/1879992#step/online_repos/2 It still says "has less than 1024MiB of memory", which is not true anymore and should be updated to reflect the changed check. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1139325 https://bugzilla.suse.com/show_bug.cgi?id=1139325#c11 --- Comment #11 from Lukas Ocilka <locilka@suse.com> --- total used free shared buff/cache available Mem: 987204 641252 63424 704 282528 182328 Swap: 2573304 326912 2246392 Does not look like a 1 GB exactly -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1139325 https://bugzilla.suse.com/show_bug.cgi?id=1139325#c12 --- Comment #12 from Fabian Vogt <fvogt@suse.com> --- (In reply to Lukas Ocilka from comment #11)
total used free shared buff/cache available Mem: 987204 641252 63424 704 282528 182328 Swap: 2573304 326912 2246392
Does not look like a 1 GB exactly
QEMU is started with "-m 1024" and the message only appears with that particular yast2-packager submission. I suppose the output of "free" has reserved memory areas (firmware, kernel) already subtracted, but YaST looks at the physical memory configuration. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1139325 https://bugzilla.suse.com/show_bug.cgi?id=1139325#c16 --- Comment #16 from Ladislav Slez�k <lslezak@suse.com> --- Yes, different systems might have different size of reserved memory. But this is just a rough estimation anyway, different kernel, drivers, glibc, X, Qt,... might also have different memory requirements. It also depends how big the additional repositories are, etc... So many factors, that's why YaST just warns "it might crash". It's up to the user to decide, and if it does not work then just restart the installer and try it again without the online repositories. That's all what we can do. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1139325 https://bugzilla.suse.com/show_bug.cgi?id=1139325#c17 Ladislav Slez�k <lslezak@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #17 from Ladislav Slez�k <lslezak@suse.com> --- (In reply to Fabian Vogt from comment #10)
The openQA tests in TW stagings run with exactly 1024MiB of RAM, so YaST runs into this condition there.
It actually found a (minor) bug: https://openqa.opensuse.org/tests/1879992#step/online_repos/2
It still says "has less than 1024MiB of memory", which is not true anymore and should be updated to reflect the changed check.
The message has been fixed in yast2-packager-4.4.11 (https://github.com/yast/yast-packager/pull/588) -- You are receiving this mail because: You are on the CC list for the bug.
participants (2)
-
bugzilla_noreply＠novell.com -
bugzilla_noreply＠suse.com