I think I might have stumbled across a bug in ospfd, where it's possible for it
to forget the mapping between OSPF external tags and routing labels defined in
it's config file.
It's possible to reproduce in various network configurations by restarting
ospfd on individual routers, but a minimal
> From: Dave Voutila
> Date: Wed, 05 Jun 2024 14:56:45 -0400
>
> >Synopsis: witness panic: acquiring blockable sleep lock with spinlock
>or critical section held (rwlock) vmmaplk
> >Category:
> >Environment:
> System : OpenBSD 7.5
> Details : OpenBSD
I witnessed a lock order reversal with vnd(4) on macppc and powerpc64.
I can't reproduce it on amd64.
Build a GENERIC.MP kernel with option WITNESS, boot it, then configure
and fdisk a vnd. The lock order reversal happens during fdisk,
# dd if=/dev/zero of=img bs=1m count=1
# vnconfig -v vnd0
> There's a corruption...
>
> > ddb{7}> show panic
> > cpu6: kernel diagnostic assertion "((flags & PGO_LOCKED) != 0 &&
> > rw_lock_held(
> > uobj->vmobjlock)) || (flags & PGO_LOCKED) == 0" failed: file
> > "/sys/uvm/uvm_vnod
> > e.c", line 953
> >
> > *cpu7: assertwaitok: non-zero mutex
>Synopsis: witness panic: acquiring blockable sleep lock with spinlock
or critical section held (rwlock) vmmaplk
>Category:
>Environment:
System : OpenBSD 7.5
Details : OpenBSD 7.5-current (GENERIC.MP) #5: Wed Jun 5 20:07:42
CEST 2024
On Wed, 05 Jun 2024 19:09:58 +0100,
Theo Buehler wrote:
>
> On Wed, Jun 05, 2024 at 07:00:05PM +0100, kir...@korins.ky wrote:
> > >Synopsis: fatal error: 'ufshci.h' file not found
> > >Category: kernel
> > >Environment:
> > System : OpenBSD 7.5
> > Details : OpenBSD
On Wed, Jun 05, 2024 at 07:00:05PM +0100, kir...@korins.ky wrote:
> >Synopsis:fatal error: 'ufshci.h' file not found
> >Category:kernel
> >Environment:
> System : OpenBSD 7.5
> Details : OpenBSD 7.5-current (GENERIC.MP) #112: Tue Jun 4
> 21:00:07 MDT 2024
>
>Synopsis: fatal error: 'ufshci.h' file not found
>Category: kernel
>Environment:
System : OpenBSD 7.5
Details : OpenBSD 7.5-current (GENERIC.MP) #112: Tue Jun 4
21:00:07 MDT 2024
George, thank you for the suggestion of changing membar_enter and
membar_consumer
from isync to sync. I did that and the frequency of crashes went way
down, admittedly on
a workload that is not solidly reproducible. But last night there was
finally another crash (see below)
so that's not the full
>Synopsis: double-free in ld.lld
>Category: compiler
>Environment:
System : OpenBSD 7.5
Details : OpenBSD 7.5-current (GENERIC.MP) #141: Mon Jun 3
16:33:28 WEST 2024
catap@matebook.local:/usr/src/sys/arch/amd64/compile/GENERIC.MP
On Mon, Jun 03, 2024 at 01:18:07PM +0200, Jeremie Courreges-Anglas wrote:
> On Mon, Jun 03, 2024 at 12:20:06PM +0200, Martin Pieuchot wrote:
> > Now that the SCHED_LOCK() is a mutex I see the following WITNESS report
> > on arm64.
>
> IIUC Claudio has proposed a diff for this, see your mails:
>
On Mon, Jun 03, 2024 at 12:20:06PM +0200, Martin Pieuchot wrote:
> Now that the SCHED_LOCK() is a mutex I see the following WITNESS report
> on arm64.
IIUC Claudio has proposed a diff for this, see your mails:
arm64: pmap ASID generation without SCHED_LOCK
--
jca
Now that the SCHED_LOCK() is a mutex I see the following WITNESS report
on arm64.
witness: lock order reversal:
1st 0xff80012486e8 /usr/src/sys/dev/rnd.c:321 (/usr/src/sys/dev/rnd.c:321)
2nd 0xff800120afb0 /usr/src/sys/kern/kern_timeout.c:57
(/usr/src/sys/kern/kern_timeout.c:57)
lock
Hi,
Here at Srce we are running OpenBSD 7.5-release as route server. I
wanted to collect some additional MRT data and I have this in bgpd.conf
dump table-v2 "/data/bgpdumps/bgp-rib-dump-%y_%m_%d-%H_%M" 300
dump all out "/data/bgpdumps/bgp-all-out-%y_%m_%d-%H_%M" 300
dump all in
And committed, will be in 7.6
Thanks,
-Otto
On Sun, Jun 02, 2024 at 08:32:28AM -0500, Don Wilburn wrote:
> Oops. I'll try sending this to the bugs list for posterity.
>
> Thanks again, DW
>
>
> On 6/2/24 3:22 AM, Otto Moerbeek wrote:
> > Thanks, but please reply to the list.
> >
Thanks Stefan for the quick answer!
I have been running with the 7265-17 image for two days and the problem
hasn't showed up. I'll keep you posted if it comes back in the next few days.
On Thu, May 30, 2024 at 12:15:26PM +0200, Stefan Sperling wrote:
> On Thu, May 30, 2024 at 09:55:00AM +0200,
Oops. I'll try sending this to the bugs list for posterity.
Thanks again, DW
On 6/2/24 3:22 AM, Otto Moerbeek wrote:
Thanks, but please reply to the list.
-Otot
On Sat, Jun 01, 2024 at 09:25:26PM -0500, Don Wilburn wrote:
Thank you Otto!
I followed your advice and successfully
Le 02/06/2024 à 16:07, Matthieu Herrb a écrit :
On Sat, Jun 01, 2024 at 09:40:48PM +0200, Sacha wrote:
Le 01/06/2024 à 14:04, Matthieu Herrb a écrit :
On Sat, Jun 01, 2024 at 11:57:35AM +0200, Sacha wrote:
Dear list,
We have a performance issue impacting all our infrastructure behind our
On Sat, Jun 01, 2024 at 09:40:48PM +0200, Sacha wrote:
> Le 01/06/2024 à 14:04, Matthieu Herrb a écrit :
> > On Sat, Jun 01, 2024 at 11:57:35AM +0200, Sacha wrote:
> > > Dear list,
> > >
> > > We have a performance issue impacting all our infrastructure behind our
> > > OpenBSD: two front
Hi all,
in lab I have 2 socket box with lot of interfaces, ix, ixl, mcx, bnxt,
em and bge. When sending high traffic over mcx whole machine is almost
unresponsive, like sending any command over console. In that state
pagedaemon is at 100% sometimes ever higher and mcl12k Fail counter is
rising.
>Synopsis: xfontsel segmentation faults with -pattern
>Category: user
>Environment:
System : OpenBSD 7.5
Details : OpenBSD 7.5-current (GENERIC.MP) #98: Thu May 30 21:14:11
MDT 2024
Synopsis: cwm: X selections cannot be pasted into menus
Category: user
Environment:
System : OpenBSD 7.5
Details : OpenBSD 7.5 (GENERIC.MP) #82: Wed Mar 20 15:48:40 MDT 2024
Le 01/06/2024 à 14:04, Matthieu Herrb a écrit :
On Sat, Jun 01, 2024 at 11:57:35AM +0200, Sacha wrote:
Dear list,
We have a performance issue impacting all our infrastructure behind our
OpenBSD: two front BGP/CARP routers with 1Gb/s transit. It seams to occur
since we have upgraded to 7.5,
Otto Moerbeek wrote:
> On Wed, May 29, 2024 at 08:05:14AM +0200, Otto Moerbeek wrote:
>
> > On Mon, May 27, 2024 at 09:21:34PM -0500, Don Wilburn wrote:
> >
> > > Dear OpenBSD,
> > >
> > > I recently upgraded from version 7.4 to 7.5. This broke the old cribbage
> > > game. This is included
On Wed, May 29, 2024 at 08:05:14AM +0200, Otto Moerbeek wrote:
> On Mon, May 27, 2024 at 09:21:34PM -0500, Don Wilburn wrote:
>
> > Dear OpenBSD,
> >
> > I recently upgraded from version 7.4 to 7.5. This broke the old cribbage
> > game. This is included with OpenBSD, if you choose to install
On Sat, Jun 01, 2024 at 11:57:35AM +0200, Sacha wrote:
> Dear list,
>
> We have a performance issue impacting all our infrastructure behind our
> OpenBSD: two front BGP/CARP routers with 1Gb/s transit. It seams to occur
> since we have upgraded to 7.5, both of the servers are up to date.
Hi
Dear list,
We have a performance issue impacting all our infrastructure behind our
OpenBSD: two front BGP/CARP routers with 1Gb/s transit. It seams to
occur since we have upgraded to 7.5, both of the servers are up to date.
A simple ssh (without login) on our the router have notable
On Thu, 30 May 2024 13:11:41 -0700
Eric Grosse wrote:
> ddb{7}> show panic
>
> cpu6: kernel diagnostic assertion "((flags & PGO_LOCKED) != 0 &&
> rw_lock_held(
> uobj->vmobjlock)) || (flags & PGO_LOCKED) == 0" failed: file
> "/sys/uvm/uvm_vnod
> e.c", line 953
>
> *cpu7: assertwaitok:
On 30/05/24(Thu) 13:11, Eric Grosse wrote:
> And, fairly quickly, another one. The load depends on what's in the Go
> team build queue, which is not under my control.To avoid further
> spamming the list I won't report any more of these until I can get
> something reproducible under my control. Of
And, fairly quickly, another one. The load depends on what's in the Go
team build queue, which is not under my control.To avoid further
spamming the list I won't report any more of these until I can get
something reproducible under my control. Of course, anyone interested
may contact me directly
openbsd-ppc64-n2vi got another crash:
UVM_PSEG_INUSE failed uvm_pager.c:227
panic
uvm_pseg_release
uvn_io
uvn_get
uvm_fault_lower
uvm_fault
trap
trapagain
type 300
during a bunch of go compiles.
On Mon, May 27, 2024 at 5:34 PM Jeremie Courreges-Anglas
wrote:
>
> On Sat, May 25, 2024 at
On Thu, May 30, 2024 at 09:55:00AM +0200, a...@alexis-fouilhe.fr wrote:
> >Synopsis:iwm frequent 'device timeout' error
> >Category:kernel
> >Environment:
> System : OpenBSD 7.5
> Details : OpenBSD 7.5 (GENERIC.MP) #55: Mon Mar 4 21:59:07 MST 2024
>
>Synopsis: iwm frequent 'device timeout' error
>Category: kernel
>Environment:
System : OpenBSD 7.5
Details : OpenBSD 7.5 (GENERIC.MP) #55: Mon Mar 4 21:59:07 MST 2024
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
On Mon, May 27, 2024 at 09:21:34PM -0500, Don Wilburn wrote:
> Dear OpenBSD,
>
> I recently upgraded from version 7.4 to 7.5. This broke the old cribbage
> game. This is included with OpenBSD, if you choose to install the games.
>
> I'm not a programmer, but I promise you this happened
On Mon, May 27, 2024 at 09:21:34PM -0500, Don Wilburn wrote:
> Dear OpenBSD,
>
> I recently upgraded from version 7.4 to 7.5. This broke the old cribbage
> game. This is included with OpenBSD, if you choose to install the games.
>
> I'm not a programmer, but I promise you this happened because
Dear OpenBSD,
I recently upgraded from version 7.4 to 7.5. This broke the old
cribbage game. This is included with OpenBSD, if you choose to install
the games.
I'm not a programmer, but I promise you this happened because ncurses
was updated from version 5.7 to 6.4
The problem:
On Sat, May 25, 2024 at 12:35:16AM -0400, George Koehler wrote:
> On Tue, 21 May 2024 03:08:49 +0200
> Jeremie Courreges-Anglas wrote:
>
> > On Tue, May 21, 2024 at 02:51:39AM +0200, Jeremie Courreges-Anglas wrote:
> > > This doesn't look powerpc64-specific. It feels like
> > >
>Synopsis: Excessively kernel spinlock and slow performance on arm64 under
UTM hypervisor
>Category: aarch64
>Environment:
System : OpenBSD 7.5
Details : OpenBSD 7.5-current (GENERIC.PROF) #0: Sat May 25 22:30:52
EST 2024
Hello,
probably mail(1) should always wait for sendmail(8) termination in order to
prevent any possible sendmail error messages from being intermixed with
subsequent terminal output.
---
usr.bin/mail/send.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git
Hello,
sendmail(8) usually prints an extraneous newline after an (E)SMTP error
message, here's a patch:
---
usr.sbin/smtpd/enqueue.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/usr.sbin/smtpd/enqueue.c b/usr.sbin/smtpd/enqueue.c
index 51616d0d590..70a25e4a1f0 100644
On Tue, 21 May 2024 03:08:49 +0200
Jeremie Courreges-Anglas wrote:
> On Tue, May 21, 2024 at 02:51:39AM +0200, Jeremie Courreges-Anglas wrote:
> > This doesn't look powerpc64-specific. It feels like
> > uvm_km_kmemalloc_pla() should call pmap_enter() with PMAP_CANFAIL and
> > unwind in case of
TCP_SACK is not a kernel option any more:
https://github.com/openbsd/src/commit/48ef9290235556f3a8883a80191c0cdca60ca4c1
diff --git a/share/man/man4/tcp.4 b/share/man/man4/tcp.4
index 6fe07e310d7..1e4a34e0a68 100644
--- a/share/man/man4/tcp.4
+++ b/share/man/man4/tcp.4
@@ -159,8 +159,6 @@ Set
>Synopsis: tcp man page references missing information
>Category: documentation
>Environment:
System : OpenBSD 7.5
Details : OpenBSD 7.5 (GENERIC.MP) #138: Wed Mar 20 19:42:15 MDT
2024
Hi,
Just a heads up I was working on UART console of a raspberry pi and needed to
xmodem a file to it, something went wrong and it caused the session to log out.
I had to relog on.
Much later I saw a login.core file in /, meaning the compressed tarball, had
some overflow on login(1) causing the
With USB audio I get very frequent disconnects which I am mostly able to
solve by reissuing:
```
$ sndioctl server.device=1
```
and audio starts working again nicely.
However, sometimes this isn't enough and I have to try switching to
another device and then back to the one I want:
```
$
Kirill A. Korinsky writes:
> On Tue, 21 May 2024 18:38:39 +0100,
> Dave Voutila wrote:
>>
>> Can you reproduce this and get details on which process panics? It's not
>> clear what the vm cpu usage has to do with this panic, if anything.
>
> I'll try. May you suggest that command / output can
On Tue, 21 May 2024 18:38:39 +0100,
Dave Voutila wrote:
>
> Can you reproduce this and get details on which process panics? It's not
> clear what the vm cpu usage has to do with this panic, if anything.
I'll try. May you suggest that command / output can be useful in the case
I've reproduced
Kirill A. Korinsky writes:
> Hi,
>
> I've removed to related quotes
>
> On Tue, 21 May 2024 18:09:15 +0100,
> Dave Voutila wrote:
>>
>>
>> kir...@korins.ky writes:
>>
>> >
>> >My machine had an uptime for about a day with a lot of zzz between
>> > active session of using it. When I've
Hi,
I've removed to related quotes
On Tue, 21 May 2024 18:09:15 +0100,
Dave Voutila wrote:
>
>
> kir...@korins.ky writes:
>
> >
> > My machine had an uptime for about a day with a lot of zzz between
> > active session of using it. When I've restarted VM with alpine linux
> > to
kir...@korins.ky writes:
>>Synopsis: Start VM leads to increased CPU usage and crash at the end
>>Category: vmd
>>Environment:
> System : OpenBSD 7.5
> Details : OpenBSD 7.5-current (GENERIC.MP) #138: Mon May 20
> 17:02:52 WEST 2024
>
>
>Synopsis: Start VM leads to increased CPU usage and crash at the end
>Category: vmd
>Environment:
System : OpenBSD 7.5
Details : OpenBSD 7.5-current (GENERIC.MP) #138: Mon May 20
17:02:52 WEST 2024
The -stable version "crash1" was reproducible almost every run; each
run is about an hour on this 8-processor Power9 running a load average
about 30. The -current version "crash2" has only happened once so far,
though because of other issues (hitting a user process limit of 126)
it was failing
On Tue, May 21, 2024 at 02:51:39AM +0200, Jeremie Courreges-Anglas wrote:
> On Sat, May 18, 2024 at 01:11:56PM -0700, Eric Grosse wrote:
> > The openbsd-ppc64-n2vi Go builder machine is converting over to LUCI
> > build infrastructure and the new workload may have stepped on a
> > pagedaemon
On Sat, May 18, 2024 at 01:11:56PM -0700, Eric Grosse wrote:
> The openbsd-ppc64-n2vi Go builder machine is converting over to LUCI
> build infrastructure and the new workload may have stepped on a
> pagedaemon corner case. While running 7.5-stable I reproducibly get
> kernel panics "pmap_enter:
Martin Pieuchot writes:
> The traces all point to a use-after-free in a mbuf that has been through
> the wg(4) machinery. The fact that using a SP system makes the crash
> disappear
The crashes I see happen consistently on both SP and MP systems (vmm and
not-vmm).
On Mon, May 20, 2024 at 11:53:26AM +0200, Martin Pieuchot wrote:
> On 19/05/24(Sun) 23:50, Vitaliy Makkoveev wrote:
> >
> >
> > > On 19 May 2024, at 22:05, Anthony J. Bentley wrote:
> > >
> > > Vitaliy Makkoveev writes:
> > >>> On 17 May 2024, at 12:06, Stuart Henderson =
> > >> wrote:
> >
On 19/05/24(Sun) 23:50, Vitaliy Makkoveev wrote:
>
>
> > On 19 May 2024, at 22:05, Anthony J. Bentley wrote:
> >
> > Vitaliy Makkoveev writes:
> >>> On 17 May 2024, at 12:06, Stuart Henderson =
> >> wrote:
> >>> =20
> >>> There are problems with wg(4) that people with some workloads have =
>
Anthony J. Bentley writes:
> Vitaliy Makkoveev writes:
> > This could be vio(4) bug. Please try this [1] diff.
> >
> > 1. https://marc.info/?l=3Dopenbsd-tech=3D171588941332420=3D2
>
> I'll try the diff, but note that before I moved this setup to a VM
> all these crashes were occurring on em(4).
Vitaliy Makkoveev writes:
> This could be vio(4) bug. Please try this [1] diff.
>
> 1. https://marc.info/?l=3Dopenbsd-tech=3D171588941332420=3D2
I'll try the diff, but note that before I moved this setup to a VM
all these crashes were occurring on em(4).
> On 19 May 2024, at 22:05, Anthony J. Bentley wrote:
>
> Vitaliy Makkoveev writes:
>>> On 17 May 2024, at 12:06, Stuart Henderson =
>> wrote:
>>> =20
>>> There are problems with wg(4) that people with some workloads have =
>> been
>>> seeing after upgrading past 7.3, though looking at this
Vitaliy Makkoveev writes:
> > On 17 May 2024, at 12:06, Stuart Henderson =
> wrote:
> >=20
> > There are problems with wg(4) that people with some workloads have =
> been
> > seeing after upgrading past 7.3, though looking at this thread from =
> when
> > it last came up
> On 17 May 2024, at 21:03, Vitaliy Makkoveev wrote:
>
> https://marc.info/?l=openbsd-bugs=170980835807159=2
Following dt(4) script could also be useful with this diff.
tracepoint:refcnt:wg_peer {
printf("%s %x %u %+d%s", probe, arg0, arg1, arg2, kstack)
}
> On 17 May 2024, at 12:06, Stuart Henderson wrote:
>
> There are problems with wg(4) that people with some workloads have been
> seeing after upgrading past 7.3, though looking at this thread from when
> it last came up https://marc.info/?t=17094089271=1=2 I'm not
> sure if we'd be
There are problems with wg(4) that people with some workloads have been
seeing after upgrading past 7.3, though looking at this thread from when
it last came up https://marc.info/?t=17094089271=1=2 I'm not
sure if we'd be expecting to see trouble on non-MP...
On 2024/05/17 00:55, Anthony J.
Hi,
This week I updated a machine from 7.3 to 7.5. Almost immediately it
started panicking constantly. The machine runs a webserver on a wg(4)
interface and receives a mild amount of traffic. I turned off
wireguard, moved the wg config to a vmm(4) virtual machine, and
immediately the host stopped
On Thu, May 16, 2024 at 07:48:55PM +, bsmnt wrote:
> Hello OpenBSD Team
> First of all I’d like to express my thankfulness for your job and sacrifices
> in order to make system we love that much !
>
> Last time I’ve spot the problem I can’t proces by myself through 2 weeks.
> I’ve made a
Hello OpenBSD Team
First of all I’d like to express my thankfulness for your job and sacrifices in
order to make system we love that much !
Last time I’ve spot the problem I can’t proces by myself through 2 weeks.
I’ve made a successful upgrade from 7.4 to 7.5 and everything works fine except
hello,
On 2024-05-16 16:14, Claudio Jeker wrote:
> On Thu, May 16, 2024 at 10:00:20AM -0400, Johan Huldtgren wrote:
> > hello,
>
> Removed a lot of text to keep this under control.
>
> > > > > >> > Relevant configs:
> > > > > >> >
> > > > > >> > # host (OpenBSD 7.5 + syspatches)
> > > > > >> >
On Thu, May 16, 2024 at 10:00:20AM -0400, Johan Huldtgren wrote:
> hello,
Removed a lot of text to keep this under control.
> > > > >> > Relevant configs:
> > > > >> >
> > > > >> > # host (OpenBSD 7.5 + syspatches)
> > > > >> >
> > > > >> > $ doas cat /etc/vm.conf
> > > > >> > vm "guest.vm" {
>
Florian Obser writes:
> On 2024-05-16 09:42 -04, Dave Voutila wrote:
>> Johan Huldtgren writes:
>>
>>> hello,
>>>
>>> On 2024-05-16 8:14, Dave Voutila wrote:
Johan Huldtgren writes:
>>> $ doas cat /etc/hostname.vio0
>>> inet autoconf
>>>
>>> # /bin/sh /etc/netstart vio0
>>>
hello,
On 2024-05-16 15:06, Claudio Jeker wrote:
> On Thu, May 16, 2024 at 08:52:24AM -0400, Johan Huldtgren wrote:
> > hello,
> >
> > On 2024-05-16 8:14, Dave Voutila wrote:
> > >
> > > Johan Huldtgren writes:
> > >
> > > > hello,
> > > >
> > > > On 2024-05-15 17:31, Dave Voutila wrote:
> >
On 2024-05-16 09:42 -04, Dave Voutila wrote:
> Johan Huldtgren writes:
>
>> hello,
>>
>> On 2024-05-16 8:14, Dave Voutila wrote:
>>>
>>> Johan Huldtgren writes:
>> $ doas cat /etc/hostname.vio0
>> inet autoconf
>>
>> # /bin/sh /etc/netstart vio0
>> ifconfig: autoconf not allowed for this AF
>>
Johan Huldtgren writes:
> hello,
>
> On 2024-05-16 8:14, Dave Voutila wrote:
>>
>> Johan Huldtgren writes:
>>
>> > hello,
>> >
>> > On 2024-05-15 17:31, Dave Voutila wrote:
>> >>
>> >> Johan Huldtgren writes:
>> >>
>> >> >> Synopsis: vmm guest does not get IP after upgrade to 7.5
>> >>
On Thu, May 16, 2024 at 08:52:24AM -0400, Johan Huldtgren wrote:
> hello,
>
> On 2024-05-16 8:14, Dave Voutila wrote:
> >
> > Johan Huldtgren writes:
> >
> > > hello,
> > >
> > > On 2024-05-15 17:31, Dave Voutila wrote:
> > >>
> > >> Johan Huldtgren writes:
> > >>
> > >> >> Synopsis: vmm
hello,
On 2024-05-16 8:14, Dave Voutila wrote:
>
> Johan Huldtgren writes:
>
> > hello,
> >
> > On 2024-05-15 17:31, Dave Voutila wrote:
> >>
> >> Johan Huldtgren writes:
> >>
> >> >> Synopsis: vmm guest does not get IP after upgrade to 7.5
> >> >> Category: vmd
> >> >>
Johan Huldtgren writes:
> hello,
>
> On 2024-05-15 17:31, Dave Voutila wrote:
>>
>> Johan Huldtgren writes:
>>
>> >> Synopsis: vmm guest does not get IP after upgrade to 7.5
>> >> Category: vmd
>> >> Environment:
>> >System : OpenBSD 7.5
>> >Details : OpenBSD 7.5 (GENERIC.MP)
hello,
On 2024-05-15 17:31, Dave Voutila wrote:
>
> Johan Huldtgren writes:
>
> >> Synopsis: vmm guest does not get IP after upgrade to 7.5
> >> Category: vmd
> >> Environment:
> > System : OpenBSD 7.5
> > Details : OpenBSD 7.5 (GENERIC.MP) #82: Wed Mar 20 15:48:40 MDT 2024
Johan Huldtgren writes:
>> Synopsis:vmm guest does not get IP after upgrade to 7.5
>> Category:vmd
>> Environment:
> System : OpenBSD 7.5
> Details : OpenBSD 7.5 (GENERIC.MP) #82: Wed Mar 20 15:48:40 MDT 2024
>
>
> Synopsis: vmm guest does not get IP after upgrade to 7.5
> Category: vmd
> Environment:
System : OpenBSD 7.5
Details : OpenBSD 7.5 (GENERIC.MP) #82: Wed Mar 20 15:48:40 MDT 2024
On 2024-05-14 13:18 +10, Jonathan Gray wrote:
> hibernate does DVACT_QUIESCE/DVACT_SUSPEND from
> diskconf()/hibernate_resume() before config_process_deferred_mountroot()
> attaches most of the driver. So don't attempt to do anything.
>
> Index: sys/dev/pci/drm/amd/amdgpu/amdgpu_drv.c
>
On Mon, May 13, 2024 at 09:16:36PM -0700, Greg Steuck wrote:
> While restoring from suspend-to-disk my /bsd crashed
diff sent to this list earlier today committed as amdgpu_drv.c rev 1.44
While restoring from suspend-to-disk my /bsd crashed
OpenBSD 7.5-current (GENERIC.MP) #32: Fri Apr 26 10:29:33 MDT 2024
The below is the OCR'd version of my screen:
iic at piixpmo not configured
pcibo at pcio dev 20 function 3 "AMD FCH LPC" rev 0x51
pchb3 at pcio dev 24 function 0 "AMD 19h/5xh
On Mon, May 13, 2024 at 08:10:32PM +0200, Florian Obser wrote:
> OCR'ed and edited a bit, there might be mistakes.
> Picture: https://dump.sha256.net/dump/unhibernating_panic.jpg
>
> unhibernating & block 50329599 Length 243MB
> uvm_fault(0x826b2860, 0x38, 0, 1) →> e
> kernel: page fault
With the recent improvements to witness I can now get a better
report of the lock order reversal I can reproduce on arm64 on
my rock5b.
May 12 13:39:19 rock5b /bsd: witness: lock order reversal:
May 12 13:39:19 rock5b /bsd: 1st 0xff8001200700 /sys/dev/rnd.c:321
(/sys/dev/rnd.c:321)
May 12
OCR'ed and edited a bit, there might be mistakes.
Picture: https://dump.sha256.net/dump/unhibernating_panic.jpg
unhibernating & block 50329599 Length 243MB
uvm_fault(0x826b2860, 0x38, 0, 1) →> e
kernel: page fault trap, code=0
Stopped at ttm_resource_manager_evict_all+0x5e: cmpq %rbx,
It's working now, the netcat must listen on lo0:
nc -kl 127.0.0.1 400
thanks for help!
--
xiangbo
On Sat, May 11, 2024 at 2:34 AM Stuart Henderson
wrote:
> Not directly answering about the change to DIOCNATLOOK (I don't know the
> answer), but that's generally not recommended any more anyway -
Thanks for your reply, I changed the rdr-to rule in the PF rules to
divert-to,
but when I try to connect from another computer,
I get a "Connection refused" error, follow is the test step:
1. PF test rules on the openbsd box with IP 192.168.11.4:
set skip on lo0
pass in quick log on em0 inet
Not directly answering about the change to DIOCNATLOOK (I don't know the
answer), but that's generally not recommended any more anyway - the
preferred option for transparent proxies is to use "divert-to" and then,
for TCP, getsockname(2), or for UDP, IP_RECVDSTADDR/IPV6_RECVDSTPORT
etc. In
PF's DIOCNATLOOK system call can not obtain correct return data in OpenBSD
7.3-7.5, but this call was normal before OpenBSD 7.3. I tested it on
OpenBSD 7.2 and OpenBSD 6.9 and both returned correct data.
The test code is at the end of the report (from man page of PF with a
little modification),
Hi,
I've got my hands on a sapphire rapids based workstation and tried to
boot a recent snapshot of OpenBSD current. The system hangs during boot
after the "efifb at mainbus0 not configured" line. I've made use of the
COM port for serial console and used a preinstalled disk in order to
Found today that the current apple-boot-firmware installed with fw_update
works.
Built my own backing out the most recent changes, but then noticed that the
boot.bin
from current fw_update package was different than the boot.bin in my efi
partition. File hashes
below if they're useful. pkg_info
Hi,
there are several outstanding patches of mine - most of them are still
unanswered:
https://marc.info/?l=openbsd-bugs=141739202313415=2
https://marc.info/?l=openbsd-bugs=171364923522323=2
https://marc.info/?l=openbsd-bugs=171407190132352=2
https://marc.info/?l=openbsd-bugs=171407191132356=2
Hi,
I have a so called "Tenda 300Mbps Mini Wireless N Adapter" (this is not the
terribly small one). It reports itself as:
urtwn0 at uhub0 port 2 configuration 1 interface 0 "Realtek 802.11n NIC" rev
2.10/2.00 addr 2
urtwn0: MAC/BB RTL8192EU, RF 6052 2T2R, address 50:2b:73:c9:11:00
It
Greetings,
How long did you wait?
It has sat there for upwards of a few hours. I have the server set to
update and reboot around 1:00 AM nightly and there are a number of times I
will get up in the morning and it will still be sitting at boot>
Does it boot if you type "boot" and press enter?
If
On 2024/05/06 22:33, John Armstrong wrote:
> Greetings,
>
> I have run into the issue since OpenBSD 7.3 and recently upgraded to OpenBSD
> 7.5 where when
> rebooting the system stalls at:
>
> Using drive 0, partition 3.
> Loading.
> probing: pc0 con0 con1 con2 mem[630k 495m 15m 2386m 1m 24k
Greetings,
I have run into the issue since OpenBSD 7.3 and recently upgraded to
OpenBSD 7.5 where when rebooting the system stalls at:
Using drive 0, partition 3.
Loading.
probing: pc0 con0 con1 con2 mem[630k 495m 15m 2386m 1m 24k 1024m a20=on]
disk:hd0+
>> OpenBSD/amd64 Boot 3.65
boot>
Here
Hi all,
On around May first (International day of labour) I revisited some old code
of mine and published it.
I understand of the implications of a broken AES, but I'm an open person and
I believe that we must pull out quantum resistant and classic resistant
alternatives, because I have found
Ely Castellano writes:
> The program 'designed by Bruce Schneier' PasswordSafe have the port to
> the OpenBSD as pwsafe (pwsafe-0.2.0p7)
No, the package in OpenBSD is a different program, written by Nicholas
Dade.
Notice how the package description is entirely dissimilar to the Bruce
Schneier
Hi OpenBSD team, The program 'designed by Bruce Schneier' PasswordSafe have the port to
the OpenBSD as pwsafe (pwsafe-0.2.0p7) The port information of this package show a site
different than the official one The port shows: " WWW: http://nsd.dyndns.org/pwsafe/
" The official:
On Fri, May 03, 2024 at 01:05:55PM +, Miod Vallat wrote:
> > >Description:
> > During boot the kernel panics:
> >
> > panic: malloc: allocation too large, type = 33, size = 292057776136
> >
> > This is during some ACPI stuff:
>
> The size, in hex, is 0x440008, i.e. a merge 272
1 - 100 of 18512 matches
Mail list logo
