"panic: spin lock entropy harvest mutex not in order list"
rwatson at freebsd.org
Mon Oct 11 01:27:56 PDT 2004
On Sun, 10 Oct 2004, Robert Huff wrote:
> About 2000 UTC Sunday I cvsuped system source and rebuilt.
> "make buildworld" went fine. (Log available)
> "make buildkernel" also good. (Log also available)
> I installed the new kernel and rebooted.
> When the system came up, I got:
> Real memory: XXXXXXXXX
> Avail memory: YYYYYYYYY
> panic: spin lock entropy harvest mutex not in order list
> KDB: enter: panic
> [thread 0]
When I committed the rewrite of the /dev/random entropy harvesting
locking, I ommitted to commit the change to subr_witness.c telling witness
about the lock change; witness requires that all spin locks be identified
in the hard-coded lock order (although maybe only if witness skipspin is
off, hence more people not running into it?). I've merged the change to
subr_witness.c as change 1.182 as of a minute or two ago. Please letme
know if that change doesn't fix the problem.
Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
robert at fledge.watson.org Principal Research Scientist, McAfee Research
> at which point neither the USB or PS/2 keyboards were
> recognized. (i.e. no trace or dump)
> I still have a workable machine (and volunteer as poster
> person for why the procedure in the Handbook is correct); I also
> have a debug kernel, dmesg (from the old kernel - no hardware
> changes) and kernel config available on request.
> I checked the mailing list archives and UPDATING and found
> nothing which seemed applicable.
> Have I just caught a hiccup in the development process?
> Robert Huff
> freebsd-current at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
More information about the freebsd-current