October 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1231825] Kernel 6.11.4 bluetooth scan stops working
by bugzilla_noreply＠suse.com 21 Oct '24

21 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231825 https://bugzilla.suse.com/show_bug.cgi?id=1231825#c1 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(novell@tower-net. | |de) CC| |novell(a)tower-net.de --- Comment #1 from Jiri Slaby <jslaby(a)suse.com> --- 6.11.4 contains: 98ccd44002d8 Bluetooth: hci_conn: Fix UAF in hci_enhanced_setup_sync e63125eec47d Bluetooth: btusb: Don't fail external suspend requests 4cb9807c9b53 Bluetooth: RFCOMM: FIX possible deadlock in rfcomm_sk_state_change I've committed to stable few moments ago: 4084286151fc Bluetooth: btusb: Fix not being able to reconnect after suspend 2c1dda2acc41 Bluetooth: btusb: Fix regression with fake CSR controllers 0a12:0001 which is supposed to fix one of the above. So could you recheck :Backport once it builds? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231832] [Build 20241020] openQA test fails in podman_netavark
by bugzilla_noreply＠suse.com 21 Oct '24

21 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231832 https://bugzilla.suse.com/show_bug.cgi?id=1231832#c1 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |jslaby(a)suse.com Resolution|--- |FIXED --- Comment #1 from Jiri Slaby <jslaby(a)suse.com> --- Pushed: https://lore.kernel.org/all/20241019-xtables-typos-v3-1-66dd2eaacf2f@0upti.… into stable. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231813] New: [riscv64][Unmatched][regression] Hard lockup on reboot/poweroff with 6.11
by bugzilla_noreply＠suse.com 19 Oct '24

