[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: diagnostic assertion "anon->an_lock == amap->am_lock"
On Sat, Jun 25, 2011 at 3:28 PM, dieter roelants
> On Fri, 24 Jun 2011 01:48:56 +0000 (UTC)
> yamt%mwd.biglobe.ne.jp@localhost (YAMAMOTO Takashi) wrote:
>> > I'm now running a more recent kernel (from yesterday morning). This
>> > time it hit `"pmap == curpmap" failed: file
>> > "/build/src/sys/arch/x86/x86/pmap.c", line 757`
>> this might be fixed by pmap.c rev.1.126.
> It could very well be, but the assertion in the subject is still
> triggered. Hmm, no, it's not the one in the subject. This time it is.
> "an->an_lock == amap->am_lock" failed: file src/sys/uvm/uvm_amap.c,
> line 1459.
IIUC, this is caused by incorrect reference counting of one of
amaps/anons and/or their locks. I guess we need to apply the
mutex_obj_* changes yamt@ did for an_lock, to am_lock too?
> traces are:
> kind regards
>> YAMAMOTO Takashi
Main Index |
Thread Index |