Re: Firefox, Chrome, Libreoffice bogus syscall on -current
On 2024-01-01, Ax0n wrote: > On Fri, Dec 29, 2023 at 7:33 PM Stuart Henderson > wrote: > >> Pity, without the deletes a transcript of a run of pkg_add -u -v >> might have shown why the packages didn't get updated. They should have, >> and in most cases they do. >> > > Here's the pkg_add -uiv output that I saved while removing stuff. There's a > bit of detail there, maybe enough to unwind the problem? > > https://gist.github.com/n0xa/934776b75ef520738c0fca16aa8b1071 > pkg_add needs at least -vvv to debug update issues. (There will be too much output for nearly any scrollback buffer so will need running under script(1) or alternative). -- Please keep replies on the mailing list.
Re: Firefox, Chrome, Libreoffice bogus syscall on -current
On Fri, Dec 29, 2023 at 7:33 PM Stuart Henderson wrote: > Pity, without the deletes a transcript of a run of pkg_add -u -v > might have shown why the packages didn't get updated. They should have, > and in most cases they do. > Here's the pkg_add -uiv output that I saved while removing stuff. There's a bit of detail there, maybe enough to unwind the problem? https://gist.github.com/n0xa/934776b75ef520738c0fca16aa8b1071
Re: Firefox, Chrome, Libreoffice bogus syscall on -current
On 2023-12-29, Ax0n wrote: > On Fri, Dec 29, 2023, 11:21 Theo de Raadt wrote: > >> Then your machine is not -current, not by a long shot. >> >> We moved to libc.so.98.0 on Dec 12. >> >> At least two rounds of new packages have shown up since then. >> >> I do believe there are circumstances where pkg_add fails to update >> library packages. > > > It turns out there was a list of 100 some packages that couldn't be > upgraded with pkg_add -u and I just wasn't reading it, as the heart of the > message scrolled way off the screen. > > I programmatically pkg_delete'd those and those which relied upon them, and > re-installed only what I really needed and all is well in the world once > again. Pity, without the deletes a transcript of a run of pkg_add -u -v might have shown why the packages didn't get updated. They should have, and in most cases they do.
Re: Firefox, Chrome, Libreoffice bogus syscall on -current
On Fri, Dec 29, 2023, 11:21 Theo de Raadt wrote: > Then your machine is not -current, not by a long shot. > > We moved to libc.so.98.0 on Dec 12. > > At least two rounds of new packages have shown up since then. > > I do believe there are circumstances where pkg_add fails to update > library packages. It turns out there was a list of 100 some packages that couldn't be upgraded with pkg_add -u and I just wasn't reading it, as the heart of the message scrolled way off the screen. I programmatically pkg_delete'd those and those which relied upon them, and re-installed only what I really needed and all is well in the world once again. Sorry for the distraction, and thanks for the guidance. Even this little adventure was still smoother than any other OS I've used.
Re: Firefox, Chrome, Libreoffice bogus syscall on -current
Ax0n wrote: > And yes, quite a lot of stuff referencing libc.so.97.1 in /usr/local - 223 > files in bin, 361 in lib, 0 in sbin. Then your machine is not -current, not by a long shot. We moved to libc.so.98.0 on Dec 12. At least two rounds of new packages have shown up since then. I do believe there are circumstances where pkg_add fails to update library packages.
Re: Firefox, Chrome, Libreoffice bogus syscall on -current
On Thu, Dec 28, 2023, 11:00 Stuart Henderson
wrote:
Not sure how much core dumps will help, but if you can try running
the binaries with problems with LD_DEBUG set in the environment (to
anything) and capture output (e.g. using script(1) as it will likely be
copious) that might give clues.
I'll likely try another new snapshot today, then try the above if it
persists.
How are you updating packages / which mirror? Do you have anything left
in /usr/local/{bin,sbin,lib} etc which still reference any libc.so.97?
Upgrade process:
doas sysupgrade
login
doas sysmerge
doas pkg_add -uiv
doas reboot
/etc/installurl is http://mirrors.sonic.net/pub/OpenBSD
And yes, quite a lot of stuff referencing libc.so.97.1 in /usr/local - 223
files in bin, 361 in lib, 0 in sbin.
I've been running -current and just rolling snapshots on this machine since
March 2021, somewhere between 6.8 and 6.9-RELEASE. It was initially
configured with softraid crypto the old manual-intervention-during-install
way. Several times along the way, I've ended up with a box that thinks it's
on -RELEASE but is a chimaera of -CURRENT snapshot stuff. The most recent
happened in the days leading up to 7.4-RELEASE. In these cases, I just add
-s the sysupgrade and/or -D snap to pkg_add to get past it.
It's possible I need a fresh install. Everything is backed up weekly.
Are you doing anything unusual with LD_PRELOAD (e.g. using a socks
wrapper)?
No. Not at all.
Re: Firefox, Chrome, Libreoffice bogus syscall on -current
Stuart Henderson wrote:
> On 2023-12-27, Ax0n wrote:
> > I had been running #1471 since December 5th without issue, and this week
> > upgraded to the latest snapshot (#1567) after which some apps such as
> > Firefox won't run. They display "msyscall a8000 error" followed by a
> > core dump. dmesg(1) shows a bogus syscall. I did ensure that I had properly
> > sysmerged and updated packages.I waited until the next snapshot hit
> > mirrors, and verified that this issue persists with build #1572 and fresh
> > packages as well. Lenovo X1 Carbon Gen 8. dmesg in body. I can put core
> > dumps somewhere if it helps.
>
> Not sure how much core dumps will help, but if you can try running
> the binaries with problems with LD_DEBUG set in the environment (to
> anything) and capture output (e.g. using script(1) as it will likely be
> copious) that might give clues.
>
> How are you updating packages / which mirror? Do you have anything left
> in /usr/local/{bin,sbin,lib} etc which still reference any libc.so.97?
>
> Are you doing anything unusual with LD_PRELOAD (e.g. using a socks
> wrapper)?
ktrace -di
kdump | grep 'NAMI.*/lib'
You will see two libc.so
That's not good, and our ld.so is going to need to learn to handle this.
Re: Firefox, Chrome, Libreoffice bogus syscall on -current
On 2023-12-27, Ax0n wrote:
> I had been running #1471 since December 5th without issue, and this week
> upgraded to the latest snapshot (#1567) after which some apps such as
> Firefox won't run. They display "msyscall a8000 error" followed by a
> core dump. dmesg(1) shows a bogus syscall. I did ensure that I had properly
> sysmerged and updated packages.I waited until the next snapshot hit
> mirrors, and verified that this issue persists with build #1572 and fresh
> packages as well. Lenovo X1 Carbon Gen 8. dmesg in body. I can put core
> dumps somewhere if it helps.
Not sure how much core dumps will help, but if you can try running
the binaries with problems with LD_DEBUG set in the environment (to
anything) and capture output (e.g. using script(1) as it will likely be
copious) that might give clues.
How are you updating packages / which mirror? Do you have anything left
in /usr/local/{bin,sbin,lib} etc which still reference any libc.so.97?
Are you doing anything unusual with LD_PRELOAD (e.g. using a socks
wrapper)?
Re: Firefox, Chrome, Libreoffice bogus syscall on -current
b...@fea.st wrote: > On Thu, Dec 28, 2023, at 00:41, Ax0n wrote: > > I had been running #1471 since December 5th without issue, and this week > > upgraded to the latest snapshot (#1567) after which some apps such as > > Firefox won't run. They display "msyscall a8000 error" followed by a > > core dump. dmesg(1) shows a bogus syscall. I did ensure that I had properly > > sysmerged and updated packages.I waited until the next snapshot hit > > mirrors, and verified that this issue persists with build #1572 and fresh > > packages as well. Lenovo X1 Carbon Gen 8. dmesg in body. I can put core > > dumps somewhere if it helps. > > I'm on #1576 and both ungoogled-chromium and firefox work fine. The problem occurs when a package uses a library which has a DT_NEEDED reference to an older libc library, but the snapshot has moved to a new library major/minor version. Then ld.so loads both libraries, and that won't work. This DT_NEEDED stuff is very much designed to discourage any trend other than ossification.
Re: Firefox, Chrome, Libreoffice bogus syscall on -current
On Thu, Dec 28, 2023, at 00:41, Ax0n wrote: > I had been running #1471 since December 5th without issue, and this week > upgraded to the latest snapshot (#1567) after which some apps such as > Firefox won't run. They display "msyscall a8000 error" followed by a > core dump. dmesg(1) shows a bogus syscall. I did ensure that I had properly > sysmerged and updated packages.I waited until the next snapshot hit > mirrors, and verified that this issue persists with build #1572 and fresh > packages as well. Lenovo X1 Carbon Gen 8. dmesg in body. I can put core > dumps somewhere if it helps. I'm on #1576 and both ungoogled-chromium and firefox work fine.
Firefox, Chrome, Libreoffice bogus syscall on -current
I had been running #1471 since December 5th without issue, and this week upgraded to the latest snapshot (#1567) after which some apps such as Firefox won't run. They display "msyscall a8000 error" followed by a core dump. dmesg(1) shows a bogus syscall. I did ensure that I had properly sysmerged and updated packages.I waited until the next snapshot hit mirrors, and verified that this issue persists with build #1572 and fresh packages as well. Lenovo X1 Carbon Gen 8. dmesg in body. I can put core dumps somewhere if it helps. OpenBSD 7.4-current (GENERIC.MP) #1572: Wed Dec 27 03:22:15 MST 2023 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 16758042624 (15981MB) avail mem = 16230166528 (15478MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.2 @ 0x6cbac000 (70 entries) bios0: vendor LENOVO version "N2WET36W (1.26 )" date 03/25/2022 bios0: LENOVO 20U9S1QP00 efi0 at bios0: UEFI 2.7 efi0: Lenovo rev 0x1260 acpi0 at bios0: ACPI 6.1 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT SSDT SSDT SSDT SSDT TPM2 SSDT HPET APIC MCFG ECDT SSDT SSDT SSDT NHLT BOOT SSDT LPIT WSMT SSDT DBGP DBG2 MSDM BATB DMAR ASF! UEFI FPDT acpi0: wakeup devices GLAN(S4) XHC_(S3) XDCI(S4) HDAS(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) PXSX(S4) RP06(S4) PXSX(S4) RP07(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 2399 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i7-10610U CPU @ 1.80GHz, 1880.50 MHz, 06-8e-0c, patch 00f8 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,IBRS_ALL,SKIP_L1DFL,MDS_NO,TSX_CTRL,MISC_PKG_CT,ENERGY_FILT,FB_CLEAR,RRSBA,GDS_CTRL,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 4-way L2 cache, 8MB 64b/line 16-way L3 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 24MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i7-10610U CPU @ 1.80GHz, 1795.08 MHz, 06-8e-0c, patch 00f8 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,IBRS_ALL,SKIP_L1DFL,MDS_NO,TSX_CTRL,MISC_PKG_CT,ENERGY_FILT,FB_CLEAR,RRSBA,GDS_CTRL,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu1: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 4-way L2 cache, 8MB 64b/line 16-way L3 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Core(TM) i7-10610U CPU @ 1.80GHz, 1791.52 MHz, 06-8e-0c, patch 00f8 cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,IBRS_ALL,SKIP_L1DFL,MDS_NO,TSX_CTRL,MISC_PKG_CT,ENERGY_FILT,FB_CLEAR,RRSBA,GDS_CTRL,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu2: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 4-way L2 cache, 8MB 64b/line 16-way L3 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Core(TM) i7-10610U CPU @ 1.80GHz, 1791.22 MHz, 06-8e-0c, patch 00f8 cpu3:
