July 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1188896] "BUG: Bad rss-counter state mm:00000000e555b579 type:MM_FILEPAGES val:-256" during build of cross-epiphany-gcc11-bootstrap
by bugzilla_noreply＠suse.com 30 Jul '21

30 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188896 https://bugzilla.suse.com/show_bug.cgi?id=1188896#c6 --- Comment #6 from Sarah Kriesch <ada.lovelace(a)gmx.de> --- (In reply to LTC BugProxy from comment #3) > ------- Comment From geraldsc(a)de.ibm.com 2021-07-30 08:13 EDT------- > (In reply to comment #4) > [...] > > > > Kernel version: 5.13.4-1.1: > > https://github.com/openSUSE/kernel/releases/tag/v5.13.4 > > Is openSUSE really running a stock stable kernel version, w/o any additional > patches on top? I might have asked that before, but I do not really > remember. If the answer is "no", then there is no use posting such links. > > What we would need is some link to openSUSE kernel source including all SUSE > add-on patches, similar to what you have for SLES, or at least the link to > the kernel source rpms. That is exactly what I have asked a SUSE Kernel Developer after our last bug report. The kernel of openSUSE Tumbleweed is based on the master branch of the openSUSE kernel repository updated by our Kernel Developers. If you are looking for any specific version used in OBS, then you can look for the specific tagged versions. That is the "Best Practice". openSUSE Tumbleweed is developed with latest kernel releases. If they are stable enough, then they are used for openSUSE Tumbleweed and builds. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188896] "BUG: Bad rss-counter state mm:00000000e555b579 type:MM_FILEPAGES val:-256" during build of cross-epiphany-gcc11-bootstrap
by bugzilla_noreply＠suse.com 30 Jul '21

30 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188896 https://bugzilla.suse.com/show_bug.cgi?id=1188896#c5 --- Comment #5 from Sarah Kriesch <ada.lovelace(a)gmx.de> --- > What is this link supposed to point at? I see only this error > "anonymous_user(Anonymous user is not allowed here - please login)". > A kernel dmesg log would be useful, but of course, as always, w/o a proper > kernel dump including kernel debuginfo not much progress can be expected > here. > > Also, there is no sign of any s390-specific issues here, seems more like > some common memory management issue. But of course this is really hard to > tell w/o (at the very least) complete kernel dmesg log. > > Last but not least, gcc build is only the workload triggering the kernel > bug, so no gcc issue here. Shouldn't be a memory issue have got a "Out of memory" as an output instead of "BUG"? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188896] "BUG: Bad rss-counter state mm:00000000e555b579 type:MM_FILEPAGES val:-256" during build of cross-epiphany-gcc11-bootstrap
by bugzilla_noreply＠suse.com 30 Jul '21

30 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188896 https://bugzilla.suse.com/show_bug.cgi?id=1188896#c4 --- Comment #4 from Sarah Kriesch <ada.lovelace(a)gmx.de> --- Created attachment 851440 --> https://bugzilla.suse.com/attachment.cgi?id=851440&action=edit cross-epiphany-gcc11-bootstrap.log Sorry! 2 weeks ago it was possible to read our build logs in OBS without any openSUSE user account. Other upstream project members were able to read that, too. I will create a bug report because of that. The log file is attached now. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188896] "BUG: Bad rss-counter state mm:00000000e555b579 type:MM_FILEPAGES val:-256" during build of cross-epiphany-gcc11-bootstrap
by bugzilla_noreply＠suse.com 30 Jul '21

