January 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1188940] New: bluetooth adapter fails to power on
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1188940 Bug ID: 1188940 Summary: bluetooth adapter fails to power on 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: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- hramrach@naga:~> bluetoothctl Agent registered [CHG] Controller 00:E0:3C:87:B8:03 Pairable: yes [bluetooth]# power on Failed to set power on: org.bluez.Error.Failed [bluetooth]# power on Failed to set power on: org.bluez.Error.Busy [bluetooth]# power on Failed to set power on: org.bluez.Error.Busy [bluetooth]# power on Failed to set power on: org.bluez.Error.Busy [bluetooth]# -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1188889] New: crash is failing with 5.13 kernels
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1188889 Bug ID: 1188889 Summary: crash is failing with 5.13 kernels 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: hare(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When trying to run crash on a 5.13 or later kernel dump I get the error message: crash: invalid structure member offset: task_struct_state FILE: task.c LINE: 5916 FUNCTION: task_state() [/usr/bin/crash] error trace: 559027f7b785 => 559027f7b54d => 559027fffe94 => 559027fffe0d This has been fixed by upstream commit d6b4f36d6b22b70fb14e692f36d20910ef5563c1. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1207398] [Build 20230121] snapper_create times out and causes kernel backtrace
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1207398 https://bugzilla.suse.com/show_bug.cgi?id=1207398#c3 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |jslaby(a)suse.com Resolution|--- |DUPLICATE --- Comment #3 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Arvin Schnell from comment #2) > The kernel backtrace looks to me like the one in bug #1206681. So maybe > the problem is already fixed with kernel 6.1.8. Yes, looks like a dup. *** This bug has been marked as a duplicate of bug 1206681 *** -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1179092] [i915] Screen occasionally goes blank, sometimes staying that way until I press a key
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1179092 https://bugzilla.suse.com/show_bug.cgi?id=1179092#c27 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |jslaby(a)suse.com Resolution|--- |UPSTREAM Flags|needinfo?(tiwai(a)suse.com) | --- Comment #27 from Jiri Slaby <jslaby(a)suse.com> --- Does this still happen? It looks the bug bitrot after such a long time :/. Has this been tested under Wayland? X attracts little attention these days. Esp. for intel drivers. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1184718] New: systemtap simple helloworld script execution fails in Tumbleweed
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1184718 Bug ID: 1184718 Summary: systemtap simple helloworld script execution fails in Tumbleweed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: vasilios.anastasiadis(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 848350 --> https://bugzilla.suse.com/attachment.cgi?id=848350&action=edit Related errors Unable to run a simple systemtap helloworld.stp example script (provided with systemtap-docs) in Tumbleweed. It works fine in SLE versions 12sp2-15sp3. Steps to reproduce: - Install systemtap, systemtap-docs, kernel-default-devel - Run: stap /usr/share/doc/packages/systemtap/examples/general/helloworld.stp See attached file for errors. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1185008] CPU tainted in dmesg since 5.11
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1185008 https://bugzilla.suse.com/show_bug.cgi?id=1185008#c18 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |NORESPONSE --- Comment #18 from Jiri Slaby <jslaby(a)suse.com> --- Feel free to reopen when providing the requested info. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188712] New: VDSO change on PPC causes random segfaults in Go applications
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1188712 Bug ID: 1188712 Summary: VDSO change on PPC causes random segfaults in Go applications Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: PowerPC-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: jkowalczyk(a)suse.com Found By: --- Blocker: --- https://lwn.net/ml/linux-kernel/cover.1601365869.git.christophe.leroy@csgro… changed the implementation of the VDSO from a PowerPC specific one to the generic C version. Apparently executables built with Go before 1.17 implicitly relied on the fact that the VDSO did not mangle r30, but with the generic C implementation it now does. This leads to random crashes in Go executables. This is fixed with https://go-review.googlesource.com/c/go/+/334410/1 and I submitted this to our go1.16 package with https://build.opensuse.org/request/show/907807. However, all executables built with a compiler which doesn't include that will not work on kernel >= 5.13. This probably affects containerized workloads as well. So it might be useful to raise awareness of this issue. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1207398] [Build 20230121] snapper_create times out and causes kernel backtrace
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1207398 https://bugzilla.suse.com/show_bug.cgi?id=1207398#c2 Arvin Schnell <aschnell(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.suse.com/s | |how_bug.cgi?id=1206681 --- Comment #2 from Arvin Schnell <aschnell(a)suse.com> --- The kernel backtrace looks to me like the one in bug #1206681. So maybe the problem is already fixed with kernel 6.1.8. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188658] Kernel crash in i915 when starting Gnome Wayland on Laptop with i915+nvidia modules loaded (Optimus)
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1188658 https://bugzilla.suse.com/show_bug.cgi?id=1188658#c4 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |jslaby(a)suse.com Resolution|--- |FIXED --- Comment #4 from Jiri Slaby <jslaby(a)suse.com> --- The upstream bug states: This issue is not happening anymore on current openSUSE Tumbleweed, where every part of the stack is newer: So closing too. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188394] Unable to use USB3 port on Rock64
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1188394 https://bugzilla.suse.com/show_bug.cgi?id=1188394#c7 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com Flags| |needinfo?(jonasdcdm@mailbox | |.org) --- Comment #7 from Jiri Slaby <jslaby(a)suse.com> --- Does this still happen? It looks the bug bitrot after such a long time :/. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207243] kernel 6.1.4 fails to boot: nvme0n1: No UUID available providing old NGUID
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207243 http://bugzilla.opensuse.org/show_bug.cgi?id=1207243#c17 --- Comment #17 from Daniel Wagner <daniel.wagner(a)suse.com> --- This looks like the system is stuck switching to the desktop environment. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207388] AMD RDNA3 Navi31: amdgpu driver and a not visible mouse cursor when using amdgpu X driver
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

1 0

[Bug 1207388] AMD RDNA3 Navi31: amdgpu driver and a not visible mouse cursor
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207388 http://bugzilla.opensuse.org/show_bug.cgi?id=1207388#c6 --- Comment #6 from Stefan Dirsch <sndirsch(a)suse.com> --- Looks like this one: https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/61 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207388] AMD RDNA3 Navi31: amdgpu driver and a not visible mouse cursor
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207388 http://bugzilla.opensuse.org/show_bug.cgi?id=1207388#c5 --- Comment #5 from Patrik Jakobsson <patrik.jakobsson(a)suse.com> --- If the firmware is not loaded the screen gets frozen during boot. So I'm assuming he's got the right firmware files installed. Unless there is a specific reason for running the amdgpu ddx driver I would recommend using the modesetting driver instead. Or even better, use Wayland. I don't think there is much development happening on the amdgpu ddx driver. Bj�rn, if you really would like to have this issue fixed I would recommend reporting this to upstream at: https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues They are in a much better position to fix the bug. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207349] OpenSuse Leap 15.5 alpha
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207349 http://bugzilla.opensuse.org/show_bug.cgi?id=1207349#c2 --- Comment #2 from uwe Luedecke <uwe.luedecke(a)t-online.de> --- Thank you Mr. Striegler for replying so quickly. I don't know if I already reported the bug here. Surely it was at www.linux-club.de. My problem in detail: Operating system: openSUSE Leap 15.5 KDE Plasma version: 5.24.4 KDE Framework Version: 5.100.0 Qt version: 5.15.2 Kernel version: 6.1.7-lp153.3.g2ebd33f-default (64-bit) GraphicsPlatform: X11 Processors: 8 �� Intel�� Core�� i7-4710HQ CPU @ 2.50GHz Memory: 15.6 GiB of RAM Graphics Processor: Mesa Intel�� HD Graphics 4600 It's all about memory: that 15.6 GIB of Ram may not be enough and the laptop freezes. No mouse, no keyboard work anymore. With LibreOffice Base I do the sales tax calculation for our two offices. I also listen to the radio via VLC. Both are enough for the RAM to run full, which is of course not so great when calculating sales tax. What I also noticed is that /usb/lib/mozillahelper is currently displayed 12 times in the system monitor. Kind regards Uwe Luedecke -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207388] AMD RDNA3 Navi31: amdgpu driver and a not visible mouse cursor
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207388 http://bugzilla.opensuse.org/show_bug.cgi?id=1207388#c4 --- Comment #4 from Bj�rn Adelberg <bjawebos(a)adelberg-online.de> --- (In reply to Takashi Iwai from comment #2) > Make sure that you've installed the latest kernel-firmware-amdgpu package > (20230110 or later). I'm sure :) ``` bja@localhost:~> zypper info kernel-firmware-amdgpu Repository-Daten werden geladen... Installierte Pakete werden gelesen... Informationen zu Paket kernel-firmware-amdgpu: ---------------------------------------------- Repository : Haupt-Repository (OSS) Name : kernel-firmware-amdgpu Version : 20230110-1.1 Arch : noarch Anbieter : openSUSE Installierte Gr��e : 14,7 MiB Installiert : Ja (automatisch) Status : aktuell Quellpaket : kernel-firmware-20230110-1.1.src Upstream-URL : https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/ Zusammenfassung : Kernel firmware files for AMDGPU graphics driver Beschreibung : This package contains compressed kernel firmware files for AMDGPU graphics driver. ``` -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207388] AMD RDNA3 Navi31: amdgpu driver and a not visible mouse cursor
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207388 http://bugzilla.opensuse.org/show_bug.cgi?id=1207388#c2 --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- Make sure that you've installed the latest kernel-firmware-amdgpu package (20230110 or later). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207388] AMD RDNA3 Navi31: amdgpu driver and a not visible mouse cursor
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207388 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|amdgpu driver and a not |AMD RDNA3 Navi31: amdgpu |visible mouse cursor |driver and a not visible | |mouse cursor -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207388] amdgpu driver and a not visible mouse cursor
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207388 http://bugzilla.opensuse.org/show_bug.cgi?id=1207388#c1 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |patrik.jakobsson(a)suse.com, | |tiwai(a)suse.com, | |tzimmermann(a)suse.com Component|X11 3rd Party Driver |Kernel Assignee|gfx-bugs(a)suse.de |kernel-bugs(a)opensuse.org QA Contact|sndirsch(a)suse.com |qa-bugs(a)suse.de --- Comment #1 from Stefan Dirsch <sndirsch(a)suse.com> --- That's interesting. AFAIK AMD hasn't released yet the required firmware for these RDNA3 Navi31 GPUs. So it's weird to see it working at all. Reassigning. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207149] brightness keys not working on Lenovo ideapad 3
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1207149 https://bugzilla.suse.com/show_bug.cgi?id=1207149#c6 --- Comment #6 from Takashi Iwai <tiwai(a)suse.com> --- Also, I'm building a test openSUSE Leap 15.4 kernel with 4 backport patches. It's being built in OBS home:tiwai:bsc1207149 project. Please give it a try later, too. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207398] New: [Build 20230121] openQA test fails in snapper_create
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207398 Bug ID: 1207398 Summary: [Build 20230121] openQA test fails in snapper_create Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3060320/modules/snap per_create/steps/175 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 [ 237.150953][ T7786] ------------[ cut here ]------------ [ 237.151305][ T7786] WARNING: CPU: 0 PID: 7786 at fs/btrfs/qgroup.c:2756 btrfs_qgroup_account_extents+0x1ae/0x260 [btrfs] [ 237.152045][ T7786] Modules linked in: dm_mirror dm_region_hash dm_log xfs algif_hash af_alg isofs loop af_packet nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 rfkill nf_tables nfnetlink qrtr intel_rapl_msr intel_rapl_common kvm_intel snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec kvm snd_hda_core hid_generic ppdev snd_hwdep snd_pcm snd_timer irqbypass virtio_net pcspkr usbhid net_failover snd soundcore failover i2c_piix4 parport_pc parport tiny_power_button button joydev fuse configfs efi_pstore dmi_sysfs ip_tables x_tables crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic gf128mul ghash_clmulni_intel sha512_ssse3 xhci_pci xhci_pci_renesas sr_mod xhci_hcd cdrom ata_generic usbcore aesni_intel bochs crypto_simd drm_vram_helper drm_ttm_helper cryptd virtio_blk virtio_scsi ttm ata_piix [ 237.152108][ T7786] floppy serio_raw btrfs blake2b_generic libcrc32c crc32c_intel xor raid6_pq sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua qemu_fw_cfg virtio_rng [ 237.159714][ T7786] CPU: 0 PID: 7786 Comm: snapperd Not tainted 6.1.7-1-default #1 openSUSE Tumbleweed a17afadcf9a901153fe6ca80a070f1e187893ea7 [ 237.160439][ T7786] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.15.0-0-g2dd4b9b-rebuilt.opensuse.org 04/01/2014 [ 237.161101][ T7786] RIP: 0010:btrfs_qgroup_account_extents+0x1ae/0x260 [btrfs] [ 237.161582][ T7786] Code: 85 c0 74 0f 48 8b 78 08 4c 89 fa 4c 89 ee e8 69 54 f5 ff 65 ff 0d 62 ed c2 3f 0f 85 b8 fe ff ff 0f 1f 44 00 00 e9 ae fe ff ff <0f> 0b 49 8b 57 18 45 31 c9 4d 8d 47 38 31 c9 4c 89 ee e8 1b 71 ff [ 237.163108][ T7786] RSP: 0018:ffffa4474276bd10 EFLAGS: 00010246 [ 237.163604][ T7786] RAX: ffff973bc45e2200 RBX: 0000000000000000 RCX: 000000001e77a000 [ 237.164070][ T7786] RDX: ffff973bc45e2200 RSI: fa4b1784ad2c596e RDI: 0000000000000000 [ 237.164517][ T7786] RBP: ffff973bf408ed60 R08: ffffa4474276bc20 R09: 0000000000000c40 [ 237.164946][ T7786] R10: 0000000000000230 R11: 0000000000000001 R12: 0000000000000001 [ 237.165377][ T7786] R13: ffff973bc57c1000 R14: ffff973bc65c62d8 R15: ffff973bc45e2200 [ 237.165839][ T7786] FS: 00007f790a7ae6c0(0000) GS:ffff973c1e400000(0000) knlGS:0000000000000000 [ 237.166360][ T7786] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 237.166709][ T7786] CR2: 00007f54d732fd10 CR3: 0000000002786005 CR4: 0000000000170ef0 [ 237.167140][ T7786] Call Trace: [ 237.167327][ T7786] <TASK> [ 237.167514][ T7786] btrfs_commit_transaction+0x30c/0xb40 [btrfs 2ea8094e67f3b293bbbe82d0cac0a33a1d6459b5] [ 237.168096][ T7786] ? start_transaction+0xc3/0x5b0 [btrfs 2ea8094e67f3b293bbbe82d0cac0a33a1d6459b5] [ 237.168646][ T7786] btrfs_qgroup_rescan+0x42/0xc0 [btrfs 2ea8094e67f3b293bbbe82d0cac0a33a1d6459b5] [ 237.169234][ T7786] btrfs_ioctl+0x1ab0/0x25b0 [btrfs 2ea8094e67f3b293bbbe82d0cac0a33a1d6459b5] [ 237.169802][ T7786] ? __seccomp_filter+0x319/0x4d0 [ 237.170125][ T7786] __x64_sys_ioctl+0x90/0xd0 [ 237.170400][ T7786] do_syscall_64+0x5b/0x80 [ 237.170666][ T7786] ? syscall_exit_to_user_mode+0x17/0x40 [ 237.170977][ T7786] ? do_syscall_64+0x67/0x80 [ 237.171229][ T7786] entry_SYSCALL_64_after_hwframe+0x63/0xcd [ 237.171549][ T7786] RIP: 0033:0x7f790af0d9bf [ 237.171791][ T7786] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00 [ 237.172859][ T7786] RSP: 002b:00007f790a7ad7e0 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [ 237.173313][ T7786] RAX: ffffffffffffffda RBX: 0000000000000007 RCX: 00007f790af0d9bf [ 237.173913][ T7786] RDX: 00007f790a7ad840 RSI: 000000004040942c RDI: 0000000000000007 [ 237.174412][ T7786] RBP: 00007f790a7ad840 R08: 0000000000000000 R09: 0000000000000000 [ 237.174915][ T7786] R10: 0000000000001000 R11: 0000000000000246 R12: 000056142ae570e0 [ 237.175889][ T7786] R13: 00007f790a7ada30 R14: 00007f790a7ada60 R15: 00007f790a7ada1f [ 237.176821][ T7786] </TASK> [ 237.177453][ T7786] ---[ end trace 0000000000000000 ]--- [ 237.182321][ T7786] ------------[ cut here ]------------ openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_filesystem@64bit fails in [snapper_create](https://openqa.opensuse.org/tests/3060320/modules/snapper_c… ## Test suite description Maintainer: QE Core Filesystem related tests, for example snapper and btrfs features. ## Reproducible Fails since (at least) Build [20230121](https://openqa.opensuse.org/tests/3059391) ## Expected result Last good: [20230120](https://openqa.opensuse.org/tests/3057710) (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 1

