Re: CPU Affinity

[Elias M. Mariani]

Hi Anton,
The why is:
An increase in performance.
In this case I want to use some cores to do a very large operation and
it will be faster if the same core continues the same operation.
Maybe there's a library for doing so, or a way that I dont know in OpenBSD.
Now, this cases come not very often, and is debatible (probably
already debated in this proyect) that if that's the case you should
run a variation of the scheduler or use other OS.
And is true...
Now, in this moment I see a lot of activity around vmd/vmm, I have
been using it myself, is great, I love it, but my guess is that you
can get more performance on the guests OS if you set the affinity of
the process.
Maybe this is already done, or may will be... If that's the case
either you added functionality to the OS for supporting affinity or
you made vmm part of the OS, and there is the back question.
If you add vmm as part of the OS you are "extending" the system duty
to be a host, if you add affinity support you are doing the same...
Anyways, the proyect clearly knows itself and if there is no affinity
support is OK. Still loving OpenBSD.
The low punch would be discuss about "nice" support, but lets leave
that aside, I dont want a fight like in other post about philosophy
and low punches.

Now in MY PARTICULAR CASE, I usually do large math calculations, I've
been using other OSes but I love OpenBSD, so I ported my most used
tool, spyder (for writing python).
I love to test algorithms and things for a large time and things like
that. That is my taste, and is not an obligation for OpenBSD to
support affinity just because I want (Its obvious), but I see lots of
applications for "user level programs", for example vmm, pf, and
others components, I dont know if PF and VMM are "user level
programs", if they are you are already doing things that might be seen
as "not OS duty", if they are not, they would benefit probably of
affinity.

Just my opinion, again, dont do of this remarks something that it is not...
I just kindly ask about a funcionality, because I want to use my
favorite OS, made right, and test algorithms and look for big prime
numbers on it. If there is no funcionality, then, Its my problem...
Elias.

2018-04-29 23:15 GMT-03:00  :
> Sun, 29 Apr 2018 22:07:18 -0300 "Elias M. Mariani"
> 
>> Hi,
>> I was trying to port mprime to OpenBSD.
>> The main issue is not finding any way to set affinity on cores.
>> Searching for how to do this on OpenBSD bring this result in undeadly:
>> http://undeadly.org/cgi?action=article=20090324210236
>>
>> Is CPU Affinity dropped out of OpenBSD for some reason?
>>
>> Elias.
>>
>
> Hi Elias,
>
> Why do you want to do the operating system duty in user level programs?
>
> Kind regards,
> Anton Lazarov

Re: CPU Affinity

[lists]

Sun, 29 Apr 2018 22:07:18 -0300 "Elias M. Mariani"

> Hi,
> I was trying to port mprime to OpenBSD.
> The main issue is not finding any way to set affinity on cores.
> Searching for how to do this on OpenBSD bring this result in undeadly:
> http://undeadly.org/cgi?action=article=20090324210236
> 
> Is CPU Affinity dropped out of OpenBSD for some reason?
> 
> Elias.
> 

Hi Elias,

Why do you want to do the operating system duty in user level programs?

Kind regards,
Anton Lazarov

Re: Raid offline when newfs

[Nick Holland]

