Re: [nohz] 2a16fc93d2c: kernel lockup on idle injection

[Viresh Kumar]

Cc'ing Thomas as well..

On 12 December 2014 at 01:12, Fengguang Wu <fengguang.wu@xxxxxxxxx> wrote:
> Hi Viresh,
>
> We noticed the below lockup regression on commit 2a16fc93d2c ("nohz:
> Avoid tick's double reprogramming in highres mode").
>
> testbox/testcase/testparams: ivb42/idle-inject/60s-200%-10cp
>
> b5e995e671d8e4d7  2a16fc93d2c9568e16d45db77c
> ----------------  --------------------------
>        fail:runs  %reproduction    fail:runs
>            |             |             |
>            :5          100%           1:1     last_state.is_incomplete_run
>            :5          100%           1:1     last_state.running
>
> testbox/testcase/testparams: lkp-sb03/idle-inject/60s-200%-10cp
>
> b5e995e671d8e4d7  2a16fc93d2c9568e16d45db77c
> ----------------  --------------------------
>            :7          100%           1:1     last_state.is_incomplete_run
>            :7          100%           1:1     last_state.running
>
> Where test box ivb42 is Ivy Bridge-EP and lkp-sb03 is Sandy Bridge-EP.
>
> To reproduce:
>
>         apt-get install ruby ruby-oj
>         git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
>         cd lkp-tests
>         bin/setup-local job.yaml # the job file attached in this email
>         bin/run-local   job.yaml
>
> Basically what the test case does is to
>
> - find a Sandy Bridge or newer machine
> - look for a cooling device with type âintel_powerclampâ
> - set cur_state to 10
> - run any CPU extensive workload
>
> Then expect soft lockup. It's very reproducible.

Thanks Fengguang. Yes I am able to reproduce it, but don't know yet what
went wrong..

--
viresh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/