'make clean && make config' from
> GENERIC.MP/
Indeed, make config was missed from used script.
Sorry for noise.
--
wbr, Kirill
>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: 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
nd chrome, seems "normal".
--
wbr, Kirill
ckerd and related processes. Nothing else.
At the time of crash it hadn't run anything docker container inside, it was
just rebooted.
--
wbr, Kirill
>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
.sb_flags & SB_OWNLOCK) == 0)
> + if ((so->so_rcv.sb_flags & SB_MTXLOCK) == 0)
> soassertlocked(so);
>
> mtx_enter(>so_rcv.sb_mtx);
I can boot with this patch and write this answer.
Thanks!
--
wbr, Kirill
>Synopsis: panic: unix: lock not held
>Category: kernel
>Environment:
System : OpenBSD 7.5
Details : OpenBSD 7.5-current (GENERIC.MP) #96: Thu May 2 22:01:31
CEST 2024
>Synopsis: sysctl hw.smt=0 may lead to crash
>Category: mp
>Environment:
System : OpenBSD 7.5
Details : OpenBSD 7.5-current (GENERIC.MP) #38: Tue Apr 30 14:42:19
MDT 2024
On Sat, 27 Apr 2024 19:35:13 +0200,
Matthieu Herrb wrote:
>
> On Sat, Apr 27, 2024 at 07:20:15PM +0200, Kirill A. Korinsky wrote:
> > On Sat, 27 Apr 2024 19:06:40 +0200,
> > Matthieu Herrb wrote:
> > >
> > > There was a regression in Xorg 21.1.12 that m
xserver 21.1.0 [2].
Footnotes:
[1]
https://gitlab.freedesktop.org/xorg/xserver/-/commit/c7414f4d07b69a4b2f0d0af06f032393cf5fe6aa
[2]
https://github.com/openbsd/xenocara/tree/e086cf5adf82811c219a3e76c4079278a4e75250
--
wbr, Kirill
Apr 27 14:05 X
drwxrwxrwx 2 root wheel 512 Apr 27 14:00 X11
-rw-r--r-- 1 root wheel5 Oct 10 2023 minfree
~ $
but it doesn't help.
--
wbr, Kirill
>Synopsis: X11 crashes when start Intellij IDEA
>Category: X11
>Environment:
System : OpenBSD 7.5
Details : OpenBSD 7.5-current (GENERIC.MP) #32: Fri Apr 26 10:29:33
MDT 2024
9b:48:af ssid
"catap's Network" channel 136 start MCS 0 long preamble long slot time HT
enabled VHT enabled
Apr 21 10:59:44 matebook /bsd: iwx0: missed beacon threshold set to 30
beacons, beacon interval is 100 TU
Apr 21 10:59:44 matebook /bsd: iwx0: received msg 3/4 of the 4-way handshake
from b6:fb:e4:9b:48:af
Apr 21 10:59:44 matebook /bsd: iwx0: sending msg 4/4 of the 4-way handshake
to b6:fb:e4:9b:48:af
Apr 21 10:59:46 matebook /bsd: iwx0: sending addba_resp to b6:fb:e4:9b:48:af
on channel 136 mode 11ac
--
wbr, Kirill
>Synopsis: Disk sync on reboot nevers end
>Category: filesystem
>Environment:
System : OpenBSD 7.5
Details : OpenBSD 7.5-current (GENERIC.MP) #31: Wed Apr 17 18:33:33
MDT 2024
fatal firmware error
--
wbr, Kirill
On Tue, 27 Feb 2024 08:45:44 +0100,
Stefan Sperling wrote:
>
> On Mon, Feb 26, 2024 at 10:17:20PM +0100, Kirill A. Korinsky wrote:
>
> > Anyway, I'll keep debug enabled for the case if frimeware error happens.
>
> Yes, that would still be interesting, thanks.
It's happenin
On Mon, 26 Feb 2024 12:39:12 +0100,
Stefan Sperling wrote:
>
> On Mon, Feb 26, 2024 at 11:40:35AM +0100, Kirill A. Korinsky wrote:
> > all of this seems like a strong indicator that the issue is inside iwx
>
> I have no idea what causes the latency spikes you are seeing, and
On Mon, 26 Feb 2024 12:39:12 +0100,
Stefan Sperling wrote:
>
> On Mon, Feb 26, 2024 at 11:40:35AM +0100, Kirill A. Korinsky wrote:
> > all of this seems like a strong indicator that the issue is inside iwx
>
> You don't need to try hard to convince me that there could be
&
Done.
√ ~ %
all of this seems like a strong indicator that the issue is inside iwx
Meanwhile, I have't got anythin inside dmesg.
--
wbr, Kirill
SD laptop, the second one MBP.
Both are connected to the same AP. The red zone is near the time when I've
wrote email with very bad pings.
Unfortently I don't understand how to get historical WiFi expirences, but it
was almsot always green on OpenBSD laptop as well.
--
wbr, Kirill
ile, I've rebooted it and now ping is 1.3-1.7 ms as it should be.
--
wbr, Kirill
on the kernel as it was
installed on taday's snapshot.
And my home WiFi network is running on Automatic mode from Unifi, without
any hacks.
--
wbr, Kirill
d5kl-b-5k-uhd-led-monitor
--
wbr, Kirill
start to boot, but never light up. If I
recconect the laptop (plug and unplug USB-C), it light up.
Wired, but this behaviour happenes not always. Seems that it need couple
of minutes (5-10, not sure) to be disconnected from everything to go
into that deep sleep state.
Anz thoughts?
--
wbr, Kirill
On Tue, 20 Feb 2024 11:08:21 +0100,
Kirill A. Korinsky wrote:
>
> Anyway, I'll try to reserve some time to dig into cam with hope that
> this nice screen will be fully functional on OpenBSD-7.5.
>
BTW with the last patch behaviour seems a bit improved.
~ $ video -q -f /dev/video1
eserve some time to dig into cam with hope that
this nice screen will be fully functional on OpenBSD-7.5.
--
wbr, Kirill
On Mon, 19 Feb 2024 12:23:46 +0100,
Jonathan Gray wrote:
>
> Can you revert that and see if only 1 of the 3 commits is enough?
>
> Diff below includes only
> "drm/i915/pxp/mtl: Update pxp-firmware response timeout"
>
It works.
--
wbr, Kirill
Thanks, this is much cleaner than my durty patch.
--
wbr, Kirill
my approach is hack which fixed my issue, but I haven't got any way to
test it on different hardware, so, I may introduce something.
But I happy that I can use my screen again
P.S. bug report: https://marc.info/?l=openbsd-bugs=170821608101004=2
--
wbr, Kirill
diff --git sys/dev/pci/drm/i915/
://github.com/catap/OpenBSD-src/tree/LG5k-issue
--
wbr, Kirill
>Synopsis: External display doesn't work (start?) anymore
>Category: X11
>Environment:
System : OpenBSD 7.5
Details : OpenBSD 7.5-beta (GENERIC.MP) #1694: Sat Feb 17 11:17:45
MST 2024
rate_flags |= (iwx_fw_rateidx_cck(rinfo->rate) &
> IWX_RATE_LEGACY_RATE_MSK);
> }
> } else
Just appllied to a local root
https://github.com/openbsd/src/commit/19619287f1f0d0217f654c44bd972f72836ef04e
It doesn't help.
--
wbr, Kirill
ones,
> laptops running an OS other than OpenBSD, etc.
I do have an issue with wifi printer which sometimes lose network. Thanks for
bring it, I've moved back to auto mode with hope that it works cleaner.
--
wbr, Kirill
sending msg 4/4 of the 4-way handshake
to b4:fb:e4:8b:48:af
Feb 16 03:00:24 matebook /bsd: iwx0: sending addba_resp to b4:fb:e4:8b:48:af
on channel 136 mode 11ac
Thus, disabling 5Ghz does help. that lead me to dig an issue on network settings
side. After poking around I've discovered that settings which triggers an issue
is "Minimum Data Rate Control" inside Unifi UI. It has settings for 5Ghz
network: 6, 9, 12 and 24 mbps. Old one was 12 (or 24), anyway, an issue
happening when this settings is 12 or 24 mbps.
--
wbr, Kirill
>Synopsis: iwx obtains IP via DHCP but no traffic
>Category: network, drivers
>Environment:
System : OpenBSD 7.4
Details : OpenBSD 7.4-current (GENERIC.MP) #1688: Thu Feb 15
10:48:34 MST 2024
address to autoinstall?
Thanks.
Footnotes:
[1]
https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/distrib/miniroot/install.sub.diff?r1=1.1173=1.1174=h
[2] base on available doc
--
wbr, Kirill
cat /etc/group
fG???V?y
X???Gm?V?+?(l?]?I??.??B?NF?d?6??pV?>??Ob64?MXXg?
so,
# mount -uw /
# mount /usr
# mount /var
# tar -xzvf /var/sysmerge/etc.tgz ./etc/group
was enough to boot it again, but now I a bit scary :)
Shall I revert the patch or it isn't related, or?
--
wbr, Kirill
tch to the 7.4 and rebuild kernel, reboot machine and
wait a few days to confirm that it hadn't introduced any unexpected issues.
2. After that I've repeated installation of new VM 10 times in the row to
reproduce the issue. I can't.
Thanks for the patch!
--
wbr, Kirill
better to avoid that?
--
wbr, Kirill
--
wbr, Kirill
0 8296 9584 ?? Ic 12:33AM0:00.02 -
> /usr/local/sbin/named -t /var/named -u _bind -U 4
> root 30890 0.0 0.0 2172 2696 ?? IU 12:33AM0:00.00 -
> /usr/sbin/relayd
> _relayd 41014 0.0 0.0 1720 3372 ?? Spc12:33AM0:00.00 |--
> relayd: pfe (relayd)
> _relayd 69672 0.0 0.0 1720 3252 ?? Spc12:33AM0:00.00 |--
> relayd: hce (relayd)
> _relayd 61468 0.0 0.0 2568 5504 ?? Spc12:33AM0:00.01 |--
> relayd: relay (relayd)
> _relayd 19441 0.0 0.0 2140 4992 ?? Spc12:33AM0:00.01 |--
> relayd: relay (relayd)
> _relayd 34772 0.0 0.0 2568 5508 ?? Spc12:33AM0:00.01 |--
> relayd: relay (relayd)
> _relayd 48437 0.0 0.0 1932 4260 ?? Spc12:33AM0:00.03 |--
> relayd: ca (relayd)
> _relayd 6066 0.0 0.0 1668 4188 ?? Ipc12:33AM0:00.01 |--
> relayd: ca (relayd)
> _relayd 28873 0.0 0.0 1912 4264 ?? Spc12:33AM0:00.04 `--
> relayd: ca (relayd)
> root 5407 0.0 0.0 808 1316 C0 I+pU 12:26AM0:00.00 -
> /usr/libexec/getty std.9600 ttyC0
> root 53681 0.0 0.0 804 1304 C1 I+pU 12:26AM0:00.00 -
> /usr/libexec/getty std.9600 ttyC1
> root 34338 0.0 0.0 800 1296 C2 I+pU 12:26AM0:00.00 -
> /usr/libexec/getty std.9600 ttyC2
> root 21579 0.0 0.0 804 1316 C3 I+pU 12:26AM0:00.00 -
> /usr/libexec/getty std.9600 ttyC3
> root 34603 0.0 0.0 804 1304 C5 I+pU 12:26AM0:00.00 -
> /usr/libexec/getty std.9600 ttyC5
> $
and system fully booted.
I expect that relayd won't send traffic to unavailable backend, but not stuck
everything. And DNS shouldn't be single point of failure, isn't it?
--
wbr, Kirill
reboot of host node help to fix issue with network.
It also allows to avoid pool_do_get: mcl2k free on installation.
But, as soon as pool_do_get: mcl2k free is back, the network instability back
as well.
--
wbr, Kirill
9.843791 192.168.240.7 > 146.75.123.52: icmp: echo request
> 21:43:59.848569 146.75.123.52 > 192.168.240.7: icmp: echo reply
> 21:44:02.303897 192.168.240.7 > 146.75.123.52: icmp: echo request
> 21:44:03.323806 192.168.240.7 > 146.75.123.52: icmp: echo request
> 21:44:04.323763 192.168.240.7 > 146.75.123.52: icmp: echo request
> 21:44:05.323755 192.168.240.7 > 146.75.123.52: icmp: echo request
> 21:44:06.323741 192.168.240.7 > 146.75.123.52: icmp: echo request
> ^C
> 200 packets received by filter
> 0 packets dropped by kernel
--
wbr, Kirill
hat as well or
> maybe there's a way to do it today that I'm not aware of. (I don't use
> any of the lladdr features in vmd.)
Confirmed no bug here, I was misslead of tap address.
The cause of investigation was forgotten update of /etc/mygate
--
wbr, Kirill
> On 2. Jan 2024, at 16:34, Dave Voutila wrote:
>
> "Kirill A. Korinsky" writes:
>
>> Greetings,
>>
>> When playing with autoinstall in VM I encountered a kernel panic. It doesn't
>> happened each attempt, but often enough to be easy found.
&g
te some MAC to IP address and everything which it
generates can be used here.
But all of them starts from 00:50.
--
wbr, Kirill
.
VM configuration quite simple:
vm "playground" {
memory 1G
disk "/var/vm/playground.qcow2"
interface {
switch "local"
lladdr "fe:e1:ba:05:ec:58"
}
owner catap
}
and disk size is 200Gb.
--
wbr, Kirill
Errors gone in this one:
OpenBSD 7.2-current (GENERIC.MP) #835: Mon Nov 14 21:07:22 MST 2022
• Kirill Miazine [2022-11-14 22:40]:
> The most recent snapshot gives non-recoverable failure in name
> resolution upon boot starting with configuration which I had not
> touched:
>
-recoverable failure in name resolution
This is on OpenBSD 7.2-current (GENERIC.MP) #833: Mon Nov 14 11:25:32 MST 2022.
--
-- Kirill Miazine
7 -
> @@ -1040,8 +1040,8 @@ static void vlv_display_power_well_deini
> #ifdef notyet
> /* Prevent us from re-enabling polling on accident in late suspend */
> if (!dev_priv->drm.dev->power.is_suspended)
> - intel_hpd_poll_init(dev_priv);
> #endif
> + intel_hpd_poll_init(dev_priv);
> }
>
> static void vlv_display_power_well_enable(struct drm_i915_private *dev_priv,
>
--
-- Kirill Miazine
Synopsis: splassert ip_output
Category: kernel amd64
Environment:
System : OpenBSD 6.0
Details : OpenBSD 6.0-current (GENERIC) #58: Mon Dec 19 19:57:52
MST 2016
bu...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
51 matches
Mail list logo
