Re: gdb in uninterruptible wait

2020-07-19 Thread Visa Hankala 
On Sun, Jul 19, 2020 at 09:47:54PM +0100, Julian Smith wrote:
> I've been finding egdb and gdb rather easily get stuck in an
> uninterruptible wait, e.g. when running the 'next' command after
> hitting a breakpoint.
> 
> So it's not possible to kill the debuggee or gdb and the only way to
> kill the debuggee process and free up its listening sockets seems to be
> to reboot the entire system.
> 
> Perhaps unsurprisingly one cannot attach a second invocation of gdb to
> the uninterruptible gdb, so i don't know for sure what syscall is being
> run that is getting stuck.
> 
> The debuggee is a local build of the flightgear flight simulator.
> 
> Here's the output of ps for the debugger and debuggee:
> 
> 12419 p0  D0:34.37 egdb -ex handle SIGPIPE noprint nostop -ex set 
> print thread-events off -ex set print pretty on -ex run --args 
> build-walk/fgfs,clang,debug,opt,co
> 63921 p0  TX+  0:42.45 
> /home/jules/flightgear/build-walk/fgfs,clang,debug,opt,compositor,osg.exe 
> --airport=egtk (fgfs,clang,debug)
> 
> I've tried using ktrace on egdb, and the kdump output ends like this:
> 
>  53950 egdb CALL  wait4(WAIT_ANY,0x7f7e8efc,0<>,0)
>  53950 egdb RET   wait4 97562/0x17d1a
>  53950 egdb CALL  ptrace(PT_GET_PROCESS_STATE,97562,0x7f7e8ef0,12)
>  53950 egdb RET   ptrace 0
>  53950 egdb CALL  ptrace(PT_GETREGS,161560,0x7f7e8b40,0)
>  53950 egdb RET   ptrace 0
>  53950 egdb CALL  
> futex(0x6444e37c490,0x82,1,0,0)
>  53950 egdb RET   futex 0
>  53950 egdb CALL  
> futex(0x644bef12740,0x82,1,0,0)
>  53950 egdb RET   futex 0
>  53950 egdb CALL  ptrace(PT_IO,97562,0x7f7e8a30,0)
>  53950 egdb RET   ptrace 0
>  53950 egdb CALL  ptrace(PT_IO,97562,0x7f7e8a30,0)
>  53950 egdb RET   ptrace 0
>  53950 egdb CALL  ptrace(PT_STEP,97562,0x1,0)
>  53950 egdb RET   ptrace 0
>  53950 egdb CALL  read(6,0x7f7e9187,0x1)
>  53950 egdb RET   read -1 errno 35 Resource temporarily unavailable
>  53950 egdb CALL  poll(0x6441581e720,3,0)
>  53950 egdb STRU  struct pollfd [3] { fd=4, events=0x1, 
> revents=0<> } { fd=6, events=0x1, revents=0<> } { fd=10, 
> events=0x1, revents=0<> }
>  53950 egdb RET   poll 0
>  53950 egdb CALL  wait4(WAIT_ANY,0x7f7e8efc,0<>,0)
> 
> Assuming that this is the actual end of the ktrace output and there
> isn't some missing ktrace output in a buffer somewhere, this looks
> like egdb is simply blocked in wait4(), which should be harmless and
> certainly not uninterruptable?

The single-thread check done by wait4() is non-interruptible.
When the debugger gets stuck, is it blocked in "suspend" state?

However, I think there is a bug in the single-thread switch code.
It looks that ps_singlecount can be decremented too much. This probably
is a regression of making ps_singlecount unsigned and letting
single_thread_check() run without the kernel lock.

The bug might go away if single_thread_check() made sure that
P_SUSPSINGLE is set before the thread suspends. 

Does the following patch help? Even if it does, it probably needs
some refining.

Index: kern/kern_sig.c
===
RCS file: src/sys/kern/kern_sig.c,v
retrieving revision 1.258
diff -u -p -r1.258 kern_sig.c
--- kern/kern_sig.c 15 Jun 2020 13:18:33 -  1.258
+++ kern/kern_sig.c 20 Jul 2020 04:27:30 -
@@ -1915,16 +1915,23 @@ single_thread_check(struct proc *p, int 
return (EINTR);
}
 
