Re: Panic on boot with Hyper-V since Jun 17 snapshot

On 30/07/2020 10:37, Mark Kettenis wrote: >> From: Mike Belopuhov >> Date: Thu, 30 Jul 2020 09:21:32 +0200 >> >> On 29/07/2020 15:23, Mark Kettenis wrote: >>>> Date: Wed, 29 Jul 2020 23:01:15 +1000 >>>> From: Jonathan Gray >>>> >&

Re: Panic on boot with Hyper-V since Jun 17 snapshot

On 29/07/2020 15:23, Mark Kettenis wrote: >> Date: Wed, 29 Jul 2020 23:01:15 +1000 >> From: Jonathan Gray >> >> On Wed, Jul 29, 2020 at 02:05:18PM +0200, Andre Stoebe wrote: Synopsis: Panic on boot with Hyper-V since Jun 17 snapshot Category: kernel Environment: >>> System

Re: relayd closing sessions prematurely

Hi, Pascal Guitierrez writes: > I seem to be having the same issue as this post: > https://marc.info/?l=openbsd-misc=156080861431000=2 > > > however even with the suggestion of disabling socket splicing i'm still > hitting the same problem, which seems to be an hard timeout where the > relayd

Re: Panic with pf 'once' rule

Aaron Bieber writes: > Hi, > > Adding a rule similar to the below causes a panic on -current (OpenBSD > 6.5-current (GENERIC) #95: Thu Jul 4 21:22:25 MDT 2019). This also panics 6.3 > and 6.5 (I didn't test 6.4): > > pass in quick on egress proto tcp from any to port once rdr-to \ >

Re: "ipsecctl -sa" dumps core on i386

Stefan Sperling writes: > On Sun, Mar 03, 2019 at 01:14:06PM +0100, Stefan Sperling wrote: >> On Thu, Feb 28, 2019 at 10:53:35PM +0100, Stefan Sperling wrote: >> > This problem is still present in the latest snapshot: >> > kern.version=OpenBSD 6.5-beta (GENERIC) #1248: Thu Feb 28 09:57:20 MST

Re: AWS t2.medium GENERIC.MP with 010-intelfpu has floating point exceptions with commands like dhclient

On 17 July 2018 at 18:21, Mike Erdely wrote: > > > In reply to a private reply I received, I sent the following update: > > > Does your single-CPU micro instance also provide the same Xen and CPU versions? i.e. > > Diff below. First machine: t2.small (1 cpu). Second machine: t2.medium (2 cpu) >

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

On Mon, Feb 12, 2018 at 15:47 +0100, Renaud Allard wrote: > > > On 02/12/2018 01:32 PM, Renaud Allard wrote: > > Hello, > > > > I am running OpenBSD 6.2 i386 on a VIA CPU with padlock. > > cpu0: VIA Eden Processor 1000MHz ("CentaurHauls" 686-class) 1 GHz > > cpu0: RNG AES AES-CTR SHA1 SHA256

Re: OpenBSD 6.2 amd64 on "Xen Project": Very slow download rate via VPN

Hi, Can you please try a dual cpu VM with a GENERIC.MP kernel. Does anyone else see perfomance issues on Xen in general, single cpu VMs or single-processor kernels? On Thu, Nov 02, 2017 at 13:56 -0700, Berry Wendermouth wrote: > OpenBSD 6.2 amd64 on "Xen Project": Very slow download rate via

Re: Openbsd 6.1 and Current Console Freezes and lockup Proxmox PVE5.0

On Thu, Oct 26, 2017 at 19:05 +0100, Tom Smyth wrote: > Lads, > > Im pleased to say that my testing of OpenBSD 6.1 and OpenBSD 6.2 > Release > amd64 , > appear to work a little better in Proxmox PVE5.1 as released this week, > > I used iso version 5.1-722cc488-1 from Proxmox > Updated on 24

Re: frozen clock on Intel NUC

On Thu, Oct 19, 2017 at 08:25 -0400, Joe Gidi wrote: > >> On Tue, Oct 17, 2017 at 7:43 PM, Mike Belopuhov <m...@belopuhov.com> > >> wrote: > >> > > >> > Looks like your acpitimer takes a bit too much to obtain the value > >> > a

Re: frozen clock on Intel NUC

On Tue, Oct 17, 2017 at 20:11 +0800, Adam Steen wrote: > On Tue, Oct 17, 2017 at 7:43 PM, Mike Belopuhov <m...@belopuhov.com> wrote: > > > > Looks like your acpitimer takes a bit too much to obtain the value > > and exceeds the threshold that we've imposed. Adam, I'd

Re: frozen clock on Intel NUC

Looks like your acpitimer takes a bit too much to obtain the value and exceeds the threshold that we've imposed. Adam, I'd like to commit the diff below but unsure how many successes should we consider before accepting the value. Any particular reason you've picked the minimum frequency out of

Re: frozen clock on Intel NUC

On Mon, Oct 16, 2017 at 16:10 +, Joe Gidi wrote: > Hi Mike, > > Thanks for the patch; it appears to fix the clock: > > acpitimer0 at acpi0: 3579545 Hz, 24 bits > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > > System time is advancing at the expected rate :-) > No, nothing is fixed

