Re: PERC 6/i existence of Virtual Drives hangs boot

[Base Pr1me]

Thanks for the input! I greatly appreciate your time.

However, in a last ditch effort -- as you were typing and sending your
email --, I solved the problem. I was completely barking up the wrong tree
... sigh.

The issue was an old BIOS in the server. Once I updated the server BIOS,
the softraid hang went away!

You've given me fun things to look in to in the future, however! The more
you know, right?

Regards,
Tracey

On Tue, Apr 24, 2018 at 4:24 PM, IL Ka  wrote:

> >>  Or, is there a gdb method of booting the kernel?
>
> Short answer:
> http://openbsd-archive.7691.n7.nabble.com/on-line-kernel-
> debugging-td335833.html
>
> Long answer:
> /dev/kmem (kmem(4)) could be used to access kernel memory.
> gdb has special target (kvm) that uses it to debug bsd kernels   (
> https://sourceware.org/gdb//onlinedocs/gdb/BSD-libkvm-Interface.html)
>
> so, we need 2 things here:
> 1) Access to /dev/kmem is disabled by default (due to securelevel(7)).
> We need to enable it with "kern.allowkmem=1" in /etc/sysctl.conf
> Or we can switch to insecure level (echo "sysctl kernl.securelevel=-1 >
> /etc/rc.securelevel")
> Make sure to reboot before it.
>
> Never set these values for production system!!
>
> 2) Kernel with debug symbols
> You can build your kernel (man config).
> As last step in "compile" folder you will have /bsd (stripped) and
> /bsd.gdb (symbolized)
>
> Then, copy /bsd.gdb to root, reboot and boot it:
> boot> boot hd0a:/bsd.gdb
>
> I think we should have article about it in FAQ:)
>
>

Re: PERC 6/i existence of Virtual Drives hangs boot

[IL Ka]

>>  Or, is there a gdb method of booting the kernel?

Short answer:
http://openbsd-archive.7691.n7.nabble.com/on-line-kernel-debugging-td335833.html

Long answer:
/dev/kmem (kmem(4)) could be used to access kernel memory.
gdb has special target (kvm) that uses it to debug bsd kernels   (
https://sourceware.org/gdb//onlinedocs/gdb/BSD-libkvm-Interface.html)

so, we need 2 things here:
1) Access to /dev/kmem is disabled by default (due to securelevel(7)).
We need to enable it with "kern.allowkmem=1" in /etc/sysctl.conf
Or we can switch to insecure level (echo "sysctl kernl.securelevel=-1 >
/etc/rc.securelevel")
Make sure to reboot before it.

Never set these values for production system!!

2) Kernel with debug symbols
You can build your kernel (man config).
As last step in "compile" folder you will have /bsd (stripped) and /bsd.gdb
(symbolized)

Then, copy /bsd.gdb to root, reboot and boot it:
boot> boot hd0a:/bsd.gdb

I think we should have article about it in FAQ:)

Re: Beg for Atheros wifi driver

[Manuel Solis]

Hello Misc,

Just to close this topic,

I have just received my new usb wifi adapter, the one that Mr. Pettijohn
recommended (i orderer 4 of them just in case) and it works.

Thank you again for your kind support.

https://www.amazon.com/Edimax-EW-7811Un-150Mbps-Raspberry-Su
pports/dp/B003MTTJOY




2018-04-17 13:25 GMT-05:00 Carlos Cardenas :

