Jan 21 snapshot - fixed kernel crash

[David Alten]

Hello,

TLDR
I just wanted to send a quick message to say that the Jan 21 snapshot fixed
a kernel issue for me on amd64. The Intel firmware was installed. It also
seems faster than 6.2. Thank you!

Background:
I have a mini PC for testing Elastic. I decided to use it as my desktop.
With 6.1 the video was not supported. With 6.2 it was. However, after a few
minutes in X I started getting regular kernel panics and the box became
unresponsive:

kernel: page fault trap, code=0
Stopped at  pmap_flush_cache+0x30:  clflush 0(%rdi)
ddb{0}>

Just as I was about to reproduce the issue so I could file a bug report I
remembered to try a snapshot. A few minutes later, I had upgraded and could
no longer reproduce the crash!

Anyway, thanks for all the hard work; each upgrade keeps getting better and
better!

Sincerely,
David

OpenBSD 6.2-current (GENERIC.MP) #382: Sun Jan 21 14:13:38 MST 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 16813948928 (16035MB)
avail mem = 16297398272 (15542MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xed9d0 (17 entries)
bios0: vendor American Megatrends Inc. version "P1.30H" date 08/16/2016
bios0: Logic Supply N3160
acpi0 at bios0: rev 2
acpi0: sleep states S0 S4 S5
acpi0: tables DSDT FACP APIC FPDT FIDT AAFT MCFG SSDT SSDT SSDT UEFI LPIT
CSRT
acpi0: wakeup devices XHC1(S4) HDEF(S4) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4)
PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PWRB(S4)
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 N3160 @ 1.60GHz, 1600.44 MHz
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,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT
cpu0: 1MB 64b/line 16-way L2 cache
acpitimer0: recalibrated TSC frequency 1599954218 Hz
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 80MHz
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 N3160 @ 1.60GHz, 1600.01 MHz
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,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT
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 N3160 @ 1.60GHz, 1600.01 MHz
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,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT
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 N3160 @ 1.60GHz, 1600.01 MHz
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,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT
cpu3: 1MB 64b/line 16-way L2 cache
cpu3: smt 0, core 3, package 0
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 115 pins
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (RP01)
acpiprt2 at acpi0: bus 2 (RP02)
acpiprt3 at acpi0: bus -1 (RP03)
acpiprt4 at acpi0: bus -1 (RP04)
acpiec0 at acpi0: not present
acpicpu0 at acpi0: C3(10@1000 mwait.1@0x64), C2(10@500 mwait.1@0x58),
C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: C3(10@1000 mwait.1@0x64), C2(10@500 mwait.1@0x58),
C1(1000@1 mwait.1), PSS
acpicpu2 at acpi0: C3(10@1000 mwait.1@0x64), C2(10@500 mwait.1@0x58),
C1(1000@1 mwait.1), PSS
acpicpu3 at acpi0: C3(10@1000 mwait.1@0x64), C2(10@500 mwait.1@0x58),
C1(1000@1 mwait.1), PSS
acpipwrres0 at acpi0: CLK0, resource for CAMD
acpipwrres1 at acpi0: CLK0, resource for CAM1
acpipwrres2 at acpi0: CLK1, resource for CAM2, CAM3
acpipwrres3 at acpi0: USBC, resource for XHC1
"NTN0530" at acpi0 not configured
"BCM2E64" at acpi0 not configured
"BCM4752" at acpi0 not configured
"SMO91D0" at acpi0 not configured
"INT33F7" at acpi0 not configured
"INT33BE" at acpi0 not configured
"INTCF1C" at acpi0 not configured
"MSFT0002" at acpi0 not configured
acpibtn0 at acpi0: PWRB
acpibtn1 at acpi0: SLPB
acpivideo0 at acpi0: GFX0
acpivout0 at acpivideo0: DD1F
cpu0: Enhanced SpeedStep 1600 MHz: speeds: 1601, 1600, 1520, 1440, 

Re: popen from cgi program

[Jordon]

> Bingo!  I copied all the necessary libs to corresponding usr/lib dirs and got 
> the chrooted programs to run from a chroot command, but they would still not 
> work from the cgi program.  You pointing out that popen requires sh got me 
> thinking.  Sh was already in /var/www/bin but it had 000 for perms.  I make 
> it 111 and it works now!  Thanks!

Looks like I spoke too soon.  The uname and all required libs that i copied 
into the chroot is working fine.  The ping (that was already there) and my 
homemade program both work fine when manually executed in the chroot, but do 
nothing when run through popen().  How do you even debug this?

Re: Flatbed scanner that works well with OpenBSD?

[Abel Abraham Camarillo Ojeda]

On Fri, Jan 19, 2018 at 1:47 PM, Ax0n  wrote:
> Slightly related, I have a CanoScan LiDE 100 that used to work great with
> OpenBSD, using either ScanImage or simple-scan. It's detected, but sometime
> around OpenBSD-5.6 it stopped working. I use it infrequently enough, and I
> have enough computers that I usually just give up and have my wife use her
> Windows laptop to scan for me. I have a slightly vested interest in having
> my only scanner work with my main daily desktop/laptop OS.

Same here with same CanoScan LiDE 100, also don't know precisely when
it stopped working.

>
> I'll try installing some old versions of OpenBSD and see if I can find
> where it broke, and post dmesg's of the before/after mess, if anyone thinks
> that would help.
>
> On Fri, Jan 19, 2018 at 11:38 AM, Anthony J. Bentley 
> wrote:
>
>> Base Pr1me writes:
>> > Did you give your userland user/group permissions to use the uhub/ugen
>> > device?
>>
>> Of course; without that I wasn't able to detect the scanner in the first
>> place.
>>
>> > On Fri, Jan 19, 2018 at 9:59 AM, Anthony J. Bentley 
>> > wrote:
>> >
>> > > Bryan Linton writes:
>> > > > Hello misc@
>> > > >
>> > > > I'm currently looking to purchase a scanner that works well with
>> OpenBSD.
>> > > >
>> > > > I'm aware of the list provided at:
>> > > >
>> > > >   http://www.sane-project.org/sane-mfgs.html
>> > > >
>> > > > but I recently purchased (and returned) a scanner that was listed as
>> > > being
>> > > > fully supported on that list because no matter what I did, I couldn't
>> > > > get it to work right with xsane or scanimage.  Though I purchased it
>> > > used,
>> > > > so it's possible it may have simply been broken from the get-go.
>> > > >
>> > > > Does anyone happen to know of a scanner that is *known* to work well
>> > > > with OpenBSD?
>> > >
>> > > Well, I just bought a CanoScan 9000F MkII specifically because it was
>> > > marked as fully supported on that list, and I can say it does NOT work
>> > > on OpenBSD; scanimage -L detects it just fine but attempting to scan
>> > > gives an I/O error. As a workaround I plugged it into a Linux laptop,
>> > > started saned, and scan seamlessly from OpenBSD with scanimage's
>> network
>> > > support, until I find the time to make a proper bug report.
>> > >
>> > > In the past I used a CanoScan LiDE 20 quite regularly from OpenBSD, but
>> > > that was several years ago.
>> > >
>> > >
>>
>>

