[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
re: PCU panic on V240
> panic: kernel diagnostic assertion "!cpu_intr_p()" failed: file
> "/work/build/src/sys/kern/subr_xcall.c", line 351
[ .. ]
> This is the high priority xcall from subr_pcu.c and
> curcpu()->ci_idepth is zero.
this doesn't make sense. ci_idepth should be zero here, and that
should force cpu_intr_p() to return false, and thus the ASSERT()
shouldn't fire. has something changed ci_idepth between the check
and ddb??? yhuck.
> What is going wrong here?
assuming this has nothing to do with PCU, something very very
strange and unknown.
Main Index |
Thread Index |