> On Tue, Apr 17, 2018 at 11:11:30AM -0500, Manuel Solis wrote:
> > done :D
>
> It's an ath10k NIC.  There is no support for this NIC in tree.
>
> +--+
> Carlos
>
> >
> > Domain /dev/pci0:
> >  0:0:0: AMD AMD64 15h Root Complex
> >   0x: Vendor ID: 1022 Product ID: 1576
> >   0x0004: Command: 0004 Status: 
> >   0x0008: Class: 06 Subclass: 00 Interface: 00 Revision: 00
> >   0x000c: BIST: 00 Header Type: 80 Latency Timer: 00 Cache Line
> Size: 00
> >   0x0010: BAR empty ()
> >   0x0014: BAR empty ()
> >   0x0018: BAR empty ()
> >   0x001c: BAR empty ()
> >   0x0020: BAR empty ()
> >   0x0024: BAR empty ()
> >   0x0028: Cardbus CIS: 
> >   0x002c: Subsystem Vendor ID: 1025 Product ID: 1213
> >   0x0030: Expansion ROM Base Address: 
> >   0x0038: 
> >   0x003c: Interrupt Pin: 00 Line: 00 Min Gnt: 00 Max Lat: 00
> >  0:1:0: ATI Carrizo
> >   0x: Vendor ID: 1002 Product ID: 9874
> >   0x0004: Command: 0007 Status: 0010
> >   0x0008: Class: 03 Subclass: 00 Interface: 00 Revision: cc
> >   0x000c: BIST: 00 Header Type: 80 Latency Timer: 00 Cache Line
> Size: 10
> >   0x0010: BAR mem prefetchable 64bit addr:
> 0xe000/0x1000
> >   0x0018: BAR mem prefetchable 64bit addr:
> 0xd080/0x0080
> >   0x0020: BAR io addr: 0x4000/0x0100
> >   0x0024: BAR mem 32bit addr: 0xd160/0x0004
> >   0x0028: Cardbus CIS: 
> >   0x002c: Subsystem Vendor ID: 1025 Product ID: 1213
> >   0x0030: Expansion ROM Base Address: fffe
> >   0x0038: 
> >   0x003c: Interrupt Pin: 01 Line: 03 Min Gnt: 00 Max Lat: 00
> >   0x0048: Capability 0x09: Vendor Specific
> >   0x0050: Capability 0x01: Power Management
> >   State: D0
> >   0x0058: Capability 0x10: PCI Express
> >   0x0100: Enhanced Capability 0x0b: Vendor-Specific
> >   0x0270: Enhanced Capability 0x19: Secondary PCIe Capability
> >   0x02b0: Enhanced Capability 0x0f: Address Translation Services
> >   0x02c0: Enhanced Capability 0x13: Page Request Interface
> >   0x02d0: Enhanced Capability 0x1b: Process Address Space ID
> >   0x00a0: Capability 0x05: Message Signalled Interrupts (MSI)
> >  0:1:1: ATI Radeon HD Audio
> >   0x: Vendor ID: 1002 Product ID: 9840
> >   0x0004: Command: 0007 Status: 0010
> >   0x0008: Class: 04 Subclass: 03 Interface: 00 Revision: 00
> >   0x000c: BIST: 00 Header Type: 80 Latency Timer: 00 Cache Line
> Size: 10
> >   0x0010: BAR mem 64bit addr: 0xd166/0x4000
> >   0x0018: BAR empty ()
> >   0x001c: BAR empty ()
> >   0x0020: BAR empty ()
> >   0x0024: BAR empty ()
> >   0x0028: Cardbus CIS: 
> >   0x002c: Subsystem Vendor ID: 1025 Product ID: 1213
> >   0x0030: Expansion ROM Base Address: 
> >   0x0038: 
> >   0x003c: Interrupt Pin: 02 Line: 04 Min Gnt: 00 Max Lat: 00
> >   0x0048: Capability 0x09: Vendor Specific
> >   0x0050: Capability 0x01: Power Management
> >   State: D0
> >   0x0058: Capability 0x10: PCI Express
> >   0x0100: Enhanced Capability 0x0b: Vendor-Specific
> >   0x00a0: Capability 0x05: Message Signalled Interrupts (MSI)
> >  0:2:0: AMD AMD64 15h Host
> >   0x: Vendor ID: 1022 Product ID: 157b
> >   0x0004: Command:  Status: 
> >   0x0008: Class: 06 Subclass: 00 Interface: 00 Revision: 00
> >   0x000c: BIST: 00 Header Type: 80 Latency Timer: 00 Cache Line
> Size: 00
> >   0x0010: BAR empty ()
> >   0x0014: BAR empty ()
> >   0x0018: BAR empty ()
> >   0x001c: BAR empty ()
> >   0x0020: BAR empty ()
> >   0x0024: BAR empty ()
> >   0x0028: Cardbus CIS: 
> >   0x002c: Subsystem Vendor ID:  Product ID: 
> >   0x0030: Expansion ROM Base Address: 
> >   0x0038: 
> >   0x003c: Interrupt Pin: 00 Line: 00 Min Gnt: 00 Max Lat: 00
> >  0:2:2: AMD AMD64 15h PCIE
> >   0x: Vendor ID: 1022 Product ID: 157c
> >   0x0004: Command: 0007 Status: 0010
> >   0x0008: Class: 06 Subclass: 04 Interface: 00 Revision: 00
> >   0x000c: BIST: 00 Header Type: 81 Latency Timer: 00 Cache Line
> Size: 10
> >   0x0010: 
> >   0x0014: 
> >   0x0018: Primary Bus: 0 Secondary Bus: 1 Subordinate Bus: 1
> >   Secondary Latency Timer: 00
> >   

