Hi Michael, Indeed this looks bad (stack dump and all), but it is only cosmetic, an INFO kernel stall warning.
We have been seeing this "INFO: rcu_bh detected stall" very rarely, but from time to time. I have seen it recently on my APU2 box. It just so happens, earlier this week I spent much of a day researching this in detail, and it became clear that for a production system like AstLinux we should disable stall warnings by default. Here is the kernel patch: https://sourceforge.net/p/astlinux/code/7679 If you want, the following CLI command will do the same thing at runtime on your current systems before revision 7679. -- echo 1 >/sys/module/rcutree/parameters/rcu_cpu_stall_suppress -- So either ignore the kernel stall warnings for now, or add the above command at startup until the 1.2.7 official release. In my research there were reported cases, (not AstLinux) where stall warnings were causing additional stall warnings and the kernel messages were dragging down the system. I have never seen that with AstLinux. Lonnie On May 20, 2016, at 6:40 PM, Michael Knill <michael.kn...@ipcsolutions.com.au> wrote: > Hi all > > I am running two Astlinux appliances in a VMWare vCloud environment and both > are getting the same errors as follows: > > May 19 12:18:50 CTS-CM-01 user.err kernel: INFO: rcu_bh detected stall on CPU > 1 (t=0 jiffies) > May 19 12:18:50 CTS-CM-01 user.warn kernel: Pid: 0, comm: swapper/1 Tainted: > G O 3.2.66-astlinux #1 > May 19 12:18:50 CTS-CM-01 user.warn kernel: Call Trace: > May 19 12:18:50 CTS-CM-01 user.warn kernel: <IRQ> [<ffffffff8105a940>] > __rcu_pending+0x98/0x38c > May 19 12:18:50 CTS-CM-01 user.warn kernel: [<ffffffff8104b01c>] ? > tick_init_highres+0x12/0x12 > May 19 12:18:50 CTS-CM-01 user.warn kernel: [<ffffffff8105b52e>] > rcu_check_callbacks+0xdc/0x10e > May 19 12:18:50 CTS-CM-01 user.warn kernel: [<ffffffff8103400c>] > update_process_times+0x39/0x6d > May 19 12:18:50 CTS-CM-01 user.warn kernel: [<ffffffff8104b10b>] > tick_sched_timer+0xef/0x10e > May 19 12:18:50 CTS-CM-01 user.warn kernel: [<ffffffff810426ef>] > __run_hrtimer.isra.31+0x52/0xab > May 19 12:18:50 CTS-CM-01 user.warn kernel: [<ffffffff81042aa8>] > hrtimer_interrupt+0xd1/0x1ba > May 19 12:18:50 CTS-CM-01 user.warn kernel: [<ffffffff81014edd>] > smp_apic_timer_interrupt+0x81/0x94 > May 19 12:18:50 CTS-CM-01 user.warn kernel: [<ffffffff812f108b>] > apic_timer_interrupt+0x6b/0x70 > May 19 12:18:50 CTS-CM-01 user.warn kernel: <EOI> [<ffffffff8100813e>] ? > default_idle+0x24/0x39 > May 19 12:18:50 CTS-CM-01 user.warn kernel: [<ffffffff810010fb>] > cpu_idle+0x69/0x7d > May 19 12:18:50 CTS-CM-01 user.warn kernel: [<ffffffff812e2969>] > start_secondary+0x1a8/0x1ac > > > Any ideas? > > Regards > Michael Knill ------------------------------------------------------------------------------ Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