Re: Kernel panic with openbsd 6.2

[Mik J]

Hello Stuart,Thank you for your answer.I had my VM running for months in 
version 6.1 and had not problem but I reinstalled it in version 6.2 and the 
problem is happening.It seems to me that something in version 6.2 is producing 
the error.One crash today again
 

Le dimanche 21 janvier 2018 à 11:48:00 UTC+1, Stuart Henderson 
 a écrit :  
 
 On 2018-01-19, Mik J  wrote:
> I had many kernel panic these past days. This is a 6.2 openbsd VM running o=
> n esxi 5.5
>
> # grep "" /tmp/if_vmx.dis

I've reported a lot of vmxnet3_getbuf panics, nobody seems interested.
I suggest switching to e1000 in the vmx file, this works with the em(4)
driver and has been stable so far.


  

Re: Jan 20 snapshot

[Base Pr1me]

Running on this 20180108 kernel now. Here's the dmesg. Seems to be running 
stable now. Normally, I'd be completely hung at this point. Hopefully, I haven't 
screwed all of this up with my intoxication, but, I'm too stubborn to not keep a 
system running! ;)



On 1/21/18 4:10 PM, Stuart Henderson wrote:

On 2018-01-21, Base Pr1me  wrote:

I'll try. Not sure I can keep it running long enough to get dmesg lol. Last
upgrade was ~1 1/2 weeks ago. I know, full of information today. I'll try
and get dmesg this week, when I have more time ... Or wait until newer
snaps and try again.

On Jan 21, 2018 10:37, "Sebastien Marie"  wrote:


On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote:

Anyone else's system hanging randomly after upgrading to yesterday's
snapshot? This isn't a panic that drops to ddb. It's just freezing with

no

response to anything.

A full dmesg would be welcome, and having the date of your previous
version too.

thanks.
--
Sebastien Marie


Moving back to a slightly older kernel and getting dmesg would be useful.

If you have an working bsd.rd on the disk you can drop to a shell and
mount the filesystems, save a copy of /var/run/dmesg.boot (interested
to see any microcode-update related lines from the newer one).

Here's a saved snapshot from a couple of weeks ago you could try:
https://junkpile.org/bsd.mp.20180108.gz

Hopefully that will be stable and you can then send a dmesg showing what's
in the system.