Re: frozen clock on Intel NUC

On Sun, Oct 15, 2017 at 16:38 +, Joe Gidi wrote: > >Synopsis:Recent TSC changes seem to result in frozen clock on Intel NUC > >Category:kernel > >Environment: > System : OpenBSD 6.2 > Details : OpenBSD 6.2-current (GENERIC.MP) #148: Fri Oct 13 16:30:01 > MDT 2017 >

Re: panic probing wdc0 at isa0

Please try the attached diff. On 22 September 2017 at 20:45, Andrew Daugherity < andrew.daugher...@gmail.com> wrote: > > >Synopsis: panic on boot during probe of wdc0 at isa0 > >Category: kernel > >Environment: > System : OpenBSD 6.2 > Details : OpenBSD 6.2-beta

Re: panic: kernel diagnostic assertion

On Sat, Aug 12, 2017 at 09:50 +0300, Atanas Vladimirov wrote: > Hi, > > My home server (-current) freeze with kernel panic and I have to reboot it > because no keyboard or IPMI working. > > panic: kernel diagnostic assertion "TAILQ_EMPTY(>cl_actc)" failed: file > "/usr/src/sys/net/hfsc.c", line

Re: -pg broken with clang

On Thu, Aug 10, 2017 at 12:38 -0400, Jeremie Courreges-Anglas wrote: > On Thu, Aug 10 2017, Mike Belopuhov <m...@belopuhov.com> wrote: > > On Thu, Aug 10, 2017 at 12:27 -0400, Martin Pieuchot wrote: > >> On 10/08/17(Thu) 18:21, Mark Kettenis wrote: > >> > >

Re: -pg broken with clang

On Thu, Aug 10, 2017 at 12:27 -0400, Martin Pieuchot wrote: > On 10/08/17(Thu) 18:21, Mark Kettenis wrote: > > > Date: Thu, 10 Aug 2017 12:10:27 -0400 > > > From: Martin Pieuchot > > > > > > Building a profiled binary, using -pg with clang doesn't work as > > > expected. A

Re: apu2 gateway crashed upon reboot

On 4 August 2017 at 13:05, Jesper Wallin wrote: > > On Fri, Aug 04, 2017 at 10:47:31AM +0100, Stuart Henderson wrote: > > To clarify: you ran syspatch, and after fetching the patches (but still > > on the old kernel) you attempted to reboot, and it stopped responding > > at

Re: Kernel panic on 6.1: init dies under load

ificant amount of load on the machine with out a panic. > I'll try and load it up more and see where we get, but so far this is > positive. > > On Wed, May 24, 2017 at 7:37 PM, Mike Belopuhov <m...@belopuhov.com> > wrote: > >> On Wed, May 24, 2017 at 12:27 -0400, Dan Cros

Re: fq codel panic: ifq_is_serialized and MP interrupt

On Thu, Jun 01, 2017 at 10:30 +0200, Mike Belopuhov wrote: > On Mon, May 29, 2017 at 14:16 +0200, Mike Belopuhov wrote: > > Thanks for taking your time to test, but unfortunately I have to > > withdraw both diffs. I've realised that there's a ton of drivers > > calling ifq_de

Re: fq codel panic: ifq_is_serialized and MP interrupt

On Mon, May 29, 2017 at 14:16 +0200, Mike Belopuhov wrote: > Thanks for taking your time to test, but unfortunately I have to > withdraw both diffs. I've realised that there's a ton of drivers > calling ifq_deq_begin manually from their start routines and > there's no sim

Re: fq codel panic: ifq_is_serialized and MP interrupt

On Mon, May 29, 2017 at 06:57 +0200, Sebastien Marie wrote: > On Sun, May 28, 2017 at 10:45:34PM +0200, Mike Belopuhov wrote: > > > > > > mikeb@, I don't reproduce if I backout the local diff. > > > > > > it seems bce(4) doesn't like it. > > >

Re: fq codel panic: ifq_is_serialized and MP interrupt

On Sat, May 27, 2017 at 20:06 +0200, Sebastien Marie wrote: > On Sat, May 27, 2017 at 07:28:26AM +0200, Sebastien Marie wrote: > > Hi, > > > > I am experiencing often the following panic: > > > > panic: kernel diagnostic assertion "ifq_is_serialized(ifq)" failed: > > ../sys/net/ifq.c, line 394

