From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 17 Aug 2018 06:06:19 -0500 (CDT) From: Per Oberg Message-ID: <2057360471.14584235.1534503979924.JavaMail.zimbra@wolfram.com> In-Reply-To: References: <1128666844.14578797.1534496239671.JavaMail.zimbra@wolfram.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Xenomai] Question about kernel warning (Yocto/meta-linux + xenomai homebrew) List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: xenomai > On 2018-08-17 10:57, Per Oberg wrote: > > Hi there > > could someone please help me understand what this warning is: > > [ 2932.508097] ------------[ cut here ]------------ >> [ 2932.514724] WARNING: CPU: 0 PID: 20645 at > > /usr/src/kernel/arch/x86/include/asm/fpu/internal.h:538 fpu__drop+0x19e= /0x200 > > [ 2932.529155] Modules linked in: > > [ 2932.533513] CPU: 0 PID: 20645 Comm: cat Not tainted 4.9.90-xeno-cobo= lt #1 >> [ 2932.542067] Hardware name: Hewlett-Packard HP Z620 Workstation/158A, = BIOS J61 > > v03.65 12/19/2013 > > [ 2932.552955] I-pipe domain: Linux >> [ 2932.557675] ffffc90007f37dc8 ffffffff8143da78 0000000000000000 > > 0000000000000000 >> [ 2932.566582] ffffffff81ba4cc0 ffffc90007f37e08 ffffffff810785c1 > > 0000021a00000000 >> [ 2932.576484] 0000000000025dc0 ffff88041a1d5780 0000000000000246 > > 0000000000000000 > > [ 2932.585818] Call Trace: > > [ 2932.590167] [] dump_stack+0xbf/0xe7 > > [ 2932.593148] [] __warn+0xe1/0x100 > > [ 2932.595426] [] warn_slowpath_null+0x1d/0x20 > > [ 2932.597715] [] fpu__drop+0x19e/0x200 > > [ 2932.600849] [] exit_thread+0xa5/0xc0 > > [ 2932.603976] [] do_exit+0x2bd/0xb40 > > [ 2932.606097] [] ? __do_page_fault+0x285/0x550 > > [ 2932.608534] [] do_group_exit+0x43/0xb0 > > [ 2932.610757] [] SyS_exit_group+0x14/0x20 > > [ 2932.613920] [] do_syscall_64+0x82/0xf0 > > [ 2932.617071] [] entry_SYSCALL_64_after_swapgs+0x58/= 0xc6 > > [ 2932.620705] ---[ end trace 8ef0d875e55c5ad1 ]--- > > At the time of running I was doing > >> dohell 5& > > followed by > >> latency > > Long story: > > Xenomai version is 3.0.7, > > Kernel is 4.9.90-ish >> The kernel is a x86-64 yocto/meta-intel kernel patched with xenomai patc= hes. >> Unfortunately they didn't have their branch merged at Linux 4.9.90 so I = had to >> merge their mainline-linux branch into their project-branch myself, but = there >> were no changes from their part compared to their previous "release-tag"= and >> the merge was mostly ok except for some macros in intel hardware detecti= on code > > for different sound chips. >> Also, patching the xenomai-patches (4.9.90-x86-6 something..) went ok, (= except > > for som stupid whitespace-stuff in a mmu-function). >> I will try with another kernel but I was having some troubles with modul= e > > configuration since the default does not write any modules to the flash= . > I would indeed be helpful if you can reproduce the issue with the > ipipe-4.9 kernel we provide. The yocto-linux kernel is unfortunately not > in a good shape /wrt will-never-go-upstream patches (like yocto is in > general), though those patches should not touch core infrastructure > (AFAIK). What is the added-value of that kernel you would need? > Jan > -- > Siemens AG, Corporate Technology, CT RDA IOT SES-DE > Corporate Competence Center Embedded Linux I have been running xenomai-kernel patched from mainline for a few hours no= w and it does not have the issue as it seems. The problem seemed to trigger quite easily = before so=20 I'm almost confident it's gone.=20 About added value I've never delved deep enough into the world of mainline= linux vs distribution=20 specific kernels to have an informed opinion. For my first attempts I ran i= nto a few kernel panics because=20 of missing drivers and I figured that the meta-intel and yocto defaults wou= ld give a better starting point.=20 Now that I have a working configuration I am considering dropping their ker= nel in favor of a clean one.=20 Thanks Per =C3=96berg=20