19 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231813 Bug ID: 1231813 Summary: [riscv64][Unmatched][regression] Hard lockup on reboot/poweroff with 6.11 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: RISC-V OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: afaerber(a)suse.com QA Contact: qa-bugs(a)suse.de CC: ddavis(a)suse.com, jeffm(a)suse.com, schwab(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Reboot or poweroff on HiFive Unmatched board is no longer working at 20241016/17 (was working with 20240828; its 6.10.5 kernel with 20241017 does not help) and runs into a hard CPU lockup kernel panic: [ 56.329837][ T1379] sifive-serial 10010000.serial: BREAK detection not supported [ 57.664396][ T1] reboot: Power down [ 72.030230][ C3] watchdog: Watchdog detected hard LOCKUP on cpu 0 [ 96.026864][ C2] watchdog: Watchdog detected hard LOCKUP on cpu 3 [ 96.026873][ C2] Modules linked in: af_packet rfkill nf_tables libcrc32c snd_hda_codec_hdmi snd_hda_intel mscc snd_intel_dspcfg macsec snd_hda_codec nls_iso8859_1 nls_cp437 snd_hda_core vfat macb fat snd_hwdep phylink snd_pcm ofpart of_mdio snd_timer fixed_phy fwnode_mdio libphy snd spi_nor ptp at24 soundcore da9063_onkey pps_core mtd uio_pdrv_genirq uio fuse dm_mod nvme_fabrics nvme_keyring loop efi_pstore configfs nfnetlink dmi_sysfs ip_tables x_tables ext4 mbcache jbd2 xe hid_apple hid_generic usbhid apple_mfi_fastcharge xhci_pci mmc_block xhci_pci_renesas xhci_hcd drm_ttm_helper ttm i2c_algo_bit gpu_sched drm_buddy video drm_suballoc_helper drm_gpuvm mmc_spi crc_itu_t crc7 drm_exec of_mmc_spi usbcore drm_display_helper mmc_core rtc_da9063 da9063_regulator nvme cec lm90 da9063 mfd_core regmap_i2c rc_core nvme_core usb_common nvme_auth i2c_ocores pwm_sifive spi_sifive efivarfs [ 96.027165][ C2] Kernel panic - not syncing: Hard LOCKUP [ 96.027178][ C2] CPU: 2 UID: 0 PID: 0 Comm: swapper/2 Tainted: G U 6.11.3-1-default #1 openSUSE Tumbleweed 1400000003000000474e55005c3864d57907faa4 [ 96.027195][ C2] Tainted: [U]=USER [ 96.027198][ C2] Hardware name: sifive SiFive HiFive Unmatched A00/SiFive HiFive Unmatched A00, BIOS 2024.10 10/01/2024 [ 96.027204][ C2] Call Trace: [ 96.027211][ C2] [<ffffffff80006b4a>] dump_backtrace+0x1c/0x24 [ 96.027236][ C2] [<ffffffff80a00178>] show_stack+0x2c/0x38 [ 96.027251][ C2] [<ffffffff80a0cd7c>] dump_stack_lvl+0x50/0x72 [ 96.027270][ C2] [<ffffffff80a0cdb2>] dump_stack+0x14/0x1c [ 96.027279][ C2] [<ffffffff80a00410>] panic+0x106/0x312 [ 96.027288][ C2] [<ffffffff80022c0a>] add_taint+0x0/0x8c [ 96.027302][ C2] [<ffffffff80123204>] watchdog_hardlockup_check+0x170/0x1b4 [ 96.027322][ C2] [<ffffffff80123ca8>] watchdog_buddy_check_hardlockup+0x4c/0x5c [ 96.027334][ C2] [<ffffffff80122e98>] watchdog_timer_fn+0x70/0x238 [ 96.027344][ C2] [<ffffffff800d0540>] __hrtimer_run_queues+0xfe/0x240 [ 96.027364][ C2] [<ffffffff800d133a>] hrtimer_interrupt+0xca/0x1d6 [ 96.027374][ C2] [<ffffffff807b5e58>] riscv_timer_interrupt+0x3a/0x52 [ 96.027387][ C2] [<ffffffff800a1e0a>] handle_percpu_devid_irq+0x8a/0x1c0 [ 96.027403][ C2] [<ffffffff8009c6b0>] generic_handle_domain_irq+0x1c/0x2a [ 96.027423][ C2] [<ffffffff8055d908>] riscv_intc_irq+0x26/0x60 [ 96.027441][ C2] [<ffffffff80a0ce20>] handle_riscv_irq+0x4c/0x76 [ 96.027451][ C2] [<ffffffff80a1b106>] call_on_irq_stack+0x32/0x40 [ 96.788253][ C2] SMP: failed to stop secondary CPUs 0,2-3 [ 96.788264][ C2] Kernel Offset: 0x0 from 0xffffffff80000000 After some minutes it then reboots (also for poweroff). I've manually updated the two U-Boot partitions to latest Factory 2024.10, to no improvement. The taint is from xe.force_probe (bug #1231756); happens without as well. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1196835] [riscv64][Unmatched] CPU#0 stuck forever while trying to reboot the board.
by bugzilla_noreply＠suse.com 19 Oct '24

19 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1196835 Andreas Färber <afaerber(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.opensuse.o | |rg/show_bug.cgi?id=1231813 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1229020] Zypper dup installed kernels which reboot immediately
by bugzilla_noreply＠suse.com 19 Oct '24

19 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1229020 https://bugzilla.suse.com/show_bug.cgi?id=1229020#c10 Louis Erickson <wwonko(a)rdwarf.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(wwonko(a)rdwarf.com | |) | --- Comment #10 from Louis Erickson <wwonko(a)rdwarf.com> --- Created attachment 878105 --> https://bugzilla.suse.com/attachment.cgi?id=878105&action=edit Screenshot before reboot. Sorry about the delay. Travel and a case of COVID slowed me down. Back in the saddle now, and getting you that screenshot with quiet and splash disabled. The boot pauses here for a bit, then cold boots itself. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1227144] iwlwifi 0000:6f:00.0: Microcode SW error detected. Restarting 0x0.
by bugzilla_noreply＠suse.com 18 Oct '24

18 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1227144 https://bugzilla.suse.com/show_bug.cgi?id=1227144#c15 --- Comment #15 from Takashi Iwai <tiwai(a)suse.com> --- Then retest with the latest upstream kernel in OBS Kernel:stable:Backport repo again and see whether the issue appears with it or not. Honestly speaking, there is little thing we can do from the distro side for such a bug unless it's addressed in the upstream; it's a device-specific, mostly a firmware-related bug. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1227144] iwlwifi 0000:6f:00.0: Microcode SW error detected. Restarting 0x0.
by bugzilla_noreply＠suse.com 18 Oct '24

18 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1227144 https://bugzilla.suse.com/show_bug.cgi?id=1227144#c14 --- Comment #14 from Andreas <opendreas(a)gmail.com> --- Created attachment 878078 --> https://bugzilla.suse.com/attachment.cgi?id=878078&action=edit dmesg-6.4.0-150600.23.25-2 the errors started appearing again. Here is the log when the laptop came out of standby and, while watching YouTube, wifi began to reconnect. Now the laptop is frozen, I turned it off and on, after starting Firefox (Flatpak) from Youtube, the wifi starts to reconnect again. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189456] Add ashmem and binder drivers
by bugzilla_noreply＠suse.com 18 Oct '24

18 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1189456 https://bugzilla.suse.com/show_bug.cgi?id=1189456#c14 --- Comment #14 from Takashi Iwai <tiwai(a)suse.com> --- Not yet. Rust for Linux requires CONFIG_MODVERSION to be disabled, but it's a mandatory feature for (open)SUSE kernels, hence R4L can't be enabled. Once after it's addressed in the upstream, we might consider enabling Rust for Linux for Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 0

[Bug 1189456] Add ashmem and binder drivers
by bugzilla_noreply＠suse.com 17 Oct '24

17 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1189456 https://bugzilla.suse.com/show_bug.cgi?id=1189456#c13 llyyr <llyyr.public(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |llyyr.public(a)gmail.com --- Comment #13 from llyyr <llyyr.public(a)gmail.com> --- ashmem is not required anymore, since memfd exists now. And there's ongoing effort on a rust_binder driver to replace the old insecure binder driver. Will TW enable the rust_binder driver in the default kernel? -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.

1 0

[Bug 1229999] High idle power usage on Lenovo Slim 7 16" AMD
by bugzilla_noreply＠suse.com 17 Oct '24

17 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1229999 https://bugzilla.suse.com/show_bug.cgi?id=1229999#c11 --- Comment #11 from varval761 <variable_valuables761(a)simplelogin.com> --- I tested a few other distros, including Kubuntu and previous versions of Fedora and Tumbleweed, and they all had similar minimum idle power draw as the latest Tumbleweed/Krypton (25W+). So it seems so far that only recent Fedora versions have lower power draw (~14W). Does this maybe have any relevant info? https://fedoraproject.org/wiki/Changes/TunedAsTheDefaultPowerProfileManagem… (Fedora had less power draw even when replacing tuned with p-p-d or tlp though, in my previously mentioned tests) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231465] Kernel 6.11.2-1 only a fraction of ram is available
by bugzilla_noreply＠suse.com 17 Oct '24

17 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231465 https://bugzilla.suse.com/show_bug.cgi?id=1231465#c33 --- Comment #33 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Jiri Slaby from comment #32) > (In reply to Felix Niederwanger from comment #31) > > I forgot the KASAN sequence: > > > > > (poweroff) > > > 6.11.3-5-KASAN: error > > > 6.11.3-5-KASAN: error > > > 6.11.3-5-KASAN: error > > > > This kernel fails to boot from cold. FWIW I enabled kasan in my kernel, so that it contains both the workaround and KASAN: home:jirislaby:kernel-bsc1231465 It might be worth trying too. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231465] Kernel 6.11.2-1 only a fraction of ram is available
by bugzilla_noreply＠suse.com 17 Oct '24

17 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231465 https://bugzilla.suse.com/show_bug.cgi?id=1231465#c32 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(felix.niederwange | |r(a)suse.com) --- Comment #32 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Felix Niederwanger from comment #31) > I forgot the KASAN sequence: > > > (poweroff) > > 6.11.3-5-KASAN: error > > 6.11.3-5-KASAN: error > > 6.11.3-5-KASAN: error > > This kernel fails to boot from cold. It might die well due to the bug. Or not. Did you boot with "quiet" in cmdline? Can you see any messages if not? Or any chance it managed to store the kernel messages into the journal? Or would it be possible to boot with init=/bin/bash and look into the dmesg directly (I am not sure if it's not too late -- perhaps boot with rd.break, but that might be too late too)? But you at least confirmed 6.11.0 is ok and 6.11.2 is not. What about 6.12? And I've just pushed 6.11.4 -- still the same? Sorry, but I am not clever from this bug at all. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1225352] [Build 13.199] openQA test fails in prepare_firstboot: RPi3 not booting?
by bugzilla_noreply＠suse.com 17 Oct '24

17 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c48 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #48 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Guillaume GARDET from comment #47) > (In reply to Patrik Jakobsson from comment #46) > > Why is the test still failing? Shouldn't QA have the fix by now? > > There is a regression, since the test passed 9 days ago: > https://openqa.opensuse.org/tests/4543603 Also affecting 15.5 and 15.6 again. Can you check the serial log? Maybe it's the same cause again, maybe something else. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231465] Kernel 6.11.2-1 only a fraction of ram is available
by bugzilla_noreply＠suse.com 17 Oct '24

17 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231465 https://bugzilla.suse.com/show_bug.cgi?id=1231465#c29 --- Comment #29 from Vlastimil Babka <vbabka(a)suse.com> --- Some parts of the following comment don't match the current theory for me. Is it because of imprecise wording or is something else happening? (In reply to Felix Niederwanger from comment #12) > Another observation: kernel 6.12.0-rc2-3.g4f5e31e-default only works on the > first boot. This part is ok. > When the machine is powered down, then also with this kernel the > machine only detects 1.3 GiB of memory. "powered down" would mean another cold boot? That wouldn't match the theory. If there was "rebooted", it would. > I powered the machine on this morning with the same kernel as Friday > (6.12.0-rc2-3.g4f5e31e) and run into the OOM issues. Running into the OOM issue immediately on cold boot doesn't match the theory? > I rolled back to the > 6.11.0-1 kernel and everything was fine. Then I re-installed the current > kernel:HEAD (now 6.12.0-rc3-1gefb99), rebooted and the system was running > fine with 32 GiB. This means here 6.11.0 would not corrupt EFI memory if a reboot from that to 6.12.0 was fine? > Then I powered off the laptop and the same kernel then > detected only 1.3 GiB of memory. I rebooted 3 times with this kernel, always > 1.3 GiB. Again if it's "powered off" the first boot should have been ok? > I used then an older snapshot with the 6.11.0-1 kernel and everything was > fine again (32 GiB memory). From there rebooting into the 6.12.0-rc3 kernel > only shows again 1.3 GiB of memory. But here it seems 6.11.0 is corrupting the EFI memory, so it's a different result than above? Maybe the corruption is not completely deterministic? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231465] Kernel 6.11.2-1 only a fraction of ram is available
by bugzilla_noreply＠suse.com 17 Oct '24

17 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231465 https://bugzilla.suse.com/show_bug.cgi?id=1231465#c28 --- Comment #28 from Vlastimil Babka <vbabka(a)suse.com> --- (In reply to Felix Niederwanger from comment #12) > I used then an older snapshot with the 6.11.0-1 kernel and everything was > fine again (32 GiB memory). From there rebooting into the 6.12.0-rc3 kernel > only shows again 1.3 GiB of memory. This suggests 6.11.0 itself already was corrupting the EFI memory? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231465] Kernel 6.11.2-1 only a fraction of ram is available
by bugzilla_noreply＠suse.com 17 Oct '24

17 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231465 https://bugzilla.suse.com/show_bug.cgi?id=1231465#c27 --- Comment #27 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Jiri Slaby from comment #26) > (In reply to Felix Niederwanger from comment #20) > > To cross-check I needed 2 reboot attempts with the 6.11.2 kernel to end up > > with only 1.3 GiB. > > Side note: you have to boot each tested kernel twice to actually *see* the > behavior. The first boot corrupts the EFI memory, the second one loads the > memory. And cold-boot/shutdown in between to reset to the original BIOS/EFI state. > Having that in mind, you still confirm 6.12 is fine, 6.11 is fine, but > 6.11.2 is not? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231465] Kernel 6.11.2-1 only a fraction of ram is available
by bugzilla_noreply＠suse.com 17 Oct '24

17 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231465 https://bugzilla.suse.com/show_bug.cgi?id=1231465#c26 --- Comment #26 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Felix Niederwanger from comment #20) > To cross-check I needed 2 reboot attempts with the 6.11.2 kernel to end up > with only 1.3 GiB. Side note: you have to boot each tested kernel twice to actually *see* the behavior. The first boot corrupts the EFI memory, the second one loads the memory. Having that in mind, you still confirm 6.12 is fine, 6.11 is fine, but 6.11.2 is not? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231465] Kernel 6.11.2-1 only a fraction of ram is available
by bugzilla_noreply＠suse.com 17 Oct '24

17 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231465 https://bugzilla.suse.com/show_bug.cgi?id=1231465#c25 --- Comment #25 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Jiri Slaby from comment #24) > Out of curiosity, could you boot several times: > https://github.com/jirislaby/collected_sources/tree/master/efi-dump-memattr As per PM, it output 6 times the same. I believe something corrupts the EFI memory. And it remains until cold booted. Given it is corrupted some later (the first boot is fine at this point), it might help to give KASAN a try. Could you try that: https://download.opensuse.org/repositories/home:/tiwai:/kernel:/stable-kasa… ? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231465] Kernel 6.11.2-1 only a fraction of ram is available
by bugzilla_noreply＠suse.com 17 Oct '24

17 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231465 https://bugzilla.suse.com/show_bug.cgi?id=1231465#c24 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(felix.niederwange | |r(a)suse.com) --- Comment #24 from Jiri Slaby <jslaby(a)suse.com> --- Out of curiosity, could you boot several times: https://github.com/jirislaby/collected_sources/tree/master/efi-dump-memattr prebuilt here: https://decibel.fi.muni.cz/~xslaby/n/myefi.efi (Put it to /boot/efi/EFI/boot/ and persuade bios to boot it.) To see if kernel (mapping) is at fault. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231465] Kernel 6.11.2-1 only a fraction of ram is available
by bugzilla_noreply＠suse.com 17 Oct '24

17 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231465 https://bugzilla.suse.com/show_bug.cgi?id=1231465#c23 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(felix.niederwange | |r(a)suse.com) | --- Comment #23 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Felix Niederwanger from comment #20) > I tried it now 8 times with the provided 6.11.3-4-default kernel from > https://build.opensuse.org/project/monitor/home:jirislaby:kernel-bsc1231465, > all times the system recognized 32 GiB of system memory. > > To cross-check I needed 2 reboot attempts with the 6.11.2 kernel to end up > with only 1.3 GiB. > > Did something else changed in the meantime, that would explain this? As I wrote, with my patch, it no longer wraps. So it should not eat all your ram. It eats now only: 0x0000000077535018-0x00000001429e9027 This is funny: > 08:30:26 ... efi: memattr: efi_memattr_init: tab=0x77526018 size=16+45*48=0x0000000000000880 > 08:47:54 ... efi: memattr: efi_memattr_init: tab=0x77535018 size=16+2*1705353216=0x00000000cb4b4010 > 08:51:23 ... efi: memattr: efi_memattr_init: tab=0x77535018 size=16+2*1705353216=0x00000000cb4b4010 > 08:56:03 ... efi: memattr: efi_memattr_init: tab=0x77535018 size=16+2*1705353216=0x00000000cb4b4010 > 08:59:48 ... efi: memattr: efi_memattr_init: tab=0x77535018 size=16+2*1705353216=0x00000000cb4b4010 With the first boot, your bios reported 45 tables (looks reasonable) of size 48 (this is correct). Subsequent boots of the kernel, the firmware got mad and reports 2 tables (wrong) of size 1705353216 (wrong!). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1225352] [Build 13.199] openQA test fails in prepare_firstboot: RPi3 not booting?
by bugzilla_noreply＠suse.com 17 Oct '24

17 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c47 --- Comment #47 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- (In reply to Patrik Jakobsson from comment #46) > Why is the test still failing? Shouldn't QA have the fix by now? There is a regression, since the test passed 9 days ago: https://openqa.opensuse.org/tests/4543603 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1230849] systemd[1]: bpf-restrict-fs: Failed to load BPF object: No such process
by bugzilla_noreply＠suse.com 17 Oct '24

17 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230849 Shung-Hsi Yu <shung-hsi.yu(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(shung-hsi.yu@suse | |.com) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1212696] Q965 with modesetting DIX GPU HANG
by bugzilla_noreply＠suse.com 16 Oct '24

16 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1212696 https://bugzilla.suse.com/show_bug.cgi?id=1212696#c26 Felix Miata <mrmazda(a)earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|Leap 15.5 |Leap 15.6 --- Comment #26 from Felix Miata <mrmazda(a)earthlink.net> --- In upstream report I commented again. Interestingly, 6.10.11 in TW is fine, while 6.10.11 in Debian Trixie is not, like 15.5 and 15.6. Thus, the problem might not be purely, or at all, upstream. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1225352] [Build 13.199] openQA test fails in prepare_firstboot: RPi3 not booting?
by bugzilla_noreply＠suse.com 16 Oct '24

16 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c46 --- Comment #46 from Patrik Jakobsson <patrik.jakobsson(a)suse.com> --- Why is the test still failing? Shouldn't QA have the fix by now? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231268] New: [Build 20241001] openQA test fails in cve-2017-17806
by bugzilla_noreply＠suse.com 16 Oct '24

16 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231268 Bug ID: 1231268 Summary: [Build 20241001] openQA test fails in cve-2017-17806 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/4526310/modules/cve- 2017-17806/steps/8 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: avinesh.kumar(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-ltp_cve_kotd@64bit fails in [cve-2017-17806](https://openqa.opensuse.org/tests/4526310/modules/cve-2017-… ltp test: https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/cryp… /* * Regression test for commit af3ff8045bbf ("crypto: hmac - require that the * underlying hash algorithm is unkeyed"), or CVE-2017-17806. This test * verifies that the hmac template cannot be nested inside itself. */ ## Reproducible Fails since Build [20241001](https://openqa.opensuse.org/tests/4526310) (openSUSE Tumbleweed 20241001 - Kernel 6.12.0-rc1-1.gfcf4d55-default) ## Expected result Last good: [20240930](https://openqa.opensuse.org/tests/4523252) (openSUSE Tumbleweed 20240930 - Kernel 6.11.0-3.g746ccde-default) ## 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