Re: fqcodel panic

On Thu, May 25, 2017 at 14:54 +0200, Sebastien Marie wrote: > On Thu, May 25, 2017 at 01:14:54PM +0200, Mike Belopuhov wrote: > > > > > > Sorry I didn't test it: I had understood that due the problem was due to > > > my (unsupported) use of fq on pppoe0, so I just s

Re: fqcodel panic

On Thu, May 25, 2017 at 07:25 +0200, Sebastien Marie wrote: > On Wed, May 24, 2017 at 06:03:04PM +0200, Mike Belopuhov wrote: > > On Sun, May 21, 2017 at 11:53 +0200, Mike Belopuhov wrote: > > > On Sat, May 20, 2017 at 18:53 +0200, Mike Belopuhov wrote: > > > > On Sa

Re: Kernel panic on 6.1: init dies under load

On Wed, May 24, 2017 at 12:27 -0400, Dan Cross wrote: > Thanks for the patch; I just got a few minutes today and I applied it, > rebuilt and installed the kernel and rebooted. Sadly, I get a similar > panic. Attached is a screenshot of console output. Note that, 'boot sync' > from ddb hangs

Re: fqcodel panic - pfctl

On Sat, May 20, 2017 at 18:03 +0200, Sebastien Marie wrote: > Hi, > > Here a report for a second panic regarding fqcodel. > > The panic occurs at pfctl time: KASSERT(qs->parent_qid == 0) from > fqcodel_pf_addqueue is reached. > > I suspect a fqcodel queue not to be usable as parent of another

Re: fqcodel panic

