February 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1207655] amdgpu [RX 7900] causing system freeze
by bugzilla_noreply＠suse.com 08 Feb '23

08 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207655 https://bugzilla.suse.com/show_bug.cgi?id=1207655#c6 --- Comment #6 from Stefan Dirsch <sndirsch(a)suse.com> --- I've branched Mesa to build Mesa 23.0.0-rc4. Unfortunately this doesn't include these fixes yet. I think it was branched before the patches got merged. :-( https://build.opensuse.org/package/show/home:sndirsch:branches:X11:XOrg/Mesa -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207374] Cannot set up iscsi targets during installation
by bugzilla_noreply＠suse.com 08 Feb '23

08 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207374 https://bugzilla.suse.com/show_bug.cgi?id=1207374#c8 --- Comment #8 from Stefan Hundhammer <shundhammer(a)suse.com> --- Bingo. It's now open-iscsi-2.1.8 (Leap 15.4: 2.1.7), and the change log even tells us this: https://build.opensuse.org/package/view_file/openSUSE:Factory/open-iscsi/op… ------------------------------------------------------------------- Wed Dec 7 18:47:08 UTC 2022 - Lee Duncan <lduncan(a)suse.com> - Moving DB files from /etc/iscsi/* to /var/lib/iscsi/* for SLE-15-SP5 and forward, as is done in Tumbleweed. - Added /etc/iscsi/README.DB-files-moved, and added SPEC file changes to support this, including a post-install script to move the DB files, only installed if DB files are moved. - Renamed shared library from libopeniscsiusr0_2_0 to libopeniscsiusr0, to correctly match SONAME in library. ------------------------------------------------------------------- -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207944] intel_iommu=on Is not work on Alderlake
by bugzilla_noreply＠suse.com 08 Feb '23

08 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207944 https://bugzilla.suse.com/show_bug.cgi?id=1207944#c4 --- Comment #4 from Michiya Hagimoto <kokeko(a)mac.com> --- Today I try to test another bug(bug 1207943) and fix this problem. I add i915 force load command on kernel cmdline. i915.force_probe=46a6 and ge-generate initrd and reboot iommu is work! sudo dmesg | grep iommu [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.14.21-150400.24.41-default root=UUID=033623f0-6823-4876-86b6-c4dc6c3d88d1 rd.timeout=60 splash=verbose quiet preempt=full intel_iommu=on iommu=pt module_blacklist=iwlwifi,btusb mitigations=auto net.ifnames=1 cpufreq.default_governor=powersave i915.force_probe=46a6 [ 0.022828] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.14.21-150400.24.41-default root=UUID=033623f0-6823-4876-86b6-c4dc6c3d88d1 rd.timeout=60 splash=verbose quiet preempt=full intel_iommu=on iommu=pt module_blacklist=iwlwifi,btusb mitigations=auto net.ifnames=1 cpufreq.default_governor=powersave i915.force_probe=46a6 [ 0.687908] iommu: Default domain type: Passthrough (set via kernel command line) [ 0.821297] pci 0000:00:00.0: Adding to iommu group 0 [ 0.821303] pci 0000:00:02.0: Adding to iommu group 1 [ 0.821320] pci 0000:00:06.0: Adding to iommu group 2 [ 0.821325] pci 0000:00:08.0: Adding to iommu group 3 [ 0.821330] pci 0000:00:0a.0: Adding to iommu group 4 [ 0.821338] pci 0000:00:14.0: Adding to iommu group 5 [ 0.821342] pci 0000:00:14.2: Adding to iommu group 5 [ 0.821347] pci 0000:00:14.3: Adding to iommu group 6 [ 0.821355] pci 0000:00:15.0: Adding to iommu group 7 [ 0.821359] pci 0000:00:15.1: Adding to iommu group 7 [ 0.821365] pci 0000:00:16.0: Adding to iommu group 8 [ 0.821370] pci 0000:00:17.0: Adding to iommu group 9 [ 0.821396] pci 0000:00:1d.0: Adding to iommu group 10 [ 0.821405] pci 0000:00:1f.0: Adding to iommu group 11 [ 0.821410] pci 0000:00:1f.4: Adding to iommu group 11 [ 0.821415] pci 0000:00:1f.5: Adding to iommu group 11 [ 0.821431] pci 0000:01:00.0: Adding to iommu group 12 [ 0.821457] pci 0000:02:00.0: Adding to iommu group 13 I hope to passthrough wlan device to my VM. sudo lspci [sudo] password for koke: 00:00.0 Host bridge: Intel Corporation Device 4621 (rev 02) 00:02.0 VGA compatible controller: Intel Corporation Alder Lake-P Integrated Graphics Controller (rev 0c) 00:06.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x4 Controller #0 (rev 02) 00:08.0 System peripheral: Intel Corporation 12th Gen Core Processor Gaussian & Neural Accelerator (rev 02) 00:0a.0 Signal processing controller: Intel Corporation Platform Monitoring Technology (rev 01) 00:14.0 USB controller: Intel Corporation Alder Lake PCH USB 3.2 xHCI Host Controller (rev 01) 00:14.2 RAM memory: Intel Corporation Alder Lake PCH Shared SRAM (rev 01) 00:14.3 Network controller: Intel Corporation Alder Lake-P PCH CNVi WiFi (rev 01) 00:15.0 Serial bus controller: Intel Corporation Alder Lake PCH Serial IO I2C Controller #0 (rev 01) 00:15.1 Serial bus controller: Intel Corporation Alder Lake PCH Serial IO I2C Controller #1 (rev 01) 00:16.0 Communication controller: Intel Corporation Alder Lake PCH HECI Controller (rev 01) 00:17.0 SATA controller: Intel Corporation Alder Lake-P SATA AHCI Controller (rev 01) 00:1d.0 PCI bridge: Intel Corporation Device 51b0 (rev 01) 00:1f.0 ISA bridge: Intel Corporation Alder Lake PCH eSPI Controller (rev 01) 00:1f.4 SMBus: Intel Corporation Alder Lake PCH-P SMBus Host Controller (rev 01) 00:1f.5 Serial bus controller: Intel Corporation Alder Lake-P PCH SPI Controller (rev 01) 01:00.0 Non-Volatile memory controller: Intel Corporation SSD 600P Series (rev 03) 02:00.0 Ethernet controller: Intel Corporation Ethernet Controller I225-V (rev 03) Add device to libvirt xml. <hostdev mode='subsystem' type='pci' managed='yes'> <source> <address domain='0x0000' bus='0x00' slot='0x14' function='0x3'/> </source> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </hostdev> Works! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207374] Cannot set up iscsi targets during installation
by bugzilla_noreply＠suse.com 08 Feb '23

