January 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1216575] RPi2 TW images not start into desktop environment
by bugzilla_noreply＠suse.com 23 Jan '24

23 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1216575 https://bugzilla.suse.com/show_bug.cgi?id=1216575#c11 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- QA Contact|gfx-bugs(a)suse.de |qa-bugs(a)suse.de CC| |tiwai(a)suse.com Component|X.Org |Kernel:Drivers Assignee|gfx-bugs(a)suse.de |kernel-bugs(a)suse.de --- Comment #11 from Stefan Dirsch <sndirsch(a)suse.com> --- Did this OpenSource Driver stack ever work on RPi2? I think things didn't improve before RPi4. :-( Reassigning and adding our DRM experts ... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212462] RAID Resync on every reboot with latest mdadm-4.1-150300.24.27.1 update
by bugzilla_noreply＠suse.com 23 Jan '24

23 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1212462 https://bugzilla.suse.com/show_bug.cgi?id=1212462#c6 --- Comment #6 from Björn Voigt <bjoernv(a)arcor.de> --- (In reply to Santiago Zarate from comment #5) > I wonder if this is related also to: > https://bugzilla.suse.com/show_bug.cgi?id=1216381 The symptoms of both issues look similar (initrd mount timeouts, MD devices not ready). A difference is, that this issue here is related to a Gigabyte BIOS RAID5 setup. The issue https://bugzilla.suse.com/show_bug.cgi?id=1216381 looks related to a KVM virtual host setup. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1218948] kernel:[ 3380.214840][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 112s! [kworker/0:2:156]
by bugzilla_noreply＠suse.com 23 Jan '24

23 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1218948 https://bugzilla.suse.com/show_bug.cgi?id=1218948#c35 --- Comment #35 from Takashi Iwai <tiwai(a)suse.com> --- Also, is this a regression by the recent kernel updates? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1218948] kernel:[ 3380.214840][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 112s! [kworker/0:2:156]
by bugzilla_noreply＠suse.com 23 Jan '24