On Sun, May 21, 2017 at 11:53 +0200, Mike Belopuhov wrote: > On Sat, May 20, 2017 at 18:53 +0200, Mike Belopuhov wrote: > > On Sat, May 20, 2017 at 17:30 +0200, Sebastien Marie wrote: > > > Hi, > > > > > > Yesterday, I upgraded my amd64 gateway (pppoe +

Re: Suspend-to-disk doesn't work anymore

On Mon, May 22, 2017 at 12:34 -0700, Mike Larkin wrote: > On Mon, May 22, 2017 at 08:55:31PM +0200, Mike Belopuhov wrote: > > On Mon, May 22, 2017 at 20:20 +0200, Sebastien Marie wrote: > > > On Mon, May 22, 2017 at 07:32:07PM +0200, Mike Belopuhov wrote: > > > > >

Re: Suspend-to-disk doesn't work anymore

On Mon, May 22, 2017 at 20:20 +0200, Sebastien Marie wrote: > On Mon, May 22, 2017 at 07:32:07PM +0200, Mike Belopuhov wrote: > > > > > > With the last commit to revert AES_XTS to rijndael, I pushed it on > > > top of the tested tree (7 days old). Th

Re: Suspend-to-disk doesn't work anymore

On Thu, May 18, 2017 at 10:07 +0200, Sebastien Marie wrote: > On Fri, May 12, 2017 at 03:11:35PM +, Natasha Kerensikova wrote: > > >Synopsis: Suspend-to-disk doesn't work anymore > > >Category: > > >Environment: > > System : OpenBSD 6.1 > > Details : OpenBSD 6.1-current

Re: fqcodel panic

On Sat, May 20, 2017 at 18:53 +0200, Mike Belopuhov wrote: > On Sat, May 20, 2017 at 17:30 +0200, Sebastien Marie wrote: > > Hi, > > > > Yesterday, I upgraded my amd64 gateway (pppoe + vlans) with a recent > > -current in order to test a bit codel queue. > > &g

Re: fqcodel panic

On Sat, May 20, 2017 at 17:30 +0200, Sebastien Marie wrote: > Hi, > > Yesterday, I upgraded my amd64 gateway (pppoe + vlans) with a recent > -current in order to test a bit codel queue. > > OpenBSD 6.1-current (GENERIC.MP) #67: Thu May 18 18:28:26 MDT 2017 >

Re: Kernel panic on 6.1: init dies under load

On Thu, May 18, 2017 at 21:15 -0400, Dan Cross wrote: > Okay, here is the output. I apologize for the screen shot; there's no other > particularly great way to capture the console output from the VPS and I > don't trust myself to type it all in without making a mistake of some kind. > That's OK,

Re: Kernel panic on 6.1: init dies under load

On Mon, May 15, 2017 at 19:24 +0200, Mike Belopuhov wrote: > Indeed. You can run a "show uvmexp" DDB command. > > Please try running with the diff below. It will log all polled > and bounced transfers as well as some additional info. Hi, While I'm still interested in th

Re: softraid crypto performance regression

On Wed, May 17, 2017 at 18:23 +0200, Stefan Sperling wrote: > On Sun, May 07, 2017 at 08:06:56PM -0400, m.r...@excitingdomainname.com wrote: > > On 2017-05-07 19:30, Mike Belopuhov wrote: > > > You observe a decrease in performance because we've switched to > > &

Re: softraid crypto performance regression

On Wed, May 17, 2017 at 12:42 -0400, Ted Unangst wrote: > Stefan Sperling wrote: > > I also have some machines which are affected by this, and I am > > not sure what to about it. I cannot judge the advantages of > > either AES implementation. > > There's very little advantage to a constant time

Re: Kernel panic on 6.1: init dies under load

On Mon, May 15, 2017 at 11:45 -0400, Dan Cross wrote: > On Mon, May 15, 2017 at 11:28 AM, Mike Belopuhov <m...@belopuhov.com> wrote: > > > On Mon, May 15, 2017 at 11:18 -0400, Dan Cross wrote: > > > On Mon, May 15, 2017 at 11:01 AM, Mike Belopuhov <

Re: Kernel panic on 6.1: init dies under load

On Mon, May 15, 2017 at 11:18 -0400, Dan Cross wrote: > On Mon, May 15, 2017 at 11:01 AM, Mike Belopuhov <m...@belopuhov.com> wrote: > > > > Thanks for reporting this, however there's not enough info to follow > > up on this right now. What is clear is that your provi

Re: Kernel panic on 6.1: init dies under load

Hi, Thanks for reporting this, however there's not enough info to follow up on this right now. What is clear is that your provider is using an ancient version of Xen that doesn't even support the callback vector interrupt delivery (the emulated xspd0 device is delivering all interrupts). We

Re: softraid crypto performance regression

On 8 May 2017 at 01:04, wrote: > Synopsis: softraid crypto performance regression >> Category: system >> Environment: >> > System : OpenBSD 6.1 > Details : OpenBSD 6.1-current (GENERIC.MP) #51: Sat May 6 > 12:01:40 MDT 2017 >

Re: Evergrowing source tracking table

On Fri, May 05, 2017 at 16:21 +0200, Remi Barbier wrote: > >Synopsis: PF: Evergrowing source tracking table. > >Category: PF > >Environment: > System : OpenBSD 6.1 > Details : OpenBSD 6.1-current (GENERIC.MP) #50: Thu May 4 > 11:52:48 MDT 2017 > >

Re: Hardware Initialization Failed with Intel I219-V

On 5 December 2016 at 11:16, wrote: >>Synopsis: >>Category: >>Environment: > System : OpenBSD 6.0 > Details : OpenBSD 6.0-current (GENERIC.MP) #0: Wed Nov 30 > 09:19:28 MST 2016 > >

Re: m_pullup(9) regression

On Tue, Nov 08, 2016 at 11:01 +0100, Martin Pieuchot wrote: > semarie exposed a bug in m_pullup(9) while testing my diff to > automatically create lo(4) interfaces per rdomain. > > In the block below ``m'' is dereferenced without being previously set. > Indeed. My test coverage wasn't

Re: IPv6/NDP/IPsec breakage in -current

On Thu, Oct 13, 2016 at 21:43 +0200, Markus Friedl wrote: > > > Am 13.10.2016 um 13:06 schrieb Christian Weisgerber : > > > >> After the second m_makespace(): > >> > >>+--+-+ +--+ ++-+ > >>| IPv6 | ESP | | IPv6 | | ICMPv6 |

Re: IPv6/NDP/IPsec breakage in -current

On Wed, Oct 12, 2016 at 18:00 +0200, Christian Weisgerber wrote: > Mike Belopuhov: > > > It's also not clear what's wrong with those broken NS/ND > > packets that you receive. > > Oct 12 17:30:10 bardioc /bsd: nd6_na_input: ND packet from non-neighbor > Oct 12 17

Re: IPv6/NDP/IPsec breakage in -current

On Mon, Oct 10, 2016 at 21:13 +, Christian Weisgerber wrote: > On 2016-10-09, Christian Weisgerber wrote: > > > Found by bisection. The culprit is this commit: > > > > > > CVSROOT:/cvs > >

Re: crash with oce(4)

On Fri, Sep 16, 2016 at 08:50 +, Olivier Cherrier wrote: > On Thu, Sep 15, 2016 at 08:09:51PM +0200, m...@belopuhov.com wrote: > > On Thu, Sep 15, 2016 at 18:16 +0200, Martin Pieuchot wrote: > > > On 15/09/16(Thu) 14:58, Olivier Cherrier wrote: > > > > # for i in oce0 oce1 trunk0 vlan20; do >

Re: probably bug in using in combination rdomain + nat-to + specific ip addresses

Sorry for a huge delay in responding. You're right that I've missed the quick keyword. However, it appears to me that your problem stems from the fact that you don't have a gateway in rdomain 100. You must have some valid route in every rdomain otherwise routing won't happen at all. Point the

Re: cpsw(4) SIOCSETVLAN: No buffer space available, since 6.0

On 15 September 2016 at 20:14, Mike Belopuhov <m...@belopuhov.com> wrote: > On 15 September 2016 at 19:37, Steven Chamberlain <ste...@pyro.eu.org> wrote: >> Hi, >> >> After upgrading a Beaglebone Black from 5.9 to 6.0 GENERIC, VLANs seem >> to not work any m

Re: crash with oce(4)

On Wed, Sep 14, 2016 at 21:46 +0200, Mike Belopuhov wrote: > On Tue, Sep 13, 2016 at 08:50 +, Olivier Cherrier wrote: > > >Synopsis: crash with oce(4) > > >Category: network > > >Environment: > > System : OpenBSD 6.0 > > Details :

Re: crash with oce(4)

On Tue, Sep 13, 2016 at 08:50 +, Olivier Cherrier wrote: > >Synopsis:crash with oce(4) > >Category:network > >Environment: > System : OpenBSD 6.0 > Details : OpenBSD 6.0 (GENERIC.MP) #2319: Tue Jul 26 > 13:00:43 MDT 2016 > >

Re: very slow ssh / sshd performance on current

On 12 September 2016 at 20:25, Mike Belopuhov <m...@belopuhov.com> wrote: > On Fri, Sep 02, 2016 at 13:43 +0200, Alexander Bluhm wrote: >> On Fri, Sep 02, 2016 at 10:33:19AM +0200, Andreas Bartelt wrote: >> > On 09/02/16 10:24, Alexander Bluhm wrote: >> > > I s

Re: very slow ssh / sshd performance on current

On Fri, Sep 02, 2016 at 13:43 +0200, Alexander Bluhm wrote: > On Fri, Sep 02, 2016 at 10:33:19AM +0200, Andreas Bartelt wrote: > > On 09/02/16 10:24, Alexander Bluhm wrote: > > > I see a performance drop to 10 Mbit/sec on some old i386 machines > > > with em(4). Can you try this kernel diff to

Re: x260 Toshiba SATA disk keeps freezing the system

VFS_SYNC calls ffs_sync for ffs. Where does it hang inside ffs_sync? Do you have softdeps enabled for these filesystems? On 11 August 2016 at 10:04, Paul Irofti wrote: > I managed to reproduce the bug. It rarely manifests itself and it seems to > block on the partition where I

Re: OpenBSD 5.9 on XenServer 6.5, Network unresponsive

gt; > I really want to help resolve that so please excuse my inexperience on > reporting. > > You shouldn't send us your excuses. Instead, improve your reports. Help us to help you. > > Regards > > > > > > From: Mike Belopuhov [mailto:m...@belopuhov.com] > S

Re: OpenBSD 5.9 on XenServer 6.5, Network unresponsive

ello Mike > > > > One more crash with hi CPU usage > > > > > > -Original Message- > From: Mike Belopuhov [mailto:m...@belopuhov.com] > Sent: Saturday, July 30, 2016 1:35 AM > To: Antonis Psaras <psaras.anto...@gmail.com> > Cc: bugs@openbsd

Re: OpenBSD 5.9 on XenServer 6.5, Network unresponsive

timer or a thread wakeup). On 28 July 2016 at 13:49, Antonis Psaras <psaras.anto...@gmail.com> wrote: > I ‘ve done many updates in the past without any issue. I am not sure why I > have that problem on updating to snapshot. > > > > I will give it a try again. > > > &

