On Wed, Nov 12, 2008 at 10:05:08AM +0100, Heiko Carstens wrote: > On Tue, Nov 11, 2008 at 09:34:51AM -0800, Paul E. McKenney wrote: > > On Tue, Nov 11, 2008 at 08:45:23AM -0800, Paul E. McKenney wrote: > > > On Tue, Nov 11, 2008 at 05:14:01PM +0100, Heiko Carstens wrote: > > > > > > Could you please apply the following debug patch (due to Jiangshan and > > > > > > myself)? Then you should be able to build with CONFIG_RCU_TRACE, > > > > > > then mount debugfs after boot, for example, on /debug. This will > > > > > > create a /debug/rcu directory with three files, "rcucb", "rcu_data", > > > > > > and "rcu_bh_data". Since you are still able to log in, could you > > > > > > please send the contents of these three files? > > > > > > > > > > > > Thanx, Paul > > > > > > > > > > This time with the patch actually attached... Thanks to Peter Z. > > > > > for alerting me to my omission. > > > > > > > > Well, your patch doesn't apply on git head. However I used preemptible > > > > RCU instead and had tracing enabled. > > > > > > Were you using preemptible RCU earlier as well? Raphael was using > > > classic RCU. Don't get me wrong, all problems need fixing, just trying > > > to make sure I understand where the problems are occurring. > > Indeed, my fault. I just try to reproduce a cpu hotplug bug with classic RCU > and cpu hotplug stress test, but no luck so far. OK, then my next step will be to send Rafael an updated version of my hierarchical RCU, which is more robust than classic RCU against online/offline stress tests. On the machines I have access to, anyway. ;-) Then I will look at preemptable RCU, which undoubtably needs some of the same help that I have been giving to hierarchical RCU. Manfred thus wins the clairvoyance award! Thanx, Paul -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
