On 23/02/21(Tue) 07:53, Jonathan Matthew wrote:
> On Mon, Feb 22, 2021 at 01:48:01PM +0000, Stuart Henderson wrote:
> > Not much information on this but it's an unusual one so I thought I'd
> > post in case it's of interest to anyone. (Re-typed from a screen photo,
> > it's remote and used by non-technical people, this is all I have).
> >
> > panic: uao_fin_swhash_elt: can't allocate entry
>
> uao_find_swhash_elt():
>
> /* allocate a new entry for the bucket and init/insert it in */
> elt = pool_get(&uao_swhash_elt_pool, PR_NOWAIT | PR_ZERO);
> /*
> * XXX We cannot sleep here as the hash table might disappear
> * from under our feet. And we run the risk of deadlocking
> * the pagedeamon. In fact this code will only be called by
> * the pagedaemon and allocation will only fail if we
> * exhausted the pagedeamon reserve. In that case we're
> * doomed anyway, so panic.
> */
> if (elt == NULL)
> panic("%s: can't allocate entry", __func__);
>
> so it sounds like the machine was so out of memory it couldn't swap.
Another hypothesis would be a kind of deadlock, showing "ps", "all pools"
and "uvmexp" would help get a better understanding.
