Stack dump on ipipe 4.9.135-7 x86_64

Mauro Salvini mauro.salvini at smigroup.net
Fri Dec 21 16:59:38 CET 2018


On Fri, 2018-12-21 at 16:11 +0100, Mauro Salvini via Xenomai wrote:
> On Fri, 2018-12-21 at 14:51 +0100, Henning Schild wrote:
> > Am Thu, 20 Dec 2018 10:10:29 +0100
> > schrieb Jan Kiszka <jan.kiszka at siemens.com>:
> > 
> > > On 20.12.18 09:28, Mauro Salvini via Xenomai wrote:
> > > > Hi all,
> > > > 
> > > > I'm testing Xenomai 3 on an Intel Braswell board (Atom x5-
> > > > E8000).
> > > > I'm using ipipe kernel at last commit from [1], branch ipipe-
> > > > 4.9.y,
> > > > 64bit build on a Debian Stretch 9.6 64bit.
> > > > Xenomai library is from [2], branch stable/v3.0.x on commit
> > > > bc53d03f (I haven't two last commits but seems not related). I
> > > > tried both 32bit (mixed ABI) and 64bit builds with same
> > > > following
> > > > result.
> > > > 
> > > > I launch:
> > > > 
> > > > xeno-test -l "dohell -s xxx -p yyy -m xxx 90000" -T 90000
> > > > 
> > > > After a variable time (from minutes to hours) from latency test
> > > > start I get a few overruns that I discovered are generated by a
> > > > kernel stack dump (attached to mail the dmesg tail). Latency
> > > > test
> > > > doesn't stop, and after this stackdump never reports other
> > > > overruns
> > > > or latency peaks (seems I need to reboot to reproduce stack).
> > > > 
> > > > I read in this mailing list that on last patches much work has
> > > > done
> > > > on FPU part, should it be related?
> > > > 
> > > > Glad to give other infos if you need.  
> > > 
> > > Thanks for reporting. Maybe we need your config later on, but I'm
> > > first of all looking at the code, see below.
> > > 
> > > In general, it's better to run the kernel with frame-pointers
> > > enabled
> > > to get more reliable backtraces, at least when an error occurs.
> > > 
> > > > 
> > > > Thanks in advance, regards.
> > > > 
> > > > Mauro
> > > > 
> > > > [1] https://gitlab.denx.de/Xenomai/ipipe
> > > > [2] https://gitlab.denx.de/Xenomai/xenomai
> > > > -------------- next part --------------
> > > > [  233.205940] /home/build-user/develop/linux-ipipe-
> > > > 4.9.y/arch/x86/xenomai/include/asm/xenomai/fptest.h:43:
> > > > Warning: Linux is compiled to use FPU in kernel-space. For this
> > > > reason, switchtest can not test using FPU in Linux kernel-
> > > > space.
> > > > [  295.660454] ------------[ cut here ]------------
> > > > [  295.660461]
> > > > WARNING: CPU: 0 PID: 139
> > > > at /home/build-user/develop/linux-ipipe-
> > > > 4.9.y/arch/x86/include/asm/fpu/internal.h:502
> > > > xnarch_leave_root+0x1a4/0x1b0  
> > > 
> > > Henning, the kernel checks fpu->fpregs_active here and finds it
> > > off
> > > while Xenomai looks at fpu.fpstate_active - intentionally or by
> > > accident?
> > 
> > That was by accident. In eager mode they should mostly be in sync,
> > unless when playing the nasty tricks ipipe has to play. I guess
> > there
> > is a path where we tried to "unown" a task that we unowned shortly
> > before. I did not try to find that path, i just sent a patch.
> > 
> > Mauro, since you can reproduce the problem you can probably tell if
> > the
> > patch fixes it.
> 
> Hi Henning,
> 
> I tried the patch but result is the same (see attached stackdump).
> 
> I attached also my config if could help.
> Now I'm compiling a kernel with frame-pointers enabled (as suggested
> by
> Jan).
> 

Hi all,

attached the stackdump with frame-pointers activated (seems very
similar to the previous, but I checked and CONFIG_FRAME_POINTER is
active in config...did I do some mistake?).

Unfortunately, I will not be able to do other tests next weeks (seasons
holidays), but feel free to give me possible tests to do when I'll come
back.

By the way, best wishes to all.

Mauro
-------------- next part --------------
[  145.774418] /home/build-user/develop/linux-ipipe-4.9.y/arch/x86/xenomai/include/asm/xenomai/fptest.h:43: Warning: Linux is compiled to use FPU in kernel-space.
               For this reason, switchtest can not test using FPU in Linux kernel-space.
