Re: [10.0_STABLE] Hard lock

[Taylor R Campbell <riastradh%NetBSD.org@localhost>]

> Date: Fri, 18 Oct 2024 17:52:24 +0200
> From: BERTRAND Jo�<joel.bertrand%systella.fr@localhost>
> 
> 	I have tested. Same hard lock with iscsi patches from -current.

Exactly what date from current?

In particular, you're using altq, right?  Can you confirm with

ident /netbsd | grep -F cprng_fast.c

(or similarly on whatever kerneel you've booted) whether you're running
with this change?

https://mail-index.netbsd.org/source-changes/2024/10/15/msg153958.html

When the system locks up while running a current kernel, do you get a
heartbeat panic after 15sec?

Do you have a dump device configured?  When the system locks up, is
there any indication of disk activity?  (That might be the system
dumping to disk, which would be useful for diagnostics later -- the
amount of time it takes depends on the size of RAM and the latency of
disk I/O.)

When you said `DIAGNOSTIC doesn't return usable information' in your
original message, what does that mean?  When the system locks up, can
you reset it (note: reset, not power off and back on), and share dmesg
output, which (on reset) should include the previous boot?