On Tue, Apr 26, 2022 at 02:32:22AM +, Lucas wrote:
> >Synopsis:`ttyflags -a` hangs the system
> >Category:tty?
> >Environment:
> System : OpenBSD 7.1
> Details : OpenBSD 7.1 (GENERIC.MP) #465: Mon Apr 11 18:03:57 MDT
> 2022
>
> dera...@amd64
>Synopsis: `ttyflags -a` hangs the system
>Category: tty?
>Environment:
System : OpenBSD 7.1
Details : OpenBSD 7.1 (GENERIC.MP) #465: Mon Apr 11 18:03:57 MDT
2022
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> From: Dan Cross
> Date: Sun, 24 Apr 2022 21:12:29 -0400
On a machine of this vintage you probably shouldn't boot using the
legacy BIOS. Try UEFI mode instead.
> >Synopsis: Boot(8) timeouts take excessively long on OnLogic Helix 500.
> >Category: boot, amd64
> >Environment:
> Syst
On Mon, Apr 25, 2022 at 05:49:49PM +0300, Vitaliy Makkoveev wrote:
> > I would suggest to replace the timeout garbage collector with
> > reference counting. This diff is only compile tested as I have no
> > setup for IPsec ids yet. Should work on 7.1 an -current.
> >
> > bluhm
>
> Your diff is
On Mon, Apr 25, 2022 at 05:49:49PM +0300, Vitaliy Makkoveev wrote:
> I guess, this race exposes that the IPL_SOFTNET level is not enough for
> `ipsec_flows_mtx' mutex(9). This mutex(9) protects multiple objects, so
> could get similar panic on other places. I propose to increase the
> `ipsec_flows_
On Mon, Apr 25, 2022 at 04:01:49PM +0200, Alexander Bluhm wrote:
> On Sat, Apr 23, 2022 at 04:48:00PM +0300, kasak wrote:
> > ipsp_ids_gc(0) at ipsp_ids_gc+0xb4
> > softclock_thread(800022baf260) at softclock_thread+0x13b
>
> This code was modified between 7.0 and 7.1. It crashes here:
>
> /
On Sat, Apr 23, 2022 at 04:48:00PM +0300, kasak wrote:
> ipsp_ids_gc(0) at ipsp_ids_gc+0xb4
> softclock_thread(800022baf260) at softclock_thread+0x13b
This code was modified between 7.0 and 7.1. It crashes here:
/usr/src/sys/netinet/ip_ipsp.c:1266
* b4: 41 83 7e 64 00 cmpl
Hi,
When booting OpenBSD on a Lenovo B470e laptop (dmesg below), the
screen becomes garbled once the boot prompt disappears and the kernel
starts. The system remains responsive, however.
For context, this is the output of the `machine gop` command:
Mode 0: 1024 x 768 (stride = 1024)
Mode 1: