>Synopsis: Crash while using ospfd over vxlan
>Category: bug
>Environment:
System : OpenBSD 6.6
Details : OpenBSD 6.6 (GENERIC.MP) #5: Sun Feb 16 01:56:11 MST 2020
r...@syspatch-66-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.
Synopsis: Once a day, my APU1D4 used to crash
Category: kernel
Environment:
System : OpenBSD 6.6
Details : OpenBSD 6.6 (GENERIC.MP) #372: Sat Oct 12 10:56:27 MDT
2019
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.
Both sparc64-1c and sparc64-2c panicked. Apparently they did during startup
before any processes were run. (I had cu running in a tmux for sparc64-1c).
Repeating the upgrade manually via the bsd.rd restored those ldoms to
working order.
--Kurt
sparc64-2c:
ddb{0}> show panic
trap type 0x10 (ille
Yes, clang bsd.rd doesn't work.
Kurt Mosiejczuk wrote:
> Both sparc64-1c and sparc64-2c panicked. Apparently they did during startup
> before any processes were run. (I had cu running in a tmux for sparc64-1c).
>
> Repeating the upgrade manually via the bsd.rd restored those ldoms to
> working
On Thu, Apr 09, 2020 at 12:57:44PM -0600, Theo de Raadt wrote:
> Yes, clang bsd.rd doesn't work.
Just to clarify. The upgrades completed. It was the boot off from bsd
that panicked.
--Kurt
> Kurt Mosiejczuk wrote:
>
> > Both sparc64-1c and sparc64-2c panicked. Apparently they did during startu
Kurt Mosiejczuk wrote:
> On Thu, Apr 09, 2020 at 12:57:44PM -0600, Theo de Raadt wrote:
> > Yes, clang bsd.rd doesn't work.
>
> Just to clarify. The upgrades completed. It was the boot off from bsd
> that panicked.
I guess so. bsd is also too tight on memory.
We go back to gcc kernels until w
On 08/04/2020 06.52, Martin Pieuchot wrote:
It's the same bug as reported by sthen@. Two interfaces in the same subnet
have two identical cloning routes:
I've been able to reproduce systematically the problem with an OpenBSD
virtual machine running the latest snapshot and two vio interfac