[Bug 1207149] brightness keys not working on Lenovo ideapad 3
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1207149 https://bugzilla.suse.com/show_bug.cgi?id=1207149#c5 --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- Could you test the 6.2-rc kernel in OBS Kernel:HEAD:Backport? I found the upstream bug entry https://bugzilla.kernel.org/show_bug.cgi?id=214899 and the fix patches landed in 6.2-rc1. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207243] kernel 6.1.4 fails to boot: nvme0n1: No UUID available providing old NGUID
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207243 http://bugzilla.opensuse.org/show_bug.cgi?id=1207243#c16 --- Comment #16 from Chris Puttick <chris(a)twoten.is> --- Created attachment 864312 --> http://bugzilla.opensuse.org/attachment.cgi?id=864312&action=edit photo of screen following crashed start up sequence -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207243] kernel 6.1.4 fails to boot: nvme0n1: No UUID available providing old NGUID
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207243 http://bugzilla.opensuse.org/show_bug.cgi?id=1207243#c15 --- Comment #15 from Chris Puttick <chris(a)twoten.is> --- Have now persuaded journalctl to be in a sensible configuration, but it doesn't log anything particularly insightful the fail per se. Last line logged on failed boots (both normal and recovery) is systemd-journald[610]: Time spent on flushing to /var/log/journal/ on the normal boot process with the older kernel, this line is followed with systemd-journald[605]: Received client request to flush runtime journal. systemd-journald[605]: File /var/log/journal/84403c8f9fc24658abd0248aa7f8cc73/system.journal corrupted or uncleanly shut down, renaming and replacing. kernel: thermal LNXTHERM:00: registered as thermal_zone10 kernel: ACPI: thermal: Thermal Zone [THM] (25 C) kernel: intel-lpss 0000:00:15.0: enabling device (0000 -> 0002) kernel: mc: Linux media interface: v0.10 kernel: idma64 idma64.0: Found Intel integrated DMA 64-bit kernel: mei_me 0000:00:16.0: enabling device (0000 -> 0002) kernel: ACPI: bus type thunderbolt registered I took a pic of the lines showing on the failed boot in recovery mode and will attach it. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1187510] Display crashes on RPI 4B with Gnome/Wayland
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1187510 https://bugzilla.suse.com/show_bug.cgi?id=1187510#c8 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |David(a)WalkerStreet.info, | |jslaby(a)suse.com Flags| |needinfo?(David@WalkerStree | |t.info) --- Comment #8 from Jiri Slaby <jslaby(a)suse.com> --- Does this still happen? It looks the bug bitrot after such a long time :/. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1185649] [Build 20210504] openQA test fails in kdump_and_crash
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1185649 Guillaume GARDET <guillaume.gardet(a)arm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.opensuse.o | |rg/show_bug.cgi?id=1190434 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1185649] [Build 20210504] openQA test fails in kdump_and_crash
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1185649 https://bugzilla.suse.com/show_bug.cgi?id=1185649#c9 --- Comment #9 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- (In reply to Guillaume GARDET from comment #8) > (In reply to Jiri Slaby from comment #7) > > Does this still happen? It looks like the bug bitrot. > > Yes, it still happens, see: > https://openqa.opensuse.org/tests/3055822#step/kdump_and_crash/61 But this seems to be different from the original report and tracked here: https://bugzilla.opensuse.org/show_bug.cgi?id=1190434 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1187761] [RPi3] brcmfmac problem
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1187761 https://bugzilla.suse.com/show_bug.cgi?id=1187761#c20 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |jslaby(a)suse.com Resolution|--- |INVALID --- Comment #20 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Marius Tomaschewski from comment #19) > I think, we can close this issue then (IMO as INVALID) then. Let's proceed after such a long time. Feel free to reopen when providing the requested info. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1185649] [Build 20210504] openQA test fails in kdump_and_crash
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1185649 https://bugzilla.suse.com/show_bug.cgi?id=1185649#c8 Guillaume GARDET <guillaume.gardet(a)arm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(guillaume.gardet@ | |arm.com) | --- Comment #8 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- (In reply to Jiri Slaby from comment #7) > Does this still happen? It looks like the bug bitrot. Yes, it still happens, see: https://openqa.opensuse.org/tests/3055822#step/kdump_and_crash/61 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1185970] Switching Graphics Freezes Whole System
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1185970 https://bugzilla.suse.com/show_bug.cgi?id=1185970#c5 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |jslaby(a)suse.com Resolution|--- |NORESPONSE --- Comment #5 from Jiri Slaby <jslaby(a)suse.com> --- Feel free to reopen when providing the requested info. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1185649] [Build 20210504] openQA test fails in kdump_and_crash
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1185649 https://bugzilla.suse.com/show_bug.cgi?id=1185649#c7 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com Flags| |needinfo?(guillaume.gardet@ | |arm.com) --- Comment #7 from Jiri Slaby <jslaby(a)suse.com> --- Does this still happen? It looks like the bug bitrot. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1187521] System freezes randomly Lenovo Thinkpad E495
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1187521 https://bugzilla.suse.com/show_bug.cgi?id=1187521#c6 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |jslaby(a)suse.com Resolution|--- |UPSTREAM --- Comment #6 from Jiri Slaby <jslaby(a)suse.com> --- I'm afraid there is a little we can do about this, provided this is an upstream bug. Maybe the FW down/upgrade helped as they suggest? In anyway, let's continue in the upstream bug... -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1186944] Recent kernel builds interfere with amdgpu power management on certain hardware
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1186944 https://bugzilla.suse.com/show_bug.cgi?id=1186944#c10 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |jslaby(a)suse.com Resolution|--- |UPSTREAM --- Comment #10 from Jiri Slaby <jslaby(a)suse.com> --- I'm afraid there is a little we can do about this, provided this is an upstream bug and noone in upstream cared to fix this quite yet. Sorry. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1183210] Rebooting instead of shutdown
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1183210 https://bugzilla.suse.com/show_bug.cgi?id=1183210#c2 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |jslaby(a)suse.com Resolution|--- |NORESPONSE --- Comment #2 from Jiri Slaby <jslaby(a)suse.com> --- Feel free to reopen when providing the requested info. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1186122] VM_L2_PROTECTION_FAULT_STATUS:0x00741051 and other errors related to AMDGPU
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1186122 https://bugzilla.suse.com/show_bug.cgi?id=1186122#c5 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |jslaby(a)suse.com Resolution|--- |UPSTREAM --- Comment #5 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Stuart Rogers from comment #4) > It is https://gitlab.freedesktop.org/drm/amd/-/issues/1609 Clearly an upstream (and yet not completely fixed) bug. We can do a little about that, sorry. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1186368] nouveau: BUG: kernel NULL pointer dereference in nouveau_bo_sync_for_device
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1186368 https://bugzilla.suse.com/show_bug.cgi?id=1186368#c2 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |jslaby(a)suse.com Resolution|--- |UPSTREAM --- Comment #2 from Jiri Slaby <jslaby(a)suse.com> --- Even if this still happens, this is rather an upstream bug. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1185864] setting selinux label works on read only btrfs subvolumes
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1185864 https://bugzilla.suse.com/show_bug.cgi?id=1185864#c4 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |fdmanana(a)suse.com --- Comment #4 from Jiri Slaby <jslaby(a)suse.com> --- Maybe btrfs fellow know? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1183825] When in graphical environment on RPI3, system goes down at when screen goes into powersave
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1183825 https://bugzilla.suse.com/show_bug.cgi?id=1183825#c6 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |jslaby(a)suse.com Resolution|--- |FIXED --- Comment #6 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Ivan Ivanov from comment #5) > Probably deserves its own bug? Yes, if it still happens. Re the original bug. IF it still persists, please reopen. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1132456] Raspberry Pi 3B console video fails using DSI interface
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1132456 https://bugzilla.suse.com/show_bug.cgi?id=1132456#c12 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED CC| |jslaby(a)suse.com Resolution|--- |FIXED --- Comment #12 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Guillaume GARDET from comment #11) > (In reply to Andreas F�rber from comment #9) > > I wonder whether this unfinished -dt submission might be related? > > https://build.opensuse.org/request/show/684245 > > It is now in Factory. Is this bug still occurring? Hopefully? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207243] kernel 6.1.4 fails to boot: nvme0n1: No UUID available providing old NGUID
by bugzilla_noreply＠suse.com 23 Jan '23

