Re: NFS server down, again, and again, and again...

> Do you mean nfsd server dies? I mean the NFS service as delivered by nfsd, portmap and mountd. > Does it provide core dump? No! > You do not need to restart it manually: just create script that checks for server existence (like ``/etc/rc.d/nfsd check``) and run it if it is dead. I usually

Re: NFS server down, again, and again, and again...

You could use ktrace(1) to trace all calls and then use kdump(1) to read them, and may help you to find what cause it to die, but it may be tricky for anyone except nfsd developer.. You can also try to find person who supports it by looking at last commits to:

Re: IKEv2 vpn between OpenBSD 6.2 and Cisco ASA 5510 using PSK

I'll answer my own post. I've come to the conclusion that the OpenBSD IKEv2 implementation in iked is incompatible with Cisco. It works between OpenBSD boxes but none of the several Cisco ASA devices I've tried with did I get it to work. Switching to IKEv1, i.e. ISAKMPd, works immediately. /

Re: NFS server down, again, and again, and again...

Do you mean nfsd server dies? Does it provide core dump? You do not need to restart it manually: just create script that checks for server existence (like ``/etc/rc.d/nfsd check``) and run it if it is dead. On Wed, Apr 18, 2018 at 12:00 AM, Rupert Gallagher wrote: > The

NFS server down, again, and again, and again...

The crash usually occurs in the morning, when the 'windows 10 pro' clients are powered up. The obsd nfs server must be restarted manually, and the clients are happy again. No error messages, clear logs, and yet it crashes. A mistery.

Re: Capturing ddb output when "boot reboot" fails

On 2018-04-17, Rodney Polkinghorne wrote: > Dear list > > My old Dell laptop ran stably under 6.1. After I upgraded to 6.2, > the kernel started to crash with "page fault trap, code=0" every > time I started the X server. Every other time, this left the file > system in a

Re: Regarding latest errata

I agree. Your initial response was all I needed, I thought I needed more because I'm an absolutist. -- Patrick Harper paia...@fastmail.com On Tue, 17 Apr 2018, at 10:28, Theo de Raadt wrote: > What a futile and pointless discussion. > > > Assuming that is the case, was it 6.3 or 6.1 that

Re: Beg for Atheros wifi driver

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:

Re: Beg for Atheros wifi driver

> 0x: Vendor ID: 168c Product ID: 003e https://vendev.org/pci/ven_168c_003e/ "QCA6174 802.11ac Wireless Network Adapter" You can try $ man pci | grep Atheros or $ apropos Atheros To get list all Atheros-related drivers ( ath(4), athn(4) and same for usb) but it seems that they do not

Re: Beg for Atheros wifi driver

Unless I'm blind, I don't see support for that chip. So, no amount of fw_update with a supported card is going to help you with that device. On Tue, Apr 17, 2018 at 10:11 AM, Manuel Solis wrote: > done :D > > Domain /dev/pci0: > 0:0:0: AMD AMD64 15h Root Complex >

Re: Regarding latest errata

What a futile and pointless discussion. > Assuming that is the case, was it 6.3 or 6.1 that was not 'active' > from the 2nd to the 15th? Conveniently the original 6.3 release dates > are now censored on the website, but if it had been built for the > projected date then it would not have needed

Re: Regarding latest errata

Assuming that is the case, was it 6.3 or 6.1 that was not 'active' from the 2nd to the 15th? Conveniently the original 6.3 release dates are now censored on the website, but if it had been built for the projected date then it would not have needed the 14th patches. -- Patrick Harper

Re: Beg for Atheros wifi driver

done :D 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

Re: Beg for Atheros wifi driver

Verbose output with pcidump -v would give you the vendor and product ids, which would give you more information about the "unknown" device. On Tue, Apr 17, 2018 at 9:40 AM, Manuel Solis wrote: > Thank you again, > > As i said, i am ordering the wifi usb adapters that you

Re: Regarding latest errata

> What changed was that there was a period after 6.3 was pushed out the > door (2-15 April) in which there were effectively three active > releases and the project felt obliged to support 6.1 until 6.3's > projected release date. My previous post attempted to review a > possible workaround, though

Re: Regarding latest errata

What changed was that there was a period after 6.3 was pushed out the door (2-15 April) in which there were effectively three active releases and the project felt obliged to support 6.1 until 6.3's projected release date. My previous post attempted to review a possible workaround, though I

Re: Beg for Atheros wifi driver

Thank you again, As i said, i am ordering the wifi usb adapters that you suggested, but for the record, this are the outputs from lspci and pcidump pcidump Domain /dev/pci0: 0:0:0: AMD AMD64 15h Root Complex 0:1:0: ATI Carrizo 0:1:1: ATI Radeon HD Audio 0:2:0: AMD AMD64 15h Host 0:2:2: AMD

Re: Regarding latest errata

Huh? We've told everyone 2 releases maintained with errata/syspatches, 6 months apart, only. Nothing changed here. We don't need to change a single word about EOL. It is exactly the same as before. > The best solution I can think of is planning, announcing and > implementing oldstable EOLs in

Re: Regarding latest errata

