February 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1159134] UEFI bios for aarch64 not available on other architectures
by bugzilla_noreply＠novell.com 04 Feb '20

04 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1159134 http://bugzilla.suse.com/show_bug.cgi?id=1159134#c4 --- Comment #4 from Liang Yan <lyan(a)suse.com> --- (In reply to Luigi Baldoni from comment #3) > @Liang Yan I filed the bug regarding the package in openSUSE Tumbleweed. > My question is: if no package in it supplies qemu-uefi-aarch64.bin, doesn't > that make qemu-system-aarch64 broken on x86_64? If so, what's the point of > building it at all? > > Am I getting some part of this wrong? ah, you are right. It indeeded has this issue for cross architecture scenario. We well change it ASAP. Nice catch. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1162555] New: [doc] 27.2 Required Software should reference kernels which support KVM
by bugzilla_noreply＠novell.com 04 Feb '20

04 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1162555 Bug ID: 1162555 Summary: [doc] 27.2 Required Software should reference kernels which support KVM Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Documentation Assignee: fs(a)suse.com Reporter: distroguy(a)gmail.com QA Contact: fs(a)suse.com Found By: --- Blocker: --- 27.2 Required Software https://doc.opensuse.org/documentation/leap/virtualization/single-html/book… If using JeOS version of Leap, the default kernel is kernel-default-base which does not include KVM kernel modules. Zypper does not seem to find the kernel modules via --provide regex, so you can't find out what kernel to install. Might be nice to have a note that mentions you need a specific kernel or a non-base kernel, especially if the modules fail to load. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1161296] systemtap print_backtrace() Pass 4: compilation failed
by bugzilla_noreply＠novell.com 04 Feb '20

04 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1161296 http://bugzilla.suse.com/show_bug.cgi?id=1161296#c2 Tony Jones <tonyj(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Tony Jones <tonyj(a)suse.com> --- submit request 769807 +Mon Feb 3 23:01:33 UTC 2020 - Tony Jones <tonyj(a)suse.com> + +- Resolve protoype issue when invoking tracebacks (bsc#1161296) + Also dependent fix to handle GCC fallthrough + + New patch: systemtap-fix-strict-prototypes-in-autoconf-stack-trace-save-regs.c.patch + New patch: systemtap-amend-fallback-comment-to-work-with-newer-gcc.patch + # stap -ve 'probe module("af_packet").function("packet_snd") { print_backtrace(); }' Pass 1: parsed user script and 479 library scripts using 97808virt/88952res/6964shr/82296data kb, in 370usr/50sys/427real ms. Pass 2: analyzed script: 1 probe, 1 function, 0 embeds, 0 globals using 99884virt/92480res/8100shr/84372data kb, in 1190usr/60sys/1249real ms. Pass 3: translated to C into "/tmp/stappfLM9c/stap_dd005a0ebba188a045107c12bbf77940_1144_src.c" using 100016virt/92772res/8292shr/84504data kb, in 1070usr/90sys/1184real ms. Pass 4: compiled C into "stap_dd005a0ebba188a045107c12bbf77940_1144.ko" in 25170usr/4130sys/29367real ms. Pass 5: starting run. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1162511] Flooded with messages dev_pm_opp_set_rate: failed to find current OPP for freq on Raspberry Pi 4B
by bugzilla_noreply＠novell.com 03 Feb '20

03 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1162511 http://bugzilla.suse.com/show_bug.cgi?id=1162511#c2 --- Comment #2 from Freek de Kruijf <freek(a)opensuse.org> --- Still the same. Lots of these messages. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1162547] New: Upgrade python-typing_extensions to 3.7.4
by bugzilla_noreply＠novell.com 03 Feb '20

03 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1162547 Bug ID: 1162547 Summary: Upgrade python-typing_extensions to 3.7.4 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: maintenance(a)opensuse.org Reporter: stasiek(a)michalski.cc QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Required for newer matrix-synapse -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1159134] UEFI bios for aarch64 not available on other architectures
by bugzilla_noreply＠novell.com 03 Feb '20