23 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207243 http://bugzilla.opensuse.org/show_bug.cgi?id=1207243#c14 --- Comment #14 from Chris Puttick <chris(a)twoten.is> --- Rescue/maintenance/failsafe, whatever the menu item is named this year. Have just run zypper dup and got kernel 6.1.7 with the same outcome. 6.0.12 still boots as expected. I can't easily see log entries pertaining to the failed boots. journalctl only seems to have log entries for the current boot stored. /var/log/messages logs the shutdown before the restart but nothing else until the known good boot following the failed boot. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207355] Battery drain despite shutdown...
by bugzilla_noreply＠suse.com 22 Jan '23

22 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1207355 https://bugzilla.suse.com/show_bug.cgi?id=1207355#c6 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |millstonepoet(a)gmail.com Flags| |needinfo?(millstonepoet@gma | |il.com) --- Comment #6 from Takashi Iwai <tiwai(a)suse.com> --- Just to be sure: you've tested 6.0.12 kernel and it showed the same problem as 6.1.x, right? If so, the regression appears to be between 5.19.x and 6.0.x. In anyway, it'd be helpful to give the journal output of the working (5.19.x) and non-working (6.x) cases (from boot to shutdown) for comparison. I don't expect much, but we might see some traces there. Also, please give the hwinfo outputs from both working and non-working cases. Upload (attach) the generated files on Bugzilla. Thanks. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207355] Battery drain despite shutdown...
by bugzilla_noreply＠suse.com 21 Jan '23

