Committed, thanks!
On 2024-02-24 03:18 +01, Einfach Jemand wrote:
> Hiya,
>
> when working with my OpenBSD-Laptop (running OpenBSD 7.4-current
> (GENERIC.MP) #1667: Wed Feb 7 20:09:35 MST 2024) using unwind in a
> large customer network and having problems resolving some PTRs from
> 18.172.in
Well,
I just rebooted to a new snapshot, and WiFi has been future degradated.
I do run a MPD sync in background which downloads some files via HTTP,
but I may run before, and it never creates an issue.
Meanwhile the ping to GW from latop seems like:
~ $ ping 172.31.2.1
PING 172.31.2.1 (172
On Sun, Feb 25, 2024 at 05:19:33PM +0100, Kirill A. Korinsky wrote:
> Well,
>
> I just rebooted to a new snapshot, and WiFi has been future degradated.
>
> I do run a MPD sync in background which downloads some files via HTTP,
> but I may run before, and it never creates an issue.
>
> Meanwhile
>Synopsis: amd64 boot reordering warning
>Category: boot
>Environment:
System : OpenBSD 7.5
Details : OpenBSD 7.5-beta (GENERIC.MP) #25: Sat Feb 24 20:50:14
MST 2024
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
On Sun, 25 Feb 2024 17:32:46 +0100,
Stefan Sperling wrote:
>
> I have less than 2ms ping latency to my 5 GHz AP over iwx.
> So this is probably not an issue in iwx but something else.
I wan't near machine for couple of hours, but it stay up and connected to
the wifinetwork.
When I'll back nothin
No, you can ignore this "warning".
It is unimportant and temporary.
Jacqueline Jolicoeur wrote:
> >Synopsis:amd64 boot reordering warning
> >Category:boot
> >Environment:
> System : OpenBSD 7.5
> Details : OpenBSD 7.5-beta (GENERIC.MP) #25: Sat Feb 24 20:50:14
> M
On Sun, Feb 25, 2024 at 10:17:37PM +0100, Kirill A. Korinsky wrote:
> On Sun, 25 Feb 2024 17:32:46 +0100,
> Stefan Sperling wrote:
> >
> > I have less than 2ms ping latency to my 5 GHz AP over iwx.
> > So this is probably not an issue in iwx but something else.
>
> I wan't near machine for couple
On Sun, 25 Feb 2024 23:03:31 +0100,
Stefan Sperling wrote:
>
> To get more information about this error please run with 'ifconfig iwx0
> debug'.
> Just adding the line 'debug' in /etc/hostname.iwx0 is enough to activate
> at boot. It will be a bit more noise in dmesg and once this firmware error