Re: OpenBSD 5.9 on XenServer 6.5, Network unresponsive

, 2016 at 20:41 +0200, Mike Belopuhov wrote: > A number of TX-related issues have been fixed in -current. > Please make sure that you're running -current with up-to-date > source tree (sys/dev/pv/if_xnf is at revision 1.27 as of writing) > and retest. > > I don't have a sensible

Re: OpenBSD 5.9 on XenServer 6.5, Network unresponsive

formance in > general > > > > > Paravirtualized disk driver is not implemented yet. > Would it be help full for you to give you access on the box? > > > Definitely not. > Regards > > > > > > > > *From:* Mike Belopuhov [mailto:m...@belopuhov.com] &

Re: OpenBSD 5.9 on XenServer 6.5, Network unresponsive

ng bsd.rd to update the system but I get an error > message stating that cannot find OpenBSD/amd64 6.0 sets. > > > > Path is correct, I crossed check that. > > > > When 6.0 is expected? > > > > Regards > > > > > > *From:* Mike Belopuhov [mai

Re: OpenBSD 5.9 on XenServer 6.5, Network unresponsive

; > > > I can try any patch but please send me some more information on how to do > that. > > > > Regards > > > > > > -Original Message- > From: Mike Belopuhov [mailto:m...@belopuhov.com] > Sent: Wednesday, July 27, 2016 1:01 PM > To: Antonis Psara

Re: OpenBSD 5.9 on XenServer 6.5, Network unresponsive

Hi Antonis, While your report could have been a bit more detailed (for instance describing how did you get into this situation), I'm aware of the generic problem with failed interrupt delivery that can be triggered under heavy network load, e.g. packet flood. I'm trying to fix this right now.

Re: probably bug in using in combination rdomain + nat-to + specific ip addresses

Hi Imre, Not sure you've got a reply to this (I was going through unread mail on bugs@), but your "pass all flags" rule is a last match thus neither of the other pass rules are taken into account. Cheers, Mike On 28 May 2016 at 00:20, wrote: > Hi! > > I think i stumbed onto

Re: Supermicro X10SDV-TP8F with USB3 won't boot

On 6 May 2016 at 23:24, Hrvoje Popovski <hrv...@srce.hr> wrote: > On 6.5.2016. 18:08, Mike Belopuhov wrote: >> Or alternatively, if there are some devices with working Lynx Point >> xhci, we could disable enforced port routing on these models and use >> the default port

Re: two audio beep bugs

On 13 May 2016 at 06:56, Ted Unangst wrote: > 1. I have wsconsctl keyboard.bell.volume=0 because I don't like things beeping > at me. This recently stopped working in xterm, where I now get a loud beep. > Related to loss of pcvt? > > I'm not sure where the failure is, but my

Re: Supermicro X10SDV-TP8F with USB3 won't boot

On 6 May 2016 at 16:59, Mike Belopuhov <m...@belopuhov.com> wrote: > On 6 May 2016 at 16:55, Mike Belopuhov <m...@belopuhov.com> wrote: >> On 6 May 2016 at 13:48, Hrvoje Popovski <hrv...@srce.hr> wrote: >>> On 6.5.2016. 13:31, Martin Pieuchot wrote: >>

Re: Supermicro X10SDV-TP8F with USB3 won't boot

On 6 May 2016 at 16:55, Mike Belopuhov <m...@belopuhov.com> wrote: > On 6 May 2016 at 13:48, Hrvoje Popovski <hrv...@srce.hr> wrote: >> On 6.5.2016. 13:31, Martin Pieuchot wrote: >>> On 06/05/16(Fri) 13:21, Hrvoje Popovski wrote: >>>> On 6.5.2016. 13:01

Re: Supermicro X10SDV-TP8F with USB3 won't boot

On 6 May 2016 at 13:48, Hrvoje Popovski wrote: > On 6.5.2016. 13:31, Martin Pieuchot wrote: >> On 06/05/16(Fri) 13:21, Hrvoje Popovski wrote: >>> On 6.5.2016. 13:01, Martin Pieuchot wrote: On 06/05/16(Fri) 01:13, Hrvoje Popovski wrote: > Hi, > > I've got >

Re: messages log flooded with "xen0: grant table reference..."

/CTX138115#XenServer%206.5 > > I can get it installed tomorrow and even can provide access to XenServer for > time you will need. > > -- > Evgeniy > > On Wed, Mar 30, 2016 at 10:35 PM, Mike Belopuhov <m...@belopuhov.com> wrote: >> >> On 30 March 2016 at

Re: messages log flooded with "xen0: grant table reference..."

Server of yours seems to advertise Hyper-V presence as well. Any idea why is it so? > -- > Evgeniy > > On Wed, Mar 30, 2016 at 8:12 PM, Mike Belopuhov <m...@belopuhov.com> wrote: >> >> On Tue, Mar 29, 2016 at 13:43 -0700, siaro wrote: >> > Hi , I have a fresh in

Re: messages log flooded with "xen0: grant table reference..."

On Tue, Mar 29, 2016 at 13:43 -0700, siaro wrote: > Hi , I have a fresh install 5.9 > its base system , nothing pf rule and service. > Indeed. I can see the issue as well. Please use bsd.mp kernel for now (even on uniprocessor VM configurations). I'll try to resolve this issue in -current. >

Re: messages log flooded with "xen0: grant table reference..."

On 25 March 2016 at 01:17, wrote: > Synopsis: on XenServer 6.5 messages log is flooded with xen related events > Category: Xen > Environment: > System : OpenBSD 5.9 > Details : OpenBSD 5.9-current (GENERIC) #1829: Thu Mar 24 > 12:13:34 MDT 2016 >

Re: alignment fault on armv7 when using carp(4)

On 9 February 2016 at 11:31, David Gwynne wrote: > On Mon, Feb 08, 2016 at 11:02:06PM +1000, David Gwynne wrote: >> On Sat, Feb 06, 2016 at 04:43:28PM -0500, Anthony Eden wrote: >> > >Synopsis: >> > >> > To me that behavior might suggest the problem is deeper than a >> >

Re: alignment fault on armv7 when using carp(4)

On 9 February 2016 at 12:19, David Gwynne <da...@gwynne.id.au> wrote: > >> On 9 Feb 2016, at 9:12 PM, Mike Belopuhov <m...@belopuhov.com> wrote: >> >> On 9 February 2016 at 11:31, David Gwynne <da...@gwynne.id.au> wrote: >>> On Mon, Feb 08, 2016 at 1

Re: xnf crash - repeatable

On 20 January 2016 at 00:46, Jonathon Sisson <open...@j3z.org> wrote: > On Tue, Jan 19, 2016 at 06:17:40PM +0100, Mike Belopuhov wrote: >> On 19 January 2016 at 17:02, Mike Belopuhov <m...@belopuhov.com> wrote: >> > That's OK. Thank you for taking your time to

Re: xnf crash - repeatable

On 19 January 2016 at 17:02, Mike Belopuhov <m...@belopuhov.com> wrote: > On 18 January 2016 at 23:20, Jonathon Sisson <open...@j3z.org> wrote: >> On Mon, Jan 18, 2016 at 08:30:21PM +0100, Mike Belopuhov wrote: >>> On Mon, Jan 18, 2016 at 20:25 +0100, Mike Belopuh

Re: xnf crash - repeatable

On Sun, Jan 17, 2016 at 20:46 -0800, Jonathon Sisson wrote: > Hi, > > First off, thank you for OpenBSD in general, and thank you specifically > for the PV drivers on OpenBSD =) The day of migrating workloads to AWS > gets ever closer for me, and I appreciate everything the OpenBSD dev > team

