June 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1184650] Kernel:HEAD should use tilde instead of dot/dash for version
by bugzilla_noreply＠suse.com 16 Jun '21

16 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1184650 https://bugzilla.suse.com/show_bug.cgi?id=1184650#c38 --- Comment #38 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-SU-2021:0873-1: An update that solves two vulnerabilities and has 57 fixes is now available. Category: security (important) Bug References: 1043990,1055117,1065729,1152457,1152489,1155518,1156395,1167260,1167574,1168838,1174416,1174426,1175995,1178089,1179243,1179851,1180846,1181161,1182613,1183063,1183203,1183289,1184208,1184209,1184436,1184485,1184514,1184585,1184650,1184724,1184728,1184730,1184731,1184736,1184737,1184738,1184740,1184741,1184742,1184760,1184811,1184893,1184934,1184942,1184957,1184969,1184984,1185041,1185113,1185233,1185244,1185269,1185365,1185454,1185472,1185491,1185549,1185586,1185587 CVE References: CVE-2021-29155,CVE-2021-29650 JIRA References: Sources used: openSUSE Leap 15.2 (src): kernel-rt-5.3.18-lp152.3.11.1, kernel-rt_debug-5.3.18-lp152.3.11.1, kernel-source-rt-5.3.18-lp152.3.11.1, kernel-syms-rt-5.3.18-lp152.3.11.1 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1184514] kernel-default-devel-5.11.11-1.2.x86_64 does not depend on kernel-default-5.11.11-1.2.x86_64
by bugzilla_noreply＠suse.com 16 Jun '21

16 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1184514 https://bugzilla.suse.com/show_bug.cgi?id=1184514#c59 --- Comment #59 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-SU-2021:0873-1: An update that solves two vulnerabilities and has 57 fixes is now available. Category: security (important) Bug References: 1043990,1055117,1065729,1152457,1152489,1155518,1156395,1167260,1167574,1168838,1174416,1174426,1175995,1178089,1179243,1179851,1180846,1181161,1182613,1183063,1183203,1183289,1184208,1184209,1184436,1184485,1184514,1184585,1184650,1184724,1184728,1184730,1184731,1184736,1184737,1184738,1184740,1184741,1184742,1184760,1184811,1184893,1184934,1184942,1184957,1184969,1184984,1185041,1185113,1185233,1185244,1185269,1185365,1185454,1185472,1185491,1185549,1185586,1185587 CVE References: CVE-2021-29155,CVE-2021-29650 JIRA References: Sources used: openSUSE Leap 15.2 (src): kernel-rt-5.3.18-lp152.3.11.1, kernel-rt_debug-5.3.18-lp152.3.11.1, kernel-source-rt-5.3.18-lp152.3.11.1, kernel-syms-rt-5.3.18-lp152.3.11.1 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1187264] [Build 20210611] [s390x] "Bad page state in process cc1plus pfn:fe401" during build of nodejs16
by bugzilla_noreply＠suse.com 16 Jun '21

16 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1187264 https://bugzilla.suse.com/show_bug.cgi?id=1187264#c24 --- Comment #24 from LTC BugProxy <bugproxy(a)us.ibm.com> --- ------- Comment From geraldsc(a)de.ibm.com 2021-06-16 14:30 EDT------- (In reply to comment #17) > > Which kernel version is this, and where can we find the corresponding source > > code? > Linux version: 5.12.9-1-default > > Tumbleweed is using the latest kernel source code from upstream. > Patched kernel sources are (master) here: https://github.com/openSUSE/kernel Hmm, I know and use that repo a lot, for SLES kernels, to get the source including all distro-specific add-on patches. I see no special tags or branches there for openSUSE releases, unlike SLES. So does that mean that you use the vanilla upstream version (tag v5.12.9 in this case) for openSUSE Tumbleweed, w/o any additional distro patches on top? But then what do you mean with "Patched kernel sources are (master) here"? The master branch in that repo is on 5.13-rc6 level... -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1187264] [Build 20210611] [s390x] "Bad page state in process cc1plus pfn:fe401" during build of nodejs16
by bugzilla_noreply＠suse.com 16 Jun '21

16 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1187264 https://bugzilla.suse.com/show_bug.cgi?id=1187264#c23 --- Comment #23 from LTC BugProxy <bugproxy(a)us.ibm.com> --- ------- Comment From cborntra(a)de.ibm.com 2021-06-16 14:02 EDT------- and what is the kvm host kernel version and the guest xml? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1187264] [Build 20210611] [s390x] "Bad page state in process cc1plus pfn:fe401" during build of nodejs16
by bugzilla_noreply＠suse.com 16 Jun '21

