• Vitaliy Makkoveev [2023-10-05 01:10]:
On Thu, Oct 05, 2023 at 12:08:55AM +0200, Kirill Miazine wrote:
• Vitaliy Makkoveev [2023-10-05 00:02]:
On 5 Oct 2023, at 00:56, Kirill Miazine wrote:
new diff doesn't prevent hang in test scenario either.
Which one?
I meant to say new diffS,
On Mon, Sep 25, 2023 at 01:33:31PM +, Klemens Nanni wrote:
> On Tue, Jul 25, 2023 at 01:30:43PM +0300, Slava Voronzoff wrote:
> > Hi, pinging and refreshing this patch
> >
> > What it does:
> > allow arm64 cpus to break from the loop of waiting to start core and
> > drop to DDB or OS.
> >
>
On Thu, Oct 05, 2023 at 12:08:55AM +0200, Kirill Miazine wrote:
> • Vitaliy Makkoveev [2023-10-05 00:02]:
> > > On 5 Oct 2023, at 00:56, Kirill Miazine wrote:
> > >
> > > new diff doesn't prevent hang in test scenario either.
> > >
> >
> > Which one?
>
> I meant to say new diffS, as I had
On Sun, Sep 03, 2023 at 02:00:46AM +0200, Alexander Bluhm wrote:
> When DNS lookup for remote loghost in @ line in syslog.conf does
> not work at startup, retry in intervals.
Thanks Paul de Weerd for testing my diff. Together we improved the
debug output to make clear what is going on. I also
Hi,
This is a first step to unlock TCP syn cache. The timer function
is independent of the socket code. That makes it easy to start
there.
Introduce tcp syn cache mutex. Document fields protected by net
lock and mutex. Devide timer function in parts protected by mutex
and sending with
• Vitaliy Makkoveev [2023-10-05 00:02]:
On 5 Oct 2023, at 00:56, Kirill Miazine wrote:
new diff doesn't prevent hang in test scenario either.
Which one?
I meant to say new diffS, as I had applied both... what I have now is this:
> On 5 Oct 2023, at 00:56, Kirill Miazine wrote:
>
> new diff doesn't prevent hang in test scenario either.
>
Which one?
• Vitaliy Makkoveev [2023-10-04 23:38]:
On 5 Oct 2023, at 00:31, Alexander Bluhm wrote:
On Wed, Oct 04, 2023 at 11:03:27PM +0300, Vitaliy Makkoveev wrote:
On Wed, Oct 04, 2023 at 09:13:59PM +0200, Alexander Bluhm wrote:
On Wed, Oct 04, 2023 at 08:42:48PM +0200, Kirill Miazine wrote:
If
> On 5 Oct 2023, at 00:31, Alexander Bluhm wrote:
>
> On Wed, Oct 04, 2023 at 11:03:27PM +0300, Vitaliy Makkoveev wrote:
>> On Wed, Oct 04, 2023 at 09:13:59PM +0200, Alexander Bluhm wrote:
>>> On Wed, Oct 04, 2023 at 08:42:48PM +0200, Kirill Miazine wrote:
> If it happns again, could you
On Wed, Oct 04, 2023 at 11:03:27PM +0300, Vitaliy Makkoveev wrote:
> On Wed, Oct 04, 2023 at 09:13:59PM +0200, Alexander Bluhm wrote:
> > On Wed, Oct 04, 2023 at 08:42:48PM +0200, Kirill Miazine wrote:
> > > > If it happns again, could you send an 'ps axlww | grep ifconifg'
> > > > output? Then
On Wed, Oct 04, 2023 at 11:07:24PM +0200, Kirill Miazine wrote:
>
>
> • Vitaliy Makkoveev [2023-10-04 22:03]:
> > On Wed, Oct 04, 2023 at 09:13:59PM +0200, Alexander Bluhm wrote:
> > > On Wed, Oct 04, 2023 at 08:42:48PM +0200, Kirill Miazine wrote:
> > > > > If it happns again, could you send an
• Vitaliy Makkoveev [2023-10-04 22:03]:
On Wed, Oct 04, 2023 at 09:13:59PM +0200, Alexander Bluhm wrote:
On Wed, Oct 04, 2023 at 08:42:48PM +0200, Kirill Miazine wrote:
If it happns again, could you send an 'ps axlww | grep ifconifg'
output? Then we see the wait channel where it hangs in
rpki-client 8.6 has just been released and will be available in the
rpki-client directory of any OpenBSD mirror soon.
rpki-client is a FREE, easy-to-use implementation of the Resource
Public Key Infrastructure (RPKI) for Relying Parties (RP) to
facilitate validation of BGP announcements. The
On Wed, Oct 04, 2023 at 09:13:59PM +0200, Alexander Bluhm wrote:
> On Wed, Oct 04, 2023 at 08:42:48PM +0200, Kirill Miazine wrote:
> > > If it happns again, could you send an 'ps axlww | grep ifconifg'
> > > output? Then we see the wait channel where it hangs in the kernel.
> > >
> > > $ ps
On Wed, Oct 4, 2023 at 12:46 PM Todd C. Miller wrote:
>
> On Wed, 04 Oct 2023 11:53:51 -0600, Todd C. Miller wrote:
>
> > Yes, this should be fixed. One difference is that in FreeBSD,
> > __swsetup() sets errno whereas in OpenBSD we set errno in the caller
> > when cantwrite() is true. I think
On Wed, 04 Oct 2023 11:53:51 -0600, Todd C. Miller wrote:
> Yes, this should be fixed. One difference is that in FreeBSD,
> __swsetup() sets errno whereas in OpenBSD we set errno in the caller
> when cantwrite() is true. I think it makes sense to set both errno
> and the __SERR flag in the same
On Wed, Oct 04, 2023 at 08:42:48PM +0200, Kirill Miazine wrote:
> > If it happns again, could you send an 'ps axlww | grep ifconifg'
> > output? Then we see the wait channel where it hangs in the kernel.
> >
> > $ ps axlww
> >UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT
• Kirill Miazine [2023-10-04 20:42]:
I saw some changes to wg recently, so I wanted to report the issue in
case recent commit changed something in time for release. I understand
the issue is probably a year old by now. I guess I hadn't destroyed wg
for a while, although I do believe I
I saw some changes to wg recently, so I wanted to report the issue in
case recent commit changed something in time for release. I understand
the issue is probably a year old by now. I guess I hadn't destroyed wg
for a while, although I do believe I have...
• Alexander Bluhm [2023-10-04
On Tue, 03 Oct 2023 16:09:12 -0700, enh wrote:
> looks like OpenBSD is missing this patch from FreeBSD? llvm libc++ hit
> this (a test worked on other OSes, including FreeBSD-based macOS) but
> failed on OpenBSD-based Android.
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=127335 was the
>
It works currently on my own firewall. The problem occured on a client's
firewall, which I can't test right now. It's an amd64 system (older
Supermicro) and as I was shelled in remotely I was getting worried about
recovering and then I discovered "reboot -q" - nothing else was working to
get the
On Wed, Oct 04, 2023 at 10:53:30AM -0400, Sonic wrote:
> When it happened to me back then (2022) I'm pretty sure I did a "down"
> followed by a "delete" and then the "destroy".
root@ot6:.../~# cd /usr/src/regress/sys/net/wg
root@ot6:.../wg# make ifconfig
...
root@ot6:.../wg# ifconfig wg11
wg11:
When it happened to me back then (2022) I'm pretty sure I did a "down"
followed by a "delete" and then the "destroy".
Have not tried to recreate since then.
On Wed, Oct 4, 2023 at 10:31 AM Alexander Bluhm
wrote:
> On Wed, Oct 04, 2023 at 10:08:01AM -0400, Sonic wrote:
> > See the post:
> >
On Wed, Oct 04, 2023 at 10:08:01AM -0400, Sonic wrote:
> See the post:
> "Uninterruptible D State after ifconfig wg0 destroy" Oct. 31, 2022 in the
> Bugs archive.
I have a test regress/sys/net/wg that configures a wg(4), sends
some traffic, and destroys it. I have never seen this bug. There
See the post:
"Uninterruptible D State after ifconfig wg0 destroy" Oct. 31, 2022 in the
Bugs archive.
On Wed, Oct 4, 2023 at 10:04 AM Sonic wrote:
> This goes back a ways, to at least 7.2 in October 2022.
>
>
> On Wed, Oct 4, 2023 at 8:54 AM Kirill Miazine wrote:
>
>> Recently on snapshots I
This goes back a ways, to at least 7.2 in October 2022.
On Wed, Oct 4, 2023 at 8:54 AM Kirill Miazine wrote:
> Recently on snapshots I have noticed that ifconfig wgN destroy would
> just hang there, without any way to get back the control. Power reset
> would be the only way to reboot and
Can you try compiling without this:
https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/net/if_wg.c.diff?r1=1.29=1.30
Kirill Miazine [k...@krot.org] wrote:
> Recently on snapshots I have noticed that ifconfig wgN destroy would just
> hang there, without any way to get back the control. Power reset
Recently on snapshots I have noticed that ifconfig wgN destroy would
just hang there, without any way to get back the control. Power reset
would be the only way to reboot and regain control.
I don't have exact date when it happened first, maybe some 10 days ago,
but problem is present on most
Hello,
m...@paianis.name (Paianis), 2023.10.03 (Tue) 14:47 (CEST):
> I wanted some cleaner pixmaps of the logo for the login greeter than
> those currently in the tree, so I remade them from the PDFs that used to
> be on the website, using mutool and imagemagick's convert.
>
> The low-color and
29 matches
Mail list logo