-   if (atomic_dec_int_nv(>ps_singlecount) == 0)
-   wakeup(>ps_singlecount);
+   SCHED_LOCK(s);
+   if (p->p_flag & P_SUSPSINGLE) {
+   if (atomic_dec_int_nv(>ps_singlecount) == 0)
+   wakeup(>ps_singlecount);
+   } else if ((p->p_flag & P_WEXIT) == 0) {
+   SCHED_UNLOCK(s);
+   CPU_BUSY_CYCLE();
+   continue;
+   }
if (pr->ps_flags & PS_SINGLEEXIT) {
+   SCHED_UNLOCK(s);
KERNEL_LOCK();
exit1(p, 0, 0, EXIT_THREAD_NOCHECK);
-   KERNEL_UNLOCK();
+   /* NOTREACHED */
}
 
/* not exiting and don't need to unwind, so suspend */
-   SCHED_LOCK(s);
p->p_stat = SSTOP;
mi_switch();
SCHED_UNLOCK(s);

Re: Bug? having no monitor plugged in causes a reboot in bsd.rd

2020-07-19 Thread Alfred Morgan 
Status Code Available
DXE Status Code Available
>> OpenBSD/amd64 BOOTX64 3.50
boot>
booting hd0a:/bsd: 12952904+2757640+331808+0+708608
[807661+128+1024872+749630]=0x1272b18
entry point at 0x1001000
[ using 2583320 bytes of bsd ELF symbol table ]
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California.  All rights reserved.
Copyright (c) 1995-2020 OpenBSD. All rights reserved.
https://www.OpenBSD.org

OpenBSD 6.7 (GENERIC.MP) #182: Thu May  7 11:11:58 MDT 2020
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8462508032 (8070MB)
avail mem = 8193417216 (7813MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xb99e7000 (51 entries)
bios0: vendor American Megatrends Inc. version "B219P028" date 04/27/2016
bios0: Motherboard by ZOTAC ZBOX-CI320NANO series
acpi0 at bios0: ACPI 5.0
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT FIDT MCFG LPIT HPET SSDT SSDT SSDT UEFI
BGRT
acpi0: wakeup devices XHC1(S4) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) PWRB(S0)
BRCM(S0)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Celeron(R) CPU N2930 @ 1.83GHz, 1833.68 MHz, 06-37-08
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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,TSC_ADJUST,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu0: 1MB 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 83MHz
cpu0: mwait min=64, max=64, C-substates=0.2.0.0.0.0.3.3, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Celeron(R) CPU N2930 @ 1.83GHz, 1833.34 MHz, 06-37-08
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,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,TSC_ADJUST,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu1: 1MB 64b/line 16-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Celeron(R) CPU N2930 @ 1.83GHz, 1833.36 MHz, 06-37-08
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,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,TSC_ADJUST,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu2: 1MB 64b/line 16-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6 (application processor)
cpu3: Intel(R) Celeron(R) CPU N2930 @ 1.83GHz, 1833.35 MHz, 06-37-08
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,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,TSC_ADJUST,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu3: 1MB 64b/line 16-way L2 cache
cpu3: smt 0, core 3, package 0
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 87 pins
acpimcfg0 at acpi0
acpimcfg0: addr 0xe000, bus 0-255
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (RP01)
acpiprt2 at acpi0: bus 2 (RP02)
acpiprt3 at acpi0: bus 3 (RP03)
acpiprt4 at acpi0: bus 4 (RP04)
acpiec0 at acpi0: not present
acpicpu0 at acpi0: C3(10@1500 mwait.1@0x52), C2(10@500 mwait.1@0x51),
C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: C3(10@1500 mwait.1@0x52), C2(10@500 mwait.1@0x51),
C1(1000@1 mwait.1), PSS
acpicpu2 at acpi0: C3(10@1500 mwait.1@0x52), C2(10@500 mwait.1@0x51),
C1(1000@1 mwait.1), PSS
acpicpu3 at acpi0: C3(10@1500 mwait.1@0x52), C2(10@500 mwait.1@0x51),
C1(1000@1 mwait.1), PSS
acpipwrres0 at acpi0: PLPE
acpipwrres1 at acpi0: PLPE
acpipwrres2 at acpi0: USBC, resource for EHC1, OTG1
acpipwrres3 at acpi0: CLK0, resource for CAM1
acpipwrres4 at acpi0: CLK1, resource for CAM0, CAM2
acpicmos0 at acpi0
acpipci0 at acpi0 PCI0: 0x0010 0x0011 0x
"DMA0F28" at acpi0 not configured
acpibtn0 at acpi0: PWRB
acpibtn1 at acpi0: SLPB
bytgpio0 at acpi0: GPO0 uid 1 addr 0xfed0c000/0x1000 irq 49, 102 pins
bytgpio1 at acpi0: GPO1 uid 2 addr 0xfed0d000/0x1000 irq 48, 28 pins
bytgpio2 at acpi0: GPO2 uid 3 addr 0xfed0e000/0x1000 irq 50, 44 pins
sdhc0 at acpi0 SDHD addr 0xd081c000/0x1000 irq 44
sdhc0: SDHC 3.0, 200 MHz base clock
sdmmc0 at sdhc0: 8-bit, sd high-speed, mmc high-speed, dma
sdhc1 at acpi0 SDHC addr 0xd081a000/0x1000 irq 47, gpio
sdhc1: SDHC 3.0, 100 MHz base clock
sdmmc1 at sdhc1: 4-bit, sd