21 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1207355 https://bugzilla.suse.com/show_bug.cgi?id=1207355#c5 --- Comment #5 from P Gillespie <millstonepoet(a)gmail.com> --- System: Host: neugerig Kernel: 5.19.12-1.g95fa5b8-default arch: x86_64 bits: 64 Desktop: GNOME v: 43.2 Distro: openSUSE Tumbleweed 20230119 Have been testing all afternoon with restarts, some immediate, some after normal usage, and haven't been able to reproduce the bug. Using 6.x, when first shutting down to reboot into the older kernel, the bug prevented a normal shutdown. That argues, to me, that if this weren't a kernel issue I would have bumped into it by now, using 5.19, but I'll continue using the older kernel over the week-end and report back if anything changes. Thank you so much for the instructions. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207355] Battery drain despite shutdown...
by bugzilla_noreply＠suse.com 21 Jan '23

21 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1207355 https://bugzilla.suse.com/show_bug.cgi?id=1207355#c4 --- Comment #4 from P Gillespie <millstonepoet(a)gmail.com> --- (In reply to Takashi Iwai from comment #3) > (In reply to P Gillespie from comment #2) > > (In reply to Takashi Iwai from comment #1) > > > Could you verify whether the problem persists with the old kernel found in > > > TW history repo, too? > > > http://download.opensuse.org/history/ > > > At least 6.1.0 is found there. > > > > > > For older version, you can find my OBS repos home:tiwai:kernel:6.0, > > > home:tiwai:kernel:5.19, ... Note that those contain the unofficial builds, > > > hence it won't boot with Secure Boot (without manual hacks). > > > > Thanks. The problem has been going on since 6.1.0, so I'm apt to test with > > 5.x. Still somewhat new to Opensuse however. Rolling back to an earlier > > Kernel on Ubuntu? That I know how to do, but I haven't done this on > > Opensuse. Can you recommend a link or provide brief instructions? > > You can install multiple kernel versions at the same time on openSUSE system. > > But, first off, verify whether you're using Secure Boot or not. If yes, > you'd need to disable Secure Boot on BIOS at first. The way depends on the > machine. > > Then, as a preparation, increase the number of multiple installable kernels > by editing /etc/zypp/zypp.conf as root. Add more entries to the line > multiversion.kernels, e.g. > multiversion.kernels = latest,latest-1,latest-2,latest-3,running > > Now, go to the download URL. Choose x86_64 instead of i686. e.g. for 6.0, > from > > http://download.opensuse.org/repositories/home:/tiwai:/kernel:/6.0/standard/ > x86_64/ > and download kernel-default-6.0.*.rpm file from there. > > Install it via zypper, > % zypper in --oldpackage kernel-default-6.0.*.rpm > > You'll be asked for the signature, but you can ignore it and continue. > After installing, reboot, choose the kernel on GRUB menu, and retest. > > If the kernel isn't needed any longer, uninstall it > % zypper rm kernel-default-6.0.12 > > > I found the following at your site: > > > > https://mirrorcache-us.opensuse.org/repositories/home:/tiwai:/kernel:/5.19/ > > standard/i686/ > > > > And: kernel-vanilla-5.19.12-1.1.g95fa5b8.i686.rpm > > > > Is it simply a matter of downloading and zyppering in the RPM? Will the > > option to boot with 5.19 be configured in grub? > > The i686 is a wrong one, that's for 32bit. > > > Lastly, for what it's worth, I posted this on Reddit and another user, also > > with an MS Go, reported the same issue. > > We'd need to report this to the upstream in the end, but at first we need to > figure out whether a regression and the exact regression range if so. Thank you. There's no Secure Boot. My listing the 686 Kernel was me being daft. I'll test this this afternoon or evening. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207347] New: Webcam not working in Lenovo T14 gen 1
by bugzilla_noreply＠suse.com 21 Jan '23