The best solution I can think of is planning, announcing and implementing oldstable EOLs in advance, but I'm not sure this would kill enough time in building patches to be worth a process change, and users would have to trade patches for contingency. Make of this whatever you will, I don't know

Re: trouble installing php on 6.3

According to /usr.sbin/pkg_add/OpenBSD/Temp.pm If PKG_TMPDIR is not set, it uses OpenBSD::Paths->vartmp >our $tempbase = $ENV{'PKG_TMPDIR'} || OpenBSD::Paths->vartmp; And according to /usr.sbin/pkg_add/OpenBSD/Paths.pm Default value is "/var/tmp". >sub vartmp() { '/var/tmp' } It seems that

Re: trouble installing php on 6.3

On 17 April 2018 at 14:13, IL Ka wrote: > So, does it work only with PKG_TMPDIR set? > > # PKG_TMPDIR=/tmp/foo pkg_add -r -vvv curl > (-r is used to replace old package) > > Could it be your harddrive or filesystem problem? > Try to fsck partition where pkg_add stores

Re: question regarding architecture mailing lists

On Mon, 16 Apr 2018, Theo de Raadt wrote: Discuss what? That OpenBSD doesn't run on it? With pleasant requests that someone will write the code? I know there is arm@, but sgi@ does not seem appropriate for Cavium Octeon or other hardware. lists which very few people pay attention to

Re: trouble installing php on 6.3

So, does it work only with PKG_TMPDIR set? # PKG_TMPDIR=/tmp/foo pkg_add -r -vvv curl (-r is used to replace old package) Could it be your harddrive or filesystem problem? Try to fsck partition where pkg_add stores packages. If you are able to download file by wget, you can install it using

Re: trouble installing php on 6.3

On 17 April 2018 at 08:56, Michael Maurer wrote: > On 16 April 2018 at 18:41, IL Ka wrote: >> Hm.. sounds strange then. >> >> Did you try to call "pkg_add libxml"? >> If not, then try and in case of success try pkg_add php again >> >> >> If it

Re: Listen-on parameter in iked.conf

On 2018/04/17 12:54, Stefan Sperling wrote: > On Mon, Apr 16, 2018 at 07:05:12AM +, Stuart Henderson wrote: > > On 2018-04-15, mabi wrote: > > > I just moved from isakmpd to iked and could not find the parameter name > > > in iked.conf in order to tell iked on which IP it

Re: Listen-on parameter in iked.conf

On Mon, Apr 16, 2018 at 07:05:12AM +, Stuart Henderson wrote: > On 2018-04-15, mabi wrote: > > I just moved from isakmpd to iked and could not find the parameter name in > > iked.conf in order to tell iked on which IP it should listen. With > > isakmpd.conf I would use

Re: Kakoune editor on openbsd

Le 2018-04-17 02:43, Patrick Marchand a écrit : On 04/16, Stuart Henderson wrote: > On 2018-04-16, Patrick Marchand wrote: > So trying again I looked closer at what the function was doing and how > it was implemented for freebsd and dragonflybsd. The function > tries

Re: carp ssh setup

On 17/04/18 02:06, jungle Boogie wrote: > Hi All, > > I have a very simple carp setup - basically I want ssh access if the > master goes offline. > In theory, this are functioning correctly. In practice, it seems the > backup is taking over way too often - the backup takes over way too > often,

Re: OpenBSD vs Linux KVM Guest Performance and Stability

On 17/04/18 10:28, Daniel Santos wrote: > On 2018-04-16 23:00, Claudio Jeker wrote: >> On Mon, Apr 16, 2018 at 11:10:46PM +0300, Kapetanakis Giannis wrote: >>> On 16/04/18 18:40, Claudio Jeker wrote: >>> > >>> >>really depends on the KVM/linux version >>> >> >>> >Don't forget to set "options

Capturing ddb output when "boot reboot" fails

Dear list My old Dell laptop ran stably under 6.1. After I upgraded to 6.2, the kernel started to crash with "page fault trap, code=0" every time I started the X server. Every other time, this left the file system in a state that fsck could not repair. I don't have a spare laptop for

Re: OpenBSD + 3G/4G USB modem

On 2018-04-16, MS wrote: > One more thing though, how do I know which USB port is which cuaXX? If I > connect to cua00 it seems to start conversation but the whole thing > freezes. cuaU0 gives not configured info. It would be a cuaU* device, the exact number depends on

Re: OpenBSD vs Linux KVM Guest Performance and Stability

On 2018-04-16 23:00, Claudio Jeker wrote: On Mon, Apr 16, 2018 at 11:10:46PM +0300, Kapetanakis Giannis wrote: On 16/04/18 18:40, Claudio Jeker wrote: > >>really depends on the KVM/linux version >> >Don't forget to set "options kvm-intel preemption_timer=0" for modprobe on >newer linux kernels.

Re: trouble installing php on 6.3

On 16 April 2018 at 18:41, IL Ka wrote: > Hm.. sounds strange then. > > Did you try to call "pkg_add libxml"? > If not, then try and in case of success try pkg_add php again > > > If it does not work, then lets do the following: > > To make sure libxml is deleted > #