Re: Bug? having no monitor plugged in causes a reboot in bsd.rd

2020-07-19 Thread Aaron Mason 
On Sun, Jul 19, 2020 at 9:06 AM Alfred Morgan  wrote:
>
> OpenBSD upgrade.lan 6.7 GENERIC.MP#182 amd64
>
> If I set tty com0 then bsd.rd boots fine. If I have a monitor plugged in
> bsd.rd boots fine. If I don't have a monitor and I don't direct tty to com0
> then bsd.rd reboots my machine after a few seconds.
> Any tips on how I can inspect what is going on here?
>
> -alfred

It might help if we knew a bit more about your system.

-- 
Aaron Mason - Programmer, open source addict
I've taken my software vows - for beta or for worse

Re: OpenBSD Hangs On

2020-07-19 Thread Tom Smyth 
Paddy,

I wastnt engaging in FUD,
I was describing a situation which I and others experienced where there
were certain releases of
KVM / Linux Hypervisors which on Intel platforms on which OpenBSD
would Freeze,
the console would slow down and eventually become unresponsive,
if I recall correctly Proxmox 4.x worked ... and I think the versions up to
5.0-5.1 Didnt work so well
and version 6.x of proxmox seems to work well hosting OpenBSD...
the kernel preemption timer and some Hypervisor kernel versions
apparently were the source of the bug

ALl the Best ...



On Sun, 19 Jul 2020 at 23:43, Patrick Dohman 
wrote:

>
>
> > On Jun 23, 2020, at 11:31 AM, Tom Smyth 
> wrote:
> >
> > But newerversions of kvm / linux kernels  are unaffected
> > By the bug fyi
>
> Sounds like FUD.
> B.T.W where is Boba’s ride?
> Regards
> Patrick
>
>

-- 
Kindest regards,
Tom Smyth.

Re: OpenBSD Hangs On

2020-07-19 Thread Patrick Dohman 



> On Jul 19, 2020, at 5:44 PM, Tom Smyth  wrote:
> 
> Im not sure what you mean? 

I can has all your VM’s in carbonite.
Regards
Patrick

Re: OpenBSD Hangs On

2020-07-19 Thread Tom Smyth 
Im not sure what you mean?

On Sun, 19 Jul 2020 at 23:43, Patrick Dohman 
wrote:

>
>
> > On Jun 23, 2020, at 11:31 AM, Tom Smyth 
> wrote:
> >
> > But newerversions of kvm / linux kernels  are unaffected
> > By the bug fyi
>
> Sounds like FUD.
> B.T.W where is Boba’s ride?
> Regards
> Patrick
>
>

-- 
Kindest regards,
Tom Smyth.

Re: OpenBSD Hangs On

2020-07-19 Thread Patrick Dohman 



> On Jun 23, 2020, at 11:31 AM, Tom Smyth  wrote:
> 
> But newerversions of kvm / linux kernels  are unaffected
> By the bug fyi

Sounds like FUD.
B.T.W where is Boba’s ride?
Regards
Patrick

gdb in uninterruptible wait

2020-07-19 Thread Julian Smith 
I've been finding egdb and gdb rather easily get stuck in an
uninterruptible wait, e.g. when running the 'next' command after
hitting a breakpoint.

So it's not possible to kill the debuggee or gdb and the only way to
kill the debuggee process and free up its listening sockets seems to be
to reboot the entire system.

Perhaps unsurprisingly one cannot attach a second invocation of gdb to
the uninterruptible gdb, so i don't know for sure what syscall is being
run that is getting stuck.

The debuggee is a local build of the flightgear flight simulator.

Here's the output of ps for the debugger and debuggee:

12419 p0  D0:34.37 egdb -ex handle SIGPIPE noprint nostop -ex set print 
thread-events off -ex set print pretty on -ex run --args 
build-walk/fgfs,clang,debug,opt,co
63921 p0  TX+  0:42.45 
/home/jules/flightgear/build-walk/fgfs,clang,debug,opt,compositor,osg.exe 
--airport=egtk (fgfs,clang,debug)

I've tried using ktrace on egdb, and the kdump output ends like this:

 53950 egdb CALL  wait4(WAIT_ANY,0x7f7e8efc,0<>,0)
 53950 egdb RET   wait4 97562/0x17d1a
 53950 egdb CALL  ptrace(PT_GET_PROCESS_STATE,97562,0x7f7e8ef0,12)
 53950 egdb RET   ptrace 0
 53950 egdb CALL  ptrace(PT_GETREGS,161560,0x7f7e8b40,0)
 53950 egdb RET   ptrace 0
 53950 egdb CALL  
futex(0x6444e37c490,0x82,1,0,0)
 53950 egdb RET   futex 0
 53950 egdb CALL  
futex(0x644bef12740,0x82,1,0,0)
 53950 egdb RET   futex 0
 53950 egdb CALL  ptrace(PT_IO,97562,0x7f7e8a30,0)
 53950 egdb RET   ptrace 0
 53950 egdb CALL  ptrace(PT_IO,97562,0x7f7e8a30,0)
 53950 egdb RET   ptrace 0
 53950 egdb CALL  ptrace(PT_STEP,97562,0x1,0)
 53950 egdb RET   ptrace 0
 53950 egdb CALL  read(6,0x7f7e9187,0x1)
 53950 egdb RET   read -1 errno 35 Resource temporarily unavailable
 53950 egdb CALL  poll(0x6441581e720,3,0)
 53950 egdb STRU  struct pollfd [3] { fd=4, events=0x1, revents=0<> 
} { fd=6, events=0x1, revents=0<> } { fd=10, events=0x1, 
revents=0<> }
 53950 egdb RET   poll 0
 53950 egdb CALL  wait4(WAIT_ANY,0x7f7e8efc,0<>,0)

Assuming that this is the actual end of the ktrace output and there
isn't some missing ktrace output in a buffer somewhere, this looks
like egdb is simply blocked in wait4(), which should be harmless and
certainly not uninterruptable?

Does anyone have any suggestions about how to investigate this further?

I'm running OpenBSD 6.7 GENERIC.MP#182 amd64.

Thanks,

- Jules

-- 
http://op59.net

Re: non-checksummed UDP packets

2020-07-19 Thread Stuart Henderson 
On 2020-07-19, obs...@loopw.com  wrote:
>
>> Is this normal?  
>
> Checksum is OPTIONAL in UDP, not required.  This is covered in RFC 768.

For IPv4, anyway. It's required for v6.