16 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1187264 https://bugzilla.suse.com/show_bug.cgi?id=1187264#c22 --- Comment #22 from LTC BugProxy <bugproxy(a)us.ibm.com> --- ------- Comment From cborntra(a)de.ibm.com 2021-06-16 13:53 EDT------- It might also be helpful to configure the kvm in a way to have a 2nd console redirected into a file e.g. add <console type='file'> <source path='/var/log/guest.log' append='on'/> <target type='sclplm' port='1'/> </console> to the libvirt xml to also have the line mode console (and then redirected to a file). Inside the guest you should add console=ttyS0 console=ttyS1 to the kernel command line to get kernel messages on both consoles. ------- Comment From cborntra(a)de.ibm.com 2021-06-16 13:55 EDT------- kernel loglevel on the kernel command line would be loglevel=7 (see Documentation/admin-guide/kernel-parameters.txt) ------- Comment From cborntra(a)de.ibm.com 2021-06-16 14:00 EDT------- Can you check the host dmesg for any error messages (or /var/log/libvirt/qemu/xxx.log ? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1187264] [Build 20210611] [s390x] "Bad page state in process cc1plus pfn:fe401" during build of nodejs16
by bugzilla_noreply＠suse.com 16 Jun '21

16 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1187264 https://bugzilla.suse.com/show_bug.cgi?id=1187264#c21 --- Comment #21 from LTC BugProxy <bugproxy(a)us.ibm.com> --- ------- Comment From cborntra(a)de.ibm.com 2021-06-16 13:36 EDT------- To get a normal ELF file dump you have to add --memory-only to the virsh dump command. This can be normally read with crash. Of course you then also need the debuginfo and vmlinux file for the kernel (this should be part of the rpms of 5.12.10-1-default if I read the logs properly) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1185513] ACPI BIOS Error after upgrade to 5.12.0-1-default
by bugzilla_noreply＠suse.com 16 Jun '21

16 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1185513 https://bugzilla.suse.com/show_bug.cgi?id=1185513#c68 --- Comment #68 from Frank Kr�ger <fkrueger(a)mailbox.org> --- FYI: The patch is now part of the upstream stable kernel 5.12.11. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1187264] [Build 20210611] [s390x] "Bad page state in process cc1plus pfn:fe401" during build of nodejs16
by bugzilla_noreply＠suse.com 16 Jun '21

16 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1187264 https://bugzilla.suse.com/show_bug.cgi?id=1187264#c18 --- Comment #18 from LTC BugProxy <bugproxy(a)us.ibm.com> --- ------- Comment From geraldsc(a)de.ibm.com 2021-06-16 10:33 EDT------- (In reply to comment #19) > the STATEFILE.gz is a qemu migrate-to-file so it's a full dump of the state > of the VM including memory. > > actually looking at a few of these stuck VMs the first BUG message printed > is not even a "Bad page state" but always seems to be "Bad rss-counter state" > > llvm11 build: > [ 3049s] [ 3032.903705] BUG: Bad rss-counter state mm:0000000077185176 > type:MM_FILEPAGES val:-432 > [11742s] [11725.874403] BUG: Bad page state in process clang++ pfn:1e0a01 > [11742s] [11725.874961] BUG: Bad page state in process clang++ pfn:1e0a02 > [11742s] [11725.876569] BUG: Bad page state in process clang++ pfn:1e0a03 > [11742s] [11725.877561] BUG: Bad page state in process clang++ pfn:1e0a04 > > mongodb build: > [ 229s] [ 218.670108] BUG: Bad rss-counter state mm:000000004cfc260c > type:MM_FILEPAGES val:-256 > [ 315s] [ 304.902152] BUG: Bad page state in process cc1plus pfn:148101 > [ 315s] [ 304.903082] BUG: Bad page state in process cc1plus pfn:148102 > [ 315s] [ 304.904555] BUG: Bad page state in process cc1plus pfn:148103 > [ 315s] [ 304.905273] BUG: Bad page state in process cc1plus pfn:148104 > [ 315s] [ 304.906991] BUG: Bad page state in process cc1plus pfn:148105 > > cross-arm-none-gcc11-bootstrap: > [ 320s] [ 281.035581] BUG: Bad rss-counter state mm:00000000a12d99da > type:MM_FILEPAGES val:-256 > [ 1113s] [ 1074.149241] BUG: Bad page state in process cc1plus pfn:13ff01 > [ 1113s] [ 1074.150288] BUG: Bad page state in process cc1plus pfn:13ff02 > [ 1113s] [ 1074.150718] BUG: Bad page state in process cc1plus pfn:13ff03 > [ 1113s] [ 1074.150884] BUG: Bad page state in process cc1plus pfn:13ff04 > Again, those messages do not show the complete picture, probably because you only collect certain loglevels. A simple dmesg output, containing _all_ the kernel messages would be the very least, for all kind of kernel problems that you want to report. A (proper) dump might also not give more information than this, if it was not collected at the exact time where the problem occurred, which is of course not possible if the kernel does not panic at this time. > # A proper dump would contain a vmcore plus a vmlinux with debuginfo. > > that would be kdump, but there is no easy way to set this up for our on the > fly created VMs. The dump that I created was done with qemu migrating the > stuck VM to a file. OK, could you please give some instruction on how I would be able to open this with crash for analysis? To my knowledge, I would certainly always need at least the vmlinux with debuginfo, which is missing (or is it?), but I never had to look into qemu dumps. Or, just forget about that dump, which would be after-the-facts anyway, and simply provide the dmesg output? BTW, is this easily reproducible, and can you verify if it also occurs with THP disabled? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1187264] [Build 20210611] [s390x] "Bad page state in process cc1plus pfn:fe401" during build of nodejs16
by bugzilla_noreply＠suse.com 16 Jun '21

16 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1187264 https://bugzilla.suse.com/show_bug.cgi?id=1187264#c16 --- Comment #16 from Ruediger Oertel <ro(a)suse.com> --- # A proper dump would contain a vmcore plus a vmlinux with debuginfo. that would be kdump, but there is no easy way to set this up for our on the fly created VMs. The dump that I created was done with qemu migrating the stuck VM to a file. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1187264] [Build 20210611] [s390x] "Bad page state in process cc1plus pfn:fe401" during build of nodejs16
by bugzilla_noreply＠suse.com 16 Jun '21

16 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1187264 https://bugzilla.suse.com/show_bug.cgi?id=1187264#c15 --- Comment #15 from Ruediger Oertel <ro(a)suse.com> --- the STATEFILE.gz is a qemu migrate-to-file so it's a full dump of the state of the VM including memory. actually looking at a few of these stuck VMs the first BUG message printed is not even a "Bad page state" but always seems to be "Bad rss-counter state" llvm11 build: [ 3049s] [ 3032.903705] BUG: Bad rss-counter state mm:0000000077185176 type:MM_FILEPAGES val:-432 [11742s] [11725.874403] BUG: Bad page state in process clang++ pfn:1e0a01 [11742s] [11725.874961] BUG: Bad page state in process clang++ pfn:1e0a02 [11742s] [11725.876569] BUG: Bad page state in process clang++ pfn:1e0a03 [11742s] [11725.877561] BUG: Bad page state in process clang++ pfn:1e0a04 mongodb build: [ 229s] [ 218.670108] BUG: Bad rss-counter state mm:000000004cfc260c type:MM_FILEPAGES val:-256 [ 315s] [ 304.902152] BUG: Bad page state in process cc1plus pfn:148101 [ 315s] [ 304.903082] BUG: Bad page state in process cc1plus pfn:148102 [ 315s] [ 304.904555] BUG: Bad page state in process cc1plus pfn:148103 [ 315s] [ 304.905273] BUG: Bad page state in process cc1plus pfn:148104 [ 315s] [ 304.906991] BUG: Bad page state in process cc1plus pfn:148105 cross-arm-none-gcc11-bootstrap: [ 320s] [ 281.035581] BUG: Bad rss-counter state mm:00000000a12d99da type:MM_FILEPAGES val:-256 [ 1113s] [ 1074.149241] BUG: Bad page state in process cc1plus pfn:13ff01 [ 1113s] [ 1074.150288] BUG: Bad page state in process cc1plus pfn:13ff02 [ 1113s] [ 1074.150718] BUG: Bad page state in process cc1plus pfn:13ff03 [ 1113s] [ 1074.150884] BUG: Bad page state in process cc1plus pfn:13ff04 -- You are receiving this mail because: You are the assignee for the bug.

1 0