November 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[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