Re: port-evbarm/55639: Assertion "anon != NULL && anon->an_ref != 0" fails on evbarm-earmv7hf

[Andreas Gustafsson <gson%gson.org@localhost>]

The following reply was made to PR port-evbarm/55639; it has been noted by GNATS.

From: Andreas Gustafsson <gson%gson.org@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: Martin Husemann <martin%duskware.de@localhost>, chs%NetBSD.org@localhost
Subject: Re: port-evbarm/55639: Assertion "anon != NULL && anon->an_ref != 0" fails on evbarm-earmv7hf
Date: Thu, 3 Sep 2020 16:46:52 +0300

 Earlier, I wrote:
 > The system panics with the message:
 >
 >   panic: kernel diagnostic assertion "uvm_pagelookup(uobj, offset) == NULL || ((a->ar_flags & UVM_PAGE_ARRAY_FILL_DIRTY) != 0 && !uvm_obj_page_dirty_p(pg))" failed: file "/tmp/bracket/build/2020.08.14.09.06.15-evbarm-earmv7hf/src/sys/uvm/uvm_vnode.c", line 321
 
 To clarify, the system paniced with that message testing sources from
 Aug 14 (2020.08.14.09.06.15, 2020.08.14.14.42.44, 2020.08.14.16.53.06).
 
 Testing sources from Aug 16 (2020.08.16.10.31.40) onwards, it's
 panicing with a different message, the one shown in the PR synopsis:
 
   panic: kernel diagnostic assertion "anon != NULL && anon->an_ref != 0" failed: file "/tmp/bracket/build/2020.08.16.10.31.40-evbarm-earmv7hf/src/sys/uvm/uvm_amap.c", line 747
 
 I will run some further tests to determine exactly when the panic
 message changed, but they will take several days to run.
 -- 
 Andreas Gustafsson, gson%gson.org@localhost