08 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207374 https://bugzilla.suse.com/show_bug.cgi?id=1207374#c7 --- Comment #7 from Stefan Hundhammer <shundhammer(a)suse.com> --- Hm... on my Leap 15.4, it uses /etc/iscsi/send_targets; in the y2log it complains about /var/lib/iscsi/send_targets being read-only. Was there a recent change what directory it uses, and we need to adapt the inst-sys and/or our yast-iscsi part? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207374] Cannot set up iscsi targets during installation
by bugzilla_noreply＠suse.com 08 Feb '23

08 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207374 https://bugzilla.suse.com/show_bug.cgi?id=1207374#c6 --- Comment #6 from Stefan Hundhammer <shundhammer(a)suse.com> --- According to "man iscsiadm", exit code 6 is ISCSI_ERR_IDBM - error accessing/managing iSCSI DB (the "timeout" command exits with 124 if the command times out, otherwise it's the exit status of the called command; see "timeout --help") -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207943] btrfs i/o error on Alderlake
by bugzilla_noreply＠suse.com 08 Feb '23

08 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207943 https://bugzilla.suse.com/show_bug.cgi?id=1207943#c6 Michiya Hagimoto <kokeko(a)mac.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Michiya Hagimoto <kokeko(a)mac.com> --- OK, I confirm no error. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207374] Cannot set up iscsi targets during installation
by bugzilla_noreply＠suse.com 08 Feb '23

08 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207374 https://bugzilla.suse.com/show_bug.cgi?id=1207374#c5 --- Comment #5 from Stefan Hundhammer <shundhammer(a)suse.com> --- Exact messages from y2log: 2023-02-06 12:42:27 <1> htpc(3965) [Ruby] lib/cheetah.rb(record_commands):163 Executing "timeout --kill-after\=5s 10s iscsiadm -m discovery -P 1 -t st -I default -p 192.168.69.6:3260 -o new". iscsiadm: Could not make /var/lib/iscsi/send_targets: Read-only file system iscsiadm: Could not add new discovery record. 2023-02-06 12:42:27 <1> htpc(3965) [Ruby] lib/cheetah.rb(record_status):183 Status: 6 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207675] [Build 388.1] nothing provides 'libbpf.so.0()(64bit)' needed by the to be installed qemu-arm-7.1.0-150500.43.3.aarch64
by bugzilla_noreply＠suse.com 08 Feb '23

08 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207675 Dario Faggioli <dfaggioli(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lubos.kocman(a)suse.com Flags| |needinfo?(lubos.kocman@suse | |.com) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207675] [Build 388.1] nothing provides 'libbpf.so.0()(64bit)' needed by the to be installed qemu-arm-7.1.0-150500.43.3.aarch64
by bugzilla_noreply＠suse.com 08 Feb '23

08 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207675 Dario Faggioli <dfaggioli(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aginies(a)suse.com Flags| |needinfo?(aginies(a)suse.com) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207675] [Build 388.1] nothing provides 'libbpf.so.0()(64bit)' needed by the to be installed qemu-arm-7.1.0-150500.43.3.aarch64
by bugzilla_noreply＠suse.com 08 Feb '23

08 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207675 https://bugzilla.suse.com/show_bug.cgi?id=1207675#c2 Dario Faggioli <dfaggioli(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dfaggioli(a)suse.com Flags| |needinfo? --- Comment #2 from Dario Faggioli <dfaggioli(a)suse.com> --- (In reply to Lubos Kocman from comment #1) > Same happens on x86_64 https://openqa.opensuse.org/tests/3070490#step/qemu/14 > Right. However, I'm still not sure about how to handle things like these. In fact, as far as I can see in both OBS and IBS, all the dependencies are there and the build works. Who do I need to ask to also put them in the proper places, in order for the actual package installation to work as well? Antoine, any clue? -- You are receiving this mail because: You are on the CC list for the bug.

1 0