| |||||||||||||
Might this bug be related?Might this bug be related?Posted Oct 17, 2012 12:56 UTC (Wed) by DOT (subscriber, #58786)Parent article: The new visibility of RCU processing
Might this bug be related to the RCU work that is now being done? The computer appears to hang for a some time and it spews messages like this: INFO: rcu_sched detected stalls on CPUs/tasks: { 1} (detected by 0, t=15603 jiffies)
(Log in to post comments)
Might this bug be related? Posted Oct 18, 2012 14:01 UTC (Thu) by PaulMcKenney (subscriber, #9624) [Link] Given that the bug seems to have happened on a 3.2 kernel, I suspect that the kthreading is not responsible. ;-)But here are some commits that have fixed RCU-related CPU stall warning issues in reverse chronological order: c96ea7cf: rcu: Avoid spurious RCU CPU stall warnings * c8020a67: rcu: Protect rcu_node accesses during CPU stall warnings 5fd4dc06: rcu: Avoid rcu_print_detail_task_stall_rnp() segfault a10d206e: rcu: Fix day-one dyntick-idle stall-warning bug * 1c17e4d4: rcu: Prevent uninitialized string in RCU CPU stall info 13cfcca0: rcu: Set RCU CPU stall times via sysfs 2d1dc9a6: rcu: Remove redundant rcu_cpu_stall_suppress declarationThe two commits marked with “*” are the most likely to address this bug.
|
|||||||||||||