21 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207347 Bug ID: 1207347 Summary: Webcam not working in Lenovo T14 gen 1 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: paolabonacini(a)virgilio.it QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi! The webcam of my Lenovo T14 gen 1 is not working. The problem is the same as in https://bugzilla.opensuse.org/show_bug.cgi?id=1189207 and the laptop is the same. A few days ago I had the same problem in endeavouros (I just reinstalled opensuse tumbleweed) and solved it by using the package https://aur.archlinux.org/packages/upd72020x-fw. Here on tumbleweed I solved it (but it should be just a temporary solution) by downloading the firmware from https://github.com/Ntemis/renesas-fw, going to https://github.com/markusj/upd72020x-load, and compiling the code. I placed the firmware file in the same folder upd72020x-load bin is compiled and renamed it to K2026.mem. After doing sudo ./upd72020x-check-and-init, the webcam immediately worked. I don't if it is relevant, but the bios version is 1.35. Thank you very much Paola -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 1207355] Battery drain despite shutdown...
by bugzilla_noreply＠suse.com 21 Jan '23

21 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1207355 https://bugzilla.suse.com/show_bug.cgi?id=1207355#c3 --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to P Gillespie from comment #2) > (In reply to Takashi Iwai from comment #1) > > Could you verify whether the problem persists with the old kernel found in > > TW history repo, too? > > http://download.opensuse.org/history/ > > At least 6.1.0 is found there. > > > > For older version, you can find my OBS repos home:tiwai:kernel:6.0, > > home:tiwai:kernel:5.19, ... Note that those contain the unofficial builds, > > hence it won't boot with Secure Boot (without manual hacks). > > Thanks. The problem has been going on since 6.1.0, so I'm apt to test with > 5.x. Still somewhat new to Opensuse however. Rolling back to an earlier > Kernel on Ubuntu? That I know how to do, but I haven't done this on > Opensuse. Can you recommend a link or provide brief instructions? You can install multiple kernel versions at the same time on openSUSE system. But, first off, verify whether you're using Secure Boot or not. If yes, you'd need to disable Secure Boot on BIOS at first. The way depends on the machine. Then, as a preparation, increase the number of multiple installable kernels by editing /etc/zypp/zypp.conf as root. Add more entries to the line multiversion.kernels, e.g. multiversion.kernels = latest,latest-1,latest-2,latest-3,running Now, go to the download URL. Choose x86_64 instead of i686. e.g. for 6.0, from http://download.opensuse.org/repositories/home:/tiwai:/kernel:/6.0/standard… and download kernel-default-6.0.*.rpm file from there. Install it via zypper, % zypper in --oldpackage kernel-default-6.0.*.rpm You'll be asked for the signature, but you can ignore it and continue. After installing, reboot, choose the kernel on GRUB menu, and retest. If the kernel isn't needed any longer, uninstall it % zypper rm kernel-default-6.0.12 > I found the following at your site: > > https://mirrorcache-us.opensuse.org/repositories/home:/tiwai:/kernel:/5.19/ > standard/i686/ > > And: kernel-vanilla-5.19.12-1.1.g95fa5b8.i686.rpm > > Is it simply a matter of downloading and zyppering in the RPM? Will the > option to boot with 5.19 be configured in grub? The i686 is a wrong one, that's for 32bit. > Lastly, for what it's worth, I posted this on Reddit and another user, also > with an MS Go, reported the same issue. We'd need to report this to the upstream in the end, but at first we need to figure out whether a regression and the exact regression range if so. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207349] OpenSuse Leap 15.5 alpha
by bugzilla_noreply＠suse.com 20 Jan '23