Touchpad seems to be considered like a keyboard

2020-07-19 Thread Jérôme FRGACIC 

Hi misc@,

I've installed OpenBSD 6.7 on a new laptop and I exprience some troubles 
with the touchpad. To be simple: it seems to be considered like a 
keyboard because when I use it, my computer behave like if I press a 
letter indefinitely until I use the keyboard (then the behaviour stops 
but I have to erase those letters).


I see nothing linked to the touchpad in the output of dmesg and I have 
no options in the BIOS to disable it. Does anyone have an idea in order 
to fix this?


If it can help, you will find bellow the output of dmesg, pcidump -v and 
wsconsctl.


Thanks in adavance.

Kind regards,


Jérôme FRGACIC

$ dmesg
OpenBSD 6.7 (GENERIC.MP) #4: Wed Jul 15 11:16:20 MDT 2020

r...@syspatch-67-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8384339968 (7995MB)
avail mem = 8117616640 (7741MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.2 @ 0x97265000 (56 entries)
bios0: vendor INSYDE Corp. version "1.07.05" date 10/24/2019
bios0: Notebook NJ50_70CU
acpi0 at bios0: ACPI 5.1
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP UEFI SSDT SSDT LPIT WSMT SSDT DBGP DBG2 SSDT 
SSDT NHLT HPET APIC MCFG SSDT FPDT BGRT
acpi0: wakeup devices XHC_(S3) HDAS(S4) RP01(S3) PXSX(S4) RP02(S3) 
PXSX(S4) RP03(S3) PXSX(S4) RP04(S3) PXSX(S4) RP05(S3) PXSX(S4) RP06(S3) 
PXSX(S4) RP07(S3) PXSX(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) i3-10110U CPU @ 2.10GHz, 15447.77 MHz, 06-8e-0c
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,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,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES

cpu0: 256KB 64b/line 8-way L2 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) i3-10110U CPU @ 2.10GHz, 3691.42 MHz, 06-8e-0c
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,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,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES

cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Core(TM) i3-10110U CPU @ 2.10GHz, 3691.40 MHz, 06-8e-0c
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,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,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES

cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 1, core 0, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i3-10110U CPU @ 2.10GHz, 3691.40 MHz, 06-8e-0c
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,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,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES

cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 120 pins
acpimcfg0 at acpi0
acpimcfg0: addr 0xe000, bus 0-255
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 -1 (RP04)
acpiprt5 at acpi0: bus -1 (RP05)
acpiprt6 at acpi0: bus -1 (RP06)
acpiprt7 at acpi0: bus -1 (RP07)
acpiprt8 at acpi0: bus -1 (RP08)
acpiprt9 at acpi0: bus 1 (RP09)
acpiprt10 at acpi0: bus 6 (RP10)
acpiprt11 at acpi0: bus -1 (RP11)
acpiprt12 at acpi0: bus -1 (RP12)
acpiprt13 at acpi0: bus -1 (RP13)
acpiprt14 at

Screen stays off after resuming

2020-07-19 Thread Jérôme FRGACIC 

Hi misc@,

I've installed OpenBSD 6.7 on a new laptop and I experience some 
problems when my laptop resume : the screen stays off. Whatever I do 
like switching to a tty or restarting the X server, it stays off.


Everything seems to be ok behind because I can still enter commands if I 
“blind typing”, it's just that the screen is off.


I must precise that I've disabled inteldrm at kernel level because I 
experience kernel panic when I use it (I've exposed my problem in 
another thread).


I only remark those errors in dmesg and in /var/log/Xorg.0.log at some 
points:


- “wddisplay_switch2: not switching”;
- “ioctl FBIOPUTCMAP: Inappropriate ioctl for device”; and
- “ioctl FBIOGETCMAP: Inappropriate ioctl for device”.

Does anyone have an idea in order to fix this issue?

If it can help, you will find below the output of dmesg, pcidump -v and 
/var/log/Xorg.0.log.


Thanks in advance.

Kind regards,


Jérôme FRGACIC