OpenBSD 6.2-current (GENERIC.MP) #333: Sun Jan  7 09:13:00 MST 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 16951357440 (16166MB)
avail mem = 16430698496 (15669MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xbeb88018 (58 entries)
bios0: vendor American Megatrends Inc. version "F2i" date 10/07/2014
bios0: Gigabyte Technology Co., Ltd. 970A-DS3P
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT MCFG HPET BGRT SSDT IVRS
acpi0: wakeup devices SBAZ(S4) PS2K(S3) P0PC(S4) GEC_(S4) UHC1(S4) UHC2(S4) 
USB3(S4) UHC4(S4) USB5(S4) UHC6(S4) UHC7(S4) PE20(S4) PE21(S4) PE22(S4) 
PE23(S4) PC02(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 16 (boot processor)
cpu0: AMD FX(tm)-8320 Eight-Core Processor, 3516.57 MHz
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,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,BMI1
cpu0: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 
16-way L2 cache, 8MB 64b/line 64-way L3 cache
cpu0: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative
cpu0: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative
acpitimer0: recalibrated TSC frequency 3516153538 Hz
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 17 (application processor)
cpu1: AMD FX(tm)-8320 Eight-Core Processor, 3516.14 MHz
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,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,BMI1
cpu1: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 
16-way L2 cache, 8MB 64b/line 64-way L3 cache
cpu1: ITLB 48 4KB entries fully associative, 24 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 18 (application processor)
cpu2: AMD FX(tm)-8320 Eight-Core Processor, 3516.15 MHz
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,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,BMI1
cpu2: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 
16-way L2 cache, 8MB 64b/line 64-way L3 cache
cpu2: ITLB 48 4KB entries fully associative, 24 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 19 (application processor)
cpu3: AMD FX(tm)-8320 Eight-Core Processor, 3516.15 MHz
cpu3: 

Re: Jan 20 snapshot

[Base Pr1me]

Got it ... I hope ... "Gin"ny and all

On 1/21/18 4:10 PM, Stuart Henderson wrote:

On 2018-01-21, Base Pr1me  wrote:

I'll try. Not sure I can keep it running long enough to get dmesg lol. Last
upgrade was ~1 1/2 weeks ago. I know, full of information today. I'll try
and get dmesg this week, when I have more time ... Or wait until newer
snaps and try again.

On Jan 21, 2018 10:37, "Sebastien Marie"  wrote:


On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote:

Anyone else's system hanging randomly after upgrading to yesterday's
snapshot? This isn't a panic that drops to ddb. It's just freezing with

no

response to anything.

A full dmesg would be welcome, and having the date of your previous
version too.

thanks.
--
Sebastien Marie


Moving back to a slightly older kernel and getting dmesg would be useful.

If you have an working bsd.rd on the disk you can drop to a shell and
mount the filesystems, save a copy of /var/run/dmesg.boot (interested
to see any microcode-update related lines from the newer one).

Here's a saved snapshot from a couple of weeks ago you could try:
https://junkpile.org/bsd.mp.20180108.gz

Hopefully that will be stable and you can then send a dmesg showing what's
in the system.


OpenBSD 6.2-current (GENERIC.MP) #379: Sat Jan 20 14:30:55 MST 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 16951357440 (16166MB)
avail mem = 16430669824 (15669MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xbeb88018 (58 entries)
bios0: vendor American Megatrends Inc. version "F2i" date 10/07/2014
bios0: Gigabyte Technology Co., Ltd. 970A-DS3P
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT MCFG HPET BGRT SSDT IVRS
acpi0: wakeup devices SBAZ(S4) PS2K(S3) P0PC(S4) GEC_(S4) UHC1(S4) UHC2(S4) 
USB3(S4) UHC4(S4) USB5(S4) UHC6(S4) UHC7(S4) PE20(S4) PE21(S4) PE22(S4) 
PE23(S4) PC02(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 16 (boot processor)
cpu0: AMD FX(tm)-8320 Eight-Core Processor, 3516.53 MHz
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,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,BMI1
cpu0: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 
16-way L2 cache, 8MB 64b/line 64-way L3 cache
cpu0: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative
cpu0: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative
acpitimer0: recalibrated TSC frequency 3516127432 Hz
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 17 (application processor)
cpu1: AMD FX(tm)-8320 Eight-Core Processor, 3516.11 MHz
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,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,BMI1
cpu1: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 
16-way L2 cache, 8MB 64b/line 64-way L3 cache
cpu1: ITLB 48 4KB entries fully associative, 24 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 18 (application processor)
cpu2: AMD FX(tm)-8320 Eight-Core Processor, 3516.11 MHz
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,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,BMI1
cpu2: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 
16-way L2 cache, 8MB 64b/line 64-way L3 cache
cpu2: ITLB 48 4KB entries fully associative, 24 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 19 (application processor)
cpu3: AMD FX(tm)-8320 Eight-Core Processor, 3516.11 MHz
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,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,BMI1
cpu3: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way 

Re: Jan 20 snapshot

[Base Pr1me]

Cool, thanks. I'll check this out this week. Much gratitude. I'm far too
'ginned' up at the moment. ;)

On Jan 21, 2018 16:13, "Stuart Henderson"  wrote:

> On 2018-01-21, Base Pr1me  wrote:
> > I'll try. Not sure I can keep it running long enough to get dmesg lol.
> Last
> > upgrade was ~1 1/2 weeks ago. I know, full of information today. I'll try
> > and get dmesg this week, when I have more time ... Or wait until newer
> > snaps and try again.
> >
> > On Jan 21, 2018 10:37, "Sebastien Marie"  wrote:
> >
> >> On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote:
> >> > Anyone else's system hanging randomly after upgrading to yesterday's
> >> > snapshot? This isn't a panic that drops to ddb. It's just freezing
> with
> >> no
> >> > response to anything.
> >>
> >> A full dmesg would be welcome, and having the date of your previous
> >> version too.
> >>
> >> thanks.
> >> --
> >> Sebastien Marie
> >>
> >
>
> Moving back to a slightly older kernel and getting dmesg would be useful.
>
> If you have an working bsd.rd on the disk you can drop to a shell and
> mount the filesystems, save a copy of /var/run/dmesg.boot (interested
> to see any microcode-update related lines from the newer one).
>
> Here's a saved snapshot from a couple of weeks ago you could try:
> https://junkpile.org/bsd.mp.20180108.gz
>
> Hopefully that will be stable and you can then send a dmesg showing what's
> in the system.
>
>
>

Re: Jan 20 snapshot

[Stuart Henderson]

On 2018-01-21, Base Pr1me  wrote:
> I'll try. Not sure I can keep it running long enough to get dmesg lol. Last
> upgrade was ~1 1/2 weeks ago. I know, full of information today. I'll try
> and get dmesg this week, when I have more time ... Or wait until newer
> snaps and try again.
>
> On Jan 21, 2018 10:37, "Sebastien Marie"  wrote:
>
>> On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote:
>> > Anyone else's system hanging randomly after upgrading to yesterday's
>> > snapshot? This isn't a panic that drops to ddb. It's just freezing with
>> no
>> > response to anything.
>>
>> A full dmesg would be welcome, and having the date of your previous
>> version too.
>>
>> thanks.
>> --
>> Sebastien Marie
>>
>

Moving back to a slightly older kernel and getting dmesg would be useful.

If you have an working bsd.rd on the disk you can drop to a shell and
mount the filesystems, save a copy of /var/run/dmesg.boot (interested
to see any microcode-update related lines from the newer one).

Here's a saved snapshot from a couple of weeks ago you could try:
https://junkpile.org/bsd.mp.20180108.gz

Hopefully that will be stable and you can then send a dmesg showing what's
in the system.

Re: popen from cgi program

[Jordon]

> popen() requires a shell. You are most likely running it in a chroot and
> don't have /bin/sh.

Bingo!  I copied all the necessary libs to corresponding usr/lib dirs and got 
the chrooted programs to run from a chroot command, but they would still not 
work from the cgi program.  You pointing out that popen requires sh got me 
thinking.  Sh was already in /var/www/bin but it had 000 for perms.  I make it 
111 and it works now!  Thanks!

Re: Jan 20 snapshot

[Base Pr1me]

Ok, thanks.

On Jan 21, 2018 11:02, "Sebastien Marie"  wrote:

> On Sun, Jan 21, 2018 at 06:44:56PM +0100, Adam Wolk wrote:
> > On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote:
> > > Anyone else's system hanging randomly after upgrading to yesterday's
> > > snapshot? This isn't a panic that drops to ddb. It's just freezing
> with no
> > > response to anything.
> >
> > I haven't notice any problems with:
> > kern.version=OpenBSD 6.2-current (GENERIC.MP) #379: Sat Jan 20 14:30:55
> MST 2018
>
> I reported a problem (unexpected reboots) with recent snapshots (and not
> reproductible with rebuilt kernel).
>
> I quickly check with binary diffing for changes and snapshots have
> uncommited changes.
>
> It is why I asked for dmesg and previous working snap.
> --
> Sebastien Marie
>

Re: Jan 20 snapshot

[Sebastien Marie]

On Sun, Jan 21, 2018 at 06:44:56PM +0100, Adam Wolk wrote:
> On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote:
> > Anyone else's system hanging randomly after upgrading to yesterday's
> > snapshot? This isn't a panic that drops to ddb. It's just freezing with no
> > response to anything.
> 
> I haven't notice any problems with:
> kern.version=OpenBSD 6.2-current (GENERIC.MP) #379: Sat Jan 20 14:30:55 MST 
> 2018

I reported a problem (unexpected reboots) with recent snapshots (and not
reproductible with rebuilt kernel).

I quickly check with binary diffing for changes and snapshots have
uncommited changes.

It is why I asked for dmesg and previous working snap.
-- 
Sebastien Marie

Re: Jan 20 snapshot

[Base Pr1me]

Ty.

On Jan 21, 2018 10:45, "Adam Wolk"  wrote:

> On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote:
> > Anyone else's system hanging randomly after upgrading to yesterday's
> > snapshot? This isn't a panic that drops to ddb. It's just freezing with
> no
> > response to anything.
>
> I haven't notice any problems with:
> kern.version=OpenBSD 6.2-current (GENERIC.MP) #379: Sat Jan 20 14:30:55
> MST 2018
>
> Regards,
> Adam
>

Re: Jan 20 snapshot

[Base Pr1me]

I'll try. Not sure I can keep it running long enough to get dmesg lol. Last
upgrade was ~1 1/2 weeks ago. I know, full of information today. I'll try
and get dmesg this week, when I have more time ... Or wait until newer
snaps and try again.

On Jan 21, 2018 10:37, "Sebastien Marie"  wrote:

> On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote:
> > Anyone else's system hanging randomly after upgrading to yesterday's
> > snapshot? This isn't a panic that drops to ddb. It's just freezing with
> no
> > response to anything.
>
> A full dmesg would be welcome, and having the date of your previous
> version too.
>
> thanks.
> --
> Sebastien Marie
>

Re: Jan 20 snapshot

[Adam Wolk]

On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote:
> Anyone else's system hanging randomly after upgrading to yesterday's
> snapshot? This isn't a panic that drops to ddb. It's just freezing with no
> response to anything.

I haven't notice any problems with:
kern.version=OpenBSD 6.2-current (GENERIC.MP) #379: Sat Jan 20 14:30:55 MST 2018

Regards,
Adam

Re: Jan 20 snapshot

[Sebastien Marie]

On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote:
> Anyone else's system hanging randomly after upgrading to yesterday's
> snapshot? This isn't a panic that drops to ddb. It's just freezing with no
> response to anything.

A full dmesg would be welcome, and having the date of your previous
version too.

thanks.
-- 
Sebastien Marie

Jan 20 snapshot

[Base Pr1me]

Anyone else's system hanging randomly after upgrading to yesterday's
snapshot? This isn't a panic that drops to ddb. It's just freezing with no
response to anything.

Re: Flatbed scanner that works well with OpenBSD?

[Freddy Fisker]

I have an Epson WP-4595 Network Multifunction Printer, and the scanner 
works fine with XSane.


I also have an older Epson Perfection 2480 Photo USB scanner, but it needs 
a Firmware to run.

Re: usewithtor lynx core: pledge "getpw", syscall 33

[Stuart Henderson]

On 2018/01/21 12:35, Sebastien Marie wrote:
> On Sun, Jan 21, 2018 at 10:25:30AM +, Stuart Henderson wrote:
> > On 2018-01-20, clematis  wrote:
> > > Hello,
> > > 'usewithtor' (torsocks) works fine with ftp and ssh but it will core
> > > with lynx. 
> > > running: usewithtor lynx
> > > will start lynx, resolve openbsd.org but core when trying to make the
> > > http connection.
> > > In /var/log/messages I get: /bsd: lynx[26197]: pledge "getpw", syscall 33
> > >
> > > And running gdb lynx then core lynx.core: 
> > > ---
> > > Reading symbols from /usr/libexec/ld.so...done.   
> > >   
> > >
> > > Loaded symbols for /usr/libexec/ld.so 
> > >   
> > >
> > > #0  access () at -:3  
> > >   
> > >
> > > 3   -: No such file or directory. 
> > >   
> > >
> > > in -  
> > >   
> > >
> > > Current language:  auto; currently asm
> > > ---
> > >
> > > same result using 'torsocks' directly and not 'usewithtor' or trying
> > > lynx http://openbsd.org
> > >
> > >
> > > Config: OpenBSD current + lynx-2.8.9pl16 + torsocks-1.2p4
> > >
> > > Any idea on how to torify lynx?
> > >
> > > Thanks,
> > 
> > What happens if you just replace the getpwuid functions in torsocks
> > with NULL? They don't seem terribly useful for sending to a local tor
> > proxy, they're more relevant for communicating with a standard socks
> > server with authentication (and even then you can pass the username via
> > a config file or environment variable).. Does that make it work or does
> > it then fail on something else?
> 
> removing getpw calls is enought: lynx works well with torsocks this way.
> 
> in fact, it could reduces a bit the SOCKS support, as for socks4 and
> socks4a the environment variable isn't used (only for socks5). but as
> torsocks explicitly targets Tor proxy, I think it don't bother.
> 
> > Otherwise torsocks could wrap the pledge() function to weaken the pledge.
> > It's easy to do but far less appealing.
> 
> In fact, I started in this direction... so if you want a working diff to
> add "getpw" in pledge(2) promise, it is available.
> 
> but removing getpw calls if far better.

I've sent torsocks MAINTAINER the ports diff to remove getpw*.
Definitely seems the right way to go.

Re: usewithtor lynx core: pledge "getpw", syscall 33

[Stuart Henderson]

On 2018-01-21, Juan Francisco Cantero Hurtado  wrote:
> Another idea. Create a special user only for tor use, then add the
> proper rules to pf to pass its traffic to the tor daemon.

Oh, please no. Not until it's fixed to avoid the DIOCNATLOOK crap
that requires giving tor access to /dev/pf. Just needs some changes
to use getsockname (which work with divert-to rules) like it does
on some other OS.

Re: usewithtor lynx core: pledge "getpw", syscall 33

[unk]

Hello,

2018-01-20 22:13 GMT+03:00 clematis :
>
>
>
> Any idea on how to torify lynx?
>
>
Fresh tor 0.3.2.9 from ports can works as HTTP proxy:
---
HTTPTunnelPort [address:]port|auto [isolation flags]

Open this port to listen for proxy connections using the "HTTP
CONNECT" protocol instead of SOCKS. Set this to 0 0 if you don’t want
to allow "HTTP CONNECT" connections. Set the port to "auto" to have
Tor pick a port for you. This directive can be specified multiple
times to bind to multiple addresses/ports. See SOCKSPort for an
explanation of isolation flags. (Default: 0)
---

Re: usewithtor lynx core: pledge "getpw", syscall 33

[Juan Francisco Cantero Hurtado]

On Sun, Jan 21, 2018 at 07:05:20AM +0100, Sebastien Marie wrote:
> On Sat, Jan 20, 2018 at 07:13:54PM +, clematis wrote:
> > Hello,
> > 'usewithtor' (torsocks) works fine with ftp and ssh but it will core
> > with lynx. 
> > running: usewithtor lynx
> > will start lynx, resolve openbsd.org but core when trying to make the
> > http connection.
> > In /var/log/messages I get: /bsd: lynx[26197]: pledge "getpw", syscall 33
> > 
> > And running gdb lynx then core lynx.core: 
> > ---
> > Reading symbols from /usr/libexec/ld.so...done. 
> > 
> >
> > Loaded symbols for /usr/libexec/ld.so   
> > 
> >
> > #0  access () at -:3
> > 
> >
> > 3   -: No such file or directory.   
> > 
> >
> > in -
> > 
> >
> > Current language:  auto; currently asm
> > ---
> > 
> > same result using 'torsocks' directly and not 'usewithtor' or trying
> > lynx http://openbsd.org
> 
> I will reply mainly on the pledge aspect.
> 
> The way torsocks is done is to replace some syscall/libc libary calls by
> other ones (by using LD_PRELOAD trick). The replaced functions are
> network related (connect(2) for example) in order to catch TCP
> connection and replacing it by another one wrapper on SOCKS protocol
> (connect to proxy, ask for particular terminaison point, and pass it
> to program stuff).
> 
> It is some sort of MITM, but at the code program level.
> 
> The pledge(2) policy done for lynx assumes a specific behaviour. By
> replacing some code by another, torsocks did some additional stuff not
> in the initial pledge policy (getting information on users with getpw
> family here), and the kernel detects this pledge violation.
>  
> > Config: OpenBSD current + lynx-2.8.9pl16 + torsocks-1.2p4
> > 
> > Any idea on how to torify lynx?
> 
> the simpler would be to use lynx options to connect to SOCKS proxy. I am
> unsure the current code has this possibility. But as it have HTTP proxy
> support, a way could be to have an HTTP proxy listener which forward its
> traffic to SOCKS upstream server. Polipo is a program of this kind (see
> socksParentProxy="localhost:9050" and socksProxyType=socks5 parameters
> on polipo config file).

Another idea. Create a special user only for tor use, then add the
proper rules to pf to pass its traffic to the tor daemon.


-- 
Juan Francisco Cantero Hurtado http://juanfra.info

Re: usewithtor lynx core: pledge "getpw", syscall 33

[clematis]

Hi Sebastien, Stuart, 
Thank you both for your reply.

On Sun, Jan 21, 2018 at 10:25:30AM +, Stuart Henderson wrote:
> What happens if you just replace the getpwuid functions in torsocks
> with NULL? They don't seem terribly useful for sending to a local tor
> proxy, they're more relevant for communicating with a standard socks
> server with authentication (and even then you can pass the username via
> a config file or environment variable).. Does that make it work or does
> it then fail on something else?

It does make it works. (Properly through tor). .onion are also
reachable. So all seems pretty good.

getting:
libtorsocks(86898): Call to connect received on completed request 3 

No other messages.

Thanks,

-- 
clematis (0x7e96fd2400fe7b59)

Re: usewithtor lynx core: pledge "getpw", syscall 33

[Sebastien Marie]

On Sun, Jan 21, 2018 at 10:25:30AM +, Stuart Henderson wrote:
> On 2018-01-20, clematis  wrote:
> > Hello,
> > 'usewithtor' (torsocks) works fine with ftp and ssh but it will core
> > with lynx. 
> > running: usewithtor lynx
> > will start lynx, resolve openbsd.org but core when trying to make the
> > http connection.
> > In /var/log/messages I get: /bsd: lynx[26197]: pledge "getpw", syscall 33
> >
> > And running gdb lynx then core lynx.core: 
> > ---
> > Reading symbols from /usr/libexec/ld.so...done. 
> > 
> >
> > Loaded symbols for /usr/libexec/ld.so   
> > 
> >
> > #0  access () at -:3
> > 
> >
> > 3   -: No such file or directory.   
> > 
> >
> > in -
> > 
> >
> > Current language:  auto; currently asm
> > ---
> >
> > same result using 'torsocks' directly and not 'usewithtor' or trying
> > lynx http://openbsd.org
> >
> >
> > Config: OpenBSD current + lynx-2.8.9pl16 + torsocks-1.2p4
> >
> > Any idea on how to torify lynx?
> >
> > Thanks,
> 
> What happens if you just replace the getpwuid functions in torsocks
> with NULL? They don't seem terribly useful for sending to a local tor
> proxy, they're more relevant for communicating with a standard socks
> server with authentication (and even then you can pass the username via
> a config file or environment variable).. Does that make it work or does
> it then fail on something else?

removing getpw calls is enought: lynx works well with torsocks this way.

in fact, it could reduces a bit the SOCKS support, as for socks4 and
socks4a the environment variable isn't used (only for socks5). but as
torsocks explicitly targets Tor proxy, I think it don't bother.

> Otherwise torsocks could wrap the pledge() function to weaken the pledge.
> It's easy to do but far less appealing.

In fact, I started in this direction... so if you want a working diff to
add "getpw" in pledge(2) promise, it is available.

but removing getpw calls if far better.

Thanks.
-- 
Sebastien Marie

Re: Flatbed scanner that works well with OpenBSD?

[Robert]

A couple of people started to recommend network-attached devices.

I would be careful with this. Those devices often utilize an ancient embedded 
Linux or Windows, with lots of proprietary daemons of questionable quality 
("features before security!") exposed to the network.
There are tons of CVEs and vulnerabilities for those devices.
If you consider such a device, at least do a vulnerability search about it 
first.
If you are paranoid, connect it through a dedicated NIC and non-routed local 
network to your computer.

For a single user I very much prefer a locally attached USB device than 
introducing such a risk into a network.
YMMV.

regards,
Robert

Re: Kernel panic with openbsd 6.2

[Stuart Henderson]

On 2018-01-19, Mik J  wrote:
> I had many kernel panic these past days. This is a 6.2 openbsd VM running o=
> n esxi 5.5
>
> # grep "" /tmp/if_vmx.dis

I've reported a lot of vmxnet3_getbuf panics, nobody seems interested.
I suggest switching to e1000 in the vmx file, this works with the em(4)
driver and has been stable so far.

Re: After 6.1amd64 -> 6.2amd64 upgrade namecoind malloc(): free(): error

[Otto Moerbeek]

On Sun, Jan 21, 2018 at 11:21:12AM +0100, Otto Moerbeek wrote:

> On Sun, Jan 21, 2018 at 12:41:50PM +0300, Denis wrote:
> 
> > I used namecoin on 6.1amd64 statically builded from source using boost
> > 1.61 library. All works pretty fine before upgrade to 6.2amd64.
> > 
> > I have rebuilt the the same namecoin source with boost 1.61 lib statically.
> > After running it on OpenBSD6.2amd64 I see the error with malloc() and
> > free() listed below:
> > 
> > namecoind (4563) malloc():bogus pointer (double free?) 0xdfdfdfdfdfdfdfdf
> > namecoind (4563) free(): chunk is already free 0x1bc9981cae20
> > 
> > Is something changed in malloc() since than?
> > How to get work statically built  namecoin on 6.2?
> > 
> > Thank you for answer in advance.
> > 
> > Denis
> 
> Yes, a few things changed, making malloc more strict.
> This is almost certainly a bug wrt memory management in namecoind. 
> 
>   -Otto

To diagnose this further, you can play with malloc options. See man
malloc.conf.
e.g. run with option S, which is even more strict. That might give you
a hint where the bug is.

-Otto

Re: Flatbed scanner that works well with OpenBSD?

[Stuart Henderson]

On 2018-01-19, Predrag Punosevac  wrote:
> Bryan Linton writes:
>> Hello misc@
>>
>> I'm currently looking to purchase a scanner that works well with OpenBSD.
>>
>> I'm aware of the list provided at: 
>>
>> 0211038.pdf Desktop Documents Downloads Library Movies Music Pictures 
>> Programs Videos s-nail.corehttp://www.sane-project.org/sane-mfgs.html
>>
>> but I recently purchased (and returned) a scanner that was listed as being
>> fully supported on that list because no matter what I did, I couldn't
>> get it to work right with xsane or scanimage.  Though I purchased it used,
>> so it's possible it may have simply been broken from the get-go.
>>
>> Does anyone happen to know of a scanner that is *known* to work well
>> with OpenBSD?
>
>
> This is a very silly question. Most modern all-in-one office grade
> devices can scan directly onto an umass device or into the e-mail. You
> don't need OpenBSD to scan. The scan quality fall within technical
> requirements you have.

I have a couple-of-years-old HP all-in-one network printer/scanner, it
was pretty cheap (I think I bought it in LIDL), works fine with xsane,
I'm using the hpaio/hpcups/hplip drivers over the network from OpenBSD
(also no problems with macos/windows).

I doubt the same model (Officejet_4500_G510g-m) would still be available
but in general the hpaio-supported things shouldn't be too awkward.

Re: popen from cgi program

[Stuart Henderson]

On 2018-01-20, Jordon  wrote:
> I am still learning cgi/web stuff and stumbled upon an issue.  I am 
> trying to popen() a program to catch what it dumps to stdout.  To start 
> simply, I am just trying to run uname.  I get nothing.  No errors on 
> popen() or pclose(), but nothing printed.  I run the same code from a 
> regular cpp program (changing the khtml_puts() to printf() and it works 
> perfectly.  That makes me wonder if there is something environmental 
> that I am missing, or maybe this is just not allowed.
>
> My code is this:
>
>    char dump[1024];
>    memset(dump, 0, sizeof(dump));
>    FILE *f = popen("uname -a", "r");
>    if(f == NULL) {
>      khtml_puts(, "popen()FAILED!");
>    } else {
>      khtml_puts(, "output: ");
>      while (fgets(dump, sizeof(dump), f) != NULL) {
>    khtml_puts(, "GOTSOMETHING!");
>    khtml_puts(, dump);
>      }
>      int status = pclose(f);
>      if(status==-1) {
>    khtml_puts(, "pclose()FAILED");
>      }
>    }
>    khtml_puts(, "done");
>
>
> All I get from it is "output: done"
>
>
>
> Also, my httpd.conf is this:
>
> ext_addr="egress"
> prefork 2
> server "localhost" {
>      listen on $ext_addr port 80
>      root "/htdocs"
>      location "/cgi-bin/*" {
>      fastcgi
>      root "/"
>      }
> }
>
> Any ideas?
>
>

popen() requires a shell. You are most likely running it in a chroot and
don't have /bin/sh.

Re: Trying to use OpenBSD as webserver, inside home network (ADSL internet connection)

[Michel von Behr]

Thank you! I received several answers, mostly in private. I was able to
solve the issue, but it had nothing to do with the OpenBSD machine. Some
brief comments:

1) About DMZ (Demilitarised Zone), I tried configuring the router with and
without putting my OpenBSD laptop in DMZ (unfortunately it didn't change
the results).

2) I'm including PF config here - no change from defaults. I'm assuming for
now I shouldn't bother with PF config in this context, but please let me
know if I'm wrong.

3) What I did was to reset the cheap modem/router to factory settings
(because at a certain point the whole thing was a bit of a chaotic tweaked
mess!), put it in bridge mode, and disabled DHCP. I then connected the
cheap modem to the TP-Link WAN input, and configured PPPoE using the same
config that was being used in the cheap modem/router. It worked like a
charm! :-)