20 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207349 http://bugzilla.opensuse.org/show_bug.cgi?id=1207349#c1 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |uwe.luedecke(a)t-online.de Component|Packages |Kernel Version|SLE-15-SP4 |Leap 15.5 Assignee|packagehub-bugs(a)suse.com |kernel-bugs(a)opensuse.org Product|openSUSE Backports |openSUSE Distribution QA Contact|packagehub-bugs(a)suse.com |qa-bugs(a)suse.de Flags| |needinfo?(uwe.luedecke@t-on | |line.de) --- Comment #1 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- (In reply to uwe Luedecke from comment #0) > Unfortunately I have to report again because of the same syptom. What is this referring to? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207355] Battery drain despite shutdown...
by bugzilla_noreply＠suse.com 20 Jan '23

20 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1207355 https://bugzilla.suse.com/show_bug.cgi?id=1207355#c2 --- Comment #2 from P Gillespie <millstonepoet(a)gmail.com> --- (In reply to Takashi Iwai from comment #1) > Could you verify whether the problem persists with the old kernel found in > TW history repo, too? > http://download.opensuse.org/history/ > At least 6.1.0 is found there. > > For older version, you can find my OBS repos home:tiwai:kernel:6.0, > home:tiwai:kernel:5.19, ... Note that those contain the unofficial builds, > hence it won't boot with Secure Boot (without manual hacks). Thanks. The problem has been going on since 6.1.0, so I'm apt to test with 5.x. Still somewhat new to Opensuse however. Rolling back to an earlier Kernel on Ubuntu? That I know how to do, but I haven't done this on Opensuse. Can you recommend a link or provide brief instructions? I found the following at your site: https://mirrorcache-us.opensuse.org/repositories/home:/tiwai:/kernel:/5.19/… And: kernel-vanilla-5.19.12-1.1.g95fa5b8.i686.rpm Is it simply a matter of downloading and zyppering in the RPM? Will the option to boot with 5.19 be configured in grub? Lastly, for what it's worth, I posted this on Reddit and another user, also with an MS Go, reported the same issue. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207355] Battery drain despite shutdown...
by bugzilla_noreply＠suse.com 20 Jan '23