Re: xnf crash - repeatable

On Mon, Jan 18, 2016 at 20:25 +0100, Mike Belopuhov wrote: > On Sun, Jan 17, 2016 at 20:46 -0800, Jonathon Sisson wrote: > > Hi, > > > > First off, thank you for OpenBSD in general, and thank you specifically > > for the PV drivers on OpenBSD =) The day of migratin

Re: stinkpad x120e USB issue with 20160114 snapshot

On 17 January 2016 at 17:53, George Rosamond <geo...@ceetonetechnology.com> wrote: > > > George Rosamond: >> Mike Belopuhov: >>> On 15 January 2016 at 21:54, George Rosamond >>> <geo...@ceetonetechnology.com> wrote: >>>> Mike Belopu

Re: stinkpad x120e USB issue with 20160114 snapshot

Hi, Thanks for the report. Could you please do a "boot -d", "w mp_verbose 1", "continue" and then show us the ioapic dump. On 15 January 2016 at 20:24, George Rosamond wrote: > no console, so manually typing out trace output > > ehci_sync_hc: tsleep() = 35 >

Re: kernel panic on boot with latest snapshot

On 15 January 2016 at 19:21, Nils Reuße wrote: >>Synopsis: ehci_sync_hc: kernel panic, protection fault trap on boot >>Category: kernel >>Environment: > System : OpenBSD 5.9 > Details : OpenBSD 5.9-beta (GENERIC.MP) #1811: Mon Jan 11 >

