On Tue, Dec 02, 2014 at 08:01:49PM -0200, Dâniel Fraga wrote:
> On Tue, 2 Dec 2014 12:56:36 -0800
> "Paul E. McKenney" <paul...@linux.vnet.ibm.com> wrote:
>
> > And I left out a step. Let's make sure that my preempt_disabled() hack
> > to CONFIG_TREE_PREEMPT_RCU=y has the same effect as the Kconfig hack
> > that allowed CONFIG_PREEMPT=y and CONFIG_TREE_PREEMPT_RCU=n. Could you
> > please try out the following patch configured with CONFIG_PREEMPT=y
> > and CONFIG_TREE_PREEMPT_RCU=y?
>
> Of course! I applied your patch to 3.17 stock kernel and after
> stressing it (compiling with -j8 and watching videos on Youtube) to
> trigger the bug I got the following:
Thank you!!!
Was this as difficult to trigger as the version with the Kconfig hack
that used CONFIG_PREEMPT=y and CONFIG_TREE_PREEMPT_RCU=n?
Thanx, Paul
> Dec 2 19:47:25 tux kernel: [ 927.973547] INFO: rcu_preempt detected stalls
> on CPUs/tasks: { 5} (detected by 1, t=60002 jiffies, g=71142, c=71141, q=0)
> Dec 2 19:47:26 tux kernel: [ 927.973553] Task dump for CPU 5:
> Dec 2 19:47:26 tux kernel: [ 927.973555] cc1 R running task
> 0 30691 30680 0x00080008
> Dec 2 19:47:26 tux kernel: [ 927.973558] ffff88021f351bc0 ffff8801d5743f00
> ffffffff8107062a ffff88021f351c38
> Dec 2 19:47:26 tux kernel: [ 927.973560] ffff8801d5743ea8 ffff8800cd3b0000
> ffff8800cd3b041c 0000000000000000
> Dec 2 19:47:26 tux kernel: [ 927.973562] 00007f89b4d7d8e8 00007f89b5939a60
> ffff88021f34d2c0 00007f89b4d7f000
> Dec 2 19:47:26 tux kernel: [ 927.973564] Call Trace:
> Dec 2 19:47:26 tux kernel: [ 927.973573] [<ffffffff8107062a>] ?
> pick_next_task_fair+0x6aa/0x890
> Dec 2 19:47:26 tux kernel: [ 927.973577] [<ffffffff81087483>] ?
> rcu_eqs_enter+0x93/0xa0
> Dec 2 19:47:26 tux kernel: [ 927.973579] [<ffffffff81087f2e>] ?
> rcu_user_enter+0xe/0x10
> Dec 2 19:47:26 tux kernel: [ 927.973582] [<ffffffff8103935a>] ?
> do_page_fault+0x5a/0x70
> Dec 2 19:47:26 tux kernel: [ 927.973585] [<ffffffff8139bed2>] ?
> page_fault+0x22/0x30
> Dec 2 19:47:30 tux kernel: [ 932.471964] CPU1: Core temperature above
> threshold, cpu clock throttled (total events = 820)
> Dec 2 19:47:30 tux kernel: [ 932.471966] CPU6: Package temperature above
> threshold, cpu clock throttled (total events = 2624)
> Dec 2 19:47:30 tux kernel: [ 932.471967] CPU3: Package temperature above
> threshold, cpu clock throttled (total events = 2624)
> Dec 2 19:47:30 tux kernel: [ 932.471968] CPU7: Package temperature above
> threshold, cpu clock throttled (total events = 2624)
> Dec 2 19:47:30 tux kernel: [ 932.471969] CPU0: Package temperature above
> threshold, cpu clock throttled (total events = 2624)
> Dec 2 19:47:30 tux kernel: [ 932.471970] CPU2: Package temperature above
> threshold, cpu clock throttled (total events = 2624)
> Dec 2 19:47:30 tux kernel: [ 932.471978] CPU1: Package temperature above
> threshold, cpu clock throttled (total events = 2624)
> Dec 2 19:47:30 tux kernel: [ 932.472922] CPU1: Core temperature/speed normal
> Dec 2 19:47:30 tux kernel: [ 932.472923] CPU6: Package temperature/speed
> normal
> Dec 2 19:47:31 tux kernel: [ 932.472923] CPU2: Package temperature/speed
> normal
> Dec 2 19:47:31 tux kernel: [ 932.472924] CPU3: Package temperature/speed
> normal
> Dec 2 19:47:31 tux kernel: [ 932.472925] CPU0: Package temperature/speed
> normal
>
> Waiting for your next instructions.
>
> --
> Linux 3.17.0-dirty: Shuffling Zombie Juror
> http://www.youtube.com/DanielFragaBR
> http://exchangewar.info
> Bitcoin: 12H6661yoLDUZaYPdah6urZS5WiXwTAUgL
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
