February 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1207562] U-Boot: Raspberry Pi 4 booting from USB stopped booting
by bugzilla_noreply＠suse.com 01 Feb '23

01 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207562 https://bugzilla.suse.com/show_bug.cgi?id=1207562#c19 --- Comment #19 from Chester Lin <chester.lin(a)suse.com> --- Hi Stefan and Pruessmann, (In reply to Stefan Seyfried from comment #17) > I can try different things, but I'd need instructions what to do where and > when. > > My U-boot knowledge is from embedded systems that do not use UEFI stuff at > all ;-) and from a time when there were no such things as "device trees" but > instead separate kernels for different hardware configurations were built :-) > > So what I wanted to say... > I don't even know what a "runtime FDT" is, much less how I would check if it > declares reserved memory ;-) > > The bdinfo would need to come from the "broken" U-boot? or can I use a > "good", working version? Just found that I can reproduce this issue as well [Snapshot20230130] based on the following configuration: 1. Run rpi-imager to turn usb-boot on. (BOOT-EEPROM updated) 2. Directly boot from USB stick and then the issue happens. Running the 'usb_boot' script in u-boot console has the same symptom. The console log is attached in #Comment18. But booting from mmc and then 'run usb_boot' just works fine. Compared to mmc boot, indeed there's one more reserved region in USB boot although none of them occupies address 0x00080000 at the beginning, which should be the default load address of grub2 for the distro bootcmd: ---- U-Boot> bdinfo <snip> lmb_dump_all: memory.cnt = 0x2 memory[0] [0x0-0x3defffff], 0x3df00000 bytes flags: 0 memory[1] [0x40000000-0xfbffffff], 0xbc000000 bytes flags: 0 reserved.cnt = 0x6 reserved[0] [0x0-0x7ffff], 0x00080000 bytes flags: 4 reserved[1] [0x3c820000-0x3defffff], 0x016e0000 bytes flags: 0 reserved[2] [0x3d8262d0-0x3dcfffff], 0x004d9d30 bytes flags: 0 reserved[3] [0x3ee62be0-0x3ee62fdf], 0x00000400 bytes flags: 4 reserved[4] [0x3ee63020-0x3ee63067], 0x00000048 bytes flags: 4 reserved[5] [0x40000000-0xfbffffff], 0xbc000000 bytes flags: 0 ---- However, I also tried to manually load grub2 and then ran bootefi directly, and it just worked well: ---- U-Boot 2023.01 (Jan 27 2023 - 00:00:00 +0000) DRAM: 991 MiB (effective 3.9 GiB) RPI 4 Model B (0xc03111) Core: 210 devices, 17 uclasses, devicetree: board MMC: mmcnr@7e300000: 1, mmc@7e340000: 0 Loading Environment from FAT... Card did not respond to voltage select! : -110 ** Bad device specification mmc 0 ** In: serial Out: serial Err: serial Net: eth0: ethernet@7d580000 PCIe BRCM: link up, 5.0 Gbps x1 (SSC) starting USB... Bus xhci_pci: Register 5000420 NbrPorts 5 Starting the controller USB XHCI 1.00 scanning bus xhci_pci for devices... 3 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found Hit any key to stop autoboot: 0 U-Boot> load usb 0:1 ${kernel_addr_r} /EFI/BOOT/bootaa64.efi 1574768 bytes read in 21 ms (71.5 MiB/s) U-Boot> bootefi ${kernel_addr_r} ${fdtcontroladdr} sdhci_set_clock: Timeout to wait cmd & data inhibit sdhci_set_clock: Timeout to wait cmd & data inhibit sdhci_set_clock: Timeout to wait cmd & data inhibit sdhci_send_command: MMC: 1 busy timeout increasing to: 200 ms. sdhci_send_command: MMC: 1 busy timeout increasing to: 400 ms. sdhci_send_command: MMC: 1 busy timeout increasing to: 800 ms. sdhci_send_command: MMC: 1 busy timeout increasing to: 1600 ms. sdhci_send_command: MMC: 1 busy timeout increasing to: 3200 ms. sdhci_send_command: MMC: 1 busy timeout. Card did not respond to voltage select! : -110 No EFI system partition Booting /\EFI\BOOT\bootaa64.efi ethernet@7d580000 Waiting for PHY auto negotiation to complete.... ---- I doubt that something in the default boot scan/process might cause an additional reservation on 0x00080000 at runtime since the manual load & bootefi commands seem to work fine. > > The problem with the broken one is that it is already in the TFTP BOOTP > stage once the HDMI output stabilizes and once it is there, no keyboard > input seems to do anything at all. So I'd need to set up a serial console > etc and since this would be possible, it's quite some effort here and I'd > leave that experiment to someone else experiencing this issue who already > might have everything set up. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207562] U-Boot: Raspberry Pi 4 booting from USB stopped booting
by bugzilla_noreply＠suse.com 01 Feb '23