Re: PERC 6/i existence of Virtual Drives hangs boot

[Base Pr1me]

Well I was able to get SR_DEBUG working with the attached diff.

I have tracked the hang down to the open device call on line 1038 `error =
VOP_OPEN(vn, FREAD, NOCRED, curproc);` in the sr_meta_native_bootprobe
function of /usr/src/sys/dev/softraid.c.

Now that I'm completely out of my depth, can anyone suggest a method for
getting the kernel to panic to ddb to get a trace or something, instead of
just freezing? Or, is there a gdb method of booting the kernel?

I'm running of trails to follow.

Thanks for any suggestions.

On Fri, Apr 20, 2018 at 2:37 PM, Base Pr1me  wrote:

> Sorry, I put the hang position in the wrong place on the first email:
>
> scsibus6 at vscsi0: 256 targets <--- not here! sorry
> softraid0 at root
> scsibus7 at softraid0: 256 targets <- here is where the system hangs
> when virtual drives are present
>
> On Fri, Apr 20, 2018 at 2:33 PM, Base Pr1me  wrote:
>
>> Hello all,
>>
>> I'm having virtual drive problems on a Dell 2900. When no virtual drives
>> are set up in the PERC 6/i controller, the server will not hang. However,
>> when there are virtual drives available on the system, it appears the
>> system is hanging at the probe stage -- I'm just guessing that's what is
>> occurring. The hang occurs on a fully installed kernel and ramdisk kernels.
>> I have a full install on a SATA drive for the testing, currently.
>>
>> I've tried booting with the single processor kernel and even the i386
>> ramdisk kernel. To complete boot, I'm disabling the mfi driver so the PERC
>> 6/i is not configured, or alternatively removing configured virtual drives.
>>
>> I've tried different virtual drive configurations to see if that's the
>> issue, all the way down to a single hdd configured as RAID-0. It hangs
>> regardless of configuration. The hang position in dmesg would be "scsibus7
>> at softraid0: 256 targets" -- see below. That is the last message displayed
>> on the console.
>>
>> I compiled and tried a couple of different kernels with SCSIDEBUG and
>> various SCSIDEBUG options to see if it would report anything before the
>> hang, with no luck. I also tried to see if mfi or softraid would report
>> anything, but I must be missing a compile option to get these working,
>> because the compiler had errors with these options set:
>>
>> option MFI_DEBUG - wanted to see if mfi reported anything
>> option SR_DEBUG - wanted to see of softraid reported anything
>>
>> It's also VERY possible I have the wrong SCSIDEBUG options set. The two I
>> tried were:
>>
>> # i don't understand these options well enough
>> option SCSIDEBUG
>> option SCSIDEBUG_LEVEL=0x0080
>> option SCSIDEBUG_BUSES=0x8
>> option SCSIDEBUG_TARGETS=0x1
>> option SCSIDEBUG_LUN=0x1
>>
>> # hell, let's go for it
>> option SCSIDEBUG
>> option SCSIDEBUG_LEVEL=0x0080
>> option SCSIDEBUG_BUSES=0xff
>> option SCSIDEBUG_TARGETS=0xff
>> option SCSIDEBUG_LUN=0xff
>>
>> I didn't see any differences.
>>
>> Does anyone have any suggestions on further troubleshooting and/or better
>> SCSIDEBUG options? Am I digging in the wrong area? I appreciate any
>> thoughts or suggestions. I'm attaching 3 dmesg's. The first has mfi enabled
>> and no virtual drives configured, the second has mfi disabled, and the
>> third has SCSIDEBUG enabled with mfi disabled, to capture the dmesg.
>>
>> Thanks,
>>
>> Tracey
>>
>> No virtual drives
>> 
>> OpenBSD 6.3 (GENERIC.MP) #107: Sat Mar 24 14:21:59 MDT 2018
>> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
>> real mem = 12863209472 (12267MB)
>> avail mem = 12466286592 (11888MB)
>> mpath0 at root
>> scsibus0 at mpath0: 256 targets
>> mainbus0 at root
>> bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xcfb9c000 (64 entries)
>> bios0: vendor Dell Inc. version "2.0.1" date 10/27/2007
>> bios0: Dell Inc. PowerEdge 2900
>> acpi0 at bios0: rev 2
>> acpi0: sleep states S0 S4 S5
>> acpi0: tables DSDT FACP APIC SPCR HPET MCFG WD__ SLIC ERST HEST BERT EINJ
>> TCPA
>> acpi0: wakeup devices PCI0(S5)
>> 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) Xeon(R) CPU E5410 @ 2.33GHz, 2327.86 MHz
>> cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMO
>> V,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,
>> SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,
>> DCA,SSE4.1,NXE,LONG,LAHF,PERF,SENSOR,MELTDOWN
>> cpu0: 6MB 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 332MHz
>> cpu0: mwait min=64, max=64, C-substates=0.2.2.2, IBE
>> cpu1 at mainbus0: apid 1 (application processor)
>> cpu1: Intel(R) Xeon(R) CPU E5410 @ 2.33GHz, 2327.51 MHz
>> cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMO
>> V,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,
>> 

