ssh check local and remote forwarding
Currently ssh -O check doesn't show active forwardings. Do you think it's possible to add this feature? To check if a local or remote forwarding is active? Something like this: ssh -O check -L 127.0.0.1:2000:127.0.0.1: -S /tmp/to_remote remote
Re: apm doesn't know AC state on APU1C
On Wed, Apr 26, 2023 at 08:48:00PM +0200, Jan Stary wrote: > On Apr 26 11:38:40, dera...@openbsd.org wrote: > > Jan Stary wrote: > > > > > On Apr 26 14:57:22, stu.li...@spacehopper.org wrote: > > > > On 2023-04-26, Jan Stary wrote: > > > > > This is current/amd64 on an APU1C (dmesg below). > > > > > While 'sysctl hw' knows hw.power=1, apm doesn't know: > > > > > > > > > > Battery state: absent, 0% remaining, unknown life estimate > > > > > AC adapter state: not known > > > > > Performance adjustment mode: auto (1000 MHz) > > > > > > > > > > Yes, apmd -A is running. > > > > > > > > > > Not that this matters much, the machine will always be on AC; > > > > > but it still seems strange for apm to not know. > > > > > > > > I don't expect the machine has bothered with a way to pass that > > > > information through to the OS. > > > > > > Does sysctl hw.power know through a different way than apm? > > > > Does your APU1C have acpi? > > Yes (dmesg below). Is that how sysctl hw gets it, as opposed to apm? > > Jan > no acpiac(4). > > OpenBSD 7.3-current (GENERIC.MP) #0: Wed Apr 26 12:48:53 CEST 2023 > h...@stary.stare.cz:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 2098511872 (2001MB) > avail mem = 2015346688 (1921MB) > random: good seed from bootblocks > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x7e16d820 (7 entries) > bios0: vendor coreboot version "4.0" date 09/08/2014 > bios0: PC Engines APU > acpi0 at bios0: ACPI 4.0 > acpi0: sleep states S0 S1 S3 S4 S5 > acpi0: tables DSDT FACP SPCR HPET APIC HEST SSDT SSDT SSDT > acpi0: wakeup devices AGPB(S4) HDMI(S4) PBR4(S4) PBR5(S4) PBR6(S4) PBR7(S4) > PE20(S4) PE21(S4) PE22(S4) PE23(S4) PIBR(S4) UOH1(S3) UOH2(S3) UOH3(S3) > UOH4(S3) UOH5(S3) [...] > acpitimer0 at acpi0: 3579545 Hz, 32 bits > acpihpet0 at acpi0: 14318180 Hz > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: AMD G-T40E Processor, 1000.02 MHz, 14-02-00 > cpu0: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,SSSE3,CX16,POPCNT,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,IBS,SKINIT,ITSC > cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 2-way I-cache > cpu0: 512KB 64b/line 16-way L2 cache > cpu0: smt 0, core 0, package 0 > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges > cpu0: apic clock running at 200MHz > cpu0: mwait min=64, max=64, IBE > cpu1 at mainbus0: apid 1 (application processor) > cpu1: AMD G-T40E Processor, 1000.02 MHz, 14-02-00 > cpu1: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,SSSE3,CX16,POPCNT,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,IBS,SKINIT,ITSC > cpu1: 32KB 64b/line 8-way D-cache, 32KB 64b/line 2-way I-cache > cpu1: 512KB 64b/line 16-way L2 cache > cpu1: smt 0, core 1, package 0 > ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins > acpiprt0 at acpi0: bus 0 (PCI0) > acpiprt1 at acpi0: bus -1 (AGPB) > acpiprt2 at acpi0: bus -1 (HDMI) > acpiprt3 at acpi0: bus 1 (PBR4) > acpiprt4 at acpi0: bus 2 (PBR5) > acpiprt5 at acpi0: bus 3 (PBR6) > acpiprt6 at acpi0: bus -1 (PBR7) > acpiprt7 at acpi0: bus 5 (PE20) > acpiprt8 at acpi0: bus -1 (PE21) > acpiprt9 at acpi0: bus -1 (PE22) > acpiprt10 at acpi0: bus -1 (PE23) > acpiprt11 at acpi0: bus 4 (PIBR) > acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001 > acpicmos0 at acpi0 > acpibtn0 at acpi0: PWRB > acpicpu0 at acpi0: C2(0@100 io@0x841), C1(@1 halt!), PSS > acpicpu1 at acpi0: C2(0@100 io@0x841), C1(@1 halt!), PSS > cpu0: 1000 MHz: speeds: 1000 800 MHz > pci0 at mainbus0 bus 0 > pchb0 at pci0 dev 0 function 0 "AMD 14h Host" rev 0x00 > ppb0 at pci0 dev 4 function 0 "AMD 14h PCIE" rev 0x00: msi > pci1 at ppb0 bus 1 > re0 at pci1 dev 0 function 0 "Realtek 8168" rev 0x06: RTL8168E/8111E > (0x2c00), msi, address 00:0d:b9:3d:bb:fc > rgephy0 at re0 phy 7: RTL8169S/8110S/8211 PHY, rev. 4 > ppb1 at pci0 dev 5 function 0 "AMD 14h PCIE" rev 0x00: msi > pci2 at ppb1 bus 2 > re1 at pci2 dev 0 function 0 "Realtek 8168" rev 0x06: RTL8168E/8111E > (0x2c00), msi, address 00:0d:b9:3d:bb:fd > rgephy1 at re1 phy 7: RTL8169S/8110S/8211 PHY, rev. 4 > ppb2 at pci0 dev 6 function 0 "AMD 14h PCIE" rev 0x00: msi > pci3 at ppb2 bus 3 > re2 at pci3 dev 0 function 0 "Realtek 8168" rev 0x06: RTL8168E/8111E > (0x2c00), msi, address 00:0d:b9:3d:bb:fe > rgephy2 at re2 phy 7: RTL8169S/8110S/8211 PHY, rev. 4 > ahci0 at pci0 dev 17 function 0 "ATI SBx00 SATA" rev 0x40: apic 2 int 19, > AHCI 1.2 > scsibus1 at ahci0: 32 targets > ohci0 at pci0 dev 18 function 0 "ATI SB700 USB" rev 0x00: apic 2 int 18, > version 1.0, legacy support > ehci0 at pci0 dev 18 function 2 "ATI SB700 USB2" rev 0x00: apic 2 int 17 > usb0 at ehci0: USB revision 2.0 > uhub0 at usb0 configuration 1 interface 0 "ATI
Re: supermicro 5019D-FTN4 server with AMD EPYC 3251 SoC Processor
On 30.6.2021. 15:34, Denis Fondras wrote: > Le Tue, Jun 29, 2021 at 07:46:55PM +0200, EdaSky a écrit : >> Good day everyone >> >> Does anyone use supermicro 5019D-FTN4 server with AMD EPYC 3251 SoC >> Processor? >> >> https://www.supermicro.com/Aplus/system/Embedded/AS-5019D-FTN4.cfm >> >> Experience and dmesg would be perfect. >> > > Experience is perfect so far. I am really happy with it as BGP edge. > > Hi Denis, are you still happy with this box? Is amd64 OpenBSD stable on it? Are you happy with pf or forwarding performance ? As in your dmesg, I thought of putting 4 port ixl(4) card in it, 1G sfp uplink, 10G for internal vlans and em(4) for pfsync... > OpenBSD 6.9-current (GENERIC.MP) #20: Sun May 16 00:32:45 MDT 2021 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 34228760576 (32643MB) > avail mem = 33175949312 (31639MB) > random: good seed from bootblocks > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xdab19000 (51 entries) > bios0: vendor American Megatrends Inc. version "1.0c" date 06/30/2020 > bios0: Supermicro AS -5019D-FTN4 > acpi0 at bios0: ACPI 6.1 > acpi0: sleep states S0 S5 > acpi0: tables DSDT FACP APIC FPDT FIDT SSDT SPMI SSDT MCFG SSDT CRAT CDIT > BERT EINJ HEST HPET SSDT UEFI SSDT WSMT > acpi0: wakeup devices S0D0(S3) S0D1(S3) S0D2(S3) S0D3(S3) S1D0(S3) S1D1(S3) > S1D2(S3) S1D3(S3) > acpitimer0 at acpi0: 3579545 Hz, 32 bits > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: AMD EPYC 3251 8-Core Processor, 2500.55 MHz, 17-01-02 > cpu0: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,RDSEED,ADX,SMAP,CLFLUSHOPT,SHA,IBPB,XSAVEOPT,XSAVEC,XGETBV1,XSAVES > cpu0: 64KB 64b/line 4-way I-cache, 32KB 64b/line 8-way D-cache, 512KB > 64b/line 8-way L2 cache > cpu0: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative > cpu0: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative > cpu0: smt 0, core 0, package 0 > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges > cpu0: apic clock running at 99MHz > cpu0: mwait min=64, max=64, C-substates=1.1, IBE > cpu1 at mainbus0: apid 2 (application processor) > cpu1: AMD EPYC 3251 8-Core Processor, 2500.01 MHz, 17-01-02 > cpu1: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,RDSEED,ADX,SMAP,CLFLUSHOPT,SHA,IBPB,XSAVEOPT,XSAVEC,XGETBV1,XSAVES > cpu1: 64KB 64b/line 4-way I-cache, 32KB 64b/line 8-way D-cache, 512KB > 64b/line 8-way L2 cache > cpu1: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative > cpu1: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative > cpu1: smt 0, core 1, package 0 > cpu2 at mainbus0: apid 4 (application processor) > cpu2: AMD EPYC 3251 8-Core Processor, 2500.01 MHz, 17-01-02 > cpu2: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,RDSEED,ADX,SMAP,CLFLUSHOPT,SHA,IBPB,XSAVEOPT,XSAVEC,XGETBV1,XSAVES > cpu2: 64KB 64b/line 4-way I-cache, 32KB 64b/line 8-way D-cache, 512KB > 64b/line 8-way L2 cache > cpu2: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative > cpu2: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative > cpu2: smt 0, core 2, package 0 > cpu3 at mainbus0: apid 6 (application processor) > cpu3: AMD EPYC 3251 8-Core Processor, 2500.01 MHz, 17-01-02 > cpu3: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,RDSEED,ADX,SMAP,CLFLUSHOPT,SHA,IBPB,XSAVEOPT,XSAVEC,XGETBV1,XSAVES > cpu3: 64KB 64b/line 4-way I-cache, 32KB 64b/line 8-way D-cache, 512KB > 64b/line 8-way L2 cache > cpu3: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative > cpu3: DTLB 64 4KB entries fully associative, 64 4MB entries fully a
T480s: USB port gets disabled
Hi, i have bought a second hand Lenovo Thinkpad T480s and installed OpenBSD 7.3 on it using UEFI without CSM. The most important features of the laptop works ok, except the left hand USB A port.The dmesg says: uhub0: device problem, disabling port 1 While i found many similar reports, their solutions did not helps for me (I have tried UEFI+CSM so far) As the laptop have only 2 USB-A port, it is important to have both in good working condition. Do you have any idea what should i try? Thank You! --Z-- Complete dmesg: OpenBSD 7.3 (GENERIC.MP) #1125: Sat Mar 25 10:36:29 MDT 2023 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17018585088 (16230MB) avail mem = 16483405824 (15719MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0xda65 (62 entries) bios0: vendor LENOVO version "N22ET76W (1.53 )" date 01/04/2023 bios0: LENOVO 20L8S2SX1H efi0 at bios0: UEFI 2.5 efi0: Lenovo rev 0x1530 acpi0 at bios0: ACPI 5.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT SSDT TPM2 UEFI SSDT SSDT HPET APIC MCFG ECDT SSDT SSDT BOOT BATB SLIC SSDT SSDT SSDT LPIT WSMT SSDT SSDT SSDT DBGP DBG2 MSDM DMAR ASF! FPDT BGRT UEFI 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-8650U CPU @ 1.90GHz, 1496.94 MHz, 06-8e-0a 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,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN 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-8650U CPU @ 1.90GHz, 1270.13 MHz, 06-8e-0a 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,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN 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-8650U CPU @ 1.90GHz, 1105.51 MHz, 06-8e-0a 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,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN 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-8650U CPU @ 1.90GHz, 998.66 MHz, 06-8e-0a cpu3: 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,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu3: 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 cpu3: smt 0, core 3, package 0 ioapic0 at mainbus0: apid 2 pa 0xfe
A messed-up fresh install due to a careless user
Hello, I’m blind, and got sighted help to install OpenBSD on the machine which should become a new router. Unfortunately, I was stupid enough to detach the USB stick I booted from, before I was to hit R for the reboot. The result was that the last selection disappeared due to the detach message from the kernel, and I didn’t manage to get it back. The only way I thaught could be used for reboot was to hit ctrl+Z, and then type reboot. And it “worked”. When I connected the machine to the LAN afterwords, I didn’t get contact. After trying a few things, I finally got an IP on it, with the correct hostname. (I connected a keyboard, logged in as root, and configured one of the interfaces with ifconfig $if autoconf.) I’ve good expereince doing so without braille. So the machine got an IP, but still no contact, either with ping or ssh. I then realized that mandatory files has not been written, including the hostname.if file for the NIC used durring install. And I guess others too. :-) Which files are actually written when rebooting the corret way? I’ve OpenBSD 7.3 installed on both a arm64 and a i386 machine. Can I use the missing files from one of those? I should be able to copy them to a USB stick, and mount it and get the files in place without sighted help. And the network interface can be configured with dhcp for now. As soon as the machine is on the lan, I’ll ssh into it from a linux machine with a braille display. Regards, Martin PS: I’ve now learned that one should reboot _BEFORE_ detaching any external device when the installer is still running. :-)
Re: A messed-up fresh install due to a careless user
If that's a new install, may as well just redo it. The install is really fast, so this way you are sure you have a clean system and NOT one that you may have problem down the road, specially if that's your first time. That's what I would do anyway. Compare to any other IS, the install for OpenBSD is the fastest I ever seen, except may be NixOS when you move it to a new system. (; On 4/27/23 5:31 PM, Odd Martin Baanrud wrote: Hello, I’m blind, and got sighted help to install OpenBSD on the machine which should become a new router. Unfortunately, I was stupid enough to detach the USB stick I booted from, before I was to hit R for the reboot. The result was that the last selection disappeared due to the detach message from the kernel, and I didn’t manage to get it back. The only way I thaught could be used for reboot was to hit ctrl+Z, and then type reboot. And it “worked”. When I connected the machine to the LAN afterwords, I didn’t get contact. After trying a few things, I finally got an IP on it, with the correct hostname. (I connected a keyboard, logged in as root, and configured one of the interfaces with ifconfig $if autoconf.) I’ve good expereince doing so without braille. So the machine got an IP, but still no contact, either with ping or ssh. I then realized that mandatory files has not been written, including the hostname.if file for the NIC used durring install. And I guess others too. :-) Which files are actually written when rebooting the corret way? I’ve OpenBSD 7.3 installed on both a arm64 and a i386 machine. Can I use the missing files from one of those? I should be able to copy them to a USB stick, and mount it and get the files in place without sighted help. And the network interface can be configured with dhcp for now. As soon as the machine is on the lan, I’ll ssh into it from a linux machine with a braille display. Regards, Martin PS: I’ve now learned that one should reboot _BEFORE_ detaching any external device when the installer is still running. :-)
Re: A messed-up fresh install due to a careless user
Hello Daniel, The problem is, as I told, that I’m blind. I don’t have a screen at home, and it’s not easy to bring it to someone who has. All went just fine until it was time to reboot. So if someone could tell me what is missing, I guess it should work to get in the missing files from another install of the same version. (7.3) Regards, Martin
Re: OpenBSD 7.2 on Oracle Cloud
On Tue, Apr 25, 2023 at 10:53 PM Aaron Mason wrote:
>
> On Mon, Apr 24, 2023 at 3:47 PM Aaron Mason wrote:
> >
> > On Fri, Apr 21, 2023 at 2:50 PM Aaron Mason
> > wrote:
> > >
> > > On Fri, Apr 21, 2023 at 1:39 PM Aaron Mason
> > > wrote:
> > > >
> > > > On Fri, Apr 7, 2023 at 3:25 AM Antun Matanović
> > > > wrote:
> > > > >
> > > > > On Thu, 6 Apr 2023 at 12:55, Fabio Martins wrote:
> > > > > >
> > > > > > Try to add an entry in grub like in this article:
> > > > > >
> > > > > > https://raby.sh/installing-openbsd-on-ovhs-vps-2016-kvm-machines.html
> > > > >
> > > > > I have tried that, but it did not resolve the issue. Sorry I forgot to
> > > > > mention it originally.
> > > > >
> > > > > On Thu, 6 Apr 2023 at 14:24, Janne Johansson
> > > > > wrote:
> > > > > >
> > > > > > That is very much not the same issue. The arm64 instances on Oracle
> > > > > > finds the correct kernel and boots it, it just crashes at or after
> > > > > > the
> > > > > > scsi attachment.
> > > > >
> > > > > This has been my experience as well, except on the amd64 instance,
> > > > > haven't tried arm64.
> > > > >
> > > >
> > > > Yeah I'm getting the same thing. Trying a build in QEMU and
> > > > transferring in to see if that helps. Will report back.
> > > >
> > >
> > > Ok, good news, it still crashes at the same spot, but this time I've
> > > got more data. Copying in tech@ - if I've forgotten anything let me
> > > know and I'll fire up a fresh instance.
> > >
> > > [REDACTED]
> > > vioscsi_req_done(e,80024a00,fd803f81c338,e,80024a00,800
> > > d3228) at vioscsi_req_done+0x26
> > > [REDACTED]
> >
> > Ok, so based on the trace I got, I was able to trace the stop itself
> > back to line 299 of vioscsi.c (thank. you. random relink. And
> > anonymous CVS):
> >
> >293 vioscsi_req_done(struct vioscsi_softc *sc, struct virtio_softc *vsc,
> >294 struct vioscsi_req *vr)
> >295 {
> >296 struct scsi_xfer *xs = vr->vr_xs;
> >297 DPRINTF("vioscsi_req_done: enter vr: %p xs: %p\n", vr, xs);
> >298
> > -->299 int isread = !!(xs->flags & SCSI_DATA_IN);
> >300 bus_dmamap_sync(vsc->sc_dmat, vr->vr_control,
> >301 offsetof(struct vioscsi_req, vr_req),
> >302 sizeof(struct virtio_scsi_req_hdr),
> >303 BUS_DMASYNC_POSTWRITE);
> >
> > Maybe if I follow the rabbit hole enough, I might find out what's
> > going wrong between the driver and OCI. I've got a day off tomorrow
> > (yay for war I guess), I'll give it a bash and see where we end up.
> >
> > --
> > Aaron Mason - Programmer, open source addict
> > I've taken my software vows - for beta or for worse
>
> I enabled debugging on the vioscsi driver, rebuilt the RAMDISK kernel
> with those drivers enabled, and got this:
>
> vioscsi0 at virtio1: qsize 128
> scsibus0 at vioscsi0: 255 targets
> vioscsi_req_get: 0xfd803f80d338
> vioscsi_scsi_cmd: enter
> vioscsi_scsi_cmd: polling...
> vioscsi_scsi_cmd: polling timeout
> vioscsi_scsi_cmd: done (timeout=0)
> vioscsi_scsi_cmd: enter
> vioscsi_scsi_cmd: polling...
> vioscsi_vq_done: enter
> vioscsi_vq_done: slot=127
> vioscsi_req_done: enter vr: 0xfd803f80d338 xs: 0xfd803f8a5e58
> vioscsi_req_done: done 0, 2, 0
> vioscsi_vq_done: slot=127
> vioscsi_req_done: enter vr: 0xfd803f80d338 xs: 0x0
> uvm_fault(0x813ec2e0, 0x8, 0, 1) -> e
> fatal page fault in supervisor mode
> trap type 6 code 0 rip 810e6190 cs 8 rflags 10286 cr2 8 cpl e
> rsp 81606670
> gsbase 0x813dfff0 kgsbase 0x0
> panic: trap type 6, code=0, pc=810e6190
>
> That "xs: 0x0" bit feels like a clue. It should be trivial to pick up
> and handle, but what would be the correct way to handle that?
>
> If I have it return if "xs" is found to be NULL, it continues - the
> debugging suggests it goes through each possible target before
> finishing up. I don't know if that's correct, but it seems to continue
> booting after that even if my example didn't detect the drive with the
> kernel I built (I used the RAMDISK kernel and it was pretty stripped
> down).
>
> I'm about to attempt a -STABLE build (I've got 7.3 installed and thus
> can't yet build a snapshot, but I will do that if this test succeeds)
> - here's the patch that hopefully fixes the problem. (and hopefully
> gmail doesn't clobber the tabs)
>
> Index: sys/dev/pv/vioscsi.c
> ===
> RCS file: /cvs/src/sys/dev/pv/vioscsi.c,v
> retrieving revision 1.30
> diff -u -p -u -p -r1.30 vioscsi.c
> --- sys/dev/pv/vioscsi.c 16 Apr 2022 19:19:59 - 1.30
> +++ sys/dev/pv/vioscsi.c 25 Apr 2023 12:51:16 -
> @@ -296,6 +296,7 @@ vioscsi_req_done(struct vioscsi_softc *s
> struct scsi_xfer *xs = vr->vr_xs;
> DPRINTF("vioscsi_req_done: enter vr: %p xs: %p\n", vr, xs);
>
> + if (xs == NULL) return;
> int isread = !!(xs->flags & SCSI_DATA_IN);
> bus_dmamap_sync(vsc->sc_dmat, vr->vr_c
Re: OpenBSD 7.2 on Oracle Cloud
On Wed, Apr 26, 2023 at 7:36 AM Antun Matanović
wrote:
>
> I tested the patch you provided on my local qemu install and it booted
> successfully.
>
>> Index: sys/dev/pv/vioscsi.c
>> ===
>> RCS file: /cvs/src/sys/dev/pv/vioscsi.c,v
>> retrieving revision 1.30
>> diff -u -p -u -p -r1.30 vioscsi.c
>> --- sys/dev/pv/vioscsi.c 16 Apr 2022 19:19:59 - 1.30
>> +++ sys/dev/pv/vioscsi.c 25 Apr 2023 12:51:16 -
>> @@ -296,6 +296,7 @@ vioscsi_req_done(struct vioscsi_softc *s
>> struct scsi_xfer *xs = vr->vr_xs;
>> DPRINTF("vioscsi_req_done: enter vr: %p xs: %p\n", vr, xs);
>>
>>
>> + if (xs == NULL) return;
>> int isread = !!(xs->flags & SCSI_DATA_IN);
>> bus_dmamap_sync(vsc->sc_dmat, vr->vr_control,
>> offsetof(struct vioscsi_req, vr_req),
>>
Sorry just got this email - it got caught in gmail's spam filter. I
managed to test it in OCI as well, and bsd.rd boots and detects the
virtual disk without issue.
--
Aaron Mason - Programmer, open source addict
I've taken my software vows - for beta or for worse
Minimum install size
In the OpenBSD FAQ, in the Installation Guide section, it says "OpenBSD can be installed in as little as 512MB, but using a device that small is something for advanced users". https://www.openbsd.org/faq/faq4.html#Partitioning In fact, the installation of only the kernel and base73.tgz required 629MB for i386 and 1GB for amd64. For example, if I delete the files under /usr/share/relink, I can get within 512MB, but this is not a desirable installation method, is it? Yoshihiro Kawamata https://fuguita.org