01 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207562 https://bugzilla.suse.com/show_bug.cgi?id=1207562#c18 --- Comment #18 from Chester Lin <chester.lin(a)suse.com> --- Created attachment 864673 --> https://bugzilla.suse.com/attachment.cgi?id=864673&action=edit USB boot fail log -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207757] New: DBus error on SSH login caused by mc package
by bugzilla_noreply＠suse.com 01 Feb '23

01 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207757 Bug ID: 1207757 Summary: DBus error on SSH login caused by mc package Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: igor.jasan(a)lbv.nrw.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The following error message appears when logging into a openSUSE Leap 15.4 and SLES 15 SP4 machine via SSH (Putty). The message does not appear when logging in via a console. dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.InvalidArgs: Invalid environment assignments An investigation has shown that the problem is caused by the 'mc' package. # dbus-update-activation-environment --systemd --all --verbose ... <<< deleted some output >>> ... dbus-update-activation-environment: setting BASH_FUNC_mc%%=() { . /usr/share/mc/mc-wrapper.sh } dbus-update-activation-environment: setting _=/usr/bin/dbus-update-activation-environment dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.InvalidArgs: Invalid environment assignments # rpm -qf /usr/share/mc/mc-wrapper.sh mc-4.8.27-bp154.1.50.x86_64 The error message is suppressed if lines 7 to 10 in the /etc/profile.d/mc.sh file are commented out: # cat -n /etc/profile.d/mc.sh 1 # Don't define aliases in plain Bourne shell 2 [ -n "${BASH_VERSION}${KSH_VERSION}${ZSH_VERSION}" ] || return 0 3 mc() 4 { 5 . /usr/share/mc/mc-wrapper.sh 6 } 7 #if [ -n "$BASH_VERSION" ] 8 #then 9 # export -f mc 10 #fi -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1206500] After update: when ssh'ing to other 15.4: Invalid environment assignments
by bugzilla_noreply＠suse.com 01 Feb '23

01 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206500 http://bugzilla.opensuse.org/show_bug.cgi?id=1206500#c16 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |igor.jasan(a)lbv.nrw.de --- Comment #16 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- *** Bug 1207757 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 1207836] New: container-selinux conflicting with rke2-selinux and k3s-selinux (MicroOS)
by bugzilla_noreply＠suse.com 01 Feb '23

01 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207836 Bug ID: 1207836 Summary: ��container-selinux conflicting with rke2-selinux and ��k3s-selinux (MicroOS) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: henrik.dermer(a)fouredge.se QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On a fresh install of MicroOS, kernel 6.1.8-1-default (I have not tested on Tumbleweed transactional) installing rke2-selinux and ��k3s-selinux print the following, Conflicting name type transition rules Binary policy creation failed at /var/lib/selinux/targeted/tmp/modules/400/rke2/cil:324 Failed to generate binary semodule: Failed! I report this bug here since it's been working earlier, with the same selinux packages for RKE2 and K3S. This issue prevents RKE2 and K3S to start. containerd when running RKE2 is logging, time="2023-02-01T17:41:08.449020719+01:00" level=warning msg="cleanup warnings time=\"2023-02-01T17:41:08+01:00\" level=info msg=\"starting signal loop\" namespace=k8s.io pid=1491 runtime=io.containerd.runc.v2\ntime=\"2023-02-01T17:41:08+01:00\" level=warning msg=\"failed to read init pid file\" error=\"open /run/k3s/containerd/io.containerd.runtime.v2.task/k8s.io/cd82f9836efb766f011072fa70dbe98b5fcc2b1f21b2d384a317a25261ff8d7e/init.pid: no such file or directory\" runtime=io.containerd.runc.v2\n" time="2023-02-01T17:41:08.449375940+01:00" level=error msg="copy shim log" error="read /proc/self/fd/25: file already closed" time="2023-02-01T17:41:08.453617146+01:00" level=error msg="RunPodSandbox for &PodSandboxMetadata{Name:etcd-node1.k8s.testing,Uid:e18aa5e5b83a5a3c56d78e4054612394,Namespace:kube-system,Attempt:0,} failed, error" error="failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: write /proc/self/attr/keycreate: invalid argument: unknown" -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1207562] U-Boot: Raspberry Pi 4 booting from USB stopped booting
by bugzilla_noreply＠suse.com 01 Feb '23

