November 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1192714] [Build 20211114] podman tests triggering gpf in kernel 5.15.1
by bugzilla_noreply＠suse.com 18 Nov '21

18 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192714 https://bugzilla.suse.com/show_bug.cgi?id=1192714#c16 --- Comment #16 from Jan Kara <jack(a)suse.com> --- Hmm, I was trying for some time but for some reason the problem does not reproduce for me when I run the VM from your image on my test host. Not sure why is that. I've also looked into the code and the refcounting of blkg's inside BFQ looks rather straightforward and I didn't find any problem there. Any chance for triggering a crashdump when the problem happens so that we can poke around memory? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192767] Kernel boot logging gets mixed up when bringing up CPUs on SMP system
by bugzilla_noreply＠suse.com 18 Nov '21

18 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192767 https://bugzilla.suse.com/show_bug.cgi?id=1192767#c10 --- Comment #10 from Archie Cobbs <archie.cobbs(a)gmail.com> --- > That said. It would be easy to make the loglevel consistent here. But there will be another 2000 pr_cont() calls that might cause the same problem. And there is no simple generic solution. ��A journey of a thousand miles begins with a single step�� - Chinese proverb -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192767] Kernel boot logging gets mixed up when bringing up CPUs on SMP system
by bugzilla_noreply＠suse.com 18 Nov '21

18 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192767 https://bugzilla.suse.com/show_bug.cgi?id=1192767#c9 --- Comment #9 from Petr Mladek <pmladek(a)suse.com> --- (In reply to Archie Cobbs from comment #4) > But to be clear there are two bugs here... > > #1 Bogus promotion from INFO to WARN This "bug" can be fixed by using pr_cont(KERN_INFO "...") instead of plain pr_cont("..."). This notation has been supported by commit 4bcc595ccd80decb424509 ("printk: reinstate KERN_CONT for printing continuation lines") since kernel 4.9. But I do not see it used anywhere: $> git grep pr_cont\( | wc -l 1977 $> git grep pr_cont\(KERN_ | wc -l 0 Why? My guess is that it is because: + pr_cont() mostly works + it would be an extra work to keep loglevel of all the related pr_cont() pieces in sync + nobody cared enough to fix location where it did not work + many people do not know about the notation We might make it easier to use it by introducing pr_cont_<level>() wrappers. But will people use them? I do not know. There were some ideas to support continuous lines another way. For example, create an API that would use some local buffer on stack and explicitely flush it when the string is complete. But nobody cared enough to implement it. Also it would be more complicated to use and error prone. And any local buffering might cause that the message will never reach the main log buffer when something gets wrong. From my point of view. It is an aesthetic issue that it not worth fixing. The fix might do more harm than good. > #2 Broken formatting if there are any per-CPU log messages One possibility would be to print each CPU on a separate line. But it would look ugly on systems with many CPUs. Also it would create problems with slow consoles (softlockups, lost messages). Another possibility would be to use a local buffer and print the line when it is complete. But it would make it harder to debug when something went wrong in the middle. Interleaving with other messages helps to find correlation with between various events/problems on the system. It is even the case here. The interleaving helps to understand that "Disabled fast string operations" is printed for each initialized CPU. > Both bugs should be fixed. Any solution has its drawbacks. IMHO, the current code is a good compromise as long as the list of CPU IDs is interleaved only rarely. That said. It would be easy to make the loglevel consistent here. But there will be another 2000 pr_cont() calls that might cause the same problem. And there is no simple generic solution. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192473] DE0-Nano-SoC boot fails on 15.3
by bugzilla_noreply＠suse.com 18 Nov '21

18 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192473 https://bugzilla.suse.com/show_bug.cgi?id=1192473#c15 --- Comment #15 from Christian Gross <christian.gross(a)centerofgravity.at> --- This kernel is also booting. And it looks like a very good solution. ... [ OK ] Reached target Timers. Welcome to openSUSE Leap 15.2 - Kernel 5.3.18-3.g07d0aaa-default (ttyS0). localhost login: -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191795] Ethernet (RJ45) Not Detected
by bugzilla_noreply＠suse.com 18 Nov '21

18 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1191795 https://bugzilla.suse.com/show_bug.cgi?id=1191795#c37 --- Comment #37 from Oliver Neukum <oneukum(a)suse.com> --- Please conduct the following test. In the description I am assuming that your interface is named enp5s0. If it isn't, please replace the name. 1. Do not use TLP 2. Unplug the RJ45 on the laptop's side 3 Do: ethtool -s enp5s0 wol p 4: Suspend your laptop 5. Wait 60s 6. Plug the cable back in If it does not wake up from the plug, repeat the test with ethtool -s enp5s0 wol umb and report the result. To get your system back to normal do: ethtool -s enp5s0 wol d -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191795] Ethernet (RJ45) Not Detected
by bugzilla_noreply＠suse.com 18 Nov '21

18 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1191795 https://bugzilla.suse.com/show_bug.cgi?id=1191795#c36 --- Comment #36 from Oliver Neukum <oneukum(a)suse.com> --- OK, another extremely specific question. What is on the other end of the ethernet cable when you do that experiment? Are they in a hub or switch or do you dangle them in the air? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192118] [Build 20211027] openQA test fails in finit_module02
by bugzilla_noreply＠suse.com 18 Nov '21

18 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192118 https://bugzilla.suse.com/show_bug.cgi?id=1192118#c5 --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- .. or do you mean that this is triggered by other (SLE) release? If so, we may need backport. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191795] Ethernet (RJ45) Not Detected
by bugzilla_noreply＠suse.com 18 Nov '21

18 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1191795 https://bugzilla.suse.com/show_bug.cgi?id=1191795#c35 --- Comment #35 from Oliver Neukum <oneukum(a)suse.com> --- Please provide the output of "ethtool NAMEOFFAILINGDEVICE" while in the state plug ins are not recognized. To explain: The device implements runtime power management setting its WOL level to "anything". A reason for the problem is that this may fail. I am also trying to come up with a test procedure. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191795] Ethernet (RJ45) Not Detected
by bugzilla_noreply＠suse.com 18 Nov '21

18 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1191795 https://bugzilla.suse.com/show_bug.cgi?id=1191795#c34 --- Comment #34 from Oliver Neukum <oneukum(a)suse.com> --- Please provide te outputs of "lspci -vvv" and "lspci -vvvn" (as root) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192714] [Build 20211114] podman tests triggering gpf in kernel 5.15.1
by bugzilla_noreply＠suse.com 18 Nov '21

18 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192714 https://bugzilla.suse.com/show_bug.cgi?id=1192714#c15 --- Comment #15 from Jan Kara <jack(a)suse.com> --- Thanks for the traces. So in all the cases it seems that struct bfq_group got freed while still being fully linked into various structures. The freeing always happened from blkg_free() called from RCU callback so everything points to the fact that blkg refcount got somehow corrupted (likely someone dropping a ref without taking it). Looking more into this... -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192118] New: [Build 20211027] openQA test fails in finit_module02
by bugzilla_noreply＠suse.com 18 Nov '21