Re: Wake-on-LAN from suspended state

[Daniel Melameth]

On Tue, Apr 24, 2018 at 2:11 PM, Paul de Weerd  wrote:
> I've been playing with WoL recently and found that my desktop machine
> (a Dell Optiplex 9020) can be woken up from another OpenBSD machine on
> the same network with `doas arp -W ${MAC} em1` (where ${MAC} is the
> mac address of my desktop machine).  As I'm using softraid full disk
> encryption, this doesn't help too much - I still need to be present to
> unlock the crypto volume manually.
>
> Figured I try waking the machine up from sleep mode.  This machine
> suspends fine with zzz, and also wakes perfectly from sleep by pushing
> the power button (included dmesg contains one suspend / resume cycle).
> However, in suspended state, I can't wake up the machine with the
> magic packet.
>
> Reading up on the topic of WoL shows a field full of rabbit holes.
> Does anyone know if it is possible at all to do this with OpenBSD?
> I'm guessing the NIC should be left in a state that allows it to wake
> the rest of the machine when entering suspend - perhaps that's not
> done on purpose because it's not wanted.  Can anyone shed some light
> on this matter?

If I understand you correctly, have you tried enabling WoL via ifconfig?

Wake-on-LAN from suspended state

[Paul de Weerd]

Hi all,

I've been playing with WoL recently and found that my desktop machine
(a Dell Optiplex 9020) can be woken up from another OpenBSD machine on
the same network with `doas arp -W ${MAC} em1` (where ${MAC} is the
mac address of my desktop machine).  As I'm using softraid full disk
encryption, this doesn't help too much - I still need to be present to
unlock the crypto volume manually.

Figured I try waking the machine up from sleep mode.  This machine
suspends fine with zzz, and also wakes perfectly from sleep by pushing
the power button (included dmesg contains one suspend / resume cycle).
However, in suspended state, I can't wake up the machine with the
magic packet.

Reading up on the topic of WoL shows a field full of rabbit holes.
Does anyone know if it is possible at all to do this with OpenBSD?
I'm guessing the NIC should be left in a state that allows it to wake
the rest of the machine when entering suspend - perhaps that's not
done on purpose because it's not wanted.  Can anyone shed some light
on this matter?

Thanks,

Paul 'WEiRD' de Weerd