23 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1218948 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(chris@computersal | |at.de) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1218948] kernel:[ 3380.214840][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 112s! [kworker/0:2:156]
by bugzilla_noreply＠suse.com 23 Jan '24

23 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1218948 https://bugzilla.suse.com/show_bug.cgi?id=1218948#c34 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?, | |needinfo?(tiwai(a)suse.com) | --- Comment #34 from Takashi Iwai <tiwai(a)suse.com> --- OK, then the original issue of Christian's machine is completely different from others. The problem for others is about a regression of ax88179 driver (the actual crash), and this was already fixed in SLE15-SP5 git branch. Meanwhile, your problem seems related with i915 graphics driver. The hangup detected by the watchdog might be related with the firmware loading of i915. Could you try to boot with i915.enable_guc=0 boot option and see whether the problem still happens? The kernel warnings might still appear, but the hangup could be avoided by that. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1216575] RPi2 TW images not start into desktop environment
by bugzilla_noreply＠suse.com 23 Jan '24

23 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1216575 https://bugzilla.suse.com/show_bug.cgi?id=1216575#c10 Ivan Ivanov <ivan.ivanov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- QA Contact|qa-bugs(a)suse.de |gfx-bugs(a)suse.de Component|Xfce |X.Org Assignee|bnc-team-xfce(a)forge.provo.n |gfx-bugs(a)suse.de |ovell.com | --- Comment #10 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- Hm, I can't see any errors, display manager reports that it is runing fine, but still nothing on the HDMI output?? # systemctl status display-manager.service ● display-manager.service - X Display Manager Loaded: loaded (/usr/lib/systemd/system/display-manager.service; enabled; preset: enabled) Active: active (running) since Tue 2024-01-23 07:17:18 UTC; 3min 23s ago Process: 2024 ExecStart=/usr/lib/X11/display-manager start (code=exited, status=0/SUCCESS) Main PID: 2032 (lightdm) Tasks: 7 (limit: 1957) CPU: 3.744s CGroup: /system.slice/display-manager.service ├─2032 /usr/sbin/lightdm ├─2039 /usr/bin/Xorg.bin :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch └─2082 lightdm --session-child 13 20 Jan 23 07:17:17 2b11 systemd[1]: Starting X Display Manager... Jan 23 07:17:17 2b11 display-manager[2028]: /etc/vconsole.conf available Jan 23 07:17:17 2b11 display-manager[2028]: XKBLAYOUT: us Jan 23 07:17:17 2b11 display-manager[2028]: XKBLAYOUT is already set. Better don't touch X11 keyboard configuration. Jan 23 07:17:18 2b11 systemd[1]: Started X Display Manager. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1218864] grub2: error messages: 'not a correct XFS inode' shown many many times
by bugzilla_noreply＠suse.com 23 Jan '24

23 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1218864 https://bugzilla.suse.com/show_bug.cgi?id=1218864#c32 --- Comment #32 from Michael Chang <mchang(a)suse.com> --- The obs repository containing the test package: https://download.opensuse.org/repositories/home:/michael-chang:/bsc:/121886… For openSUSE Tumbleweed, you may follow the procedure to install the test package: > zypper ar --repo https://download.opensuse.org/repositories/home:/michael-chang:/bsc:/121886… > zypper ref > zypper dup --from home_michael-chang_bsc_1218864 --allow-vendor-change And this procedure to remove the test package: > zypper rr home_michael-chang_bsc_1218864 > zypper dup --allow-vendor-change For uefi, you may have to disable secure boot because the test grub.efi is not signed by SUSE. Optionally it is possible to keep secure boot on, but you have entrust the key of my home project by enrolling it into "Machine Owner Key" (MOK) keyring. > mokutil --import /usr/share/efi/x86_64/grub.der Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1218682] EFI aarch64 boot failure on honeycomb lx2
by bugzilla_noreply＠suse.com 23 Jan '24

23 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1218682 https://bugzilla.suse.com/show_bug.cgi?id=1218682#c3 --- Comment #3 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- Hi James, could you try suggestion from Stanimir? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1219060] New: lxqt test
by bugzilla_noreply＠suse.com 23 Jan '24

23 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219060 Bug ID: 1219060 Summary: lxqt test Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: LXQt Assignee: lxqt-bugs(a)suse.de Reporter: mvetter(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Just a test for our new lxqt-bugs(a)suse.de list to confirm we all get the notification. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1218864] grub2: error messages: 'not a correct XFS inode' shown many many times
by bugzilla_noreply＠suse.com 23 Jan '24

23 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1218864 https://bugzilla.suse.com/show_bug.cgi?id=1218864#c31 --- Comment #31 from Michael Chang <mchang(a)suse.com> --- (In reply to Lorenz Hüdepohl from comment #29) > To chime in as a third party: On my tumbleweed installation with the latest > change, I can no longer boot kernels from my root XFS. I had problems before > that were fixed in > > https://build.opensuse.org/request/show/1138021 > > already before I could report them :) > > But with the newest > > https://build.opensuse.org/request/show/1138021 > > it no longer works, again. > > (A compounding factor seems to be the move of the kernels from /boot to > /usr/lib/modules/$kernelversion, as the rather small /boot directory can > always be parsed by grub in my tests so far, whereas the rather large /usr > metadata is probably stored somehow differently by XFS, triggering this > issue. This could blur the timeline of events, somewhat, not sure what came > when) > > Here are details about the currently installed package (which is not able to > boot): > > root@~> rpm -q grub2 --changelog | head > * Mi Jan 17 2024 Michael Chang <mchang(a)suse.com> > - Resolved XFS regression leading to the "not a correct XFS inode" error by > temporarily reverting the problematic commit (bsc#1218864) > * 0001-Revert-fs-xfs-Fix-XFS-directory-extent-parsing.patch > [...] > root@~> rpm -qi grub2 > Name : grub2 > Version : 2.12 > Release : 2.1 > Architecture: x86_64 > Install Date: Sa 20 Jan 2024 09:23:11 CET > Group : System/Boot > Size : 27941722 > License : GPL-3.0-or-later > Signature : RSA/SHA512, Mi 17 Jan 2024 23:54:16 CET, Key ID > 35a2f86e29b700a4 > Source RPM : grub2-2.12-2.1.src.rpm > Build Date : Mi 17 Jan 2024 23:53:48 CET > Build Host : i04-ch1d > Packager : https://bugs.opensuse.org > Vendor : openSUSE > URL : http://www.gnu.org/software/grub/ > Summary : Bootloader with support for Linux, Multiboot and more > Description : > This is the second version of the GRUB (Grand Unified Bootloader), a > highly configurable and customizable bootloader with modular > architecture. It support rich scale of kernel formats, file systems, > computer architectures and hardware devices. > > This package includes user space utlities to manage GRUB on your system. > Distribution: openSUSE Tumbleweed This can the consequence of reverting "fs/xfs: Fix XFS directory extent parsing" that caused the xfs error here ... Before a proper fix landing upstream, I think we may provide a band-aid fix by adding back the number of entries check to the "Fix XFS directory extent parsing" patch whereas the node is not single extent and hence filtering out those "unmapped blocks" globally. I will try to provide test package so that you can help to verify it on two different potential layouts. -- You are receiving this mail because: You are on the CC list for the bug.

1 0