Thanks for the tips anyway!


On Fri, Jan 19, 2018 at 2:29 PM, Oliver Marugg  wrote:

> hi
>
> check: which device does nat for you. On that device configure
> portforwarding from external to internal, eg external ip:port to your
> internal host:port. test it from outside.
>
> ip forwarding on your OpenBSD laptop isnt necessary here, your laptop
> doesnt act as a router in your homesetup.
>
> -om
>
>
>
> On 19 Jan 2018, at 15:55, Michel von Behr wrote:
>
> Hi - rookie question: I have ADSL internet at home, distributed to local
>> hosts via a cheap modem/router provided by the ISP. And connected as one
>> of
>> the network nodes is an old laptop running OpenBSD. I want to use that
>> laptop as a webserver, ftp server, etc. I can connect to the laptop
>> internally, from within the local network (192.168.15.11) via http, ssh,
>> ftp, etc, but I can't see it from external hosts. I already tried
>> different
>> configurations in the router/modem related to port forwarding, NAT, but
>> without success, so I'm starting to think that it might be something I'm
>> missing on OpenBSD network config (PF maybe?).
>>
>> I tried enabling ip forwarding in sysctl but I still can't see it from
>> outside hosts.
>>
>> Specifically, my question would be this: if I can see my laptop from
>> within
>> the local network, would that be enough to guarantee that I should be able
>> to detect it externally? If not, what configuration should I be looking to
>> adjust?
>>
>> httpd.conf is accepting connections from any IP address, as far as I
>> understand this:
>>
>> # $OpenBSD: httpd.conf,v 1.17 2017/04/16 08:50:49 ajacoutot Exp $
>>
>> #
>> # Macros
>> #
>> ext_addr="*"
>>
>> #
>> # Global Options
>> #
>> # prefork 3
>>
>>
>> #
>> # Servers
>> #
>>
>> # A minimal default server
>> server "default" {
>> listen on $ext_addr port 80
>> listen on $ext_addr port 8080
>> listen on $ext_addr port 50080
>> root "/htdocs/"
>> directory {
>> no index
>> }
>>
>> location "*.php" {
>> fastcgi socket "/run/php-fpm.sock"
>> }
>> }
>>
>> As for ssh_config the only change I made to the default config file was to
>> include port 50022 (trying to avoid any blocking to port 22 that my ISP
>> might be enforcing).
>>
>> Any pointing to the right direction would be appreciated...
>>
>> Kind regards,
>>
>> Michel
>>
>

