From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <1547197070.2322.4.camel@smigroup.net> Subject: FPU warn on ipipe 4.9.146-8 i386 From: Mauro Salvini Date: Fri, 11 Jan 2019 09:57:50 +0100 Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: xenomai Hi all, I'm testing same hardware of [1], with kernel 4.9.146 from ipipe-4.9.y with [2] applied, compiled with ARCH=3Di386 and Xenomai 3.0.7. Launching xeno-test -l "dohell -s xxx -p yyy -m xxx 90000" -T 90000 I got this dump in dmesg, sometimes=C2=A0just after latency starts, sometimes after few seconds (side effect is a max latency value increase): [=C2=A0=C2=A0167.914184] ------------[ cut here ]------------ [=C2=A0=C2=A0167.914208] WARNING: CPU: 0 PID: 606 at /home/build-ws/devel= op/linux-4.9.146/arch/x86/include/asm/fpu/internal.h:511 fpu__restore+0x1= eb/0x2b0 [=C2=A0=C2=A0167.914216] Modules linked in: intel_rapl intel_powerclamp i= TCO_wdt iTCO_vendor_support coretemp kvm_intel kvm irqbypass crc32_pclmul= aesni_intel xts aes_i586 lrw gf128mul ablk_helper cryptd snd_pcm intel_c= state snd_timer evdev snd soundcore i915 pcspkr drm_kms_helper drm fb_sys= _fops syscopyarea sysfillrect sysimgblt shpchp video lpc_ich mfd_core but= ton ip_tables x_tables autofs4 ext4 crc16 jbd2 fscrypto mbcache hid_gener= ic usbhid hid mmc_block crc32c_intel i2c_i801 i2c_smbus igb i2c_algo_bit = xhci_pci ptp pps_core xhci_hcd sdhci_pci sdhci usbcore mmc_core fjes [las= t unloaded: rtnet] [=C2=A0=C2=A0167.914768] CPU: 0 PID: 606 Comm: dohell Not tainted 4.9.146= + #1 [=C2=A0=C2=A0167.914772] Hardware name: Default string Default string/Q7-= BW, BIOS V1.20#KW050220A 03/16/2018 [=C2=A0=C2=A0167.914775] I-pipe domain: Linux [=C2=A0=C2=A0167.914778]=C2=A0=C2=A0f42e5e44 daeffa2d 00000000 db335030 d= ac1ff3b f42e5e74 dac59dea db34504c [=C2=A0=C2=A0167.914800]=C2=A0=C2=A000000000 0000025e db335030 000001ff d= ac1ff3b 000001ff f4291bc0 00000246 [=C2=A0=C2=A0167.914822]=C2=A0=C2=A0f4291c00 f42e5e88 dac59efb 00000009 0= 0000000 00000000 f42e5ea4 dac1ff3b [=C2=A0=C2=A0167.914843] Call Trace: [=C2=A0=C2=A0167.914846]=C2=A0=C2=A0[] dump_stack+0x9f/0xc2 [=C2=A0=C2=A0167.914849]=C2=A0=C2=A0[] ? fpu__restore+0x1eb/0x2= b0 [=C2=A0=C2=A0167.914865]=C2=A0=C2=A0[] __warn+0xea/0x110 [=C2=A0=C2=A0167.914868]=C2=A0=C2=A0[] ? fpu__restore+0x1eb/0x2= b0 [=C2=A0=C2=A0167.914871]=C2=A0=C2=A0[] warn_slowpath_null+0x2b/= 0x30 [=C2=A0=C2=A0167.914874]=C2=A0=C2=A0[] fpu__restore+0x1eb/0x2b0 [=C2=A0=C2=A0167.914877]=C2=A0=C2=A0[] __fpu__restore_sig+0x2ba= /0x680 [=C2=A0=C2=A0167.914879]=C2=A0=C2=A0[] fpu__restore_sig+0x31/0x= 50 [=C2=A0=C2=A0167.914882]=C2=A0=C2=A0[] restore_sigcontext.isra.= 9+0xf2/0x110 [=C2=A0=C2=A0167.914885]=C2=A0=C2=A0[] sys_sigreturn+0xa9/0xc0 [=C2=A0=C2=A0167.914888]=C2=A0=C2=A0[] do_int80_syscall_32+0x85= /0x190 [=C2=A0=C2=A0167.914891]=C2=A0=C2=A0[] entry_INT80_32+0x31/0x31 [=C2=A0=C2=A0167.914898] ---[ end trace e57344f10f300a76 ]--- I found discussion at [3], and applied patch at [4] that comes from it, but result is the same. Starting xeno-test without -l argument result is the same. Launching dohell alone (with same arguments as when launched from xeno- test -l), dump does not appear. Could be a Xenomai-related problem (though the stack seems not concern Xenomai) or it is better to post it on LKML? Thanks in advance, regards Mauro [1] https://xenomai.org/pipermail/xenomai/2018-December/040142.html [2] https://xenomai.org/pipermail/xenomai/2019-January/040172.html [3] https://lore.kernel.org/lkml/20181120102635.ddv3fvavxajjlfqk@linutr onix.de/ [4] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/co mmit/?h=3Dlinux-4.9.y&id=3Dd3741e0390287056011950493a641524f49fa05a