$ dmesg
OpenBSD 6.7 (GENERIC.MP) #4: Wed Jul 15 11:16:20 MDT 2020

r...@syspatch-67-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8384339968 (7995MB)
avail mem = 8117616640 (7741MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.2 @ 0x97265000 (56 entries)
bios0: vendor INSYDE Corp. version "1.07.05" date 10/24/2019
bios0: Notebook NJ50_70CU
acpi0 at bios0: ACPI 5.1
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP UEFI SSDT SSDT LPIT WSMT SSDT DBGP DBG2 SSDT 
SSDT NHLT HPET APIC MCFG SSDT FPDT BGRT
acpi0: wakeup devices XHC_(S3) HDAS(S4) RP01(S3) PXSX(S4) RP02(S3) 
PXSX(S4) RP03(S3) PXSX(S4) RP04(S3) PXSX(S4) RP05(S3) PXSX(S4) RP06(S3) 
PXSX(S4) RP07(S3) PXSX(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) i3-10110U CPU @ 2.10GHz, 15447.77 MHz, 06-8e-0c
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,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,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES

cpu0: 256KB 64b/line 8-way L2 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) i3-10110U CPU @ 2.10GHz, 3691.42 MHz, 06-8e-0c
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,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,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES

cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Core(TM) i3-10110U CPU @ 2.10GHz, 3691.40 MHz, 06-8e-0c
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,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,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES

cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 1, core 0, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i3-10110U CPU @ 2.10GHz, 3691.40 MHz, 06-8e-0c
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,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,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES

cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 120 pins
acpimcfg0 at acpi0
acpimcfg0: addr 0xe000, bus 0-255
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 -1 (RP04)
acpiprt5 at

Re: Shell account service providers

2020-07-19 Thread Chris Cappuccio 
Adrian Grigore [adrian.emil.grig...@gmail.com] wrote:
> https://tilde.institute/
> 

That's a cool project. Shell environments are the original social network.

Kernel panic probably linked to inteldrm

2020-07-19 Thread Jérôme FRGACIC 

Hi misc@,

I have installed OpenBSD 6.7 on a new laptop and I experiment regular 
kernel panic. Unfortunately, I lack of information because ddb doesn't 
start when it happens.


After some researches and tests, I've disabled inteldrm at kernel level 
and since I don't experience any kernel panic. So, I suppose this is 
linked, but since the behaviour seems to be random I'm not 100% sure.


Is there any way to get more information when a kernel panic happen and 
ddb doesn't start? I see nothing in /var/log/messages nor 
/var/log/Xorg.0.log nor dmesg... And can I try something else in order 
to fix this issue with inteldrm?


I have an Intel UHD Graphics « card ».

I put below the output of dmesg, pcidump -v and Xorg.0.log, if it can help.

Thanks in adavance.

Kind regards,


Jérôme FRGACIC

$ dmesg
OpenBSD 6.7 (GENERIC.MP) #4: Wed Jul 15 11:16:20 MDT 2020

r...@syspatch-67-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8384339968 (7995MB)
avail mem = 8117616640 (7741MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.2 @ 0x97265000 (56 entries)
bios0: vendor INSYDE Corp. version "1.07.05" date 10/24/2019
bios0: Notebook NJ50_70CU
acpi0 at bios0: ACPI 5.1
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP UEFI SSDT SSDT LPIT WSMT SSDT DBGP DBG2 SSDT 
SSDT NHLT HPET APIC MCFG SSDT FPDT BGRT
acpi0: wakeup devices XHC_(S3) HDAS(S4) RP01(S3) PXSX(S4) RP02(S3) 
PXSX(S4) RP03(S3) PXSX(S4) RP04(S3) PXSX(S4) RP05(S3) PXSX(S4) RP06(S3) 
PXSX(S4) RP07(S3) PXSX(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) i3-10110U CPU @ 2.10GHz, 15439.45 MHz, 06-8e-0c
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,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,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES

cpu0: 256KB 64b/line 8-way L2 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) i3-10110U CPU @ 2.10GHz, 3691.42 MHz, 06-8e-0c
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,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,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES

cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Core(TM) i3-10110U CPU @ 2.10GHz, 3691.40 MHz, 06-8e-0c
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,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,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES

cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 1, core 0, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i3-10110U CPU @ 2.10GHz, 3691.41 MHz, 06-8e-0c
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,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,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES

cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 120 pins
acpimcfg0 at acpi0
acpimcfg0: addr 0xe000, bus 0-255
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 -1 (RP04)
acpiprt5 at acpi0: bus -1 (RP05)
acpiprt6 at acpi0: bus -1 (RP06)
acpiprt7 at acpi0: bus -1 (RP07)
acpiprt8 at acpi0: bus -1 (RP08)
acpiprt9 at

Re: dhcpd synchronization: leases recovery after downtime

2020-07-19 Thread Guy Godfroy 
Hello Edgar,

Le 19/07/2020 à 00:35, ed...@pettijohn-web.com a écrit :
> Not sure how to integrate it properly but this sounds like a job for
> ifstated(8).

Triggering a sync at interface up status change wouldn't be enough: for
instance if only dhcpd crashes and recovers later, there is no change on
interface status.

Re: dhcpd synchronization: leases recovery after downtime

2020-07-19 Thread Guy Godfroy 
Hello Janne,

Le 19/07/2020 à 10:21, Janne Johansson a écrit :
> 2) dhcpd checks that ip's don't reply to ping (or exist in arp?) before
> handing out an ip from a dynamic range

How did you check that? I'm not as sure as you about that. For instance
if you define a static lease for a given machine, you have to exclude
the IP address from your dynamic range. So I don't think there is any
kind of check if the address is free on the network before assigning it.
There is no such piece of information in the man page either.

Also, even if it worked, I would like to know the purpose of the lease
sync mechanism; indeed, because of the lack of downtime recovery, high
availability isn't the reason of its existence.

Re: dhcpd synchronization: leases recovery after downtime

2020-07-19 Thread Janne Johansson 
Den lör 18 juli 2020 kl 23:28 skrev Guy Godfroy :

> Hello,
>
> I am using two routers on OpenBSD (called mulder and scully), and I wish
> to make dhcpd listen on a carp interface between both of them. I am
> using the synchronization mechanism:
>

I noticed the same issue long time ago, but settled for just running two
unconnected dhcpds and made sure that
1) all fixed replies exist on both (and clients don't mind getting two
answers, they pick the first and stop listening for any extra replies)
and
2) dhcpd checks that ip's don't reply to ping (or exist in arp?) before
handing out an ip from a dynamic range

and this seems to cover most of my concerns, no client would get a
different offer from both dhcpds and ack both, and putting as many fixed
entries as possible on important hosts to make sure they would work in any
case.

-- 
May the most significant bit of your life be positive.

Re: Shell account service providers

2020-07-19 Thread Adrian Grigore 
https://tilde.institute/

dum., 19 iul. 2020, 08:47 Chris Cappuccio  a scris:

> ibs...@ripsbusker.no.eu.org [ibs...@ripsbusker.no.eu.org] wrote:
> > Aaron Mason writes:
> > > What are you looking for in such a service?
> >
> > Minimally, SSH login, 100GB disk space, and build tools
> >
> > It's easy enough to find something like this, but it is usually bundled
> > with other stuff and priced accordingly.
> >
> > I'll mostly use it for nmh and mairix.
>
> Why not just buy a cheap vhost?
>
>

Re: non-checksummed UDP packets

2020-07-19 Thread obsdml 


> Is this normal?  

Checksum is OPTIONAL in UDP, not required.  This is covered in RFC 768.

non-checksummed UDP packets

2020-07-19 Thread Peter J. Philipp 
Hi,

I noticed that UDP packets with a checksum of zero (0) make it through the
UDP stack to userland programs.  Is there a knob to turn that off?

Offending packet:

08:38:28.035351 45.148.10.91.80 > 5.9.87.75.53: [no udp cksum] 65534+ [1au] ANY 
(Class 10531)? .(24) (ttl 241, id 35118, len 52)
  : 4500 0034 892e  f111 ac47 2d94 0a5b  E..4...G-..[
  0010: 0509 574b 0050 0035 0020  fffe 0100  ..WK.P.5. ..
  0020: 0001   0001  ff29 2328   ...)#(..
  0030:  

My program:

Jul 19 08:38:28 kite delphinusdnsd[78611]: expand_compression() failed
Jul 19 08:38:28 kite delphinusdnsd[48090]: on descriptor 15 interface "5.9.87.75
" malformed question from 45.148.10.91, drop

OpenBSD's counters:

udp:
1556 datagrams received
0 with incomplete header
0 with bad data length field
0 with bad checksum
234 with no checksum

Is this normal?  Allowing packets with no checksum through makes it so much
easier for level 0 script kiddies.  BTW the checksum of zero should be at 
offset 0x1A in the dump.

Best Regards,

-peter

Re: amdgpu: AMD 5700XT (NAVI10) misreported and non-working

2020-07-19 Thread Jonathan Gray 
On Sun, Jul 19, 2020 at 01:13:51AM -0400, jcm...@gmail.com wrote:
> I saw that much of the amdgpu related drm code had been updated against
> linux 5.7 and decided to try it out using a recent snapshot.  While the
> amdgpu module loads and is able to mirror to both of my displays when in
> a tty, attempting to use startx or starting xenodm results in both
> displays showing a blank black screen.  When this occurs I am unable to
> switch to another tty though I am able to SSH into the system and poke
> around.

Userland support for navi10/gfx1010 requires at least llvm 9.
Currently llvm 8 is in the tree.  We stopped updating when the license
changed for the worse.  With llvm versions being tied to amd hardware
support and newer c++ standards, not updating is becoming increasingly
painful as time goes by so this may have to change in the near future.

I would expect the modesetting driver to be able to run even if amdgpu
with acceleration does not.  I'm not sure why it does not fallback.

> 
> 
> /etc/sysctl.conf
> 
> > machdep.allowaperture=1
> 
> 
> dmesg
> 
> > OpenBSD 6.7-current (GENERIC.MP) #358: Sat Jul 18 11:25:13 MDT 2020
> > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> > real mem = 17111711744 (16319MB)
> > avail mem = 16578068480 (15810MB)
> > random: good seed from bootblocks
> > mpath0 at root
> > scsibus0 at mpath0: 256 targets
> > mainbus0 at root
> > bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xdcecf000 (59 entries)
> > bios0: vendor American Megatrends Inc. version "1.C0" date 09/06/2019
> > bios0: Micro-Star International Co., Ltd. MS-7B79
> > acpi0 at bios0: ACPI 6.0
> > acpi0: sleep states S0 S3 S4 S5
> > acpi0: tables DSDT FACP APIC FPDT FIDT SSDT SSDT SSDT MCFG HPET SSDT UEFI 
> > VFCT IVRS SSDT CRAT CDIT BGRT SSDT SSDT WSMT
> > acpi0: wakeup devices GPP0(S4) GPP1(S4) GPP3(S4) GPP4(S4) GPP5(S4) GPP6(S4) 
> > GPP7(S4) GPP8(S4) GPP9(S4) GPPA(S4) GPPB(S4) GPPC(S4) GPPD(S4) GPPE(S4) 
> > GPPF(S4) GP17(S4) [...]
> > acpitimer0 at acpi0: 3579545 Hz, 32 bits
> > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> > cpu0 at mainbus0: apid 0 (boot processor)
> > cpu0: AMD Ryzen 5 2600 Six-Core Processor, 3400.52 MHz, 17-08-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, 16MB 64b/line 16-way L3 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 Ryzen 5 2600 Six-Core Processor, 3400.00 MHz, 17-08-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, 16MB 64b/line 16-way L3 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: disabling user TSC (skew=102)
> > cpu1: smt 0, core 1, package 0
> > cpu2 at mainbus0: apid 4 (application processor)
> > cpu2: AMD Ryzen 5 2600 Six-Core Processor, 3400.00 MHz, 17-08-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, 16MB 64b/line 16-way L3 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