Re: usewithtor lynx core: pledge "getpw", syscall 33

[Stuart Henderson]

On 2018-01-20, clematis  wrote:
> Hello,
> 'usewithtor' (torsocks) works fine with ftp and ssh but it will core
> with lynx. 
> running: usewithtor lynx
> will start lynx, resolve openbsd.org but core when trying to make the
> http connection.
> In /var/log/messages I get: /bsd: lynx[26197]: pledge "getpw", syscall 33
>
> And running gdb lynx then core lynx.core: 
> ---
> Reading symbols from /usr/libexec/ld.so...done.   
>   
>
> Loaded symbols for /usr/libexec/ld.so 
>   
>
> #0  access () at -:3  
>   
>
> 3   -: No such file or directory. 
>   
>
> in -  
>   
>
> Current language:  auto; currently asm
> ---
>
> same result using 'torsocks' directly and not 'usewithtor' or trying
> lynx http://openbsd.org
>
>
> Config: OpenBSD current + lynx-2.8.9pl16 + torsocks-1.2p4
>
> Any idea on how to torify lynx?
>
> Thanks,

What happens if you just replace the getpwuid functions in torsocks
with NULL? They don't seem terribly useful for sending to a local tor
proxy, they're more relevant for communicating with a standard socks
server with authentication (and even then you can pass the username via
a config file or environment variable).. Does that make it work or does
it then fail on something else?

