Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 21 Aug 2015 00:39:20 +0200
From:      Svatopluk Kraus <onwahe@gmail.com>
To:        Dmitry Marakasov <amdmi3@amdmi3.ru>
Cc:        Adrian Chadd <adrian.chadd@gmail.com>,  "freebsd-arm@FreeBSD.org" <freebsd-arm@freebsd.org>, Ian Lepore <ian@freebsd.org>
Subject:   Re: Instability likely related to new pmap on Cubieboard A10
Message-ID:  <CAFHCsPWYuYkh2EhcYR5XmVRQ-EA9yAP3-W=4wc2jDc9Bfod0-Q@mail.gmail.com>
In-Reply-To: <20150820201020.GC1245@hades.panopticon>
References:  <20150819013834.GD79354@hades.panopticon> <CAJ-VmokJv=nvcEkBogWeNJT65MosxnFcaitWn8FXJu32eahSdw@mail.gmail.com> <20150819120753.GH79354@hades.panopticon> <CAFHCsPVSGuWWY97ac2QVGAE77Lz2gJ12wDLpzH_kNdZsLQxh%2BQ@mail.gmail.com> <20150819134708.GJ79354@hades.panopticon> <CAFHCsPVwZS_rCnvKztg7g2%2BvrOBwQpqpPYyA2=hCLGiiU5=mrQ@mail.gmail.com> <20150819232836.GA1245@hades.panopticon> <CAFHCsPUfMhkCjiip7o6ZwGx4jNb1-Xqptsj9h_CzZ8xtfZswiA@mail.gmail.com> <20150820185417.GB1245@hades.panopticon> <CAFHCsPVrNFEDkq-j99j7a5GDBN2u7kRJRGk6Ggym2v_dre%2BN3A@mail.gmail.com> <20150820201020.GC1245@hades.panopticon>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Aug 20, 2015 at 10:10 PM, Dmitry Marakasov <amdmi3@amdmi3.ru> wrote:
> * Svatopluk Kraus (onwahe@gmail.com) wrote:
>
>> >> If it helps, set it again to 1 and try attached patch, please.
>> >>
>> >> If neither the first nor the seconf attemp will work, can you send me
>> >> output like before but from another panic. I would like to see
>> >> diference.
>> >
>> > Just for the case, with patch and sp_enabled back to 1:
>> >
>> > https://people.freebsd.org/~amdmi3/pmap3.log
>> >
>>
>> Thanks. Meantime, I tried most recent HEAD on pandaboard and
>> beaglebone black and no problem there. Do you have enabled INVARIANTS
>> and INVARIANT_SUPPORT in your config?
>
> I've enabled them at some point - at least last two runs had these
> enabled. Any other way I could help? Maybe I should check if it was
> new pmap commit which caused this, and if not, bisect it?
>

Yes, if you know that some revision of kernel was working, it would be
nice to confirm that.

Next thing is, with KTR option enabled, set mask to KTR_TRAP only and
get me output from "show ktr" after panic or freeze if you can get to
kdb. This way we will know addresses which cause segmentation faults.

 Svata



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFHCsPWYuYkh2EhcYR5XmVRQ-EA9yAP3-W=4wc2jDc9Bfod0-Q>