20 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1207355 https://bugzilla.suse.com/show_bug.cgi?id=1207355#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Could you verify whether the problem persists with the old kernel found in TW history repo, too? http://download.opensuse.org/history/ At least 6.1.0 is found there. For older version, you can find my OBS repos home:tiwai:kernel:6.0, home:tiwai:kernel:5.19, ... Note that those contain the unofficial builds, hence it won't boot with Secure Boot (without manual hacks). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207347] Webcam not working in Lenovo T14 gen 1
by bugzilla_noreply＠suse.com 20 Jan '23

20 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1207347 https://bugzilla.suse.com/show_bug.cgi?id=1207347#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |paolabonacini(a)virgilio.it, | |tiwai(a)suse.com Flags| |needinfo?(paolabonacini@vir | |gilio.it) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Either something got changed and broke, or your model has no accessible ROM by some reason... Could you give the dmesg output, as well as the hwinfo output? At best both working and non-working cases. Attach (don't paste) the output files on Bugzilla. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205624] qemu fails in test on openSUSE:Step:15-SP5 armv7
by bugzilla_noreply＠suse.com 20 Jan '23

20 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1205624 https://bugzilla.suse.com/show_bug.cgi?id=1205624#c12 --- Comment #12 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- Dirk added a workaround to move forward with Leap 15.5 armv7 (thanks!): https://build.opensuse.org/package/rdiff/openSUSE:Step:15-SP5/qemu?linkrev=… But what is the current status of the underlying bug? It seems to stall. -- You are receiving this mail because: You are the assignee for the bug.

1 0