Otherwise torsocks could wrap the pledge() function to weaken the pledge.
It's easy to do but far less appealing.

Index: src/socks.c
--- src/socks.c.orig
+++ src/socks.c
@@ -281,7 +281,7 @@ static int send_socksv4a_request(struct connreq *conn,
 struct sockreq *thisreq;
 int endOfUser;
 /* Determine the current username */
-user = getpwuid(getuid());
+user = NULL;
 
 thisreq = (struct sockreq *) conn->buffer;
 endOfUser=sizeof(struct sockreq) +
@@ -324,7 +324,7 @@ static int send_socksv4_request(struct connreq *conn)
 struct sockreq *thisreq;
 
 /* Determine the current username */
-user = getpwuid(getuid());
+user = NULL;
 
 thisreq = (struct sockreq *) conn->buffer;
 
@@ -493,7 +493,7 @@ static int read_socksv5_method(struct connreq *conn)
 show_msg(MSGDEBUG, "SOCKS V5 server chose username/password 
authentication\n");
 
 /* Determine the current *nix username */
-nixuser = getpwuid(getuid());
+nixuser = NULL;
 
 if (((uname = conn->path->defuser) == NULL) &&
   ((uname = getenv("TORSOCKS_USERNAME")) == NULL) &&

Re: After 6.1amd64 -> 6.2amd64 upgrade namecoind malloc(): free(): error

[Otto Moerbeek]

On Sun, Jan 21, 2018 at 12:41:50PM +0300, Denis wrote:

> I used namecoin on 6.1amd64 statically builded from source using boost
> 1.61 library. All works pretty fine before upgrade to 6.2amd64.
> 
> I have rebuilt the the same namecoin source with boost 1.61 lib statically.
> After running it on OpenBSD6.2amd64 I see the error with malloc() and
> free() listed below:
> 
> namecoind (4563) malloc():bogus pointer (double free?) 0xdfdfdfdfdfdfdfdf
> namecoind (4563) free(): chunk is already free 0x1bc9981cae20
> 
> Is something changed in malloc() since than?
> How to get work statically built  namecoin on 6.2?
> 
> Thank you for answer in advance.
> 
> Denis

Yes, a few things changed, making malloc more strict.
This is almost certainly a bug wrt memory management in namecoind. 

-Otto

After 6.1amd64 -> 6.2amd64 upgrade namecoind malloc(): free(): error

[Denis]

I used namecoin on 6.1amd64 statically builded from source using boost
1.61 library. All works pretty fine before upgrade to 6.2amd64.

I have rebuilt the the same namecoin source with boost 1.61 lib statically.
After running it on OpenBSD6.2amd64 I see the error with malloc() and
free() listed below:

namecoind (4563) malloc():bogus pointer (double free?) 0xdfdfdfdfdfdfdfdf
namecoind (4563) free(): chunk is already free 0x1bc9981cae20

Is something changed in malloc() since than?
How to get work statically built  namecoin on 6.2?

Thank you for answer in advance.

Denis

Re: Intel C610 azalia (ALC888) not configuring at /dev/audio

[Alexandre Ratchov]

On Fri, Jan 19, 2018 at 05:23:06PM -0800, yu...@cock.li wrote:
> Hello,
> 
> I have just installed the latest snapshot and audio is not configuring,
> i.e. the output of mixerctl, audioctl, et al are "device not configured".
> My motherboard is a Supermicro X10DAL-I-O, which has the Intel C610
> chipset, and the audio codec is the Realtek ALC888, although the latter
> is not immediately relevant, as the azalia driver does not even get to
> the stage of evaluating the codec; pertinent dmesg output with GENERIC.MP
> modified with AZALIA_DEBUG enabled:

Thanks, the output of AZALIA_DEBUG is very useful. So, you confirm
that this used to work, and something broke it in last snaps.

Are there audio-related BIOS options that may have changed recently,
including because of BIOS update or whatever?

> azalia1 at pci0 dev 27 function 0 "Intel C610 HD Audio" rev 0x05: msi
> azalia_reset: resetting
> azalia_reset: reset counter = 0
> azalia1: reset failure
> azalia_pci_detach
> azalia_pci_detach: delete streams
> azalia_pci_detach: delete codecs
> azalia_pci_detach: delete CORB and RIRB
> azalia_pci_detach: disable interrupts
> azalia_pci_detach: clear interrupts
> azalia_pci_detach: delete PCI resources
> 
> For reference, azalia0 was my AMD GPU's HDMI/DisplayPort audio (I
> understand from the man page that this is unsupported; thankfully I
> have no need of it).
> 
> Grepping through the source shows that this is a supported chipset;
> what gives? Any and all help is appreciated. Might it have something
> to do with it being the second device that azalia(4) tries to set up?

There's no interaction between azalia1 and azalia0.

Re: Problems with inteldrm on ASRock J3455-ITX (Apollo Lake)

[Nils Reuße]

Hi all,

with the help of Chris i finally got it working and i'm happily writing this 
email from X!  I broke it down to these two settings one has to change in the 
UEFI:

* Disable c-states and enable legacy BIOS:

  - Advanced -> CPU Configuration -> CPU C States Support => Disable
  - Boot -> CSM => Enable

Also, i had to connect my monitor with VGA, with DVI the screen goes black when 
the graphics card gets initialized (did not try HDMI).

I'm a bit confused about the xrandr output, there's no VGA and no DVI, but eDP 
and DP, and also two HDMI connectors shown, even though the board only has one. 
 Could this be firmware—related?  Anyway, it works:

$ xrandr -q
Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 8192 x 8192
eDP-1 connected primary 1680x1050+0+0 (normal left inverted right x axis y 
axis) 474mm x 296mm
   1680x1050 59.88*+
   1400x1050 59.98
   1280x1024 75.0260.02
   1280x960  60.00
   1152x864  75.00
   1024x768  60.0475.0875.0370.0760.00
   960x720   60.00
   928x696   75.0060.05
   896x672   75.0560.01
   832x624   74.55
   800x600   75.0070.0065.0060.0072.1975.0060.32
56.25
   700x525   74.7659.98
   640x512   75.0260.02
   640x480   60.0075.0072.8172.8175.0066.6760.00
59.94
   720x400   70.08
   576x432   75.00
   512x384   75.0370.0760.00
   416x312   74.66
   400x300   72.1975.1260.3256.34
   320x240   72.8175.0060.05
DP-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)
HDMI-2 disconnected (normal left inverted right x axis y axis)

Here's an excerpt from dmesg for drm (full dmesg attached):

$ dmesg | grep -i drm
inteldrm0 at pci0 dev 2 function 0 vendor "Intel", unknown product 0x5a85 rev 
0x0b
drm0 at inteldrm0
inteldrm0: msi
error: [drm:pid0:i915_firmware_load_error_print] *ERROR* failed to load 
firmware i915/bxt_dmc_ver1.bin (-22)
error: [drm:pid0:i915_gem_init_hw] *ERROR* Failed to initialize GuC, error -8 
(ignored)
inteldrm0: 1680x1050, 32bpp
wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation)
error: [drm:pid51995:intel_pipe_update_start] *ERROR* Potential atomic update 
failure on pipe A