18 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192118 Bug ID: 1192118 Summary: [Build 20211027] openQA test fails in finit_module02 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1998049/modules/fini t_module02/steps/7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos-ltp-syscalls@uefi_virtio-2G fails in [finit_module02](https://openqa.opensuse.org/tests/1998049/modules/finit_mod… failed # echo 'OpenQA::run_ltp.pm: Starting finit_module02' > /dev/ttyS0; echo EuAAc-$?- EuAAc-0- # finit_module02; echo "### TEST finit_module02 COMPLETE >>> $?" tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s finit_module02.c:119: TPASS: TestName: invalid-fd : EBADF (9) fin�� finit_module02 finit_module02.c:119: TPASS: TestName: invalid-fd : EBADF (9) finit_module02.c:119: TPASS: TestName: zero-fd : EINVAL (22) finit_module02.c:119: TPASS: TestName: null-param : EFAULT (14) finit_module02.c:119: TPASS: TestName: invalid-param : EINVAL (22) finit_module02.c:119: TPASS: TestName: invalid-flags : EINVAL (22) finit_module02.c:119: TPASS: TestName: no-perm : EPERM (1) finit_module02.c:119: TPASS: TestName: module-exists : EEXIST (17) finit_module02.c:119: TFAIL: TestName: file-not-readable expected EBADF: ETXTBSY (26) finit_module02.c:119: TPASS: TestName: directory : EINVAL (22) Failed. Test took approximately 0.0326297609935864 seconds Some test output could not be parsed: 12 lines were ignored. ## Test suite description ## Reproducible Fails since (at least) Build [20211026](https://openqa.opensuse.org/tests/1994788) ## Expected result Last good: [20211025](https://openqa.opensuse.org/tests/1992656) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1192714] [Build 20211114] podman tests triggering gpf in kernel 5.15.1
by bugzilla_noreply＠suse.com 18 Nov '21

18 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192714 https://bugzilla.suse.com/show_bug.cgi?id=1192714#c13 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(fvogt(a)suse.com) | --- Comment #13 from Fabian Vogt <fvogt(a)suse.com> --- Created attachment 853836 --> https://bugzilla.suse.com/attachment.cgi?id=853836&action=edit decoded traces + dmesg (In reply to Jiri Slaby from > comment #10) > > (In reply to Fabian Vogt from comment #8) > > > Created attachment 853801 [details] > > > dmesg + blktrace > > > > Could you feed the trace through the kernel's ./scripts/decode_stacktrace.sh > > (provided you built the kernel with debuginfo)? > > Will do. decode_stacktrace.sh got confused when using a serial console dump as input, because of CRLF line endings. After dos2unix treatment it worked. Decoded traces and dmesg are attached. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191795] Ethernet (RJ45) Not Detected
by bugzilla_noreply＠suse.com 18 Nov '21

18 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1191795 https://bugzilla.suse.com/show_bug.cgi?id=1191795#c33 --- Comment #33 from Frank Kr�ger <fkrueger(a)mailbox.org> --- (In reply to Oliver Neukum from comment #32) > (In reply to Frank Kr�ger from comment #29) > > > Unfortunately, your kernel version does not work for me. > > Same effect or does it crash? Same, i.e., no effect. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191795] Ethernet (RJ45) Not Detected
by bugzilla_noreply＠suse.com 18 Nov '21

18 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1191795 https://bugzilla.suse.com/show_bug.cgi?id=1191795#c32 --- Comment #32 from Oliver Neukum <oneukum(a)suse.com> --- (In reply to Frank Kr�ger from comment #29) > Unfortunately, your kernel version does not work for me. Same effect or does it crash? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192714] [Build 20211114] podman tests triggering gpf in kernel 5.15.1
by bugzilla_noreply＠suse.com 18 Nov '21

18 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192714 https://bugzilla.suse.com/show_bug.cgi?id=1192714#c12 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dsterba(a)suse.com, | |nborisov(a)suse.com Flags| |needinfo?(dsterba(a)suse.com) | |, | |needinfo?(nborisov(a)suse.com | |), SHIP_STOPPER? --- Comment #12 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Jiri Slaby from comment #9) > (In reply to Fabian Vogt from comment #6) > > Inside, I ran "podman run --rm --entrypoint 'printenv' myapp WORLD_VAR | > > I cannot reproduce using opensuse/httpd. So how did you obtain/build the > myapp container? (In reply to Fabian Vogt from comment #7) > [ 1562.502838] btrfs_submit_data_bio+0x30f/0x7b0 [btrfs] I have just realized that I use ext4... Let me retest w/ btrfs. This looks like btrfs specific. (In reply to Jiri Slaby from comment #10) > First, let's ask our block layer fellows. Maybe it rings a bell there? Or at > least they know who to blame/contact... s/block/btrfs/ this time. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192714] [Build 20211114] podman tests triggering gpf in kernel 5.15.1
by bugzilla_noreply＠suse.com 18 Nov '21

18 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192714 https://bugzilla.suse.com/show_bug.cgi?id=1192714#c11 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? | --- Comment #11 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Jiri Slaby from comment #9) > (In reply to Fabian Vogt from comment #6) > > Inside, I ran "podman run --rm --entrypoint 'printenv' myapp WORLD_VAR | > > I cannot reproduce using opensuse/httpd. So how did you obtain/build the > myapp container? I can reproduce it with opensuse/httpd as well. I'm using the following QEMU line (single CPU, 1024MiB RAM): /usr/bin/qemu-system-x86_64 -only-migratable -chardev ringbuf,id=serial0,logfile=serial0,logappend=on -serial chardev:serial0 -audiodev none,id=snd0 -device intel-hda -device hda-output,audiodev=snd0 -global isa-fdc.fdtypeA=none -m 1024 -cpu qemu64 -netdev user,id=qanet0 -device virtio-net,netdev=qanet0,mac=52:54:00:12:34:56 -boot once=d -device qemu-xhci -device usb-tablet -smp 1 -enable-kvm -no-shutdown -device virtio-serial -chardev pipe,id=virtio_console,path=virtio_console,logfile=virtio_console.log,logappend=on -device virtconsole,chardev=virtio_console,name=org.openqa.console.virtio_console -chardev pipe,id=virtio_console1,path=virtio_console1,logfile=virtio_console1.log,logappend=on -device virtconsole,chardev=virtio_console1,name=org.openqa.console.virtio_console1 -chardev socket,path=qmp_socket,server,nowait,id=qmp_socket,logfile=qmp_socket.log,logappend=on -qmp chardev:qmp_socket -S -device virtio-scsi-pci,id=scsi0 -blockdev driver=file,node-name=hd0-file,filename=/data/libvirt/disks/boo1192714.qcow2,cache.no-flush=on -blockdev driver=qcow2,node-name=hd0,file=hd0-file,cache.no-flush=on -device virtio-blk,id=hd0-device,drive=hd0,serial=hd0 -blockdev driver=file,node-name=cd0-overlay0-file,filename=/data/libvirt/isos/openSUSE-Kubic-DVD-x86_64-Snapshot20211115-Media.iso,cache.no-flush=on,read-only=on -blockdev driver=raw,read-only=on,node-name=cd0-overlay0,file=cd0-overlay0-file,cache.no-flush=on -device scsi-cd,id=cd0-device,drive=cd0-overlay0,serial=cd0 And running this command on tty1 as well as tty2: while podman run --rm --entrypoint 'printenv' opensuse/httpd PATH; do :; done And after a few iterations it usually results in the kasan report. This time it even reproduced the system freeze.(In reply to Jiri Slaby from comment #10) > (In reply to Fabian Vogt from comment #8) > > Created attachment 853801 [details] > > dmesg + blktrace > > Could you feed the trace through the kernel's ./scripts/decode_stacktrace.sh > (provided you built the kernel with debuginfo)? Will do. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192473] DE0-Nano-SoC boot fails on 15.3
by bugzilla_noreply＠suse.com 18 Nov '21

18 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192473 https://bugzilla.suse.com/show_bug.cgi?id=1192473#c14 --- Comment #14 from Takashi Iwai <tiwai(a)suse.com> --- Thanks! I submitted the fix patch, and now the upstream suggested a better way. https://lore.kernel.org/r/20211117193244.31162-1-tiwai@suse.de The test kernel is being rebuilt again with the new patch in the same OBS repo home:tiwai:bsc1192473. Could you retest once after the package build finishes? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192714] [Build 20211114] podman tests triggering gpf in kernel 5.15.1
by bugzilla_noreply＠suse.com 18 Nov '21

18 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192714 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Comment #7 is|1 |0 private| | -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192714] [Build 20211114] podman tests triggering gpf in kernel 5.15.1
by bugzilla_noreply＠suse.com 18 Nov '21

18 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192714 https://bugzilla.suse.com/show_bug.cgi?id=1192714#c10 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |colyli(a)suse.com Flags| |needinfo?(jack(a)suse.com), | |needinfo?(colyli(a)suse.com) --- Comment #10 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Fabian Vogt from comment #8) > Created attachment 853801 [details] > dmesg + blktrace Could you feed the trace through the kernel's ./scripts/decode_stacktrace.sh (provided you built the kernel with debuginfo)? > I got another kasan trace. This time I had blk tracing enabled. The full > trace and dmesg are attached. > Can someone please forward all the logs to the proper ML? First, let's ask our block layer fellows. Maybe it rings a bell there? Or at least they know who to blame/contact... -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192767] Kernel boot logging gets mixed up when bringing up CPUs on SMP system
by bugzilla_noreply＠suse.com 18 Nov '21

18 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192767 https://bugzilla.suse.com/show_bug.cgi?id=1192767#c8 --- Comment #8 from Takashi Iwai <tiwai(a)suse.com> --- Created attachment 853828 --> https://bugzilla.suse.com/attachment.cgi?id=853828&action=edit Hackish PoC patch -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192767] Kernel boot logging gets mixed up when bringing up CPUs on SMP system
by bugzilla_noreply＠suse.com 18 Nov '21

18 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192767 https://bugzilla.suse.com/show_bug.cgi?id=1192767#c7 --- Comment #7 from Takashi Iwai <tiwai(a)suse.com> --- For #1, one possible fix would be to extend pr_cont() such as pr_cont_info() to pass a new corresponding printk level (e.g. '8'..'F'). And check the printk level of the previous ringbuffer, and if it's different, treat as a new line message. A fairly untested PoC patch is like below. But maybe better to wait for the response from Petr. There might be already more clever way. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192714] [Build 20211114] podman tests triggering gpf in kernel 5.15.1
by bugzilla_noreply＠suse.com 18 Nov '21

18 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192714 https://bugzilla.suse.com/show_bug.cgi?id=1192714#c9 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(fvogt(a)suse.com) --- Comment #9 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Fabian Vogt from comment #6) > Inside, I ran "podman run --rm --entrypoint 'printenv' myapp WORLD_VAR | I cannot reproduce using opensuse/httpd. So how did you obtain/build the myapp container? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192807] Kernel 5.16 rc1: Unable to suspend: DEAD callback error for CPU1
by bugzilla_noreply＠suse.com 18 Nov '21

18 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192807 https://bugzilla.suse.com/show_bug.cgi?id=1192807#c4 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- A known bug of powercap driver, I also hit and debugged yesterday :) An upstream fix is found in linux-next 4d1cd1443db3d5605ebcde8672869b1944ade92d powercap: DTPM: Fix suspend failure and kernel warning The patch was submitted at https://lore.kernel.org/r/20211108062345.273855-1-daniel.lezcano@linaro.org -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192809] New: [RPi4] tc358743-based HDMI input does not work with kernel-default; works with kernel from raspberry foundation
by bugzilla_noreply＠suse.com 18 Nov '21

18 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192809 Bug ID: 1192809 Summary: [RPi4] tc358743-based HDMI input does not work with kernel-default; works with kernel from raspberry foundation Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: marmarek(a)mimuw.edu.pl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 853822 --> http://bugzilla.opensuse.org/attachment.cgi?id=853822&action=edit dmesg, opensuse kernel with dtoverlay=tc358743 I've spent quite some time trying to get tc358743 on RPi4 to work with OpenSUSE Tumbleweed. Besides `config.txt` entries (where I hit https://bugzilla.opensuse.org/show_bug.cgi?id=1192047) there needs to be a kernel module. tc358743 itself is present, but I still can't get `/dev/video0`. The best I've got is: ``` [ 19.841631] Registered IR keymap rc-cec [ 19.841804] rc rc2: 10-000f as /devices/platform/soc/fe205000.i2c/i2c-22/i2c-10/10-000f/rc/rc2 [ 19.842070] input: 10-000f as /devices/platform/soc/fe205000.i2c/i2c-22/i2c-10/10-000f/rc/rc2/input2 [ 19.845518] tc358743 10-000f: tc358743 found @ 0x1e (i2c-22-mux (chan_id 1)) ``` with no `start_x=1` but with `dtoverlay=tc358743` in config.txt. But still no /dev/video0 (or any other /dev/video*). I do have `videodev` module loaded. I'm attaching full dmesg and lsmod outputs. This all is with kernel-default-5.14.14-1.1.aarch64. The whole thing _does_ work with a kernel built from raspberry foundation's tree, with the config attached. And with `start_x=1` in config.txt. I'm attaching dmesg and lsmod from this too (rpi-* files). I suspect the issue is some part of the video stack not available yet in the upstream kernel (bcm2835-unicam module specifically), but I was told to report the issue anyway. Some hints to that from the working setup: ``` localhost:/home/pi # ls -l /sys/class/video4linux/video0/device/driver lrwxrwxrwx 1 root root 0 Oct 15 00:00 /sys/class/video4linux/video0/device/driver -> ../../../../bus/platform/drivers/unicam localhost:/home/pi # ls -l /sys/class/video4linux/video0/device/driver/module lrwxrwxrwx 1 root root 0 Nov 18 03:12 /sys/class/video4linux/video0/device/driver/module -> ../../../../module/bcm2835_unicam ``` Some more information is at those two links: https://forums.raspberrypi.com/viewtopic.php?f=38&t=281972 https://www.raspberrypi.com/documentation/accessories/camera.html#camera-se… I've also seen https://en.opensuse.org/HCL:Raspberry_Pi_Camera_Modules but that didn't helped me getting it working with default kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1192758] Kernel Crash for i915 GPU driver
by bugzilla_noreply＠suse.com 17 Nov '21

17 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192758 https://bugzilla.suse.com/show_bug.cgi?id=1192758#c8 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Flags|needinfo?(noslin005(a)gmail.c | |om) | --- Comment #8 from Takashi Iwai <tiwai(a)suse.com> --- I pushed the fix for merging, so it'll be included likely in the next update, at latest in December. Until then, you can keep my test kernel (and report back if other problem happens with it). Let's close for now. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192758] New: Kernel Crash for i915 GPU driver
by bugzilla_noreply＠suse.com 17 Nov '21

17 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192758 Bug ID: 1192758 Summary: Kernel Crash for i915 GPU driver Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: openSUSE Leap 15.3 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: noslin005(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 853784 --> http://bugzilla.opensuse.org/attachment.cgi?id=853784&action=edit crash message for i915 driver I notice a frequent kernel crash assotiated with i915 GPU driver on MSI MS-7D16/H510I PRO WIFI (MS-7D16), BIOS 1.30 09/09/2021. [ 2.558990] ------------[ cut here ]------------ [ 2.558990] i915 0000:00:02.0: drm_WARN_ON(enabled_irq_mask & ~interrupt_mask) [ 2.559023] WARNING: CPU: 5 PID: 330 at ../drivers/gpu/drm/i915/i915_irq.c:434 ibx_display_interrupt_update+0xb9/0x110 [i915] [ 2.559023] Modules linked in: i915(+) i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cec xhci_pci rc_core xhci_hcd drm ahci libahci usbcore libata nvme nvme_core crc32c_intel t10_pi video wmi pinctrl_tigerlake sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua scsi_mod msr efivarfs If I boot with 'nomodeset', the crash does not happen, but I can not get the front audio to work. For more details, refer to the logs uploaded here https://linux-hardware.org/?probe=d50547de1f -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1191795] Ethernet (RJ45) Not Detected
by bugzilla_noreply＠suse.com 17 Nov '21

17 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1191795 https://bugzilla.suse.com/show_bug.cgi?id=1191795#c31 --- Comment #31 from Frank Kr�ger <fkrueger(a)mailbox.org> --- (In reply to Art Hemming from comment #30) > (In reply to Oliver Neukum from comment #28) > > Test kernel abuilding at: > > > > https://build.opensuse.org/project/monitor/home:oneukum:bsc1191795_20211117a > > > > Please test > > This is a dumb question, but are there videos somewhere of how to use the > OBS service to test a kernel for (this and similar) bugs? Or documentation? > > I find myself at present unable to contribute due to a sheer lack of knowing > what to do, for which I apologize. > > Have a lovely day! One possibility is to add https://download.opensuse.org/repositories/home:/oneukum:/bsc1191795_202111… as an additional repo and install the corresponding kernel or use the 1-click-installation via https://software.opensuse.org/ymp/home:oneukum:bsc1191795_20211117a/ARM/ker… (the latter does not work for me). Hope this helps. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191795] Ethernet (RJ45) Not Detected
by bugzilla_noreply＠suse.com 17 Nov '21

17 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1191795 https://bugzilla.suse.com/show_bug.cgi?id=1191795#c30 --- Comment #30 from Art Hemming <cameron.cn(a)yagowap.com> --- (In reply to Oliver Neukum from comment #28) > Test kernel abuilding at: > > https://build.opensuse.org/project/monitor/home:oneukum:bsc1191795_20211117a > > Please test This is a dumb question, but are there videos somewhere of how to use the OBS service to test a kernel for (this and similar) bugs? Or documentation? I find myself at present unable to contribute due to a sheer lack of knowing what to do, for which I apologize. Have a lovely day! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191795] Ethernet (RJ45) Not Detected
by bugzilla_noreply＠suse.com 17 Nov '21

17 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1191795 https://bugzilla.suse.com/show_bug.cgi?id=1191795#c29 --- Comment #29 from Frank Kr�ger <fkrueger(a)mailbox.org> --- (In reply to Oliver Neukum from comment #28) > Test kernel abuilding at: > > https://build.opensuse.org/project/monitor/home:oneukum:bsc1191795_20211117a > > Please test Unfortunately, your kernel version does not work for me. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192767] Kernel boot logging gets mixed up when bringing up CPUs on SMP system
by bugzilla_noreply＠suse.com 17 Nov '21

17 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192767 https://bugzilla.suse.com/show_bug.cgi?id=1192767#c6 --- Comment #6 from Archie Cobbs <archie.cobbs(a)gmail.com> --- > #1 I understand - you're not the only one who's looking at warning-level > messages - people do care about them. But our booting is already very > fragile so fixing stuff only for the formatting's sake is not worth the > effort and complexity. In an ideal world both bugs would be fixed but practically speaking I agree #1 is both easier to fix and higher priority. So let's start there. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192767] Kernel boot logging gets mixed up when bringing up CPUs on SMP system
by bugzilla_noreply＠suse.com 17 Nov '21

17 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192767 https://bugzilla.suse.com/show_bug.cgi?id=1192767#c5 --- Comment #5 from Borislav Petkov <bpetkov(a)suse.com> --- (In reply to Archie Cobbs from comment #4) > #1 Bogus promotion from INFO to WARN That is probably a bug... > #2 Broken formatting if there are any per-CPU log messages ... but I can't call this a bug frankly. > Both bugs should be fixed. For #2 I can see where the problem comes from... > when you have 127 CPU's and there are no warnings emitted, it's nicer to > have them listed all on one or two lines. But of course, you don't want to > stop any per-CPU log messages from being emitted, so if they are emitted, > they get emitted "in the middle" of the single, in-progress log line for > that node. Pretty much. > Given the simplistic way kernel logging works, to give proper formatting > when there is a possibility of any CPU startup emitting a warning AND have > each CPU listed in "real time", you would be forced to log each CPU on its > own line. The reason it was done this way is to save dmesg space. Imagine you had 9K CPUs. Because there are boxes like that. That's 9K lines of dmesg log ring buffer wasted. Or on a slow serial line. 9K seconds only for the cores if it takes a second to issue a line. > Alternatively, if you don't care about "real time" logging (would probably > be a bad idea to give this up) then you could wait until all CPU's are done > to log the results... I don't care if the logging is interleaved by some message during a logical thread's initialization. dmesg message format is not an ABI but a best-effort thing, roughly speaking. #1 I understand - you're not the only one who's looking at warning-level messages - people do care about them. But our booting is already very fragile so fixing stuff only for the formatting's sake is not worth the effort and complexity. HTH. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192767] Kernel boot logging gets mixed up when bringing up CPUs on SMP system
by bugzilla_noreply＠suse.com 17 Nov '21

17 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192767 https://bugzilla.suse.com/show_bug.cgi?id=1192767#c4 --- Comment #4 from Archie Cobbs <archie.cobbs(a)gmail.com> --- > The purpose of the "meaningless log messages" is to show the CPU configuration of the machine. Understood - apologies for calling them meaningless. But to be clear there are two bugs here... #1 Bogus promotion from INFO to WARN #2 Broken formatting if there are any per-CPU log messages Both bugs should be fixed. For #2 I can see where the problem comes from... when you have 127 CPU's and there are no warnings emitted, it's nicer to have them listed all on one or two lines. But of course, you don't want to stop any per-CPU log messages from being emitted, so if they are emitted, they get emitted "in the middle" of the single, in-progress log line for that node. Given the simplistic way kernel logging works, to give proper formatting when there is a possibility of any CPU startup emitting a warning AND have each CPU listed in "real time", you would be forced to log each CPU on its own line. For example, that might look like this (if only CPU#3 had a problem): x86: Booting SMP configuration: .... node #0 CPU #1 .... node #0 CPU #2 .... node #0 CPU #3 core: CPUID marked event: 'cpu cycles' unavailable .... node #0 CPU #4 smp: Brought up 1 node, 4 CPUs Alternatively, if you don't care about "real time" logging (would probably be a bad idea to give this up) then you could wait until all CPU's are done to log the results... x86: Booting SMP configuration: .... node #0 CPU #3: core: CPUID marked event: 'cpu cycles' unavailable smp: Brought up 1 node, 4 CPUs This would require some new trickery with the logging infrastructure to allow configuring an thread-local "log prefix" (in this case, the ".... node #0 CPU #3: " part). Right now the code is trying to have it both ways and it's not working... -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192758] Kernel Crash for i915 GPU driver
by bugzilla_noreply＠suse.com 17 Nov '21

17 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192758 https://bugzilla.suse.com/show_bug.cgi?id=1192758#c4 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |noslin005(a)gmail.com Flags| |needinfo?(noslin005(a)gmail.c | |om) --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- Thanks. It's a PCH_TGP, so relatively new stuff. I guess this could be covered by the upstream commit 6d3144eb367063df630248e0564b75701f63423b. A test kernel is being built in OBS home:tiwai:bsc1192758 repo. Once after the build finishes, it'll appear at http://download.opensuse.org/repositories/home:/tiwai:/bsc1192758/pool/ Please give it a try later. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192767] Kernel boot logging gets mixed up when bringing up CPUs on SMP system
by bugzilla_noreply＠suse.com 17 Nov '21

17 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192767 https://bugzilla.suse.com/show_bug.cgi?id=1192767#c3 --- Comment #3 from Borislav Petkov <bpetkov(a)suse.com> --- The purpose of the "meaningless log messages" is to show the CPU configuration of the machine. Example: x86: Booting SMP configuration: .... node #0, CPUs: #1 #2 #3 ... #63 .... node #1, CPUs: #64 #65 #66 ... #127 where the ellipsis "..." has the other core numbers which I've not added here for readability. I guess we can make "Disabled fast string operations" a once message so that it doesn't fire on every CPU as that's pointless and redundant. But that's all cosmetic stuff - the "promotion" of info messages to warn is the bigger issue which Petr can comment on. HTH. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192767] Kernel boot logging gets mixed up when bringing up CPUs on SMP system
by bugzilla_noreply＠suse.com 17 Nov '21

17 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192767 https://bugzilla.suse.com/show_bug.cgi?id=1192767#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bpetkov(a)suse.com, | |pmladek(a)suse.com, | |tiwai(a)suse.com --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- I guess it's the code in arch/x86/kernel/smpboot.c, and indeed it's with a few pr_cont() in a loop where an intervention may happen. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192771] raid5rec.mod missing error from grub2
by bugzilla_noreply＠suse.com 17 Nov '21

17 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192771 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |Bootloader Assignee|kernel-bugs(a)opensuse.org |screening-team-bugs(a)suse.de -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191795] Ethernet (RJ45) Not Detected
by bugzilla_noreply＠suse.com 17 Nov '21

17 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1191795 https://bugzilla.suse.com/show_bug.cgi?id=1191795#c28 --- Comment #28 from Oliver Neukum <oneukum(a)suse.com> --- Test kernel abuilding at: https://build.opensuse.org/project/monitor/home:oneukum:bsc1191795_20211117a Please test -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191795] Ethernet (RJ45) Not Detected
by bugzilla_noreply＠suse.com 17 Nov '21

17 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1191795 https://bugzilla.suse.com/show_bug.cgi?id=1191795#c27 --- Comment #27 from Oliver Neukum <oneukum(a)suse.com> --- Working hypothesis: static int rtl8169_runtime_suspend(struct device *device) { struct rtl8169_private *tp = dev_get_drvdata(device); if (!tp->TxDescArray) { netif_device_detach(tp->dev); return 0; } This test is wrong. I'll make a test kernel that omits it. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191795] Ethernet (RJ45) Not Detected
by bugzilla_noreply＠suse.com 17 Nov '21

17 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1191795 https://bugzilla.suse.com/show_bug.cgi?id=1191795#c26 Oliver Neukum <oneukum(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |IN_PROGRESS --- Comment #26 from Oliver Neukum <oneukum(a)suse.com> --- OK, good, so we can confirm that this is a kernel bug due to overzealous runtime power management. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192714] [Build 20211114] podman tests triggering gpf in kernel 5.15.1
by bugzilla_noreply＠suse.com 17 Nov '21

17 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192714 https://bugzilla.suse.com/show_bug.cgi?id=1192714#c8 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo? --- Comment #8 from Fabian Vogt <fvogt(a)suse.com> --- Created attachment 853801 --> https://bugzilla.suse.com/attachment.cgi?id=853801&action=edit dmesg + blktrace I got another kasan trace. This time I had blk tracing enabled. The full trace and dmesg are attached. Can someone please forward all the logs to the proper ML? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190256] Keyboard not working after cold-boot on ASUS Zenbook 14 UM425UA with Tumbleweed 20210904
by bugzilla_noreply＠suse.com 17 Nov '21

17 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1190256 https://bugzilla.suse.com/show_bug.cgi?id=1190256#c25 Jeffrey Cheung <jcheung(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #25 from Jeffrey Cheung <jcheung(a)suse.com> --- I see the below patch is just backported and submitted to 15 SP4 kernel commit 0a16328b172b9c25243f925338af97e5d25e7969 Author: Takashi Iwai <tiwai(a)suse.de> Date: Wed Nov 17 07:49:57 2021 +0100 Input: i8042 - Add deferred probe support (bsc#1190256). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192473] DE0-Nano-SoC boot fails on 15.3
by bugzilla_noreply＠suse.com 16 Nov '21

16 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192473 https://bugzilla.suse.com/show_bug.cgi?id=1192473#c13 --- Comment #13 from Christian Gross <christian.gross(a)centerofgravity.at> --- Looks like this fixed it. �� ... [ OK ] Reached target Timers. Welcome to openSUSE Leap 15.2 - Kernel 5.3.18-2.g599038f-default (ttyS0). localhost login: -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192721] New: Logitech QuickCam Zoom (pwc) no longer works on TW 20211110
by bugzilla_noreply＠suse.com 16 Nov '21

16 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192721 Bug ID: 1192721 Summary: Logitech QuickCam Zoom (pwc) no longer works on TW 20211110 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: javier(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 853749 --> http://bugzilla.opensuse.org/attachment.cgi?id=853749&action=edit dmesg Unfortunately, the webcam does not work again on openSUSE Tumbleweed 20211110 (kernel-default-5.14.14-2.1.x86_64). It worked fine with your fix (bug #1181133). pwc: isoc_init() submit_urb 0 failed with error -28 lsusb: Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 003: ID 1a81:1004 Holtek Semiconductor, Inc. Wireless Dongle 2.4 GHZ HT82D40REW Bus 001 Device 005: ID 046d:08b3 Logitech, Inc. QuickCam Zoom Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 148f:761a Ralink Technology, Corp. MT7610U ("Archer T2U" 2.4G+5G WLAN Adapter Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub hwinfo --cam 01: USB 00.2: 10f00 Camera [Created at usb.122] Unique ID: zPMs.AN_e7XL7ryA Parent ID: ADDn.4Nx_qoDfSd7 SysFS ID: /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.2 SysFS BusID: 1-1.4:1.2 Hardware Class: camera Model: "Logitech QuickCam Zoom" Hotplug: USB Vendor: usb 0x046d "Logitech, Inc." Device: usb 0x08b3 "QuickCam Zoom" Driver: "snd-usb-audio" Driver Modules: "snd_usb_audio" Speed: 12 Mbps Module Alias: "usb:v046Dp08B3d0000dc00dsc00dp00ic01isc02ip00in02" Driver Info #0: Driver Status: pwc is active Driver Activation Cmd: "modprobe pwc" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #12 (Hub) -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1192473] DE0-Nano-SoC boot fails on 15.3
by bugzilla_noreply＠suse.com 16 Nov '21

16 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192473 https://bugzilla.suse.com/show_bug.cgi?id=1192473#c12 --- Comment #12 from Takashi Iwai <tiwai(a)suse.com> --- A newer test kernel is read in the same OBS home:tiwai:bsc1192473 repo. Please give it a try. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192771] New: raid5rec.mod missing error from grub2
by bugzilla_noreply＠suse.com 16 Nov '21

16 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192771 Bug ID: 1192771 Summary: raid5rec.mod missing error from grub2 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: lvl(a)omnitec.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After selecting default option, grub2 throws error: raid5rec.mod missing File is present in multiple locations: /boot/grub2/x86_64-efi/raid5rec.mod /usr/share/grub2/i386-pc/raid5rec.mod /usr/share/grub2/x86_64-efi/raid5rec.mod Why would grub2 not see it? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192549] Kernel 5.3.18-lp152.98-default breaks getdents(2) system call on NFS shares
by bugzilla_noreply＠suse.com 16 Nov '21

16 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192549 https://bugzilla.suse.com/show_bug.cgi?id=1192549#c24 --- Comment #24 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-SU-2021:3675-1: An update that solves 15 vulnerabilities and has 56 fixes is now available. Category: security (important) Bug References: 1065729,1085030,1089118,1094840,1133021,1152472,1152489,1154353,1156395,1157177,1167773,1172073,1173604,1176447,1176774,1176914,1176940,1178134,1180100,1180749,1181147,1184673,1185762,1186063,1186109,1187167,1188563,1188601,1189841,1190006,1190067,1190349,1190351,1190479,1190620,1190642,1190795,1190801,1190941,1191229,1191240,1191241,1191315,1191317,1191349,1191384,1191449,1191450,1191451,1191452,1191455,1191456,1191628,1191645,1191663,1191731,1191800,1191851,1191867,1191934,1191958,1191980,1192040,1192041,1192074,1192107,1192145,1192229,1192267,1192288,1192549 CVE References: CVE-2021-33033,CVE-2021-34866,CVE-2021-3542,CVE-2021-3655,CVE-2021-3715,CVE-2021-37159,CVE-2021-3760,CVE-2021-3772,CVE-2021-3896,CVE-2021-41864,CVE-2021-42008,CVE-2021-42252,CVE-2021-42739,CVE-2021-43056,CVE-2021-43389 JIRA References: Sources used: openSUSE Leap 15.3 (src): dtb-aarch64-5.3.18-59.34.1, kernel-64kb-5.3.18-59.34.1, kernel-debug-5.3.18-59.34.1, kernel-default-5.3.18-59.34.1, kernel-default-base-5.3.18-59.34.1.18.21.1, kernel-docs-5.3.18-59.34.1, kernel-kvmsmall-5.3.18-59.34.1, kernel-obs-build-5.3.18-59.34.1, kernel-obs-qa-5.3.18-59.34.1, kernel-preempt-5.3.18-59.34.1, kernel-source-5.3.18-59.34.1, kernel-syms-5.3.18-59.34.1, kernel-zfcpdump-5.3.18-59.34.1 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191980] Touchpad not working during and after install
by bugzilla_noreply＠suse.com 16 Nov '21

16 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1191980 https://bugzilla.suse.com/show_bug.cgi?id=1191980#c21 --- Comment #21 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-SU-2021:3675-1: An update that solves 15 vulnerabilities and has 56 fixes is now available. Category: security (important) Bug References: 1065729,1085030,1089118,1094840,1133021,1152472,1152489,1154353,1156395,1157177,1167773,1172073,1173604,1176447,1176774,1176914,1176940,1178134,1180100,1180749,1181147,1184673,1185762,1186063,1186109,1187167,1188563,1188601,1189841,1190006,1190067,1190349,1190351,1190479,1190620,1190642,1190795,1190801,1190941,1191229,1191240,1191241,1191315,1191317,1191349,1191384,1191449,1191450,1191451,1191452,1191455,1191456,1191628,1191645,1191663,1191731,1191800,1191851,1191867,1191934,1191958,1191980,1192040,1192041,1192074,1192107,1192145,1192229,1192267,1192288,1192549 CVE References: CVE-2021-33033,CVE-2021-34866,CVE-2021-3542,CVE-2021-3655,CVE-2021-3715,CVE-2021-37159,CVE-2021-3760,CVE-2021-3772,CVE-2021-3896,CVE-2021-41864,CVE-2021-42008,CVE-2021-42252,CVE-2021-42739,CVE-2021-43056,CVE-2021-43389 JIRA References: Sources used: openSUSE Leap 15.3 (src): dtb-aarch64-5.3.18-59.34.1, kernel-64kb-5.3.18-59.34.1, kernel-debug-5.3.18-59.34.1, kernel-default-5.3.18-59.34.1, kernel-default-base-5.3.18-59.34.1.18.21.1, kernel-docs-5.3.18-59.34.1, kernel-kvmsmall-5.3.18-59.34.1, kernel-obs-build-5.3.18-59.34.1, kernel-obs-qa-5.3.18-59.34.1, kernel-preempt-5.3.18-59.34.1, kernel-source-5.3.18-59.34.1, kernel-syms-5.3.18-59.34.1, kernel-zfcpdump-5.3.18-59.34.1 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191229] [Staging][rpm4.17] Kernel fails to build with rpm 4.17
by bugzilla_noreply＠suse.com 16 Nov '21

16 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1191229 https://bugzilla.suse.com/show_bug.cgi?id=1191229#c25 --- Comment #25 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-SU-2021:3675-1: An update that solves 15 vulnerabilities and has 56 fixes is now available. Category: security (important) Bug References: 1065729,1085030,1089118,1094840,1133021,1152472,1152489,1154353,1156395,1157177,1167773,1172073,1173604,1176447,1176774,1176914,1176940,1178134,1180100,1180749,1181147,1184673,1185762,1186063,1186109,1187167,1188563,1188601,1189841,1190006,1190067,1190349,1190351,1190479,1190620,1190642,1190795,1190801,1190941,1191229,1191240,1191241,1191315,1191317,1191349,1191384,1191449,1191450,1191451,1191452,1191455,1191456,1191628,1191645,1191663,1191731,1191800,1191851,1191867,1191934,1191958,1191980,1192040,1192041,1192074,1192107,1192145,1192229,1192267,1192288,1192549 CVE References: CVE-2021-33033,CVE-2021-34866,CVE-2021-3542,CVE-2021-3655,CVE-2021-3715,CVE-2021-37159,CVE-2021-3760,CVE-2021-3772,CVE-2021-3896,CVE-2021-41864,CVE-2021-42008,CVE-2021-42252,CVE-2021-42739,CVE-2021-43056,CVE-2021-43389 JIRA References: Sources used: openSUSE Leap 15.3 (src): dtb-aarch64-5.3.18-59.34.1, kernel-64kb-5.3.18-59.34.1, kernel-debug-5.3.18-59.34.1, kernel-default-5.3.18-59.34.1, kernel-default-base-5.3.18-59.34.1.18.21.1, kernel-docs-5.3.18-59.34.1, kernel-kvmsmall-5.3.18-59.34.1, kernel-obs-build-5.3.18-59.34.1, kernel-obs-qa-5.3.18-59.34.1, kernel-preempt-5.3.18-59.34.1, kernel-source-5.3.18-59.34.1, kernel-syms-5.3.18-59.34.1, kernel-zfcpdump-5.3.18-59.34.1 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180749] AMD Ryzen 4800H Renoir APU brightness control not working as found in some Lenovo Legion 5 15ARH05
by bugzilla_noreply＠suse.com 16 Nov '21

16 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1180749 https://bugzilla.suse.com/show_bug.cgi?id=1180749#c50 --- Comment #50 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-SU-2021:3675-1: An update that solves 15 vulnerabilities and has 56 fixes is now available. Category: security (important) Bug References: 1065729,1085030,1089118,1094840,1133021,1152472,1152489,1154353,1156395,1157177,1167773,1172073,1173604,1176447,1176774,1176914,1176940,1178134,1180100,1180749,1181147,1184673,1185762,1186063,1186109,1187167,1188563,1188601,1189841,1190006,1190067,1190349,1190351,1190479,1190620,1190642,1190795,1190801,1190941,1191229,1191240,1191241,1191315,1191317,1191349,1191384,1191449,1191450,1191451,1191452,1191455,1191456,1191628,1191645,1191663,1191731,1191800,1191851,1191867,1191934,1191958,1191980,1192040,1192041,1192074,1192107,1192145,1192229,1192267,1192288,1192549 CVE References: CVE-2021-33033,CVE-2021-34866,CVE-2021-3542,CVE-2021-3655,CVE-2021-3715,CVE-2021-37159,CVE-2021-3760,CVE-2021-3772,CVE-2021-3896,CVE-2021-41864,CVE-2021-42008,CVE-2021-42252,CVE-2021-42739,CVE-2021-43056,CVE-2021-43389 JIRA References: Sources used: openSUSE Leap 15.3 (src): dtb-aarch64-5.3.18-59.34.1, kernel-64kb-5.3.18-59.34.1, kernel-debug-5.3.18-59.34.1, kernel-default-5.3.18-59.34.1, kernel-default-base-5.3.18-59.34.1.18.21.1, kernel-docs-5.3.18-59.34.1, kernel-kvmsmall-5.3.18-59.34.1, kernel-obs-build-5.3.18-59.34.1, kernel-obs-qa-5.3.18-59.34.1, kernel-preempt-5.3.18-59.34.1, kernel-source-5.3.18-59.34.1, kernel-syms-5.3.18-59.34.1, kernel-zfcpdump-5.3.18-59.34.1 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192549] Kernel 5.3.18-lp152.98-default breaks getdents(2) system call on NFS shares
by bugzilla_noreply＠suse.com 16 Nov '21

16 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192549 https://bugzilla.suse.com/show_bug.cgi?id=1192549#c23 --- Comment #23 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2021:3675-1: An update that solves 15 vulnerabilities and has 56 fixes is now available. Category: security (important) Bug References: 1065729,1085030,1089118,1094840,1133021,1152472,1152489,1154353,1156395,1157177,1167773,1172073,1173604,1176447,1176774,1176914,1176940,1178134,1180100,1180749,1181147,1184673,1185762,1186063,1186109,1187167,1188563,1188601,1189841,1190006,1190067,1190349,1190351,1190479,1190620,1190642,1190795,1190801,1190941,1191229,1191240,1191241,1191315,1191317,1191349,1191384,1191449,1191450,1191451,1191452,1191455,1191456,1191628,1191645,1191663,1191731,1191800,1191851,1191867,1191934,1191958,1191980,1192040,1192041,1192074,1192107,1192145,1192229,1192267,1192288,1192549 CVE References: CVE-2021-33033,CVE-2021-34866,CVE-2021-3542,CVE-2021-3655,CVE-2021-3715,CVE-2021-37159,CVE-2021-3760,CVE-2021-3772,CVE-2021-3896,CVE-2021-41864,CVE-2021-42008,CVE-2021-42252,CVE-2021-42739,CVE-2021-43056,CVE-2021-43389 JIRA References: Sources used: SUSE MicroOS 5.1 (src): kernel-default-5.3.18-59.34.1, kernel-default-base-5.3.18-59.34.1.18.21.1 SUSE Linux Enterprise Workstation Extension 15-SP3 (src): kernel-default-5.3.18-59.34.1, kernel-preempt-5.3.18-59.34.1 SUSE Linux Enterprise Module for Live Patching 15-SP3 (src): kernel-default-5.3.18-59.34.1, kernel-livepatch-SLE15-SP3_Update_9-1-7.3.1 SUSE Linux Enterprise Module for Legacy Software 15-SP3 (src): kernel-default-5.3.18-59.34.1 SUSE Linux Enterprise Module for Development Tools 15-SP3 (src): kernel-docs-5.3.18-59.34.1, kernel-obs-build-5.3.18-59.34.1, kernel-preempt-5.3.18-59.34.1, kernel-source-5.3.18-59.34.1, kernel-syms-5.3.18-59.34.1 SUSE Linux Enterprise Module for Basesystem 15-SP3 (src): kernel-64kb-5.3.18-59.34.1, kernel-default-5.3.18-59.34.1, kernel-default-base-5.3.18-59.34.1.18.21.1, kernel-preempt-5.3.18-59.34.1, kernel-source-5.3.18-59.34.1, kernel-zfcpdump-5.3.18-59.34.1 SUSE Linux Enterprise High Availability 15-SP3 (src): kernel-default-5.3.18-59.34.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191980] Touchpad not working during and after install
by bugzilla_noreply＠suse.com 16 Nov '21

16 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1191980 https://bugzilla.suse.com/show_bug.cgi?id=1191980#c20 --- Comment #20 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2021:3675-1: An update that solves 15 vulnerabilities and has 56 fixes is now available. Category: security (important) Bug References: 1065729,1085030,1089118,1094840,1133021,1152472,1152489,1154353,1156395,1157177,1167773,1172073,1173604,1176447,1176774,1176914,1176940,1178134,1180100,1180749,1181147,1184673,1185762,1186063,1186109,1187167,1188563,1188601,1189841,1190006,1190067,1190349,1190351,1190479,1190620,1190642,1190795,1190801,1190941,1191229,1191240,1191241,1191315,1191317,1191349,1191384,1191449,1191450,1191451,1191452,1191455,1191456,1191628,1191645,1191663,1191731,1191800,1191851,1191867,1191934,1191958,1191980,1192040,1192041,1192074,1192107,1192145,1192229,1192267,1192288,1192549 CVE References: CVE-2021-33033,CVE-2021-34866,CVE-2021-3542,CVE-2021-3655,CVE-2021-3715,CVE-2021-37159,CVE-2021-3760,CVE-2021-3772,CVE-2021-3896,CVE-2021-41864,CVE-2021-42008,CVE-2021-42252,CVE-2021-42739,CVE-2021-43056,CVE-2021-43389 JIRA References: Sources used: SUSE MicroOS 5.1 (src): kernel-default-5.3.18-59.34.1, kernel-default-base-5.3.18-59.34.1.18.21.1 SUSE Linux Enterprise Workstation Extension 15-SP3 (src): kernel-default-5.3.18-59.34.1, kernel-preempt-5.3.18-59.34.1 SUSE Linux Enterprise Module for Live Patching 15-SP3 (src): kernel-default-5.3.18-59.34.1, kernel-livepatch-SLE15-SP3_Update_9-1-7.3.1 SUSE Linux Enterprise Module for Legacy Software 15-SP3 (src): kernel-default-5.3.18-59.34.1 SUSE Linux Enterprise Module for Development Tools 15-SP3 (src): kernel-docs-5.3.18-59.34.1, kernel-obs-build-5.3.18-59.34.1, kernel-preempt-5.3.18-59.34.1, kernel-source-5.3.18-59.34.1, kernel-syms-5.3.18-59.34.1 SUSE Linux Enterprise Module for Basesystem 15-SP3 (src): kernel-64kb-5.3.18-59.34.1, kernel-default-5.3.18-59.34.1, kernel-default-base-5.3.18-59.34.1.18.21.1, kernel-preempt-5.3.18-59.34.1, kernel-source-5.3.18-59.34.1, kernel-zfcpdump-5.3.18-59.34.1 SUSE Linux Enterprise High Availability 15-SP3 (src): kernel-default-5.3.18-59.34.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191229] [Staging][rpm4.17] Kernel fails to build with rpm 4.17
by bugzilla_noreply＠suse.com 16 Nov '21

16 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1191229 https://bugzilla.suse.com/show_bug.cgi?id=1191229#c24 --- Comment #24 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2021:3675-1: An update that solves 15 vulnerabilities and has 56 fixes is now available. Category: security (important) Bug References: 1065729,1085030,1089118,1094840,1133021,1152472,1152489,1154353,1156395,1157177,1167773,1172073,1173604,1176447,1176774,1176914,1176940,1178134,1180100,1180749,1181147,1184673,1185762,1186063,1186109,1187167,1188563,1188601,1189841,1190006,1190067,1190349,1190351,1190479,1190620,1190642,1190795,1190801,1190941,1191229,1191240,1191241,1191315,1191317,1191349,1191384,1191449,1191450,1191451,1191452,1191455,1191456,1191628,1191645,1191663,1191731,1191800,1191851,1191867,1191934,1191958,1191980,1192040,1192041,1192074,1192107,1192145,1192229,1192267,1192288,1192549 CVE References: CVE-2021-33033,CVE-2021-34866,CVE-2021-3542,CVE-2021-3655,CVE-2021-3715,CVE-2021-37159,CVE-2021-3760,CVE-2021-3772,CVE-2021-3896,CVE-2021-41864,CVE-2021-42008,CVE-2021-42252,CVE-2021-42739,CVE-2021-43056,CVE-2021-43389 JIRA References: Sources used: SUSE MicroOS 5.1 (src): kernel-default-5.3.18-59.34.1, kernel-default-base-5.3.18-59.34.1.18.21.1 SUSE Linux Enterprise Workstation Extension 15-SP3 (src): kernel-default-5.3.18-59.34.1, kernel-preempt-5.3.18-59.34.1 SUSE Linux Enterprise Module for Live Patching 15-SP3 (src): kernel-default-5.3.18-59.34.1, kernel-livepatch-SLE15-SP3_Update_9-1-7.3.1 SUSE Linux Enterprise Module for Legacy Software 15-SP3 (src): kernel-default-5.3.18-59.34.1 SUSE Linux Enterprise Module for Development Tools 15-SP3 (src): kernel-docs-5.3.18-59.34.1, kernel-obs-build-5.3.18-59.34.1, kernel-preempt-5.3.18-59.34.1, kernel-source-5.3.18-59.34.1, kernel-syms-5.3.18-59.34.1 SUSE Linux Enterprise Module for Basesystem 15-SP3 (src): kernel-64kb-5.3.18-59.34.1, kernel-default-5.3.18-59.34.1, kernel-default-base-5.3.18-59.34.1.18.21.1, kernel-preempt-5.3.18-59.34.1, kernel-source-5.3.18-59.34.1, kernel-zfcpdump-5.3.18-59.34.1 SUSE Linux Enterprise High Availability 15-SP3 (src): kernel-default-5.3.18-59.34.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180749] AMD Ryzen 4800H Renoir APU brightness control not working as found in some Lenovo Legion 5 15ARH05
by bugzilla_noreply＠suse.com 16 Nov '21

16 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1180749 https://bugzilla.suse.com/show_bug.cgi?id=1180749#c49 --- Comment #49 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2021:3675-1: An update that solves 15 vulnerabilities and has 56 fixes is now available. Category: security (important) Bug References: 1065729,1085030,1089118,1094840,1133021,1152472,1152489,1154353,1156395,1157177,1167773,1172073,1173604,1176447,1176774,1176914,1176940,1178134,1180100,1180749,1181147,1184673,1185762,1186063,1186109,1187167,1188563,1188601,1189841,1190006,1190067,1190349,1190351,1190479,1190620,1190642,1190795,1190801,1190941,1191229,1191240,1191241,1191315,1191317,1191349,1191384,1191449,1191450,1191451,1191452,1191455,1191456,1191628,1191645,1191663,1191731,1191800,1191851,1191867,1191934,1191958,1191980,1192040,1192041,1192074,1192107,1192145,1192229,1192267,1192288,1192549 CVE References: CVE-2021-33033,CVE-2021-34866,CVE-2021-3542,CVE-2021-3655,CVE-2021-3715,CVE-2021-37159,CVE-2021-3760,CVE-2021-3772,CVE-2021-3896,CVE-2021-41864,CVE-2021-42008,CVE-2021-42252,CVE-2021-42739,CVE-2021-43056,CVE-2021-43389 JIRA References: Sources used: SUSE MicroOS 5.1 (src): kernel-default-5.3.18-59.34.1, kernel-default-base-5.3.18-59.34.1.18.21.1 SUSE Linux Enterprise Workstation Extension 15-SP3 (src): kernel-default-5.3.18-59.34.1, kernel-preempt-5.3.18-59.34.1 SUSE Linux Enterprise Module for Live Patching 15-SP3 (src): kernel-default-5.3.18-59.34.1, kernel-livepatch-SLE15-SP3_Update_9-1-7.3.1 SUSE Linux Enterprise Module for Legacy Software 15-SP3 (src): kernel-default-5.3.18-59.34.1 SUSE Linux Enterprise Module for Development Tools 15-SP3 (src): kernel-docs-5.3.18-59.34.1, kernel-obs-build-5.3.18-59.34.1, kernel-preempt-5.3.18-59.34.1, kernel-source-5.3.18-59.34.1, kernel-syms-5.3.18-59.34.1 SUSE Linux Enterprise Module for Basesystem 15-SP3 (src): kernel-64kb-5.3.18-59.34.1, kernel-default-5.3.18-59.34.1, kernel-default-base-5.3.18-59.34.1.18.21.1, kernel-preempt-5.3.18-59.34.1, kernel-source-5.3.18-59.34.1, kernel-zfcpdump-5.3.18-59.34.1 SUSE Linux Enterprise High Availability 15-SP3 (src): kernel-default-5.3.18-59.34.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192767] New: Kernel boot logging gets mixed up when bringing up CPUs on SMP system
by bugzilla_noreply＠suse.com 16 Nov '21

16 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192767 Bug ID: 1192767 Summary: Kernel boot logging gets mixed up when bringing up CPUs on SMP system Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: VMWare OS: openSUSE Leap 15.2 Status: NEW Severity: Minor Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: archie.cobbs(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I booted kernel-default-5.3.18-lp152.95.1.x86_64 (running on VMWare). Here is a snippet from dmesg -T: [Tue Nov 2 20:14:51 2021] smpboot: CPU0: Intel(R) Xeon(R) Gold 6226 CPU @ 2.70GHz (family: 0x6, model: 0x3f, stepping: 0x0) [Tue Nov 2 20:14:51 2021] Performance Events: Haswell events, core PMU driver. [Tue Nov 2 20:14:51 2021] core: CPUID marked event: 'cpu cycles' unavailable [Tue Nov 2 20:14:51 2021] core: CPUID marked event: 'instructions' unavailable [Tue Nov 2 20:14:51 2021] core: CPUID marked event: 'bus cycles' unavailable [Tue Nov 2 20:14:51 2021] core: CPUID marked event: 'cache references' unavailable [Tue Nov 2 20:14:51 2021] core: CPUID marked event: 'cache misses' unavailable [Tue Nov 2 20:14:51 2021] core: CPUID marked event: 'branch instructions' unavailable [Tue Nov 2 20:14:51 2021] core: CPUID marked event: 'branch misses' unavailable [Tue Nov 2 20:14:51 2021] ... version: 1 [Tue Nov 2 20:14:51 2021] ... bit width: 48 [Tue Nov 2 20:14:51 2021] ... generic registers: 4 [Tue Nov 2 20:14:51 2021] ... value mask: 0000ffffffffffff [Tue Nov 2 20:14:51 2021] ... max period: 000000007fffffff [Tue Nov 2 20:14:51 2021] ... fixed-purpose events: 0 [Tue Nov 2 20:14:51 2021] ... event mask: 000000000000000f [Tue Nov 2 20:14:51 2021] rcu: Hierarchical SRCU implementation. [Tue Nov 2 20:14:51 2021] NMI watchdog: Perf NMI watchdog permanently disabled [Tue Nov 2 20:14:51 2021] smp: Bringing up secondary CPUs ... [Tue Nov 2 20:14:51 2021] x86: Booting SMP configuration: [Tue Nov 2 20:14:51 2021] .... node #0, CPUs: #1 [Tue Nov 2 20:14:51 2021] Disabled fast string operations [Tue Nov 2 20:14:51 2021] #2 [Tue Nov 2 20:14:51 2021] Disabled fast string operations [Tue Nov 2 20:14:51 2021] #3 [Tue Nov 2 20:14:51 2021] Disabled fast string operations [Tue Nov 2 20:14:51 2021] #4 [Tue Nov 2 20:14:51 2021] Disabled fast string operations [Tue Nov 2 20:14:51 2021] #5 [Tue Nov 2 20:14:51 2021] Disabled fast string operations [Tue Nov 2 20:14:51 2021] #6 [Tue Nov 2 20:14:51 2021] Disabled fast string operations [Tue Nov 2 20:14:51 2021] #7 [Tue Nov 2 20:14:51 2021] Disabled fast string operations [Tue Nov 2 20:14:51 2021] smp: Brought up 1 node, 8 CPUs Here is what showed up in /var/log/warn: Nov 2 20:14:53 prod kernel: core: CPUID marked event: 'cpu cycles' unavailable Nov 2 20:14:53 prod kernel: core: CPUID marked event: 'instructions' unavailable Nov 2 20:14:53 prod kernel: core: CPUID marked event: 'bus cycles' unavailable Nov 2 20:14:53 prod kernel: core: CPUID marked event: 'cache references' unavailable Nov 2 20:14:53 prod kernel: core: CPUID marked event: 'cache misses' unavailable Nov 2 20:14:53 prod kernel: core: CPUID marked event: 'branch instructions' unavailable Nov 2 20:14:53 prod kernel: core: CPUID marked event: 'branch misses' unavailable Nov 2 20:14:53 prod kernel: #2 Nov 2 20:14:53 prod kernel: #3 Nov 2 20:14:53 prod kernel: #4 Nov 2 20:14:53 prod kernel: #5 Nov 2 20:14:53 prod kernel: #6 Nov 2 20:14:53 prod kernel: #7 The "marked event" log messages are normal/expected. The problem here is the meaningless log messages "#2", "#3", etc. appearing in /var/log/warn (on my systems, this file is always monitored automatically and any unexpected warnings result in escalation to humans). The file smpboot.c uses pr_cont() [1] apparently assuming nothing will be logged when each CPU is brought up. But this is incorrect, as obviously "Disabled fast string operations" is a counter-example. Moreover, there is some mixup with pr_cont() being bumped up from log level INFO to WARN by the "Disabled fast string operations" message being logged, although it's logged at INFO [2]. So there are two related problems here. In any case, it's obvious some cleanup is needed in the code's assumptions about how messages are logged at this point in the bootup sequence - both with respect to separate lines and mixing up INFO vs. WARN. [1] https://github.com/torvalds/linux/blob/fc661f2dcb7e41dcda9ae862efb822bb2f46… [2] https://github.com/torvalds/linux/blob/1b1cf8fe99830e8c95f0fe110b02ba51c2bb… -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1191260] kernel 5.14.8 post scriptlets failing
by bugzilla_noreply＠suse.com 16 Nov '21

16 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1191260 https://bugzilla.suse.com/show_bug.cgi?id=1191260#c26 Michal Suchanek <msuchanek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED Flags|needinfo?(dimstar@opensuse. | |org), | |needinfo?(ptesarik(a)suse.com | |) | --- Comment #26 from Michal Suchanek <msuchanek(a)suse.com> --- Update released. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192473] DE0-Nano-SoC boot fails on 15.3
by bugzilla_noreply＠suse.com 16 Nov '21

16 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192473 https://bugzilla.suse.com/show_bug.cgi?id=1192473#c11 --- Comment #11 from Takashi Iwai <tiwai(a)suse.com> --- Thanks. Then the pointer cast doesn't seem helping for avoiding the compiler thinking of the constant size of the source. Then just putting __NO_FORTIFY would be the easiest way to go, as it seems. I'll try to refresh the test kernel again with that later. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192714] [Build 20211114] podman tests triggering gpf in kernel 5.15.1
by bugzilla_noreply＠suse.com 16 Nov '21

16 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192714 https://bugzilla.suse.com/show_bug.cgi?id=1192714#c7 --- Comment #7 from Fabian Vogt <fvogt(a)suse.com> --- Another one, with more info: [ 1562.396848] ================================================================== [ 1562.401006] BUG: KASAN: use-after-free in __bfq_deactivate_entity+0x72b/0xa50 [ 1562.403329] Read of size 8 at addr ffff8880218f60c0 by task swapper/0/0 [ 1562.407362] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G E 5.15.2-0.g5fb85fd-default #1 openSUSE Tumbleweed (unreleased) f1f3b891c72369aebecd2e43e4641a6358867c70 [ 1562.412042] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a-rebuilt.opensuse.org 04/01/2014 [ 1562.416385] Call Trace: [ 1562.418285] <IRQ> [ 1562.420087] dump_stack_lvl+0x46/0x5a [ 1562.422053] print_address_description.constprop.0+0x1f/0x140 [ 1562.424227] ? __bfq_deactivate_entity+0x72b/0xa50 [ 1562.426309] kasan_report.cold+0x7f/0x11b [ 1562.428310] ? update_curr+0x2b0/0x5d0 [ 1562.430273] ? __bfq_deactivate_entity+0x72b/0xa50 [ 1562.432335] __bfq_deactivate_entity+0x72b/0xa50 [ 1562.434377] bfq_deactivate_entity+0xa0/0x1d0 [ 1562.436402] bfq_del_bfqq_busy+0x28a/0x420 [ 1562.438366] ? bfq_requeue_bfqq+0x70/0x70 [ 1562.440295] ? update_curr+0x32f/0x5d0 [ 1562.442179] __bfq_bfqq_expire+0x1a2/0x270 [ 1562.444061] bfq_bfqq_expire+0xd16/0x2160 [ 1562.445896] ? enqueue_entity+0x466/0x2520 [ 1562.447704] ? bfq_end_wr_async_queues+0xe0/0xe0 [ 1562.449543] ? _raw_write_unlock_bh+0x60/0x60 [ 1562.451317] bfq_idle_slice_timer+0x109/0x280 [ 1562.453066] ? bfq_dispatch_request+0x4870/0x4870 [ 1562.454811] __hrtimer_run_queues+0x37d/0x700 [ 1562.456498] ? enqueue_hrtimer+0x1b0/0x1b0 [ 1562.458121] ? kvm_clock_get_cycles+0xd/0x10 [ 1562.459962] ? ktime_get_update_offsets_now+0x6f/0x280 [ 1562.461690] hrtimer_interrupt+0x2c8/0x740 [ 1562.463313] __sysvec_apic_timer_interrupt+0xcd/0x260 [ 1562.465044] sysvec_apic_timer_interrupt+0x6a/0x90 [ 1562.466712] </IRQ> [ 1562.468103] asm_sysvec_apic_timer_interrupt+0x12/0x20 [ 1562.469783] RIP: 0010:native_safe_halt+0xb/0x10 [ 1562.471397] Code: ff ff ff 4c 89 e7 e8 34 e2 91 fe e9 f0 fe ff ff 48 89 ef e8 27 e2 91 fe eb a3 cc cc cc cc cc eb 07 0f 00 2d 27 37 52 00 fb f4 <c3> 0f 1f 40 00 eb 07 0f 00 2d 17 37 52 00 f4 c3 cc cc cc cc cc 0f [ 1562.475550] RSP: 0018:ffffffffb7e07e40 EFLAGS: 00000202 [ 1562.477283] RAX: ffffffffb6b5ded0 RBX: ffffffffb7e24780 RCX: ffffffffb6b36fb6 [ 1562.479197] RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000024b46 [ 1562.481117] RBP: 0000000000000000 R08: 0000000000000001 R09: ffff8880218388a3 [ 1562.483018] R10: ffffed1004307114 R11: 0000000000000001 R12: 0000000000000000 [ 1562.484915] R13: ffffffffb874e6a0 R14: 0000000000000000 R15: dffffc0000000000 [ 1562.486801] ? __cpuidle_text_start+0x8/0x8 [ 1562.488371] ? rcu_eqs_enter.constprop.0+0x86/0xb0 [ 1562.489967] default_idle+0xa/0x10 [ 1562.491412] default_idle_call+0x71/0x1f0 [ 1562.492896] do_idle+0x3e7/0x570 [ 1562.494287] ? arch_cpu_idle_exit+0x40/0x40 [ 1562.495749] cpu_startup_entry+0x19/0x20 [ 1562.497160] start_kernel+0x3bb/0x3d9 [ 1562.498503] secondary_startup_64_no_verify+0xc2/0xcb [ 1562.501055] Allocated by task 463: [ 1562.502353] kasan_save_stack+0x1b/0x40 [ 1562.502359] __kasan_kmalloc+0xa4/0xd0 [ 1562.502362] bfq_pd_alloc+0xa8/0x170 [ 1562.502365] blkg_alloc+0x397/0x540 [ 1562.502369] blkg_create+0x66b/0xcd0 [ 1562.502372] bio_associate_blkg_from_css+0x43c/0xb20 [ 1562.502375] bio_associate_blkg+0x66/0x100 [ 1562.502378] btrfs_map_bio+0x53e/0x10d0 [btrfs] [ 1562.502447] btrfs_submit_metadata_bio+0x209/0x410 [btrfs] [ 1562.502489] submit_one_bio+0x14f/0x1c0 [btrfs] [ 1562.502536] read_extent_buffer_pages+0x557/0xfb0 [btrfs] [ 1562.502585] btree_read_extent_buffer_pages+0x166/0x240 [btrfs] [ 1562.502629] read_tree_block+0x39/0x60 [btrfs] [ 1562.502670] read_block_for_search+0x420/0x710 [btrfs] [ 1562.502710] btrfs_search_slot+0x74f/0x1fe0 [btrfs] [ 1562.502752] btrfs_lookup_csum+0x108/0x350 [btrfs] [ 1562.502797] btrfs_lookup_bio_sums+0x71b/0x13a0 [btrfs] [ 1562.502838] btrfs_submit_data_bio+0x30f/0x7b0 [btrfs] [ 1562.502880] submit_one_bio+0x108/0x1c0 [btrfs] [ 1562.502926] extent_readahead+0x7fb/0xac0 [btrfs] [ 1562.502975] read_pages+0x1bf/0xb00 [ 1562.502979] page_cache_ra_unbounded+0x329/0x720 [ 1562.502982] filemap_fault+0xf35/0x1c70 [ 1562.502984] __do_fault+0xf8/0x390 [ 1562.502988] __handle_mm_fault+0x1a26/0x3020 [ 1562.502990] handle_mm_fault+0x196/0x610 [ 1562.502992] do_user_addr_fault+0x323/0xd60 [ 1562.502995] exc_page_fault+0x5b/0xc0 [ 1562.502997] asm_exc_page_fault+0x1e/0x30 [ 1562.504110] Freed by task 6904: [ 1562.505366] kasan_save_stack+0x1b/0x40 [ 1562.505370] kasan_set_track+0x1c/0x30 [ 1562.505373] kasan_set_free_info+0x20/0x30 [ 1562.505376] __kasan_slab_free+0x10b/0x140 [ 1562.505379] slab_free_freelist_hook+0x8e/0x180 [ 1562.505382] kfree+0xc7/0x400 [ 1562.505385] blkg_free.part.0+0x78/0xf0 [ 1562.505387] rcu_do_batch+0x365/0x1280 [ 1562.505391] rcu_core+0x493/0x8d0 [ 1562.505394] __do_softirq+0x18e/0x544 [ 1562.506477] Last potentially related work creation: [ 1562.507892] kasan_save_stack+0x1b/0x40 [ 1562.507904] kasan_record_aux_stack+0xbe/0xd0 [ 1562.507907] call_rcu+0xe0/0x14e0 [ 1562.507909] netlink_release+0x7ce/0x1140 [ 1562.507912] __sock_release+0xc5/0x270 [ 1562.507916] sock_close+0x11/0x20 [ 1562.507919] __fput+0x1ec/0x8b0 [ 1562.507922] task_work_run+0xd3/0x160 [ 1562.507926] exit_to_user_mode_prepare+0x224/0x230 [ 1562.507930] syscall_exit_to_user_mode+0x18/0x40 [ 1562.507932] do_syscall_64+0x69/0x80 [ 1562.507936] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 1562.509029] Second to last potentially related work creation: [ 1562.510539] kasan_save_stack+0x1b/0x40 [ 1562.510544] kasan_record_aux_stack+0xbe/0xd0 [ 1562.510546] call_rcu+0xe0/0x14e0 [ 1562.510549] netlink_release+0x7ce/0x1140 [ 1562.510551] __sock_release+0xc5/0x270 [ 1562.510554] sock_close+0x11/0x20 [ 1562.510556] __fput+0x1ec/0x8b0 [ 1562.510559] task_work_run+0xd3/0x160 [ 1562.510562] exit_to_user_mode_prepare+0x224/0x230 [ 1562.510564] syscall_exit_to_user_mode+0x18/0x40 [ 1562.510567] do_syscall_64+0x69/0x80 [ 1562.510570] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 1562.511666] The buggy address belongs to the object at ffff8880218f6000 which belongs to the cache kmalloc-2k of size 2048 [ 1562.514812] The buggy address is located 192 bytes inside of 2048-byte region [ffff8880218f6000, ffff8880218f6800) [ 1562.517930] The buggy address belongs to the page: [ 1562.519403] page:00000000d524ba6f refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x218f0 [ 1562.519408] head:00000000d524ba6f order:3 compound_mapcount:0 compound_pincount:0 [ 1562.519410] flags: 0xfffffc0010200(slab|head|node=0|zone=1|lastcpupid=0x1fffff) [ 1562.519416] raw: 000fffffc0010200 0000000000000000 0000000100000001 ffff888001042000 [ 1562.519421] raw: 0000000000000000 0000000000080008 00000001ffffffff 0000000000000000 [ 1562.519423] page dumped because: kasan: bad access detected [ 1562.520576] Memory state around the buggy address: [ 1562.522053] ffff8880218f5f80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc [ 1562.523785] ffff8880218f6000: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb [ 1562.525529] >ffff8880218f6080: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb [ 1562.527247] ^ [ 1562.528790] ffff8880218f6100: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb [ 1562.530535] ffff8880218f6180: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb [ 1562.532267] ================================================================== [ 1562.534011] Disabling lock debugging due to kernel taint -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192740] Upgrade of broadcom-wl fails with "line 1: /usr/lib/module-init-tools/kernel-scriptlets/kmp-pre: No such file or directory"
by bugzilla_noreply＠suse.com 16 Nov '21

16 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192740 https://bugzilla.suse.com/show_bug.cgi?id=1192740#c4 --- Comment #4 from Oliver Kurz <okurz(a)suse.com> --- Thanks for the very quick response and the fixes. (In reply to Takashi Iwai from comment #1) > I guess you need to update suse-module-tools package. That worked as workaround. Thank you! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192473] DE0-Nano-SoC boot fails on 15.3
by bugzilla_noreply＠suse.com 16 Nov '21

16 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192473 https://bugzilla.suse.com/show_bug.cgi?id=1192473#c10 --- Comment #10 from Christian Gross <christian.gross(a)centerofgravity.at> --- Loading Linux 5.3.18-1.gc0621f6-default ... Loading initial ramdisk ... EFI stub: Entering in SVC mode with MMU enabled EFI stub: Booting Linux Kernel... EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map... [ 0.009046] detected buffer overflow in memcpy [ 0.013565] ------------[ cut here ]------------ [ 0.018162] kernel BUG at ../lib/string.c:1090! [ 0.022671] Internal error: Oops - BUG: 0 [#1] SMP ARM [ 0.027784] Modules linked in: [ 0.030824] Supported: No, Unreleased kernel [ 0.035079] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.3.18-1.gc0621f6-default #1 openSUSE Leap 15.2 (unreleased) [ 0.045375] Hardware name: Altera SOCFPGA [ 0.049375] PC is at fortify_panic+0x1c/0x20 [ 0.053630] LR is at vprintk_emit+0x118/0x2a0 [ 0.057966] pc : [<c0da9dc8>] lr : [<c03e6624>] psr: 60000053 [ 0.064201] sp : ee949de0 ip : ee949d20 fp : ee949dec [ 0.069400] r10: c16321b4 r9 : c032ec34 r8 : c12b9118 [ 0.074599] r7 : 00000000 r6 : c1765658 r5 : 00000020 r4 : c176565c [ 0.081094] r3 : 14e8545b r2 : 14e8545b r1 : 00000000 r0 : 00000022 [ 0.087591] Flags: nZCv IRQs on FIQs off Mode SVC_32 ISA ARM Segment user [ 0.094778] Control: 10c5387d Table: 0020404a DAC: 00000055 [ 0.100497] Process swapper/0 (pid: 1, stack limit = 0x(ptrval)) [ 0.106475] Stack: (0xee949de0 to 0xee94a000) [ 0.110814] 9de0: ee949e0c ee949df0 c035fd20 c0da9db8 c1763658 00000001 c1763668 ee942000 [ 0.118955] 9e00: ee949e34 ee949e10 c031e578 c035fc24 ee942000 00000001 2e14e000 c036e4cc [ 0.127095] 9e20: 00000001 ef6d42e8 ee949e54 ee949e38 c036e4fc c031e4ac c15862e8 00000056 [ 0.135236] 9e40: 2e14e000 c036e4cc ee949eb4 ee949e58 c036daa8 c036e4d8 c0daf0f8 c11b1844 [ 0.143376] 9e60: c11b183c c1631f70 c1767140 c1743138 ef6d42e8 c1605fac ffffe000 00000003 [ 0.151516] 9e80: c047b844 00000001 2e14e000 ef6d42e8 c15862e8 00000001 00000056 c1605fb0 [ 0.159656] 9ea0: 2e14e000 00000000 ee949ef4 ee949eb8 c036f998 c036d9fc 00000000 c03e67b8 [ 0.167796] 9ec0: 00000000 00000000 00000000 00000001 000000d4 c1640ed4 c16060e4 c1605fb0 [ 0.175936] 9ee0: 00000000 00000000 ee949f0c ee949ef8 c036fac8 c036f878 00000001 c1605fac [ 0.184076] 9f00: ee949f1c ee949f10 c036fb08 c036fa48 ee949f4c ee949f20 c14267ac c036faf8 [ 0.192216] 9f20: 00000000 c1429b6c ee949f4c c15840e4 c15840e4 00000001 00000000 00000000 [ 0.200356] 9f40: ee949f94 ee949f50 c14013bc c142670c c048c08c c031b8cc ee948000 00000000 [ 0.208495] 9f60: 00000000 00000000 00000000 00000000 c0db2b08 00000000 00000000 00000000 [ 0.216635] 9f80: 00000000 00000000 ee949fac ee949f98 c0db2b20 c14011bc 00000000 c0db2b08 [ 0.224775] 9fa0: 00000000 ee949fb0 c03010b0 c0db2b14 00000000 00000000 00000000 00000000 [ 0.232914] 9fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 0.241054] 9fe0: 00000000 00000000 00000000 00000000 00000013 00000000 00000000 00000000 [ 0.249188] Backtrace: [ 0.251635] [<c0da9dac>] (fortify_panic) from [<c035fd20>] (socfpga_a10_boot_secondary+0x0/0x10c) [ 0.260470] [<c035fc18>] (socfpga_boot_secondary) from [<c031e578>] (__cpu_up+0xd8/0x19c) [ 0.268611] r7:ee942000 r6:c1763668 r5:00000001 r4:c1763658 [ 0.274251] [<c031e4a0>] (__cpu_up) from [<c036e4fc>] (bringup_cpu+0x30/0x104) [ 0.281442] r9:ef6d42e8 r8:00000001 r7:c036e4cc r6:2e14e000 r5:00000001 r4:ee942000 [ 0.289154] [<c036e4cc>] (bringup_cpu) from [<c036daa8>] (cpuhp_invoke_callback+0xb8/0x7bc) [ 0.297466] r7:c036e4cc r6:2e14e000 r5:00000056 r4:c15862e8 [ 0.303103] [<c036d9f0>] (cpuhp_invoke_callback) from [<c036f998>] (_cpu_up+0x12c/0x1d0) [ 0.311157] r10:00000000 r9:2e14e000 r8:c1605fb0 r7:00000056 r6:00000001 r5:c15862e8 [ 0.318948] r4:ef6d42e8 [ 0.321472] [<c036f86c>] (_cpu_up) from [<c036fac8>] (do_cpu_up+0x8c/0xb0) [ 0.328316] r10:00000000 r9:00000000 r8:c1605fb0 r7:c16060e4 r6:c1640ed4 r5:000000d4 [ 0.336107] r4:00000001 [ 0.338630] [<c036fa3c>] (do_cpu_up) from [<c036fb08>] (cpu_up+0x1c/0x24) [ 0.345385] r5:c1605fac r4:00000001 [ 0.348949] [<c036faec>] (cpu_up) from [<c14267ac>] (smp_init+0xac/0xf8) [ 0.355622] [<c1426700>] (smp_init) from [<c14013bc>] (kernel_init_freeable+0x20c/0x40c) [ 0.363675] r8:00000000 r7:00000000 r6:00000001 r5:c15840e4 r4:c15840e4 [ 0.370350] [<c14011b0>] (kernel_init_freeable) from [<c0db2b20>] (kernel_init+0x18/0x128) [ 0.378576] r10:00000000 r9:00000000 r8:00000000 r7:00000000 r6:00000000 r5:c0db2b08 [ 0.386366] r4:00000000 [ 0.388893] [<c0db2b08>] (kernel_init) from [<c03010b0>] (ret_from_fork+0x14/0x24) [ 0.396425] Exception stack(0xee949fb0 to 0xee949ff8) [ 0.401452] 9fa0: 00000000 00000000 00000000 00000000 [ 0.409592] 9fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 0.417731] 9fe0: 00000000 00000000 00000000 00000000 00000013 00000000 [ 0.424312] r5:c0db2b08 r4:00000000 [ 0.427874] Code: e1a01000 e3070774 e34c012b ebd8f49a (e7f001f2) [ 0.433950] ---[ end trace d15559ddf68b8b2c ]--- [ 0.438551] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b [ 0.446178] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]--- -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189791] btrfs filesystem corruptions with HyperPAV
by bugzilla_noreply＠suse.com 16 Nov '21

16 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1189791 Ihno Krumreich <ihno(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(bugproxy(a)us.ibm.c | |om) | -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192714] [Build 20211114] podman tests triggering gpf in kernel 5.15.1
by bugzilla_noreply＠suse.com 16 Nov '21

16 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192714 https://bugzilla.suse.com/show_bug.cgi?id=1192714#c6 --- Comment #6 from Fabian Vogt <fvogt(a)suse.com> --- I built kernel-default with KASAN enabled (https://build.opensuse.org/package/show/home:favogt:boo1192714/kernel-source) and installed that in a local VM (configured like openQA). Inside, I ran "podman run --rm --entrypoint 'printenv' myapp WORLD_VAR | grep Arda" (command which freezes in openQA) in a loop and ran another instance of that in another tty. That immediately resulted in this splat: [ 235.949241] ================================================================== [ 235.950326] BUG: KASAN: use-after-free in __bfq_deactivate_entity+0x9cb/0xa50 [ 235.951369] Read of size 8 at addr ffff88800693c0c0 by task runc:[2:INIT]/10544 [ 235.953476] CPU: 0 PID: 10544 Comm: runc:[2:INIT] Tainted: G E 5.15.2-0.g5fb85fd-default #1 openSUSE Tumbleweed (unreleased) f1f3b891c72369aebecd2e43e4641a6358867c70 [ 235.955726] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a-rebuilt.opensuse.org 04/01/2014 [ 235.958007] Call Trace: [ 235.959157] <IRQ> [ 235.960287] dump_stack_lvl+0x46/0x5a [ 235.961412] print_address_description.constprop.0+0x1f/0x140 [ 235.962556] ? __bfq_deactivate_entity+0x9cb/0xa50 [ 235.963707] kasan_report.cold+0x7f/0x11b [ 235.964841] ? __bfq_deactivate_entity+0x9cb/0xa50 [ 235.965970] __bfq_deactivate_entity+0x9cb/0xa50 [ 235.967092] ? update_curr+0x32f/0x5d0 [ 235.968227] bfq_deactivate_entity+0xa0/0x1d0 [ 235.969365] bfq_del_bfqq_busy+0x28a/0x420 [ 235.970481] ? resched_curr+0x116/0x1d0 [ 235.971573] ? bfq_requeue_bfqq+0x70/0x70 [ 235.972657] ? check_preempt_wakeup+0x52b/0xbc0 [ 235.973748] __bfq_bfqq_expire+0x1a2/0x270 [ 235.974822] bfq_bfqq_expire+0xd16/0x2160 [ 235.975893] ? try_to_wake_up+0x4ee/0x1260 [ 235.976965] ? bfq_end_wr_async_queues+0xe0/0xe0 [ 235.978039] ? _raw_write_unlock_bh+0x60/0x60 [ 235.979105] ? _raw_spin_lock_irq+0x81/0xe0 [ 235.980162] bfq_idle_slice_timer+0x109/0x280 [ 235.981199] ? bfq_dispatch_request+0x4870/0x4870 [ 235.982220] __hrtimer_run_queues+0x37d/0x700 [ 235.983242] ? enqueue_hrtimer+0x1b0/0x1b0 [ 235.984278] ? kvm_clock_get_cycles+0xd/0x10 [ 235.985301] ? ktime_get_update_offsets_now+0x6f/0x280 [ 235.986317] hrtimer_interrupt+0x2c8/0x740 [ 235.987321] __sysvec_apic_timer_interrupt+0xcd/0x260 [ 235.988357] sysvec_apic_timer_interrupt+0x6a/0x90 [ 235.989373] </IRQ> [ 235.990355] asm_sysvec_apic_timer_interrupt+0x12/0x20 [ 235.991366] RIP: 0010:do_seccomp+0x4f5/0x1f40 [ 235.992376] Code: 00 fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 cb 14 00 00 48 8b bd d8 0b 00 00 c6 07 00 0f 1f 40 00 fb 66 0f 1f 44 00 00 <8b> 4c 24 30 85 c9 0f 85 06 07 00 00 8b 54 24 04 85 d2 74 19 4d 85 [ 235.994481] RSP: 0018:ffffc900020cfd48 EFLAGS: 00000246 [ 235.995546] RAX: dffffc0000000000 RBX: 1ffff92000419fb1 RCX: ffffffffb9a8d89d [ 235.996638] RDX: 1ffff1100080f17b RSI: 0000000000000008 RDI: ffff888008c56040 [ 235.997717] RBP: ffff888004078000 R08: 0000000000000001 R09: ffff88800407800f [ 235.998784] R10: ffffed100080f001 R11: 0000000000000001 R12: 00000000ffffffff [ 235.999852] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 [ 236.000906] ? do_seccomp+0xfed/0x1f40 [ 236.001937] ? do_seccomp+0xfed/0x1f40 [ 236.002938] ? get_nth_filter+0x2e0/0x2e0 [ 236.003932] ? security_task_prctl+0x66/0xd0 [ 236.004910] __do_sys_prctl+0x420/0xd60 [ 236.005842] ? handle_mm_fault+0x196/0x610 [ 236.006739] ? __ia32_compat_sys_getrusage+0x90/0x90 [ 236.007611] ? up_read+0x15/0x90 [ 236.008477] do_syscall_64+0x5c/0x80 [ 236.009349] ? exc_page_fault+0x60/0xc0 [ 236.010219] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 236.011094] RIP: 0033:0x561fa9ceec6a [ 236.011976] Code: e8 db 46 f8 ff 48 8b 7c 24 10 48 8b 74 24 18 48 8b 54 24 20 4c 8b 54 24 28 4c 8b 44 24 30 4c 8b 4c 24 38 48 8b 44 24 08 0f 05 <48> 3d 01 f0 ff ff 76 20 48 c7 44 24 40 ff ff ff ff 48 c7 44 24 48 [ 236.013823] RSP: 002b:000000c000116e38 EFLAGS: 00000216 ORIG_RAX: 000000000000009d [ 236.014778] RAX: ffffffffffffffda RBX: 000000c000028000 RCX: 0000561fa9ceec6a [ 236.015748] RDX: 000000c000116ee0 RSI: 0000000000000002 RDI: 0000000000000016 [ 236.016716] RBP: 000000c000116e90 R08: 0000000000000000 R09: 0000000000000000 [ 236.017685] R10: 0000000000000000 R11: 0000000000000216 R12: 00000000000000b8 [ 236.018645] R13: 00000000000000b7 R14: 0000000000000200 R15: 0000000000000004 [ 236.020558] Allocated by task 485: [ 236.021511] kasan_save_stack+0x1b/0x40 [ 236.022460] __kasan_kmalloc+0xa4/0xd0 [ 236.023410] bfq_pd_alloc+0xa8/0x170 [ 236.024351] blkg_alloc+0x397/0x540 [ 236.025287] blkg_create+0x66b/0xcd0 [ 236.026219] bio_associate_blkg_from_css+0x43c/0xb20 [ 236.027161] bio_associate_blkg+0x66/0x100 [ 236.028098] submit_extent_page+0x744/0x1380 [btrfs] [ 236.029126] __extent_writepage_io+0x605/0xaa0 [btrfs] [ 236.030113] __extent_writepage+0x360/0x740 [btrfs] [ 236.031093] extent_write_cache_pages+0x5a7/0xa50 [btrfs] [ 236.032084] extent_writepages+0xcb/0x1a0 [btrfs] [ 236.033063] do_writepages+0x188/0x720 [ 236.033997] filemap_fdatawrite_wbc+0x19f/0x2b0 [ 236.034929] filemap_fdatawrite_range+0x99/0xd0 [ 236.035855] btrfs_fdatawrite_range+0x46/0xf0 [btrfs] [ 236.036833] start_ordered_ops.constprop.0+0xb6/0x110 [btrfs] [ 236.037803] btrfs_sync_file+0x1bf/0xe70 [btrfs] [ 236.038747] __x64_sys_fsync+0x51/0x80 [ 236.039622] do_syscall_64+0x5c/0x80 [ 236.040468] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 236.042137] Freed by task 10561: [ 236.042966] kasan_save_stack+0x1b/0x40 [ 236.043802] kasan_set_track+0x1c/0x30 [ 236.044628] kasan_set_free_info+0x20/0x30 [ 236.045437] __kasan_slab_free+0x10b/0x140 [ 236.046256] slab_free_freelist_hook+0x8e/0x180 [ 236.047081] kfree+0xc7/0x400 [ 236.047907] blkg_free.part.0+0x78/0xf0 [ 236.048736] rcu_do_batch+0x365/0x1280 [ 236.049558] rcu_core+0x493/0x8d0 [ 236.050376] __do_softirq+0x18e/0x544 [ 236.051992] The buggy address belongs to the object at ffff88800693c000 which belongs to the cache kmalloc-2k of size 2048 [ 236.053672] The buggy address is located 192 bytes inside of 2048-byte region [ffff88800693c000, ffff88800693c800) [ 236.055328] The buggy address belongs to the page: [ 236.056136] page:00000000544d2d6e refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x6938 [ 236.056954] head:00000000544d2d6e order:3 compound_mapcount:0 compound_pincount:0 [ 236.057764] flags: 0xfffffc0010200(slab|head|node=0|zone=1|lastcpupid=0x1fffff) [ 236.058588] raw: 000fffffc0010200 dead000000000100 dead000000000122 ffff888001042000 [ 236.059439] raw: 0000000000000000 0000000000080008 00000001ffffffff 0000000000000000 [ 236.060293] page dumped because: kasan: bad access detected [ 236.062000] Memory state around the buggy address: [ 236.062862] ffff88800693bf80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc [ 236.063756] ffff88800693c000: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb [ 236.064645] >ffff88800693c080: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb [ 236.065525] ^ [ 236.066412] ffff88800693c100: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb [ 236.067333] ffff88800693c180: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb [ 236.068240] ================================================================== [ 236.069174] Disabling lock debugging due to kernel taint -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192714] [Build 20211114] podman tests triggering gpf in kernel 5.15.1
by bugzilla_noreply＠suse.com 16 Nov '21

16 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192714 https://bugzilla.suse.com/show_bug.cgi?id=1192714#c5 --- Comment #5 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Jiri Slaby from comment #3) > fedora with 5.14.16 hit the same: > https://github.com/coreos/fedora-coreos-tracker/issues/1021 > https://bugzilla.redhat.com/show_bug.cgi?id=2022819 We also hit it with 5.14.14 now: https://openqa.opensuse.org/tests/2038671#step/podman/182 (In reply to Takashi Iwai from comment #4) > If that's the same bug, it could be there for long time: > https://lkml.org/lkml/2020/10/9/1120 > > Can the Oops be reproduced reliably? The oops message was only printed in a single run so far, but the freeze happens fairly often. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192714] [Build 20211114] podman tests triggering gpf in kernel 5.15.1
by bugzilla_noreply＠suse.com 16 Nov '21

16 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192714 https://bugzilla.suse.com/show_bug.cgi?id=1192714#c4 --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- If that's the same bug, it could be there for long time: https://lkml.org/lkml/2020/10/9/1120 Can the Oops be reproduced reliably? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192714] [Build 20211114] podman tests triggering gpf in kernel 5.15.1
by bugzilla_noreply＠suse.com 16 Nov '21

16 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192714 https://bugzilla.suse.com/show_bug.cgi?id=1192714#c3 --- Comment #3 from Jiri Slaby <jslaby(a)suse.com> --- fedora with 5.14.16 hit the same: https://github.com/coreos/fedora-coreos-tracker/issues/1021 https://bugzilla.redhat.com/show_bug.cgi?id=2022819 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192473] DE0-Nano-SoC boot fails on 15.3
by bugzilla_noreply＠suse.com 16 Nov '21

16 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192473 https://bugzilla.suse.com/show_bug.cgi?id=1192473#c9 --- Comment #9 from Takashi Iwai <tiwai(a)suse.com> --- So the problem remains in the upstream code, as expected. I'm building a Leap 15.3 kernel with the test fix patch. It's being built in OBS home:tiwai:bsc1192473 repo. Could you give it a try later (once after the build finishes)? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192232] Dock stations work but the devices become disconnected periodically
by bugzilla_noreply＠suse.com 16 Nov '21

16 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192232 http://bugzilla.opensuse.org/show_bug.cgi?id=1192232#c3 Sebastian Turza��ski <dpbasti(a)wp.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #3 from Sebastian Turza��ski <dpbasti(a)wp.pl> --- I have disabled powertop service and removed+reinstalled TLP and now I cannot reproduce the problem anymore. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192549] Kernel 5.3.18-lp152.98-default breaks getdents(2) system call on NFS shares
by bugzilla_noreply＠suse.com 15 Nov '21

15 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192549 https://bugzilla.suse.com/show_bug.cgi?id=1192549#c22 --- Comment #22 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-SU-2021:1477-1: An update that solves 15 vulnerabilities and has 41 fixes is now available. Category: security (important) Bug References: 1065729,1085030,1100416,1129735,1152489,1154353,1156395,1157177,1167773,1172073,1173604,1176940,1184673,1185762,1186109,1187167,1188563,1188876,1188983,1188985,1189841,1190006,1190067,1190349,1190351,1190479,1190620,1190642,1190795,1190941,1191229,1191238,1191241,1191315,1191317,1191343,1191349,1191384,1191449,1191450,1191451,1191452,1191455,1191456,1191628,1191731,1191800,1191934,1191958,1192036,1192040,1192041,1192107,1192145,1192267,1192549 CVE References: CVE-2018-13405,CVE-2021-33033,CVE-2021-34556,CVE-2021-3542,CVE-2021-35477,CVE-2021-3655,CVE-2021-3715,CVE-2021-3760,CVE-2021-3772,CVE-2021-3896,CVE-2021-41864,CVE-2021-42008,CVE-2021-42252,CVE-2021-42739,CVE-2021-43056 JIRA References: Sources used: openSUSE Leap 15.2 (src): kernel-debug-5.3.18-lp152.102.1, kernel-default-5.3.18-lp152.102.1, kernel-default-base-5.3.18-lp152.102.1.lp152.8.49.1, kernel-docs-5.3.18-lp152.102.1, kernel-kvmsmall-5.3.18-lp152.102.1, kernel-obs-build-5.3.18-lp152.102.1, kernel-obs-qa-5.3.18-lp152.102.1, kernel-preempt-5.3.18-lp152.102.1, kernel-source-5.3.18-lp152.102.1, kernel-syms-5.3.18-lp152.102.1 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191229] [Staging][rpm4.17] Kernel fails to build with rpm 4.17
by bugzilla_noreply＠suse.com 15 Nov '21

15 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1191229 https://bugzilla.suse.com/show_bug.cgi?id=1191229#c23 --- Comment #23 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-SU-2021:1477-1: An update that solves 15 vulnerabilities and has 41 fixes is now available. Category: security (important) Bug References: 1065729,1085030,1100416,1129735,1152489,1154353,1156395,1157177,1167773,1172073,1173604,1176940,1184673,1185762,1186109,1187167,1188563,1188876,1188983,1188985,1189841,1190006,1190067,1190349,1190351,1190479,1190620,1190642,1190795,1190941,1191229,1191238,1191241,1191315,1191317,1191343,1191349,1191384,1191449,1191450,1191451,1191452,1191455,1191456,1191628,1191731,1191800,1191934,1191958,1192036,1192040,1192041,1192107,1192145,1192267,1192549 CVE References: CVE-2018-13405,CVE-2021-33033,CVE-2021-34556,CVE-2021-3542,CVE-2021-35477,CVE-2021-3655,CVE-2021-3715,CVE-2021-3760,CVE-2021-3772,CVE-2021-3896,CVE-2021-41864,CVE-2021-42008,CVE-2021-42252,CVE-2021-42739,CVE-2021-43056 JIRA References: Sources used: openSUSE Leap 15.2 (src): kernel-debug-5.3.18-lp152.102.1, kernel-default-5.3.18-lp152.102.1, kernel-default-base-5.3.18-lp152.102.1.lp152.8.49.1, kernel-docs-5.3.18-lp152.102.1, kernel-kvmsmall-5.3.18-lp152.102.1, kernel-obs-build-5.3.18-lp152.102.1, kernel-obs-qa-5.3.18-lp152.102.1, kernel-preempt-5.3.18-lp152.102.1, kernel-source-5.3.18-lp152.102.1, kernel-syms-5.3.18-lp152.102.1 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192714] New: [Build 20211114] podman tests triggering gpf in kernel 5.15.1
by bugzilla_noreply＠suse.com 15 Nov '21

15 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192714 Bug ID: 1192714 Summary: [Build 20211114] podman tests triggering gpf in kernel 5.15.1 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/2035837/modules/podm an/steps/190 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario microos-Tumbleweed-DVD-x86_64-container-host@64bit fails in [podman](https://openqa.opensuse.org/tests/2035837/modules/podman/steps/190) [ 584.097423][ T90] general protection fault, probably for non-canonical address 0x10100060000017d: 0000 [#1] SMP PTI [ 584.101544][ T90] CPU: 0 PID: 90 Comm: kworker/0:1H Not tainted 5.15.1-1-default #1 openSUSE Tumbleweed 97f095665b737bda12eb7baaa176e74b709dc583 [ 584.105238][ T90] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a-rebuilt.opensuse.org 04/01/2014 [ 584.108998][ T90] Workqueue: kblockd blk_mq_run_work_fn [ 584.110773][ T90] RIP: 0010:__bfq_deactivate_entity+0x154/0x220 [ 584.112630][ T90] Code: 8b 43 28 48 2b 41 28 48 85 c0 7e 04 48 89 5d 18 48 8b 45 08 4c 8d 7d 08 48 85 c0 0f 84 c0 00 00 00 48 8b 7b 28 eb 03 48 89 c8 <48> 8b 48 28 48 8d 70 10 48 8d 50 08 48 29 f9 48 85 c9 48 0f 4f d6 [ 584.117149][ T90] RSP: 0000:ffffa91b00d13c00 EFLAGS: 00010006 [ 584.118951][ T90] RAX: 0101000600000155 RBX: ffff8f43a8792098 RCX: 0101000600000155 [ 584.121015][ T90] RDX: ffff8f4384634548 RSI: ffff8f4384634550 RDI: 0000016445c7b623 [ 584.123043][ T90] RBP: ffff8f4386165958 R08: ffff8f4386165958 R09: 0000000000000000 [ 584.125125][ T90] R10: 00000087f7c61c86 R11: 0000000000000000 R12: 0000000000000001 [ 584.127174][ T90] R13: 0000000000000001 R14: 0000000000000000 R15: ffff8f4386165960 [ 584.129196][ T90] FS: 0000000000000000(0000) GS:ffff8f43bec00000(0000) knlGS:0000000000000000 [ 584.131389][ T90] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 584.133271][ T90] CR2: 000055ac46cbd0d8 CR3: 000000002b6f8000 CR4: 00000000000006f0 [ 584.135337][ T90] Call Trace: [ 584.136818][ T90] bfq_deactivate_entity+0x4f/0xc0 [ 584.138493][ T90] bfq_del_bfqq_busy+0xc9/0x180 [ 584.140132][ T90] bfq_remove_request+0x11d/0x390 [ 584.141744][ T90] ? bfq_may_expire_for_budg_timeout+0x7f/0x1b0 [ 584.143501][ T90] ? bfq_bfqq_served+0xb0/0x1c0 [ 584.145050][ T90] bfq_dispatch_request+0x40d/0x1240 [ 584.146631][ T90] ? update_load_avg+0x7a/0x5a0 [ 584.148166][ T90] __blk_mq_do_dispatch_sched+0x1f1/0x2d0 [ 584.149762][ T90] __blk_mq_sched_dispatch_requests+0xf6/0x140 [ 584.151407][ T90] blk_mq_sched_dispatch_requests+0x30/0x60 [ 584.153010][ T90] __blk_mq_run_hw_queue+0x2d/0x60 [ 584.154523][ T90] process_one_work+0x1e4/0x380 [ 584.156030][ T90] worker_thread+0x50/0x410 [ 584.157447][ T90] ? process_one_work+0x380/0x380 [ 584.158911][ T90] kthread+0x127/0x150 [ 584.160288][ T90] ? set_kthread_struct+0x40/0x40 [ 584.161752][ T90] ret_from_fork+0x22/0x30 [ 584.163112][ T90] Modules linked in: xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_counter xt_comment nft_compat nf_tables nfnetlink veth af_packet iscsi_ibft iscsi_boot_sysfs dm_mod rfkill snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec ppdev snd_hda_core snd_hwdep snd_pcm virtio_net pcspkr snd_timer snd joydev parport_pc net_failover soundcore failover i2c_piix4 tiny_power_button parport button fuse configfs ip_tables x_tables hid_generic usbhid bochs drm_vram_helper drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core xhci_pci xhci_pci_renesas drm_ttm_helper ttm xhci_hcd drm sr_mod cdrom ata_generic usbcore virtio_scsi serio_raw virtio_blk floppy ata_piix qemu_fw_cfg overlay btrfs blake2b_generic libcrc32c xor raid6_pq sg br_netfilter bridge stp llc [ 584.178930][ T90] ---[ end trace 9b57d9c956a65e78 ]--- [ 584.180613][ T90] RIP: 0010:__bfq_deactivate_entity+0x154/0x220 [ 584.182305][ T90] Code: 8b 43 28 48 2b 41 28 48 85 c0 7e 04 48 89 5d 18 48 8b 45 08 4c 8d 7d 08 48 85 c0 0f 84 c0 00 00 00 48 8b 7b 28 eb 03 48 89 c8 <48> 8b 48 28 48 8d 70 10 48 8d 50 08 48 29 f9 48 85 c9 48 0f 4f d6 [ 584.186605][ T90] RSP: 0000:ffffa91b00d13c00 EFLAGS: 00010006 [ 584.188297][ T90] RAX: 0101000600000155 RBX: ffff8f43a8792098 RCX: 0101000600000155 [ 584.190175][ T90] RDX: ffff8f4384634548 RSI: ffff8f4384634550 RDI: 0000016445c7b623 [ 584.192050][ T90] RBP: ffff8f4386165958 R08: ffff8f4386165958 R09: 0000000000000000 [ 584.193893][ T90] R10: 00000087f7c61c86 R11: 0000000000000000 R12: 0000000000000001 [ 584.195726][ T90] R13: 0000000000000001 R14: 0000000000000000 R15: ffff8f4386165960 [ 584.197541][ T90] FS: 0000000000000000(0000) GS:ffff8f43bec00000(0000) knlGS:0000000000000000 [ 584.199490][ T90] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 584.201127][ T90] CR2: 000055ac46cbd0d8 CR3: 000000002b6f8000 CR4: 00000000000006f0 ## Test suite description ## Reproducible Fails since (at least) Build [20211114](https://openqa.opensuse.org/tests/2035837) (current job) ## Expected result Last good: [20211113](https://openqa.opensuse.org/tests/2034900) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=microos… -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1192714] [Build 20211114] podman tests triggering gpf in kernel 5.15.1
by bugzilla_noreply＠suse.com 15 Nov '21

15 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192714 https://bugzilla.suse.com/show_bug.cgi?id=1192714#c1 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt(a)suse.com --- Comment #1 from Fabian Vogt <fvogt(a)suse.com> --- There are two more failures in openQA at the same point (starting a container with podman). Those don't show the GPF, but the system is frozen. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188970] Xorg crashes with a segmentation fault when a secondary USB display using DisplayLink is connected
by bugzilla_noreply＠suse.com 15 Nov '21

15 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1188970 http://bugzilla.opensuse.org/show_bug.cgi?id=1188970#c62 --- Comment #62 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Thomas Zimmermann from comment #57) > I cannot reproduce the issue. > > STR: > > * Installed the latest SLE15-SP3 LEAP installer without updates. Just to make sure, could you try rather with SLE15-SP3 installer? The quarter-update-1 should be new enough and still have the problem accordingly. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 15 Nov '21

15 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c46 Dominique Leuenberger <dleuenberger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(dimstar@opensuse. | |org) | --- Comment #46 from Dominique Leuenberger <dleuenberger(a)suse.com> --- (In reply to Martin Wilck from comment #45) > (In reply to Michal Suchanek from comment #43) > > > It will need some adjustment to include kernel-default-extra and > > uncompression support but should be doable. > > Dominique, is this a requirement from the distro engineering side? IMO for > the kernel side, introducing new flavors just for this undesirable, in > particular because we may need multiple such flavors as Jiri pointed out. In > a way we'd create an orthogonal new "dimension" of kernel flavors just for > compression. Considering we do need this hack (at least at the moment) only on the Live images (which are, essentially, just a big collection of hacks anyway) I don't think it's justified to increase the burden on the kernel package for this -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 15 Nov '21

15 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c45 Martin Wilck <martin.wilck(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(dimstar@opensuse. | |org) --- Comment #45 from Martin Wilck <martin.wilck(a)suse.com> --- (In reply to Michal Suchanek from comment #43) > It will need some adjustment to include kernel-default-extra and > uncompression support but should be doable. Dominique, is this a requirement from the distro engineering side? IMO for the kernel side, introducing new flavors just for this undesirable, in particular because we may need multiple such flavors as Jiri pointed out. In a way we'd create an orthogonal new "dimension" of kernel flavors just for compression. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 15 Nov '21

15 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c44 --- Comment #44 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Michal Suchanek from comment #43) > I suppose we could build kernel-default-uncompressed as we build > kernel-default-base. Side note: is only -default enough? I have pae, lpae on my mind. I don't think pae ends up on the installation media, not sure about arm... -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 15 Nov '21

15 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c43 --- Comment #43 from Michal Suchanek <msuchanek(a)suse.com> --- (In reply to Dominique Leuenberger from comment #12) > (In reply to Martin Wilck from comment #11) > > The idea would be something like > > > > find /usr/lib/modules -name '*.ko.xz' -print0 | xargs -0 xz -d > > > > after installing the kernel, and before creating the image. > > OUCH :) > > rpm -qV kernel-default will hate us for this and eat our kittens > > (but as a workaround probably doable for the live images; openQA debug > helpers will get a bit noisy) I suppose we could build kernel-default-uncompressed as we build kernel-default-base. It will need some adjustment to include kernel-default-extra and uncompression support but should be doable. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192194] irq 40: nobody cared (try booting with the "irqpoll" option)
by bugzilla_noreply＠suse.com 15 Nov '21

15 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192194 http://bugzilla.opensuse.org/show_bug.cgi?id=1192194#c11 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME Flags|needinfo?(jshand2013@gmail. | |com) | --- Comment #11 from Takashi Iwai <tiwai(a)suse.com> --- OK, thanks, then let's close the bug for now. Feel free to reopen if you encounter the problem again. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192194] irq 40: nobody cared (try booting with the "irqpoll" option)
by bugzilla_noreply＠suse.com 15 Nov '21

15 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192194 http://bugzilla.opensuse.org/show_bug.cgi?id=1192194#c10 --- Comment #10 from John Shand <jshand2013(a)gmail.com> --- this error hasn't happened again, perhaps it was a one off. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192664] New: Failed to start Entropy Daemon based on the HAVEGE algorithm.
by bugzilla_noreply＠suse.com 14 Nov '21

14 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192664 Bug ID: 1192664 Summary: Failed to start Entropy Daemon based on the HAVEGE algorithm. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since latest TW snapshot 20211111, I get Failed to start Entropy Daemon based on the HAVEGE algorithm. journal entries: haveged[217]: haveged: command socket is listening at fd 3 haveged[217]: haveged: Fail:set_watermark()! haveged[217]: haveged starting up systemd[1]: haveged.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: haveged.service: Failed with result 'exit-code'. systemd[1]: haveged.service: Scheduled restart job, restart counter is at 1. haveged[402]: haveged: command socket is listening at fd 3 haveged[402]: haveged: Fail:set_watermark()! haveged[402]: haveged starting up systemd[1]: haveged.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: haveged.service: Failed with result 'exit-code'. systemd[1]: haveged.service: Scheduled restart job, restart counter is at 2. haveged[554]: haveged: command socket is listening at fd 3 haveged[554]: haveged: Fail:set_watermark()! haveged[554]: haveged starting up systemd[1]: haveged.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: haveged.service: Failed with result 'exit-code'. systemd[1]: haveged.service: Scheduled restart job, restart counter is at 3. haveged[563]: haveged: command socket is listening at fd 3 haveged[563]: haveged: Fail:set_watermark()! haveged[563]: haveged starting up systemd[1]: haveged.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: haveged.service: Failed with result 'exit-code'. systemd[1]: haveged.service: Scheduled restart job, restart counter is at 4. haveged[576]: haveged: command socket is listening at fd 3 haveged[576]: haveged: Fail:set_watermark()! haveged[576]: haveged starting up systemd[1]: haveged.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: haveged.service: Failed with result 'exit-code'. systemd[1]: haveged.service: Scheduled restart job, restart counter is at 5. haveged[586]: haveged: command socket is listening at fd 3 haveged[586]: haveged: Fail:set_watermark()! haveged[586]: haveged starting up systemd[1]: haveged.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: haveged.service: Failed with result 'exit-code'. systemd[1]: haveged.service: Scheduled restart job, restart counter is at 6. haveged[593]: haveged: command socket is listening at fd 3 haveged[593]: haveged: Fail:set_watermark()! haveged[593]: haveged starting up systemd[1]: haveged.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: haveged.service: Failed with result 'exit-code'. systemd[1]: haveged.service: Scheduled restart job, restart counter is at 7. systemd[1]: haveged.service: Start request repeated too quickly. systemd[1]: haveged.service: Failed with result 'exit-code'. systemd[1]: Starting Tell haveged about new root... haveged[739]: haveged: command socket is listening at fd 3 systemd[1]: haveged-switch-root.service: Deactivated successfully. systemd[1]: Finished Tell haveged about new root. systemd[1]: haveged.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: haveged.service: Failed with result 'exit-code'. haveged[1092]: haveged: command socket is listening at fd 3 haveged[1092]: haveged: Fail:set_watermark()! haveged[1092]: haveged starting up haveged[1204]: haveged: command socket is listening at fd 3 haveged[1204]: haveged: Fail:set_watermark()! haveged[1204]: haveged starting up haveged[1379]: haveged: command socket is listening at fd 3 haveged[1379]: haveged: Fail:set_watermark()! haveged[1379]: haveged starting up systemd[1]: haveged.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: haveged.service: Failed with result 'exit-code'. systemd[1]: haveged.service: Scheduled restart job, restart counter is at 3. haveged[1572]: haveged: command socket is listening at fd 3 haveged[1572]: haveged: Fail:set_watermark()! haveged[1572]: haveged starting up systemd[1]: haveged.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: haveged.service: Failed with result 'exit-code'. systemd[1]: haveged.service: Scheduled restart job, restart counter is at 4. haveged[1845]: haveged: command socket is listening at fd 3 haveged[1845]: haveged: Fail:set_watermark()! haveged[1845]: haveged starting up systemd[1]: haveged.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: haveged.service: Failed with result 'exit-code'. systemd[1]: haveged.service: Scheduled restart job, restart counter is at 5. systemd[1]: haveged.service: Start request repeated too quickly. systemd[1]: haveged.service: Failed with result 'exit-code'. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1190256] Keyboard not working after cold-boot on ASUS Zenbook 14 UM425UA with Tumbleweed 20210904
by bugzilla_noreply＠suse.com 13 Nov '21

13 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1190256 https://bugzilla.suse.com/show_bug.cgi?id=1190256#c24 --- Comment #24 from Takashi Iwai <tiwai(a)suse.com> --- Thanks for testing. I submitted the fix now and will backport it to TW kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190256] Keyboard not working after cold-boot on ASUS Zenbook 14 UM425UA with Tumbleweed 20210904
by bugzilla_noreply＠suse.com 12 Nov '21

12 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1190256 https://bugzilla.suse.com/show_bug.cgi?id=1190256#c23 Michael Krapp <mkrapp(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #852400|0 |1 is obsolete| | Attachment #852402|0 |1 is obsolete| | Attachment #852445|0 |1 is obsolete| | Attachment #852567|0 |1 is obsolete| | Flags|needinfo?(mkrapp(a)suse.com) | --- Comment #23 from Michael Krapp <mkrapp(a)suse.com> --- Created attachment 853721 --> https://bugzilla.suse.com/attachment.cgi?id=853721&action=edit dmesg, cold boot with 5.15.0-1.g8b20058 That one works like a charm :) I tried several times and it worked at every boot. Thank you! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192047] New: Camera module does not work with ov5647 device on RPi3B+
by bugzilla_noreply＠suse.com 12 Nov '21

12 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192047 Bug ID: 1192047 Summary: Camera module does not work with ov5647 device on RPi3B+ Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de CC: afaerber(a)suse.com, dmueller(a)suse.com, mbrugger(a)suse.com Found By: --- Blocker: --- Created attachment 853365 --> http://bugzilla.opensuse.org/attachment.cgi?id=853365&action=edit dmesg log I tried to use an IR camera module, based on OV5647 device, but I fail to get it working. On top of Tumbleweed, I installed raspberrypi-firmware-extra and created /boot/efi/extraconfig.txt with: # Camera IR ov5647 start_x=1 gpu_mem=128 dtoverlay=ov5647 # I2C dtparam=i2c_arm=on On reboot, ov5647 and bcm2835_v4l2 kernel drivers are loaded, but no error is displayed in dmesg and there is no /dev/video* devices. 'i2cdetect -l' retuns: i2c-0 i2c i2c-11-mux (chan_id 0) I2C adapter i2c-1 i2c bcm2835 (i2c@7e804000) I2C adapter i2c-2 i2c bcm2835 (i2c@7e805000) I2C adapter i2c-10 i2c i2c-11-mux (chan_id 1) I2C adapter i2c-11 i2c bcm2835 (i2c@7e205000) I2C adapter and 'i2cdetect -y 10' confirms that i2c address 36 is used by a driver, likely ov5647: 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- UU -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- Any idea what I am missing? -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 1192625] New: Sound issues kernel 5.14
by bugzilla_noreply＠suse.com 12 Nov '21

12 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192625 Bug ID: 1192625 Summary: Sound issues kernel 5.14 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: snettlet(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I've a new computer and tried everything to get the sound to work. Experienced people on the Suse Forum (deano & oldcpu) believe it is a kernel bug. Both the speakers and microphone show moving gauges indicating sound is being processed. Also the speakers work in Windows (installed on a different ssd, not dual boot). The alsa-info.sh is attached as text. Thankyou, Stuart -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1192549] Kernel 5.3.18-lp152.98-default breaks getdents(2) system call on NFS shares
by bugzilla_noreply＠suse.com 12 Nov '21

12 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192549 https://bugzilla.suse.com/show_bug.cgi?id=1192549#c21 --- Comment #21 from Ralf Fassel <ralf.fassel(a)akutech.de> --- Thanks for the quick action! Indeed, the patch is no longer offered today. Colleague of mine got bitten by this yesterday... -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192549] Kernel 5.3.18-lp152.98-default breaks getdents(2) system call on NFS shares
by bugzilla_noreply＠suse.com 12 Nov '21

12 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192549 https://bugzilla.suse.com/show_bug.cgi?id=1192549#c20 --- Comment #20 from Marcus Meissner <meissner(a)suse.com> --- the update is marked as retracted on 15.3 too, unless you installed in the first 3 hours, it should not be visible in your update stack. That said, we are expediting a fixup updte. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 12 Nov '21

12 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c42 --- Comment #42 from Martin Wilck <martin.wilck(a)suse.com> --- Created attachment 853708 --> https://bugzilla.suse.com/attachment.cgi?id=853708&action=edit script used for comment 39 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192549] New: Kernel 5.3.18-lp152.98-default breaks getdents(2) system call on NFS shares
by bugzilla_noreply＠suse.com 12 Nov '21

12 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192549 Bug ID: 1192549 Summary: Kernel 5.3.18-lp152.98-default breaks getdents(2) system call on NFS shares Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: werner(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- that is in the home directory of my own as well as of other users (beside /suse/present and /suse/bin) the simply command ls returns exactly nothing ... and strace show that the system call getdents(2) returns zero entries. Interesting I can e.g. change into ~/.fvwm/ or ~/.config/ or ~/.mozilla/ and list all therein ... only the topper up directory node remains empty -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 12 Nov '21

12 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c41 --- Comment #41 from Martin Wilck <martin.wilck(a)suse.com> --- My personal preference would still be "zstd -3". For images that need to be small, we have found a solution. Where else do 30MB actually matter? rpm size may be an issue, but we would need to experiment with that to find out. As we have seen, double compression can produce unexpected results. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 12 Nov '21

12 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c40 --- Comment #40 from Martin Wilck <martin.wilck(a)suse.com> --- Sorry I got the numbers wrong in the last paragraph. relative to the standard compression, the differences in disk usage are zstd level MB % 21 10 6% 15 15 10% 10 19 13% 6 23 16% 3 28 19% -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 12 Nov '21

12 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c39 --- Comment #39 from Martin Wilck <martin.wilck(a)suse.com> --- Quick test on 5.14.14, x86_64: The last column is the size of the modules tree after the command in the first column. The other columns indicate times and max RSS. 446MiB is the uncompressed size. All tests run consecutively, i.e. from the page cache. command real sys usr mem size "xz" 143 "xz -d" 0:07.58 0.56 7.01 4268 446 "xz -0" 0:20.15 0.49 19.65 4880 151 "xz -d" 0:08.05 0.55 7.49 2424 446 "zstd -21 --rm -q -T0" 2:21.79 0.95 140.75 114156 153 "zstd -d --rm -q" 0:01.71 0.60 0.89 11216 447 "zstd -15 --rm -q -T0" 0:49.35 0.77 48.53 96104 158 "zstd -d --rm -q" 0:01.33 0.65 0.67 7488 447 "zstd -10 --rm -q -T0" 0:11.17 0.54 10.59 40760 162 "zstd -d --rm -q" 0:01.24 0.54 0.66 7436 447 "zstd -6 --rm -q -T0" 0:05.79 0.53 5.30 32388 166 "zstd -d --rm -q" 0:01.28 0.49 0.77 5336 447 "zstd -3 --rm -q -T0" 0:03.06 0.51 2.56 25324 171 "zstd -d --rm -q" 0:01.88 0.79 1.04 5460 447 "zstd -0 --rm -q -T0" 0:03.24 0.58 2.69 25404 171 "zstd -d --rm -q" 0:01.24 0.52 0.71 5460 447 xz -6 (standard level) compression takes about 2:20 minutes. You can see that decompression time is actually constantly low with zstd. zstd -10 wins about 9MB, or 6% relative to the default size, compared to zstd -3, taking 4x as much time. Given that the compression time matters only during kernel building, and "zstd -10" is still 14x faster than "xz -6", it might be a good compromise. We could actually go for "zstd -21 -T0": The compression time is about the same as xz -6, and we'd loose just ~6% disk space. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 12 Nov '21

12 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c38 --- Comment #38 from Martin Wilck <martin.wilck(a)suse.com> --- (In reply to Takashi Iwai from comment #35) > (In reply to Martin Wilck from comment #32) > > Is there anything that prevents us from re-enabling zstd now? > > I think yes, at least for TW, we should try rolling things. I'd very much hope for SP4, too, as expressed in my kernel ML posting. If we consider this change risky, we should enable it in _early_ beta in order to be able revert if necessary, not vice versa. > And, let's try a bit higher compression level. The original bug description > here is about the increase of binaries, and the image creation workaround > doesn't influence the actual sizes. > > I suppose the level 10 could be a good compromise? I have systematic results only for initramfs, where the differences are smaller, probably because the default compression level in dracut (SUSE) was "xz -0" whereas we've been using just "xz" for the kernel, which defaults "xz -6". -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 12 Nov '21

12 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c37 --- Comment #37 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Michal Suchanek from comment #36) > (In reply to Takashi Iwai from comment #35) > > (In reply to Martin Wilck from comment #32) > > > Is there anything that prevents us from re-enabling zstd now? > > > > I think yes, at least for TW, we should try rolling things. > > > > And, let's try a bit higher compression level. The original bug description > > here is about the increase of binaries, and the image creation workaround > > doesn't influence the actual sizes. > > > > I suppose the level 10 could be a good compromise? > > The bug report is about the increased size making the images unbuildable > which the image build workaround addresses. The original report from Andreas is merely a complain about the size increase. The image build issue was reported in addition at first in comment 4. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 12 Nov '21

12 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c36 --- Comment #36 from Michal Suchanek <msuchanek(a)suse.com> --- (In reply to Takashi Iwai from comment #35) > (In reply to Martin Wilck from comment #32) > > Is there anything that prevents us from re-enabling zstd now? > > I think yes, at least for TW, we should try rolling things. > > And, let's try a bit higher compression level. The original bug description > here is about the increase of binaries, and the image creation workaround > doesn't influence the actual sizes. > > I suppose the level 10 could be a good compromise? The bug report is about the increased size making the images unbuildable which the image build workaround addresses. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 12 Nov '21

12 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c35 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(tiwai(a)suse.com) | --- Comment #35 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Martin Wilck from comment #32) > Is there anything that prevents us from re-enabling zstd now? I think yes, at least for TW, we should try rolling things. And, let's try a bit higher compression level. The original bug description here is about the increase of binaries, and the image creation workaround doesn't influence the actual sizes. I suppose the level 10 could be a good compromise? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192118] [Build 20211027] openQA test fails in finit_module02
by bugzilla_noreply＠suse.com 12 Nov '21

12 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192118 https://bugzilla.suse.com/show_bug.cgi?id=1192118#c1 --- Comment #1 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-ltp-syscalls@uefi_virtio-2G https://openqa.opensuse.org/tests/2029241 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 bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188729] kernel: socfpga_setup_ocram_self_refresh: Unable to find mmio-sram in dtb
by bugzilla_noreply＠suse.com 12 Nov '21

12 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1188729 https://bugzilla.suse.com/show_bug.cgi?id=1188729#c8 --- Comment #8 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 https://openqa.opensuse.org/tests/2027050 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 bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1183525] [Build 102.1] frozen linuxrc at "kexec parameters" on aarch64
by bugzilla_noreply＠suse.com 12 Nov '21

12 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1183525 https://bugzilla.suse.com/show_bug.cgi?id=1183525#c34 --- Comment #34 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: boot_linuxrc https://openqa.opensuse.org/tests/2030160 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 bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192473] DE0-Nano-SoC boot fails on 15.3
by bugzilla_noreply＠suse.com 11 Nov '21

11 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192473 https://bugzilla.suse.com/show_bug.cgi?id=1192473#c8 Christian Gross <christian.gross(a)centerofgravity.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(christian.gross@c | |enterofgravity.at) | --- Comment #8 from Christian Gross <christian.gross(a)centerofgravity.at> --- Loading Linux 5.15.1-1.ge42cffa-default ... Loading initial ramdisk ... EFI stub: Entering in SVC mode with MMU enabled EFI stub: Booting Linux Kernel... EFI stub: Using DTB from configuration table EFI stub: Exiting boot services... Deasserting all peripheral resets [ 0.007438][ T1] detected buffer overflow in memcpy [ 0.012639][ T1] ------------[ cut here ]------------ [ 0.017930][ T1] kernel BUG at lib/string.c:1165! [ 0.022873][ T1] Internal error: Oops - BUG: 0 [#1] SMP ARM [ 0.028684][ T1] Modules linked in: [ 0.032422][ T1] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.15.1-1.ge42cffa-default #1 openSUSE Tumbleweed (unreleased) 2dbadca80bbd0f39a4e26dab9e6eb470d2aadd34 [ 0.047053][ T1] Hardware name: Altera SOCFPGA [ 0.051736][ T1] PC is at fortify_panic+0x1c/0x20 [ 0.056694][ T1] LR is at 0x3fffdfff [ 0.060517][ T1] pc : [<c0eecf68>] lr : [<3fffdfff>] psr: 60000053 [ 0.067449][ T1] sp : c2141d98 ip : c19e3730 fp : c2141da4 [ 0.073344][ T1] r10: 00000000 r9 : c032095c r8 : c1b476a8 [ 0.079237][ T1] r7 : 00000000 r6 : c1b494ec r5 : 00000020 r4 : c1b494f0 [ 0.086428][ T1] r3 : 00000000 r2 : 00000000 r1 : 00000000 r0 : 00000022 [ 0.093619][ T1] Flags: nZCv IRQs on FIQs off Mode SVC_32 ISA ARM Segment user [ 0.101503][ T1] Control: 10c5387d Table: 0020404a DAC: 00000055 [ 0.107914][ T1] Register r0 information: non-paged memory [ 0.113639][ T1] Register r1 information: NULL pointer [ 0.119016][ T1] Register r2 information: NULL pointer [ 0.124393][ T1] Register r3 information: NULL pointer [ 0.129769][ T1] Register r4 information: non-slab/vmalloc memory [ 0.136098][ T1] Register r5 information: non-paged memory [ 0.141820][ T1] Register r6 information: non-slab/vmalloc memory [ 0.148148][ T1] Register r7 information: NULL pointer [ 0.153525][ T1] Register r8 information: non-slab/vmalloc memory [ 0.159853][ T1] Register r9 information: non-slab/vmalloc memory [ 0.166180][ T1] Register r10 information: NULL pointer [ 0.171644][ T1] Register r11 information: non-slab/vmalloc memory [ 0.178058][ T1] Register r12 information: non-slab/vmalloc memory [ 0.184472][ T1] Process swapper/0 (pid: 1, stack limit = 0x(ptrval)) [ 0.191146][ T1] Stack: (0xc2141d98 to 0xc2142000) [ 0.196179][ T1] 1d80: c2141dc4 c2141da8 [ 0.205015][ T1] 1da0: c034ff24 c0eecf58 c1b47698 00000001 c1619118 c21d1980 c2141dec c2141dc8 [ 0.213852][ T1] 1dc0: c0311398 c034fe28 00000001 c21d1980 c1867328 c035dfe8 2de6f000 2de6f000 [ 0.222687][ T1] 1de0: c2141e24 c2141df0 c035e01c c03112bc c2141e24 c2141e00 c03fc60c 00000001 [ 0.231524][ T1] 1e00: 0000005a c1867328 c035dfe8 2de6f000 2de6f000 00000000 c2141e7c c2141e28 [ 0.240360][ T1] 1e20: c035d5fc c035dff4 c19278f0 c19278f8 c1b21ad4 c190b094 c2140000 ef6d6328 [ 0.249196][ T1] 1e40: 00000001 c0480414 c19280e0 00000003 00007328 ef6d6328 0000005a c19279d8 [ 0.258031][ T1] 1e60: 00000001 00000001 2de6f000 00000000 c2141eac c2141e80 c035dc7c c035d494 [ 0.266867][ T1] 1e80: 00000000 00007328 00000001 c1867328 00000001 ef6d6328 00000000 000000e4 [ 0.275702][ T1] 1ea0: c2141eec c2141eb0 c035ee94 c035dc14 c2141ed4 c2141ec0 c0efa100 00000000 [ 0.284537][ T1] 1ec0: c19278bc 00000001 000000e4 c190b1e0 00000010 c190b0a0 00000000 00000000 [ 0.293372][ T1] 1ee0: c2141f04 c2141ef0 c035f0bc c035ed7c 00000001 c190b094 c2141f2c c2141f08 [ 0.302208][ T1] 1f00: c035f730 c035f060 c1a01494 c1865694 c1865694 00000000 00007000 00000000 [ 0.311043][ T1] 1f20: c2141f4c c2141f30 c1722f60 c035f6c4 c1725860 c0efb74c c2182b40 c2182b40 [ 0.319879][ T1] 1f40: c2141f94 c2141f50 c1701a30 c1722f30 c17ca908 c0efb574 c2141f94 c2141f68 [ 0.328714][ T1] 1f60: c0efb574 c03b76d0 c21cf700 00000000 c0ef73fc 00000000 00000000 00000000 [ 0.337549][ T1] 1f80: 00000000 00000000 c2141fac c2141f98 c0ef741c c17018d8 00000000 c0ef73fc [ 0.346384][ T1] 1fa0: 00000000 c2141fb0 c0300154 c0ef7408 00000000 00000000 00000000 00000000 [ 0.355219][ T1] 1fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 0.364054][ T1] 1fe0: 00000000 00000000 00000000 00000000 00000013 00000000 00000000 00000000 [ 0.372884][ T1] Backtrace: [ 0.376014][ T1] [<c0eecf4c>] (fortify_panic) from [<c034ff24>] (socfpga_a10_boot_secondary+0x0/0x10c) [ 0.385557][ T1] [<c034fe1c>] (socfpga_boot_secondary) from [<c0311398>] (__cpu_up+0xe8/0x1a0) [ 0.394409][ T1] r7:c21d1980 r6:c1619118 r5:00000001 r4:c1b47698 [ 0.400734][ T1] [<c03112b0>] (__cpu_up) from [<c035e01c>] (bringup_cpu+0x34/0x2d4) [ 0.408640][ T1] r9:2de6f000 r8:2de6f000 r7:c035dfe8 r6:c1867328 r5:c21d1980 r4:00000001 [ 0.417038][ T1] [<c035dfe8>] (bringup_cpu) from [<c035d5fc>] (cpuhp_invoke_callback+0x174/0x780) [ 0.426149][ T1] r10:00000000 r9:2de6f000 r8:2de6f000 r7:c035dfe8 r6:c1867328 r5:0000005a [ 0.434634][ T1] r4:00000001 [ 0.437847][ T1] [<c035d488>] (cpuhp_invoke_callback) from [<c035dc7c>] (cpuhp_invoke_callback_range+0x74/0xb8) [ 0.448168][ T1] r10:00000000 r9:2de6f000 r8:00000001 r7:00000001 r6:c19279d8 r5:0000005a [ 0.456654][ T1] r4:ef6d6328 [ 0.459866][ T1] [<c035dc08>] (cpuhp_invoke_callback_range) from [<c035ee94>] (_cpu_up+0x124/0x2e4) [ 0.469146][ T1] r8:000000e4 r7:00000000 r6:ef6d6328 r5:00000001 r4:c1867328 [ 0.476507][ T1] [<c035ed70>] (_cpu_up) from [<c035f0bc>] (cpu_up+0x68/0x9c) [ 0.483787][ T1] r10:00000000 r9:00000000 r8:c190b0a0 r7:00000010 r6:c190b1e0 r5:000000e4 [ 0.492272][ T1] r4:00000001 [ 0.495485][ T1] [<c035f054>] (cpu_up) from [<c035f730>] (bringup_nonboot_cpus+0x78/0x7c) [ 0.503896][ T1] r5:c190b094 r4:00000001 [ 0.508145][ T1] [<c035f6b8>] (bringup_nonboot_cpus) from [<c1722f60>] (smp_init+0x3c/0x84) [ 0.516741][ T1] r9:00000000 r8:00007000 r7:00000000 r6:c1865694 r5:c1865694 r4:c1a01494 [ 0.525139][ T1] [<c1722f24>] (smp_init) from [<c1701a30>] (kernel_init_freeable+0x164/0x2c0) [ 0.533899][ T1] r4:c2182b40 [ 0.537111][ T1] [<c17018cc>] (kernel_init_freeable) from [<c0ef741c>] (kernel_init+0x20/0x144) [ 0.546047][ T1] r10:00000000 r9:00000000 r8:00000000 r7:00000000 r6:00000000 r5:c0ef73fc [ 0.554532][ T1] r4:00000000 [ 0.557745][ T1] [<c0ef73fc>] (kernel_init) from [<c0300154>] (ret_from_fork+0x14/0x20) [ 0.565983][ T1] Exception stack(0xc2141fb0 to 0xc2141ff8) [ 0.571706][ T1] 1fa0: 00000000 00000000 00000000 00000000 [ 0.580542][ T1] 1fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 0.589375][ T1] 1fe0: 00000000 00000000 00000000 00000000 00000013 00000000 [ 0.596653][ T1] r5:c0ef73fc r4:00000000 [ 0.600907][ T1] Code: e1a01000 e30700b4 e34c0153 ebfff3a8 (e7f001f2) [ 0.607675][ T1] ---[ end trace cc0ac64ac4aab8e5 ]--- [ 0.613023][ T1] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b [ 0.621345][ T1] Rebooting in 90 seconds.. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192232] Dock stations work but the devices become disconnected periodically
by bugzilla_noreply＠suse.com 11 Nov '21

11 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192232 http://bugzilla.opensuse.org/show_bug.cgi?id=1192232#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dpbasti(a)wp.pl Flags| |needinfo?(dpbasti(a)wp.pl) --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- Could you verify whether a slightly older 5.14.x kernel (e.g. 5.14.11) found in TW history repo also shows the problem or not? http://download.opensuse.org/history/ There have been a few reports about type-C regressions on the recent 5.14.x, typically found on 5.14.15, and I wonder whether this is one of such. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191229] [Staging][rpm4.17] Kernel fails to build with rpm 4.17
by bugzilla_noreply＠suse.com 11 Nov '21

11 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1191229 https://bugzilla.suse.com/show_bug.cgi?id=1191229#c21 --- Comment #21 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2021:3655-1: An update that solves 13 vulnerabilities and has 43 fixes is now available. Category: security (important) Bug References: 1065729,1085030,1152472,1152489,1156395,1172073,1173604,1176447,1176774,1176914,1178134,1180100,1181147,1184673,1185762,1186063,1186109,1187167,1188563,1189841,1190006,1190067,1190349,1190351,1190479,1190620,1190642,1190795,1190801,1190941,1191229,1191240,1191241,1191315,1191317,1191349,1191384,1191449,1191450,1191451,1191452,1191455,1191456,1191628,1191645,1191663,1191731,1191800,1191867,1191934,1191958,1192040,1192041,1192074,1192107,1192145 CVE References: CVE-2021-33033,CVE-2021-34866,CVE-2021-3542,CVE-2021-3655,CVE-2021-3715,CVE-2021-3760,CVE-2021-3772,CVE-2021-3896,CVE-2021-41864,CVE-2021-42008,CVE-2021-42252,CVE-2021-42739,CVE-2021-43056 JIRA References: Sources used: SUSE MicroOS 5.1 (src): kernel-default-5.3.18-59.30.1, kernel-default-base-5.3.18-59.30.1.18.17.1 SUSE Linux Enterprise Workstation Extension 15-SP3 (src): kernel-default-5.3.18-59.30.1, kernel-preempt-5.3.18-59.30.1 SUSE Linux Enterprise Module for Live Patching 15-SP3 (src): kernel-default-5.3.18-59.30.1, kernel-livepatch-SLE15-SP3_Update_8-1-7.3.1 SUSE Linux Enterprise Module for Legacy Software 15-SP3 (src): kernel-default-5.3.18-59.30.1 SUSE Linux Enterprise Module for Development Tools 15-SP3 (src): kernel-docs-5.3.18-59.30.1, kernel-obs-build-5.3.18-59.30.1, kernel-preempt-5.3.18-59.30.1, kernel-source-5.3.18-59.30.1, kernel-syms-5.3.18-59.30.1 SUSE Linux Enterprise Module for Basesystem 15-SP3 (src): kernel-64kb-5.3.18-59.30.1, kernel-default-5.3.18-59.30.1, kernel-default-base-5.3.18-59.30.1.18.17.1, kernel-preempt-5.3.18-59.30.1, kernel-source-5.3.18-59.30.1, kernel-zfcpdump-5.3.18-59.30.1 SUSE Linux Enterprise High Availability 15-SP3 (src): kernel-default-5.3.18-59.30.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191229] [Staging][rpm4.17] Kernel fails to build with rpm 4.17
by bugzilla_noreply＠suse.com 11 Nov '21

11 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1191229 https://bugzilla.suse.com/show_bug.cgi?id=1191229#c20 --- Comment #20 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2021:3658-1: An update that solves 11 vulnerabilities and has 35 fixes is now available. Category: security (important) Bug References: 1065729,1085030,1152489,1154353,1156395,1157177,1167773,1172073,1173604,1176940,1184673,1185762,1186063,1187167,1188563,1189841,1190006,1190067,1190349,1190351,1190479,1190620,1190642,1190795,1190941,1191229,1191241,1191315,1191317,1191349,1191384,1191449,1191450,1191451,1191452,1191455,1191456,1191628,1191731,1191800,1191934,1191958,1192040,1192041,1192107,1192145 CVE References: CVE-2021-3542,CVE-2021-3655,CVE-2021-3715,CVE-2021-3760,CVE-2021-3772,CVE-2021-3896,CVE-2021-41864,CVE-2021-42008,CVE-2021-42252,CVE-2021-42739,CVE-2021-43056 JIRA References: Sources used: SUSE MicroOS 5.0 (src): kernel-rt-5.3.18-57.1 SUSE Linux Enterprise Module for Realtime 15-SP2 (src): kernel-rt-5.3.18-57.1, kernel-rt_debug-5.3.18-57.1, kernel-source-rt-5.3.18-57.1, kernel-syms-rt-5.3.18-57.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191229] [Staging][rpm4.17] Kernel fails to build with rpm 4.17
by bugzilla_noreply＠suse.com 11 Nov '21

11 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1191229 https://bugzilla.suse.com/show_bug.cgi?id=1191229#c19 --- Comment #19 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-SU-2021:3655-1: An update that solves 13 vulnerabilities and has 43 fixes is now available. Category: security (important) Bug References: 1065729,1085030,1152472,1152489,1156395,1172073,1173604,1176447,1176774,1176914,1178134,1180100,1181147,1184673,1185762,1186063,1186109,1187167,1188563,1189841,1190006,1190067,1190349,1190351,1190479,1190620,1190642,1190795,1190801,1190941,1191229,1191240,1191241,1191315,1191317,1191349,1191384,1191449,1191450,1191451,1191452,1191455,1191456,1191628,1191645,1191663,1191731,1191800,1191867,1191934,1191958,1192040,1192041,1192074,1192107,1192145 CVE References: CVE-2021-33033,CVE-2021-34866,CVE-2021-3542,CVE-2021-3655,CVE-2021-3715,CVE-2021-3760,CVE-2021-3772,CVE-2021-3896,CVE-2021-41864,CVE-2021-42008,CVE-2021-42252,CVE-2021-42739,CVE-2021-43056 JIRA References: Sources used: openSUSE Leap 15.3 (src): dtb-aarch64-5.3.18-59.30.1, kernel-64kb-5.3.18-59.30.1, kernel-debug-5.3.18-59.30.1, kernel-default-5.3.18-59.30.1, kernel-default-base-5.3.18-59.30.1.18.17.1, kernel-docs-5.3.18-59.30.1, kernel-kvmsmall-5.3.18-59.30.1, kernel-obs-build-5.3.18-59.30.1, kernel-obs-qa-5.3.18-59.30.1, kernel-preempt-5.3.18-59.30.1, kernel-source-5.3.18-59.30.1, kernel-syms-5.3.18-59.30.1, kernel-zfcpdump-5.3.18-59.30.1 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192473] DE0-Nano-SoC boot fails on 15.3
by bugzilla_noreply＠suse.com 11 Nov '21

11 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192473 https://bugzilla.suse.com/show_bug.cgi?id=1192473#c7 --- Comment #7 from Takashi Iwai <tiwai(a)suse.com> --- FWIW, OBS Kernel:HEAD already got a change to enable CONFIG_FORTIRY_SOURCE, too. It'll reach to stable branch and TW sooner or later. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192473] DE0-Nano-SoC boot fails on 15.3
by bugzilla_noreply＠suse.com 11 Nov '21

11 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192473 https://bugzilla.suse.com/show_bug.cgi?id=1192473#c6 --- Comment #6 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- (In reply to Takashi Iwai from comment #3) > (In reply to Christian Gross from comment #2) > > > However, here is the kernel BUG message: > > > > Loading Linux 5.3.18-59.25-default ... > > Loading initial ramdisk ... > > EFI stub: Entering in SVC mode with MMU enabled > > EFI stub: Booting Linux Kernel... > > EFI stub: Using DTB from configuration table > > EFI stub: Exiting boot services and installing virtual address map... > > [ 0.008983] detected buffer overflow in memcpy > > [ 0.013512] ------------[ cut here ]------------ > > [ 0.018109] kernel BUG at ../lib/string.c:1090! > (snip) > > [ 0.248691] Backtrace: > > [ 0.251138] [<c0da914c>] (fortify_panic) from [<c035fd20>] > > (socfpga_a10_boot_secondary+0x0/0x10c) > > So here is the problem. And I guess it's memcpy() call for the > trampoline, and possibly the compiler got confused. > > As a quirk workaround, you may add #define __NO_FORTIFY before the > inclusion of header files in arch/arm/mach-socfpga/platsmp.c. > Maybe there can be a better way to avoid it, though. I think fortified memcpy in this case works as expected. secondary_trampoline is declared as a char, while it is actually start address of the CPU entry code routine. Respectively memcpy see the source as pointer to char(1 byte) and copy size of ~40 bytes, so it panics. Christian, please, check Matthias test kernel build. There are a few FORTIFY related changes since 5.3.18 which could help. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192549] Kernel 5.3.18-lp152.98-default breaks getdents(2) system call on NFS shares
by bugzilla_noreply＠suse.com 11 Nov '21

11 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192549 Ali Abdallah <ali.abdallah(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1192586 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192549] Kernel 5.3.18-lp152.98-default breaks getdents(2) system call on NFS shares
by bugzilla_noreply＠suse.com 11 Nov '21

11 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192549 Ales Novak <alnovak(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1192585 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192549] Kernel 5.3.18-lp152.98-default breaks getdents(2) system call on NFS shares
by bugzilla_noreply＠suse.com 11 Nov '21

11 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192549 Michal Kube��ek <mkubecek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |denis.kirjanov(a)suse.com, | |ppyu(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192549] Kernel 5.3.18-lp152.98-default breaks getdents(2) system call on NFS shares
by bugzilla_noreply＠suse.com 11 Nov '21

11 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192549 https://bugzilla.suse.com/show_bug.cgi?id=1192549#c9 --- Comment #9 from Marcus Meissner <meissner(a)suse.com> --- https://progress.opensuse.org/issues/102257 filed for openqa -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192549] Kernel 5.3.18-lp152.98-default breaks getdents(2) system call on NFS shares
by bugzilla_noreply＠suse.com 11 Nov '21

11 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192549 https://bugzilla.suse.com/show_bug.cgi?id=1192549#c8 --- Comment #8 from Marcus Meissner <meissner(a)suse.com> --- hmm, remove the 15-sp3 kernel from the update repos, or just mark it as retracted -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 11 Nov '21

11 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c34 --- Comment #34 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Dominique Leuenberger from comment #27) > A possible difference was identified: my branch has debuginfo disabled - > likely causing quite some difference BTW, with debuginfo generation disabled in OBS, the resulting kernel binaries are incomplete, the modules (and probably also the main binary) lack the .BTF section. Sounds like the config doesn't explicitly enable the right options for that? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 11 Nov '21

11 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c33 Dominique Leuenberger <dleuenberger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(dimstar@opensuse. | |org) | --- Comment #33 from Dominique Leuenberger <dleuenberger(a)suse.com> --- (In reply to Martin Wilck from comment #30) > Does this mean zstd can be enabled again? Yes - the identified blocker was removed -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 11 Nov '21

11 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c32 Martin Wilck <martin.wilck(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(tiwai(a)suse.com), | |needinfo?(dimstar@opensuse. | |org), | |needinfo?(schwab@linux-m68k | |.org) --- Comment #32 from Martin Wilck <martin.wilck(a)suse.com> --- Is there anything that prevents us from re-enabling zstd now? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192549] Kernel 5.3.18-lp152.98-default breaks getdents(2) system call on NFS shares
by bugzilla_noreply＠suse.com 11 Nov '21

11 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192549 https://bugzilla.suse.com/show_bug.cgi?id=1192549#c7 --- Comment #7 from Michal Kube��ek <mkubecek(a)suse.com> --- (In reply to Marcus Meissner from comment #6) > this report is for Leap 15.2, the SLES 15 SP2 kernel. > > Is the 5.3 kernel base also affected? There is no difference in NFS related config options between SLE15-SP2 and openSUSE-15.2 (and the source code is the same) so SLE15-SP2 and SLE15-SP3 are almost certainly also affected. In particular, the offending patch is present in rpm-5.3.18-18.72--sle15-sp2-updates rpm-5.3.18-38.28--sle15-sp3-updates These are in fact SLE15-SP2-AZURE and SLE15-SP3-AZURE but SLE15-SP2 and SLE15-SP3 November update submissions (commits f07ed1b5dc6d and ebb75ee83c74, respectively) are also affected. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 11 Nov '21

11 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c31 --- Comment #31 from Martin Wilck <martin.wilck(a)suse.com> --- (In reply to Michal Suchanek from comment #25) > It's also possible to directly edit config.sh in the linked package. This isn't sufficient because mkspec needs to be run before check-in (otherwise the spec files will still use xz). It's possible to checkout from OBS locally, run mkspec in kernel-source.git, copy the spec files over to the obs dir, and commit to OBS. Running mkspec in a checked-out OBS repo doesn't work well. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 11 Nov '21

11 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c30 --- Comment #30 from Martin Wilck <martin.wilck(a)suse.com> --- Does this mean zstd can be enabled again? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192549] Kernel 5.3.18-lp152.98-default breaks getdents(2) system call on NFS shares
by bugzilla_noreply＠suse.com 11 Nov '21

11 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192549 https://bugzilla.suse.com/show_bug.cgi?id=1192549#c6 --- Comment #6 from Marcus Meissner <meissner(a)suse.com> --- this report is for Leap 15.2, the SLES 15 SP2 kernel. Is the 5.3 kernel base also affected? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 10 Nov '21

10 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c29 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt(a)suse.com --- Comment #29 from Fabian Vogt <fvogt(a)suse.com> --- The live CDs fit again after avoiding double-compression (both squashfs and the initrd), like suggested by comment 11: # Decompress kernel modules, better for squashfs (boo#1192457) find /usr/lib/modules/*/kernel -name '*.ko.xz' -exec xz -d {} + find /usr/lib/modules/*/kernel -name '*.ko.zst' -exec zstd --rm -d {} + depmod $(basename /usr/lib/modules/*) The size of the .iso shrank from 703MB to 619MiB! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 10 Nov '21

10 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c28 --- Comment #28 from Martin Wilck <martin.wilck(a)suse.com> --- FTR, I have set up projects on IBS/OBS, kernels with zstd module compression: OBS: home:mwilck:zstd:Factory (links to Kernel:stable) IBS: home:mwilck:zstd:SLE-15-SP4 (links to SUSE:SLE-15-SP4:GA) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192549] Kernel 5.3.18-lp152.98-default breaks getdents(2) system call on NFS shares
by bugzilla_noreply＠suse.com 10 Nov '21

10 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192549 https://bugzilla.suse.com/show_bug.cgi?id=1192549#c3 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P1 - Urgent --- Comment #3 from Marcus Meissner <meissner(a)suse.com> --- Neil? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 10 Nov '21

10 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c25 --- Comment #25 from Michal Suchanek <msuchanek(a)suse.com> --- (In reply to Martin Wilck from comment #22) > (In reply to Michal Suchanek from comment #20) > > (In reply to Dominique Leuenberger from comment #17) > > > > > Everyone understands that if unsurmountable problems occur, the project > > > > fails. But what happened here is that we pulled back on the first occurence > > > > of an issue. The side effect of this is that real-world testing effectively > > > > doesn't happen any more. So possible other issues will not be found, and the > > > > known ones will be harder to solve. > > > > > > It was not 'pulled back' - but moved to the 'devel area' instead of the > > > product. OBS is powerful enough to let us work out kinks outside of the > > > actual product build as long as we need to. And only put it inside the > > > product when we feel ready for it. > > > > Then you probably want to link Kernel:HEAD rather than Kernel:stable > > That's the point - factory kernels come from Kernel:stable, and by reverting > to xz in Kernel:stable, the feature was effectively "pulled back" as far as > the factory kernel is concerned. > > Maybe we should create a temporary branch that's equivalent to Kernel:stable > but uses zstd? > It's also possible to directly edit config.sh in the linked package. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 10 Nov '21

10 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c24 --- Comment #24 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Michal Suchanek from comment #20) > > > Everyone understands that if unsurmountable problems occur, the project > > > fails. But what happened here is that we pulled back on the first occurence > > > of an issue. The side effect of this is that real-world testing effectively > > > doesn't happen any more. So possible other issues will not be found, and the > > > known ones will be harder to solve. > > > > It was not 'pulled back' - but moved to the 'devel area' instead of the > > product. OBS is powerful enough to let us work out kinks outside of the > > actual product build as long as we need to. And only put it inside the > > product when we feel ready for it. > > Then you probably want to link Kernel:HEAD rather than Kernel:stable Having such a project would be really nice (that'll help the upstream development in RC phase, too), but it's certainly different from "ready to release". Instead, it'll be a position like linux-next, as the integration test of the latest kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 10 Nov '21

10 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c23 --- Comment #23 from Martin Wilck <martin.wilck(a)suse.com> --- (In reply to Takashi Iwai from comment #21) > If the decompression speed (which is the most important factor for switching > to zstd) is comparable with lower compression levels, then it can be a good > win. That was a consistent finding in my testing. It's also documented in the technical papers about zstd, it's a property of the algorithm by design. I haven't digged deep enough into the math to explain why. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 10 Nov '21

10 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c22 --- Comment #22 from Martin Wilck <martin.wilck(a)suse.com> --- (In reply to Michal Suchanek from comment #20) > (In reply to Dominique Leuenberger from comment #17) > > > Everyone understands that if unsurmountable problems occur, the project > > > fails. But what happened here is that we pulled back on the first occurence > > > of an issue. The side effect of this is that real-world testing effectively > > > doesn't happen any more. So possible other issues will not be found, and the > > > known ones will be harder to solve. > > > > It was not 'pulled back' - but moved to the 'devel area' instead of the > > product. OBS is powerful enough to let us work out kinks outside of the > > actual product build as long as we need to. And only put it inside the > > product when we feel ready for it. > > Then you probably want to link Kernel:HEAD rather than Kernel:stable That's the point - factory kernels come from Kernel:stable, and by reverting to xz in Kernel:stable, the feature was effectively "pulled back" as far as the factory kernel is concerned. Maybe we should create a temporary branch that's equivalent to Kernel:stable but uses zstd? > > > It was expected that some issues would occur. It was known beforehand that > > > package size would increase. > > > > So why did nobody look at the product deliverables and verify that they can > > be produced? Throw over the fence and let Release Managers pick up the > > broken glass is not the way to go. > > And how do we look at them and ensure that they are buildable? > > That's what we have release managers for. To know the deliverables. Ack. This was in Jira for some time. IMO this is part of the reason why we have Jira. There are product managers and release engineers involved who should have this on their radar. You can't expect *kernel* people to anticipate issues in every area. > > Be my guest: branch it, fix it, submit it. > > That's not so easy. Last time I tried to branch a release package it would > not build because it requires some complex project setup which is not > documented. Image building requires special knowledge that only a few people have. I certainly don't. Also, I'm pretty sure that you wouldn't be pleased if Michal or myself started throwing things out of the Live image to our own taste. We need to do this together somehow. (In reply to Dominique Leuenberger from comment #17) @Dominique, I agree that the burden shouldn't be on _you_. The question is how it can be shared. > There are 'rough edged' and 'unbuildable product deliverables'. Rough edges > can be ok, rebuildable deliverables are not ok. If the lives ar enot being > built, there is no Tumbleweed snapshot being produced which in turn means: > no user gets the change to test anyway. So what do you win? Nada. I wasn't aware that building live images was a prerequisite for releasing snapshots. My expectation was that few people are using these images. I thought they were mainly for newcomers checking out openSUSE. I don't think I ever used one. > > And this is what happens with "factory first" - effectively > > we beta-test on a distribution that others use in production. It's not the > > first time something breaks in factory, and not a unique incident by any > > means. > > Guess what: there were plenty of cases where a snapshot is not published > because of broken submissions. We have QA, we block snapshots if they are > too broken. Developers are still meant to do their tasks and deliver > functioning pieces. The pieces do function. It's malfunctioning at an entirely different level, image creation, which is outside the scope of kernel developers. I believe that releasing a snapshot without a live CD image would have close to zero impact on regular TW users, unlike e.g. the move to glibc 2.34. > We don't give up - we move back to the drawing board with the findings and > work out the issues. Good, thank you very much. As Michal suggested, you may want to link your test project to Kernel:HEAD. That means you'll also get another kernel, but that shouldn't matter much, hopefully. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 10 Nov '21

10 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c21 --- Comment #21 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Martin Wilck from comment #19) > My experiments showed that at levels >~15, compression with zstd may > actually be slower than xz (that was with initramfs payloads). > *decrompression* with zstd is always at 10-15x faster than with xz, > independent of the compression level. Also, multithreading can be enabled > with zstd, speeding it up (can't be done with xz easily, because compression > results may not be reproducible any more). If the decompression speed (which is the most important factor for switching to zstd) is comparable with lower compression levels, then it can be a good win. In the case of module compressions, it's done at the kernel package build time, not at the run time, so a slightly longer build time should be acceptable. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 10 Nov '21

10 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c20 --- Comment #20 from Michal Suchanek <msuchanek(a)suse.com> --- (In reply to Dominique Leuenberger from comment #17) > (In reply to Martin Wilck from comment #16) > > Let me ask again how we are supposed to proceed now. > > The tests we discussed continues in home:dimstar:Live - when we overcome the > obstacle, we can move to zstd again and build TW using this. Thanks for setting this up. The build with Factory packages showed the CD size as 630MB which is less than 650MB but maybe it's supposed to be in different units. > > > Everyone understands that if unsurmountable problems occur, the project > > fails. But what happened here is that we pulled back on the first occurence > > of an issue. The side effect of this is that real-world testing effectively > > doesn't happen any more. So possible other issues will not be found, and the > > known ones will be harder to solve. > > It was not 'pulled back' - but moved to the 'devel area' instead of the > product. OBS is powerful enough to let us work out kinks outside of the > actual product build as long as we need to. And only put it inside the > product when we feel ready for it. Then you probably want to link Kernel:HEAD rather than Kernel:stable > > > It was expected that some issues would occur. It was known beforehand that > > package size would increase. > > So why did nobody look at the product deliverables and verify that they can > be produced? Throw over the fence and let Release Managers pick up the > broken glass is not the way to go. And how do we look at them and ensure that they are buildable? That's what we have release managers for. To know the deliverables. I was not aware that there is a medium built that has exactly CD size. All the media I work with are either way over 4G or 100-300MB so I do not see the problem there. > > > Therefore if we want to have this feature, we > > need to deal with that and free the required space on the media. > > Be my guest: branch it, fix it, submit it. That's not so easy. Last time I tried to branch a release package it would not build because it requires some complex project setup which is not documented. When I did some project setup it would not build presumably because there is some size quota on the home projects. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189791] btrfs filesystem corruptions with HyperPAV
by bugzilla_noreply＠suse.com 10 Nov '21

10 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1189791 https://bugzilla.suse.com/show_bug.cgi?id=1189791#c16 --- Comment #16 from Berthold Gunreben <azouhr(a)opensuse.org> --- (In reply to LTC BugProxy from comment #15) > ------- Comment From stefan.haberland(a)de.ibm.com 2021-11-09 11:23 EDT------- > Can you please also share the output of lsdasd? Unfortunately, I only had z/VM 7.2 available during a PoC of openshift. The machine in question actually was the bastion server for that. I will update the other z/VM when I am back from vacation (in 2 weeks) and will try to reproduce, but at the moment I do not have more data. With regards to thick provisioned: I can only emulate that by doing a full format. This will have to wait until I upgraded z/VM as well. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192473] DE0-Nano-SoC boot fails on 15.3
by bugzilla_noreply＠suse.com 10 Nov '21

10 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192473 https://bugzilla.suse.com/show_bug.cgi?id=1192473#c5 Matthias Brugger <mbrugger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(christian.gross@c | |enterofgravity.at) --- Comment #5 from Matthias Brugger <mbrugger(a)suse.com> --- Can you double check that the system doesn't boot with Tumbleweed + FORTIFY_SOURCE. I just started a test kernel build. You can download the RPMs once finished here: https://build.opensuse.org/project/show/home:mbrugger:bsc1192473 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 10 Nov '21

10 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c19 --- Comment #19 from Martin Wilck <martin.wilck(a)suse.com> --- Sure, we could so that. As you can see xz compresses still better than zstd on high levels, but the difference to xz goes down from 18 to 7MB, or 28% to 12%, in your example. Not sure if that would be enough for Dominique. My experiments showed that at levels >~15, compression with zstd may actually be slower than xz (that was with initramfs payloads). *decrompression* with zstd is always at 10-15x faster than with xz, independent of the compression level. Also, multithreading can be enabled with zstd, speeding it up (can't be done with xz easily, because compression results may not be reproducible any more). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 10 Nov '21

10 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c18 --- Comment #18 from Takashi Iwai <tiwai(a)suse.com> --- BTW, I wonder now whether trying a higher compression level would be worth or not. Through a quick test, the size reduction varies much (also the compression time increases, though). % du -sh * 64188 xz 82128 zst03 79508 zst05 75160 zst10 71788 zst19 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 10 Nov '21

10 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c17 --- Comment #17 from Dominique Leuenberger <dleuenberger(a)suse.com> --- (In reply to Martin Wilck from comment #16) > Let me ask again how we are supposed to proceed now. The tests we discussed continues in home:dimstar:Live - when we overcome the obstacle, we can move to zstd again and build TW using this. > In my understanding, the existence of this "Sould have" Jira ticket implies > that engineering got an order from PM for the implementation this feature. > So we should try. Trying implies exposing the feature to a larger audience > for testing and finding possible rough edges. There are 'rough edged' and 'unbuildable product deliverables'. Rough edges can be ok, rebuildable deliverables are not ok. If the lives ar enot being built, there is no Tumbleweed snapshot being produced which in turn means: no user gets the change to test anyway. So what do you win? Nada. > Everyone understands that if unsurmountable problems occur, the project > fails. But what happened here is that we pulled back on the first occurence > of an issue. The side effect of this is that real-world testing effectively > doesn't happen any more. So possible other issues will not be found, and the > known ones will be harder to solve. It was not 'pulled back' - but moved to the 'devel area' instead of the product. OBS is powerful enough to let us work out kinks outside of the actual product build as long as we need to. And only put it inside the product when we feel ready for it. > It was expected that some issues would occur. It was known beforehand that > package size would increase. So why did nobody look at the product deliverables and verify that they can be produced? Throw over the fence and let Release Managers pick up the broken glass is not the way to go. > Therefore if we want to have this feature, we > need to deal with that and free the required space on the media. Be my guest: branch it, fix it, submit it. > That's > difficult, and it might mean that live image creation fails for a certain > period of time. This implies: no product deliverables are generated, which means no snapshot is generated, which means no user gets the new fancy feature. Tumbleweed is NOT a beta product. It is a fast-moving target, it accepts some rough edges here and there, but it is to be considered a stable product. > And this is what happens with "factory first" - effectively > we beta-test on a distribution that others use in production. It's not the > first time something breaks in factory, and not a unique incident by any > means. Guess what: there were plenty of cases where a snapshot is not published because of broken submissions. We have QA, we block snapshots if they are too broken. Developers are still meant to do their tasks and deliver functioning pieces. > By pulling back and switching to xz for both Factory and SP4 at this point > in time, we basically give up the chance to "test if fully on TW first" as > Takashi said above. That puts the implementation of this feature for SP4 at > high risk. We don't give up - we move back to the drawing board with the findings and work out the issues. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 10 Nov '21

10 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c16 --- Comment #16 from Martin Wilck <martin.wilck(a)suse.com> --- (Copied this from https://jira.suse.com/browse/PM-2971 for information - I think further discussion should happen there, or possibly on the kernel ML, rather than on BZ). Let me ask again how we are supposed to proceed now. In my understanding, the existence of this "Sould have" Jira ticket implies that engineering got an order from PM for the implementation this feature. So we should try. Trying implies exposing the feature to a larger audience for testing and finding possible rough edges. Everyone understands that if unsurmountable problems occur, the project fails. But what happened here is that we pulled back on the first occurence of an issue. The side effect of this is that real-world testing effectively doesn't happen any more. So possible other issues will not be found, and the known ones will be harder to solve. It was expected that some issues would occur. It was known beforehand that package size would increase. Therefore if we want to have this feature, we need to deal with that and free the required space on the media. That's difficult, and it might mean that live image creation fails for a certain period of time. And this is what happens with "factory first" - effectively we beta-test on a distribution that others use in production. It's not the first time something breaks in factory, and not a unique incident by any means. By pulling back and switching to xz for both Factory and SP4 at this point in time, we basically give up the chance to "test if fully on TW first" as Takashi said above. That puts the implementation of this feature for SP4 at high risk. I don't want to push this feature forcibly. If there are strong reasons not to implement it, I won't insist. But I believe this pull-back was premature. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 10 Nov '21

10 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c15 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com --- Comment #15 from Jiri Slaby <jslaby(a)suse.com> --- JFYI Michal reverted stable back to xz for the time being. And I submitted 5.15.1 to factory incl. this change. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191229] [Staging][rpm4.17] Kernel fails to build with rpm 4.17
by bugzilla_noreply＠suse.com 09 Nov '21

09 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1191229 https://bugzilla.suse.com/show_bug.cgi?id=1191229#c16 --- Comment #16 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2021:3640-1: An update that solves 11 vulnerabilities and has 35 fixes is now available. Category: security (important) Bug References: 1065729,1085030,1133021,1152489,1154353,1156395,1157177,1167773,1172073,1173604,1176940,1184673,1185762,1186063,1187167,1188563,1189841,1190006,1190067,1190349,1190351,1190479,1190620,1190642,1190795,1190941,1191229,1191241,1191315,1191317,1191384,1191449,1191450,1191451,1191452,1191455,1191456,1191628,1191731,1191800,1191934,1191958,1192040,1192041,1192107,1192145 CVE References: CVE-2021-3542,CVE-2021-3655,CVE-2021-3715,CVE-2021-3760,CVE-2021-3772,CVE-2021-3896,CVE-2021-41864,CVE-2021-42008,CVE-2021-42252,CVE-2021-42739,CVE-2021-43056 JIRA References: Sources used: SUSE Linux Enterprise Module for Public Cloud 15-SP2 (src): kernel-azure-5.3.18-18.72.2, kernel-source-azure-5.3.18-18.72.2, kernel-syms-azure-5.3.18-18.72.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191229] [Staging][rpm4.17] Kernel fails to build with rpm 4.17
by bugzilla_noreply＠suse.com 09 Nov '21

09 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1191229 https://bugzilla.suse.com/show_bug.cgi?id=1191229#c15 --- Comment #15 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-SU-2021:3641-1: An update that solves 13 vulnerabilities and has 43 fixes is now available. Category: security (important) Bug References: 1065729,1085030,1152472,1152489,1156395,1172073,1173604,1176447,1176774,1176914,1178134,1180100,1181147,1184673,1185762,1186063,1186109,1187167,1188563,1189841,1190006,1190067,1190349,1190351,1190479,1190620,1190642,1190795,1190801,1190941,1191229,1191240,1191241,1191315,1191317,1191349,1191384,1191449,1191450,1191451,1191452,1191455,1191456,1191628,1191645,1191663,1191731,1191800,1191867,1191934,1191958,1192040,1192041,1192074,1192107,1192145 CVE References: CVE-2021-33033,CVE-2021-34866,CVE-2021-3542,CVE-2021-3655,CVE-2021-3715,CVE-2021-3760,CVE-2021-3772,CVE-2021-3896,CVE-2021-41864,CVE-2021-42008,CVE-2021-42252,CVE-2021-42739,CVE-2021-43056 JIRA References: Sources used: openSUSE Leap 15.3 (src): kernel-azure-5.3.18-38.28.2, kernel-source-azure-5.3.18-38.28.2, kernel-syms-azure-5.3.18-38.28.1 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191229] [Staging][rpm4.17] Kernel fails to build with rpm 4.17
by bugzilla_noreply＠suse.com 09 Nov '21

09 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1191229 https://bugzilla.suse.com/show_bug.cgi?id=1191229#c14 --- Comment #14 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2021:3641-1: An update that solves 13 vulnerabilities and has 43 fixes is now available. Category: security (important) Bug References: 1065729,1085030,1152472,1152489,1156395,1172073,1173604,1176447,1176774,1176914,1178134,1180100,1181147,1184673,1185762,1186063,1186109,1187167,1188563,1189841,1190006,1190067,1190349,1190351,1190479,1190620,1190642,1190795,1190801,1190941,1191229,1191240,1191241,1191315,1191317,1191349,1191384,1191449,1191450,1191451,1191452,1191455,1191456,1191628,1191645,1191663,1191731,1191800,1191867,1191934,1191958,1192040,1192041,1192074,1192107,1192145 CVE References: CVE-2021-33033,CVE-2021-34866,CVE-2021-3542,CVE-2021-3655,CVE-2021-3715,CVE-2021-3760,CVE-2021-3772,CVE-2021-3896,CVE-2021-41864,CVE-2021-42008,CVE-2021-42252,CVE-2021-42739,CVE-2021-43056 JIRA References: Sources used: SUSE Linux Enterprise Module for Public Cloud 15-SP3 (src): kernel-azure-5.3.18-38.28.2, kernel-source-azure-5.3.18-38.28.2, kernel-syms-azure-5.3.18-38.28.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191229] [Staging][rpm4.17] Kernel fails to build with rpm 4.17
by bugzilla_noreply＠suse.com 09 Nov '21

09 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1191229 https://bugzilla.suse.com/show_bug.cgi?id=1191229#c13 --- Comment #13 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2021:3642-1: An update that solves 13 vulnerabilities and has 43 fixes is now available. Category: security (important) Bug References: 1065729,1085030,1152472,1152489,1156395,1172073,1173604,1176447,1176774,1176914,1178134,1180100,1181147,1184673,1185762,1186063,1186109,1187167,1188563,1189841,1190006,1190067,1190349,1190351,1190479,1190620,1190642,1190795,1190801,1190941,1191229,1191240,1191241,1191315,1191317,1191349,1191384,1191449,1191450,1191451,1191452,1191455,1191456,1191628,1191645,1191663,1191731,1191800,1191867,1191934,1191958,1192040,1192041,1192074,1192107,1192145 CVE References: CVE-2021-33033,CVE-2021-34866,CVE-2021-3542,CVE-2021-3655,CVE-2021-3715,CVE-2021-3760,CVE-2021-3772,CVE-2021-3896,CVE-2021-41864,CVE-2021-42008,CVE-2021-42252,CVE-2021-42739,CVE-2021-43056 JIRA References: Sources used: SUSE MicroOS 5.1 (src): kernel-rt-5.3.18-60.1 SUSE Linux Enterprise Module for Realtime 15-SP3 (src): kernel-rt-5.3.18-60.1, kernel-rt_debug-5.3.18-60.1, kernel-source-rt-5.3.18-60.1, kernel-syms-rt-5.3.18-60.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189791] btrfs filesystem corruptions with HyperPAV
by bugzilla_noreply＠suse.com 09 Nov '21

09 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1189791 https://bugzilla.suse.com/show_bug.cgi?id=1189791#c15 --- Comment #15 from LTC BugProxy <bugproxy(a)us.ibm.com> --- ------- Comment From stefan.haberland(a)de.ibm.com 2021-11-09 11:23 EDT------- Can you please also share the output of lsdasd? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 09 Nov '21

09 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c14 --- Comment #14 from Dominique Leuenberger <dleuenberger(a)suse.com> --- (In reply to Martin Wilck from comment #13) > It might be worthwhile to just try it and see if it actually saves space, > and how much. If it turns out to be helpful, we can worry about protecting > the kittens from rpm's wrath. experiments started in https://build.opensuse.org/project/show/home:dimstar:Live -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 09 Nov '21

09 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c13 --- Comment #13 from Martin Wilck <martin.wilck(a)suse.com> --- It might be worthwhile to just try it and see if it actually saves space, and how much. If it turns out to be helpful, we can worry about protecting the kittens from rpm's wrath. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 09 Nov '21

09 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c12 --- Comment #12 from Dominique Leuenberger <dleuenberger(a)suse.com> --- (In reply to Martin Wilck from comment #11) > The idea would be something like > > find /usr/lib/modules -name '*.ko.xz' -print0 | xargs -0 xz -d > > after installing the kernel, and before creating the image. OUCH :) rpm -qV kernel-default will hate us for this and eat our kittens (but as a workaround probably doable for the live images; openQA debug helpers will get a bit noisy) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189791] btrfs filesystem corruptions with HyperPAV
by bugzilla_noreply＠suse.com 09 Nov '21

09 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1189791 https://bugzilla.suse.com/show_bug.cgi?id=1189791#c14 --- Comment #14 from LTC BugProxy <bugproxy(a)us.ibm.com> --- ------- Comment From stefan.haberland(a)de.ibm.com 2021-11-09 10:49 EDT------- Thanks a lot for the answer. OK, I expected it to be /dev/dasdX1 but just wanted to make sure that not accidentally the base blockdevice has been used, which is always a problem with DASD devices. But I noticed another thing in your report. You mentioned that the devices are thinly provisioned. Did you ever try something similar with fully allocated devices? Or is it possible to test your workflow with fully allocated devices? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 09 Nov '21

09 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c11 --- Comment #11 from Martin Wilck <martin.wilck(a)suse.com> --- (In reply to Dominique Leuenberger from comment #10) > Sounds good - but: kernel-default is the kernel with the compressed modules. > We do not have a kernel build flavor with uncompressed modules The idea would be something like find /usr/lib/modules -name '*.ko.xz' -print0 | xargs -0 xz -d after installing the kernel, and before creating the image. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 09 Nov '21

09 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c10 Dominique Leuenberger <dleuenberger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dleuenberger(a)suse.com --- Comment #10 from Dominique Leuenberger <dleuenberger(a)suse.com> --- (In reply to Martin Wilck from comment #9) > Suggested by Takashi in chat: for the Live CD image, it might be worthwhile > to try including the *uncompressed* modules, because they can be compressed > much better during image creation. That would have the additional benefit > that the result would be independent of whether or not the modules were > shiped xz or zstd-compressed. Sounds good - but: kernel-default is the kernel with the compressed modules. We do not have a kernel build flavor with uncompressed modules (we only do have that for firmware, where we already DO pick the uncompressed ones on lives) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 09 Nov '21

09 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c9 --- Comment #9 from Martin Wilck <martin.wilck(a)suse.com> --- Suggested by Takashi in chat: for the Live CD image, it might be worthwhile to try including the *uncompressed* modules, because they can be compressed much better during image creation. That would have the additional benefit that the result would be independent of whether or not the modules were shiped xz or zstd-compressed. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192476] CONFIG_FORTIFY_SOURCE isn't enabled on TW kernels
by bugzilla_noreply＠suse.com 09 Nov '21

09 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192476 https://bugzilla.suse.com/show_bug.cgi?id=1192476#c2 --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- Submitted to my master/for-next branch. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 09 Nov '21

09 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c8 --- Comment #8 from Martin Wilck <martin.wilck(a)suse.com> --- (In reply to Michal Suchanek from comment #7) > Isn't rescue CD recompressed anyway? > > Does recomressing the zstd compressed data with xz (squashfs, initrd) > recover the space? Probably not. Compressing already-compressed payloads is inefficient. See https://mwilck.github.io/labsconf2021/#/1/5 for example. The _rpm_ size is smallest if the the payload (the modules) are uncompressed. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 09 Nov '21

09 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c7 --- Comment #7 from Michal Suchanek <msuchanek(a)suse.com> --- Isn't rescue CD recompressed anyway? Does recomressing the zstd compressed data with xz (squashfs, initrd) recover the space? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192375] Bose Revolve+ SoundLink USB speaker bad dB
by bugzilla_noreply＠suse.com 09 Nov '21

09 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192375 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |tiwai(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 09 Nov '21

09 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c6 --- Comment #6 from Martin Wilck <martin.wilck(a)suse.com> --- I made a note in SUSE Jira (PM-2971) about this to inform PM. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 09 Nov '21

09 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c5 --- Comment #5 from Martin Wilck <martin.wilck(a)suse.com> --- Understood. There's obviously a trade-off which needs to be considered. I believe there are strong arguments in favor of zstd, mainly speed. But if it's prohibitive in other areas, we must reconsider the decision. One obvious possiblility would be to split off kernel-default-extra like we do in Leap, reducing the install size of the kernel base package. But that's yet another trade-off, and doing it would cost substantial effort. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189791] btrfs filesystem corruptions with HyperPAV
by bugzilla_noreply＠suse.com 08 Nov '21

08 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1189791 https://bugzilla.suse.com/show_bug.cgi?id=1189791#c13 --- Comment #13 from Berthold Gunreben <azouhr(a)opensuse.org> --- (In reply to LTC BugProxy from comment #12) > ------- Comment From stefan.haberland(a)de.ibm.com 2021-11-08 10:27 EDT------- > Hi, currently there are only btrfs error messages shared. > Are there any DASD related error messages? I did not see any. > What I see in the workflow: > > > 2.3 Use yast to activate and format disk then create raw partition > > Could you please explain a little more in detail what this exactly looks > like and what exactly is meant by "raw partition"? > > Is the disk that is added to btrfs a partition created by fsdasd or the base > blockdevice (e.g. /dev/dasdx1 vs /dev/dasdx). It is /dev/dasdx1 (as you can see from the btrfs device stats as well) The lowlevel dasdfmt has been done with yast, since I was unsure about how to accomplish this correctly with keeping the disk devices thin provisioned. After this, the single partition was created in the partitioner dialog. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188428] New: udev: failed to get device info: could not read 'authorized': No such file or directory
by bugzilla_noreply＠suse.com 08 Nov '21

08 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1188428 Bug ID: 1188428 Summary: udev: failed to get device info: could not read 'authorized': No such file or directory 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: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Starting with kernel 5.13.0-1 (Jul 09) on boot I always get an error message (see subject) from boltd regarding device cd010000-0060-XPS 9370. All messages from boltd: boltd[1189]: bolt 0.9.1 starting up. boltd[1189]: manager: initializing store boltd[1189]: store: located at: /var/lib/boltd boltd[1189]: config: loading user config boltd[1189]: bouncer: initializing polkit boltd[1189]: watchdog: enabled [pulse: 90s] boltd[1189]: udev: initializing udev boltd[1189]: store: loading domains boltd[1189]: [cd010000-0060-domain? ] store: loading domain boltd[1189]: journal: opened for 'cd010000-0060'; size: 0 bytes boltd[1189]: [cd010000-0060-domain? ] domain: registered (bootacl: 16/16) boltd[1189]: store: loading devices boltd[1189]: [00cd30c8-3205 ] store: loading device boltd[1189]: [cd010000-0060 ] store: loading device boltd[1189]: global 'generation' set to '3' boltd[1189]: [da010000-0070 ] store: loading device boltd[1189]: power: state located at: /run/boltd/power boltd[1189]: power: force power support: yes boltd[1189]: udev: found 1 domain boltd[1189]: udev: enumerating devices boltd[1189]: probing: adding /sys/devices/pci0000:00/0000:00:1c.4/0000:03:00.0 to roots boltd[1189]: [cd010000-0060-domain0 ] bootacl: synchronizing journal boltd[1189]: security level set to 'user' boltd[1189]: [cd010000-0060-domain0 ] connected: as domain0 [user] (/sys/devices/pci0000:00/0000:00:1c.4/0000:03:00.0/0000:04:00.0/0000:05:00.0/domain0) boltd[1189]: [cd010000-0060-XPS 9370 ] udev: failed to get device info: could not read 'authorized': No such file or directory boltd[1189]: [cd010000-0060-XPS 9370 ] parent is (null)... boltd[1189]: [cd010000-0060-XPS 9370 ] store: updating device boltd[1189]: [cd010000-0060-XPS 9370 ] connected: unknown (/sys/devices/pci0000:00/0000:00:1c.4/0000:03:00.0/0000:04:00.0/0000:05:00.0/domain0/0-0) boltd[1189]: [00cd30c8-3205-TS3 Plus ] parent is cd010000-0060... boltd[1189]: [00cd30c8-3205-TS3 Plus ] connected: authorized (/sys/devices/pci0000:00/0000:00:1c.4/0000:03:00.0/0000:04:00.0/0000:05:00.0/domain0/0-0/0-3) boltd[1189]: [cd010000-0060-domain0 ] dbus: exported domain at /org/freedesktop/bolt/domains/cd010000_0060_6d18_a364_e809ccc32820 boltd[1189]: [00cd30c8-3205-TS3 Plus ] dbus: exported device at /org/freedesktop/bolt/devices/00cd30c8_3205... boltd[1189]: [cd010000-0060-XPS 9370 ] dbus: exported device at /org/freedesktop/bolt/devices/cd010000_0060... boltd[1189]: [da010000-0070-XPS 13 9370 ] dbus: exported device at /org/freedesktop/bolt/devices/da010000_0070... boltd[1189]: probing: started [1000] boltd[1189]: [00cd30c8-3205-TS3 Plus ] udev: device changed: authorized -> authorized boltd[1189]: probing: timeout, done: [2974874] (2000000) System info: Operating System: openSUSE Tumbleweed 20210715 KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 Kernel Version: 5.13.1-1-default (64-bit) Graphics Platform: X11 Processors: 8 �� Intel�� Core�� i7-8550U CPU @ 1.80GHz Memory: 15,0 GiB of RAM Graphics Processor: Mesa DRI Intel�� UHD Graphics 620 This is a DELL XPS 9370 notebook. -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 1189791] btrfs filesystem corruptions with HyperPAV
by bugzilla_noreply＠suse.com 08 Nov '21

08 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1189791 https://bugzilla.suse.com/show_bug.cgi?id=1189791#c12 --- Comment #12 from LTC BugProxy <bugproxy(a)us.ibm.com> --- ------- Comment From stefan.haberland(a)de.ibm.com 2021-11-08 10:27 EDT------- Hi, currently there are only btrfs error messages shared. Are there any DASD related error messages? What I see in the workflow: > 2.3 Use yast to activate and format disk then create raw partition Could you please explain a little more in detail what this exactly looks like and what exactly is meant by "raw partition"? Is the disk that is added to btrfs a partition created by fsdasd or the base blockdevice (e.g. /dev/dasdx1 vs /dev/dasdx). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189791] btrfs filesystem corruptions with HyperPAV
by bugzilla_noreply＠suse.com 08 Nov '21

08 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1189791 https://bugzilla.suse.com/show_bug.cgi?id=1189791#c11 --- Comment #11 from Thomas Staudt <tstaudt(a)de.ibm.com> --- . -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192473] DE0-Nano-SoC boot fails on 15.3
by bugzilla_noreply＠suse.com 08 Nov '21

08 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192473 https://bugzilla.suse.com/show_bug.cgi?id=1192473#c4 --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- Also adding Guillaume to Cc. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192476] CONFIG_FORTIFY_SOURCE isn't enabled on TW kernels
by bugzilla_noreply＠suse.com 08 Nov '21

08 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192476 https://bugzilla.suse.com/show_bug.cgi?id=1192476#c1 --- Comment #1 from Marcus Meissner <meissner(a)suse.com> --- please enable. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192473] New: DE0-Nano-SoC boot fails on 15.3
by bugzilla_noreply＠suse.com 08 Nov '21

08 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192473 Bug ID: 1192473 Summary: DE0-Nano-SoC boot fails on 15.3 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: armv7 OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: christian.gross(a)centerofgravity.at QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- DE0-Nano-SoC with Leap 15.3 freezes at boot. Booting `openSUSE Leap 15.3' Loading Linux 5.3.18-59.25-default ... Loading initial ramdisk ... EFI stub: Entering in SVC mode with MMU enabled EFI stub: Booting Linux Kernel... EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map... Deasserting all peripheral resets [freeze] The freeze is caused by the CONFIG_FORTIFY_SOURCE kernel configuration item. The following patch fix the problem. --- /boot/config-5.3.18-59.25-default 2021-09-23 14:34:53.000000000 +0000 +++ .config 2021-07-15 12:07:05.608153308 +0000 @@ -10294,7 +10294,7 @@ CONFIG_LSM_MMAP_MIN_ADDR=0 CONFIG_HAVE_HARDENED_USERCOPY_ALLOCATOR=y # CONFIG_HARDENED_USERCOPY is not set -CONFIG_FORTIFY_SOURCE=y +# CONFIG_FORTIFY_SOURCE is not set # CONFIG_STATIC_USERMODEHELPER is not set # CONFIG_HIDDEN_AREA is not set CONFIG_SECURITY_SELINUX=y -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 08 Nov '21

08 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c3 --- Comment #3 from Martin Wilck <martin.wilck(a)suse.com> --- Is this prohibitive e.g. on ARM? Note OTOH that (according to my measurements) ARM systems suffer more from the slowness of xz than others. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 08 Nov '21

08 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c2 --- Comment #2 from Martin Wilck <martin.wilck(a)suse.com> --- This is in the expectected range. The numbers I measured for SLE15-SP3 were 170M uncompressed, 35M xz, 47M zstd (numbers from my labsconf talk). This matches. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191229] [Staging][rpm4.17] Kernel fails to build with rpm 4.17
by bugzilla_noreply＠suse.com 08 Nov '21

08 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1191229 https://bugzilla.suse.com/show_bug.cgi?id=1191229#c12 --- Comment #12 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-SU-2021:1460-1: An update that solves 15 vulnerabilities and has 40 fixes is now available. Category: security (important) Bug References: 1065729,1085030,1100416,1129735,1152489,1154353,1156395,1157177,1167773,1172073,1173604,1176940,1184673,1185762,1186109,1187167,1188563,1188876,1188983,1188985,1189841,1190006,1190067,1190349,1190351,1190479,1190620,1190642,1190795,1190941,1191229,1191238,1191241,1191315,1191317,1191343,1191349,1191384,1191449,1191450,1191451,1191452,1191455,1191456,1191628,1191731,1191800,1191934,1191958,1192036,1192040,1192041,1192107,1192145,1192267 CVE References: CVE-2018-13405,CVE-2021-33033,CVE-2021-34556,CVE-2021-3542,CVE-2021-35477,CVE-2021-3655,CVE-2021-3715,CVE-2021-3760,CVE-2021-3772,CVE-2021-3896,CVE-2021-41864,CVE-2021-42008,CVE-2021-42252,CVE-2021-42739,CVE-2021-43056 JIRA References: Sources used: openSUSE Leap 15.2 (src): kernel-debug-5.3.18-lp152.98.1, kernel-default-5.3.18-lp152.98.1, kernel-default-base-5.3.18-lp152.98.1.lp152.8.46.1, kernel-docs-5.3.18-lp152.98.1, kernel-kvmsmall-5.3.18-lp152.98.1, kernel-obs-build-5.3.18-lp152.98.1, kernel-obs-qa-5.3.18-lp152.98.1, kernel-preempt-5.3.18-lp152.98.1, kernel-source-5.3.18-lp152.98.1, kernel-syms-5.3.18-lp152.98.1 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192190] iwlwifi driver fails to load after restart
by bugzilla_noreply＠suse.com 08 Nov '21

08 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192190 https://bugzilla.suse.com/show_bug.cgi?id=1192190#c3 --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- So this isn't about a regression on the recent TW updates? If you had a properly working system, we may narrow down the cause. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188970] Xorg crashes with a segmentation fault when a secondary USB display using DisplayLink is connected
by bugzilla_noreply＠suse.com 07 Nov '21

07 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1188970 Ricardo Lopez Caballero <ricardo-lopez-caballero(a)toshibagcs.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #853573|Supportconfig Tumbleweed |Supportconfig Tumbleweed description|05112021 X11 |05112021 with X11 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188970] Xorg crashes with a segmentation fault when a secondary USB display using DisplayLink is connected
by bugzilla_noreply＠suse.com 07 Nov '21

07 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1188970 http://bugzilla.opensuse.org/show_bug.cgi?id=1188970#c61 --- Comment #61 from Ricardo Lopez Caballero <ricardo-lopez-caballero(a)toshibagcs.com> --- Comment on attachment 853573 --> http://bugzilla.opensuse.org/attachment.cgi?id=853573 Supportconfig Tumbleweed 05112021 X11 I installed the latest Tumbleweed "openSUSE-Tumbleweed-DVD-x86_64-Snapshot20211105-Media.iso" on same hardware as before and no issue. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188970] Xorg crashes with a segmentation fault when a secondary USB display using DisplayLink is connected
by bugzilla_noreply＠suse.com 07 Nov '21

07 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1188970 http://bugzilla.opensuse.org/show_bug.cgi?id=1188970#c60 --- Comment #60 from Ricardo Lopez Caballero <ricardo-lopez-caballero(a)toshibagcs.com> --- Created attachment 853573 --> http://bugzilla.opensuse.org/attachment.cgi?id=853573&action=edit Supportconfig Tumbleweed 05112021 X11 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192181] brightness keys mute mic instead (HP Elitebook 840 G6)
by bugzilla_noreply＠suse.com 07 Nov '21

07 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192181 https://bugzilla.suse.com/show_bug.cgi?id=1192181#c7 --- Comment #7 from Takashi Iwai <tiwai(a)suse.com> --- OK, thanks. To make sure, could you do cold boot with hp_wmi module blackisted? Create a file e.g. /etc/modprobe.d/90-hp-wmi.conf containing blacklist hp_wmi and reboot. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188970] Xorg crashes with a segmentation fault when a secondary USB display using DisplayLink is connected
by bugzilla_noreply＠suse.com 05 Nov '21

05 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1188970 http://bugzilla.opensuse.org/show_bug.cgi?id=1188970#c59 --- Comment #59 from Ricardo Lopez Caballero <ricardo-lopez-caballero(a)toshibagcs.com> --- (In reply to Thomas Zimmermann from comment #57) > I cannot reproduce the issue. > > STR: > > * Installed the latest SLE15-SP3 LEAP installer without updates. > * Started Gnome in X11 mode. > * Tried with 3 different DisplayLink USB adapters, with VGA and DVI > connectors. > > The main graphics card is an AMD driven by the radeon driver. > > There are no X crashes and no kernel warnings. The xorg-x11-server package > is at 1.20.3.5.33.1. > > If there's better way to reproduce the bug, please let me know. Hi Thomas, if you take a look to the supportconfig files, i have reproduced the issue with Intel processors incl. onboard video, units with Intel Haswell, Intel Kaby Lake, Intel Whiskey Lake, Intel Tiger Lake. What means USB Adapters with VGA and DVI ? The display we connect is an USB Display conncected to PC USB2/USB3 port at system unit. a) When you install SLES15 SP3 from usb stick and the 2nd usb video display is connected, the installer during installation will end with error due to Xorg crash. The Install fails. b) You can install SLES15 SP3 with 2nd usb video display connected. After successfull installation you boot and check that GDM and login with GNOME and X11 is successfull. You switch to terminal, init 3, connect the 2nd usb video display and startx. The GUI session with GDM login will not appear, just a blinking cursor left upper corner of primary display. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192375] New: Bose Revolve+ SoundLink USB speaker bad dB
by bugzilla_noreply＠suse.com 05 Nov '21

05 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192375 Bug ID: 1192375 Summary: Bose Revolve+ SoundLink USB speaker bad dB Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: x86-64 OS: openSUSE Leap 42.3 Status: NEW Severity: Minor Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: cliff.dugal(a)pico.ca QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When I connect my Bose Revolve+ SoundLink to my computer via USB, it can play music, but the volume mapping is way off. AlsaMixer shows a dB gain of 0.00 to 0.38 in 39 steps. 0.00 dB is no volume, and 0.38 dB is ridiculously loud. The PulseAudio mixer is essentially useless in this situation. 98% volume maps to the speaker being off, 99% volume maps to 0.11 dB in AlsaMixer (actually listenable), and 100% volume maps to insanely loud. Clearly the volume level to dB mapping is wrong. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1188970] Xorg crashes with a segmentation fault when a secondary USB display using DisplayLink is connected
by bugzilla_noreply＠suse.com 05 Nov '21

05 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1188970 http://bugzilla.opensuse.org/show_bug.cgi?id=1188970#c58 --- Comment #58 from Thomas Zimmermann <tzimmermann(a)suse.com> --- Do I have to plug-in the USB device *before* starting X? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188970] Xorg crashes with a segmentation fault when a secondary USB display using DisplayLink is connected
by bugzilla_noreply＠suse.com 05 Nov '21

05 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1188970 http://bugzilla.opensuse.org/show_bug.cgi?id=1188970#c57 --- Comment #57 from Thomas Zimmermann <tzimmermann(a)suse.com> --- I cannot reproduce the issue. STR: * Installed the latest SLE15-SP3 LEAP installer without updates. * Started Gnome in X11 mode. * Tried with 3 different DisplayLink USB adapters, with VGA and DVI connectors. The main graphics card is an AMD driven by the radeon driver. There are no X crashes and no kernel warnings. The xorg-x11-server package is at 1.20.3.5.33.1. If there's better way to reproduce the bug, please let me know. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190256] Keyboard not working after cold-boot on ASUS Zenbook 14 UM425UA with Tumbleweed 20210904
by bugzilla_noreply＠suse.com 05 Nov '21

05 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1190256 https://bugzilla.suse.com/show_bug.cgi?id=1190256#c22 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(mkrapp(a)suse.com) --- Comment #22 from Takashi Iwai <tiwai(a)suse.com> --- I refreshed OBS home:tiwai:bsc1190256-2 repo with the latest patch. The 5.15.0 kernel is being built there, could you give it a try and verify that it works later? Once after confirming, I'll try to submit the fix to the upstream. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192232] Dock stations work but the devices become disconnected periodically
by bugzilla_noreply＠suse.com 05 Nov '21

05 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192232 https://bugzilla.suse.com/show_bug.cgi?id=1192232#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |oneukum(a)suse.com, | |tiwai(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Sounds like the TB/USB power management issue. Adding Oliver to Cc. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192232] Dock stations work but the devices become disconnected periodically
by bugzilla_noreply＠suse.com 05 Nov '21

05 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192232 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Other |Kernel Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192181] brightness keys mute mic instead (HP Elitebook 840 G6)
by bugzilla_noreply＠suse.com 04 Nov '21

04 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192181 https://bugzilla.suse.com/show_bug.cgi?id=1192181#c2 --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- Also please give the hwinfo output. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192181] brightness keys mute mic instead (HP Elitebook 840 G6)
by bugzilla_noreply＠suse.com 04 Nov '21

04 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192181 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andreas_nordal_4(a)hotmail.co | |m Flags| |needinfo?(andreas_nordal_4@ | |hotmail.com) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192091] 5.14.14 assumes USB controller as dead
by bugzilla_noreply＠suse.com 04 Nov '21

04 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192091 https://bugzilla.suse.com/show_bug.cgi?id=1192091#c9 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(stigpro(a)outlook.f | |r) --- Comment #9 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Nicolas FORMICHELLA from comment #8) > Thanks for that info, will try compiling my kernel from scratch and post > upstream if it is still broken Thanks! Meanwhile, I'm building three kernels to identify which patch breaks. OBS home:tiwai:bsc1192091-1 repo is with the revert of patches.kernel.org/5.14.12-007-usb-typec-tcpci-don-t-handle-vSafe0V-event-i…, OBS home:tiwai:bsc1192091-2 repo is with the revert of patches.kernel.org/5.14.12-008-usb-typec-tcpm-handle-SRC_STARTUP-state-if-c…, OBS home:tiwai:bsc1192091-3 repo is with the revert of patches.kernel.org/5.14.12-009-usb-typec-tipd-Remove-dependency-on-connecto…. Once when those get ready, please try one by one. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190095] New: Kernel 5.13.12: Intel graphics suddenly very slow on redraw
by bugzilla_noreply＠suse.com 04 Nov '21

04 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190095 Bug ID: 1190095 Summary: Kernel 5.13.12: Intel graphics suddenly very slow on redraw Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: axel.braun(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I did a dup from 20210810 to 20210828, and since then I noticed a very slow redraw on KDE Plasma: when scolling in a terminal or in a window, the screen looks 'broken' for a moment, then the rendering is back. 30: PCI 02.0: 0300 VGA compatible controller (VGA) [Created at pci.386] Unique ID: _Znp.WlxwpsiDkK3 SysFS ID: /devices/pci0000:00/0000:00:02.0 SysFS BusID: 0000:00:02.0 Hardware Class: graphics card Model: "Intel CoffeeLake-H GT2 [UHD Graphics 630]" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x3e9b "CoffeeLake-H GT2 [UHD Graphics 630]" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x229f Driver: "i915" Driver Modules: "i915" Memory Range: 0xe9000000-0xe9ffffff (rw,non-prefetchable) Memory Range: 0xc0000000-0xcfffffff (ro,non-prefetchable) I/O Ports: 0x4000-0x403f (rw) Memory Range: 0x000c0000-0x000dffff (rw,non-prefetchable,disabled) IRQ: 143 (1116926 events) Module Alias: "pci:v00008086d00003E9Bsv000017AAsd0000229Fbc03sc00i00" Driver Info #0: Driver Status: i915 is active Driver Activation Cmd: "modprobe i915" Config Status: cfg=new, avail=yes, need=no, active=unknown Switching to nvidia chipset (prime-select) the issue is gone Other users to confirm this issue (see factory mailing list) -- You are receiving this mail because: You are the assignee for the bug.

1 18

[Bug 1192328] New: copy files form exFAT with --preserve=timestamps
by bugzilla_noreply＠suse.com 04 Nov '21

04 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192328 Bug ID: 1192328 Summary: copy files form exFAT with --preserve=timestamps Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: wilms(a)pre-sense.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 853522 --> http://bugzilla.opensuse.org/attachment.cgi?id=853522&action=edit 5M exFAT partition for reproducing the error When mounting an exFAT partition in read-only mode: mount -o ro /path/to/partition /mountpoint and then trying to copy a file with: cp --preserve=timestamps /path/to/file/on/exfat /path/to/target/file then cp shows the following error: cp: preserving times for '/path/to/target/file': Invalid argument The file is copied but the timestamp is set to the current system time instead of the correct timestamp. This error occurs in a openSUSE Leap 15.3 Installation and also in the openSUSE Leap 15.3 LiveCD version. This error _does not_ occur when using Tumbleweed, which uses the native kernel implementation of exFAT due to having a more recent kernel afaik. Attached a qemu img with a 5M exFAT partition and a testfile easily reproduce the error. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1190200] New: Severe graphics glitches in KDE applications when compositor is disabled
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190200 Bug ID: 1190200 Summary: Severe graphics glitches in KDE applications when compositor is disabled Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: psychonaut(a)nothingisreal.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I normally run KDE with the compositor disabled. In this mode, all KDE applications exhibit severe screen corruption: all new text or graphics that appear have a garbled appearance, to the extent that text is completely illegible. The corruption sometimes disappears after a few seconds or after the window is scrolled. The problem does not affect GTK+ applications. The problem can be worked around by using systemsettings5 to tell KDE to enable the compositor at startup. However, simply changing the rendering backend (XRender vs. OpenGL) has no effect. I am using an onboard Intel HD Graphics 630 controller with the i915 driver. I'm not sure if it's the kernel driver/firmware which is causing the problem, but based on past experience with Intel graphics glitches, I am tentatively assuming it is. The problem occurred after updating Tumbleweed from version 20210810 to version 20210827. (In case it's relevant, this included an update of kernel-default 5.13.8 to 5.13.12, and from kernel-firmware-i915 from 20210719 to 20210812.) The problem persists in version 20210830. Booting from the old 5.13.8 kernel doesn't work around the problem. I could also try reverting kernel-firmware-i915 if I can find or build an old package. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1192116] Kernel 5.14.14 performance slow
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192116 https://bugzilla.suse.com/show_bug.cgi?id=1192116#c7 --- Comment #7 from Jason Straight <jason-opensuse(a)straights.net> --- (In reply to Takashi Iwai from comment #6) > Well, if it's with Nvidia binary-only driver, the things get more > complicated, unfortunately. Can we reproduce the problem without Nvidia > driver? Okay. I've given it some time with difference scenarios today. It appears to be nvidia. The time it did it with intel with me was after switching from nvidia to intel and whatever it does, it *corrupts* the operation so that switching with prime-select to intel still leaves things slow. It does not do it if I use only intel from boot, nor does it do it if I use offload. My system is an MSI GS75 Stealth laptop with a GTX2060. I mostly just use the nvidia because I need it for the external monitors, and nvenc is nice too. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180749] AMD Ryzen 4800H Renoir APU brightness control not working as found in some Lenovo Legion 5 15ARH05
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1180749 https://bugzilla.suse.com/show_bug.cgi?id=1180749#c46 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #46 from Takashi Iwai <tiwai(a)suse.com> --- Thanks for the updates. The commit mentioned above is also included in SLE15-SP3 kernel, so hopefully everything works now. Let's close for now. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192194] irq 40: nobody cared (try booting with the "irqpoll" option)
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192194 http://bugzilla.opensuse.org/show_bug.cgi?id=1192194#c9 --- Comment #9 from Takashi Iwai <tiwai(a)suse.com> --- Hmm, in the log you attached, irq 40 is assigned to the HD-audio device, so I guess it's a different situation. Could you try to reproduce the bug and get hwinfo / dmesg outputs from that state? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188970] Xorg crashes with a segmentation fault when a secondary USB display using DisplayLink is connected
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1188970 http://bugzilla.opensuse.org/show_bug.cgi?id=1188970#c56 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(guek.neo@toshibag | |cs.com) | --- Comment #56 from Stefan Dirsch <sndirsch(a)suse.com> --- Thanks. [ 3838.044] (EE) modeset(G0): glamor initialization failed So glamor still fails, but AIGLX/GLX working. Still the same crash ... [ 3840.795] (EE) [ 3840.795] (EE) Backtrace: [ 3840.795] (EE) 0: X (xorg_backtrace+0x65) [0x559970f6f5a5] [ 3840.795] (EE) 1: X (0x559970dbd000+0x1b6279) [0x559970f73279] [ 3840.795] (EE) 2: /lib64/libpthread.so.0 (0x7f476eec5000+0x13f80) [0x7f476eed8f80] [ 3840.795] (EE) 3: X (xf86ProbeOutputModes+0xa0e) [0x559970e8af2e] [ 3840.795] (EE) 4: X (0x559970dbd000+0xd6939) [0x559970e93939] [ 3840.795] (EE) 5: X (RRGetInfo+0x95) [0x559970ed44f5] [ 3840.795] (EE) 6: X (0x559970dbd000+0x1209e7) [0x559970edd9e7] [ 3840.795] (EE) 7: X (0x559970dbd000+0x5d018) [0x559970e1a018] [ 3840.795] (EE) 8: X (0x559970dbd000+0x6101c) [0x559970e1e01c] [ 3840.795] (EE) 9: /lib64/libc.so.6 (__libc_start_main+0xed) [0x7f476eb1534d] [ 3840.795] (EE) 10: X (_start+0x2a) [0x559970e07cba] [ 3840.796] (EE) [ 3840.796] (EE) Segmentation fault at address 0x0 [ 3840.796] (EE) [ 3840.796] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 3840.796] (EE) [ 3840.796] (EE) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188970] Xorg crashes with a segmentation fault when a secondary USB display using DisplayLink is connected
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1188970 http://bugzilla.opensuse.org/show_bug.cgi?id=1188970#c55 --- Comment #55 from Ricardo Lopez Caballero <ricardo-lopez-caballero(a)toshibagcs.com> --- (In reply to Stefan Dirsch from comment #53) > (In reply to Ricardo Lopez Caballero from comment #50) > > Created attachment 853506 [details] > > Supportconfig SLES15 SP3 QU1 kernel 5.3.18-59.24 without USB Display > > There's only x.txt, which doesn't contain Xorg.0.log apparently here. Did > this one crash? > > (In reply to Ricardo Lopez Caballero from comment #51) > > Created attachment 853507 [details] > > Supportconfig SLES15 SP3 QU1 kernel 5.3.18-59.24 Xorg crash USB display > > connected > > x.txt with Xorg.0.log but only the last 500 lines of /var/log/Xorg.0.log. > Not sure if this is from installation or from the installed system. Installation without USB Display. After installation and reboot, connected the USB Display and ran startx from console. See another supportconfig after Xorg crashed. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188970] Xorg crashes with a segmentation fault when a secondary USB display using DisplayLink is connected
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1188970 http://bugzilla.opensuse.org/show_bug.cgi?id=1188970#c54 Ricardo Lopez Caballero <ricardo-lopez-caballero(a)toshibagcs.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #853507|0 |1 is obsolete| | --- Comment #54 from Ricardo Lopez Caballero <ricardo-lopez-caballero(a)toshibagcs.com> --- Created attachment 853511 --> http://bugzilla.opensuse.org/attachment.cgi?id=853511&action=edit Supportconfig SLES15 SP3 QU1 5.3.18-59.24 Xorg crash USB Display connected supportconfig and Xorg.0.log added -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188970] Xorg crashes with a segmentation fault when a secondary USB display using DisplayLink is connected
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1188970 http://bugzilla.opensuse.org/show_bug.cgi?id=1188970#c53 --- Comment #53 from Stefan Dirsch <sndirsch(a)suse.com> --- (In reply to Ricardo Lopez Caballero from comment #50) > Created attachment 853506 [details] > Supportconfig SLES15 SP3 QU1 kernel 5.3.18-59.24 without USB Display There's only x.txt, which doesn't contain Xorg.0.log apparently here. Did this one crash? (In reply to Ricardo Lopez Caballero from comment #51) > Created attachment 853507 [details] > Supportconfig SLES15 SP3 QU1 kernel 5.3.18-59.24 Xorg crash USB display > connected x.txt with Xorg.0.log but only the last 500 lines of /var/log/Xorg.0.log. Not sure if this is from installation or from the installed system. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188970] Xorg crashes with a segmentation fault when a secondary USB display using DisplayLink is connected
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1188970 http://bugzilla.opensuse.org/show_bug.cgi?id=1188970#c52 --- Comment #52 from Ricardo Lopez Caballero <ricardo-lopez-caballero(a)toshibagcs.com> --- (In reply to Ricardo Lopez Caballero from comment #51) > Created attachment 853507 [details] > Supportconfig SLES15 SP3 QU1 kernel 5.3.18-59.24 Xorg crash USB display > connected [ 3840.795] (EE) Backtrace: [ 3840.795] (EE) 0: X (xorg_backtrace+0x65) [0x559970f6f5a5] [ 3840.795] (EE) 1: X (0x559970dbd000+0x1b6279) [0x559970f73279] [ 3840.795] (EE) 2: /lib64/libpthread.so.0 (0x7f476eec5000+0x13f80) [0x7f476eed8f80] [ 3840.795] (EE) 3: X (xf86ProbeOutputModes+0xa0e) [0x559970e8af2e] [ 3840.795] (EE) 4: X (0x559970dbd000+0xd6939) [0x559970e93939] [ 3840.795] (EE) 5: X (RRGetInfo+0x95) [0x559970ed44f5] [ 3840.795] (EE) 6: X (0x559970dbd000+0x1209e7) [0x559970edd9e7] [ 3840.795] (EE) 7: X (0x559970dbd000+0x5d018) [0x559970e1a018] [ 3840.795] (EE) 8: X (0x559970dbd000+0x6101c) [0x559970e1e01c] [ 3840.795] (EE) 9: /lib64/libc.so.6 (__libc_start_main+0xed) [0x7f476eb1534d] [ 3840.795] (EE) 10: X (_start+0x2a) [0x559970e07cba] [ 3840.796] (EE) [ 3840.796] (EE) Segmentation fault at address 0x0 [ 3840.796] (EE) Fatal server error: [ 3840.796] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 3840.796] (EE) [ 3840.796] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 3840.796] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 3840.796] (EE) [ 3840.796] (II) AIGLX: Suspending AIGLX clients for VT switch [ 3840.808] (EE) Server terminated with error (1). Closing log file. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188970] Xorg crashes with a segmentation fault when a secondary USB display using DisplayLink is connected
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1188970 http://bugzilla.opensuse.org/show_bug.cgi?id=1188970#c51 --- Comment #51 from Ricardo Lopez Caballero <ricardo-lopez-caballero(a)toshibagcs.com> --- Created attachment 853507 --> http://bugzilla.opensuse.org/attachment.cgi?id=853507&action=edit Supportconfig SLES15 SP3 QU1 kernel 5.3.18-59.24 Xorg crash USB display connected -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188970] Xorg crashes with a segmentation fault when a secondary USB display using DisplayLink is connected
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1188970 http://bugzilla.opensuse.org/show_bug.cgi?id=1188970#c50 --- Comment #50 from Ricardo Lopez Caballero <ricardo-lopez-caballero(a)toshibagcs.com> --- Created attachment 853506 --> http://bugzilla.opensuse.org/attachment.cgi?id=853506&action=edit Supportconfig SLES15 SP3 QU1 kernel 5.3.18-59.24 without USB Display -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192116] Kernel 5.14.14 performance slow
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192116 https://bugzilla.suse.com/show_bug.cgi?id=1192116#c6 --- Comment #6 from Takashi Iwai <tiwai(a)suse.com> --- Well, if it's with Nvidia binary-only driver, the things get more complicated, unfortunately. Can we reproduce the problem without Nvidia driver? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192116] Kernel 5.14.14 performance slow
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192116 https://bugzilla.suse.com/show_bug.cgi?id=1192116#c5 --- Comment #5 from Jason Straight <jason-opensuse(a)straights.net> --- I'm afraid I spoke too soon. After the computer was on all night, the slowness is back this morning. How do I go about getting the source and compiling? I've compiled the kernel many times, but that was prior to about 15-20 yrs ago. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192288] New: amd64_edac_mod does not load after CPU upgrade
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192288 Bug ID: 1192288 Summary: amd64_edac_mod does not load after CPU upgrade Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: seroton10(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On a server running an AMD Ryzen 9 3900X CPU, I use the following output, written during boot, to verify that DRAM ECC is enabled: Oct 31 13:44:48 blackbox kernel: EDAC MC: Ver: 3.0.0 ... Oct 31 13:44:53 blackbox kernel: EDAC amd64: F17h_M70h detected (node 0). Oct 31 13:44:53 blackbox kernel: EDAC MC: UMC0 chip selects: Oct 31 13:44:53 blackbox kernel: EDAC amd64: MC: 0: 0MB 1: 0MB Oct 31 13:44:53 blackbox kernel: EDAC amd64: MC: 2: 8192MB 3: 8192MB Oct 31 13:44:53 blackbox kernel: EDAC MC: UMC1 chip selects: Oct 31 13:44:53 blackbox kernel: EDAC amd64: MC: 0: 0MB 1: 0MB Oct 31 13:44:53 blackbox kernel: EDAC amd64: MC: 2: 8192MB 3: 8192MB Oct 31 13:44:53 blackbox kernel: EDAC amd64: using x16 syndromes. Oct 31 13:44:53 blackbox kernel: EDAC amd64: Node 0: DRAM ECC enabled. Oct 31 13:44:53 blackbox kernel: EDAC amd64: MCT channel count: 2 Oct 31 13:44:53 blackbox kernel: EDAC MC0: Giving out device to module amd64_edac controller F17h_M70h: DEV 0000:00:18.3 (INTERRUPT) Oct 31 13:44:53 blackbox kernel: EDAC PCI0: Giving out device to module amd64_edac controller EDAC PCI controller: DEV 0000:00:18.0 (POLLED) Oct 31 13:44:53 blackbox kernel: AMD64 EDAC driver v3.5.0 Due to a CPU failure, I was forced to replace it, so decided to also upgrade to an AMD Ryzen 9 5900X CPU. (No other hardware or software changes were made.) Now I only see the first line mentioning EDAC in the log: Nov 02 13:28:54 blackbox kernel: EDAC amd64: F19h detected (node 0). Nov 02 13:28:54 blackbox kernel: EDAC amd64: Error: F0 not found, device 0x1650 (broken BIOS?) An attempt to manually load the AMD EDAC driver fails: # modprobe amd64_edac_mod modprobe: ERROR: could not insert 'amd64_edac_mod': No such device Would it be possible to add or backport the missing hardware support in the Leap 15.3 kernel, please? -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1188970] Xorg crashes with a segmentation fault when a secondary USB display using DisplayLink is connected
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1188970 https://bugzilla.suse.com/show_bug.cgi?id=1188970#c49 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(guek.neo@toshibag | |cs.com) --- Comment #49 from Stefan Dirsch <sndirsch(a)suse.com> --- Does this crash happen only during installation or also still on installed system? I'm asking since OpenGL driver is missing during installation (by intention; llvm libs are simply too big), but should be available on installed system. In order to do a successful installation, install *without* the USB Displaylink. After successful installation add it again and reboot. Also I would like to see a /var/log/Xorg.0.log for an installed system with USB Displaylink attached. Thanks. Notes for myself: [ 84.881] (EE) modeset(G0): glamor initialization failed [ 85.173] (II) Initializing extension MIT-SCREEN-SAVER [ 85.175] (EE) AIGLX error: dlopen of /usr/lib64/dri/swrast_dri.so failed (/usr/lib64/dri/swrast_dri.so: cannot open shared object file: No such file or directory) [ 85.175] (EE) AIGLX error: unable to load driver swrast [ 85.175] (EE) GLX: could not load software renderer [ 86.030] (EE) [ 86.030] (EE) Backtrace: [ 86.030] (EE) 0: Xorg (xorg_backtrace+0x65) [0x562700e315a5] [ 86.031] (EE) 1: Xorg (0x562700c7f000+0x1b6279) [0x562700e35279] [ 86.031] (EE) 2: /lib64/libpthread.so.0 (0x7f982b1e2000+0x13f80) [0x7f982b1f5f80] [ 86.031] (EE) 3: Xorg (xf86ProbeOutputModes+0xa0e) [0x562700d4cf2e] [ 86.031] (EE) 4: Xorg (0x562700c7f000+0xd6939) [0x562700d55939] [ 86.031] (EE) 5: Xorg (RRGetInfo+0x95) [0x562700d964f5] [ 86.031] (EE) 6: Xorg (0x562700c7f000+0x1209e7) [0x562700d9f9e7] [ 86.031] (EE) 7: Xorg (0x562700c7f000+0x5d018) [0x562700cdc018] [ 86.031] (EE) 8: Xorg (0x562700c7f000+0x6101c) [0x562700ce001c] [ 86.031] (EE) 9: /lib64/libc.so.6 (__libc_start_main+0xed) [0x7f982ae3234d] [ 86.031] (EE) 10: Xorg (_start+0x2a) [0x562700cc9cba] [ 86.031] (EE) [ 86.031] (EE) Segmentation fault at address 0x0 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192116] Kernel 5.14.14 performance slow
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192116 https://bugzilla.suse.com/show_bug.cgi?id=1192116#c4 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- OK, thanks for the updates. Let's close now. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188970] Xorg crashes with a segmentation fault when a secondary USB display using DisplayLink is connected
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1188970 https://bugzilla.suse.com/show_bug.cgi?id=1188970#c48 --- Comment #48 from Thomas Zimmermann <tzimmermann(a)suse.com> --- (In reply to guek wu neo from comment #47) > (In reply to Thomas Zimmermann from comment #45) > > (In reply to guek wu neo from comment #40) > > > (In reply to guek wu neo from comment #38) > > > > (In reply to Takashi Iwai from comment #37) > > > > > Then please try the quarterly update release of SLE15-SP3. It contains the > > > > > recent upstream kernel in the installer, and this might have been already > > > > > fixed. > > > > > > > I tried 'SLE-15-SP3-Full-x86_64-QU1-Media1.iso' that is with kernel > > > 5.3.18=59.24-default.. but still run into the same red error prompt > > > 'An error occured during the installation' > > > > Can you please confirm that the kernel bug is present even with the latest > > installer? > > > > According to our internal logs, the kernel fix was added on Jan 12. It > > should have been in the installer since forever. If it still shows up, > > there's maybe another issue here. :/ > > Yes, see comment 46 :attachment 853485 [details] for the Zip of /var/log of > the affected system of TigerLake. > Thanks for the pointer. In these logs there is no *kernel* error AFAICS. The i915 and udl drivers load without problems. > > Xorg.0.log: > > "..[ 86.031] (EE) 9: /lib64/libc.so.6 (__libc_start_main+0xed) > [0x7f982ae3234d] > [ 86.031] (EE) 10: Xorg (_start+0x2a) [0x562700cc9cba] > [ 86.031] (EE) > [ 86.031] (EE) Segmentation fault at address 0x0 > [ 86.031] (EE) > Fatal server error: > [ 86.031] (EE) Caught signal 11 (Segmentation fault). Server aborting > [ 86.031] (EE) > [ 86.031] (EE) > ...? This is the X11 crash and still present on the TigerLake system. Here's my guess: these are two separate issues; one in the kernel and one in X11. The kernel has been fixed already, but for some reason your installer doesn't have that fix. The X11 issue is still present. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192194] irq 40: nobody cared (try booting with the "irqpoll" option)
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192194 http://bugzilla.opensuse.org/show_bug.cgi?id=1192194#c8 --- Comment #8 from John Shand <jshand2013(a)gmail.com> --- Created attachment 853488 --> http://bugzilla.opensuse.org/attachment.cgi?id=853488&action=edit dmesg file log -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192194] irq 40: nobody cared (try booting with the "irqpoll" option)
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192194 http://bugzilla.opensuse.org/show_bug.cgi?id=1192194#c7 --- Comment #7 from John Shand <jshand2013(a)gmail.com> --- Created attachment 853487 --> http://bugzilla.opensuse.org/attachment.cgi?id=853487&action=edit Hardware Information -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192194] irq 40: nobody cared (try booting with the "irqpoll" option)
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192194 http://bugzilla.opensuse.org/show_bug.cgi?id=1192194#c6 --- Comment #6 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to John Shand from comment #5) > (In reply to John Shand from comment #3) > > (In reply to Takashi Iwai from comment #1) > > > Hm, this might be a stray irq after de-registering the HD-audio controller > > > irq handler. Could you check what takes irq 40? Please check the contents > > > of /proc/interrupts during playing some tone from the onboard audio. > > > > i'm new to debugging. how do i go about finding this information out? > > all good i found it out. > > irq 40 was interestingly my ethernet card named enp2s0f1. i have this card > setup just incase of a system meltdown OK, then could you give hwinfo output as well as the full dmesg output? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188970] Xorg crashes with a segmentation fault when a secondary USB display using DisplayLink is connected
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1188970 https://bugzilla.suse.com/show_bug.cgi?id=1188970#c47 --- Comment #47 from guek wu neo <guek.neo(a)toshibagcs.com> --- (In reply to Thomas Zimmermann from comment #45) > (In reply to guek wu neo from comment #40) > > (In reply to guek wu neo from comment #38) > > > (In reply to Takashi Iwai from comment #37) > > > > Then please try the quarterly update release of SLE15-SP3. It contains the > > > > recent upstream kernel in the installer, and this might have been already > > > > fixed. > > > > > I tried 'SLE-15-SP3-Full-x86_64-QU1-Media1.iso' that is with kernel > > 5.3.18=59.24-default.. but still run into the same red error prompt > > 'An error occured during the installation' > > Can you please confirm that the kernel bug is present even with the latest > installer? > > According to our internal logs, the kernel fix was added on Jan 12. It > should have been in the installer since forever. If it still shows up, > there's maybe another issue here. :/ Yes, see comment 46 :attachment 853485 for the Zip of /var/log of the affected system of TigerLake. Xorg.0.log: "..[ 86.031] (EE) 9: /lib64/libc.so.6 (__libc_start_main+0xed) [0x7f982ae3234d] [ 86.031] (EE) 10: Xorg (_start+0x2a) [0x562700cc9cba] [ 86.031] (EE) [ 86.031] (EE) Segmentation fault at address 0x0 [ 86.031] (EE) Fatal server error: [ 86.031] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 86.031] (EE) [ 86.031] (EE) ...? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192116] Kernel 5.14.14 performance slow
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192116 https://bugzilla.suse.com/show_bug.cgi?id=1192116#c3 --- Comment #3 from Jason Straight <jason-opensuse(a)straights.net> --- (In reply to Takashi Iwai from comment #2) > Hrm, it's very hard to judge only from the description... Does the problem > appear without graphics? > > Basically the best option for hunting the culprit would be the git > bisection. If you don't mind to compile the kernel by yourself, it'd be > appreciated to perform git bisection. > > The kernel build itself won't be too difficult in this case. It'll need the > significant disk space and certain compile time, though. Booted with latest nvidia drivers that updated today and the problem appears to be gone, so it was likely just the last nvidia driver with that kernel version. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188970] Xorg crashes with a segmentation fault when a secondary USB display using DisplayLink is connected
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1188970 https://bugzilla.suse.com/show_bug.cgi?id=1188970#c46 --- Comment #46 from guek wu neo <guek.neo(a)toshibagcs.com> --- Created attachment 853485 --> https://bugzilla.suse.com/attachment.cgi?id=853485&action=edit zip of /var/log of the affected system -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191229] New: [Staging][rpm4.17] Kernel fails to build with rpm 4.17
by bugzilla_noreply＠suse.com 02 Nov '21

02 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1191229 Bug ID: 1191229 Summary: [Staging][rpm4.17] Kernel fails to build with rpm 4.17 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- RPM 4.17 has been submitted for inclusion into Tumbleweed. There is at least one backwards incompatible change that affects the kernel builds. The build fails with: [ 134s] error: /home/abuild/rpmbuild/SOURCES/kernel-source.spec: line 130: %verbose: unexpected argument [ 134s] 2< (%verbose) The problem there is that %{verbose} is no longer a 'function' taking an argument, but rather a variable, set to 0/1. In other packages where we encountered this issue, we simply gave up on the construct of using verbose to adjust the build log level -- You are receiving this mail because: You are the assignee for the bug.

1 1