Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 14 Apr 2013 20:51:01 +0200
From:      Damjan Marion <damjan.marion@gmail.com>
To:        Warner Losh <imp@bsdimp.com>
Cc:        "freebsd-arm@FreeBSD.org" <freebsd-arm@freebsd.org>
Subject:   Re: __rw_wlock_hard panic on 1st malloc
Message-ID:  <BD1AE699-31B2-4F13-8222-BEB90EE0E57E@gmail.com>
In-Reply-To: <8DE83B01-4508-41C5-B2BD-95A72D0AD963@bsdimp.com>
References:  <DB4E4AA0-91D8-4253-8044-9C33B60E1A3A@gmail.com> <8DE83B01-4508-41C5-B2BD-95A72D0AD963@bsdimp.com>

index | next in thread | previous in thread | raw e-mail


I doubt. init_dynamic_kenv() is called by sysinit as part of standard sysinit sequence and 
it is called after kmeminit().

There is no my custom code except standard parts of initarm initialisation.

Damjan

On Apr 14, 2013, at 7:19 PM, Warner Losh <imp@bsdimp.com> wrote:

> Maybe you are calling malloc before these locks are initialized?
> 
> Warner
> 
> On Apr 14, 2013, at 5:03 AM, Damjan Marion wrote:
> 
>> 
>> Hi,
>> 
>> I'm playing a bit with i.MX6 based board (wandboard) and I have serial console working but
>> now it panics in init_dynamic_kenv() with the following error:
>> 
>> panic: __rw_wlock_hard: recursing but non-recursive rw pmap pv global @ /usr/src/sys/arm/arm/pmap-v6.c:1187
>> 
>> It looks like this is the 1st place where malloc() is called, an malloc returns valid VA
>> but 1st attempt to access that address produces panic above.
>> 
>> Any idea what can be the reason for this or any other hint?
>> 
>> Thanks,
>> 
>> Damjan
>> _______________________________________________
>> freebsd-arm@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-arm
>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"
> 



help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BD1AE699-31B2-4F13-8222-BEB90EE0E57E>