On 11/20/23 15:40, Bjoern A. Zeeb wrote:
On Mon, 20 Nov 2023, Mitchell Horne wrote:
Hi Mitchell,
On 11/16/23 18:21, Bjoern A. Zeeb wrote:
Hi,
I seem to remember changes related to that a while ago but my cache
is miss for the actual change. Are we suppoed to handle this case?
It would be
On Mon, 20 Nov 2023, Mitchell Horne wrote:
Hi Mitchell,
On 11/16/23 18:21, Bjoern A. Zeeb wrote:
Hi,
I seem to remember changes related to that a while ago but my cache
is miss for the actual change. Are we suppoed to handle this case?
It would be nice if "reset" would reset again the
ries :)
I apologize for the delay on this, my ability to finish some of the work I've
started has been spotty this year.
Cheers,
Mitchell
KDB: enter: Break to debugger
[ thread pid 11 tid 15 ]
Stopped at kdb_alt_break_internal+0x180: str xzr, [x19, #896]
db> reset
panic: acquiring bl
; KDB: enter: Break to debugger
> [ thread pid 11 tid 15 ]
> Stopped at kdb_alt_break_internal+0x180: str xzr, [x19, #896]
> db> reset
> panic: acquiring blockable sleep lock with spinlock or critical section held
> (sleep mutex) eventhandler @ /usr/src/sys/kern/subr_
]
Stopped at kdb_alt_break_internal+0x180: str xzr, [x19, #896]
db> reset
panic: acquiring blockable sleep lock with spinlock or critical section held
(sleep mutex) eventhandler @ /usr/src/sys/kern/subr_eventhandler.c:269
cpuid = 2
time = 307
KDB: stack backtrace:
db_trace_self() at db_trace_self
db_trace
