February 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1202820] kexec --load on UEFI with secure boot
by bugzilla_noreply＠suse.com 23 Feb '23

23 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1202820 Michal Suchanek <msuchanek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |msuchanek(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202820] kexec --load on UEFI with secure boot
by bugzilla_noreply＠suse.com 23 Feb '23

23 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1202820 Matthias Brugger <mbrugger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mbrugger(a)suse.com Assignee|ptesarik(a)suse.com |jbohac(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208571] installation interrupted by unexpected reboot
by bugzilla_noreply＠suse.com 23 Feb '23

23 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208571 https://bugzilla.suse.com/show_bug.cgi?id=1208571#c6 --- Comment #6 from Stefan Hundhammer <shundhammer(a)suse.com> --- Hm - unpacking those tarballs, I only see this: % tree . �� dmesg �� etc �� os-release �� X11 �� xorg.conf.d �� xorg.conf.install �� inst-sys �� journalctl-dmesg �� pbl.log �� rpm-qa �� YaST2 �� zypp �� history 6 directories, 7 files I don't know what's going on there. Was there a kernel panic during the installation? But if so, shouldn't it be stuck in that kernel panic screen? Or did just one of the steps in the final phase of the installation (inst_finish_xxx) fail and simply not copy the y2logs from the inst-sys RAM disk into the target system? Obviously, it did install something, and according to the "rpm-qa" file, it was yast2-*4.5.*.rpms, i.e. Leap 15.5 / SLE-15 SP5. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207116] New: kdump doesn't start frequently
by bugzilla_noreply＠suse.com 23 Feb '23

23 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207116 Bug ID: 1207116 Summary: kdump doesn't start frequently Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: jbohac(a)suse.com Reporter: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 864081 --> https://bugzilla.suse.com/attachment.cgi?id=864081&action=edit journalctl -u kdump|tail -200 systemctl status kdump �� kdump.service - Load kdump kernel and initrd Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled; preset: disabled) Active: active (exited) since Fri 2023-01-13 08:24:02 CET; 14min ago Process: 596 ExecStart=/usr/lib/kdump/load.sh --update (code=exited, status=0/SUCCESS) Main PID: 596 (code=exited, status=0/SUCCESS) CPU: 2.117s Jan 13 08:24:02 factory load.sh[596]: kexec_file_load failed: Device or resource busy This happens very often, see the attachment (journalctl -u kdump|tail -200). -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1196335] [Build C.520.1] kdump failed to start: device or resource busy
by bugzilla_noreply＠suse.com 23 Feb '23

23 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1196335 https://bugzilla.suse.com/show_bug.cgi?id=1196335#c10 Jiri Bohac <jbohac(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com --- Comment #10 from Jiri Bohac <jbohac(a)suse.com> --- *** Bug 1207116 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208567] qemu-system-x86_64: Failed to lock byte 100
by bugzilla_noreply＠suse.com 23 Feb '23

23 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208567 https://bugzilla.suse.com/show_bug.cgi?id=1208567#c6 David Disseldorp <ddiss(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jfehlig(a)suse.com Flags| |needinfo?(william.brown@sus | |e.com) --- Comment #6 from David Disseldorp <ddiss(a)suse.com> --- (In reply to David Disseldorp from comment #5) > (In reply to David Disseldorp from comment #3) > ... > > Putting it on my queue. My initial impression is that some changes to > > virt-aa-helper are needed to permit the file locking. > > Actually, it looks like what's needed here is a follow up to the boo#1203976 > 7aec69b7-apparmor-Fix-QEMU-access-for-UEFI.patch which permits locking of > qemu-ovmf-x86_64 paths installed under /usr/share/qemu/ovmf-*.bin . It looks > as though this edk2/OVMF path is somewhat SUSE-unique, which would explain > why this didn't make it into the upstream profile. @William: please try manually changing the profile at /etc/apparmor.d/abstractions/libvirt-qemu : @@ -90,7 +90,7 @@ /usr/share/proll/** r, /usr/share/qemu-efi/** r, /usr/share/qemu-kvm/** r, - /usr/share/qemu/** r, + /usr/share/qemu/** rk, /usr/share/seabios/** r, /usr/share/sgabios/** r, /usr/share/slof/** r, Then as root reload the profile (reload of all profiles is probably easiest): aa-teardown && systemctl restart apparmor.service This should allow locking of the /usr/share/qemu/ovmf-* files from the qemu-ovmf-x86_64 rpm. @James: it appears that the qemu-ovmf-x86_64 paths are SUSE-specific. Do you think upstream would be open to this change? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1204277] IPMI of power8 machine (type 8247-22L) is not accessible after firmware upgrade
by bugzilla_noreply＠suse.com 23 Feb '23