On 04/29/18 20:23, Mimoza wrote:
> 
> 
> Le 30/04/2018 à 00:01, Mimoza a écrit :
>> Hi,
>> I have a problem to create a second RAID 1 on my  router an Soekris 
>> 6501-70 (http://www.soekris.com/products/net6501-1.html)
> […]
>> I can rebuild the offline device but he still offline …
>> 
>> So, there any option or configuration to explain/solve that ? Something 
>> wrong with what i do ?
>> 
>> Maybe something bad with the expansion card ?
>> 
>> Thanks for any help.
>> 
> 
> Well, i respond to myself but i foud the guilty.
> My last question was the good way. I don't know why but the expansion 
> card do something wrong. I created the RAID system on another computer 
> and go back on router with the expansion card with the 2 HDD ready to 
> use and it's fine !
> 
> Sorry for the noise
> 

Did you disable the RAID functionality of this card?  If not, the BIOS
probably tried to "rebuild" one disk onto the other, causing you all
kinds of pain.  softraid has to do everything for this to work properly.

Nick.

CPU Affinity

[Elias M. Mariani]

Hi,
I was trying to port mprime to OpenBSD.
The main issue is not finding any way to set affinity on cores.
Searching for how to do this on OpenBSD bring this result in undeadly:
http://undeadly.org/cgi?action=article=20090324210236

Is CPU Affinity dropped out of OpenBSD for some reason?

Elias.

Re: Raid offline when newfs

[Mimoza]

Le 30/04/2018 à 00:01, Mimoza a écrit :

Hi,
I have a problem to create a second RAID 1 on my  router an Soekris 
6501-70 (http://www.soekris.com/products/net6501-1.html)

[…]

I can rebuild the offline device but he still offline …

So, there any option or configuration to explain/solve that ? Something 
wrong with what i do ?


Maybe something bad with the expansion card ?

Thanks for any help.



Well, i respond to myself but i foud the guilty.
My last question was the good way. I don't know why but the expansion 
card do something wrong. I created the RAID system on another computer 
and go back on router with the expansion card with the 2 HDD ready to 
use and it's fine !


Sorry for the noise

Raid offline when newfs

[Mimoza]

Hi,
I have a problem to create a second RAID 1 on my  router an Soekris 
6501-70 (http://www.soekris.com/products/net6501-1.html)


The first RAID 1 is on 2 m-sata SSD (sd0+sd1=sd4) and is fine.

The second is connected to a PCI-E to S-ATA expansion card 
(https://www.aliexpress.com/item/PCI-E-to-2-Port-SATA-III-3-0-RAID-Card-88SE9218-Chipset-for-Marvell-NCQ/32706555172.html) 
with 2 HDD of 2Tb (both are quite new, so no bad sector or anything 
else) (sd2+sd3=sd5).


I do the following commands

# dd if=/dev/zero of=/dev/sd2c bs=1m count=1
# dd if=/dev/zero of=/dev/sd3c bs=1m count=1
# fdisk -iy sd2
# fdisk -iy sd3
# disklabel -E sd2 # make an "a" partition of type RAID
# disklabel -E sd3 # make an "a" partition of type RAID
# bioctl -c 1 -l sd2a,sd3a softraid0
sd5 at scsibus4 targ 2 lun 0:  SCSI2 0/direct fixed
sd5: 1907726MB, 512 bytes/sector, 3907023473 sectors
# dd if=/dev/zero of=/dev/rsd5c bs=1m count=1
# fdisk -iy sd5
# disklabel -E sd5 # make an "d" partition

until here everything is OK. I can detach the device and/or reboot the 
router, the RAID still fine.


/root # bioctl softraid0
Volume  Status   Size Device
softraid0 0 Online31560135680 sd4 RAID1
  0 Online31560135680 0:0.0   noencl 
  1 Online31560135680 0:1.0   noencl 
softraid0 1 Online  2000396018176 sd5 RAID1
  0 Online  2000396018176 1:0.0   noencl 
  1 Online  2000396018176 1:1.0   noencl 

/root # disklabel sd5
# /dev/rsd5c:
type: SCSI
disk: SCSI disk
label: SR RAID 1
duid: e010d540c6ee0085
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 243200
total sectors: 3907023473
boundstart: 64
boundend: 3907008000
drivedata: 0

16 partitions:
#size   offset  fstype [fsize bsize   cpg]
  c:   39070234730  unused
  d:   3907007936   64  4.2BSD   8192 65536 1

But when i try to set a file system …

/root # newfs sd5d
/dev/rsd5d: 1907718.7MB in 3907007936 sectors of 512 bytes
584 cylinder groups of 3266.88MB, 52270 blocks, 104704 inodes each
super-block backups (for fsck -b #) at:
 256, […], 3900596736,

/root # bioctl softraid0
Volume  Status   Size Device
softraid0 0 Online31560135680 sd4 RAID1
  0 Online31560135680 0:0.0   noencl 
  1 Online31560135680 0:1.0   noencl 
softraid0 1 Degraded2000396018176 sd5 RAID1
  0 Offline 2000396018176 1:0.0   noencl 
  1 Online  2000396018176 1:1.0   noencl 

I can rebuild the offline device but he still offline …

So, there any option or configuration to explain/solve that ? Something 
wrong with what i do ?


Maybe something bad with the expansion card ?

Thanks for any help.

Re: Problem with OpenBSD as nfs client

[philipper01]

I had a cpy/paste mistake 

my exports file is :
 
> /home/filip/Documents 192.168.1.128 (rw)
> /home/filip/Public 192.168.1.128 (rw)

and the output of rpcinfo :
 
filip@openbsd:~$ rpcinfo -p 192.168.1.85
   program vers proto   port
104   tcp111  portmapper
103   tcp111  portmapper
102   tcp111  portmapper
104   udp111  portmapper
103   udp111  portmapper
102   udp111  portmapper
1000241   udp  51927  status
1000241   tcp  46983  status
151   udp  20048  mountd
151   tcp  20048  mountd
152   udp  20048  mountd
152   tcp  20048  mountd
153   udp  20048  mountd
153   tcp  20048  mountd
133   tcp   2049  nfs
134   tcp   2049  nfs
1002273   tcp   2049
1000211   udp  37969  nlockmgr
1000213   udp  37969  nlockmgr
1000214   udp  37969  nlockmgr
1000211   tcp  45991  nlockmgr
1000213   tcp  45991  nlockmgr
1000214   tcp  45991  nlockmgr




--
Sent from: http://openbsd-archive.7691.n7.nabble.com/openbsd-user-misc-f3.html

Re: Troubleshooting rl instability on OpenBSD 6.1

[Stuart Longland]

On 29/04/18 18:58, Stuart Henderson wrote:
> On 2018-04-29, Stuart Longland  wrote:
>> The rack has 5 servers, a ARM-based PC and the switch, all of which run
>> from a pair of 12V 105Ah AGM batteries, charged from mains power and
>> solar.  Switch is a Linksys LGS326-AU.  No other devices plugged into
>> this switch have connectivity issues.
>>
>> The port the industrial PC is connected to is a plain access port with
>> no VLAN tagging, trunking or other funny stuff (although all of the
>> above get used elsewhere in the network).
>>
>> When the link drops out, there's nothing in `dmesg`.  If I tether my
>> phone and hit the machine via SSH, I find it is unable to ping anything
>> on the internal network via IPv4 or IPv6, or vice versa.
> 
> What does "ifconfig rl0" show, both normally and when this happens?
> 
> How about "netstat -nI rl0"?

Not sure about netstat; but ifconfig rl0 isn't any different during and
outside of inaccessibility events.  Right now, I'm getting this:

> # ifconfig rl0
>   
> rl0: flags=8843 mtu 1500
> lladdr 00:d0:c9:e0:f4:75
> index 1 priority 0 llprio 3
> media: Ethernet autoselect (100baseTX full-duplex)
> status: active
> inet 172.31.249.254 netmask 0xff00 broadcast 172.31.249.255
> inet6 fe80::2d0:c9ff:fee0:f475%rl0 prefixlen 64 scopeid 0x1
> inet6 2001:44b8:21ac:70f9::fe prefixlen 64> # netstat -nI rl0
> NameMtu   Network Address  Ipkts IerrsOpkts Oerrs 
> Colls
> rl0 150000:d0:c9:e0:f4:75 13402102 0 16803928 0 > 0
> rl0 1500  172.31.249/ 172.31.249.25413402102 0 16803928 0 > 0
> rl0 1500  fe80::%rl0/ fe80::2d0:c9ff:fe 13402102 0 16803928 0 > 0
> rl0 1500  2001:44b8:2 2001:44b8:21ac:70 13402102 0 16803928 0 > 0

I'll try both commands again when I get problems.

> Is anything logged on the switch? This model has things like broadcast
> storm control, I'm wondering if that might have triggered or if it shows
> anything else useful.

I'll have a closer look, there were some messages about the link going
up and down, but it seems I missed turning the SNTP client on (settings
in two places) so the log timestamps are years off.  I've reset the logs
and will see how we go.

> Can you try a different cable, can you try a different switch port?

Unfortunately all ports are full.  I did replace the cable though.

>> Is there some sort of debugging flag I can turn on in the kernel to log
>> more detail about what's going on with rl0 when the loss of connectivity
>> is being experienced?
> 
> I don't see any extra debugging that can be enabled for rl.
> 

No problems, well, I'll keep an eye on the switch and see what it tells me.
-- 
Stuart Longland (aka Redhatter, VK4MSL)

I haven't lost my mind...
  ...it's backed up on a tape somewhere.

Re: Troubleshooting rl instability on OpenBSD 6.1

[Stuart Longland]

On 29/04/18 18:08, Solene Rapenne wrote:
> 
> Stuart Longland writes:
> 
>> Hi all,
>>
>> I've got an Advantech UNO-1150G industrial PC running OpenBSD 6.1 acting
>> as an ADSL router, public NTP server and DNS server.  dmesg info:
>>
>>> OpenBSD 6.1 (GENERIC) #291: Sat Apr  1 13:49:08 MDT 2017
> 
> OpenBSD 6.1 isn't supported anymore, please upgrade.
> 

Upgrade what?  The OS, the router?  If I'm 100% certain that moving to
6.2/6.3 will fix rl, then sure, but this answer is not helpful, as I've
been battling this problem for over a month.
-- 
Stuart Longland (aka Redhatter, VK4MSL)

I haven't lost my mind...
  ...it's backed up on a tape somewhere.

Re: Installboot uses wrong device for secondary boot loader

[Eric Zylstra]

I rebooted and checked each step again.  One big difference is this time on 
reboot, my installer USB drive was not sd0 as in my last install attempt.  My 
RAID1 devices now were sd0 and sd1.  After running through all the RAID prep 
steps, the install went without incident.

Thanks for your help,

EZ


> On Apr 29, 2018, at 8:58 AM, Eric Zylstra  > wrote:
> 
> Interesting.  I’ll look into that.  Not sure why installboot, upon seeing an 
> error condition (missing MBR), would not generate an error but instead try 
> another device.
> 
> EZ
> 
> 
>> On Apr 29, 2018, at 8:54 AM, Joel Sing > > wrote:
>> 
>> On Saturday 28 April 2018 22:21:08 Eric Zylstra wrote:
>>> I’m installing 6.3 on a RAID1.  Install was fine until ending with an error
>>> message, “invalid boot record signature…”.
>>> I manually ran installboot:
 . installboot -v -r /mnt sd4
>>> 
>>> Hand transcription:
>>> 
>>> Using /mnt as root
>>> Installing bootstrap on /dev/rsd4c
>>> Using first-stage /mnt/usr/mdec/biosboot, second-stage /mnt/usr/mdec/boot
>>> sd4:  softraid volume with 2 disk(s)
>>> sd4:  installing boot loader on softraid volume
>>> /mnt/usr/mdec/boot is 6 blocks x 16384 bytes
>>> sd0a:  installing boot blocks on /dev/rsd0c, part offset 144
>>> Master boot record (MBR) at sector 0
>>> Install boot:  invalid boot record signature (0x) @ sector 0
>>> 
>>> I did not typo the secondary boot block install.  It attempts to install on
>>> sd0 instead of sd4 as specified in my command.
>> 
>> In order to boot a softraid volume, the underlying disks have to be bootable 
>> with the first stage boot block being installed in the MBR (at least for 
>> i386/amd64). This is why it's looked at sd4, then gone to install the first 
>> stage boot block on sd0... however there is no MBR on this device to install 
>> it into. This suggests that you've not run fdisk correctly - but with 
>> insufficient details I can only guess.
> 

Re: vmm/vmd with Linux guest

[Carlos Cardenas]

On Sun, Apr 29, 2018 at 06:45:11AM -0400, mabi wrote:
> Hello,
> 
> I just read the OpenBSD vmm/vmd Update slides from Mike Larkin and have the 
> following 2 questions.
> 
> - it is mentioned that RHEL/CentOS is now supported and was wondering if Suse 
> is also already supported or if it is planned? I had a try at SLES 12 as a 
> guest on OpenBSD 6.3 but after the "Welcome to GRUB!" message on the console 
> it is stuck.
> 
> - when enabling "vmctl log verbose" where do the log entries go? I checked 
> /var/log/messages and daemon but did not see more verbose output while 
> starting a vm. Or what would I do if I want to investigate further why a VM 
> is stuck?
> 
> And by the way a big applause to those working on vmm/vmd for your great 
> effort!
> 
> Regards,
> Mabi
> 

Howdy.

Linux guest "support" is mainly accomplished by folks contributing code.
For example, the RHEL/CentOS piece was about those installers needing a
CD-ROM to boot, so that code was added. (Suse should work).

Two things to note when installing guests:
1) There is no VGA output and as such, the console must be specified at
boot to use serial output.  This would appear similarly to your
observation.

2) Sometimes the console can get "stuck" and seem unresponsive and on
the host you'll see the vm spin the cpu.  Simply detaching the console
(man cu(1)), waiting a bit, and re-attach resolves it.  However, if
you're able to run -current, I would advise that you do so since there
were considerable amount of improvements to vmm/vmd done at p2k18, where
among them was console responsiveness.

For your verbose logging, the messages should be present in
/var/log/daemon.  However, when I'm debugging vmd, I typically start it
on the command line ala `vmd -dvvv`.

+--+
Carlos

Re: OpenCVS: No LockDir? :)

[mazocomp]

On Sat, Apr 28, 2018 at 11:27:07PM +0300, mazoc...@disroot.org wrote:
> Hi!
> 
> opencvs server: ignoring unknown option 'LockDir'
> 
> It appears running anonymous OpenCVS server is awesome :D
> 
> Anyway, it works, but if I remove LockDir, anonymous GNU CVS
> stops working because it can't create LockDir :)
> 
> As far as I understand anonymous OpenCVS doesn't create
> lock directory and just gives me files I need, right?
> 
Ok, after reading OpenCVS's cvs.5 I see $CVSROOT/CVSROOT/config
supports only 3 options. Does OpenCVS need other options from
GNU CVS for $CVSROOT/CVSROOT/config or they should stay left out?

Re: Installboot uses wrong device for secondary boot loader

[Joel Sing]

On Saturday 28 April 2018 22:21:08 Eric Zylstra wrote:
> I’m installing 6.3 on a RAID1.  Install was fine until ending with an error
> message, “invalid boot record signature…”.
> I manually ran installboot:
> >. installboot -v -r /mnt sd4
> 
> Hand transcription:
> 
> Using /mnt as root
> Installing bootstrap on /dev/rsd4c
> Using first-stage /mnt/usr/mdec/biosboot, second-stage /mnt/usr/mdec/boot
> sd4:  softraid volume with 2 disk(s)
> sd4:  installing boot loader on softraid volume
> /mnt/usr/mdec/boot is 6 blocks x 16384 bytes
> sd0a:  installing boot blocks on /dev/rsd0c, part offset 144
> Master boot record (MBR) at sector 0
> Install boot:  invalid boot record signature (0x) @ sector 0
> 
> I did not typo the secondary boot block install.  It attempts to install on
> sd0 instead of sd4 as specified in my command.

In order to boot a softraid volume, the underlying disks have to be bootable 
with the first stage boot block being installed in the MBR (at least for 
i386/amd64). This is why it's looked at sd4, then gone to install the first 
stage boot block on sd0... however there is no MBR on this device to install 
it into. This suggests that you've not run fdisk correctly - but with 
insufficient details I can only guess.

Re: Installboot uses wrong device for secondary boot loader

[Eric Zylstra]

I’m following the documentation in OpenBSD FAQ:  disk setup.

I’m inclined to think there is a code issue since I specified device sd4 and 
installboot used that device for the first stage and then seems to have 
defaulted to sd0 for the second stage bootloader.

EZ


Sent from my iPhone

> On Apr 29, 2018, at 4:01 AM, Stuart Henderson  wrote:
> 
>> On 2018-04-29, Eric Zylstra  wrote:
>> I’m installing 6.3 on a RAID1.  Install was fine until ending with an error 
>> message, “invalid boot record signature…”.
>> 
>> I manually ran installboot:
>>> . installboot -v -r /mnt sd4
>> 
>> Hand transcription:
>> 
>> Using /mnt as root
>> Installing bootstrap on /dev/rsd4c
>> Using first-stage /mnt/usr/mdec/biosboot, second-stage /mnt/usr/mdec/boot
>> sd4:  softraid volume with 2 disk(s)
>> sd4:  installing boot loader on softraid volume
>> /mnt/usr/mdec/boot is 6 blocks x 16384 bytes
>> sd0a:  installing boot blocks on /dev/rsd0c, part offset 144
>> Master boot record (MBR) at sector 0
>> Install boot:  invalid boot record signature (0x) @ sector 0
>> 
>> I did not typo the secondary boot block install.  It attempts to install on 
>> sd0 instead of sd4 as specified in my command.
> 
> With softraid the bootblock is installed on all component disks of a raid1.
> 
> Since the installer doesn't directly support softraid...what did you type
> earlier to prepare this?
> 

Problem with OpenBSD as nfs client

[philipper01]

Hi,

First, im new with OpenBSD 6.3 that i run in Virtualbox.

I try to setup a NFS share :
server is Fedora workstation 28
 - exports file looks like this
/home/filip/Documents 192.168.1.1238 (rw)
/home/filip/Public 192.168.1.128 (rw)
Of course NFS is active on the server

client is Openbsd 6.3 and i have this message when i try to mount a share :

filip@openbsd:~$ sudo mount -t nfs 192.168.1.85:/home/filip/Documents
/mnt/nfs_Documents/
NFS Portmap: RPC: Program not registered

I will be happy to find a solution after long time on google without succes.
Thanks for help
Philippe.



--
Sent from: http://openbsd-archive.7691.n7.nabble.com/openbsd-user-misc-f3.html

Re: Problem with OpenBSD as nfs client

[Ken M]

Best guess the problem is selinux on the fedora side.

Try setting it to permissive and if that solves the problem.

If that does solve the problem you need to analyze what to change in 
selinux not just leave it at permissive. Sorry I forget the exact commands 
but they can be found with a quick google search.

Ken



> On Apr 29, 2018, at 8:48 AM, Eike Lantzsch  wrote:
> 
>> On Sunday, April 29, 2018 2:14:23 PM -04 philippe@laposte.net wrote:
>> Hi,
>> 
>> First, im new with OpenBSD 6.3 that i run in Virtualbox.
>> 
>> I try to setup a NFS share :
>> server is Fedora workstation 28
>> - exports file looks like this
>> /home/filip/Documents 192.168.1.1238 (rw)
>> /home/filip/Public 192.168.1.128 (rw)
>> Of course NFS is active on the server
>> 
>> client is Openbsd 6.3 and i have this message when i try to mount a share :
>> 
>> filip@openbsd:~$ sudo mount -t nfs 192.168.1.85:/home/filip/Documents
>> /mnt/nfs_Documents/ NFS Portmap: RPC: Program not registered
>> 
>> I will be happy to find a solution after long time on google without succes.
>> Thanks for help
>> Philippe.
> 
> Sorry Philippe, but I have no knowledge of Fedora but what does your OBSD on 
> Virtualbox say about:
> rpcinfo -p 192.168.1.85
> 
> Which version of nfs is running on Fedora and is the portmapper running?
> The following discussion might be of help:
> https://forums.fedoraforum.org/showthread.php?186999-NFS-mounting-problems-quot-RPC-Error-Program-not-registered-quot
> 
> I wish you success
> Eike
> -- 
> Eike Lantzsch ZP6CGE
> 
> You can’t have your π and eat it.
> 

Re: Problem with OpenBSD as nfs client

[Eike Lantzsch]

On Sunday, April 29, 2018 2:14:23 PM -04 philippe@laposte.net wrote:
> Hi,
> 
> First, im new with OpenBSD 6.3 that i run in Virtualbox.
> 
> I try to setup a NFS share :
> server is Fedora workstation 28
> - exports file looks like this
> /home/filip/Documents 192.168.1.1238 (rw)
> /home/filip/Public 192.168.1.128 (rw)
> Of course NFS is active on the server
> 
> client is Openbsd 6.3 and i have this message when i try to mount a share :
> 
> filip@openbsd:~$ sudo mount -t nfs 192.168.1.85:/home/filip/Documents
> /mnt/nfs_Documents/ NFS Portmap: RPC: Program not registered
> 
> I will be happy to find a solution after long time on google without succes.
> Thanks for help
> Philippe.

Sorry Philippe, but I have no knowledge of Fedora but what does your OBSD on 
Virtualbox say about:
rpcinfo -p 192.168.1.85

Which version of nfs is running on Fedora and is the portmapper running?
The following discussion might be of help:
https://forums.fedoraforum.org/showthread.php?186999-NFS-mounting-problems-quot-RPC-Error-Program-not-registered-quot

I wish you success
Eike
-- 
Eike Lantzsch ZP6CGE

You can’t have your π and eat it.

Re: Problem with OpenBSD as nfs client

[Solene Rapenne]

philippe@laposte.net writes:

> Hi, 
>
> First, im new with OpenBSD 6.3 that i run in Virtualbox. 
>
> I try to setup a NFS share : 
> server is Fedora workstation 28 
> - exports file looks like this 
> /home/filip/Documents 192.168.1.1238 (rw) 
> /home/filip/Public 192.168.1.128 (rw) 
> Of course NFS is active on the server 
>
> client is Openbsd 6.3 and i have this message when i try to mount a share : 
>
> filip@openbsd:~$ sudo mount -t nfs 192.168.1.85:/home/filip/Documents 
> /mnt/nfs_Documents/ 
> NFS Portmap: RPC: Program not registered 
>
> I will be happy to find a solution after long time on google without succes. 
> Thanks for help 
> Philippe. 

Something is wrong on your NFS server

Problem with OpenBSD as nfs client

[philippe . r01]

Hi, 

First, im new with OpenBSD 6.3 that i run in Virtualbox. 

I try to setup a NFS share : 
server is Fedora workstation 28 
- exports file looks like this 
/home/filip/Documents 192.168.1.1238 (rw) 
/home/filip/Public 192.168.1.128 (rw) 
Of course NFS is active on the server 

client is Openbsd 6.3 and i have this message when i try to mount a share : 

filip@openbsd:~$ sudo mount -t nfs 192.168.1.85:/home/filip/Documents 
/mnt/nfs_Documents/ 
NFS Portmap: RPC: Program not registered 

I will be happy to find a solution after long time on google without succes. 
Thanks for help 
Philippe. 

Re: /etc/netstart - order of operations (lo vs physical interfaces)

[Ingo Schwarze]

Hi,

this has been taken care of.  I just deleted the misleading sentences
from the lo(4) manual page.  No replacement is needed.

Thanks for reporting,
  Ingo


Hess THR wrote on Fri, Apr 27, 2018 at 07:23:49PM +0200:

> who is "jmc" in the header? can someone cc him?
> or the people who are doing the doc? :)
> 
> Many thanks. 
> 
> > Sent: Friday, April 27, 2018 at 3:28 PM
> > From: "Amelia A Lewis" 
> > To: misc@openbsd.org
> > Subject: Re: /etc/netstart - order of operations (lo vs physical interfaces)
> >
> > A read of the script itself shows loopback initialized prior to 
> > hardware interfaces, at least in 6.2 (haven't upgraded yet).
> > 
> > On Fri, 27 Apr 2018 08:21:54 -0400, Gabriel Guzman wrote:
> > > Just a quick clarification, lo(4) says that the loopback interface
> > > should be configured last, and /etc/netstart seems to support this
> > > but netstart(8) says that the loopback interface is configured `before`
> > > physical interfaces: 
> > 
> > Date in the man page for lo(4) is 2013. I'm guessing that the network 
> > system has moved on since then, and it's actually the lo(4) source 
> > that's out of date.
> > 
> > Or, possibly, the netstart authors aren't aware of the potential 
> > problems, so started initializing loopback devices first, and ought to 
> > change things.
> > 
> > :-)
> > 
> > Amy!
> > -- 
> > Amelia A. Lewisamyzing {at} talsever.com
> > There's someone in my head, but it's not me.
> > -- Pink Floyd

Re: OpenVPN and rdomains

[Zach Nedwich]

Thanks Kyle, that did the trick. I used the up script from 
http://openbsd-archive.7691.n7.nabble.com/ratble-and-rdomain-support-on-dhcpd-and-openvpn-tp300260p300262.html
 which pushed the correct default route. There seems to be an issue on boot 
with the VLAN pushing its own default route but I believe that's because it 
happens earlier than the OpenVPN connection. 

On 29 April 2018 3:13:28 pm AEST, Kyle  wrote:
>On Saturday, April 28, 2018 8:09:32 PM CDT z...@znedw.com wrote:
>> Hi all,
>> 
>> I'm trying to configure a TUN interface in a separate rdomain, so
>that my
>> default route is not via the VPN, and only a specific subnet will use
>> the TUN connection on the way out.
>> 
>> The OpenVPN connection is established ok via my default gateway on
>em1 (this
>> is my internet connection), however, once I add the TUN interface to
>> another rdomain, I'm unable to manually push the routes from the VPN
>server
>> in with route -TX add x.x.x.x x.x.x.x.
>> 
>> I'm unable to ping anything on the internet via route -TX exec.
>> With PF allowing all connections I am still unable to access the
>> internet on rdomain 2. I've uploaded config files at the link below.
>Any
>> assistance would be greatly appreciated.
>> 
>> https://gist.github.com/zachnedwich/208bcaac3bcdb15e2f5ab5737db8c2d2
>> 
>> Thank-you,
>> Zach Nedwich
>
>What does the routing table for rdomain 2 look like (route -T2 -n
>show)? Does 
>it have a default route? To set routes pushed from the server in that
>rdomain, 
>you might need to use up/down scripts on the client (commented lines at
>the 
>bottom of your pia.ovpn).
>
>I'm using a very similar config:
>
>$ cat /etc/hostname.tun0   
>
>up
>rdomain 1
>!/usr/local/sbin/openvpn --daemon --config /etc/openvpn/config.ovpn
>
>$ ifconfig tun0
>tun0: flags=8051 rdomain 1 mtu 1500
>index 13 priority 0 llprio 3
>groups: tun
>status: active
>inet 10.8.8.9 --> 10.8.8.1 netmask 0xff00
>
>$ route -T1 -n show
>Routing tables
>
>Internet:
>DestinationGatewayFlags   Refs  Use   Mtu  Prio
>Iface
>default10.8.8.1   UGS25293 27087073 - 8
>tun0 
>10.8.8.1   10.8.8.9   UHh11 - 8
>tun0 
>10.8.8.9   10.8.8.9   UHl047965 - 1
>tun0 
>127.0.0.1  127.0.0.1  UHl0  6462016 32768 1
>lo1  

PCI passthrough for VMM thoughts?

[Joseph Mayer]

Hi Mike,

First, thanks for vmm!

One practical question:

Did you think about PCI passthrough? If so, what's your perspective on
it?

There were no previous mentions of it on misc@ so here it is. Also I
have no idea what degree of complexity this is.

E.g., a VM guest can get exclusive control of a PCI device to lower PCI
device access latency (by cutting out the hypervisor/host OS as active
participant in the VM-PCI device interaction) or to enable the VM to
use a PCI device at all for the case that the host OS lacks support for
the device and hence can't virtualize it.

I guess PCI passthrough also could work as a robustness or security
measure where you have a VM drive a device so the host OS would be less
likely to crash and burn for any reason that pertains to touching
that device.

Thanks,
Joseph

vmm/vmd with Linux guest

[mabi]

Hello,

I just read the OpenBSD vmm/vmd Update slides from Mike Larkin and have the 
following 2 questions.

- it is mentioned that RHEL/CentOS is now supported and was wondering if Suse 
is also already supported or if it is planned? I had a try at SLES 12 as a 
guest on OpenBSD 6.3 but after the "Welcome to GRUB!" message on the console it 
is stuck.

- when enabling "vmctl log verbose" where do the log entries go? I checked 
/var/log/messages and daemon but did not see more verbose output while starting 
a vm. Or what would I do if I want to investigate further why a VM is stuck?

And by the way a big applause to those working on vmm/vmd for your great effort!

Regards,
Mabi

Re: Does dd have error checking and correction?

[Stuart Henderson]

On 2018-04-29, Z Ero  wrote:
> Forgive me if the is a naive question. Does the dd utility use
> something like a CRC to verify data integrity or is this managed at a
> lower level (eg. by the kernel services that dd uses to transfer
> data)?

Neither. Either read back and calculate a hash yourself (when reading
back you'll need to be careful about choosing a block size that fits a
whole number of times into the original) or some of the alternatives
to dd have built-in verification modes (e.g. dcfldd with
vf/verifylog/etc).

Re: Installboot uses wrong device for secondary boot loader

[Stuart Henderson]

On 2018-04-29, Eric Zylstra  wrote:
> I’m installing 6.3 on a RAID1.  Install was fine until ending with an error 
> message, “invalid boot record signature…”.
>
> I manually ran installboot:
>>. installboot -v -r /mnt sd4
>
> Hand transcription:
>
> Using /mnt as root
> Installing bootstrap on /dev/rsd4c
> Using first-stage /mnt/usr/mdec/biosboot, second-stage /mnt/usr/mdec/boot
> sd4:  softraid volume with 2 disk(s)
> sd4:  installing boot loader on softraid volume
> /mnt/usr/mdec/boot is 6 blocks x 16384 bytes
> sd0a:  installing boot blocks on /dev/rsd0c, part offset 144
> Master boot record (MBR) at sector 0
> Install boot:  invalid boot record signature (0x) @ sector 0
>
> I did not typo the secondary boot block install.  It attempts to install on 
> sd0 instead of sd4 as specified in my command.

With softraid the bootblock is installed on all component disks of a raid1.

Since the installer doesn't directly support softraid...what did you type
earlier to prepare this?

Re: Troubleshooting rl instability on OpenBSD 6.1

[Stuart Henderson]

On 2018-04-29, Stuart Longland  wrote:
> The rack has 5 servers, a ARM-based PC and the switch, all of which run
> from a pair of 12V 105Ah AGM batteries, charged from mains power and
> solar.  Switch is a Linksys LGS326-AU.  No other devices plugged into
> this switch have connectivity issues.
>
> The port the industrial PC is connected to is a plain access port with
> no VLAN tagging, trunking or other funny stuff (although all of the
> above get used elsewhere in the network).
>
> When the link drops out, there's nothing in `dmesg`.  If I tether my
> phone and hit the machine via SSH, I find it is unable to ping anything
> on the internal network via IPv4 or IPv6, or vice versa.

What does "ifconfig rl0" show, both normally and when this happens?

How about "netstat -nI rl0"?

Is anything logged on the switch? This model has things like broadcast
storm control, I'm wondering if that might have triggered or if it shows
anything else useful.

Can you try a different cable, can you try a different switch port?

> Is there some sort of debugging flag I can turn on in the kernel to log
> more detail about what's going on with rl0 when the loss of connectivity
> is being experienced?

I don't see any extra debugging that can be enabled for rl.

Re: Atheros ATH9485 in athn

[Stefan Sperling]

On Sat, Apr 28, 2018 at 09:11:38PM -0500, Z Ero wrote:
> Can any one give an idea as to the work required to get support for
> the ATH9485, found in the the AR5B225 and AR5B125 cards? I have a
> bunch of 225s and 125s that I would like to use with Openbsd but I see
> this chipset is not currently supported by the athn driver. I guess
> FreeBSD and Linux support it.
> 

Somebody would need to tweak the code in sys/dev/ic/ar9003.c until
your device works.

Re: Troubleshooting rl instability on OpenBSD 6.1

[Solene Rapenne]

Stuart Longland writes:

> Hi all,
>
> I've got an Advantech UNO-1150G industrial PC running OpenBSD 6.1 acting
> as an ADSL router, public NTP server and DNS server.  dmesg info:
>
>> OpenBSD 6.1 (GENERIC) #291: Sat Apr  1 13:49:08 MDT 2017

OpenBSD 6.1 isn't supported anymore, please upgrade.

Troubleshooting rl instability on OpenBSD 6.1

[Stuart Longland]

Hi all,

I've got an Advantech UNO-1150G industrial PC running OpenBSD 6.1 acting
as an ADSL router, public NTP server and DNS server.  dmesg info:

> OpenBSD 6.1 (GENERIC) #291: Sat Apr  1 13:49:08 MDT 2017
> dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
> cpu0: Geode(TM) Integrated Processor by AMD PCS ("AuthenticAMD" 586-class) 
> 499 MHz
> cpu0: FPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CFLUSH,MMX,MMXX,3DNOW2,3DNOW
> real mem  = 259272704 (247MB)
> avail mem = 241598464 (230MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: date 09/15/10, BIOS32 rev. 0 @ 0xfaa00, SMBIOS rev. 2.2 @ 
> 0xf (28 entries)
> bios0: vendor Phoenix Technologies, LTD version "6.00 PG" date 09/15/2010
> acpi at bios0 function 0x0 not configured
> apm0 at bios0: Power Management spec V1.2 (slowidle)
> pcibios0 at bios0: rev 2.1 @ 0xf/0xdfb4
> pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfded0/224 (12 entries)
> pcibios0: bad IRQ table checksum
> pcibios0: PCI BIOS has 12 Interrupt Routing table entries
> pcibios0: PCI Exclusive IRQs: 5 7 10 11
> pcibios0: no compatible PCI ICU found
> pcibios0: Warning, unable to fix up PCI interrupt routing
> pcibios0: PCI bus #0 is the last bus
> bios0: ROM list: 0xc/0x8000 0xc8000/0xa800 0xef000/0x1000!
> cpu0 at mainbus0: (uniprocessor)
> mtrr: K6-family MTRR support (2 registers)
> amdmsr0 at mainbus0
> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
> pchb0 at pci0 dev 1 function 0 "AMD Geode LX" rev 0x33
> vga1 at pci0 dev 1 function 1 "AMD Geode LX Video" rev 0x00
> wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
> wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
> glxsb0 at pci0 dev 1 function 2 "AMD Geode LX Crypto" rev 0x00: RNG AES
> unknown vendor 0x13fe product 0xa102 (class communications subclass 
> multi-port serial, rev 0x01) at pci0 dev 11 function 0 not configured
> unknown vendor 0x13fe product 0xf100 (class communications subclass 
> multi-port serial, rev 0x01) at pci0 dev 11 function 1 not configured
> rl0 at pci0 dev 12 function 0 "Realtek 8139" rev 0x10: irq 11, address 
> 00:d0:c9:e0:f4:75
> rlphy0 at rl0 phy 0: RTL internal PHY
> rl1 at pci0 dev 13 function 0 "Realtek 8139" rev 0x10: irq 10, address 
> 00:d0:c9:e0:f4:74
> rlphy1 at rl1 phy 0: RTL internal PHY
> glxpcib0 at pci0 dev 15 function 0 "AMD CS5536 ISA" rev 0x03: rev 3, 32-bit 
> 3579545Hz timer, watchdog, gpio, i2c
> gpio0 at glxpcib0: 32 pins
> iic0 at glxpcib0
> maxtmp0 at iic0 addr 0x4c: lm86
> pciide0 at pci0 dev 15 function 2 "AMD CS5536 IDE" rev 0x01: DMA, channel 0 
> wired to compatibility, channel 1 wired to compatibility
> wd0 at pciide0 channel 0 drive 0: 
> wd0: 1-sector PIO, LBA48, 7623MB, 15613920 sectors
> wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
> pciide0: channel 1 ignored (disabled)
> auglx0 at pci0 dev 15 function 3 "AMD CS5536 Audio" rev 0x01: irq 7, CS5536 
> AC97
> ac97: codec id 0x414c4760 (Avance Logic ALC655 rev 0)
> audio0 at auglx0
> ohci0 at pci0 dev 15 function 4 "AMD CS5536 USB" rev 0x02: irq 10, version 
> 1.0, legacy support
> ehci0 at pci0 dev 15 function 5 "AMD CS5536 USB" rev 0x02: irq 10
> usb0 at ehci0: USB revision 2.0
> uhub0 at usb0 configuration 1 interface 0 "AMD EHCI root hub" rev 2.00/1.00 
> addr 1
> isa0 at glxpcib0
> isadma0 at isa0
> com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
> com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
> pckbc0 at isa0 port 0x60/5 irq 1 irq 12
> pckbd0 at pckbc0 (kbd slot)
> wskbd0 at pckbd0: console keyboard, using wsdisplay0
> pcppi0 at isa0 port 0x61
> spkr0 at pcppi0
> wbsio0 at isa0 port 0x2e/2: W83627HF rev 0x41
> lm1 at wbsio0 port 0x290/8: W83627HF
> npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
> usb1 at ohci0: USB revision 1.0
> uhub1 at usb1 configuration 1 interface 0 "AMD OHCI root hub" rev 1.00/1.00 
> addr 1
> vscsi0 at root
> scsibus1 at vscsi0: 256 targets
> softraid0 at root
> scsibus2 at softraid0: 256 targets
> root on wd0a (0d087b092632bbb5.a) swap on wd0b dump on wd0b
> pppoe0: received unexpected PADO
> pppoe0: received unexpected PADO
> pppoe0: received unexpected PADO

For the most part, this machine runs fine, however intermittently, the
machine loses contact with the switch to which it's connected to.

The rack has 5 servers, a ARM-based PC and the switch, all of which run
from a pair of 12V 105Ah AGM batteries, charged from mains power and
solar.  Switch is a Linksys LGS326-AU.  No other devices plugged into
this switch have connectivity issues.

The port the industrial PC is connected to is a plain access port with
no VLAN tagging, trunking or other funny stuff (although all of the
above get used elsewhere in the network).

When the link drops out, there's nothing in `dmesg`.  If I tether my
phone and hit the machine via SSH, I find it is unable to ping anything
on the internal network via IPv4 or IPv6, or vice versa.

Very occasionally, I also get issues with the ADSL 

Re: OpenVPN and rdomains

[Kyle]

On Saturday, April 28, 2018 8:09:32 PM CDT z...@znedw.com wrote:
> Hi all,
> 
> I'm trying to configure a TUN interface in a separate rdomain, so that my
> default route is not via the VPN, and only a specific subnet will use
> the TUN connection on the way out.
> 
> The OpenVPN connection is established ok via my default gateway on em1 (this
> is my internet connection), however, once I add the TUN interface to
> another rdomain, I'm unable to manually push the routes from the VPN server
> in with route -TX add x.x.x.x x.x.x.x.
> 
> I'm unable to ping anything on the internet via route -TX exec.
> With PF allowing all connections I am still unable to access the
> internet on rdomain 2. I've uploaded config files at the link below. Any
> assistance would be greatly appreciated.
> 
> https://gist.github.com/zachnedwich/208bcaac3bcdb15e2f5ab5737db8c2d2
> 
> Thank-you,
> Zach Nedwich

What does the routing table for rdomain 2 look like (route -T2 -n show)? Does 
it have a default route? To set routes pushed from the server in that rdomain, 
you might need to use up/down scripts on the client (commented lines at the 
bottom of your pia.ovpn).

I'm using a very similar config:

$ cat /etc/hostname.tun0

up
rdomain 1
!/usr/local/sbin/openvpn --daemon --config /etc/openvpn/config.ovpn

$ ifconfig tun0
tun0: flags=8051 rdomain 1 mtu 1500
index 13 priority 0 llprio 3
groups: tun
status: active
inet 10.8.8.9 --> 10.8.8.1 netmask 0xff00

$ route -T1 -n show
Routing tables

Internet:
DestinationGatewayFlags   Refs  Use   Mtu  Prio Iface
default10.8.8.1   UGS25293 27087073 - 8 tun0 
10.8.8.1   10.8.8.9   UHh11 - 8 tun0 
10.8.8.9   10.8.8.9   UHl047965 - 1 tun0 
127.0.0.1  127.0.0.1  UHl0  6462016 32768 1 lo1  

Installboot uses wrong device for secondary boot loader

[Eric Zylstra]

I’m installing 6.3 on a RAID1.  Install was fine until ending with an error 
message, “invalid boot record signature…”.

I manually ran installboot:
>. installboot -v -r /mnt sd4

Hand transcription:

Using /mnt as root
Installing bootstrap on /dev/rsd4c
Using first-stage /mnt/usr/mdec/biosboot, second-stage /mnt/usr/mdec/boot
sd4:  softraid volume with 2 disk(s)
sd4:  installing boot loader on softraid volume
/mnt/usr/mdec/boot is 6 blocks x 16384 bytes
sd0a:  installing boot blocks on /dev/rsd0c, part offset 144
Master boot record (MBR) at sector 0
Install boot:  invalid boot record signature (0x) @ sector 0

I did not typo the secondary boot block install.  It attempts to install on sd0 
instead of sd4 as specified in my command.

Eric

Re: Plans to port the amdgpu(4) driver? (=to support Radeons made 2014/2015 and after.) Hardware/other donations needed?

[Joe Gidi]

> On Wed, Apr 25, 2018 at 10:49:53AM -0400, Joe Gidi wrote:
>>
>> > On Wed, Apr 25, 2018 at 09:08:12PM +1000, Jonathan Gray wrote:
>> >> drivers/gpu/drm/amd in linux has over 1.5 million lines of code.
>> Which
>> >> is multiple times larger than the complete OpenBSD kernel source...
>>
>> Thanks for this update!
>>
>> Just to clarify, before I spend a bunch of money on new hardware, should
>> I
>> be able to use a Radeon R7 250 to drive a 4k monitor via DisplayPort
>> with
>> this updated driver?
>>
>> Thanks again,
>
> It appears that 'R7 250' can mean either a cape verde or oland radeon
> depending on the model.  Both are GCN parts.
>
> 4k 30Hz should be possible with HDMI, 4k 60Hz on HDMI requires HDMI 2.0
> Both claim support for displayport 1.2 which should be able to do
> 4k 60Hz.  HDMI 2.0 seems to only be on later hardware with DCE >= 11
> carrizo (not carrizo-l which is mullins), polaris etc.
>
> With the low end radeons displayport is sometimes only available on
> oem models of cards sold as options for systems marketed as business
> desktops or workstations.
>
> And as mentioned earlier for acceleration you'll currently have to build
> a different version of Mesa than what OpenBSD releases/snapshots ship
> with.

Hi Jonathan,

Thanks for the detailed answer!

As best I can tell from wading through the mess of marketing names and
specifications, accelerated 4k video is currently not an option with
Radeon cards; the older cards don't support high-enough resolutions, and
the newer ones don't have acceleration support yet due to the Mesa
problem. Looks like I might need to buy an Intel machine or wait for the
Mesa issues to get resolved.

Thanks again,
Joe


-- 

Joe Gidi
j...@entropicblur.com

"You cannot buy skill." -- Ross Seyfried