W dniu 09.03.2019 o 12:43, Otto Moerbeek pisze:
On Sat, Mar 09, 2019 at 12:10:34PM +0100, Michał Koc wrote:
W dniu 09.03.2019 o 08:15, Otto Moerbeek pisze:
On Fri, Mar 08, 2019 at 12:03:25PM +0100, Michał Koc wrote:
Hi all,
We have a triple redundant vpn gateway setup with sasyncd running
W dniu 09.03.2019 o 08:15, Otto Moerbeek pisze:
On Fri, Mar 08, 2019 at 12:03:25PM +0100, Michał Koc wrote:
Hi all,
We have a triple redundant vpn gateway setup with sasyncd running and tons
of tunnels, about 1000 flows.
Looking at the graph of memory usage, you can clearly see that
Hi all,
We have a triple redundant vpn gateway setup with sasyncd running and
tons of tunnels, about 1000 flows.
Looking at the graph of memory usage, you can clearly see that something
is sucking up the memory.
The graph can be viewed here: https://pasteboard.co/I4sjzQ8.jpg
Looking at the
-- Wiadomość oryginalna --
*Temat: *Re: Openbsd 6.1 and Current Console Freezes and lockup Proxmox
PVE5.0
*Nadawca: *Mike Larkin
*Adresat: *Michał Koc
*Kopia: *misc@openbsd.org
*Data: *19.10.2017 08:36
On Fri, Oct 13, 2017 at 11:05:12PM +0200, Michał Koc wrote:
On Thu, Oct 12, 2017
On Fri, Oct 13, 2017 at 11:05:12PM +0200, Michał Koc wrote:
On Thu, Oct 12, 2017 at 03:11:31PM -0700, Mike Larkin wrote:
On Thu, Oct 12, 2017 at 10:36:42PM +0200, Michał Koc wrote:
On Thu, Oct 12, 2017 at 01:23:36PM +0200, Michał Koc wrote:
On Sun, Oct 08, 2017 at 11:59:52PM +0200, Oliver
On Thu, Oct 12, 2017 at 03:11:31PM -0700, Mike Larkin wrote:
On Thu, Oct 12, 2017 at 10:36:42PM +0200, Michał Koc wrote:
On Thu, Oct 12, 2017 at 01:23:36PM +0200, Michał Koc wrote:
On Sun, Oct 08, 2017 at 11:59:52PM +0200, Oliver Marugg wrote:
On 7 Oct 2017, at 22:01, Mike Larkin wrote
On Thu, Oct 12, 2017 at 01:23:36PM +0200, Michał Koc wrote:
On Sun, Oct 08, 2017 at 11:59:52PM +0200, Oliver Marugg wrote:
On 7 Oct 2017, at 22:01, Mike Larkin wrote:
On Sat, Oct 07, 2017 at 02:19:58PM +0200, Oliver Marugg wrote:
Just to add a 4th situation of hangs: Login via proxmox (pve
On Sun, Oct 08, 2017 at 11:59:52PM +0200, Oliver Marugg wrote:
On 7 Oct 2017, at 22:01, Mike Larkin wrote:
On Sat, Oct 07, 2017 at 02:19:58PM +0200, Oliver Marugg wrote:
Just to add a 4th situation of hangs: Login via proxmox (pve)/kvm
serial
console (via noVNC), login successful: Vm guest in
Hi Stuart,
Rising openfiles-cur does not change anything.
Best Regards
M.K.
-- Wiadomość oryginalna --
*Temat: *Re: isakmpd dies quietly with over 100 tunnels
*Nadawca: *Stuart Henderson
*Adresat: *misc@openbsd.org
*Data: *30.05.2017 11:55
On 2017-05-28, Michał Koc wrote:
Hi all
t /usr/src/sbin/isakmpd/isakmpd.c:533
(gdb)
Best regards
M.K.
-- Wiadomość oryginalna --
*Temat: *Re: isakmpd dies quietly with over 100 tunnels
*Nadawca: *Michał Koc
*Adresat: *Alexis VACHETTE , Theo de Raadt
, Florian Ermisch
*Kopia: *misc@openbsd.org
*Data: *29.05.2017 11:39
Hi all,
we are set
Hi all,
we are setting up a test environment, will be back soon with the traces.
Best Regards
M.K.
-- Wiadomość oryginalna --
*Temat: *Re: isakmpd dies quietly with over 100 tunnels
*Nadawca: *Alexis VACHETTE
*Adresat: *Theo de Raadt , Florian Ermisch
*Kopia: *, Michał Koc
*Data
Hi all,
I'm running 6.0/amd64 inside KVM/Quemu with over 100 ipsec tunnels.
Everything was running just fine when the number of tunnels was lower.
But as we have been setting up more and more tunnels we suddenly run on
problems.
The isakmpd deaemon keeps dying quietly. Probably I'm running out
Tank You for the authoritative answer,
so we will have to get used to the, let say new, ipsecctl output.
Also good to know that monitoring tools have to look some elsewhere to
see VPN and routing is up :)
Instead of waking 12 people at 1:00 AM :)
Anyway, in my opinion this king of exercises are
Hi misc,
Let me repeat myself: anyone CAPABLE to answer (and understand the
question) ?
I really admire and appreciate your (misc) commitment.
Best regards
MichaÅ Koc
-- WiadomoÅÄ oryginalna --
*Temat: *Re: what happened to the encap address_family
*Nadawca: *Fred
*Adresat: *MichaÅ
Hello misc,
anyone capable to answer ?
Best regards
MichaÅ Koc
-- WiadomoÅÄ oryginalna --
*Temat: *what happened to the encap address_family
*Nadawca: *Boris Goldberg
*Adresat: *misc@openbsd.org
*Data: *2015-05-14 18:14
> Hello misc,
>
> The encap address_family isn't in the netsta
On Mon, Dec 01, 2014 at 17:33, MichaÅ Koc wrote:
>> Hi All,
>>
>> I've got a OpenBSD installation on Microsoft Hyper-V, and there is a
>> strange issue related to time.
>> Actually the clock seems to be running fine, but all of the sleep
>> operations expire 2 times too fast.
>> cpu0 at mainbus0:
Hi All,
I've got a OpenBSD installation on Microsoft Hyper-V, and there is a
strange issue related to time.
Actually the clock seems to be running fine, but all of the sleep
operations expire 2 times too fast.
I.e.:
# date; sleep 60; date
Mon Dec 1 18:23:18 CET 2014
Mon Dec 1 18:23:48 CET 201
Can't say anything bad about WD Raid Edition drives.
Currently I've go over 100 of them without any problems.
Thou I've found some of them generating small number of Raw Read Error
Rate, but only in 2TB model WDC WD2002FYPS.
I've got much worse experience with Seagate
My policy i
Well,
it looks like the patch did the trick :) thanks a lot :)
shouldn't it get to Tag OpenBSD_4_8, so everyone can benefit ?
correct me if I'm wrong, but re(4) seems to be a popular interface
best regards
M.K.
W dniu 2010-11-12 22:32, Stuart Henderson pisze:
[moving from misc to tech@, rep
Hello,
wait a second, I'll be able to test tomorrow, will give the result instantly
best regards
M.K.
W dniu 2010-11-12 22:32, Stuart Henderson pisze:
> [moving from misc to tech@, reply-to set]
> On 2010-11-12, Stuart Henderson wrote:
>> On 2010-11-11, Micha?? Koc wrote:
>>> Yes, it does.
>
Yes, it does.
regards
M.K.
W dniu 2010-11-11 10:53, Stuart Henderson pisze:
On 2010-11-10, Micha?? Koc wrote:
Hi All,
migrating from re to em solved the network problem
With the re(4), does the system recover if you leave it for a couple of minutes?
Hi All,
migrating from re to em solved the network problem
best regards
m.k.
W dniu 2010-11-03 12:17, MichaE Koc pisze:
Hi All,
I've just upgraded two of my OpenBSD machines to 4.8:
hw.machine=i386
hw.model=Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz ("GenuineIntel"
686-class)
hw.product=
Hmmm,
I was a little bit too optimistic.
The hight disk IO seems not to cause problems now, but network io (re
adapter) from nagios(probably) has freezed the Atom machine after
approximately 2 hours.
This is top header right after freeze:
75 processes: 1 running, 70 idle, 4 on processor
CP
Thank You for your time.
The patch seems to resolve both problems on Atom platform. Will check
Core2Duo later.
Thanks once again
Best regard
M.K.
W dniu 2010-11-05 18:36, Bob Beck pisze:
Are you able to try the following? see if it solves your problem.
Index: sys/kern/vfs_bio.c
==
Hi All,
I've just upgraded two of my OpenBSD machines to 4.8:
hw.machine=i386
hw.model=Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz ("GenuineIntel"
686-class)
hw.product=DG31PR
and
hw.machine=i386
hw.model=Intel(R) Atom(TM) CPU D510 @ 1.66GHz ("GenuineIntel" 686-class)
hw.product=D510MO
Dmesg
Hi,
I've just tested SRCS28X witch is a ami0 raid controller with OpenBSD
4.4 errata 005 on fallowing architectures:
- i386
- i386 SMP
- amd64
- amd64 SMP
It occurs that dd uf=/dev/zero of=/test to the filesystem mounted on
ami0 freezes the system on amd64/SMP only. This behavior is repetitive.
Hi,
I've just set up two 4.4 boxes, i386 and amd64 on same king of hardware.
I've started bundled apache and compiled ab from apache 2.2.10
The problem is that ab stops after about 100 requests with error:
ab started on local machine: apr_socket_connect(): Connection refused (61)
ab started on d
is it ?
according to man release:
OPENBSD_x_y_BASE This tag marks the source as it exists on the release
CD-ROM where x is the major release number and y
is the
minor release number.
OPENBSD_x_y This tag is a moving target. It marks
Due to some problems witch patch formatting in mail agent
it is also available at http://www.prime.pl/relayd.diff
regards
MichaE Koc
Pierre-Yves Ritschard pisze:
>> + if (rdr->conf.flags & F_STICKY)
>> + if (ioctl(env->sc_pf->dev, DIOCCLRSRCNODES, 0) == -1)
>> +
Hi,
Looking into pf_ioctl.c and pfvar.h I've found that there is an
undocumented (for some unknown reason) IOCTL - DIOCKILLSRCNODES.
Further investigation revealed that it's purpose is to remove single
node from source tracking tree.
So the simplest way is find out what connections should be re
Hi,
actually it is enough to clear the tree of source tracking nodes right
after syncing tables, so the sticky-address is stored again.
Unfortunately there is one disadvantage, all sources will be flushed, so
some connections can be assigned to different hosts.
But I think it's better then lea
Hi,
Using drive 0, partition 3.
Loading...
probing: pc0 apm mem[635K 3573M 16K a20=on]
disk: hd0+
>> OpenBSD/i386 BOOT 3.01
boot> machine memory
Region 0: type 1 at 0x1000 for 635KB
Region 1: type 2 at 0x9fc00 for 1KB
Region 2: type 2 at 0xe for 128KB
Region 3: type 1 at 0x10 for 3659244K
Hello
I've noticed this problem on many different INTEL motherboard models.
Debugging showed that under the address where acpi structures should be
are actually zeros.
So there is probably some memory mapping problem.
regards
M.K.
Marcos Laufer pisze:
> Hello , i tried updating the BIOS to the
Hi,
same problem on Toshiba x200-21k, memory tested for 24h by memtest, so I
assume it's okey
regards
M.K.
Jack J. Woehr pisze:
Possible motherboard hardware problems (PCI controller), or possibly
memory problems?
(( "pcibios0: bad IRQ table checksum" ))
On Dec 21, 2007, at 1:28 PM, Key
Peter N. M. Hansteen pisze:
> "Leonardo Marques" <[EMAIL PROTECTED]> writes:
>
>
>> I've a HD which are returning a lot of errors. Someone know some good
>> tool to analyze this disk and tell me if i've to replace it or if
>> exist some way to repair it?
>>
>
> To my mind that kind of error
Hello,
Well, actually I've already tried this without any luck. The problem
lies somewhere deeper,
I was trying to get at least acpidump working, and what I found is,
that RSD PTR looks fine,
but under address pointed by rs->addr all I can find are zeroes.
May be a problem with physical memory
Hi,
yes, I've already googled for the issue and found this one, but it
does not help.
I think it is whole another problem.
regards
M.K.
Chris Kuethe pisze:
> http://marc.info/?l=openbsd-tech&m=118975639013313&w=2
>
> On 9/16/07, Micha3 Koc <[EMAIL PROTECTED]> wrote:
>
>> Hello everyone,
>>
>>
Hello everyone,
I have a bunch of machines based on Intel motherboards, most of them are
D945GCNL,
but unfortunately I'm not able to use SMP because of ACPI problems.
Beside the kernel side problems, acpidump outputs a strange error: RSDT
is corrupted.
Can someone tell me if there is any chance
Hello,
I've a problem with sensors on one of my machines, it seems to be coming
from ichiic slave detection.
The machine is:
INTEL BLKD865GSAL motherboard hw.product=D865GSA
It contains a Winbond W83627EHG chip, witch is the lead-free version of
W83627EHF - supported by OpenBSD (google says th
OpenBSD SMP is based on BigLock, so only one processor at the time can
execute kernel code, and IP Stack is kernel side only.
As far as I remember.
regards
M.K.
Gustavo Rios napisaE(a):
I have the same understanding you have Pachl. I believe OpenBSD IP
Stack is not multithreaded implemented.
Hello,
I tried to boot OpenBSD on E7230 chipset, but no luck so faar. System
hangs during device recognition in random moments.
Strange thing is that cursor jumps to the center of the screen.
Has anyone managed to run OpenBSD on E7230 chipset ?
regards
M.K.
[demime 1.01d removed an attachment
Shane J Pearson napisaE(a):
Hi MichaE,
On 2006.02.24, at 10:24 PM, MichaE Koc wrote:
can someone confirm that 3Ware 9500S-12 does or does not work with
OpenBSD ?
Based on what I last I heard, I think the most important point is that
3Ware the company, does not work with OpenBSD the proje
Hello,
can someone confirm that 3Ware 9500S-12 does or does not work with
OpenBSD ?
I'd also appreciate any suggestion about 12-channel sata raid solutions.
Regards
M.K.
Yes,
the problem lies in interrupts,
I've just tried xl, fxp and rl Nic's, and none of them works as em.
Furthermore their interrupts are not showed in vmstat -i.
It would be very helpfull if some wise guy could tell me where to look
for the problem.
Otherwise I'll have to go thru the kernel so
One more question:
is ist matter of wrong irq assigment ??
em0 at pci2 dev 2 function 0 "Intel PRO/1000XT (82544EI)" rev 0x02: apic
8 int 9
(irq 9), address: 00:0e:0c:70:c9:52
em1 at pci2 dev 5 function 0 "Intel PRO/1000MT (82546EB)" rev 0x01: apic
8 int 9
(irq 9), address: 00:03:47:32:c8:ca
ok,
When I run GENERIC SMP kernel, the problem persists,
I'll privide You a dmesg from GENERIC.SMP tomorrow, but it does not
change anytning.
There are 3 changes I've made to generic:
enable aac,
add my aac card to aac_pci so it can be configured,
add my ICU to pci_intr so it can be configured
OpenBSD 3.7-stable (STORAGE.MP) #1: Sat Jul 2 21:29:32 CEST 2005
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/STORAGE.MP
cpu0: Intel(R) Xeon(TM) CPU 2.66GHz ("GenuineIntel" 686-class) 2.66 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CF
real mem = 32
Here You have dmesg from 3.6 SP before patch:
I'll provide 3.7 sp, smp, after and before patch tomorrow.
Thank You.
MichaE Koc
OpenBSD 3.6-stable (GENERIC) #0: Mon Mar 7 14:01:06 CET 2005
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Xeon(TM) CPU 2.66GHz ("GenuineIn
Ok,
starting from the beginnig,
The em nics are visible in dmesg and ifconfig.
They do transmit packets as I can see in tcpdump on the destination machine.
But they do not recive any packets.
ie. I ping from SMP machine to dest
on dest I can se echo requests comming from SMP and echo replies goi
Hello all,
I've a problem with em0 (and eventually any other nic connected to the
pci bus) on double Xeon, while I run smp kernel.
I have no idea what could couse it, there was problem with ICU but I've
fixed it as follows:
pcibios0: no compatible PCI ICU found: ICU vendor 0x8086 product 0x
50 matches
Mail list logo