You've done a spectacular job deleting all the required information about the machine.
Why would you do that? Lucas <lu...@sexy.is> wrote: > Hello bugs@, > > as the subject says, I'm getting that message in dmesg and the OS seems > quite broken. It started to happen after resuming from hibernate. The > dmesg is almost the same as [0], but I installed an additional 8GB DIMM > and changed the disk since then. > > As for how broken the system is, I couldn't unlock my X session, then > tried to log in from the console, getting something like "Login: > Resource unavailable"; can't recall the exact message and now is long > lost in the scrollback. After being able to log in as my user, I get > "ksh: can't create pipe - try again", probably when it tries to read > the file pointed by ENV. Switching to root, that message doesn't show > up. I can't pipe processes, getting "ksh: cannot fork - try again" even > with ": | :", and one second after that the shell exits on its own. I > can't drop into ddb as sadly I forgot to set ddb.console=1. vmstat > reports: > > procs memory page disks traps cpu > r s avm fre flt re pi po fr sr sd0 sd1 int sys cs us sy id > 0 295 988M 9871M 413 0 0 0 0 0 16 16 89 2137 655 1 1 98 > > Also, every now and then I can't run processes at all. The system is > still running tho, so I can run some additionals commands to help > gathering information, but is my main laptop so I'd like to recover it > soonish. I can afford a day or two. > > Inspecting dmesg, the subject's message starts appearing just after I > try to resume, I think, based on uhubs being detached, attached, and > detached again. The acpi messages repeats 101 times, the last 5 times > in between uhub* attach messages. Also, just before current boot, it > reads > > root on rd0a swap on rd0b dump on rd0b > syncing disk...at pms > OpenBSD 6.8-current (GENERIC.MP) #265 Sat Jan 9 01:54:38 MST 2021 > dera...@amd64.openbsd.org:/usrc/src/sys/arch/amd64/compile/GENERIC.mp > > which seems like the final sequence of sysupgrade, except for the > suspicious "at pms". > > For completeness, transcribed as I can't SSH into it, the memory and > disk related changes now read: > > ... > real mem = 12534018048 (11953MB) > avail mem = 12138836968 (11576MB) > ... > ahci0 at pci0 dev 31 function 2 "Intel 7 Series AHCI" rev 0x04: msi, AHCI 1.3 > ahci0: port 0: 6.0Gb/s > scsibus1 at ahci0: 32 targets > sd0 at scsibus1 targ 0 lun 0: <ATA, CT480BX500SSD1, M6C> naa.0000000000000000 > sd0: 457862MB, 512 bytes/sector, 937703088 sectors, thin > ichiic0 at pci0 dev 31 function 3 "Intel 7 Series SMBus" rev 0x04: apic 2 int > 18 > iic0 at ichiic0 > spdmem0 at iic0 addr 0x50: 8GB DDR3 SDRAM PC3-12800 SO-DIMM > spdmem0 at iic0 addr 0x51: 4GB DDR3 SDRAM PC3-12800 SO-DIMM > ... > vscsi0 at root > scsibus at vscsi0: 256 targets > softraid0 at root > scsibus3 at softraid0: 256 targets > sd1 at scsibus3 targ 1 lun 0: <OPENBSD, SR CRYPTO, 006> > sd1: 457860MB, 512 bytes/sector, 937697393 sectors > root on sd1a (af42e96f6d19d2e8.a) swap on sd1b dump on sd1b > ... > > The lines matching acpi for current boot are > > acpi0 at bios0: ACPI 4.0 > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP SLIC TCPA SSDT SSDT SSDT HPET APIC MCFG ECDT FPDT > ASF! UEFI UEFI POAT SSDT SSDT DMAR UEFI > acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP3(S4) XCHI(S3) EHC1(S3) > EHC2(S#) HDEF(S4) > acpitimer0 at acpi0: 3579545 Hz, 24 bits > acpihpet0 at acpi0: 14318179 Hz > acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat > acpimcfg0: addr 0xf8000000, bus 0-63 > acpiec at acpi0 > acpiprt0 at acpi0: bus 0 (PCI0) > acpiprt1 at acpi0: bus -1 (PEG_) > acpiprt2 at acpi0: bus 2 (EXP1) > acpiprt3 at acpi0: bus 3 (EXP2) > acpiprt4 at acpi0: bus 4 (EXP3) > acpibtn0 ar acpi0: LID_ > acpibtn1 at acpi0: SLPB > acpipci0 at acpi0 PCI0: 0x00000000 0x00000011 0x00000001 > acpicmos0 at acpi0 > tpm0 at acpi0 TPM_ addr 0xfed40000/0x5000, device 0x00000104a rev 0x4e > acpibat0 at acpi0: BAT0 model "45N1029" serial 14305 type LION oem "LGC" > acpiac0 at acpi0: AC unit online > acpithinkpad0 ar acpi0: version 1.0 > "PNP0C14" at acpi0 not configured > "PNP0C14" at acpi0 not configured > acpicpu0 at acpi0 C2(350@80 mwait.1@0x20), C1(1000@1 mwait.1), PSS > acpicpu1 at acpi0 C2(350@80 mwait.1@0x20), C1(1000@1 mwait.1), PSS > acpipwrres0 at acpi0: PUBS, resource for XHCI, EHC1, EHC2 > acpitz0 at acpi0: critical temperature is 103 degC > acpidock0 at acpi0: GDCK not docked (0) > acpivideo0 at acpi0: VID_ > acpivout0 at acpivideo0: LCD0 > acpivideo1 at acpi0: VID_ > acpi0: unable to map iospace > [last message repeated x101] > > -Lucas > > [0]: https://marc.info/?l=openbsd-bugs&m=158622837109003&w=2 >