03 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1159134 http://bugzilla.suse.com/show_bug.cgi?id=1159134#c3 --- Comment #3 from Luigi Baldoni <aloisio(a)gmx.com> --- @Liang Yan I filed the bug regarding the package in openSUSE Tumbleweed. My question is: if no package in it supplies qemu-uefi-aarch64.bin, doesn't that make qemu-system-aarch64 broken on x86_64? If so, what's the point of building it at all? Am I getting some part of this wrong? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1159134] UEFI bios for aarch64 not available on other architectures
by bugzilla_noreply＠novell.com 03 Feb '20

03 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1159134 http://bugzilla.suse.com/show_bug.cgi?id=1159134#c2 --- Comment #2 from Liang Yan <lyan(a)suse.com> --- Sorry for the late response. qemu-uefi-aarch64.bin is file provided by package qemu-uefi-aarch64. This pacage even has "qemu" in the name is provided by package "ovmf", however this package is not under "Virtualization" repostory like other qemu packages. For example: https://build.suse.de/package/view_file/SUSE:SLE-15-SP2:GA/ovmf/ovmf.spec?e… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1161843] New: Screen flickering on latest Dell XPS 7390 with kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
by bugzilla_noreply＠novell.com 03 Feb '20

03 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1161843 Bug ID: 1161843 Summary: Screen flickering on latest Dell XPS 7390 with kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: sogal(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- # Hardware Latest (nov 2019) Dell XPS 7390 with Intel i915 chipset # Kernel 5.4.10-1-default (OS Tumbleweed up to date) (same behavior was noticed with the 5.3.x kernels) # Relevant outputs ## lspci 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 02) ## lshw *-display description: VGA compatible controller product: UHD Graphics vendor: Intel Corporation physical id: 2 bus info: pci@0000:00:02.0 logical name: /dev/fb0 version: 02 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb configuration: depth=32 driver=i915 latency=0 mode=1920x1080 visual=truecolor xres=1920 yres=1080 resources: iomemory:600-5ff iomemory:400-3ff irq:139 memory:604a000000-604affffff memory:4000000000-400fffffff ioport:3000(size=64) memory:c0000-dffff ## /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-5.4.10-1-default root=UUID=55518547-6da3-4579-bdad-ecf3dbee0de4 splash=silent resume=/dev/disk/by-id/nvme-PC601_NVMe_SK_hynix_512GB_AD9BN4767124YBC32-part3 mitigations=auto quiet # Description >From time to time, the screen flickers, freezes and goes back to normal. The following message can be seen in the journal: kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun Sometimes this problem leads to the computer being unusable, the screen does not return to a normal state and switching to another TTY via Ctrl+Alt+Fx does not work. When the computer exits from sleep, the same behavior can be observed, the login screens' (provided by GDM in my case) colors are messed up. This affects only the build-in screen in my case. Even if an external monitor is connected it does not seem to be affected so far. # Possibly related bugs https://bugzilla.opensuse.org/show_bug.cgi?id=1156254 https://bugzilla.opensuse.org/show_bug.cgi?id=1132926 Please let me know if I can help by providing further information or testing some kernel options. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1162435] lots of entries in vmware-vmsvc-root.log "[ warning] [guestinfo] GuestInfoGetDiskDevice: Missing disk device name;
by bugzilla_noreply＠novell.com 03 Feb '20

03 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1162435 http://bugzilla.suse.com/show_bug.cgi?id=1162435#c2 --- Comment #2 from John Wolfe <jwolfe(a)vmware.com> --- (In reply to Flex Liu from comment #1) > This issue would be introduced by: > > https://github.com/vmware/open-vm-tools/commit/ > 83dbe8ed5bf6f9e770e22c670c5617bc93e48e55 > > We need fix it to handle the btrfs subvolumns properly. Looking into this issue now. Original testing of this change was with BTRFS on SLES-15 SP0. Checking to determine what may be different with the BTRFS on SLES-12 SP4 and why the diskInfo is unable to walk the /sys/class/block links. In the meantime, the quickest fix for the warning message spew is to replace the g_warning() with g_debug() at line #683 in open-vm-tools/services/plugins/guestInfo/diskInfo.c g_warning("%s: Missing disk device name; VMDK mapping unavailable " -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1162435] lots of entries in vmware-vmsvc-root.log "[ warning] [guestinfo] GuestInfoGetDiskDevice: Missing disk device name;
by bugzilla_noreply＠novell.com 03 Feb '20

03 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1162435 John Wolfe <jwolfe(a)vmware.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jwolfe(a)vmware.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0