01 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207562 https://bugzilla.suse.com/show_bug.cgi?id=1207562#c15 Chester Lin <chester.lin(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jlee(a)suse.com --- Comment #15 from Chester Lin <chester.lin(a)suse.com> --- (In reply to Stefan Seyfried from comment #14) > updated the second machine today to u-boot-rpiarm64-2023.01-2.1.aarch64 from > tumbleweed-oss repo, last changelog > > * Fri Jan 27 2023 Guillaume GARDET <guillaume.gardet(a)opensuse.org> > Patch queue updated from https://github.com/openSUSE/u-boot.git > tumbleweed-2023.01 > Prefer upstream solution to fix boo#1207562 > * Patches dropped: > 0017-rpi-fix-boot-from-USB-on-RPi4-boo-1.patch > * Patches added: > 0017-Backport-https-patchwork.ozlabs.org.patch > > > And it still fails. > I only could take a picture of the error message, so typing in here (if this > continues, I definitely will have to set up a serial-to-syslog-device for my > raspis ;-)) > ------- > Scanning usb 0:1 > BootOrder not defined > EFI boot manager: Cannot load any image > Found EFI removable media binary efi/boot/bootaa64.efi This log was printed by the u-boot script 'scan_dev_for_efi', and then it ran the script 'boot_efi_binary' in order to load and execute grub2. > ** Reading file would overwrite reserved memory ** > Failed to load 'efi/boot/bootaa64.efi' It seemed that somehow the load address [should be 0x00080000 = kernel_addr_r] had been *reserved* so that the 'boot_efi_binary' script failed to load the grub2 from the USB disk. Could you please check if there's any reserved memory declared in the runtime FDT? > No UEFI binary known at 0x00080000 There was no grub2 binary stored in 0x00080000 so the bootefi command just failed. > EFI LOAD FILED: continuing... > BOOTP broadcast 1 > ------ > > I'd try to boot the machine simply via bootp/tftp, but these machines are in > the guest network and thus I cannot easily provide them with tftp ;-) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207810] Digest verification failed for file primary.xml.gz (opensuse.ucom.am)
by bugzilla_noreply＠suse.com 01 Feb '23

01 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207810 https://bugzilla.suse.com/show_bug.cgi?id=1207810#c5 --- Comment #5 from Michael Andres <ma(a)suse.com> --- (similar in bug#1206934) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207810] New: suspicious mirror
by bugzilla_noreply＠suse.com 01 Feb '23

01 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207810 Bug ID: 1207810 Summary: suspicious mirror Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: lcfork233(a)proton.me QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Warning: Digest verification failed for file 'bd28fa48d984b87e9f52b9940f844fd074579967dba3469b510d39488984684cbfc2513d2f461fb6bef645f3f17eedbcd23174714908089d819371fe714220f0-primary.xml.gz' [/var/tmp/AP_0xPIL2U8/repodata/bd28fa48d984b87e9f52b9940f844fd074579967dba3469b510d39488984684cbfc2513d2f461fb6bef645f3f17eedbcd23174714908089d819371fe714220f0-primary.xml.gz] expected bd28fa48d984b87e9f52b9940f844fd074579967dba3469b510d39488984684cbfc2513d2f461fb6bef645f3f17eedbcd23174714908089d819371fe714220f0 but got e14006d801ecead6e58949f5b34cf0b56e1ada07493d50ee123080c9a0b26c21e53a8d27e62f3438367a3b435992447d925f13636c47d651fa389dd9a5e5aafe Accepting packages with wrong checksums can lead to a corrupted system and in extreme cases even to a system compromise. However if you made certain that the file with checksum 'e140..' is secure, correct and should be used within this operation, enter the first 4 characters of the checksum to unblock using this file on your own risk. Empty input will discard the file. Unblock or discard? [e140/...? shows all options] (discard): When doing zypper refresh, digest verification failed, and everytime the checksum would change. I used ```curl -LI http://download.opensuse.org/tumbleweed/repo/non-oss/repodata/bd28fa48d984b… to check what mirror is doing funky things, I got opensuse.ucom.am. This mirror seems to have outdated/modified softwares. It seems suspicious and should be avoided at all cost. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1207807] kcompactd0 consumes 100% cpu apparently causing virtual machine to freeze for extended times
by bugzilla_noreply＠suse.com 01 Feb '23

01 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207807 https://bugzilla.suse.com/show_bug.cgi?id=1207807#c6 --- Comment #6 from Michal Hocko <mhocko(a)suse.com> --- Have you tried to run with the kernel mentioned in bug 1206848 comment 11? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207831] Incorrect path in message generated by yast2-auth-server package
by bugzilla_noreply＠suse.com 01 Feb '23

01 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207831 https://bugzilla.suse.com/show_bug.cgi?id=1207831#c1 Stefan Hundhammer <shundhammer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|YaST2 |Samba Assignee|yast2-maintainers(a)suse.de |samba-maintainers(a)SuSE.de QA Contact|jsrain(a)suse.com |samba-maintainers(a)SuSE.de Severity|Normal |Minor --- Comment #1 from Stefan Hundhammer <shundhammer(a)suse.com> --- Reassigning to the maintainers of yast2-auth-server which is the Samba team (AFAIK). -- You are receiving this mail because: You are on the CC list for the bug.

1 0