Re: vmctl(8) pause never returns

* Abel Abraham Camarillo Ojeda [2018-02-15 06:06:50 -0600]: Synopsis: vmctl(8) pause never returns Category: amd64 Environment: System : OpenBSD 6.2 Details : OpenBSD 6.2-current (GENERIC.MP) #5: Mon Feb 12 21:05:57 MST 2018

Re: OpenBSD 6.2 IKED IPv6 Connections and address dropped

On Thu, Feb 15, 2018 at 06:52:46PM -0200, R0me0 *** wrote: > Hello guys! > > I have a very weird issue, not sure if a bug, but seems. > > Here my iked.conf > > ikev2 "pufferfish" passive esp from 0.0.0.0/0 to 192.10.10.0/24 \ > local 10.10.10.10 peer any \ > ikesa enc aes-256 auth

Re: xhci "NEC xHCI" controller problem without any kernel errors and messages

The issue repeated on two different but the same family laptops. I've tested it on Lenovo X220 i7 i2640 2.8GHz, and X220 i7 i2620 2.7GHz. The overall configurations is identical except CPU frequency. HDD loose block during R/W operation as in my previous post. No any kernel errors present.

OpenBSD 6.2 IKED IPv6 Connections and address dropped

Hello guys! I have a very weird issue, not sure if a bug, but seems. Here my iked.conf ikev2 "pufferfish" passive esp from 0.0.0.0/0 to 192.10.10.0/24 \ local 10.10.10.10 peer any \ ikesa enc aes-256 auth hmac-sha2-256 group modp2048 \ childsa enc aes-256 auth hmac-sha2-256 group modp2048

Re: When installing to softraid, the OS installer creates an unnecessary EFI volume inside the softraid

On 2018/02/15 03:57, Tinker wrote: > When you run the installer (e.g. flash "install62.fs" onto an USB > memory stick) and install onto a softraid (e.g. by going into (S)hell > mode at boot, creating a GPT partition table on your system drive e.g. > "fdisk -igy -b 960 sd0", creating a softraid on

Re: Bug in pf-logging, logging wrong rule number

On Thu, Feb 15, 2018 at 10:25:07AM +0100, Illya Meyer wrote: > I discovered a strange behaviour since OpenBSD 6.2 with pf logging, when > an "anchor" is in the ruleset of /etc/pf.conf. It logs in some cases the > rule number of the anchor and not the matching rule, although the > correct rule

When installing to softraid, the OS installer creates an unnecessary EFI volume inside the softraid

Hi, When you run the installer (e.g. flash "install62.fs" onto an USB memory stick) and install onto a softraid (e.g. by going into (S)hell mode at boot, creating a GPT partition table on your system drive e.g. "fdisk -igy -b 960 sd0", creating a softraid on sd0 using "bioctl" that then appears

Re: When installing to softraid, the OS installer creates an unnecessary EFI volume inside the softraid

On February 15, 2018 4:57 PM, Tinker wrote: >Hi, .. > - Do "bioctl -c C -r 8192 -l /dev/sd0a softraid0", type the password (And this creates sd2.) > - Run "/install". When asked about device to install on, choose "sd2". The specific interaction is: Available disks are:

Fwd: Bug in pf-logging, logging wrong rule number (A0A2-7649-0969)

The problem still exists in the -current-branch. Betreff: Re: Bug in pf-logging, logging wrong rule number Datum: Thu, 15 Feb 2018 14:02:00 +0100 Von: Otto Moerbeek An: Illya Meyer On Thu, Feb 15, 2018 at 01:29:55PM +0100, Illya Meyer wrote: Am

vmctl(8) pause never returns

>Synopsis: vmctl(8) pause never returns >Category: amd64 >Environment: System : OpenBSD 6.2 Details : OpenBSD 6.2-current (GENERIC.MP) #5: Mon Feb 12 21:05:57 MST 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP Architecture:

Re: Bug in pf-logging, logging wrong rule number

On Thu, Feb 15, 2018 at 10:25:07AM +0100, Illya Meyer wrote: > Hello OpenBSD-Team, > > I discovered a strange behaviour since OpenBSD 6.2 with pf logging, when an > "anchor" is in the ruleset of /etc/pf.conf. It logs in some cases the rule > number of the anchor and not the matching rule,

Bug in pf-logging, logging wrong rule number

Hello OpenBSD-Team, I discovered a strange behaviour since OpenBSD 6.2 with pf logging, when an "anchor" is in the ruleset of /etc/pf.conf. It logs in some cases the rule number of the anchor and not the matching rule, although the correct rule is used. I discovered the problem on three

Re: ipsec issue since at least 6.2 on VIA CPUs with padlock

On 02/14/2018 11:26 PM, Mike Belopuhov wrote: > > Hi, > > Thank you for your report, I think I forgot to convert bits to bytes. > Please test the diff below. > > Cheers, > Mike > > > diff --git sys/arch/amd64/amd64/via.c sys/arch/amd64/amd64/via.c > index c0e1e540b12..818c35f53d0 100644 >