> Date: Tue, 14 Feb 2023 07:25:18 +0100
> From: Anton Lindqvist
>
> On Tue, Feb 14, 2023 at 01:08:54AM +0100, Alexander Bluhm wrote:
> > Hi,
> >
> > Today I saw this panic on my i386 regress machine.
> >
> > panic: kernel diagnostic assertion "timo || _kernel_lock_held()" failed:
> > file
On Tue, Feb 14, 2023 at 01:08:54AM +0100, Alexander Bluhm wrote:
> Hi,
>
> Today I saw this panic on my i386 regress machine.
>
> panic: kernel diagnostic assertion "timo || _kernel_lock_held()" failed: file
> "/usr/src/sys/kern/kern_synch.c", line 127
Same here on my amd64 and arm64
Hi,
Today I saw this panic on my i386 regress machine.
panic: kernel diagnostic assertion "timo || _kernel_lock_held()" failed: file
"/usr/src/sys/kern/kern_synch.c", line 127
Looks like src/regress/lib/libc/sys/ triggered it. Kernel was built
from some 2023-02-13 source checkout. I will
On Mon, Feb 13, 2023 at 01:31:30PM +0100, Stefan Sperling wrote:
> On Sat, Feb 11, 2023 at 06:32:31PM +0300, Vitaliy Makkoveev wrote:
> > Unfortunately the diff doesn't help. I attached photos with debug
> > information and panic report.
>
> Based on the command code in the firmware trace the
On Sat, Feb 11, 2023 at 06:32:31PM +0300, Vitaliy Makkoveev wrote:
> Unfortunately the diff doesn't help. I attached photos with debug
> information and panic report.
Based on the command code in the firmware trace the error seems to be
caused by the driver sending this command:
#define