[  181.969937] ------------[ cut here ]------------
[  181.969944] WARNING: CPU: 0 PID: 139 at /home/build-user/develop/linux-ipipe-4.9.y/arch/x86/include/asm/fpu/internal.h:502 xnarch_leave_root+0x15e/0x1c0
[  181.969971] Modules linked in: msr intel_rapl intel_powerclamp coretemp kvm_intel iTCO_wdt iTCO_vendor_support kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd intel_cstate snd_pcm i915 snd_timer snd soundcore pcspkr lpc_ich mfd_core evdev drm_kms_helper drm fb_sys_fops syscopyarea sysfillrect sysimgblt shpchp sg video button ip_tables x_tables autofs4 ext4 crc16 jbd2 fscrypto mbcache sd_mod hid_generic usbhid hid crc32c_intel i2c_i801 i2c_smbus ahci libahci igb i2c_algo_bit xhci_pci dca ptp sdhci_pci pps_core libata sdhci xhci_hcd usbcore scsi_mod mmc_core fjes [last unloaded: rtnet]
[  181.970170] CPU: 0 PID: 139 Comm: jbd2/sda1-8 Tainted: G        W       4.9.135+ #4
[  181.970173] Hardware name: Default string Default string/Q7-BW, BIOS V1.20#KW050220A 03/16/2018
[  181.970176] I-pipe domain: Xenomai
[  181.970179]  ffff992800b4f998 ffffffff9d959436 0000000000000000 0000000000000000
[  181.970191]  ffffffff9dfcd448 ffff992800b4f9d8 ffffffff9d66fb75 000001f63ac9b940
[  181.970203]  ffff8c40f690a040 ffff8c40f6ae4300 0000000000099f50 0000000000000000
[  181.970215] Call Trace:
[  181.970218]  [<ffffffff9d959436>] dump_stack+0xbc/0xe6
[  181.970221]  [<ffffffff9d66fb75>] __warn+0xd5/0xf0
[  181.970224]  [<ffffffff9d66fcae>] warn_slowpath_null+0x1e/0x20
[  181.970227]  [<ffffffff9d66b5ae>] xnarch_leave_root+0x15e/0x1c0
[  181.970229]  [<ffffffff9d77eb55>] ___xnsched_run+0x405/0x4d0
[  181.970232]  [<ffffffff9d775347>] ? xnclock_tick+0x1d7/0x2b0
[  181.970235]  [<ffffffff9d7779d7>] xnintr_core_clock_handler+0x307/0x310
[  181.970238]  [<ffffffff9d721bbf>] dispatch_irq_head+0x8f/0x120
[  181.970241]  [<ffffffff9d721f72>] __ipipe_dispatch_irq+0xe2/0x1c0
[  181.970244]  [<ffffffff9d63d1da>] __ipipe_handle_irq+0x8a/0x1b0
[  181.970261]  [<ffffffff9dc33f89>] apic_timer_interrupt+0x89/0xb0
[  181.970264]  [<ffffffffc0506f32>] ? crc_24+0xa/0x1e [crc32c_intel]
[  181.970267]  [<ffffffffc0506233>] ? crc32c_pcl_intel_update+0x53/0x60 [crc32c_intel]
[  181.970270]  [<ffffffff9d912e1c>] ? crypto_shash_update+0x3c/0x110
[  181.970273]  [<ffffffffc0408a90>] ? jbd2_journal_commit_transaction+0x9e0/0x1850 [jbd2]
[  181.970276]  [<ffffffff9d6d75fb>] ? lock_timer_base+0x7b/0xa0
[  181.970279]  [<ffffffffc040dc92>] ? kjournald2+0xe2/0x290 [jbd2]
[  181.970282]  [<ffffffff9d6b5110>] ? wake_up_atomic_t+0x30/0x30
[  181.970285]  [<ffffffffc040dbb0>] ? commit_timeout+0x10/0x10 [jbd2]
[  181.970288]  [<ffffffff9d691f4f>] ? kthread+0xff/0x120
[  181.970290]  [<ffffffff9dc32114>] ? __switch_to_asm+0x34/0x70
[  181.970293]  [<ffffffff9d691e50>] ? kthread_park+0x60/0x60
[  181.970296]  [<ffffffff9dc321a5>] ? ret_from_fork+0x55/0x60
[  181.970299] ---[ end trace d6e0629d074b0a24 ]---


More information about the Xenomai mailing list