I can quit from cwm to console and restart X as much as i like, it does not 
crash X.

Thanks to all of you who replied and especially to Chris for his time!

NilsOpenBSD 6.2-current (GENERIC.MP) #379: Sat Jan 20 14:30:55 MST 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8209772544 (7829MB)
avail mem = 7954006016 (7585MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0xed450 (18 entries)
bios0: vendor American Megatrends Inc. version "P1.40" date 07/14/2017
bios0: ASRock J3455-ITX
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP FPDT FIDT MCFG DBG2 DBGP HPET LPIT APIC NPKT PRAM WSMT 
SSDT SSDT AAFT SSDT SSDT SSDT SSDT SSDT UEFI WDAT NHLT
acpi0: wakeup devices SIO1(S3) UAR1(S4) HDAS(S3) XHC_(S4) XDCI(S4) BRCM(S0) 
PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) 
PXSX(S4) RP05(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpihpet0 at acpi0: 1920 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Celeron(R) CPU J3455 @ 1.50GHz, 1497.14 MHz
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,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,SENSOR,ARAT
cpu0: 1MB 64b/line 16-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 19MHz
cpu0: mwait min=64, max=64, C-substates=0.2.0.2.4.2.1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Celeron(R) CPU J3455 @ 1.50GHz, 1496.55 MHz
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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,SENSOR,ARAT
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 J3455 @ 1.50GHz, 1496.55 MHz
cpu2: