January 2025 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1234668] Kernel compilation with DRBD support fails with kernel-source-6.4.0-150600.23.30.1
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234668 https://bugzilla.suse.com/show_bug.cgi?id=1234668#c1 Lee Duncan <lduncan(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)suse.de |lduncan(a)suse.com Status|NEW |CONFIRMED --- Comment #1 from Lee Duncan <lduncan(a)suse.com> --- The patch in question is: > patches.suse/drdb-Convert-to-use-bdev_open_by_path.patch Which was created by me with SUSE commit 46dad6445708d8d8548937aaec384cdba93d362f, but then updated by Hannes with commit 29ae81af348d583174a9c4bac7e4ac8972e51df1. (In reply to Michael Engert from comment #0) > ... > It could be this patch: > > https://lore.kernel.org/all/20230823104857.11437-1-jack@suse.cz/ The patch referenced is part of a large series of 29 upstream commits, so I'm not sure backporting just one of that series is a good idea. I will check it out. The other possibility is reverting the problematic fix. This compilation error should have been caught when the patch was committed, but the normal builds do not test drbd compilation, even on x86. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1235020] New: Hard freeze workqueue lockup mediatek bluetooth
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1235020 Bug ID: 1235020 Summary: Hard freeze workqueue lockup mediatek bluetooth 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: andrea.ippo(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, I've been experiencing random lockups on TW for a while now (more than a month): https://community.frame.work/t/workqueue-lockup-opensuse-tw/60430 (I'm the OP here) https://forums.opensuse.org/t/workqueue-lockup-should-i-file-a-bug/180387 I had to switch to Fedora for the past couple of weeks, and surprisingly I never experienced this issue there, which makes me think it might be related to the opensuse kernel (or maybe, just bad luck on TW). The problem seems to be related to bluetooth, as we can see by checking at the logs at the timestamp preceding the BUG - lockup entry by X seconds as specified in the error: Examples: https://pastebin.com/79dj1PeX https://pastebin.com/n3m1S8B7 In both cases if we go back by 58s we get around this part: Jan 02 18:19:33 andromeda kernel: Bluetooth: hci0: Execution of wmt command timed out Jan 02 18:19:33 andromeda kernel: Bluetooth: hci0: Failed to send wmt patch dwnld (-110) Jan 02 18:19:33 andromeda kernel: Bluetooth: hci0: Failed to set up firmware (-110) Jan 02 18:19:33 andromeda kernel: Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported. Jan 02 18:19:35 andromeda kernel: Bluetooth: hci0: Failed to read MSFT supported features (-110) Jan 02 18:19:35 andromeda kernel: Bluetooth: hci0: command 0xfd30 tx timeout Jan 02 18:19:35 andromeda kernel: Bluetooth: hci0: AOSP get vendor capabilities (-110) Jan 02 18:19:35 andromeda bluetoothd[1147]: Failed to set mode: Authentication Failed (0x05) When this happens, my entire DE becomes unresponsive, even systemctl reboot won't work and I'm forced to hard power off. I'm running 6.12.6-1-default Thanks -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1234995] libvirt: libvirt: virtimetest failing with the change to year 2025
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234995 https://bugzilla.suse.com/show_bug.cgi?id=1234995#c6 James Fehlig <jfehlig(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ana.guerrero(a)suse.com Flags| |needinfo?(ana.guerrero@suse | |.com) --- Comment #6 from James Fehlig <jfehlig(a)suse.com> --- (In reply to Ana Guerrero from comment #5) > The bug still applies, we should make sure this doesn't happen in one year > again. As you can see from the referenced test code, libvirt has went to quite some extent to avoid the environment bug. IMO, the options are to remove the tests from the SUSE libvirt package, or reassign to the build service to investigate. Which do you prefer? > As mentioned in other comment, the issue consumed a significant amount of > time today. Why was time wasted? Why not simply inform the package maintainer about the build failure and be done with it? And how does a leaf package like libvirt block TW development? I guess I'm failing to understand why this issue was so critical that people unfamiliar with the package had to waste time investigating it. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234781] Intel wifi ax200 issue with kernel 6.12.6
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234781 https://bugzilla.suse.com/show_bug.cgi?id=1234781#c9 --- Comment #9 from Frank Krüger <fkrueger(a)mailbox.org> --- ...or join https://bugzilla.kernel.org/show_bug.cgi?id=219597. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234781] Intel wifi ax200 issue with kernel 6.12.6
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234781 https://bugzilla.suse.com/show_bug.cgi?id=1234781#c8 --- Comment #8 from Frank Krüger <fkrueger(a)mailbox.org> --- This should be reported upstream, since the current patch comes from commit ccdc8fd86fc7b34630bc1ce2da26537219f8b473 Author: Emmanuel Grumbach <emmanuel.grumbach(a)intel.com> Date: Mon Dec 23 14:13:59 2024 +0200 wifi: iwlwifi: be less noisy if the NIC is dead in S3 commit 0572b7715ffd2cac20aac00333706f3094028180 upstream If the NIC is dead upon resume, try to catch the error earlier and exit earlier. We'll print less error messages and get to the same recovery path as before: reload the firmware. Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach(a)intel.com> Signed-off-by: Miri Korenblit <miriam.rachel.korenblit(a)intel.com> Link: https://patch.msgid.link/20241028135215.3a18682261e5.I18f336a4537378a4c1a85… Signed-off-by: Johannes Berg <johannes.berg(a)intel.com> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=219597 Signed-off-by: Sasha Levin <sashal(a)kernel.org> You may use the wifi mailing list at https://marc.info/?l=linux-wireless or https://bugzilla.kernel.org. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234781] Intel wifi ax200 issue with kernel 6.12.6
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234781 https://bugzilla.suse.com/show_bug.cgi?id=1234781#c6 --- Comment #6 from Frank Krüger <fkrueger(a)mailbox.org> --- I am seeing these messages after wakeup from suspend as well, including kernel 6.13.0-rc5. So it's not specific to the current patch. Most importantly, it works without any loss of performance. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234995] libvirt: libvirt: virtimetest failing with the change to year 2025
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234995 https://bugzilla.suse.com/show_bug.cgi?id=1234995#c5 Ana Guerrero <ana.guerrero(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|INVALID |--- Status|RESOLVED |REOPENED --- Comment #5 from Ana Guerrero <ana.guerrero(a)suse.com> --- (In reply to James Fehlig from comment #4) > I was about to revert your temporary fix in Virtualization/libvirt, but see > you've already done that. Thanks! > > I think we can close this bug now. Please reopen if you feel otherwise. > > Happy new year! :-) Hi James, The bug still applies, we should make sure this doesn't happen in one year again. As mentioned in other comment, the issue consumed a significant amount of time today. Happy new year! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234995] libvirt: libvirt: virtimetest failing with the change to year 2025
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234995 https://bugzilla.suse.com/show_bug.cgi?id=1234995#c4 James Fehlig <jfehlig(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #4 from James Fehlig <jfehlig(a)suse.com> --- I was about to revert your temporary fix in Virtualization/libvirt, but see you've already done that. Thanks! I think we can close this bug now. Please reopen if you feel otherwise. Happy new year! :-) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234995] libvirt: libvirt: virtimetest failing with the change to year 2025
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234995 https://bugzilla.suse.com/show_bug.cgi?id=1234995#c3 --- Comment #3 from James Fehlig <jfehlig(a)suse.com> --- (In reply to Ana Guerrero from comment #1) > Created attachment 879378 [details] > libvirt virtimetest 2025 From that log the failing test is [ 176s] 28) Test localtime offset for "VIR11:00VID10:00,1/00:00:00,364/23:59:59" ... FAILED See the following code comment regarding failures of this test (and others) at the turn of the year https://gitlab.com/libvirt/libvirt/-/blob/master/tests/virtimetest.c?ref_ty… There's even an attempt to skip the tests when near the year end. See the isNearYearEnd() function earlier in the file. Apparently that didn't work in the OBS environment running this particular build. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234823] VitrtualBox-VMs refuse to stat after update to kernel 6.12.6-1-default (64-bit) because VirtualBox can't enable the AMD-V extension
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234823 https://bugzilla.suse.com/show_bug.cgi?id=1234823#c5 --- Comment #5 from Jan Engelhardt <jengelh(a)inai.de> --- Tumbleweed will have it with virtualbox-7.1.4-4.1.x86_64.rpm Download servers only have 7.1.4-3.1 currently -- You are receiving this mail because: You are on the CC list for the bug.

1 0