July 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1218682] New: EFI aarch64 boot failure on honeycomb lx2
by bugzilla_noreply＠suse.com 22 Oct '24

22 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1218682 Bug ID: 1218682 Summary: EFI aarch64 boot failure on honeycomb lx2 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: james.hobson(a)oriel.ox.ac.uk QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- We are running micro os (tumbleweed) on two build servers. Two nights ago, these failed to boot after an upgrade, same thing happened last night. The hardware is the honeycomb lx2, the boot log is: Booting `openSUSE MicroOS' Loading Linux 6.6.9-1-default ... Loading initial ramdisk ... [ 0.687447][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000140, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 0.699962][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 0.712472][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 0.724981][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 0.737490][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 0.749998][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 0.762507][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 0.775015][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 0.787522][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 0.800030][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 1.187743][ T99] fsl_mc_bus NXP0008:00: mc_get_version() failed with error -110 [ 5.689703][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 5.702224][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 5.714736][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 5.727248][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 5.739760][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 5.752271][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 5.764783][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 5.777294][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 5.789805][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 5.802316][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.693031][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.705546][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.718058][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.730569][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.743080][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.755592][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.768102][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.780613][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.793124][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.805635][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.696364][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.708881][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.721393][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.733904][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.746416][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.758927][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.771438][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.783949][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.796460][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.808971][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.699708][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.712228][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.724743][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.737256][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.749770][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.762283][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.774797][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.787311][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.799824][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.812337][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.703043][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.715557][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.728071][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.740585][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.753098][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.765611][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.778124][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.790637][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.803150][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.815663][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.706370][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.718885][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.731398][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.743911][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.756424][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.768937][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.781450][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.793964][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.806477][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.818990][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.709704][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.722219][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.734732][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.747245][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.759758][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.772271][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.784785][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.797298][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.809811][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.822325][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.713036][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.725551][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.738064][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.750578][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.763090][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.775603][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.788117][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.800630][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.813143][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.825656][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 44.003022][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 26s! [swapper/0:0] [ 45.716367][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 45.728884][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 45.741398][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 45.753912][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 45.766425][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 45.778939][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 45.791452][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 45.803965][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 45.816479][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 45.828992][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.719700][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.732214][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.744728][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.757240][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.769754][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.782267][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.794780][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.807294][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.819807][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.832320][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1227418] New: [Build 20240704] openQA test fails in journal_check
by bugzilla_noreply＠suse.com 22 Oct '24

22 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1227418 Bug ID: 1227418 Summary: [Build 20240704] openQA test fails in journal_check Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/4320773/modules/jour nal_check/steps/21 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: forgotten_u0-bnvADNc(a)user.net Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation Every once in a while, I can see things like this in the journal: Jul 05 04:38:43.198898 localhost.localdomain systemd-coredump[3116]: Resource limits disable core dumping for process 3113 (boot-plugin). Jul 05 04:38:43.199870 localhost.localdomain systemd-coredump[3116]: Process 3113 (boot-plugin) of user 0 terminated abnormally without generating a coredump. I'm fully aware that this bug report is missing all relevant information, but the coredump being limited by resources makes it really hard to extract more info from openQA Hopefully you can find similar crashes in some other systems too openQA test in scenario microos-Tumbleweed-MicroOS-Image-x86_64-microos2microosnext@64bit fails in [journal_check](https://openqa.opensuse.org/tests/4320773/modules/journal_ch… ## Test suite description Boot from the latest published MicroOS image and transactional-update dup to snapshot under test. Make sure to use %BUILD% in the URL and file name to force a redownload for new builds. ## Reproducible Fails since (at least) Build [20240704](https://openqa.opensuse.org/tests/4319742) ## Expected result Last good: [20240703](https://openqa.opensuse.org/tests/4317737) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=microos… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1227878] New: econf_readDirs crashes if one of the paths is NULL
by bugzilla_noreply＠suse.com 22 Oct '24

22 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1227878 Bug ID: 1227878 Summary: econf_readDirs crashes if one of the paths is NULL Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: schubi(a)suse.com Reporter: sbrabec(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- If util-linux is configured with a plain ./configure, agetty crashes. The reason is simple: If ./configure is called without --with-vendordir=DIR on a system with libeconf, econf_readDirs is called with dist_conf_dir=0x0. And the code does not check for it before calling strdup(). Reading the code, the same is apparently valid for etc_conf_dir. And there are more occurrences of unsanitized strdup() calls on directory names. (gdb) bt #0 __strlen_evex () at ../sysdeps/x86_64/multiarch/strlen-evex-base.S:81 #1 0x00007f06d54aa752 in __GI___strdup (s=s@entry=0x0) at strdup.c:41 #2 0x00007f06d56fa26b in econf_readDirs (comment=0x41260f "#", delim=0x412601 "= \t", config_suffix=0x412605 "defs", config_name=0x412537 "login", etc_conf_dir=0x41260a "/etc", dist_conf_dir=0x0, result=0x41b630 <file>) at ../lib/libeconf.c:510 #3 econf_readDirs (result=result@entry=0x41b630 <file>, dist_conf_dir=dist_conf_dir@entry=0x0, etc_conf_dir=etc_conf_dir@entry=0x41260a "/etc", config_name=config_name@entry=0x412537 "login", config_suffix=config_suffix@entry=0x412605 "defs", delim=delim@entry=0x412601 "= \t", comment=0x41260f "#") at ../lib/libeconf.c:495 #4 0x0000000000409a18 in load_defaults () at lib/logindefs.c:257 #5 0x0000000000409cb5 in getlogindefs_bool (name=name@entry=0x41241a "LOGIN_PLAIN_PROMPT", dflt=dflt@entry=0) at lib/logindefs.c:326 #6 0x0000000000406b11 in main (argc=<optimized out>, argv=<optimized out>) at term-utils/agetty.c:490 (gdb) up #1 0x00007f06d54aa752 in __GI___strdup (s=s@entry=0x0) at strdup.c:41 41 size_t len = strlen (s) + 1; (gdb) up #2 0x00007f06d56fa26b in econf_readDirs (comment=0x41260f "#", delim=0x412601 "= \t", config_suffix=0x412605 "defs", config_name=0x412537 "login", etc_conf_dir=0x41260a "/etc", dist_conf_dir=0x0, result=0x41b630 <file>) at ../lib/libeconf.c:510 510 (*result)->parse_dirs[0] = strdup(dist_conf_dir); (gdb) l 505 return ret; 506 507 (*result)->parse_dirs_count = 2; 508 (*result)->parse_dirs = calloc((*result)->parse_dirs_count+1, sizeof(char *)); 509 (*result)->parse_dirs[(*result)->parse_dirs_count] = NULL; 510 (*result)->parse_dirs[0] = strdup(dist_conf_dir); 511 (*result)->parse_dirs[1] = strdup(etc_conf_dir); 512 513 return readConfigWithCallback(result, 514 config_name, (gdb) p dist_conf_dir $1 = 0x0 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1223436] New: cannot login without password set
by bugzilla_noreply＠suse.com 21 Oct '24

21 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1223436 Bug ID: 1223436 Summary: cannot login without password set Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: brunopitrus(a)hotmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After updating a Tumbleweed VM without any password set either on the user account, or on root, it has locked me out — i can login neither from SDDM, nor from the kernel console. The previous update of that machine was about a month ago (after the lzma backdoor rebuild). -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1217774] New: qt6-webengine qtpdf.index reproducible builds
by bugzilla_noreply＠suse.com 19 Oct '24

19 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1217774 Bug ID: 1217774 Summary: qt6-webengine qtpdf.index reproducible builds Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: Development Blocker: --- While working on reproducible builds for openSUSE, I found that our qt6-webengine / qt6-webengine-docs-html subpackage varied between builds in /usr/share/doc/qt6/qtpdf/qtpdf.index See diff at https://rb.zq1.de/compare.factory-20230830/diffs/qt6-webengine-compare.out You probably need to build with osc build -M docs -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1227174] New: VUL-0: CVE-2024-39705: python-nltk: remote code execution through the integrated data package download functionality
by bugzilla_noreply＠suse.com 18 Oct '24

18 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1227174 Bug ID: 1227174 Summary: VUL-0: CVE-2024-39705: python-nltk: remote code execution through the integrated data package download functionality Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/412359/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: python-maintainers(a)suse.com Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: camila.matos(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- NLTK through 3.8.1 allows remote code execution if untrusted packages have pickled Python code, and the integrated data package download functionality is used. This affects, for example, averaged_perceptron_tagger and punkt. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-39705 https://www.cve.org/CVERecord?id=CVE-2024-39705 https://github.com/nltk/nltk/issues/2522 https://github.com/nltk/nltk/issues/3266 https://bugzilla.redhat.com/show_bug.cgi?id=2294671 -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1227311] New: Upgrade of mariadb from 11.2.3 to 11.4.2 will fail if ssl can't be verified.
by bugzilla_noreply＠suse.com 18 Oct '24

18 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1227311 Bug ID: 1227311 Summary: Upgrade of mariadb from 11.2.3 to 11.4.2 will fail if ssl can't be verified. Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: silentworks(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The recent release of mariadb-11.4.2 creates a quite annoying issue, the installation script will create /var/lib/misc/.mariadb_run_upgrade, since a mysql_upgrade should be done with the version change. The next time systemd tries to start mariadb /usr/libexec/mysql/mysql-systemd-helper sees that .mariadb_run_upgrade exists, and that enables the upgrade flag. Here comes the problem, since mariadb 11.3 the upgrade function has ssl verification enabled by default. So if the mariadb server has any self-signed cert, any custom cert, or the hostname doesn't match, the verification will fail. And hence the upgrade and the script will fail. mysql_upgrade will refuse the connection, and the script isn't designed to handle this. --disable-ssl-verify-server-cert should be passed by default in the script In line 119: "if /usr/bin/mysql_upgrade --disable-ssl-verify-server-cert" And i don't know if the mysqladmin behaves in he same way (didn't check). I think in some situations the .mariadb_run_upgrade may not be deleted too, even if the upgrade finished, that could cause a loop that will cause the upgrade script to run everytime mariadb is started from systemd, which is what happened to me and i had to delete the .mariadb_run_upgrade manually, but i'm not sure why. (i did the upgrade manually afterwards) -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1221890] New: Audacious crashes when opening file dialog since Plasma 6
by bugzilla_noreply＠suse.com 16 Oct '24

16 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1221890 Bug ID: 1221890 Summary: Audacious crashes when opening file dialog since Plasma 6 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: foss(a)grueninger.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After I installed Plasma and KF 6, the media player crashes when opening the file dialog (to open or append tracks). Steps to reproduce: 1. Open Audacious 2. Press Ctrl + o to open a audio file. 3. Dialog flashes and Audacious is terminated It seems to be a packaging issue, upstream has no idea. See the according issue: https://github.com/orgs/audacious-media-player/discussions/122 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1219031] New: Multiple cross-arm-none-gcc13 bugs
by bugzilla_noreply＠suse.com 16 Oct '24

16 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1219031 Bug ID: 1219031 Summary: Multiple cross-arm-none-gcc13 bugs Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: rguenther(a)suse.com Reporter: mrueckert(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- 1. the package does not require libisl23 libmpc3 so the binary does not run. 2. package not required to provide required headers: ``` Compiling: keyboards/moonlander/matrix.c In file included from ./lib/chibios/os/hal/osal/rt-nil/osal.h:29, from ./lib/chibios/os/hal/include/hal.h:30, from platforms/chibios/platform_deps.h:18, from quantum/quantum.h:18, from keyboards/moonlander/moonlander.h:21, from keyboards/moonlander/matrix.c:19: /usr/lib64/gcc/arm-none-eabi/13/include/stdint.h:9:16: fatal error: stdint.h: No such file or directory 9 | # include_next <stdint.h> | ^~~~~~~~~~ compilation terminated. [ERRORS] | | | gmake[1]: *** [builddefs/common_rules.mk:361: .build/obj_moonlander_darix-v3/matrix.o] Error 1 Make finished with errors gmake: *** [Makefile:392: moonlander:darix-v3] Error 1 ``` -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1214915] New: Please build Qt5 with configure option -xcb-native-painting
by bugzilla_noreply＠suse.com 16 Oct '24

16 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1214915 Bug ID: 1214915 Summary: Please build Qt5 with configure option -xcb-native-painting Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: Woebbeking(a)web.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, this is an experimental feature to let Qt5 paint as Qt4 did. This improves performance of Qt5 applications under X2Go a lot. First this option was enabled by default but some years later it was disabled to reduce the size of the platform plugin libqxcb.so a little bit. You don't have to worry that you brake something if you enable this option as the user also have to set the environment variable QT_XCB_NATIVE_PAINTING to make it work. Thanks in advance! Cheers, André -- You are receiving this mail because: You are on the CC list for the bug.

1 5