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.
An example of panic:
island$ vmctl start -c -b /tmp/bsd.rd -B net playground
Connected to /dev/ttyp2 (speed 115200)
Copyright (c) 1982, 1986, 1989, 19
Greetings,
Seems that it is impossible to setup some MAC address to an network interfce of
VM. For example I have a VM with settings:
vm "mx0" {
memory 1G
disk "/var/vm/mx0.qcow2"
interface {
switch "uplink"
lladdr "00:50:56:00:20:a5"
> 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 foun
> On 2. Jan 2024, at 15:38, Dave Voutila wrote:
>
> What is the hardware address for the virtio network device inside the
> VM? The tap(4) device is host-side. I just tested this locally and am
> able to have the guest-side vio(4) properly set:
>
> vio0: flags=8802 mtu 1500
>lladdr 00:
Additionally I'd like to report quite unstable network on the same host.
Some connections has 100% packet loss, some works quite fine.
If connection is good one, it works long. For example my SSH session
lasts more than few hours.
Just to prove it I had make a few ping with capturing traffic on
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
Greeting,
I'm using 7.4 and have a bit wired setup which leads to blocked relayd and seems
that it block system from a while for a boot.
Inside relayd I have a few tables like this:
> table { "podman.island.local" retry 5 }
Each table contains internal DNS.
As DNS I us
On Thu, 11 Jan 2024 19:43:08 +0100,
Dave Voutila wrote:
> Can you try the diff shared recently on bugs@?
>
> https://marc.info/?l=openbsd-bugs&m=17048267793&q=raw
>
> It looks like the vio(4) driver doesn't wait for vmd to reset the device
> before it starts touching memory. This is a kerne
On Thu, 11 Jan 2024 19:43:08 +0100,
Dave Voutila wrote:
>
> Can you try the diff shared recently on bugs@?
>
> https://marc.info/?l=openbsd-bugs&m=17048267793&q=raw
>
> It looks like the vio(4) driver doesn't wait for vmd to reset the device
> before it starts touching memory. This is a ke
On Thu, 11 Jan 2024 19:43:08 +0100,
Dave Voutila wrote:
>
> Can you try the diff shared recently on bugs@?
>
> https://marc.info/?l=openbsd-bugs&m=17048267793&q=raw
After appling this patch I do have the first issue.
An upgrade OpenBSD inside VM from 7.3 to 7.4 leads to garbage inside
/etc/
Greetings,
Before 7.0 it was possible to use tftp-server-name as a way to provide used HTTP
server to download answers files. Seems that this feature were removed with
cleanup of code. [1]
Unfortently next-server allows to use only IP address. [2]
Do you know any way to send hostname instead IP
ifconfig iwx0 debug, reconnect:
Feb 16 03:00:17 matebook /bsd: iwx0: using firmware iwx-QuZ-a0-hr-b0-77
Feb 16 03:00:17 matebook /bsd: iwx0: begin active scan
Feb 16 03:00:17 matebook /bsd: iwx0: INIT -> SCAN
Feb 16 03:00:21 matebook /bsd: iwx0: end active scan
Feb 16 03:00:21 matebook
Stefan,
On Fri, 16 Feb 2024 10:13:50 +0100,
Stefan Sperling wrote:
>
> If your AP still announces 6M even while you've disabled this rate in
> settings,
> then the AP is broken and there is nothing to fix for us, you could only try
> asking the vendor for an AP firmware fix. Otherwise, there coul
On Fri, 16 Feb 2024 12:13:32 +0100,
Stefan Sperling wrote:
>
> I might have found the root cause of your problem in iwx.
> Can you try this diff please?
>
> diff /usr/src
> commit - 5f5902b3789b6f994566004963a31af6304d3a70
> path + /usr/src
> blob - 4b945edf2c73c6e2582819b283277baff81a6586
> file
As attempt to find the cause I've tried different kernels.
The first step was to try kernel before: update drm to linux 6.6.12 [1],
which I suceffuly build and tries on current snapshot system.
The issue was reproduced.
Unfortently I can't simple switch to something before because system doesn
Greetings,
Here an ugly patch which recovers support of LG UltraFine 5K which was broken
since update drm to linux 6.6.12.
This Display is quite delicate if not to say unstable, and it won't start with
timeout other whan 250ms.
A function intel_pxp_get_backend_timeout_ms returns two possible val
Greetings,
> I'm curious if some of the newer commits in linux change what you see.
> combined diff below
Just applied it as https://marc.info/?l=openbsd-bugs&m=170833357114116&q=raw on
local root
https://github.com/openbsd/src/commit/cfda45639a5cff5780a6f40814e7d74479c846c3
And it help.
Thank
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
On Tue, 20 Feb 2024 09:11:35 +0100,
Jonathan Gray wrote:
>
> Thanks, committed.
Thanks!
Embedded cam into this display doesn't work also, but I haven't got time
to debug it right now.
Thus, discovering that the timeout was the case of issue was quite time
consuming.
Anyway, I'll try to reserve
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/v
On Tue, 20 Feb 2024 09:11:35 +0100,
Jonathan Gray wrote:
>
> Thanks, committed.
And I found one more unexpected side effect.
When I connect monitor I need to reconnect it physically some times.
Seems that it in kind of sleep or hibernate mode, and when I connect
laptop the first time, it start
On Thu, 22 Feb 2024 00:36:00 +0100,
Jonathan Gray wrote:
>
> Try directly connect with DisplayPort or HDMI if you can. USB Type-C
> involves dealing with another microcontroller.
This Display hasn't got any control nor ports other that USB-C.
See: https://www.lg.com/us/monitors/lg-27md5kl-b-5k-
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, 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
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
I'd like to add an example of ping and iperf to some host in my network
which shows how wired network is:
~ $ ping 172.31.3.10
PING 172.31.3.10 (172.31.3.10): 56 data bytes
64 bytes from 172.31.3.10: icmp_seq=0 ttl=63 time=209.458 ms
64 bytes from 172.31.3.10: icmp_seq=1 ttl=63 time=238.69
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
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 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'
On Tue, 27 Feb 2024 08:45:44 +0100,
Stefan Sperling wrote:
>
> > Anyway, I'll keep debug enabled for the case if frimeware error happens.
>
> Yes, that would still be interesting, thanks.
Here it is:
iwx0: unhandled firmware response 0x3ff/0x2008 rx ring 95[17]
iwx0: fatal firmware erro
>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
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GEN
Greeting,
finally I've catch something. I not sure is it the same error or not, but it
seems right to share anyway.
It was get from snapshot which was installed about 3 days ago.
Apr 21 10:59:40 matebook /bsd: iwx0: dumping device error log
Apr 21 10:59:40 matebook /bsd: iwx0: Start Error Lo
On Sat, 27 Apr 2024 14:15:18 +0200,
Lucas Raab wrote:
>
> Do you have a link to the project you're trying to run? I cloned the
> scala3-example-project, installed scala/sbt, and was able to run it
> without a crash. This was with:
> OpenBSD 7.5-current (GENERIC.MP) #33: Sat Apr 27 01:25:59 MDT 20
On Sat, 27 Apr 2024 19:06:40 +0200,
Matthieu Herrb wrote:
>
> Does your Xorg.0.log say "X.Org X Server 1.21.1.12" or
> "X.Org X Server 1.21.1.13" ?
>
>
> There was a regression in Xorg 21.1.12 that may be the cause. It's
> supposed to be fixed by 21.1.13 (it should be in recent snapshots).
>
I do
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 may be
On Thu, 02 May 2024 23:04:02 +0200,
Vitaliy Makkoveev wrote:
>
> Sorry, I missed this hunk.
>
> Index: sys/kern/uipc_socket2.c
> ===
> RCS file: /cvs/src/sys/kern/uipc_socket2.c,v
> diff -u -p -r1.151 uipc_socket2.c
> --- sys/kern/u
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 ru
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 the
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 7.5-current
On Sun, 23 Jun 2024 16:07:37 +0100,
Florian Obser wrote:
>
> I would argue that it works as intended. I suppose this could be
> documented better.
>
> Only resolving strategies listed in "preference" are considered.
>
From the current wording in the man page I get that the preference is a list
o
On Thu, 27 Jun 2024 11:47:25 +0100,
Claudio Jeker wrote:
>
> The ptrace code is somewhat borken. We are inside sleep_finish() but
> cursig() calls single_thread_set() without SINGLE_DEEP. Because of this
> exit1() is called in a place it is not allowed to.
>
> ptrace and SIGSTOP handling is not
On Sun, 30 Jun 2024 14:06:33 +0100,
Florian Obser wrote:
>
> On 2024-06-23 17:58 +01, Kirill A. Korinsky wrote:
> > On Sun, 23 Jun 2024 16:07:37 +0100,
> > Florian Obser wrote:
> >>
> >> I would argue that it works as intended. I suppose this could be
&g
On Sun, 07 Jul 2024 21:55:01 +0100,
Qingyao Sun wrote:
>
> Description:
> I drafted a problem report with sendbug(1) and sent it. However, it did
> not appear on
> https://marc.info/?l=openbsd-bugs after a while, so I checked
> /var/log/maillog and it
> turns out that the mess
>Synopsis: iwx: fatal firmware error
>Category: iwx
>Environment:
System : OpenBSD 7.5
Details : OpenBSD 7.5-current (DEBUG.MP) #5: Thu Jul 18 02:50:06
WEST 2024
catap@matebook.local:/usr/src/sys/arch/amd64/compile/DEBUG.MP
Arch
On Mon, 22 Jul 2024 11:40:03 +0200,
Stefan Sperling wrote:
>
> On Sat, Jul 20, 2024 at 12:48:47AM +0100, Kirill A. Korinsky wrote:
> > Jul 19 11:59:10 matebook /bsd: iwx0: 0x2010350B | ADVANCED_SYSASSERT
>
> According to intel linux devs this error means we already allocated
>Synopsis: swapctl -d crashes the system
>Category: swap
>Environment:
System : OpenBSD 7.5
Details : OpenBSD 7.5-current (DEBUG.MP) #5: Thu Jul 18 02:50:06
WEST 2024
catap@matebook.local:/usr/src/sys/arch/amd64/compile/DEBUG.MP
On Mon, 19 Aug 2024 21:13:57 +0200,
"Peter N. M. Hansteen" wrote:
>
> I did a bit of that and it looks if I read this correctly that the pain point
> is in the DKIM handling, collection of bts at
> https://nxdomain.no/~peter/exim-gdb-traces.txt
>
I wonder if this issue can be introduced by
htt
On Mon, 19 Aug 2024 22:31:54 +0200,
Stuart Henderson wrote:
>
> Wait and try again, or try a different mirror. Something is causing
> shearing in some cases i.e. a mixture of files from two different
> snapshots.
>
probably the speed of downloading parts of snapshot is the root cause
> > Nothin
On Wed, 21 Aug 2024 14:32:34 +0200,
David McMackins II wrote:
>
> rsae_send_imsg: privenc poll timeout, keyop #0
> relay gemini, session 1 (1 active), 0, 192.168.1.1 -> :11965, TLS
> handshake error: handshake failed: error:1402D438:SSL
> routines:ACCEPT_SW_CERT:tlsv1 alert internal error: Invali
On Fri, 26 Jul 2024 02:28:12 +0200,
Kirill A. Korinsky wrote:
>
> >Synopsis:swapctl -d crashes the system
> >Category:swap
> >Environment:
> System : OpenBSD 7.5
> Details : OpenBSD 7.5-current (DEBUG.MP) #5: Thu J
On Sat, 07 Sep 2024 15:13:07 +0200,
Claudio Jeker wrote:
>
> The 3rd diff will be the ps_xsig fixes for signal delivery via ptrace.
> After that I think ptrace should be fit for release
Am I right that this possible fix
https://marc.info/?t=17194840332&r=1&w=2 as well?
--
wbr, Kirill
On Sat, 12 Oct 2024 11:32:02 +0200,
Miod Vallat wrote:
>
> Does the following diff also fix the problem for you?
>
> Index: hidkbd.c
> ===
> RCS file: /OpenBSD/src/sys/dev/hid/hidkbd.c,v
> retrieving revision 1.14
> diff -u -p -r1.1
On Sun, 13 Oct 2024 01:32:03 +0200,
Kirill A. Korinsky wrote:
>
> I had discovered that the same problem was fixed in NetBSD in 2009:
> https://github.com/NetBSD/src/commit/edeb84e77a4277c9cc1470db7c51460adee28854.
>
> So, I have included their changes in the diff below. This ve
On Mon, 21 Oct 2024 20:39:51 +0200,
Miod Vallat wrote:
>
> > With and without it push a button mute leads to two events:
> >
> > KeymapNotify event, serial 28, synthetic NO, window 0x0,
> > keys: 29 0 0 0 0 0 0 0 0 0 0 0 0 0 0
> > 0
> >
On Mon, 21 Oct 2024 11:19:48 +0200,
"Anthony J. Bentley" wrote:
>
> Vitaliy Makkoveev writes:
> > I suspect vio(4).
>
> Maybe there are multiple bugs. But as we've discussed before, wg(4) is
> crashy on em(4) too.
> https://marc.info/?l=openbsd-bugs&m=171615647816882&w=2
>
I'd like to add one m
On Mon, 21 Oct 2024 20:38:34 +0200,
Miod Vallat wrote:
>
> > So, I have included their changes in the diff below. This version fixes the
> > Prtc button on my USB keyboard, and also fixes a bug with the mute button on
> > the embedded keyboard. The bug: when I press it, it feels that it emmits
>
>Synopsis: Prtsc button doesn't work on USB keyboard
>Category: xenocara
>Environment:
System : OpenBSD 7.6
Details : OpenBSD 7.6-current (GENERIC.MP) #20: Fri Oct 11 23:56:48
CEST 2024
catap@matebook.local:/usr/src/sys/arch/amd64/comp
On Sat, 12 Oct 2024 11:32:02 +0200,
Miod Vallat wrote:
>
> Does the following diff also fix the problem for you?
>
> Index: hidkbd.c
> ===
> RCS file: /OpenBSD/src/sys/dev/hid/hidkbd.c,v
> retrieving revision 1.14
> diff -u -p -r1.1
Dave, Mike,
Thanks to reply.
Here inlined replies to both emails.
On Mon, 04 Nov 2024 19:58:10 +0100,
Dave Voutila wrote:
>
> Mike Larkin writes:
>
> > On Sun, Nov 03, 2024 at 02:03:15PM +0100, Kirill A. Korinsky wrote:
> >> On Sun, 03 Nov 2024 13:28:16 +0100,
>Synopsis:
>Category:
>Environment:
System : OpenBSD 7.6
Details : OpenBSD 7.6-current (GENERIC.MP) #407: Fri Nov 1
20:31:42 MDT 2024
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
Architecture: OpenBSD.
On Sun, 03 Nov 2024 13:28:16 +0100,
Mike Larkin wrote:
>
> This is exactly what many of us do, every day. So I'm not sure what's
> triggering your scenario. Any way to narrow it down more than "just use the
> system for a day or two"? Eg, "here's a script you can run inside an alpine VM
> that tr
On Sun, 24 Nov 2024 16:55:55 +0100,
Martin Pieuchot wrote:
>
> On 24/11/24(Sun) 16:51, Kirill A. Korinsky wrote:
> > On Sun, 24 Nov 2024 15:34:30 +0100,
> > Martin Pieuchot wrote:
> > >
> > > On 23/11/24(Sat) 21:45, Kirill A. Korinsky wrote:
> &
>Synopsis: vio0: device needs reset
>Category: vmd
>Environment:
System : OpenBSD 7.6
Details : OpenBSD 7.6-current (GENERIC.MP) #455: Thu Nov 28
09:43:05 MST 2024
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
On Sat, 30 Nov 2024 01:08:09 +0100,
Mike Larkin wrote:
>
> On Thu, Nov 28, 2024 at 08:49:41PM +0100, Kirill A. Korinsky wrote:
> > >Synopsis: vio0: device needs reset
> > >Category: vmd
> > >Environment:
> > System : OpenBSD 7.6
> >
On Tue, 19 Nov 2024 22:51:25 +0100,
Rob LA LAU wrote:
>
> The resetting of statistics for all IP addresses in a specified table is
> already implemented (`pfctl -t sometable -T zero').
> However, resetting the statistics for a single IP address in a table
> would allow me to continuously block rep
On Sun, 17 Nov 2024 16:59:34 +0100,
Kirill A. Korinsky wrote:
>
> >Synopsis:ksh: syntax error: `(' unexpected
> >Category:ksh
> >Environment:
> System : OpenBSD 7.6
> Details : OpenBSD 7.6-current (GENERIC.MP) #39:
On Sun, 17 Nov 2024 18:25:47 +0100,
Andreas Kähäri wrote:
>
> A the final right curly brace of a compound command must be preceeded by
> a command terminator, most commonly a newline or a semi-colon. This is
> what causes the syntax error in the script.
>
> An additional issue is that your logi
>Synopsis: ksh: syntax error: `(' unexpected
>Category: ksh
>Environment:
System : OpenBSD 7.6
Details : OpenBSD 7.6-current (GENERIC.MP) #39: Sun Nov 17 11:27:14
CET 2024
catap@matebook.local:/usr/src/sys/arch/amd64/compile/GENERIC.MP
On Sat, 23 Nov 2024 18:55:14 +0100,
Stuart Henderson wrote:
>
> On 2024/11/23 17:06, Kirill A. Korinsky wrote:
> > >
> > > Where is it frozen? On which sleep channel is ffplay sleeping? Can you
> > > enter ddb and get a trace of the ffplay process?
> >
I had dig a bit future and setup a breakpoint at usbd_ref_decr.
It was called from uvideo_vs_start_bulk_thread, but still it crahses:
Breakpoint atusbd_ref_decr: endbr64
ddb{0}> bt
usbd_ref_decr(82177400) at usbd_ref_decr
uvideo_vs_start_bulk_thread(ff
On Sat, 30 Nov 2024 12:05:12 +0100,
Stefan Fritsch wrote:
>
> please check in syslog if vmd logs anything about what is wrong.
>
Sorry, I've missed that. /var/log/messages full of lines like this:
Nov 28 17:40:51 matebook vmd[34724]: vionet_rx: invalid descriptor state
Nov 28 17
On Sun, 24 Nov 2024 15:34:30 +0100,
Martin Pieuchot wrote:
>
> On 23/11/24(Sat) 21:45, Kirill A. Korinsky wrote:
> > I had dig a bit future and setup a breakpoint at usbd_ref_decr.
> >
> > It was called from uvideo_vs_start_bulk_thread, but still it crahses:
On Tue, 07 Jan 2025 01:56:27 +0100,
William Rusnack wrote:
>
> Lastly, if there is not opposition to receiving more legitimate bug reports,
> I am planning on auditing unbound and nsd soon.
>
Probably I missread you, but I understand it as you plan to send it here.
Any reason to do it instead h
On Thu, 26 Dec 2024 17:29:30 +0100,
Stuart Henderson wrote:
>
> Diff that can be applied with patch:
> (I added optional braces as it's multi line and I think clearer
> like that).
>
> ok?
>
Doesn't a user who runs validation need access to the keys in /etc/iked/private?
>
> Index: iked.c
> =
>Synopsis: deattach broken webcam leads to crash
>Category: uvideo
>Environment:
System : OpenBSD 7.6
Details : OpenBSD 7.6-current (GENERIC.MP) #44: Fri Nov 22 15:03:48
CET 2024
catap@matebook.local:/usr/src/sys/arch/amd64/compile/GEN
On Sun, 17 Nov 2024 17:52:26 +0100,
Jeremie Courreges-Anglas wrote:
>
> See main.c:
> /* Aliases that are builtin commands in at&t */
> "login=exec login",
>
> I guess a builtin would be slightly cleaner, but it means more code.
>
Indeed, the bug can be reproduced only when I u
Hello Martin,
On Sat, 23 Nov 2024 13:03:07 +0100,
Martin Pieuchot wrote:
>
> Hello Kirill,
>
> On 22/11/24(Fri) 15:31, Kirill A. Korinsky wrote:
> > >Synopsis: deattach broken webcam leads to crash
>
> What do you mean by broken?
>
I mean that here no support of
On Thu, 10 Apr 2025 00:44:04 +0200,
Kirill A. Korinsky wrote:
>
> which runs as follow, and I had attach and detach the display
> between each call of it:
>
I had moved forward and atach and detach external screen multiple times and
it ends in this state:
tmp $ ./a.o
>Synopsis: hotplug USB-C display decreases DisplayWidthMM and
>DisplayHeightMM
>Category: xenocara
>Environment:
System : OpenBSD 7.7
Details : OpenBSD 7.7 (GENERIC.MP) #624: Wed Apr 9 09:38:45 MDT
2025
dera...@amd64.openbsd.org:/usr/s
I'd like to add that adding --dpi X to xrand with a value from Xft.dpi
avoids this issue.
--
wbr, Kirill
>Synopsis: SIGSEGV inside swrast_dri.so from python
>Category: xenocara
>Environment:
System : OpenBSD 7.7
Details : OpenBSD 7.7-current (GENERIC.MP) #370: Sun May 4
01:06:35 MDT 2025
dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/co
>Synopsis: ssh(90208) in free(): bogus pointer (double free?) 0x7009398e6f
>Category: ssh
>Environment:
System : OpenBSD 7.6
Details : OpenBSD 7.6-current (GENERIC.MP) #322: Sat Mar 1
16:43:32 MST 2025
dera...@arm64.openbsd.org:/usr/src
On Wed, 12 Mar 2025 14:58:13 +0100,
Landry Breuil wrote:
>
> and as soon as i closed the jitsi tab in firefox, the laptop hung. so
> this last diff isnt good _at all_ :)
>
> since this is a work laptop, i'll go back to actual work..
>
Ha, I'm hunting down for a while an issue with killing ffpl
On Wed, 12 Mar 2025 14:26:49 +0100,
Landry Breuil wrote:
>
> Le Wed, Mar 12, 2025 at 01:47:09PM +0100, Marcus Glocker a écrit :
> > On Wed, Mar 12, 2025 at 11:30:03AM GMT, Marcus Glocker wrote:
> >
> > > On Wed, Mar 12, 2025 at 10:24:04AM GMT, Landry Breuil wrote:
> > >
> > > > Le Wed, Mar 12,
On Wed, 12 Mar 2025 14:29:21 +0100,
Landry Breuil wrote:
>
> with what i have now (eg the revert above), i have this
>
> Raw : yuyv422 : YUYV : 640x480 320x180 320x240 352x288 424x240
> 640x360 848x480 960x540 1280x720
> Compressed: mjpeg : MJPEG : 640x480 320x180 320x240 352x2
On Wed, 12 Mar 2025 11:30:03 +0100,
Marcus Glocker wrote:
>
> On Wed, Mar 12, 2025 at 10:24:04AM GMT, Landry Breuil wrote:
>
> > Le Wed, Mar 12, 2025 at 10:05:30AM +0100, Landry Breuil a ?crit :
> > > hi,
> > >
> > > updated my t470s from '#564: Tue Feb 25 21:20:18 MST 2025' to '#591: Tue
> > >
>Synopsis: octeon port doesn't update FS time on reboot
>Category: octeon
>Environment:
System : OpenBSD 7.7
Details : OpenBSD 7.7 (GENERIC.MP) #351: Sun Apr 13 18:13:19 MDT
2025
dera...@octeon.openbsd.org:/usr/src/sys/arch/octeon/compil
On Mon, 12 May 2025 19:03:59 +0200,
Lloyd wrote:
>
> Does the EdgeRouter hw lack an onboard real-time clock?
>
> If so it probably defaults to kernel build time if it has no reference
> until it contacts NTP.
>
Base on code it uses fs_time from /.
In the case of /bsd.rd it reads the fs_time w
On Mon, 12 May 2025 19:42:47 +0200,
Crystal Kolipe wrote:
>
> On Mon, May 12, 2025 at 05:03:59PM +, Lloyd wrote:
> > Does the EdgeRouter hw lack an onboard real-time clock?
> >
> > If so it probably defaults to kernel build time if it has no reference
> > until it contacts NTP.
>
> This is
On Tue, 13 May 2025 06:45:04 +0200,
Lloyd wrote:
>
> If it's a problem, and it takes last modified time for /,
> consider creating /etc/rc.shutdown to touch a file in /
>
This device has quite small flash: 4Gb and I use only one / partition
So, it has a lot of updates.
--
wbr, Kirill
On Mon, 12 May 2025 11:40:48 +0200,
Kirill A. Korinsky wrote:
>
> >Synopsis:octeon port doesn't update FS time on reboot
> >Category:octeon
> >Environment:
> System : OpenBSD 7.7
> Details : OpenBSD 7.7 (GENERIC.MP) #351:
Just tested an idea from
https://marc.info/?l=openbsd-misc&m=170525185806712&w=2
The test was:
1. Install a new kernel with inlined diff.
2. Reboot device.
3. Confirm that date is accurate.
4. Disable ntpd.
5. Reboot device again.
Result?
It has date 9th May which is matched the used snapsh
On Tue, 13 May 2025 19:39:33 +0200,
Visa Hankala wrote:
>
> On Tue, May 13, 2025 at 03:15:21PM +0200, Kirill A. Korinsky wrote:
> > Just tested an idea from
> > https://marc.info/?l=openbsd-misc&m=170525185806712&w=2
> >
> > The test was:
> > 1. In
>Synopsis: zzz on Honor Snapdragon leads to broken ufshci
>Category: ufs
>Environment:
System : OpenBSD 7.7
Details : OpenBSD 7.7-current (GENERIC.MP) #41: Fri Aug 1 14:59:06
MDT 2025
dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/co
94 matches
Mail list logo