Re: ehci_sync_hc: tsleep on latest snaps boot freeze

Hi Michael, Thanks for the report. If you still have this snapshot installed, could you please do a "boot -d", "w mp_verbose 1", "continue" and then show us the ioapic dump. Thanks, Mike On 14 January 2016 at 22:37, Michael Lesniewski wrote: > Synopsis:

Re: stinkpad x120e USB issue with 20160114 snapshot

On 15 January 2016 at 21:41, George Rosamond <geo...@ceetonetechnology.com> wrote: > Mike Belopuhov: >> Hi, >> >> Thanks for the report. Could you please do a "boot -d", "w mp_verbose >> 1", "continue" >> and then show

Re: kernel panic on boot with latest snapshot

On 15 January 2016 at 21:33, Mike Belopuhov <m...@belopuhov.com> wrote: > On 15 January 2016 at 19:21, Nils Reuße <n.reu...@hxgn.net> wrote: >>>Synopsis: ehci_sync_hc: kernel panic, protection fault trap on boot >>>Category: kernel >>>Environ

Re: stinkpad x120e USB issue with 20160114 snapshot

On 15 January 2016 at 21:54, George Rosamond <geo...@ceetonetechnology.com> wrote: > Mike Belopuhov: >> On 15 January 2016 at 21:43, Mike Belopuhov <m...@belopuhov.com> wrote: >>> On 15 January 2016 at 21:41, George Rosamond >>> <geo...@ceetonetechnology

Re: ehci_sync_hc: tsleep on latest snaps boot freeze