OpenBSD 6.3-current (GENERIC.MP) #8: Sun Apr 22 00:40:30 MDT 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 34243903488 (32657MB)
avail mem = 33198944256 (31660MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xec410 (88 entries)
bios0: vendor Dell Inc. version "A21" date 12/27/2017
bios0: Dell Inc. OptiPlex 9020
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT SLIC LPIT SSDT SSDT SSDT HPET SSDT MCFG SSDT 
ASF! DMAR
acpi0: wakeup devices UAR1(S3) PXSX(S4) RP01(S4) PXSX(S4) PXSX(S4) PXSX(S4) 
RP05(S4) PXSX(S4) PXSX(S4) PXSX(S4) GLAN(S4) EHC1(S3) EHC2(S3) XHC_(S4) 
HDEF(S4) PEG0(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) Core(TM) i7-4770 CPU @ 3.40GHz, 3691.98 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,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
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 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz, 3691.46 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,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz, 3691.46 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,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6 (application processor)
cpu3: Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz, 3691.46 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,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 0, core 3, package 0
cpu4 at mainbus0: apid 1 (application processor)
cpu4: Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz, 3691.46 MHz
cpu4: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu4: 256KB 64b/line 8-way L2 cache
cpu4: smt 1, core 0, package 0
cpu5 at mainbus0: apid 3 (application processor)
cpu5: Intel(R) Core(TM) 

Re: Audio stuttering on media playback with sndiod

[Alexandre Ratchov]

On Sat, Apr 14, 2018 at 11:55:23AM +0200, Alexandre Ratchov wrote:
> On Tue, Apr 10, 2018 at 03:20:33PM +0200, Robert Klein wrote:
> > Hi Daniel,
> > 
> > On Wed, 4 Apr 2018 03:22:04 -0300
> > Daniel Bolgheroni  wrote:
> > 
> > > Hi,
> > > 
> > > audio is stuttering on media playback when run through sndiod. It's OK
> > > without it.
> > 
> > Maybe related.  Yesterday I disabled webcam and microphone in BIOS on
> > my X250.  Then Video playback (audio and video) was stuttering. I
> > didn't investigate further, as: reverting BIOS settings made it Ok
> > again.
> 
> Thanks. Few notes for the mailing-list archives:
> 
> Certains laptops have a "disable microphone" knob in the BIOS which
> makes the device operate play-only, but it still reports full-duplex
> capability. This confuses any full-duplex program, including sndiod,
> and makes sound stutter. I've found no way to detect this situation.
> 
> Until we manage to properly detect it in the azalia driver, I'd
> suggest not using the BIOS knob (ie keep your microphone enabled). To
> disable it, run as root:
> 
>   chmod 600 /dev/audio[0-9]

As noted by florian@, the proper mode is 0622 (write-only, i.e.
play-only). thanks.

OpenBSD 6.3 mount_smbfs missing ?!

[Daniel Santos]

Hello,

I could not find mount_smbfs in the base OS anymore, no packages like 
it?


What is currently the recommended samba share mount tool for OpenBSD?

I have tried usmb, it works but slow:

time dd bs=1M count=1000 if=/dev/zero of=/mnt/smb/big
1000+0 records in
1000+0 records out
1048576000 bytes transferred in 56.149 secs (18674606 bytes/sec)

real0m56.405s
user0m0.010s
sys 0m4.810s

While direct disk write on the samba server which is Debian Wheezy:

time dd if=/dev/zero of=big2 bs=1M count=1000
1000+0 records in
1000+0 records out
1048576000 bytes (1.0 GB) copied, 1.07052 s, 980 MB/s

real0m1.073s
user0m0.000s
sys 0m1.068s

Takes like 1 second, I have repeated the test couple of times and come 
up with the same numbers that it is almost 60x times slower to write out 
a file through samba.

Re: Errors with Php and curl under OpenBSD 6.3

[Mario Theodoridis]

On 04/24/2018 08:23 AM, C. L. Martinez wrote:

Hi all,

   Since this morning my OpenBSD 6.3 host (with tt-rss installed) returns
the following error when I try to add some feeds:

Couldn't download the specified URL: ; 77 error setting certificate verify
locations: CAfile: /etc/ssl/cert.pem CApath: none

  It seems some type of problem with curl ... Am I right? I found some
solutions but all of them involves to make use of an insecure connection
with curl.


It's complaining about your certificate authority file being corrupt or 
missing. This is actually an SSL issue.


/etc/ssl/cert.pem should be there and look something like:

# $OpenBSD: cert.pem,v 1.15 2017/02/24 10:42:00 sthen Exp $

### AddTrust AB

=== /C=SE/O=AddTrust AB/OU=AddTrust External TTP Network/CN=AddTrust External 
CA Root
Certificate:
Data:
Version: 3 (0x2)
Serial Number: 1 (0x1)
Signature Algorithm: sha1WithRSAEncryption
Validity
Not Before: May 30 10:48:38 2000 GMT
Not After : May 30 10:48:38 2020 GMT
Subject: C=SE, O=AddTrust AB, OU=AddTrust External TTP Network, 
CN=AddTrust External CA Root
X509v3 extensions:
X509v3 Subject Key Identifier:
AD:BD:98:7A:34:B4:26:F7:FA:C4:26:54:EF:03:BD:E0:24:CB:54:1A
X509v3 Key Usage:
Certificate Sign, CRL Sign
X509v3 Basic Constraints: critical
CA:TRUE
X509v3 Authority Key Identifier:

keyid:AD:BD:98:7A:34:B4:26:F7:FA:C4:26:54:EF:03:BD:E0:24:CB:54:1A
DirName:/C=SE/O=AddTrust AB/OU=AddTrust External TTP 
Network/CN=AddTrust External CA Root
serial:01

SHA1 Fingerprint=02:FA:F3:E2:91:43:54:68:60:78:57:69:4D:F5:E4:5B:68:85:18:68
SHA256 
Fingerprint=68:7F:A4:51:38:22:78:FF:F0:C8:B1:1F:8D:43:D5:76:67:1C:6E:B2:BC:EA:B4:13:FB:83:D9:65:D0:6D:2F:F2
-BEGIN CERTIFICATE-
MIIENjCCAx6gAwIBAgIBATANBgkqhkiG9w0BAQUFADBvMQswCQYDVQQGEwJTRTEU
MBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAkBgNVBAsTHUFkZFRydXN0IEV4dGVybmFs
IFRUUCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVzdCBFeHRlcm5hbCBDQSBSb290
...[snip]

--
Mit freundlichen Grüßen/Kind regards

Mario Theodoridis

Re: Errors with Php and curl under OpenBSD 6.3

[C. L. Martinez]

Works!! ... Many thanks Manolis.

On Tue, Apr 24, 2018 at 9:10 AM, Manolis Tzanidakis 
wrote:

> Oops, forgot a sub-directory. Try this, instead:
>
> # mkdir -p /var/www/etc/ssl; cp /etc/ssl/cert.pem /var/www/etc/ssl
>
> On Tue (24/04/18), Manolis Tzanidakis wrote:
> > Hello,
> > try copying cert.pem to the www chroot:
> >
> > # mkdir -p /var/www/etc; cp /etc/ssl/cert.pem /var/www/etc/ssl
> >
> > and restart php-fpm.
> >
> > On Tue (24/04/18), C. L. Martinez wrote:
> > > Hi all,
> > >
> > >   Since this morning my OpenBSD 6.3 host (with tt-rss installed)
> returns
> > > the following error when I try to add some feeds:
> > >
> > > Couldn't download the specified URL: ; 77 error setting certificate
> verify
> > > locations: CAfile: /etc/ssl/cert.pem CApath: none
> > >
> > >  It seems some type of problem with curl ... Am I right? I found some
> > > solutions but all of them involves to make use of an insecure
> connection
> > > with curl.
> > >
> > >  Any idea?
> > >
> > > Thanks.
>
>

Re: Errors with Php and curl under OpenBSD 6.3

[Manolis Tzanidakis]

Oops, forgot a sub-directory. Try this, instead:

# mkdir -p /var/www/etc/ssl; cp /etc/ssl/cert.pem /var/www/etc/ssl

On Tue (24/04/18), Manolis Tzanidakis wrote:
> Hello,
> try copying cert.pem to the www chroot:
> 
> # mkdir -p /var/www/etc; cp /etc/ssl/cert.pem /var/www/etc/ssl
> 
> and restart php-fpm.
> 
> On Tue (24/04/18), C. L. Martinez wrote:
> > Hi all,
> > 
> >   Since this morning my OpenBSD 6.3 host (with tt-rss installed) returns
> > the following error when I try to add some feeds:
> > 
> > Couldn't download the specified URL: ; 77 error setting certificate verify
> > locations: CAfile: /etc/ssl/cert.pem CApath: none
> > 
> >  It seems some type of problem with curl ... Am I right? I found some
> > solutions but all of them involves to make use of an insecure connection
> > with curl.
> > 
> >  Any idea?
> > 
> > Thanks.

Re: Errors with Php and curl under OpenBSD 6.3

[Manolis Tzanidakis]

Hello,
try copying cert.pem to the www chroot:

# mkdir -p /var/www/etc; cp /etc/ssl/cert.pem /var/www/etc/ssl

and restart php-fpm.

On Tue (24/04/18), C. L. Martinez wrote:
> Hi all,
> 
>   Since this morning my OpenBSD 6.3 host (with tt-rss installed) returns
> the following error when I try to add some feeds:
> 
> Couldn't download the specified URL: ; 77 error setting certificate verify
> locations: CAfile: /etc/ssl/cert.pem CApath: none
> 
>  It seems some type of problem with curl ... Am I right? I found some
> solutions but all of them involves to make use of an insecure connection
> with curl.
> 
>  Any idea?
> 
> Thanks.

Errors with Php and curl under OpenBSD 6.3

[C. L. Martinez]

Hi all,

  Since this morning my OpenBSD 6.3 host (with tt-rss installed) returns
the following error when I try to add some feeds:

Couldn't download the specified URL: ; 77 error setting certificate verify
locations: CAfile: /etc/ssl/cert.pem CApath: none

 It seems some type of problem with curl ... Am I right? I found some
solutions but all of them involves to make use of an insecure connection
with curl.

 Any idea?

Thanks.