June 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1187195] tumbleweed battery drain
by bugzilla_noreply＠suse.com 17 Jun '21

17 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1187195 https://bugzilla.suse.com/show_bug.cgi?id=1187195#c12 --- Comment #12 from Sebastian Turza��ski <dpbasti(a)wp.pl> --- (In reply to Takashi Iwai from comment #11) > And, if it's about the iwlwifi, it might be worth to try to change the > firmware files. The firmware files are found in linux-firmware git > repository, and you can take the older versions from there, too. I tried that - no help I made some other observations - I think the total power consumption is just much higher and somehow powertop tries to find a a victim to blame. SOmetimes it says it's because of display backlight even if I put it to 5% brightness. Even more WHen I plugged an usb dock/hub with ethernet and usb keyboard it started to report several Wats ! on keyboard . In other case on usb drive in other case on ethernet adapter. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1187195] tumbleweed battery drain
by bugzilla_noreply＠suse.com 17 Jun '21

17 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1187195 https://bugzilla.suse.com/show_bug.cgi?id=1187195#c11 --- Comment #11 from Takashi Iwai <tiwai(a)suse.com> --- And, if it's about the iwlwifi, it might be worth to try to change the firmware files. The firmware files are found in linux-firmware git repository, and you can take the older versions from there, too. -- 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 17 Jun '21

17 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1187264 https://bugzilla.suse.com/show_bug.cgi?id=1187264#c36 --- Comment #36 from LTC BugProxy <bugproxy(a)us.ibm.com> --- ------- Comment From cborntra(a)de.ibm.com 2021-06-17 12:18 EDT------- > now after looking up kernel parameters I've added a "loglevel=4" to maybe > also get the KERN_WARNING messages Please also remove the "quiet". -- 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 17 Jun '21

17 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1187264 https://bugzilla.suse.com/show_bug.cgi?id=1187264#c35 --- Comment #35 from Ruediger Oertel <ro(a)suse.com> --- for comments 22 ... there is no libvirt involved, this is plain qemu. cmdline looks like this: /usr/bin/qemu-system-s390x -nodefaults -no-reboot -nographic -vga none -cpu host -enable-kvm -object rng-random,filename=/dev/random,id=rng0 -device virtio-rng-ccw,rng=rng0 -runas qemu -net none -kernel /var/cache/obs/worker/root_1/.mount/boot/kernel -initrd /var/cache/obs/worker/root_1/.mount/boot/initrd -append "root=/dev/disk/by-id/virtio-0 rootfstype=ext4 rootflags=noatime ext4.allow_unsupported=1 mitigations=off panic=1 quiet no-kvmclock elevator=noop nmi_watchdog=0 rw rd.driver.pre=binfmt_misc console=hvc0 init=/.build/build" -m 8192 -drive file=/var/cache/obs/worker/root_1/root,format=raw,if=none,id=disk,cache=unsafe -device virtio-blk-ccw,drive=disk,serial=0 -drive file=/var/cache/obs/worker/root_1/swap,format=raw,if=none,id=swap,cache=unsafe -device virtio-blk-ccw,drive=swap,serial=1 -device virtio-serial-ccw -device virtconsole,chardev=virtiocon0 -chardev stdio,mux=on,id=virtiocon0 -mon chardev=virtiocon0 -chardev socket,id=monitor,server,nowait,path=/var/cache/obs/worker/root_1/root.qemu/monitor -mon chardev=monitor,mode=readline -smp 4 now after looking up kernel parameters I've added a "loglevel=4" to maybe also get the KERN_WARNING messages -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1187383] Leap 15.3: can't remove kernel-default-5.3.18 without also removing other kernel
by bugzilla_noreply＠suse.com 17 Jun '21

17 Jun '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1187383 http://bugzilla.opensuse.org/show_bug.cgi?id=1187383#c10 Diethard Janssen <linux(a)ljapunow.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |linux(a)ljapunow.de --- Comment #10 from Diethard Janssen <linux(a)ljapunow.de> --- It seems that also at least correct syms and default-base are missing when installing linux kernel development. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1186692] New: CDC ACM speed regression from LEAP 15.2 Kernel 5.3 to KOTD
by bugzilla_noreply＠suse.com 17 Jun '21

17 Jun '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1186692 Bug ID: 1186692 Summary: CDC ACM speed regression from LEAP 15.2 Kernel 5.3 to KOTD Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: bon(a)elektron.ikp.physik.tu-darmstadt.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The blackmagic debug probe https://gith.im/blacksphere/blackmagic is a JTAG/SWD debugger that provides GDB server running on a microcontroller, talking to the debug device via JTAG/SWD and exposing the GDB server via a CDC ACM modem implementation. Blackmagic hosted is a PC program that talks to debugger via an additional remote protocol implemented on microcontroller, using the same CDCACM implementation. E.g reading from the device is done in bigger chunks, not single words. Running on KOTD (exactly 5.13.0-rc4-1.g1c805bd-default) read speed dropped about 1/3: Reading flash from 0x08000000 for 1048576 bytes to /tmp/bla Read/Verify succeeded for 1048576 bytes, 52.020 kiB/s while with 5.3 it is above 85 kiB/s or even about 100 kiB/s on a newer USB chipset. strace brings down the speed substantial, so I do not think that is useful for debugging the problem. Hints and help welcome. -- You are receiving this mail because: You are the assignee for the bug.

1 11

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

17 Jun '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1185513 Bug ID: 1185513 Summary: ACPI BIOS Error after upgrade to 5.12.0-1-default Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: iqgrande(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I recently updated to the 5.12.0-1-default kernel with openSUSE Tumbleweed and now I see the following messages during boot. These were not there before. The system seems to be fully functioning. There are updates to the BIOS I could try (however I'm afraid to as I've been burned updating the BIOS before) however I thought I'd start here first since it was the Linux kernel change (or whatever else came in the update this morning) that prompted it. Are there any thoughts on this? Thank you for your help with this. {{{ > dmesg | grep AE_NOT_FOUND [ 1.149107] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210105/psargs-330) [ 1.149136] ACPI Error: Aborting method \_PR.PR01._CPC due to previous error (AE_NOT_FOUND) (20210105/psparse-529) [ 1.149187] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210105/psargs-330) [ 1.149212] ACPI Error: Aborting method \_PR.PR02._CPC due to previous error (AE_NOT_FOUND) (20210105/psparse-529) [ 1.149262] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210105/psargs-330) [ 1.149287] ACPI Error: Aborting method \_PR.PR03._CPC due to previous error (AE_NOT_FOUND) (20210105/psparse-529) [ 1.149335] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210105/psargs-330) [ 1.149360] ACPI Error: Aborting method \_PR.PR04._CPC due to previous error (AE_NOT_FOUND) (20210105/psparse-529) [ 1.149408] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210105/psargs-330) [ 1.149433] ACPI Error: Aborting method \_PR.PR05._CPC due to previous error (AE_NOT_FOUND) (20210105/psparse-529) [ 1.149481] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210105/psargs-330) [ 1.149506] ACPI Error: Aborting method \_PR.PR06._CPC due to previous error (AE_NOT_FOUND) (20210105/psparse-529) [ 1.149553] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210105/psargs-330) [ 1.149578] ACPI Error: Aborting method \_PR.PR07._CPC due to previous error (AE_NOT_FOUND) (20210105/psparse-529) [ 1.149626] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210105/psargs-330) [ 1.149650] ACPI Error: Aborting method \_PR.PR08._CPC due to previous error (AE_NOT_FOUND) (20210105/psparse-529) [ 1.149698] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210105/psargs-330) [ 1.149723] ACPI Error: Aborting method \_PR.PR09._CPC due to previous error (AE_NOT_FOUND) (20210105/psparse-529) [ 1.149770] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210105/psargs-330) [ 1.149794] ACPI Error: Aborting method \_PR.PR10._CPC due to previous error (AE_NOT_FOUND) (20210105/psparse-529) [ 1.149842] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210105/psargs-330) [ 1.149867] ACPI Error: Aborting method \_PR.PR11._CPC due to previous error (AE_NOT_FOUND) (20210105/psparse-529) }}} -- You are receiving this mail because: You are the assignee for the bug.

1 33

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

17 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1187264 https://bugzilla.suse.com/show_bug.cgi?id=1187264#c29 --- Comment #29 from LTC BugProxy <bugproxy(a)us.ibm.com> --- ------- Comment From geraldsc(a)de.ibm.com 2021-06-17 10:15 EDT------- (In reply to comment #32) [...] > So, I decided to help myself, and found at least some rpms which you can use > to extract the source: > http://download.opensuse.org/tumbleweed/repo/oss/noarch/ > You need kernel-devel and kernel-source noarch.rpm, just like with SLES. A > proper git access similar to SLES would of course be nice, but the rpms are > surely better than nothing. Oh well, that would have been to easy I guess. The rpms for 5.12.10-1 are still accessible, but those for 5.12.9-1 (which seems to be the version you were using) just give a 404 error. I guess you can only download the latest version, but you probably will also see the problem with 5.12.10-1, correct? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1187454] kernel: iwlwifi 0000:03:00.0: api flags index 2 larger than supported by driver
by bugzilla_noreply＠suse.com 17 Jun '21

17 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1187454 https://bugzilla.suse.com/show_bug.cgi?id=1187454#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com, | |Ulrich.Windl(a)rz.uni-regensb | |urg.de Flags| |needinfo?(Ulrich.Windl(a)rz.u | |ni-regensburg.de) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- The message sounds like a firmware bug. Could you try the latest kernel-firmware-iwlwifi in OBS Kernel:HEAD repo? -- 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 17 Jun '21

17 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1187264 https://bugzilla.suse.com/show_bug.cgi?id=1187264#c28 --- Comment #28 from LTC BugProxy <bugproxy(a)us.ibm.com> --- ------- Comment From geraldsc(a)de.ibm.com 2021-06-17 10:04 EDT------- (In reply to comment #30) > openSUSE is working (the same as SUSE) with Upstream/Factory first. > openSUSE Tumbleweed for s390x is based on Factory. openSUSE Leap is using > the same base packages as SLES (incl. kernel) since our 15.3 (equal to 15 > SP3) release. > Therefore, it is correct that SLES kernel patches will be available in our > stable release openSUSE Leap, too. That is a closed partnership. SUSE is > giving something (kernel and stable base) to openSUSE. openSUSE is giving > applications and the latest packages to SLES. > SUSE Kernel Developers are testing in their home branches of OBS the latest > kernel sources (together with patches). IIf it is working as expected, that > will be submitted to Factory (Tumbleweed). We have got a review process with > multiple stages. That can take some days. If that all has been passed, then > we will receive a new kernel in our rolling release openSUSE Tumbleweed. > That is one reason that openSUSE Tumbleweed is recommended for Developers. > We are receiving all with possible latest versions from upstream. > Leap and SLES are one fork of Tumbleweed with more stability from the > Enterprise. > > (In reply to LTC BugProxy from comment #24) > > (In reply to comment #17) > > > > Which kernel version is this, and where can we find the corresponding source > > > > code? > > 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... > The openSUSE kernel is maintained by SUSE Kernel Developers. Therefore, the > upstream version is in a testing phase and has to pass our multiple staging > and review stages. Then we will receive this new kernel (from master) as a > new rolling release kernel version. > > I heard a nice joke from a conference: > The openSUSE/SUSE chameleon is a penguin with many SUSE kernel patches. Sorry, I cannot make any sense of this, or see how it would answer the (very simple) question "where can we find the matching kernel source for the kernel version that showed the problem". So, I decided to help myself, and found at least some rpms which you can use to extract the source: http://download.opensuse.org/tumbleweed/repo/oss/noarch/ You need kernel-devel and kernel-source noarch.rpm, just like with SLES. A proper git access similar to SLES would of course be nice, but the rpms are surely better than nothing. Feel free to bookmark this, just in case anybody should ask you that question again in the future. If we now could also get the kernel messages, we would also know (for sure) which kernel version you were using, and also see why the kernel thinks that it found bad pages or rss-counters. Please also try to answer the question about the host kernel version, as we won't be able to see that from the guest kernel messages. If you find the time, reproduction with THP disabled would also be appreciated, but that is more out of curiosity, and won't (immediately) help to make any progress, as opposed to the other questions. -- You are receiving this mail because: You are the assignee for the bug.

1 0