linux-kernel - [nohz] 2a16fc93d2c: kernel lockup on idle injection

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 11 Dec 2014 11:42:04 -0800
From:	Fengguang Wu <fengguang.wu@...el.com>
To:	Viresh Kumar <viresh.kumar@...aro.org>
Cc:	Frederic Weisbecker <frederic@...nel.org>,
	"Pan, Jacob jun" <jacob.jun.pan@...el.com>,
	LKML <linux-kernel@...r.kernel.org>, lkp@...org
Subject: [nohz] 2a16fc93d2c: kernel lockup on idle injection

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

View attachment "job.yaml" of type "text/plain" (859 bytes)

View attachment "x86_64-powerclamp" of type "text/plain" (105245 bytes)