On 15 January 2016 at 21:38, Mike Belopuhov <m...@belopuhov.com> wrote: > Hi Michael, > > Thanks for the report. If you still have this snapshot installed, > could you please > do a "boot -d", "w mp_verbose 1", "continue" and then show us the

Re: "panic: ipintr no HDR" when attempting to connect OpenBSD running l2tp/IPsec

On Thu, Dec 03, 2015 at 11:46 +, Sevan / Venture37 wrote: > Hi, > I ran into this issue last night when I was testing out a trivial VPN > config & assumed it may have been related to virtualbox but I've just > replicated it on a ThinkPad X60s. > > panic: ipintr no HDR > Stopped at

Re: "panic: ipintr no HDR" when attempting to connect OpenBSD running l2tp/IPsec

On 3 December 2015 at 16:46, Alexander Bluhm wrote: > On Thu, Dec 03, 2015 at 03:09:37PM +, Sevan / Venture37 wrote: >> panic: no HDR: pppxwrite > > Please try this (untested) > this looks correct.

Re: VLAN interface always reported unknown by snmpd(8)

On 19 October 2015 at 18:16, BARDOU Pierre wrote: > Hello, > > What information do you need ? > > I have this setup carp -> vlan -> trunk -> ix > Maybe the responsible is trunk ? I see in the snmpwalk that it is unknown too. > Does it show correct status if you restart snmpd?

Re: panic: no appropriate pool

On Mon, Aug 03, 2015 at 11:14 +1000, Jonathan Gray wrote: On Mon, Aug 03, 2015 at 12:55:46AM +0200, Mike Belopuhov wrote: On 2 August 2015 at 22:00, RD Thrush openbsd-t...@thrush.com wrote: On 08/02/15 13:37, Mike Belopuhov wrote: most likely it's triggered by the reply-to statement. you

Re: panic: no appropriate pool

On 2 August 2015 at 15:28, RD Thrush openbsd-t...@thrush.com wrote: On 08/01/15 19:31, Jonathan Gray wrote: On Sat, Aug 01, 2015 at 08:46:00PM +0200, Mike Belopuhov wrote: [... snip ...] You're slightly overanalyzing here: panic has caught the unhandled case, but it's not needed per se

Re: panic: no appropriate pool

On 2 August 2015 at 22:00, RD Thrush openbsd-t...@thrush.com wrote: On 08/02/15 13:37, Mike Belopuhov wrote: most likely it's triggered by the reply-to statement. you may try the attached diff to see which rule the state belongs to. since you're using anchors, figuring out rule numbers

Re: panic: no appropriate pool

On 1 August 2015 at 19:20, RD Thrush openbsd-t...@thrush.com wrote: The patch ran without panic for 20+ hours. Thanks for testing! I wondered about the removal of the panic() statement so I tried another kernel that added the memset() but kept the panic() statement, as follows: [snip]

Re: panic: no appropriate pool

On Fri, Jul 31, 2015 at 10:57 -0400, RD Thrush wrote: Synopsis:panic in sys/net/pf_lb.c Category:kernel Environment: System : OpenBSD 5.8 Details : OpenBSD 5.8 (GENERIC) #1047: Thu Jul 30 23:24:48 MDT 2015

Re: panic: no appropriate pool

On Fri, Jul 31, 2015 at 10:57 -0400, RD Thrush wrote: Synopsis:panic in sys/net/pf_lb.c Category:kernel Environment: System : OpenBSD 5.8 Details : OpenBSD 5.8 (GENERIC) #1047: Thu Jul 30 23:24:48 MDT 2015

Re: Invalid 'config' keyword crashes iked config parser

On 3 July 2015 at 18:03, trondd tro...@kagu-tsuchi.com wrote: Crash from iked config parser with an invalid 'config' keyword. Example config: ikev2 roadwarrior esp \ from 123.123.123.123/32 to 0.0.0.0/0 \ peer 0.0.0.0/0 local 123.123.123.123 \ srcid 123.123.123.123 \ config

Re: em0 interface on Lenovo T60 hangs starting as of OpenBSD 5.7

On 11 May 2015 at 20:38, Mark Kettenis mark.kette...@xs4all.nl wrote: Date: Mon, 11 May 2015 12:37:19 -0400 From: Brad Smith b...@comstyle.com On 05/11/15 10:23, Stuart Henderson wrote: If all em(4) need 4 descriptors, would it make more sense to just enforce lwm = 4? Both from a

Re: tcp keep-alives sent without timestamps

On 14 April 2015 at 21:08, Lauri Tirkkonen loth...@iki.fi wrote: On Tue, Apr 14 2015 20:40:58 +0200, Mike Belopuhov wrote: According to 3.2 in RFC 7323: Once TSopt has been successfully negotiated, that is both SYN and SYN,ACK contain TSopt, the TSopt MUST be sent in every non-RST

  1   2   >