Re: sysupgrade fails due to "CHECK AND RESET DATE" ?

2021-10-18 Thread kasak



19.10.2021 09:41, Otto Moerbeek пишет:

On Tue, Oct 19, 2021 at 09:30:47AM +0300, kasak wrote:


19.10.2021 08:45, Otto Moerbeek пишет:

On Mon, Oct 18, 2021 at 11:18:20PM +0300, kasak wrote:


Hello everyone!

I have one mini router, made from gigabyte GB-SBCAP4200 barebone

It has nothing special. Just base openbsd, without any additional packages
and modifications.

for some reason, sysupgrade does not upgrade this system.
It successfully boot new kernel, but do not process the upgrade, Just load
6.9 back.

This is dmesg from loading 7.0 and further:

OpenBSD 7.0 (RAMDISK_CD) #219: Thu Sep 30 14:32:42 MDT 2021
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
real mem = 8415617024 (8025MB)
avail mem = 8156545024 (7778MB)
random: good seed from bootblocks
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x79db7000 (50 entries)
bios0: vendor American Megatrends Inc. version "F1" date 06/11/2018
bios0: Gigabyte Technology Co., Ltd. Default string
acpi0 at bios0: ACPI 6.0
acpi0: tables DSDT FACP FPDT FIDT MCFG DBG2 DBGP HPET LPIT APIC NPKT PRAM
WSMT SSDT SSDT SSDT SSDT SSDT SSDT SSDT UEFI TPM2 WDAT
acpihpet0 at acpi0: 1920 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Pentium(R) CPU N4200 @ 1.10GHz, 1097.47 MHz, 06-5c-09
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,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
cpu0: 1MB 64b/line 16-way L2 cache
cpu0: apic clock running at 19MHz
cpu0: mwait min=64, max=64, C-substates=0.2.0.2.4.2.1.1, IBE
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 120 pins
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (RP01)
acpiprt2 at acpi0: bus -1 (RP02)
acpiprt3 at acpi0: bus 1 (RP03)
acpiprt4 at acpi0: bus 2 (RP04)
acpiprt5 at acpi0: bus 3 (RP05)
acpiprt6 at acpi0: bus 4 (RP06)
acpiec0 at acpi0: not present
acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001
acpicmos0 at acpi0
"PNP0C0C" at acpi0 not configured
aplgpio0 at acpi0 GPO0 uid 1 addr 0xd0c5/0x76c irq 14, 78 pins
aplgpio1 at acpi0 GPO1 uid 2 addr 0xd0c4/0x764 irq 14, 77 pins
aplgpio2 at acpi0 GPO2 uid 3 addr 0xd0c7/0x674 irq 14, 47 pins
aplgpio3 at acpi0 GPO3 uid 4 addr 0xd0c0/0x654 irq 14, 43 pins
"INT33A1" at acpi0 not configured
"MSFT0101" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
acpicpu at acpi0 not configured
acpipwrres at acpi0 not configured
acpitz at acpi0 not configured
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Apollo Lake Host" rev 0x0b
"Intel HD Graphics 505" rev 0x0b at pci0 dev 2 function 0 not configured
"Intel Apollo Lake HD Audio" rev 0x0b at pci0 dev 14 function 0 not
configured
"Intel Apollo Lake TXE" rev 0x0b at pci0 dev 15 function 0 not configured
ahci0 at pci0 dev 18 function 0 "Intel Apollo Lake AHCI" rev 0x0b: msi, AHCI
1.3.1
ahci0: PHY offline on port 0
ahci0: port 1: 6.0Gb/s
scsibus0 at ahci0: 32 targets
sd0 at scsibus0 targ 1 lun 0: 
naa.50026b7783a249ed
sd0: 228936MB, 512 bytes/sector, 468862128 sectors, thin
ppb0 at pci0 dev 19 function 0 "Intel Apollo Lake PCIE" rev 0xfb: msi
pci1 at ppb0 bus 1
ppb1 at pci0 dev 19 function 1 "Intel Apollo Lake PCIE" rev 0xfb: msi
pci2 at ppb1 bus 2
ppb2 at pci0 dev 19 function 2 "Intel Apollo Lake PCIE" rev 0xfb: msi
pci3 at ppb2 bus 3
re0 at pci3 dev 0 function 0 "Realtek 8168" rev 0x0c: RTL8168G/8111G
(0x4c00), msi, address e0:d5:5e:e7:50:4f
rgephy0 at re0 phy 7: RTL8251 PHY, rev. 0
ppb3 at pci0 dev 19 function 3 "Intel Apollo Lake PCIE" rev 0xfb: msi
pci4 at ppb3 bus 4
re1 at pci4 dev 0 function 0 "Realtek 8168" rev 0x0c: RTL8168G/8111G
(0x4c00), msi, address e0:d5:5e:e7:50:51
rgephy1 at re1 phy 7: RTL8251 PHY, rev. 0
xhci0 at pci0 dev 21 function 0 "Intel Apollo Lake xHCI" rev 0x0b: msi, xHCI
1.0
usb0 at xhci0: USB revision 3.0
uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev
3.00/1.00 addr 1
"Intel Apollo Lake LPC" rev 0x0b at pci0 dev 31 function 0 not configured
"Intel Apollo Lake SMBus" rev 0x0b at pci0 dev 31 function 1 not configured
isa0 at mainbus0
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
efifb at mainbus0 not configured
softraid0 at root
scsibus1 at softraid0: 256 targets
root on rd0a swap on rd0b dump on rd0b
WARNING: CHECK AND RESET THE DATE!
OpenBSD 6.9 (GENERIC.MP) #4: Tue Aug 10 08:12:23 MDT 2021
r...@syspatch-69-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8415617024 (8025MB)
avail mem = 8145182720 (7767MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mai

Re: sysupgrade fails due to "CHECK AND RESET DATE" ?

2021-10-18 Thread Otto Moerbeek
On Tue, Oct 19, 2021 at 09:30:47AM +0300, kasak wrote:

> 
> 19.10.2021 08:45, Otto Moerbeek пишет:
> > On Mon, Oct 18, 2021 at 11:18:20PM +0300, kasak wrote:
> > 
> > > Hello everyone!
> > > 
> > > I have one mini router, made from gigabyte GB-SBCAP4200 barebone
> > > 
> > > It has nothing special. Just base openbsd, without any additional packages
> > > and modifications.
> > > 
> > > for some reason, sysupgrade does not upgrade this system.
> > > It successfully boot new kernel, but do not process the upgrade, Just load
> > > 6.9 back.
> > > 
> > > This is dmesg from loading 7.0 and further:
> > > 
> > > OpenBSD 7.0 (RAMDISK_CD) #219: Thu Sep 30 14:32:42 MDT 2021
> > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
> > > real mem = 8415617024 (8025MB)
> > > avail mem = 8156545024 (7778MB)
> > > random: good seed from bootblocks
> > > mainbus0 at root
> > > bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x79db7000 (50 entries)
> > > bios0: vendor American Megatrends Inc. version "F1" date 06/11/2018
> > > bios0: Gigabyte Technology Co., Ltd. Default string
> > > acpi0 at bios0: ACPI 6.0
> > > acpi0: tables DSDT FACP FPDT FIDT MCFG DBG2 DBGP HPET LPIT APIC NPKT PRAM
> > > WSMT SSDT SSDT SSDT SSDT SSDT SSDT SSDT UEFI TPM2 WDAT
> > > acpihpet0 at acpi0: 1920 Hz
> > > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> > > cpu0 at mainbus0: apid 0 (boot processor)
> > > cpu0: Intel(R) Pentium(R) CPU N4200 @ 1.10GHz, 1097.47 MHz, 06-5c-09
> > > 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,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
> > > cpu0: 1MB 64b/line 16-way L2 cache
> > > cpu0: apic clock running at 19MHz
> > > cpu0: mwait min=64, max=64, C-substates=0.2.0.2.4.2.1.1, IBE
> > > cpu at mainbus0: not configured
> > > cpu at mainbus0: not configured
> > > cpu at mainbus0: not configured
> > > ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 120 pins
> > > acpiprt0 at acpi0: bus 0 (PCI0)
> > > acpiprt1 at acpi0: bus -1 (RP01)
> > > acpiprt2 at acpi0: bus -1 (RP02)
> > > acpiprt3 at acpi0: bus 1 (RP03)
> > > acpiprt4 at acpi0: bus 2 (RP04)
> > > acpiprt5 at acpi0: bus 3 (RP05)
> > > acpiprt6 at acpi0: bus 4 (RP06)
> > > acpiec0 at acpi0: not present
> > > acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001
> > > acpicmos0 at acpi0
> > > "PNP0C0C" at acpi0 not configured
> > > aplgpio0 at acpi0 GPO0 uid 1 addr 0xd0c5/0x76c irq 14, 78 pins
> > > aplgpio1 at acpi0 GPO1 uid 2 addr 0xd0c4/0x764 irq 14, 77 pins
> > > aplgpio2 at acpi0 GPO2 uid 3 addr 0xd0c7/0x674 irq 14, 47 pins
> > > aplgpio3 at acpi0 GPO3 uid 4 addr 0xd0c0/0x654 irq 14, 43 pins
> > > "INT33A1" at acpi0 not configured
> > > "MSFT0101" at acpi0 not configured
> > > "PNP0C0B" at acpi0 not configured
> > > acpicpu at acpi0 not configured
> > > acpipwrres at acpi0 not configured
> > > acpitz at acpi0 not configured
> > > pci0 at mainbus0 bus 0
> > > pchb0 at pci0 dev 0 function 0 "Intel Apollo Lake Host" rev 0x0b
> > > "Intel HD Graphics 505" rev 0x0b at pci0 dev 2 function 0 not configured
> > > "Intel Apollo Lake HD Audio" rev 0x0b at pci0 dev 14 function 0 not
> > > configured
> > > "Intel Apollo Lake TXE" rev 0x0b at pci0 dev 15 function 0 not configured
> > > ahci0 at pci0 dev 18 function 0 "Intel Apollo Lake AHCI" rev 0x0b: msi, 
> > > AHCI
> > > 1.3.1
> > > ahci0: PHY offline on port 0
> > > ahci0: port 1: 6.0Gb/s
> > > scsibus0 at ahci0: 32 targets
> > > sd0 at scsibus0 targ 1 lun 0: 
> > > naa.50026b7783a249ed
> > > sd0: 228936MB, 512 bytes/sector, 468862128 sectors, thin
> > > ppb0 at pci0 dev 19 function 0 "Intel Apollo Lake PCIE" rev 0xfb: msi
> > > pci1 at ppb0 bus 1
> > > ppb1 at pci0 dev 19 function 1 "Intel Apollo Lake PCIE" rev 0xfb: msi
> > > pci2 at ppb1 bus 2
> > > ppb2 at pci0 dev 19 function 2 "Intel Apollo Lake PCIE" rev 0xfb: msi
> > > pci3 at ppb2 bus 3
> > > re0 at pci3 dev 0 function 0 "Realtek 8168" rev 0x0c: RTL8168G/8111G
> > > (0x4c00), msi, address e0:d5:5e:e7:50:4f
> > > rgephy0 at re0 phy 7: RTL8251 PHY, rev. 0
> > > ppb3 at pci0 dev 19 function 3 "Intel Apollo Lake PCIE" rev 0xfb: msi
> > > pci4 at ppb3 bus 4
> > > re1 at pci4 dev 0 function 0 "Realtek 8168" rev 0x0c: RTL8168G/8111G
> > > (0x4c00), msi, address e0:d5:5e:e7:50:51
> > > rgephy1 at re1 phy 7: RTL8251 PHY, rev. 0
> > > xhci0 at pci0 dev 21 function 0 "Intel Apollo Lake xHCI" rev 0x0b: msi, 
> > > xHCI
> > > 1.0
> > > usb0 at xhci0: USB revision 3.0
> > > uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev
> > > 3.00/1.00 addr 1
> > > "Intel Apollo Lake LPC" rev 0x0b at pci0 dev 31 function 0 not configured
> > > "Intel Apollo Lake SMBus" rev 0x0b at pci0 dev 31 functio

Re: sysupgrade fails due to "CHECK AND RESET DATE" ?

2021-10-18 Thread kasak



19.10.2021 08:45, Otto Moerbeek пишет:

On Mon, Oct 18, 2021 at 11:18:20PM +0300, kasak wrote:


Hello everyone!

I have one mini router, made from gigabyte GB-SBCAP4200 barebone

It has nothing special. Just base openbsd, without any additional packages
and modifications.

for some reason, sysupgrade does not upgrade this system.
It successfully boot new kernel, but do not process the upgrade, Just load
6.9 back.

This is dmesg from loading 7.0 and further:

OpenBSD 7.0 (RAMDISK_CD) #219: Thu Sep 30 14:32:42 MDT 2021
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
real mem = 8415617024 (8025MB)
avail mem = 8156545024 (7778MB)
random: good seed from bootblocks
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x79db7000 (50 entries)
bios0: vendor American Megatrends Inc. version "F1" date 06/11/2018
bios0: Gigabyte Technology Co., Ltd. Default string
acpi0 at bios0: ACPI 6.0
acpi0: tables DSDT FACP FPDT FIDT MCFG DBG2 DBGP HPET LPIT APIC NPKT PRAM
WSMT SSDT SSDT SSDT SSDT SSDT SSDT SSDT UEFI TPM2 WDAT
acpihpet0 at acpi0: 1920 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Pentium(R) CPU N4200 @ 1.10GHz, 1097.47 MHz, 06-5c-09
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,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
cpu0: 1MB 64b/line 16-way L2 cache
cpu0: apic clock running at 19MHz
cpu0: mwait min=64, max=64, C-substates=0.2.0.2.4.2.1.1, IBE
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 120 pins
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (RP01)
acpiprt2 at acpi0: bus -1 (RP02)
acpiprt3 at acpi0: bus 1 (RP03)
acpiprt4 at acpi0: bus 2 (RP04)
acpiprt5 at acpi0: bus 3 (RP05)
acpiprt6 at acpi0: bus 4 (RP06)
acpiec0 at acpi0: not present
acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001
acpicmos0 at acpi0
"PNP0C0C" at acpi0 not configured
aplgpio0 at acpi0 GPO0 uid 1 addr 0xd0c5/0x76c irq 14, 78 pins
aplgpio1 at acpi0 GPO1 uid 2 addr 0xd0c4/0x764 irq 14, 77 pins
aplgpio2 at acpi0 GPO2 uid 3 addr 0xd0c7/0x674 irq 14, 47 pins
aplgpio3 at acpi0 GPO3 uid 4 addr 0xd0c0/0x654 irq 14, 43 pins
"INT33A1" at acpi0 not configured
"MSFT0101" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
acpicpu at acpi0 not configured
acpipwrres at acpi0 not configured
acpitz at acpi0 not configured
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Apollo Lake Host" rev 0x0b
"Intel HD Graphics 505" rev 0x0b at pci0 dev 2 function 0 not configured
"Intel Apollo Lake HD Audio" rev 0x0b at pci0 dev 14 function 0 not
configured
"Intel Apollo Lake TXE" rev 0x0b at pci0 dev 15 function 0 not configured
ahci0 at pci0 dev 18 function 0 "Intel Apollo Lake AHCI" rev 0x0b: msi, AHCI
1.3.1
ahci0: PHY offline on port 0
ahci0: port 1: 6.0Gb/s
scsibus0 at ahci0: 32 targets
sd0 at scsibus0 targ 1 lun 0: 
naa.50026b7783a249ed
sd0: 228936MB, 512 bytes/sector, 468862128 sectors, thin
ppb0 at pci0 dev 19 function 0 "Intel Apollo Lake PCIE" rev 0xfb: msi
pci1 at ppb0 bus 1
ppb1 at pci0 dev 19 function 1 "Intel Apollo Lake PCIE" rev 0xfb: msi
pci2 at ppb1 bus 2
ppb2 at pci0 dev 19 function 2 "Intel Apollo Lake PCIE" rev 0xfb: msi
pci3 at ppb2 bus 3
re0 at pci3 dev 0 function 0 "Realtek 8168" rev 0x0c: RTL8168G/8111G
(0x4c00), msi, address e0:d5:5e:e7:50:4f
rgephy0 at re0 phy 7: RTL8251 PHY, rev. 0
ppb3 at pci0 dev 19 function 3 "Intel Apollo Lake PCIE" rev 0xfb: msi
pci4 at ppb3 bus 4
re1 at pci4 dev 0 function 0 "Realtek 8168" rev 0x0c: RTL8168G/8111G
(0x4c00), msi, address e0:d5:5e:e7:50:51
rgephy1 at re1 phy 7: RTL8251 PHY, rev. 0
xhci0 at pci0 dev 21 function 0 "Intel Apollo Lake xHCI" rev 0x0b: msi, xHCI
1.0
usb0 at xhci0: USB revision 3.0
uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev
3.00/1.00 addr 1
"Intel Apollo Lake LPC" rev 0x0b at pci0 dev 31 function 0 not configured
"Intel Apollo Lake SMBus" rev 0x0b at pci0 dev 31 function 1 not configured
isa0 at mainbus0
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
efifb at mainbus0 not configured
softraid0 at root
scsibus1 at softraid0: 256 targets
root on rd0a swap on rd0b dump on rd0b
WARNING: CHECK AND RESET THE DATE!
OpenBSD 6.9 (GENERIC.MP) #4: Tue Aug 10 08:12:23 MDT 2021
r...@syspatch-69-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8415617024 (8025MB)
avail mem = 8145182720 (7767MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x79db7000 (50 entries)
bios0: vendor American Megatrends Inc. version "

Re: drmfreeze

2021-10-18 Thread Avon Robertson
On Mon, Oct 18, 2021 at 03:52:34PM -0700, Chris Cappuccio wrote:
> Here's a thread where people are seeing similar hangs on similar hardware 
> under Linux:
> 
> https://bugs.freedesktop.org/show_bug.cgi?id=108900
> 
> "VERIFIED WONTFIX" because the kernel driver is probably closer to the issue, 
> not Mesa
> 
> here's another: https://bugzilla.kernel.org/show_bug.cgi?id=201957
> 
> The "fix" in the second one seems to be downgrading to an earlier firmware.
> 
> Perhaps you can try to do that, the older radeondrm firmwares should be 
> available from 
> http://firmware.openbsd.org/firmware/6.8/radeondrm-firmware-20181218.tgz
> 
> You can just unpack various versions and place the appropriate files under 
> /etc/firmware for quick testing...
> 
> I have no idea if the 20181218 is the right version to test, it may not be. 
> It's just the first earlier version available on firmware.openbsd.org. You 
> may need to grab a different version from a Linux repository.
> 
> Chris
> 
> Avon Robertson [avo...@xtra.co.nz] wrote:
> > 
> > drm:pid70131:gmc_v8_0_process_interrupt *ERROR* GPU fault detected: 147 
> > 0x0582c802 for process  pid 0 thread Xorg pid 9818
> > drm:pid70131:gmc_v8_0_process_interrupt *ERROR*   
> > VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x86B0
> > drm:pid70131:gmc_v8_0_process_interrupt *ERROR*   
> > VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x070C8002
> > drm:pid70131:gmc_v8_0_vm_decode_fault *ERROR* VM fault (0x02, vmid 3, pasid 
> > 32769) at page 34480, write from 'TC2' (0x54433200) (200)
> > [drm] *ERROR* Illegal register access in command stream
> > [drm] *ERROR* ring gfx timeout, signaled seq=36730, emitted seq=36732
> > [drm] *ERROR* Process information: process  pid 0 thread Xorg pid 9818
> > amdgpu_device_suspend_display_audio: stub
> > amdgpu: cp is busy, skip halt cp
> > amdgpu: rlc is busy, skip halt rlc
> > [drm] *ERROR* Failed to initialize parser -88!
> > 
> > [drm] *ERROR* Failed to initialize parser -88!
> > [drm] *ERROR* ring gfx timeout, signaled seq=36733, emitted seq=36733
> > [drm] *ERROR* Process information: process  pid 0 thread Xorg pid 9818
> > amdgpu_device_suspend_display_audio: stub
> > [drm] *ERROR* Failed to initialize parser -88!
> > 
> > [drm] *ERROR* Failed to initialize parser -88!
> > usb_insert_transfer: xfer=0xfd901e91d000 not free
> > ucomstart: err=INVAL
> > ucom1: read start failed
> > [drm] *ERROR* Failed to initialize parser -88!
> > 
> > [drm] *ERROR* Failed to initialize parser -88!
> > 
> 

-- 

Thank you for the above reference information URLs Chris. I will see if
any fix they suggest fixes the freezes that I have been experiencing.




Re: sysupgrade fails due to "CHECK AND RESET DATE" ?

2021-10-18 Thread Otto Moerbeek
On Mon, Oct 18, 2021 at 11:18:20PM +0300, kasak wrote:

> Hello everyone!
> 
> I have one mini router, made from gigabyte GB-SBCAP4200 barebone
> 
> It has nothing special. Just base openbsd, without any additional packages
> and modifications.
> 
> for some reason, sysupgrade does not upgrade this system.
> It successfully boot new kernel, but do not process the upgrade, Just load
> 6.9 back.
> 
> This is dmesg from loading 7.0 and further:
> 
> OpenBSD 7.0 (RAMDISK_CD) #219: Thu Sep 30 14:32:42 MDT 2021
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
> real mem = 8415617024 (8025MB)
> avail mem = 8156545024 (7778MB)
> random: good seed from bootblocks
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x79db7000 (50 entries)
> bios0: vendor American Megatrends Inc. version "F1" date 06/11/2018
> bios0: Gigabyte Technology Co., Ltd. Default string
> acpi0 at bios0: ACPI 6.0
> acpi0: tables DSDT FACP FPDT FIDT MCFG DBG2 DBGP HPET LPIT APIC NPKT PRAM
> WSMT SSDT SSDT SSDT SSDT SSDT SSDT SSDT UEFI TPM2 WDAT
> acpihpet0 at acpi0: 1920 Hz
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel(R) Pentium(R) CPU N4200 @ 1.10GHz, 1097.47 MHz, 06-5c-09
> 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,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
> cpu0: 1MB 64b/line 16-way L2 cache
> cpu0: apic clock running at 19MHz
> cpu0: mwait min=64, max=64, C-substates=0.2.0.2.4.2.1.1, IBE
> cpu at mainbus0: not configured
> cpu at mainbus0: not configured
> cpu at mainbus0: not configured
> ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 120 pins
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt1 at acpi0: bus -1 (RP01)
> acpiprt2 at acpi0: bus -1 (RP02)
> acpiprt3 at acpi0: bus 1 (RP03)
> acpiprt4 at acpi0: bus 2 (RP04)
> acpiprt5 at acpi0: bus 3 (RP05)
> acpiprt6 at acpi0: bus 4 (RP06)
> acpiec0 at acpi0: not present
> acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001
> acpicmos0 at acpi0
> "PNP0C0C" at acpi0 not configured
> aplgpio0 at acpi0 GPO0 uid 1 addr 0xd0c5/0x76c irq 14, 78 pins
> aplgpio1 at acpi0 GPO1 uid 2 addr 0xd0c4/0x764 irq 14, 77 pins
> aplgpio2 at acpi0 GPO2 uid 3 addr 0xd0c7/0x674 irq 14, 47 pins
> aplgpio3 at acpi0 GPO3 uid 4 addr 0xd0c0/0x654 irq 14, 43 pins
> "INT33A1" at acpi0 not configured
> "MSFT0101" at acpi0 not configured
> "PNP0C0B" at acpi0 not configured
> acpicpu at acpi0 not configured
> acpipwrres at acpi0 not configured
> acpitz at acpi0 not configured
> pci0 at mainbus0 bus 0
> pchb0 at pci0 dev 0 function 0 "Intel Apollo Lake Host" rev 0x0b
> "Intel HD Graphics 505" rev 0x0b at pci0 dev 2 function 0 not configured
> "Intel Apollo Lake HD Audio" rev 0x0b at pci0 dev 14 function 0 not
> configured
> "Intel Apollo Lake TXE" rev 0x0b at pci0 dev 15 function 0 not configured
> ahci0 at pci0 dev 18 function 0 "Intel Apollo Lake AHCI" rev 0x0b: msi, AHCI
> 1.3.1
> ahci0: PHY offline on port 0
> ahci0: port 1: 6.0Gb/s
> scsibus0 at ahci0: 32 targets
> sd0 at scsibus0 targ 1 lun 0: 
> naa.50026b7783a249ed
> sd0: 228936MB, 512 bytes/sector, 468862128 sectors, thin
> ppb0 at pci0 dev 19 function 0 "Intel Apollo Lake PCIE" rev 0xfb: msi
> pci1 at ppb0 bus 1
> ppb1 at pci0 dev 19 function 1 "Intel Apollo Lake PCIE" rev 0xfb: msi
> pci2 at ppb1 bus 2
> ppb2 at pci0 dev 19 function 2 "Intel Apollo Lake PCIE" rev 0xfb: msi
> pci3 at ppb2 bus 3
> re0 at pci3 dev 0 function 0 "Realtek 8168" rev 0x0c: RTL8168G/8111G
> (0x4c00), msi, address e0:d5:5e:e7:50:4f
> rgephy0 at re0 phy 7: RTL8251 PHY, rev. 0
> ppb3 at pci0 dev 19 function 3 "Intel Apollo Lake PCIE" rev 0xfb: msi
> pci4 at ppb3 bus 4
> re1 at pci4 dev 0 function 0 "Realtek 8168" rev 0x0c: RTL8168G/8111G
> (0x4c00), msi, address e0:d5:5e:e7:50:51
> rgephy1 at re1 phy 7: RTL8251 PHY, rev. 0
> xhci0 at pci0 dev 21 function 0 "Intel Apollo Lake xHCI" rev 0x0b: msi, xHCI
> 1.0
> usb0 at xhci0: USB revision 3.0
> uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev
> 3.00/1.00 addr 1
> "Intel Apollo Lake LPC" rev 0x0b at pci0 dev 31 function 0 not configured
> "Intel Apollo Lake SMBus" rev 0x0b at pci0 dev 31 function 1 not configured
> isa0 at mainbus0
> pckbc0 at isa0 port 0x60/5 irq 1 irq 12
> efifb at mainbus0 not configured
> softraid0 at root
> scsibus1 at softraid0: 256 targets
> root on rd0a swap on rd0b dump on rd0b
> WARNING: CHECK AND RESET THE DATE!
> OpenBSD 6.9 (GENERIC.MP) #4: Tue Aug 10 08:12:23 MDT 2021
> r...@syspatch-69-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> real mem = 8415617024 (8025MB)
> avail mem = 8145182720 (7767MB)
> random: good seed from bootblocks
> mpa

DHCP leases not being renewed

2021-10-18 Thread Ryan Vitelli
Hello,

After upgrading to 7.0 I noticed DHCP leases from my ISP were
not being renewed.

After researching I ended up modifying my /etc/hostname.em0 file
by replacing 'dhcp' with '!dhclient \$if' and this "appears"
to resolve the issue.

The FAQ and the dhclient/hostname.if manpages infer that this
shouldn't be necessary and a simple 'dhcp' should be sufficient.
Obviously I'm missing something because our application is very basic.

With the above "fix" in place, the other thing I've noticed is that
on bootup I now get this
em0: no linkgot link
em0: no lease.got lease
em0: my.wan.ip.addr lease accepted from nnn.nnn.nnn.nnn (u:v:w:x:y:z)
This does not appear with hostname.em0 containing 'dhcp', however
it did previously when on 6.9

Any help on this would be great. Thanks.

Notes:
No related messages in daemon or messages logs
OS: openbsd 7.0 /amd64
hardware is PC Engines APU2e4 with BIOS version v4.13.0.2
em0 at pci1 dev 0 function 0 "Intel I210" rev 0x03: msi, address a:b:c:d:e:f



Re: Exit status of pkg_add

2021-10-18 Thread Yuichiro NAITO

Following patch changes pkg_add to return a error code,
if a package name is wrong.

diff --git a/usr.sbin/pkg_add/OpenBSD/AddDelete.pm 
b/usr.sbin/pkg_add/OpenBSD/AddDelete.pm

index 7a968cbf05d..39bee874ff1 100644
--- a/usr.sbin/pkg_add/OpenBSD/AddDelete.pm
+++ b/usr.sbin/pkg_add/OpenBSD/AddDelete.pm
@@ -403,12 +403,13 @@ sub check_root
 sub choose_location
 {
my ($state, $name, $list, $is_quirks) = @_;
if (@$list == 0) {
if (!$is_quirks) {
$state->errsay("Can't find #1", $name);
+   $state->{bad}++;
$state->run_quirks(
sub {
my $quirks = shift;
$quirks->filter_obsolete([$name], $state);
});
}

Is it OK?

On 10/18/21 16:53, Yuichiro NAITO wrote:

Hi, I have a question about exit status of pkg_add command.

When I wrote a package install script which included typo in a package name
(of course it's my fault), the script didn't stop in spite of `set -e`.

Because pkg_add command returns 0 even if a package name is wrong.
Is this exit status intended or design policy of pkg_add command?

If not, I want a error status getting returned.
It will save my time to look for a typo or similar bug.

I can't see 'EXIT STATUS' section in the pkg_add manual of OpenBSD 7.0.
So, I e-mailed this question.



--
Yuichiro NAITO (naito.yuich...@gmail.com)



Re: drmfreeze

2021-10-18 Thread Chris Cappuccio
Here's a thread where people are seeing similar hangs on similar hardware under 
Linux:

https://bugs.freedesktop.org/show_bug.cgi?id=108900

"VERIFIED WONTFIX" because the kernel driver is probably closer to the issue, 
not Mesa

here's another: https://bugzilla.kernel.org/show_bug.cgi?id=201957

The "fix" in the second one seems to be downgrading to an earlier firmware.

Perhaps you can try to do that, the older radeondrm firmwares should be 
available from 
http://firmware.openbsd.org/firmware/6.8/radeondrm-firmware-20181218.tgz

You can just unpack various versions and place the appropriate files under 
/etc/firmware for quick testing...

I have no idea if the 20181218 is the right version to test, it may not be. 
It's just the first earlier version available on firmware.openbsd.org. You may 
need to grab a different version from a Linux repository.

Chris

Avon Robertson [avo...@xtra.co.nz] wrote:
> 
> drm:pid70131:gmc_v8_0_process_interrupt *ERROR* GPU fault detected: 147 
> 0x0582c802 for process  pid 0 thread Xorg pid 9818
> drm:pid70131:gmc_v8_0_process_interrupt *ERROR*   
> VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x86B0
> drm:pid70131:gmc_v8_0_process_interrupt *ERROR*   
> VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x070C8002
> drm:pid70131:gmc_v8_0_vm_decode_fault *ERROR* VM fault (0x02, vmid 3, pasid 
> 32769) at page 34480, write from 'TC2' (0x54433200) (200)
> [drm] *ERROR* Illegal register access in command stream
> [drm] *ERROR* ring gfx timeout, signaled seq=36730, emitted seq=36732
> [drm] *ERROR* Process information: process  pid 0 thread Xorg pid 9818
> amdgpu_device_suspend_display_audio: stub
> amdgpu: cp is busy, skip halt cp
> amdgpu: rlc is busy, skip halt rlc
> [drm] *ERROR* Failed to initialize parser -88!
>   
> [drm] *ERROR* Failed to initialize parser -88!
> [drm] *ERROR* ring gfx timeout, signaled seq=36733, emitted seq=36733
> [drm] *ERROR* Process information: process  pid 0 thread Xorg pid 9818
> amdgpu_device_suspend_display_audio: stub
> [drm] *ERROR* Failed to initialize parser -88!
>   
> [drm] *ERROR* Failed to initialize parser -88!
> usb_insert_transfer: xfer=0xfd901e91d000 not free
> ucomstart: err=INVAL
> ucom1: read start failed
> [drm] *ERROR* Failed to initialize parser -88!
>   
> [drm] *ERROR* Failed to initialize parser -88!
> 



Re: mpd - All audio outputs are disabled

2021-10-18 Thread Alexandre Ratchov
On Mon, Oct 18, 2021 at 03:04:20PM -0400, Mario St-Gelais wrote:
> Hum, I had subject problem in the past following an upgrade, It happened
> again, yet, I cannot remember what the heck I used to do to solve it.
> 
> I vaguely remember it was a stupid thing.  Any hint please?
> 
> I can do aucat -i file.wav no problem.
> Changed ownership of audio0 to my username
> 

audio and MIDI-related files in /dev are supposed to be owned by root,
by default only sndiod(8) uses them directly.

Most probably _mpd user and you are trying to connect to sndiod
simultaneously.

If so, you can authorize _mpd to connect to your sndio session by
copying your ~/.sndio/cookie to _mpd home directory. There's a short
explanation in the "Authentication" section of sndio(7).



sysupgrade fails due to "CHECK AND RESET DATE" ?

2021-10-18 Thread kasak

Hello everyone!

I have one mini router, made from gigabyte GB-SBCAP4200 barebone

It has nothing special. Just base openbsd, without any additional 
packages and modifications.


for some reason, sysupgrade does not upgrade this system.
It successfully boot new kernel, but do not process the upgrade, Just 
load 6.9 back.


This is dmesg from loading 7.0 and further:

OpenBSD 7.0 (RAMDISK_CD) #219: Thu Sep 30 14:32:42 MDT 2021
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
real mem = 8415617024 (8025MB)
avail mem = 8156545024 (7778MB)
random: good seed from bootblocks
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x79db7000 (50 entries)
bios0: vendor American Megatrends Inc. version "F1" date 06/11/2018
bios0: Gigabyte Technology Co., Ltd. Default string
acpi0 at bios0: ACPI 6.0
acpi0: tables DSDT FACP FPDT FIDT MCFG DBG2 DBGP HPET LPIT APIC NPKT 
PRAM WSMT SSDT SSDT SSDT SSDT SSDT SSDT SSDT UEFI TPM2 WDAT

acpihpet0 at acpi0: 1920 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Pentium(R) CPU N4200 @ 1.10GHz, 1097.47 MHz, 06-5c-09
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,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN

cpu0: 1MB 64b/line 16-way L2 cache
cpu0: apic clock running at 19MHz
cpu0: mwait min=64, max=64, C-substates=0.2.0.2.4.2.1.1, IBE
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 120 pins
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (RP01)
acpiprt2 at acpi0: bus -1 (RP02)
acpiprt3 at acpi0: bus 1 (RP03)
acpiprt4 at acpi0: bus 2 (RP04)
acpiprt5 at acpi0: bus 3 (RP05)
acpiprt6 at acpi0: bus 4 (RP06)
acpiec0 at acpi0: not present
acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001
acpicmos0 at acpi0
"PNP0C0C" at acpi0 not configured
aplgpio0 at acpi0 GPO0 uid 1 addr 0xd0c5/0x76c irq 14, 78 pins
aplgpio1 at acpi0 GPO1 uid 2 addr 0xd0c4/0x764 irq 14, 77 pins
aplgpio2 at acpi0 GPO2 uid 3 addr 0xd0c7/0x674 irq 14, 47 pins
aplgpio3 at acpi0 GPO3 uid 4 addr 0xd0c0/0x654 irq 14, 43 pins
"INT33A1" at acpi0 not configured
"MSFT0101" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
acpicpu at acpi0 not configured
acpipwrres at acpi0 not configured
acpitz at acpi0 not configured
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Apollo Lake Host" rev 0x0b
"Intel HD Graphics 505" rev 0x0b at pci0 dev 2 function 0 not configured
"Intel Apollo Lake HD Audio" rev 0x0b at pci0 dev 14 function 0 not 
configured

"Intel Apollo Lake TXE" rev 0x0b at pci0 dev 15 function 0 not configured
ahci0 at pci0 dev 18 function 0 "Intel Apollo Lake AHCI" rev 0x0b: msi, 
AHCI 1.3.1

ahci0: PHY offline on port 0
ahci0: port 1: 6.0Gb/s
scsibus0 at ahci0: 32 targets
sd0 at scsibus0 targ 1 lun 0:  
naa.50026b7783a249ed

sd0: 228936MB, 512 bytes/sector, 468862128 sectors, thin
ppb0 at pci0 dev 19 function 0 "Intel Apollo Lake PCIE" rev 0xfb: msi
pci1 at ppb0 bus 1
ppb1 at pci0 dev 19 function 1 "Intel Apollo Lake PCIE" rev 0xfb: msi
pci2 at ppb1 bus 2
ppb2 at pci0 dev 19 function 2 "Intel Apollo Lake PCIE" rev 0xfb: msi
pci3 at ppb2 bus 3
re0 at pci3 dev 0 function 0 "Realtek 8168" rev 0x0c: RTL8168G/8111G 
(0x4c00), msi, address e0:d5:5e:e7:50:4f

rgephy0 at re0 phy 7: RTL8251 PHY, rev. 0
ppb3 at pci0 dev 19 function 3 "Intel Apollo Lake PCIE" rev 0xfb: msi
pci4 at ppb3 bus 4
re1 at pci4 dev 0 function 0 "Realtek 8168" rev 0x0c: RTL8168G/8111G 
(0x4c00), msi, address e0:d5:5e:e7:50:51

rgephy1 at re1 phy 7: RTL8251 PHY, rev. 0
xhci0 at pci0 dev 21 function 0 "Intel Apollo Lake xHCI" rev 0x0b: msi, 
xHCI 1.0

usb0 at xhci0: USB revision 3.0
uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev 
3.00/1.00 addr 1

"Intel Apollo Lake LPC" rev 0x0b at pci0 dev 31 function 0 not configured
"Intel Apollo Lake SMBus" rev 0x0b at pci0 dev 31 function 1 not configured
isa0 at mainbus0
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
efifb at mainbus0 not configured
softraid0 at root
scsibus1 at softraid0: 256 targets
root on rd0a swap on rd0b dump on rd0b
WARNING: CHECK AND RESET THE DATE!
OpenBSD 6.9 (GENERIC.MP) #4: Tue Aug 10 08:12:23 MDT 2021
r...@syspatch-69-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8415617024 (8025MB)
avail mem = 8145182720 (7767MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x79db7000 (50 entries)
bios0: vendor American Megatrends Inc. version "F1" date 06/11/2018
bios0: Gigabyte Technology Co., Ltd. Default string
acpi0 

mpd - All audio outputs are disabled

2021-10-18 Thread Mario St-Gelais
Hum, I had subject problem in the past following an upgrade, It happened 
again, yet, I cannot remember what the heck I used to do to solve it.


I vaguely remember it was a stupid thing.  Any hint please?

I can do aucat -i file.wav no problem.
Changed ownership of audio0 to my username

--
Mario St-Gelais
Gatineau



Re: How does bsd.upgrade work?

2021-10-18 Thread Stuart Henderson
On 2021-10-18, tetrahe...@danwin1210.me  wrote:
> On Fri, Oct 15, 2021 at 10:14:56PM +, tetrahe...@danwin1210.me wrote:
>>My setup is a little bit unusual, and I'm trying to understand why
>>`uname -a` is still reporting 6.9 after I successfully booted
>>bsd.upgrade and saw the upgrade process scroll past.
>
> I resolved the problem. The solution was to run `sysupgrade -n` to
> download all the upgrade files, and leave the `bsd.upgrade` kernel in
> place, next to the `bsd` kernel I usually boot.
>
> Then, at the next boot, manually boot the `bsd.upgrade` kernel by
> specifying its location.

Sounds like you aren't using the correct boot loader.

-- 
Please keep replies on the mailing list.



Re: Keeping a personal ports branch

2021-10-18 Thread Rubén Llorente
Stuart Henderson  wrote:
> Just use a different VCS, for example svn or git. /usr/ports/mystuff
> is listed in .cvsignore in the repository so they don't conflict, and
> there is special handling in ports infrastructure. The directory
> layout underneath it should be as with the main ports tree i.e.
> /usr/ports/mystuff/category/portname.
> 
> See PORTSDIR_PATH in bsd.port.mk(5). By default /usr/ports takes
> priority over /usr/ports/mystuff, but if you want to override things
> in the main tree you can swap that around with an entry in /etc/mk.conf
> like PORTSDIR_PATH=${PORTSDIR}/mystuff:${PORTSDIR}
> 
> 

That is all I need. It sounds great to me.

I am a CVS dude so mystuff may as well stay CVS :-)

-- 
OpenPGP Key Fingerprint:
543F EB89 7FDE 8E33 AFF7 E794 E4AB 4807 58F7 6C76



Re: iked drops network connection when roadwarrior connects 6.9+

2021-10-18 Thread Stuart Henderson
Follow the 6.9 upgrade guide.

On 2021-10-18, Matthew Ernisse  wrote:
> I have a iked(8) based VPN concentrator that terminates roadwarrior
> connections from macOS and iOS devices.  It connects back to my
> broader infrastructure via a static flow with GRE running on top.
> Starting with 6.9 I noticed that bringing up a roadwarrior tunnel would
> drop the network completely (pings to the public IP die).  I originally
> thought it was related to
> https://marc.info/?l=openbsd-misc&m=162212479408239&w=2
> so I rolled back to 6.8 and waited for 7.0.  I upgraded to 7.0 and it seems
> that the behavior remains.  I just finsihed reverting back to 6.8 to verify
> that things work as expected and they do.
>
> The roadwarrior is an automatic connection triggered by leaving a trusted
> WiFi network, I asked iked to log verbose this morning and left the house
> at 08:34.  You can see the connection in the log.  Around 09:10 I rebooted
> to bsd.rd to re-install 6.8.  Links to iked.conf and the daemon log are
> below.  I'm happy to upgrade to 7.0 again to debug this, but I don't really
> know where to start.
>
> --Matt
>
> /var/log/daemon: https://www.going-flying.com/~mernisse/iked-7.0/daemon.txt
> /etc/iked.conf: https://www.going-flying.com/~mernisse/iked-7.0/iked.conf.txt
>
>


-- 
Please keep replies on the mailing list.



Re: Multiple SSID when operating in Host AP mode?

2021-10-18 Thread Stuart Henderson
On 2021-10-18, Joel Carnat  wrote:
> Is it possible (as of OpenBSD 7.0/amd64) to configure a bwfm (Broadcom 
> BCM4356) device in hostap mode and publish several nwid ; from that single 
> device?

No (not supported on OpenBSD with any wifi interface type).




Re: How does bsd.upgrade work?

2021-10-18 Thread tetrahedra

On Fri, Oct 15, 2021 at 10:14:56PM +, tetrahe...@danwin1210.me wrote:

My setup is a little bit unusual, and I'm trying to understand why
`uname -a` is still reporting 6.9 after I successfully booted
bsd.upgrade and saw the upgrade process scroll past.


I resolved the problem. The solution was to run `sysupgrade -n` to
download all the upgrade files, and leave the `bsd.upgrade` kernel in
place, next to the `bsd` kernel I usually boot.

Then, at the next boot, manually boot the `bsd.upgrade` kernel by
specifying its location.



Re: Alpine Linux guest running slow after upgraded to OpenBSD 7.0

2021-10-18 Thread Olivier A.

On 18/10/2021 09:36, Siegfried Levin wrote:

An Alpine Linux 3.10 guest VM is running quite slow after I upgraded the host 
to 7.0. It takes quite long to get a response. Other OpenBSD guests seems ok. 
Is anyone having the same issue? Thanks.


Hi,

I recently observed performance problems on my Alpine VMs without 
knowing if it comes from the Alpine 3.14 upgrade or from a -current 
snapshot.From what I observed, the VM was struggling to maintain 
temporal stability. This had a lot of side effects in terms of network, 
performance, freeze of all kinds.I installed vmm_clock [1] and 
everything is back to normal.


[1]:https://github.com/voutilad/vmm_clock


--

Olivier


Re: Alpine Linux guest running slow after upgraded to OpenBSD 7.0

2021-10-18 Thread Dave Voutila


Siegfried Levin  writes:

> An Alpine Linux 3.10 guest VM is running quite slow after I upgraded
> the host to 7.0. It takes quite long to get a response. Other OpenBSD
> guests seems ok. Is anyone having the same issue? Thanks.

You'll need to share a bit more detail for any constructive help; "quite
long" and "a response" are too vague. A lot changed in 7.0 outside just
vmm(4)/vmd(8).

-dv



iked drops network connection when roadwarrior connects 6.9+

2021-10-18 Thread Matthew Ernisse
I have a iked(8) based VPN concentrator that terminates roadwarrior
connections from macOS and iOS devices.  It connects back to my
broader infrastructure via a static flow with GRE running on top.
Starting with 6.9 I noticed that bringing up a roadwarrior tunnel would
drop the network completely (pings to the public IP die).  I originally
thought it was related to
https://marc.info/?l=openbsd-misc&m=162212479408239&w=2
so I rolled back to 6.8 and waited for 7.0.  I upgraded to 7.0 and it seems
that the behavior remains.  I just finsihed reverting back to 6.8 to verify
that things work as expected and they do.

The roadwarrior is an automatic connection triggered by leaving a trusted
WiFi network, I asked iked to log verbose this morning and left the house
at 08:34.  You can see the connection in the log.  Around 09:10 I rebooted
to bsd.rd to re-install 6.8.  Links to iked.conf and the daemon log are
below.  I'm happy to upgrade to 7.0 again to debug this, but I don't really
know where to start.

--Matt

/var/log/daemon: https://www.going-flying.com/~mernisse/iked-7.0/daemon.txt
/etc/iked.conf: https://www.going-flying.com/~mernisse/iked-7.0/iked.conf.txt



Re: How does bsd.upgrade work?

2021-10-18 Thread Florian Obser
On 2021-10-18 14:38 UTC, tetrahe...@danwin1210.me wrote:
> On Fri, Oct 15, 2021 at 10:14:56PM +, tetrahe...@danwin1210.me wrote:
>>My setup is a little bit unusual, and I'm trying to understand why
>>`uname -a` is still reporting 6.9 after I successfully booted
>>bsd.upgrade and saw the upgrade process scroll past.

unlikely

>
> I resolved the problem. The solution was to run `sysupgrade -n` to
> download all the upgrade files, and leave the `bsd.upgrade` kernel in
> place, next to the `bsd` kernel I usually boot.
>
> Then, at the next boot, manually boot the `bsd.upgrade` kernel by
> specifying its location.
>

I wouldn't call this "resolved". You are missing the point that
bsd.upgrade should run automatically. *shrug*

-- 
I'm not entirely sure you are real.



Multiple SSID when operating in Host AP mode?

2021-10-18 Thread Joel Carnat
Hello,

Is it possible (as of OpenBSD 7.0/amd64) to configure a bwfm (Broadcom BCM4356) 
device in hostap mode and publish several nwid ; from that single device?

The idea would be to have several SSIDs with different configurations ; as some 
IoT devices don't support "greater" network than 11g when computers and phones 
would support up to 11n/11ac.

Thank you,
Joel C.



Re: Question about cryptography software compatibility on OpenBSD

2021-10-18 Thread soko.tica
Thank you Janne.

On Fri, Oct 15, 2021 at 3:57 PM Janne Johansson  wrote:

> > > > 3) Providers of public digital signatures offer software (a
> > > > one-size-fits-all Java “blob”) that should add cryptography
> capabilities
> > > to
> > > > the operating system.
>
> > >
> > > This is important. Thank you. Let me rephrase my wild guess:
> >
> > 3.1) An OS (OpenBSD or other) may have cryptography capabilities included
> > in the kernel.
>
> Yes.
>
> > 3.2) An OS that doesn't have cryptography capabilities included in the
> > kernel may provide cryptography software, not being included in the
> kernel,
> > fit and apt for use on the specific OS.
>
> This is where you seem to be missing that LOTS AND LOTS of programs use
> crypto from external libraries.
> They call openssl, they use NSS/NSPR, programs link against
> gnutls, java code use java libs, go code use go crypto and so on.
>
> > 3.3) Forcing the blind use of proprietary
> > java-crypto-one_size_fits_all-blob is technically possible, but it is a
> bad
> > practice since:
> > 3.3.1) it may downgrade crypto functionality existing in an OS as
> described
> > under 3.1 and 3.2
> > 3.3.2) it may compromise and expose to the attacks not only the digital
> > signature, but the operating system itself
> > 3.3.3) for a number of other reasons (updates, licensing issues, etc.)
>
> Those last subpoints work both ways.
>
> A brought-along crypto primitive can be controlled by
> the person installing the program in ways you can't with the OS,
> so it is, like so much else, a tradeoff. If you don't control the OS and
> what
> crypto primitives it has, bringing along your own might be "safer" than to
> trust some OS to have a stable interface forever and ever.
>
>
> --
> May the most significant bit of your life be positive.
>


Re: Library for the pf(4) device

2021-10-18 Thread J. K.
Hi Matthias!

On 18.10.21 05:30, Matthias Pressfreund wrote:
> Hi,
> 
> maybe that would serve your purposes:
> 
> https://github.com/mpfr/pftbld
> 

Awesome! This is exactly what I have planned.

Starred on GitHub. :)

Many thanks and best regards.



Exit status of pkg_add

2021-10-18 Thread Yuichiro NAITO
Hi, I have a question about exit status of pkg_add command.

When I wrote a package install script which included typo in a package name
(of course it's my fault), the script didn't stop in spite of `set -e`.

Because pkg_add command returns 0 even if a package name is wrong.
Is this exit status intended or design policy of pkg_add command?

If not, I want a error status getting returned.
It will save my time to look for a typo or similar bug.

I can't see 'EXIT STATUS' section in the pkg_add manual of OpenBSD 7.0.
So, I e-mailed this question.

-- 
Yuichiro NAITO (naito.yuic...@gmail.com)



Alpine Linux guest running slow after upgraded to OpenBSD 7.0

2021-10-18 Thread Siegfried Levin
An Alpine Linux 3.10 guest VM is running quite slow after I upgraded the host 
to 7.0. It takes quite long to get a response. Other OpenBSD guests seems ok. 
Is anyone having the same issue? Thanks.

Siegfried
siegfried.le...@gmail.com