On 19.6.2018. 15:14, Albert Martinez wrote:
> Dear OpenBSD Team,
>
> first of all, thanks for your time and effort in the OBSD project, we use it
> daily.
Hi,
please send dmesg and if you can install latest -current and report back.
On 1.10.2020. 22:22, gmercier+open...@phare.normalesup.org wrote:
>> Synopsis:em0 not recognized anymore
>> Category:Hardware Failure
>> Environment:
> System : OpenBSD 6.8
> Details : OpenBSD 6.8 (GENERIC.MP) #96: Tue Sep 29 18:30:41 MDT 2020
>
Hi all,
i'm not much of a switch user, just tried to play with it. With most
recent snapshot i'm getting this splassert
r620-1# ifconfig switch0 create && ifconfig switch0 add ix0 && ifconfig
switch0 destroy
splassert: ifpromisc: want 2 have 0
Starting stack trace...
ifpromisc(80082048,0)
On 10.4.2020. 21:30, Theo de Raadt wrote:
> Why did it take almost a year to find this?
>
> Or is this bug due to ioctl(2) becoming UNLOCKED on 2020/02/22?
Hi guys,
i think that this splassert is not related only to bridge..
hostname.bridge1242
add vxlan1242
add vlan1242
up
x3550m4# ifconfig
On 11.4.2020. 5:26, Visa Hankala wrote:
> On Fri, Apr 10, 2020 at 11:39:59PM +0200, Hrvoje Popovski wrote:
>> hostname.tpmr20
>> trunkport vxlan20
>> trunkport vlan20
>> up
>>
>>
>> x3550m4# ifconfig tpmr20 destroy
>>
>> splassert: vlan_ioct
On 31.5.2016. 18:44, Martin Pieuchot wrote:
> On 06/05/16(Fri) 01:13, Hrvoje Popovski wrote:
>> Hi,
>>
>> I've got
>> http://www.supermicro.com/products/motherboard/Xeon/D/X10SDV-TP8F.cfm
>> for my openbsd lab. Default BIOS settings for usb is USB3 and with th
On 31.5.2016. 20:11, Evgeniy Sudyr wrote:
> Hrvoje,
>
> what about disabling ACPI and USB during boot? Does it work for you?
>
> boot -c
> disable acpi
> disable xhci
>
Hi,
but with this patch box is booting fine with USB2 or USB3. Without this
patch box would boot, but with USB2 only.
On 31.5.2016. 19:26, Hrvoje Popovski wrote:
> On 31.5.2016. 18:44, Martin Pieuchot wrote:
>> On 06/05/16(Fri) 01:13, Hrvoje Popovski wrote:
>>> Hi,
>>>
>>> I've got
>>> http://www.supermicro.com/products/motherboard/Xeon/D/X10SDV-TP8F.cfm
>&g
On 2.9.2016. 20:14, Adam McDougall wrote:
> Would it be possible to add a method to the boot loader to disable
> DDB support in the kernel, or perhaps even disable it by default?
> I've encountered two different brands of servers (Dell and HP)
> where the remote graphical console loses keystrokes i
Hi all,
I don't have ip6 in network where em0 interface is.
It seems, that when I add inet6 autoconf in hostname.em0 and
when I do sh netstart em0 I loose ip4 default route. If I do
ifconfig em0 inet6 autoconf everything is ok. I think that this behavior
is not intended so i'm sending this to bugs
On 3.12.2016. 19:59, Hrvoje Popovski wrote:
> Hi all,
>
> I don't have ip6 in network where em0 interface is.
> It seems, that when I add inet6 autoconf in hostname.em0 and
> when I do sh netstart em0 I loose ip4 default route. If I do
> ifconfig em0 inet6 autoconf everyth
On 5.12.2016. 16:26, Martin Pieuchot wrote:
> Hello,
>
> On 03/12/16(Sat) 19:59, Hrvoje Popovski wrote:
>> I don't have ip6 in network where em0 interface is.
>> It seems, that when I add inet6 autoconf in hostname.em0 and
>> when I do sh netstart em0 I
Hi all,
it seems that pseudo-device can be created if you type whatever you want
after "c" in "create" parameter...
i think that this is not intended behavior so i'm sending this to bugs@.
if it is, sorry for noise...
ifconfig vlan123 c*
ifconfig: changelist: bad value
# ifconfig vlan123
vlan
On 3.1.2017. 13:54, Paul de Weerd wrote:
> On Tue, Jan 03, 2017 at 12:02:25PM +0100, Hrvoje Popovski wrote:
> | Hi all,
> |
> | it seems that pseudo-device can be created if you type whatever you want
> | after "c" in "create" parameter...
>
> N
On 8.3.2016. 5:07, Lars Noodén wrote:
> On Tue, Mar 8, 2016 at 12:08 AM, Stuart Henderson wrote:
>> On 2016/03/07 18:15, Lars Noodén wrote:
>>> I had two panics with soekris 5501 on OpenBSD 5.9-current (GENERIC)
>>> #1573: Sun Mar 6 19:15:08 MST 2016, apparently from just logging in
>>> and typing
On 3.4.2016. 2:13, Evgeniy Sudyr wrote:
> Mischa, please provide sendbug (1) with all details to developers and
> then wait and hope someone will pick that bug.
>
> Personally I will suggest you to don't use that 11 years old NIC which
> causes such problems (in archives I found some reports simil
On 11.4.2016. 23:38, Hrvoje Popovski wrote:
> Hi all,
>
> virtual console on idrac7 (dell r420,r620) and idrac8 (dell r430,r630)
> is losing characters when typing. It's not that one can't type anything
> but it's very slow and painful.
>
> Matthieu Herrb
On 6.5.2016. 13:01, Martin Pieuchot wrote:
> On 06/05/16(Fri) 01:13, Hrvoje Popovski wrote:
>> Hi,
>>
>> I've got
>> http://www.supermicro.com/products/motherboard/Xeon/D/X10SDV-TP8F.cfm
>> for my openbsd lab. Default BIOS settings for usb is USB3 and with th
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
>>>>
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 configuration that machine comes up with (in my
> case there are no enabled xhci ports, PCI_XHCI_
On 6.5.2016. 23:24, Hrvoje Popovski 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 configuration that machine
On 17.5.2016. 13:16, Mike Belopuhov wrote:
> Sorry, forgot to answer that. No and no. I think Martin will get some
> hardware soon.
>
ok, sorry for spam ...
Hi all,
while sending ip6 packets from host connected to vlan200 to host
connected vlan300 and then destroying vlan300 i'm getting kernel page
fault. it's clean snapshot from 2017-11-08. it's easily reproducible
# ifconfig vlan300 destroy
uvm_fault(0x81afe778, 0xd4, 0, 1) -> e
kernel: pa
On 9.11.2017. 1:11, Hrvoje Popovski wrote:
> Hi all,
>
> while sending ip6 packets from host connected to vlan200 to host
> connected vlan300 and then destroying vlan300 i'm getting kernel page
> fault. it's clean snapshot from 2017-11-08. it's easily reproduci
hi all,
sending ip6 traffic from host connected to vlan200 on ix0 to host
connected to vlan300 on ix1 and running
ifconfig vlan200 destroy
ifconfig ix0 down
sh netstart vlan200
sh netstart ix0
ifconfing vlan300 destroy
ifconfig ix1 down
sh netstart vlan300
sh netstart ix1
sh netstart
triggers pa
On 29.11.2017. 18:25, Hrvoje Popovski wrote:
> hi all,
>
> sending ip6 traffic from host connected to vlan200 on ix0 to host
> connected to vlan300 on ix1 and running
>
> ifconfig vlan200 destroy
> ifconfig ix0 down
> sh netstart vlan200
> sh netstart ix0
> ifconf
On 7.12.2017. 13:07, Martin Pieuchot wrote:
> On 30/11/17(Thu) 12:49, Hrvoje Popovski wrote:
>> On 29.11.2017. 18:25, Hrvoje Popovski wrote:
>>> hi all,
>>>
>>> sending ip6 traffic from host connected to vlan200 on ix0 to host
>>> connected to vlan30
On 7.12.2017. 13:07, Martin Pieuchot wrote:
> Same thing for the em(4) panic you reported before. I made an educated
> guess about which race can occur. But having the trace of all active
> processes help a lot!
hi,
i had to trigger same panic before applying your em diff and here it is:
pani
On 7.12.2017. 12:59, Martin Pieuchot wrote:
> If believe em_init() should only be called if IFF_RUNNING is still set.
>
> If you agree on that we should generalize this fix.
>
> Index: if_em.c
> ===
> RCS file: /cvs/src/sys/dev/pci/i
hi all,
this is what i'm doing in the loop:
ifconfig trunk2 destroy && sh netstart && ifconfig vlan500 destroy &&
ifconfig ix2 down && ifconfig ix2 up && sh netstart && sleep 5 &&
ifconfig vlan400 destroy && ifconfig ix3 down && ifconfig ix3 up && sh
netstart && sleep 5
and while doing that i'm
On 23.1.2018. 15:36, Martin Pieuchot wrote:
> Hello Hrvoje,
>
> On 23/01/18(Tue) 14:33, Hrvoje Popovski wrote:
>> [...]
>> uvm_fault(0x81b23f30, 0xb8, 0, 1) -> e
>
> This is the offset of `if_carp&
Hi all,
I've checkouted cvs tree few minutes ago on desktop pc and enabled
WITNESS. While booting pc with new kernel i'm getting "lock order reversal"
http://kosjenka.srce.hr/~hrvoje/zaprocvat/IMG_20180130_125928.jpg
in ddb i can't do nothing with keyboard
dmesg from obsd
OpenBSD 6.2-current (
On 30.1.2018. 13:34, Martin Pieuchot wrote:
> On 30/01/18(Tue) 13:12, Hrvoje Popovski wrote:
>> Hi all,
>>
>> I've checkouted cvs tree few minutes ago on desktop pc and enabled
>> WITNESS. While booting pc with new kernel i'm getting "lock order rever
On 30.1.2018. 14:18, Hrvoje Popovski wrote:
> On 30.1.2018. 13:34, Martin Pieuchot wrote:
>> On 30/01/18(Tue) 13:12, Hrvoje Popovski wrote:
>>> Hi all,
>>>
>>> I've checkouted cvs tree few minutes ago on desktop pc and enabled
>>> WITNESS. While
On 30.1.2018. 13:34, Martin Pieuchot wrote:
> On 30/01/18(Tue) 13:12, Hrvoje Popovski wrote:
>> Hi all,
>>
>> I've checkouted cvs tree few minutes ago on desktop pc and enabled
>> WITNESS. While booting pc with new kernel i'm getting "lock order rever
Hi,
without BFD, route -nv get 192.168.11.2 shows:
sockaddrs:
192.168.11.2 00:01:e8:8a:ea:53 255.255.255.255 00:25:90:5d:ca:38
192.168.11.1
with BFD (bfd session is up or down, doesn't matter)
route -nv get 192.168.11.2 shows:
sockaddrs:
192.168.11.2 00:01:e8:8a:ea:53 255.255.255.255 00:25:
Hi all,
test box is configured with kern.pool_debug=1 and option MP_LOCKDEBUG.
while sending traffic (9000 byte) over ix interfaces and at the same
time changing mtu on sink interface (ix1) from 9000 to 1500 drops me to
ddb console.
it seems that i can't trigger dropping to ddb console with
kern
On 15.6.2017. 18:43, Hrvoje Popovski wrote:
> Hi all,
>
> test box is configured with kern.pool_debug=1 and option MP_LOCKDEBUG.
it wasn't easy but i managed to get ddb once more :)
root@x3550m4:~
# mmpp__lloocckk((00xx881199dd3311)):: l o c k
sp u
On 19.6.2017. 10:25, Martin Pieuchot wrote:
> On 15/06/17(Thu) 18:43, Hrvoje Popovski wrote:
>> Hi all,
>>
>> test box is configured with kern.pool_debug=1 and option MP_LOCKDEBUG.
>>
>> while sending traffic (9000 byte) over ix interfaces and at the same
>&
On 19.6.2017. 11:23, Martin Pieuchot wrote:
> That means that MP_LOCKDEBUG works the following way:
>
> - Each time you spin on the lock without taking it a counter is increased
> - If this counter reaches the value of __mp_lock_spinout the machine enter
> DDB
>
> So if this value is too sm
Hi all,
with cvs tree (with or without bluhm@ uipc_syscalls patch) fetched few
minutes ago i'm getting panic below. would show witness be of any good?
Setup is quite standard, carp, pf, pfsync, isakmpd
# panic: kernel diagnostic assertion "_kernel_lock_held()" failed: file
"/usr/src/sys/n
On 4.7.2017. 12:33, Martin Pieuchot wrote:
> On 04/07/17(Tue) 01:49, Hrvoje Popovski wrote:
>> Hi all,
>>
>> with cvs tree (with or without bluhm@ uipc_syscalls patch) fetched few
>> minutes ago i'm getting panic below. would show witness be of any good?
>>
&
On 4.7.2017. 13:06, Hrvoje Popovski wrote:
> On 4.7.2017. 12:33, Martin Pieuchot wrote:
>> On 04/07/17(Tue) 01:49, Hrvoje Popovski wrote:
>>> Hi all,
>>>
>>> with cvs tree (with or without bluhm@ uipc_syscalls patch) fetched few
>>> minutes ago i'm
On 4.7.2017. 13:12, Hrvoje Popovski wrote:
> On 4.7.2017. 13:06, Hrvoje Popovski wrote:
>> On 4.7.2017. 12:33, Martin Pieuchot wrote:
>>> On 04/07/17(Tue) 01:49, Hrvoje Popovski wrote:
>>>> Hi all,
>>>>
>>>> with cvs tree (with or without bl
On 4.7.2017. 13:25, Martin Pieuchot wrote:
> On 04/07/17(Tue) 13:12, Hrvoje Popovski wrote:
>> [...]
>> and i'm to quick ..
>>
>> here's panic when killing isakmpd on other box
> My bad, 'locked' should be initialized for every iteration of the
On 14.9.2018. 19:44, Mark Kettenis wrote:
>> Date: Fri, 14 Sep 2018 10:05:34 -0700
>> From: Mike Larkin
>>
>> On Thu, Sep 13, 2018 at 11:17:15AM +0200, Hrvoje Popovski wrote:
>>> Hi all,
>>>
>>> i'm having Fujitsu PRIMERGY RX2530 M4 serve
On 15.9.2018. 19:24, Mike Larkin wrote:
> On Fri, Sep 14, 2018 at 07:44:45PM +0200, Mark Kettenis wrote:
>>> Date: Fri, 14 Sep 2018 10:05:34 -0700
>>> From: Mike Larkin
>>>
>>> On Thu, Sep 13, 2018 at 11:17:15AM +0200, Hrvoje Popovski wrote:
>>>
Hi all,
while testing sasha's "pfsync: avoid a recursion on PF_LOCK" diff i
manage to get panic. first i thought that this panic have something to
do with sasha@ work but i can easily reproduce it on clean -current.
while firewall is under stress and forwarding traffic and i'm doing this
in loop
On 1.10.2018. 14:09, Visa Hankala wrote:
> On Mon, Oct 01, 2018 at 01:50:59PM +0200, Hrvoje Popovski wrote:
>> Hi all,
>>
>> while testing sasha's "pfsync: avoid a recursion on PF_LOCK" diff i
>> manage to get panic. first i thought that this panic have
On 23.10.2018. 21:41, Florian Obser wrote:
> I'm currently on vacation and can't look into this soon.
>
> One thing that comes to mind: do these machines keep proper time or are they
> having issues with timer interrupts stopping because of too new KVM version
> and missing hypervisor flag (some
On 3.6.2018. 13:38, Visa Hankala wrote:
> On Sat, Jun 02, 2018 at 03:08:14PM -0700, Philip Guenther wrote:
>> On Sat, 2 Jun 2018, Christophe Prévotaux wrote:
>>> This a witness report I got on boot with snapshot Jun 1st amd64
>>>
>>> root on sd0a (9b49e3196b9bfae8.a) swap on sd0b dump on sd0b
>>> l
Hi all,
while playing around with stp and pair interfaces and using exactly the
same example as in man (4) pair
ifconfig pair0 up
ifconfig pair1 rdomain 1 patch pair0 up
ifconfig pair2 up
ifconfig pair3 rdomain 1 patch pair2 up
ifconfig bridge0 add pair0 add pair2 stp pair0 stp pair2 up
ifconfig
On 29.3.2019. 15:32, Martin Pieuchot wrote:
> Hello,
>
> On 24/03/19(Sun) 01:00, Hrvoje Popovski wrote:
>> Hi all,
>>
>> while playing around with stp and pair interfaces and using exactly the
>> same example as in man (4) pair
>>
>> ifconfig pair0
On 10.4.2019. 11:19, illya.me...@wiesan.de wrote:
> Am 10.04.19 um 10:58 schrieb Otto Moerbeek:
>> On Wed, Apr 10, 2019 at 10:08:51AM +0200, illya.me...@wiesan.de wrote:
>>
>>>
>>> Am 10.04.19 um 07:34 schrieb Bruno Flückiger:
On 09.04., illya.me...@wiesan.de wrote:
> Dear all,
>
>
Hi all,
While opensbd box is under pressure and in that moment i run ifconfig
bnxt0 down i get panic... it's not every time and it's that easy to
trigger panic
I'm sending traffic over ix interfaces and bnxt is for ssh and nothing
else.
I've compiled kernel with "option BNXT_DEBUG" and put debug
On 16.3.2022. 20:00, Hrvoje Popovski wrote:
> Hi all,
>
> While opensbd box is under pressure and in that moment i run ifconfig
> bnxt0 down i get panic... it's not every time and it's that easy to
> trigger panic
>
> I'm sending traffic over ix interfaces an
On 17.3.2022. 21:31, Alexander Bluhm wrote:
> I don't have the device and don't know the code. But other drivers
> don't process rx and tx interrupts when the interface is not running.
>
> Maybe this helps. dlg@ and jmatthew@ should know better than me.
>
> bluhm
Hi,
i didn't manage to trigge
On 18.3.2022. 18:59, Alexander Bluhm wrote:
> On Fri, Mar 18, 2022 at 11:21:15AM +0100, Hrvoje Popovski wrote:
>> On 17.3.2022. 21:31, Alexander Bluhm wrote:
>>> I don't have the device and don't know the code. But other drivers
>>> don't process rx a
On 9.5.2022. 22:04, Alexander Bluhm wrote:
> Can some veb or smr hacker explain how this is supposed to work?
>
> Sleeping in pf is also not ideal as it is in the hot path and slows
> down packets. But that is not easy to fix as we have to refactor
> the memory allocations before converting pf lo
On 10.5.2022. 22:55, Alexander Bluhm wrote:
> Yes. It is similar.
>
> I have read the whole mail thread and the final fix got commited.
> But it looks incomplete, pf is still sleeping.
>
> Hrvoje, can you run the tests again that triggered the panics a
> year ago?
Hi,
year ago panics was trigg
On 12.5.2022. 14:48, Claudio Jeker wrote:
> I think the diff below may be enough to fix this issue. It drops the SMR
> critical secition around the enqueue operation but uses a reference on the
> port insteadt to ensure that the device can't be removed during the
> enqueue. Once the enqueue is fini
On 12.5.2022. 16:22, Hrvoje Popovski wrote:
> On 12.5.2022. 14:48, Claudio Jeker wrote:
>> I think the diff below may be enough to fix this issue. It drops the SMR
>> critical secition around the enqueue operation but uses a reference on the
>> port insteadt to ensure tha
On 12.5.2022. 20:04, Hrvoje Popovski wrote:
> On 12.5.2022. 16:22, Hrvoje Popovski wrote:
>> On 12.5.2022. 14:48, Claudio Jeker wrote:
>>> I think the diff below may be enough to fix this issue. It drops the SMR
>>> critical secition around the enqueue operation
On 13.5.2022. 4:19, David Gwynne wrote:
> sorry i'm late to the party. can you try this diff?
>
> this diff replaces the list of ports with an array/map of ports.
> the map takes references to all the ports, so the forwarding paths
> just have to hold a reference to the map to be able to use all t
Hi all,
I can reproduce panic when sending ip6 traffic over vport and destroying
pfsync interface. It is reproducible with veb and vport but i couldn't
trigger panic when forwarding ip6 over physical interfaces.
I've compiled kernel with source fetched half an hour ago just to enable
WITNESS.
r6
On 23.5.2022. 8:34, Alexandr Nedvedicky wrote:
> looks like kind of memory corruption. my bet is use-after-free.
> will try to get to it later today.
>
> does it mean there is no such panic, when we handle IPv4 traffic only?
Hi,
yes, it seems that i can't trigger panic with ip4 only
On 23.5.2022. 10:41, Hrvoje Popovski wrote:
> On 23.5.2022. 8:34, Alexandr Nedvedicky wrote:
>> looks like kind of memory corruption. my bet is use-after-free.
>> will try to get to it later today.
>>
>> does it mean there is no such panic, when we handle
On 23.5.2022. 10:41, Hrvoje Popovski wrote:
> On 23.5.2022. 8:34, Alexandr Nedvedicky wrote:
>> looks like kind of memory corruption. my bet is use-after-free.
>> will try to get to it later today.
>>
>> does it mean there is no such panic, when we handle
On 24.5.2022. 9:01, Alexandr Nedvedicky wrote:
> interesting. I went through mbuf handling in if_veb.c
> I just could find a single nit, which is most likely unrelated,
> however I think it's still worth to give it a try a diff below.
>
> basically all calls to veb_pf() read as fol
On 1.6.2022. 0:27, Stuart Henderson wrote:
> I accidentally updated a router to -current instead of 7.1 and hit this.
> (Thanks sysupgrade - it was running a 7.0-stable kernel before...)
>
> Unfortunately it runs with ddb.panic=0 and this time it hanged, I won't
> have time to figure anything out
Hi all,
while playing around with TCP Large Receive Offloading for ix I have
configure httpd and relayd on test box.
Same second I've start relayd box panic.
This is latest snapshot and it easely reproduciable..
r420-1# cat /etc/httpd.conf
prefork 4
server "default" {
listen on 127.0.0.
On 1.6.2022. 7:01, Hrvoje Popovski wrote:
> Hi all,
>
> while playing around with TCP Large Receive Offloading for ix I have
> configure httpd and relayd on test box.
> Same second I've start relayd box panic.
> This is latest snapshot and it easely reproduciable..
With WI
On 1.6.2022. 9:16, Alexandr Nedvedicky wrote:
> Hello,
>
>
>> r420-1# rcctl -f start relayd
>> relayd(ok)
>> r420-1# uvm_fault(0xfd862f82f990, 0x0, 0, 1) -> e
>> kernel: page fault trap, code=0
>> Stopped at pf_find_or_create_ruleset+0x1c: movb0(%rdi),%al
>> TIDPIDUID
Hi,
this is follow up mail from
https://marc.info/?l=openbsd-tech&m=165450511622133&w=2
panic log:
bcbnfw1# uvm_fault(0x822e5e48, 0x0, 0, 1) -> e
kernel: page fault trap, code=0
Stopped at pf_state_export+0x38: movq0(%rax),%rcx
TIDPIDUID PRFLAGS PFLAGS CPU
On 6.6.2022. 12:45, Alexandr Nedvedicky wrote:
> this is most likely identical to crash you've reported ?two weeks ago?
> I can not find an email with it.
oh yes, yes it's on tech@ with subject
pf_state_export panic with NET_TASKQ=6 and stuff
i've totally forgot about that report :)
On 7.6.2022. 2:16, Alexandr Nedvedicky wrote:
> Hello,
>
> below is a diff which hopes to fix the issue. Although diff is fairly
> large the change itself is kind of straightforward. Let me briefly
> explain what's going on here. Diff introduces a mutex to pf_state,
> which protects array of keys
On 8.6.2022. 0:42, Alexandr Nedvedicky wrote:
> Hello Hrvoje,
>
>
>> Hi,
>>
>> while booting with this diff I've got this log:
>>
>> starting early daemons: syslogd pflogd ntpdwitness: lock_object
>> uninitialized: 0xfd8785c81a
>> 90
>> Starting stack trace...
>> witness_checkorder(fd8785
On 8.6.2022. 7:33, Hrvoje Popovski wrote:
> On 8.6.2022. 0:42, Alexandr Nedvedicky wrote:
>> Hello Hrvoje,
>>
>>
>>> Hi,
>>>
>>> while booting with this diff I've got this log:
>>>
>>> starting early daemons: syslogd pfl
On 17.3.2022. 21:31, Alexander Bluhm wrote:
> On Thu, Mar 17, 2022 at 01:01:11AM +0100, Hrvoje Popovski wrote:
>> On 16.3.2022. 20:00, Hrvoje Popovski wrote:
>>> Hi all,
>>>
>>> While opensbd box is under pressure and in that moment i run ifconfig
>>>
Hi all,
Chris Cappuccio kindly asked me if I can reproduce his PF NAT problem in
lab.
His mail:
On my NAT cluster I recently switched from nat-to source-hash $key to
nat-to round-robin and started getting hangs. The boxes would hang where
the network would stop responding and one core would be at
Hi all,
I have supermicro server with usb
ure0: RTL8153 (0x5c30), address 00:e0:4b:68:84:de
used for ssh and management.
When doing ifconfig ure0 down / up I always getting this error
smc24# ifconfig ure0 down
smc24# ifconfig ure0 up
smc24# ure0: usb errors on rx: IOERROR
ure0: usb error on tx:
On 17.7.2022. 20:19, Alexandr Nedvedicky wrote:
> So in case 49/27 we are supposed to be selecting addresses:
> 49.0.0.1, 49.0.0.2, ..., 49.0.0.30, 49.0.0.1
> we need to make sure selection mechanism skips network
> address (49.0.0.0) and network broadcast address (49.0.0.31).
Hi,
I'm I under
On 18.7.2022. 10:40, Alexandr Nedvedicky wrote:
> hello,
>
> On Sun, Jul 17, 2022 at 11:52:21PM +0200, Hrvoje Popovski wrote:
>> On 17.7.2022. 20:19, Alexandr Nedvedicky wrote:
>>> So in case 49/27 we are supposed to be selecting addresses:
>>> 49.0.0.1, 4
Hi all,
I'm running
OpenBSD 7.2-beta (GENERIC.MP) #651: Tue Jul 26 23:11:26 MDT 2022
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
on production firewall and for few weeks it was stable. Firewall panic
today and I will sysupgrade it, but maybe this panic message is
inte
Hi all,
when sending lot of traffic over firewall with pflow and if I run
ifconfig pflow0 destroy I'm getting kernel: protection fault trap.
This is latest snapshot:
OpenBSD 7.2-beta (GENERIC.MP) #677: Mon Aug 8 18:58:49 MDT 2022
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GEN
On 9.8.2022. 19:56, Alexandr Nedvedicky wrote:
> this is a NULL pointer dereference panic. I think we've seen it few months
> back. patch below was applied to one of your test machines if I remember
> correct. can you give it a try again to see if it will help?
>
> the change adds
On 9.8.2022. 22:22, Vitaliy Makkoveev wrote:
> Hi,
>
> The kernel lock within pflow_output_process() doesn't help because the
> following sosend() has sleep points. So, at least pflow_clone_destroy()
> should wait until pflow_output_process() finished. We should use
> taskq_del_barrier(9) instead
On 10.8.2022. 0:49, Vitaliy Makkoveev wrote:
> That's strange, because after we the only timeout handlers can reschedule
> pflow_output_process to run, but they have no sleep points. However the
> task handler still running after taskq_del_barrier(9).
>
> Does this help?
Hi,
this diff doesn't he
On 10.8.2022. 15:44, Vitaliy Makkoveev wrote:
> On Wed, Aug 10, 2022 at 12:52:06AM +0200, Hrvoje Popovski wrote:
>> On 9.8.2022. 22:22, Vitaliy Makkoveev wrote:
>>> Hi,
>>>
>>> The kernel lock within pflow_output_process() doesn't help because the
>&g
Hi all,
if i have bridge with rstp on interfaces and rstp on switch and i want
to disable rstp on openbsd interfaces i'm getting fault trap. I can
reproduce it on 6.4 and on -current.
i can't reproduce it if i don't have rstp on switch.
without stp:
ifconfig bridge0
bridge0: flags=41
inde
On 30.4.2019. 14:45, Hrvoje Popovski wrote:
> Hi all,
>
> if i have bridge with rstp on interfaces and rstp on switch and i want
> to disable rstp on openbsd interfaces i'm getting fault trap.
i suck so much at describing the problem
problem is executing "ifconfig b
On 30.4.2019. 23:40, Martin Pieuchot wrote:
> On 30/04/19(Tue) 14:45, Hrvoje Popovski wrote:
>> Hi all,
>>
>> if i have bridge with rstp on interfaces and rstp on switch and i want
>> to disable rstp on openbsd interfaces i'm getting fault trap. I can
>> rep
On 3.5.2019. 13:32, Alexander Bluhm wrote:
> On Fri, May 03, 2019 at 12:15:44PM +0200, Alexander Bluhm wrote:
>> 0 3082 39335 10 10 0 304 232 ifidxrm D+p00:00.00
>> /sbin/ifconfig bridge12 destroy
> Looks like a missing if_put().
Hi,
with this diff i can't reproduce panic wi
Hi all,
for testing MP network diffs i'm using some intrusive commands in loop
while sending traffic through openbsd box, leave loop to run and after
some time something will happen or not :)
few days ago by accident i run same loop twice and got various panics
and page faults... with one loop ev
Hi all,
i'm having samba server, transmission client and gnome desktop on one
box. from time to time i'm getting witness log below. source is clean
and fetched few hours ago and compiled with WITNESS. userland and
packages are up to date ..
i put kern.witness.watch=3 in sysctl.conf so now i'm in d
On 3.6.2019. 18:32, Philip Guenther wrote:
> On Mon, 3 Jun 2019, Hrvoje Popovski wrote:
>> i'm having samba server, transmission client and gnome desktop on one
>> box. from time to time i'm getting witness log below. source is clean
>> and fetched few hours ago and
On 4.6.2019. 16:38, Otto Moerbeek wrote:
> On Tue, Jun 04, 2019 at 03:41:02PM +0200, Hrvoje Popovski wrote:
>
>> Hi all,
>>
>> after upgrading Fujitsu RX 2530 M4 from 6.4 to 6.5 in dmesg i saw
>> "Segmentation fault (core dumped)" instead of "settin
On 4.6.2019. 16:54, Otto Moerbeek wrote:
> On Tue, Jun 04, 2019 at 04:50:28PM +0200, Hrvoje Popovski wrote:
>
>> On 4.6.2019. 16:38, Otto Moerbeek wrote:
>>> On Tue, Jun 04, 2019 at 03:41:02PM +0200, Hrvoje Popovski wrote:
>>>
>>>> Hi all,
>>>&g
On 4.6.2019. 17:47, Otto Moerbeek wrote:
> Any idea how you ended up with this malformed file?
No, i simply don't know how that happened ...
On 23.7.2019. 17:03, obs...@high5.nl wrote:
>> Synopsis:ifconfig bridge crashes host
>> Category:
>> Environment:
> System : OpenBSD 6.5
> Details : OpenBSD 6.5 (GENERIC.MP) #1: Mon May 27 18:27:59 CEST 2019
>
> r...@syspatch-65-amd64.openbsd.org
1 - 100 of 141 matches
Mail list logo