23 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1204277 https://bugzilla.suse.com/show_bug.cgi?id=1204277#c13 --- Comment #13 from LTC BugProxy <bugproxy(a)us.ibm.com> --- ------- Comment From FREDERIC(a)fr.ibm.com 2023-02-23 08:50 EDT------- Hi, sorry for the delay. Yes that was the path I would have like to explore :) Given the information Gery mentioned, here are, for this specific machine (8247-22L/212313A), the passwords generated for the 3 next days. If you can't make it, I'll provide more. 02/23/2023 : 42558F33 02/24/2023 : E2C62031 02/25/2023 : B57B1736 F. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1196335] [Build C.520.1] kdump failed to start: device or resource busy
by bugzilla_noreply＠suse.com 23 Feb '23

23 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1196335 https://bugzilla.suse.com/show_bug.cgi?id=1196335#c9 --- Comment #9 from Jiri Bohac <jbohac(a)suse.com> --- Also pushed this fix to SLE-15-SP4 and SLE-15-SP5 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208594] New: After update, X.org no longer recognizes nvidia driver
by bugzilla_noreply＠suse.com 23 Feb '23

23 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208594 Bug ID: 1208594 Summary: After update, X.org no longer recognizes nvidia driver Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: P.Suetterlin(a)royac.iac.es QA Contact: gfx-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 865078 --> http://bugzilla.opensuse.org/attachment.cgi?id=865078&action=edit Xorg logfiles after and before update I ran an update on my Laptop (TW 20230117->20230219). After the reboot, X started using the modesetting driver, instead of the G06 nvidia one. The G06 modules were successfully compiled, and are even loaded: woodstock:~ # lsmod|grep nvidia nvidia_drm 73728 2 nvidia_modeset 1224704 1 nvidia_drm nvidia_uvm 2883584 0 nvidia 56397824 11 nvidia_uvm,nvidia_modeset video 69632 3 thinkpad_acpi,i915,nvidia_modeset But looking at the Xorg.0.log I see no mention of it at all, in particular: [ 6.865] (==) Matched intel as autoconfigured driver 0 [ 6.865] (==) Matched modesetting as autoconfigured driver 1 [ 6.865] (==) Matched fbdev as autoconfigured driver 2 [ 6.865] (==) Matched vesa as autoconfigured driver 3 So the driver is not considered at all. From the previous boot, this read [2902759.019] (==) Matched intel as autoconfigured driver 0 [2902759.019] (==) Matched nvidia as autoconfigured driver 1 [2902759.019] (==) Matched nouveau as autoconfigured driver 2 [2902759.019] (==) Matched nv as autoconfigured driver 3 [2902759.019] (==) Matched modesetting as autoconfigured driver 4 [2902759.019] (==) Matched fbdev as autoconfigured driver 5 [2902759.019] (==) Matched vesa as autoconfigured driver 6 So none of the various nvidia drivers is found now. What is wrong? I didn't do anything other than 'zypper dup' and 'reboot'. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1204277] IPMI of power8 machine (type 8247-22L) is not accessible after firmware upgrade
by bugzilla_noreply＠suse.com 23 Feb '23

23 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1204277 https://bugzilla.suse.com/show_bug.cgi?id=1204277#c12 --- Comment #12 from Nick Singer <nsinger(a)suse.com> --- (In reply to LTC BugProxy from comment #10) > ------- Comment From FREDERIC(a)fr.ibm.com 2023-02-16 09:40 EDT------- > Hi Oliver, > which user do you login with on the FSP ? > > F. I managed to set the celogin1 password from within the admin account and see your mentioned option now. However, it prompts me to enter the temporary celogin password. Can you help us to get this one? -- You are receiving this mail because: You are on the CC list for the bug.

1 0