30 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188896 https://bugzilla.suse.com/show_bug.cgi?id=1188896#c3 --- Comment #3 from LTC BugProxy <bugproxy(a)us.ibm.com> --- ------- Comment From geraldsc(a)de.ibm.com 2021-07-30 08:13 EDT------- (In reply to comment #4) [...] > > Kernel version: 5.13.4-1.1: > https://github.com/openSUSE/kernel/releases/tag/v5.13.4 Is openSUSE really running a stock stable kernel version, w/o any additional patches on top? I might have asked that before, but I do not really remember. If the answer is "no", then there is no use posting such links. What we would need is some link to openSUSE kernel source including all SUSE add-on patches, similar to what you have for SLES, or at least the link to the kernel source rpms. > > Logs: > https://build.opensuse.org/build/openSUSE:Factory:zSystems/standard/s390x/ > cross-epiphany-gcc11-bootstrap/_log What is this link supposed to point at? I see only this error "anonymous_user(Anonymous user is not allowed here - please login)". A kernel dmesg log would be useful, but of course, as always, w/o a proper kernel dump including kernel debuginfo not much progress can be expected here. Also, there is no sign of any s390-specific issues here, seems more like some common memory management issue. But of course this is really hard to tell w/o (at the very least) complete kernel dmesg log. Last but not least, gcc build is only the workload triggering the kernel bug, so no gcc issue here. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1184804] move kernel out of /boot
by bugzilla_noreply＠suse.com 30 Jul '21

30 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1184804 https://bugzilla.suse.com/show_bug.cgi?id=1184804#c58 --- Comment #58 from Ludwig Nussel <lnussel(a)suse.com> --- (In reply to Michal Suchanek from comment #54) > [..] > If anything it should be > > Conflicts: filesystem < 16 > > and in any case it assumes the future v16 which is not yet released is > usrmerged. Although it's likely we just don't know at this point. Ah, yes of course. Whatever the next version might be we have to assume it increases the major version by at least one :-) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1184804] move kernel out of /boot
by bugzilla_noreply＠suse.com 30 Jul '21

30 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1184804 https://bugzilla.suse.com/show_bug.cgi?id=1184804#c57 --- Comment #57 from Ludwig Nussel <lnussel(a)suse.com> --- (In reply to Jiri Slaby from comment #53) > (In reply to Ludwig Nussel from comment #51) > > (In reply to Takashi Iwai from comment #49) > > > Well, the point is how to detect and conflict if a package is for UsrMerge > > > but the installed system isn't. People try to update a firmware package > > > built for TW onto a Leap system like before, and it breaks suddenly now. > > > > Can happen with anything you take from TW. Packages are hardly strictly tied > > to a specific distro. > > But the kernel is different. We always advertised Kernel:* can be installed > on any distro... Well, in the case here you can. It's just not guaranteed that it works without adding some compat symlinks or install other adjusted userspace tooling. The safeguards discussed here ie conflicting with the filesystem package actually do prevent installation on older distros though (or cause severe havoc if someone tries to "fix" that by installing filesystem). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1184804] move kernel out of /boot
by bugzilla_noreply＠suse.com 30 Jul '21

30 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1184804 https://bugzilla.suse.com/show_bug.cgi?id=1184804#c56 --- Comment #56 from Ludwig Nussel <lnussel(a)suse.com> --- (In reply to Steffen Winterfeldt from comment #52) > Cannot filesystem provide, say, 'usrmerge' and you Require or Conflict that > instead of some number? Usually you do not require the filesystem package at all. So would have to use boolean deps ie something like Conflicts: (filesystem without usrmerge). No idea if that actually works, never tried. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188896] "BUG: Bad rss-counter state mm:00000000e555b579 type:MM_FILEPAGES val:-256" during build of cross-epiphany-gcc11-bootstrap
by bugzilla_noreply＠suse.com 30 Jul '21

30 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188896 LTC BugProxy <bugproxy(a)us.ibm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.linux.ibm. | |com/show_bug.cgi?id=193804 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1183890] [Build 20210320] openQA test fails in welcome - NET ISO is stuck on linuxrc blue screen
by bugzilla_noreply＠suse.com 30 Jul '21

30 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1183890 https://bugzilla.suse.com/show_bug.cgi?id=1183890#c11 --- Comment #11 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: create_hdd_tumbleweed https://openqa.opensuse.org/tests/1858184 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1184924] [Build 134.3] openQA test fails in kdump_and_crash - forced crash didn't result into expected reboot
by bugzilla_noreply＠suse.com 30 Jul '21

30 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1184924 https://bugzilla.suse.com/show_bug.cgi?id=1184924#c9 --- Comment #9 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: jeos-extra@aarch64-HD24G https://openqa.opensuse.org/tests/1858533 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are the assignee for the bug.

1 0