Re: U2 panic: "!cpu_intr_p()" failed

[David Brownlee <abs%absd.org@localhost>]

On Fri, 28 Jun 2019 at 10:39, Julian Coleman <jdc%coris.org.uk@localhost> wrote:
>
> I see this panic on my Ultra 2 on almost every boot:
>
>   panic: kernel diagnostic assertion "!cpu_intr_p()" failed: file "/usr/cvs/2019-04-01/src/sys/kern/subr_xcall.c", line 436 high priority xcall for function 0x13afdc0
>
> (see dmesg below).  When it doesn't panic here, it detects sd1 (which is the
> same disk type as sd0) and continues.
>
> If it doesn't panic at boot time, it will panic soon after when accessing
> disks (most raidctl commands that read/write will cause it).  I've gone back
> through older kernels and I haven't seen it before Feb 2019.  However, in
> a 2019-02-01 kernel it only happens 1 boot in 10 or so.  Could it be timing
> or locking related?  It looks the same as PR 54138 (although there is a
> backtrace there).

Just curious - does it happen if you disable SMP? (More as a useful
data point than being able to suggest anything towards a fix)

David