From mboxrd@z Thu Jan 1 00:00:00 1970 From: gilles.chanteperdrix@xenomai.org (Gilles Chanteperdrix) Date: Fri, 2 Oct 2015 19:09:54 +0200 Subject: Unset LOCKDEP and TRACE_IRQFLAGS_SUPPORT In-Reply-To: References: <58262.1443283400@turing-police.cc.vt.edu> <94398.1443315287@turing-police.cc.vt.edu> <98526.1443318800@turing-police.cc.vt.edu> <147623.1443365550@turing-police.cc.vt.edu> Message-ID: <20151002170954.GU31137@hermes.click-hack.org> To: kernelnewbies@lists.kernelnewbies.org List-Id: kernelnewbies.lists.kernelnewbies.org On Fri, Oct 02, 2015 at 09:56:39AM -0600, Jim Cromie wrote: > On Sun, Sep 27, 2015 at 8:52 AM, wrote: > > > On Sun, 27 Sep 2015 15:08:57 +1300, vibnwis said: > > > > > Xenomai patching succeeded but when running one of is test apps, > > "latency" > > > showing > > > > > > > > > >> > 0"000.000| BUG in low_init(): [main] mlockall: Cannot > > > allocate > > > > > > > memory > > > And the mailing list member suggested the following > > > > Is that in dmesg, or output from the test program? > > Is there more output, or is that it? > > > > Personally, if TRACE_IRQFLAGS is causing an issue with mlock, I'd suspect > > a very buggy patch indeed. If it can't tolerate a trace function being > > turned on, there;s probably some very questionable coding in there..... > > > > > > FWIW, I think Xenomai is far better smelling than your quick sniff has told > your olfactory sensors Actually, I think the following answer on the xenomai mailing list: http://xenomai.org/pipermail/xenomai/2015-September/035126.html Should make clear the fact that the answer about TRACE_IRQFLAGS was an answer to the errors in the kernel log, not an answer to the issue with mlockall. -- Gilles. https://click-hack.org