[lkp] [writeback] 074e46e1ad: fio.write_bw_MBps -10.5% regression
by kernel test robot
FYI, we noticed fio.write_bw_MBps -10.5% regression due to commit:
commit 074e46e1aded0ac0474a5db4d50d514d9dc42e78 ("writeback: throttle buffered writeback")
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git wb-buf-throttle
in testcase: fio-basic
on test machine: lkp-bdw-ep2: threads Broadwell-EP with 128G memory
with following conditions: bs=4k/cpufreq_governor=performance/disk=1SSD/fs=xfs/ioengine=sync/nr_task=8/runtime=300/rw=write/test_size=512g
Details are as below:
-------------------------------------------------------------------------------------------------->
=========================================================================================
bs/compiler/cpufreq_governor/disk/fs/ioengine/kconfig/nr_task/rootfs/runtime/rw/tbox_group/test_size/testcase:
4k/gcc-4.9/performance/1SSD/xfs/sync/x86_64-rhel/8/debian-x86_64-2015-02-07.cgz/300/write/lkp-bdw-ep2/512g/fio-basic
commit:
565d33b77b63e5f70357ebf97c4141044854f621
074e46e1aded0ac0474a5db4d50d514d9dc42e78
565d33b77b63e5f7 074e46e1aded0ac0474a5db4d5
---------------- --------------------------
fail:runs %reproduction fail:runs
| | |
1:4 -25% :5 kmsg.ENERGY_PERF_BIAS:Set_to'normal',was'performance'
1:4 -25% :5 kmsg.ENERGY_PERF_BIAS:View_and_update_with_x86_energy_perf_policy(#)
%stddev %change %stddev
\ | \
289.61 ± 0% +3.7% 300.36 ± 0% fio.time.elapsed_time
289.61 ± 0% +3.7% 300.36 ± 0% fio.time.elapsed_time.max
1.074e+09 ± 0% -7.1% 9.971e+08 ± 0% fio.time.file_system_outputs
3446 ± 9% -64.2% 1234 ± 27% fio.time.involuntary_context_switches
105.50 ± 0% -12.8% 92.00 ± 0% fio.time.percent_of_cpu_this_job_got
268.34 ± 0% -10.4% 240.47 ± 1% fio.time.system_time
98347 ± 0% +4.6% 102892 ± 0% fio.time.voluntary_context_switches
1812 ± 0% -10.5% 1622 ± 0% fio.write_bw_MBps
463987 ± 0% -10.5% 415407 ± 0% fio.write_iops
239.56 ± 0% -1.9% 235.12 ± 0% pmeter.Average_Active_Power
1944 ± 0% -8.8% 1773 ± 0% pmeter.performance_per_watt
3446 ± 9% -64.2% 1234 ± 27% time.involuntary_context_switches
105.50 ± 0% -12.8% 92.00 ± 0% time.percent_of_cpu_this_job_got
268.34 ± 0% -10.4% 240.47 ± 1% time.system_time
1774732 ± 0% -10.9% 1581981 ± 0% vmstat.io.bo
8570 ± 1% -48.5% 4417 ± 1% vmstat.system.cs
17991 ± 0% -11.1% 15999 ± 0% vmstat.system.in
31090 ± 2% -8.5% 28447 ± 1% meminfo.Active(anon)
7169 ± 12% -32.5% 4839 ± 0% meminfo.AnonHugePages
28207 ± 3% -8.3% 25865 ± 1% meminfo.AnonPages
969710 ± 0% -12.9% 844795 ± 0% meminfo.Writeback
4437 ± 22% -32.7% 2986 ± 24% numa-vmstat.node0.nr_active_anon
3915 ± 19% -27.6% 2835 ± 18% numa-vmstat.node0.nr_anon_pages
125910 ± 6% -14.5% 107612 ± 7% numa-vmstat.node0.nr_writeback
17293 ± 5% -6.5% 16170 ± 5% numa-vmstat.node1.nr_slab_unreclaimable
120890 ± 5% -14.7% 103101 ± 8% numa-vmstat.node1.nr_writeback
1.837e+08 ± 5% +12.8% 2.072e+08 ± 5% cpuidle.C1-BDW.time
2471919 ± 1% +15.3% 2849758 ± 3% cpuidle.C1-BDW.usage
1.565e+08 ± 11% -13.7% 1.35e+08 ± 10% cpuidle.C1E-BDW.time
2.784e+08 ± 16% -80.3% 54791144 ± 18% cpuidle.C3-BDW.time
380002 ± 5% -24.9% 285251 ± 10% cpuidle.C3-BDW.usage
1340681 ± 2% -32.0% 911539 ± 7% cpuidle.C6-BDW.usage
71772 ± 6% -9.0% 65308 ± 4% numa-meminfo.node0.Active
17749 ± 22% -32.7% 11947 ± 24% numa-meminfo.node0.Active(anon)
5249 ± 49% -66.0% 1786 ±123% numa-meminfo.node0.AnonHugePages
15662 ± 19% -27.6% 11342 ± 18% numa-meminfo.node0.AnonPages
503521 ± 6% -14.1% 432594 ± 7% numa-meminfo.node0.Writeback
69173 ± 5% -6.5% 64685 ± 5% numa-meminfo.node1.SUnreclaim
483701 ± 5% -14.7% 412545 ± 8% numa-meminfo.node1.Writeback
1.77 ± 1% -14.4% 1.52 ± 1% turbostat.%Busy
59.50 ± 1% -13.6% 51.40 ± 0% turbostat.Avg_MHz
6.52 ± 2% -17.7% 5.36 ± 2% turbostat.CPU%c1
1.47 ± 20% -82.3% 0.26 ± 23% turbostat.CPU%c3
0.24 ± 48% +52.4% 0.36 ± 5% turbostat.Pkg%pc6
93.44 ± 0% -2.6% 90.99 ± 0% turbostat.PkgWatt
58.25 ± 0% -1.8% 57.22 ± 1% turbostat.RAMWatt
675.50 ± 6% -46.5% 361.60 ± 7% proc-vmstat.kswapd_low_wmark_hit_quickly
7768 ± 2% -8.5% 7108 ± 1% proc-vmstat.nr_active_anon
7047 ± 3% -8.3% 6463 ± 1% proc-vmstat.nr_anon_pages
242465 ± 0% -12.8% 211436 ± 0% proc-vmstat.nr_writeback
1544 ± 5% -9.8% 1393 ± 1% proc-vmstat.pgactivate
1.058e+08 ± 0% -9.4% 95845408 ± 0% proc-vmstat.pgfree
1.015e+08 ± 0% -9.4% 91969429 ± 0% proc-vmstat.pgscan_kswapd_normal
1.014e+08 ± 0% -9.4% 91873948 ± 0% proc-vmstat.pgsteal_kswapd_normal
1.76 ± 3% -23.4% 1.35 ± 4% perf-profile.cycles-pp.blk_mq_make_request
18.28 ± 5% -14.4% 15.64 ± 7% perf-profile.cycles-pp.call_cpuidle
19.04 ± 5% -14.1% 16.34 ± 7% perf-profile.cycles-pp.cpu_startup_entry
18.27 ± 5% -14.5% 15.63 ± 7% perf-profile.cycles-pp.cpuidle_enter
15.93 ± 5% -15.3% 13.50 ± 9% perf-profile.cycles-pp.cpuidle_enter_state
1.79 ± 3% -22.5% 1.39 ± 2% perf-profile.cycles-pp.generic_make_request
15.70 ± 5% -16.1% 13.17 ± 10% perf-profile.cycles-pp.intel_idle
18.21 ± 5% -15.5% 15.40 ± 7% perf-profile.cycles-pp.start_secondary
1.79 ± 3% -22.5% 1.39 ± 2% perf-profile.cycles-pp.submit_bio
2.56 ± 0% -22.5% 1.99 ± 2% perf-profile.cycles-pp.xfs_submit_ioend
1.80 ± 3% -22.5% 1.39 ± 2% perf-profile.cycles-pp.xfs_submit_ioend_bio
6238 ± 1% -14.0% 5367 ± 3% slabinfo.kmalloc-1024.active_objs
6430 ± 1% -15.4% 5442 ± 3% slabinfo.kmalloc-1024.num_objs
25207 ± 3% -65.5% 8700 ± 2% slabinfo.kmalloc-128.active_objs
398.75 ± 3% -66.0% 135.40 ± 1% slabinfo.kmalloc-128.active_slabs
25559 ± 3% -65.9% 8709 ± 1% slabinfo.kmalloc-128.num_objs
398.75 ± 3% -66.0% 135.40 ± 1% slabinfo.kmalloc-128.num_slabs
14482 ± 0% -35.4% 9349 ± 1% slabinfo.kmalloc-192.active_objs
347.75 ± 0% -36.0% 222.40 ± 1% slabinfo.kmalloc-192.active_slabs
14626 ± 0% -36.0% 9360 ± 1% slabinfo.kmalloc-192.num_objs
347.75 ± 0% -36.0% 222.40 ± 1% slabinfo.kmalloc-192.num_slabs
1644 ± 1% -10.0% 1480 ± 1% slabinfo.kmalloc-4096.active_objs
1703 ± 1% -9.5% 1541 ± 1% slabinfo.kmalloc-4096.num_objs
22806 ± 2% -9.4% 20665 ± 3% slabinfo.kmalloc-512.active_objs
23061 ± 3% -10.4% 20670 ± 3% slabinfo.kmalloc-512.num_objs
49871 ± 0% -16.9% 41459 ± 0% slabinfo.kmalloc-64.active_objs
783.00 ± 0% -17.0% 649.80 ± 0% slabinfo.kmalloc-64.active_slabs
50152 ± 0% -17.1% 41598 ± 0% slabinfo.kmalloc-64.num_objs
783.00 ± 0% -17.0% 649.80 ± 0% slabinfo.kmalloc-64.num_slabs
22015 ± 1% -20.7% 17458 ± 4% slabinfo.kmalloc-96.active_objs
529.25 ± 1% -20.8% 419.40 ± 4% slabinfo.kmalloc-96.active_slabs
22233 ± 1% -20.7% 17632 ± 4% slabinfo.kmalloc-96.num_objs
529.25 ± 1% -20.8% 419.40 ± 4% slabinfo.kmalloc-96.num_slabs
34.21 ±154% -93.6% 2.21 ± 38% sched_debug.cfs_rq:/.runnable_load_avg.avg
2872 ±161% -96.2% 108.07 ± 44% sched_debug.cfs_rq:/.runnable_load_avg.max
306.53 ±160% -95.7% 13.25 ± 41% sched_debug.cfs_rq:/.runnable_load_avg.stddev
34.84 ± 9% -21.3% 27.43 ± 3% sched_debug.cfs_rq:/.util_avg.avg
471.10 ± 13% -17.3% 389.73 ± 6% sched_debug.cfs_rq:/.util_avg.max
83.48 ± 6% -18.1% 68.41 ± 3% sched_debug.cfs_rq:/.util_avg.stddev
350786 ± 3% +32.0% 463179 ± 9% sched_debug.cpu.avg_idle.min
165474 ± 9% -23.8% 126079 ± 12% sched_debug.cpu.avg_idle.stddev
167991 ± 2% +19.6% 200863 ± 0% sched_debug.cpu.clock.avg
167997 ± 2% +19.6% 200869 ± 0% sched_debug.cpu.clock.max
167942 ± 2% +19.6% 200832 ± 0% sched_debug.cpu.clock.min
8.46 ± 23% -28.8% 6.02 ± 21% sched_debug.cpu.clock.stddev
167991 ± 2% +19.6% 200863 ± 0% sched_debug.cpu.clock_task.avg
167997 ± 2% +19.6% 200869 ± 0% sched_debug.cpu.clock_task.max
167942 ± 2% +19.6% 200832 ± 0% sched_debug.cpu.clock_task.min
8.46 ± 23% -28.8% 6.02 ± 21% sched_debug.cpu.clock_task.stddev
3039 ±153% -92.6% 224.07 ± 35% sched_debug.cpu.cpu_load[0].max
2930 ±155% -93.4% 192.50 ± 23% sched_debug.cpu.cpu_load[1].max
316.33 ±152% -91.6% 26.43 ± 24% sched_debug.cpu.cpu_load[1].stddev
34.90 ±142% -87.2% 4.47 ± 12% sched_debug.cpu.cpu_load[2].avg
2792 ±157% -93.9% 169.40 ± 19% sched_debug.cpu.cpu_load[2].max
300.71 ±154% -92.6% 22.15 ± 17% sched_debug.cpu.cpu_load[2].stddev
32.00 ±144% -88.4% 3.70 ± 10% sched_debug.cpu.cpu_load[3].avg
2573 ±157% -94.2% 150.10 ± 23% sched_debug.cpu.cpu_load[3].max
276.30 ±155% -93.2% 18.91 ± 17% sched_debug.cpu.cpu_load[3].stddev
26.92 ±143% -87.8% 3.28 ± 7% sched_debug.cpu.cpu_load[4].avg
2160 ±157% -93.3% 145.60 ± 19% sched_debug.cpu.cpu_load[4].max
231.48 ±155% -92.5% 17.47 ± 15% sched_debug.cpu.cpu_load[4].stddev
12611 ± 2% -33.4% 8396 ± 2% sched_debug.cpu.nr_switches.avg
68299 ± 7% -37.6% 42632 ± 11% sched_debug.cpu.nr_switches.max
14204 ± 2% -38.9% 8675 ± 1% sched_debug.cpu.nr_switches.stddev
13.50 ± 13% +95.1% 26.33 ± 15% sched_debug.cpu.nr_uninterruptible.max
-30.65 ±-20% +63.9% -50.23 ±-17% sched_debug.cpu.nr_uninterruptible.min
6.48 ± 7% +55.3% 10.07 ± 7% sched_debug.cpu.nr_uninterruptible.stddev
167990 ± 2% +19.6% 200861 ± 0% sched_debug.cpu_clk
164597 ± 2% +19.9% 197433 ± 0% sched_debug.ktime
167990 ± 2% +19.6% 200861 ± 0% sched_debug.sched_clk
fio.write_bw_MBps
1850 ++-------------------------------------------------------------------+
| .*..*.*.. |
*. *..*..*.*..*..*.. .*..*..*..*.*..*..*..*.*..*.. .*.*..*..*
1800 ++ * *. |
| |
| |
1750 ++ |
| |
1700 ++ |
| |
| |
1650 ++ |
| |
O O O O O |
1600 ++-------------------------------------------------------------------+
fio.write_iops
470000 ++------*----------------------------------------------------------+
*..*.*. *.*..*..*.*..*.. .*.. .*. .*..*.*.. .*..*.*..*
460000 ++ *.*. *. *. *..*.*. |
| |
| |
450000 ++ |
| |
440000 ++ |
| |
430000 ++ |
| |
| |
420000 ++ |
O O O O O |
410000 ++-----------------------------------------------------------------+
turbostat.Avg_MHz
75 ++---------------------------------------------------------------------+
| |
| .*..*..*.*.. |
70 *+ |
| *..* |
| : |
65 ++ : |
| : |
60 ++ : .*.. .*..*.. .*.. .*
| *..*..* *..*. *.*. *..*..*..*.*..*..*. |
| |
55 ++ |
| |
O O O O O |
50 ++---------------------------------------------------------------------+
turbostat._Busy
2.2 ++--------------------------------------------------------------------+
| .*..*. |
2.1 *+ *..*.. |
2 ++ .* |
| *. : |
1.9 ++ : |
| : |
1.8 ++ : .*..*.. .*. .*
| *.*..*..*..*..* *..*. *..*..*..*..*.*..*. |
1.7 ++ |
1.6 ++ |
| O |
1.5 O+ O O O |
| |
1.4 ++--------------------------------------------------------------------+
turbostat.CPU_c3
2 ++--------------------*-----------------------------------------*-----+
1.8 ++ :+ :: |
| *.. : + *.. .*. : : |
1.6 ++ .. : *.. + *. .*.. *. *.. : : |
1.4 ++ *. .* * + *. .. *..*..*.. : *..*
| .. *..*. * * : |
1.2 *+.* * |
1 ++ |
0.8 ++ |
| |
0.6 ++ |
0.4 ++ |
| O O O |
0.2 O+ O |
0 ++--------------------------------------------------------------------+
fio.time.system_time
285 ++--------------------------------------------------------------------+
280 ++ *.. * |
| + *. .* :: |
275 ++ *. : .*.. * : : |
270 *+ : * *.. : : : : .*.*..*..|
| : .. : : .*.. : *.. .*. |
265 ++ *..* *.. : *. *.. : .*. *
260 ++ * * *. |
255 ++ |
| |
250 ++ |
245 ++ O |
| O O |
240 ++ O |
235 O+--------------------------------------------------------------------+
fio.time.percent_of_cpu_this_job_got
110 ++-*--------------------------------------------*---------------------+
108 ++. *.*..* * : : |
* : .*.. : : : : |
106 ++ : * *.. : : .*.. : * .*.*..*..|
104 ++ : .. : *. : + .*. *
| *..* *..* *..* + .*. |
102 ++ *. |
100 ++ |
98 ++ |
| |
96 ++ |
94 ++ |
| O O |
92 O+ O O |
90 ++--------------------------------------------------------------------+
fio.time.elapsed_time
302 ++--------------------------------------------------------------------+
O O O O O |
300 ++ |
298 ++ |
| |
296 ++ |
| |
294 ++ |
| |
292 ++ *.. .*.. |
290 ++ .. *.. .*.. .*.. *..*. |
| .*..*..*.*..* * *. *..*. .. *.*..*..*
288 *+. .*. * |
| *..*.*. |
286 ++--------------------------------------------------------------------+
fio.time.elapsed_time.max
302 ++--------------------------------------------------------------------+
O O O O O |
300 ++ |
298 ++ |
| |
296 ++ |
| |
294 ++ |
| |
292 ++ *.. .*.. |
290 ++ .. *.. .*.. .*.. *..*. |
| .*..*..*.*..* * *. *..*. .. *.*..*..*
288 *+. .*. * |
| *..*.*. |
286 ++--------------------------------------------------------------------+
fio.time.voluntary_context_switches
104000 ++-----------------------------------------------------------------+
| |
103000 O+ O O O O |
102000 ++ |
| |
101000 ++ |
| |
100000 ++ |
| |
99000 ++ .*. .*.. *.. .*.. |
98000 ++ *..*..*.*..*. *..*..*..* *..*. .. * *..*.*..*
| + * |
97000 *+.*.*..*..* |
| |
96000 ++-----------------------------------------------------------------+
fio.time.file_system_outputs
1.08e+09 ++---------------------------------------------------------------+
*..*.*..*.*..*..*.*..*.*..*..*.*..*.*..*..*.*..*.*..*..*.*..*.*..*
1.07e+09 ++ |
1.06e+09 ++ |
| |
1.05e+09 ++ |
1.04e+09 ++ |
| |
1.03e+09 ++ |
1.02e+09 ++ |
| |
1.01e+09 ++ |
1e+09 ++ |
O O O O O |
9.9e+08 ++---------------------------------------------------------------+
[*] bisect-good sample
[O] bisect-bad sample
To reproduce:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
cd lkp-tests
bin/lkp install job.yaml # job file is attached in this email
bin/lkp run job.yaml
Disclaimer:
Results have been estimated based on internal Intel analysis and are provided
for informational purposes only. Any difference in system hardware or software
design or configuration may affect actual performance.
Thanks,
Xiaolong
4 years, 11 months
[lkp] [ext4] c42b993e20: WARNING: CPU: 4 PID: 716 at lib/kobject.c:690 kobject_put+0x4b/0x50
by kernel test robot
FYI, we noticed the following commit:
https://github.com/0day-ci/linux Goldwyn-Rodrigues/kobject-in-sysfs-superblock/20160513-021915
commit c42b993e205c4609db822de74464597564f1b1f7 ("ext4: Let fs create the sysfs entries")
in testcase: ltp
on test machine: nhm-white2: 8 threads Nehalem with 4G memory
caused below changes:
+------------------------------------------+------------+------------+
| | a8f69dff3d | c42b993e20 |
+------------------------------------------+------------+------------+
| boot_successes | 4 | 3 |
| boot_failures | 0 | 4 |
| WARNING:at_lib/kobject.c:#kobject_put | 0 | 4 |
| BUG:unable_to_handle_kernel | 0 | 4 |
| Oops | 0 | 4 |
| RIP:__list_add | 0 | 4 |
| Kernel_panic-not_syncing:Fatal_exception | 0 | 4 |
+------------------------------------------+------------+------------+
[ 20.135211] EXT4-fs (loop0): mounting ext2 file system using the ext4 subsystem
[ 20.135944] EXT4-fs (loop0): mounted filesystem without journal. Opts: (null)
[ 20.147798] ------------[ cut here ]------------
[ 20.148094] WARNING: CPU: 4 PID: 716 at lib/kobject.c:690 kobject_put+0x4b/0x50
[ 20.148582] kobject: '(null)' (ffff88011d548190): is not initialized, yet kobject_put() is being called.
[ 20.149104] Modules linked in: loop rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver netconsole sg sr_mod cdrom sd_mod dcdbas coretemp kvm_intel kvm irqbypass crc32c_intel i7core_edac snd_hda_codec_realtek serio_raw pcspkr ata_generic pata_acpi snd_hda_codec_generic edac_core ata_piix libata snd_hda_codec_hdmi usb_storage snd_hda_intel snd_hda_codec firewire_ohci snd_hda_core firewire_core crc_itu_t snd_hwdep snd_pcm snd_timer snd soundcore shpchp acpi_cpufreq broadcom bcm_phy_lib
[ 20.152706] CPU: 4 PID: 716 Comm: access06 Not tainted 4.6.0-rc7-00008-gc42b993e #4
[ 20.153200] Hardware name: Dell Inc. Studio XPS 8000/0X231R, BIOS A01 08/11/2009
[ 20.153637] 0000000000000000 ffff88008b1b3d18 ffffffff8142ea6a ffff88008b1b3d68
[ 20.154205] 0000000000000000 ffff88008b1b3d58 ffffffff8107b9c1 000002b281188307
[ 20.154774] ffff88011d548190 ffff88011d548200 ffff88011d548800 0000000000000000
[ 20.155343] Call Trace:
[ 20.155535] [<ffffffff8142ea6a>] dump_stack+0x63/0x89
[ 20.155827] [<ffffffff8107b9c1>] __warn+0xd1/0xf0
[ 20.156154] [<ffffffff8107ba2f>] warn_slowpath_fmt+0x4f/0x60
[ 20.156469] [<ffffffff812580e1>] ? mb_cache_destroy+0x101/0x140
[ 20.156792] [<ffffffff814311db>] kobject_put+0x4b/0x50
[ 20.157088] [<ffffffff812a8eeb>] ext4_put_super+0x28b/0x340
[ 20.157399] [<ffffffff811fdf4a>] generic_shutdown_super+0x8a/0x130
[ 20.157731] [<ffffffff811fe077>] kill_block_super+0x27/0x70
[ 20.158041] [<ffffffff811fd963>] deactivate_locked_super+0x43/0x70
[ 20.158373] [<ffffffff811fd9ec>] deactivate_super+0x5c/0x60
[ 20.158685] [<ffffffff8121b06f>] cleanup_mnt+0x3f/0x90
[ 20.160796] [<ffffffff8121b102>] __cleanup_mnt+0x12/0x20
[ 20.161097] [<ffffffff81099516>] task_work_run+0x76/0xb0
[ 20.161398] [<ffffffff81003242>] exit_to_usermode_loop+0xc2/0xd0
[ 20.161725] [<ffffffff81003bd5>] syscall_return_slowpath+0xf5/0x180
[ 20.162063] [<ffffffff818fb53a>] entry_SYSCALL_64_fastpath+0xa2/0xa4
[ 20.162463] ---[ end trace ce6b70e95bff5208 ]---
[ 20.162741] BUG: unable to handle kernel NULL pointer dereference at (null)
To reproduce:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
cd lkp-tests
bin/lkp install job.yaml # job file is attached in this email
bin/lkp run job.yaml
Thanks,
Xiaolong
4 years, 11 months
[lkp] [Btrfs] 2e78c927d7: WARNING: CPU: 0 PID: 2145 at fs/btrfs/inode.c:9113 btrfs_destroy_inode+0x254/0x2c0 [btrfs]()
by kernel test robot
FYI, we noticed the following commit:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
commit 2e78c927d79333f299a8ac81c2fd2952caeef335 ("Btrfs: __btrfs_buffered_write: Reserve/release extents aligned to block size")
on test machine: lkp-ws02: threads Westmere-EP with 16G memory
caused below changes:
<12>
[ 42.862819] run fstests generic/127 at 2016-03-17 20:23:35
<4>[ 1224.626228] ------------[ cut here ]------------
<4>[ 1224.631015] WARNING: CPU: 0 PID: 2145 at fs/btrfs/inode.c:9113 btrfs_destroy_inode+0x254/0x2c0 [btrfs]()
<4>[ 1224.642679] Modules linked in: dm_mod btrfs xor raid6_pq ses enclosure ipmi_devintf rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver sg sr_mod cdrom ata_generic sd_mod pata_acpi coretemp kvm_intel mptsas mptscsih mptbase kvm irqbypass crct10dif_pclmul snd_pcm ahci snd_timer crc32_pclmul libahci pata_jmicron crc32c_intel scsi_transport_sas snd soundcore aesni_intel lrw gf128mul glue_helper ppdev pcspkr serio_raw libata ipmi_si ablk_helper i7core_edac shpchp cryptd parport_pc edac_core parport ipmi_msghandler acpi_cpufreq
<4>[ 1224.691853] CPU: 0 PID: 2145 Comm: umount Not tainted 4.4.0-rc6-00122-g2e78c92 #1
<4>[ 1224.699638] Hardware name: Supermicro X8DTN/X8DTN, BIOS 4.6.3 01/06/2010
<47>
[ 1224.700052] systemd-journald[291]: Compressed data object 519 -> 436
<4>[ 1224.713053] ffffffffa051bd30 ffff88022889bcb0 ffffffff8140cce2 0000000000000000
<4>[ 1224.720978] ffff88022889bce8 ffffffff81078736 ffff88022b6801c8 ffff88022b6801c8
<4>[ 1224.728840] ffff88043ac42000 ffff88042bea3ce8 ffff88042bea3ce8 ffff88022889bcf8
<4>[ 1224.736719] Call Trace:
<4>[ 1224.739359] [<ffffffff8140cce2>] dump_stack+0x4b/0x69
<4>[ 1224.744684] [<ffffffff81078736>] warn_slowpath_common+0x86/0xc0
<4>[ 1224.750879] [<ffffffff8107882a>] warn_slowpath_null+0x1a/0x20
<4>[ 1224.756913] [<ffffffffa04a6e34>] btrfs_destroy_inode+0x254/0x2c0 [btrfs]
<4>[ 1224.763891] [<ffffffff81200d28>] destroy_inode+0x38/0x60
<4>[ 1224.769476] [<ffffffff81201262>] evict+0x132/0x190
<4>[ 1224.774539] [<ffffffff812012f7>] dispose_list+0x37/0x60
<4>[ 1224.780046] [<ffffffff812028aa>] evict_inodes+0x16a/0x180
<4>[ 1224.785733] [<ffffffff811e8d9f>] generic_shutdown_super+0x3f/0x100
<4>[ 1224.792183] [<ffffffff811e8e72>] kill_anon_super+0x12/0x20
<4>[ 1224.797942] [<ffffffffa04664f8>] btrfs_kill_super+0x18/0x110 [btrfs]
<4>[ 1224.804577] [<ffffffff811e8803>] deactivate_locked_super+0x43/0x70
<4>[ 1224.811034] [<ffffffff811e888c>] deactivate_super+0x5c/0x60
<4>[ 1224.816884] [<ffffffff8120594f>] cleanup_mnt+0x3f/0x90
<4>[ 1224.822297] [<ffffffff812059e2>] __cleanup_mnt+0x12/0x20
<4>[ 1224.827884] [<ffffffff81094d16>] task_work_run+0x76/0xb0
<4>[ 1224.833474] [<ffffffff81003352>] exit_to_usermode_loop+0xc2/0xd0
<4>[ 1224.839753] [<ffffffff81003bd5>] syscall_return_slowpath+0xf5/0x160
<4>[ 1224.846307] [<ffffffff818c2288>] int_ret_from_sys_call+0x25/0x8f
<4>[ 1224.852582] ---[ end trace cb6a25f841edb72b ]---
<4>[ 1224.857482] ------------[ cut here ]------------
To reproduce:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
cd lkp-tests
bin/lkp install job.yaml # job file is attached in this email
bin/lkp run job.yaml
Thanks,
Xiaolong
4 years, 11 months
[x86, acpi, cpu] e9f7f55950: BUG: unable to handle kernel paging request at 0000000000001b00
by kernel test robot
FYI, we noticed the following commit:
https://github.com/zhuguihua/linux.git workqueue
commit e9f7f5595053b965b83f2e452a7bec6436c62191 ("x86, acpi, cpu-hotplug: Set persistent cpuid <-> nodeid mapping when booting.")
on test machine: ivb42: 48 threads Ivytown Ivy Bridge-EP with 64G memory
caused below changes:
+------------------------------------------+------------+------------+
| | eb7c120390 | e9f7f55950 |
+------------------------------------------+------------+------------+
| boot_successes | 4 | 0 |
| boot_failures | 0 | 8 |
| BUG:unable_to_handle_kernel | 0 | 8 |
| Oops | 0 | 8 |
| RIP:__alloc_pages_nodemask | 0 | 8 |
| Kernel_panic-not_syncing:Fatal_exception | 0 | 8 |
| backtrace:pcpu_balance_workfn | 0 | 8 |
+------------------------------------------+------------+------------+
[ 10.503155] RAPL PMU: hw unit of domain pp0-core 2^-16 Joules
[ 10.509574] RAPL PMU: hw unit of domain package 2^-16 Joules
[ 10.515894] RAPL PMU: hw unit of domain dram 2^-16 Joules
[ 10.523589] BUG: unable to handle kernel paging request at 0000000000001b00
[ 10.531381] IP: [<ffffffff8117e5c0>] __alloc_pages_nodemask+0x210/0xc10
[ 10.538779] PGD 0
[ 10.541035] Oops: 0000 [#1] SMP
[ 10.544657] Modules linked in:
[ 10.548075] CPU: 12 PID: 410 Comm: kworker/12:1 Not tainted 4.6.0-00005-ge9f7f55 #1
[ 10.556622] Hardware name: Intel Corporation S2600WP/S2600WP, BIOS SE5C600.86B.02.02.0002.122320131210 12/23/2013
[ 10.568081] Workqueue: events pcpu_balance_workfn
[ 10.573341] task: ffff881008620000 ti: ffff881008628000 task.ti: ffff881008628000
[ 10.581687] RIP: 0010:[<ffffffff8117e5c0>] [<ffffffff8117e5c0>] __alloc_pages_nodemask+0x210/0xc10
[ 10.591789] RSP: 0000:ffff88100862bc28 EFLAGS: 00010286
[ 10.597717] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000004
[ 10.605682] RDX: 0000000080000000 RSI: 0000000000000d06 RDI: ffffffff81c9f408
[ 10.613647] RBP: ffff88100862bd40 R08: 0000000000000000 R09: 0000000000000000
[ 10.621610] R10: ffffffff81ca420c R11: ffffc90000076000 R12: 0000000000000003
[ 10.629574] R13: 0000000000001b00 R14: 0000000000000000 R15: ffff88100e020200
[ 10.637537] FS: 0000000000000000(0000) GS:ffff881012c00000(0000) knlGS:0000000000000000
[ 10.646569] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 10.652980] CR2: 0000000000001b00 CR3: 000000103ee06000 CR4: 00000000001406e0
[ 10.660946] Stack:
[ 10.663190] ffffc90000090fff ffffc90000091000 ffff881012802008 0000000000000001
[ 10.671486] 8000000000000163 00000000ffffffff 00000000024082c2 0000000000400000
[ 10.679786] 000000000000001e ffff880ffdc080c0 ffff88100862bc88 ffffffff811b7a26
[ 10.688083] Call Trace:
[ 10.690818] [<ffffffff811b7a26>] ? map_vm_area+0x36/0x50
[ 10.696843] [<ffffffff81198e9e>] pcpu_populate_chunk+0xae/0x340
[ 10.703547] [<ffffffff8119a4d8>] pcpu_balance_workfn+0x578/0x5b0
[ 10.710348] [<ffffffff81094d28>] process_one_work+0x158/0x440
[ 10.716859] [<ffffffff8109596e>] worker_thread+0x4e/0x4c0
[ 10.722984] [<ffffffff818f6e6b>] ? __schedule+0x34b/0x8b0
[ 10.729105] [<ffffffff81095920>] ? rescuer_thread+0x350/0x350
[ 10.735614] [<ffffffff81095920>] ? rescuer_thread+0x350/0x350
[ 10.742127] [<ffffffff8109af24>] kthread+0xd4/0xf0
[ 10.747573] [<ffffffff818fba02>] ret_from_fork+0x22/0x40
[ 10.753598] [<ffffffff8109ae50>] ? kthread_park+0x60/0x60
[ 10.759720] Code: d0 49 8b 04 24 48 85 c0 75 e0 65 ff 0d b2 ed e8 7e eb 8b 31 d2 be 06 0d 00 00 48 c7 c7 08 f4 c9 81 e8 05 2b f2 ff e8 b0 90 77 00 <49> 83 7d 00 00 0f 85 7c fe ff ff 31 c0 e9 6d ff ff ff 0f 1f 44
[ 10.781422] RIP [<ffffffff8117e5c0>] __alloc_pages_nodemask+0x210/0xc10
[ 10.788913] RSP <ffff88100862bc28>
[ 10.792804] CR2: 0000000000001b00
[ 10.796508] ---[ end trace 13e5dd28007700a2 ]---
[ 10.801661] Kernel panic - not syncing: Fatal exception
To reproduce:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
cd lkp-tests
bin/lkp install job.yaml # job file is attached in this email
bin/lkp run job.yaml
Thanks,
Kernel Test Robot
4 years, 11 months
[lkp] [xfs] a08ee40a79: kmsg.XFS(vdd):unknown_mount_option[nosuchopt]
by kernel test robot
FYI, we noticed the following commit:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
commit a08ee40a79653d082911cab9fbeff94baa7714cb ("xfs: sanitize remount options")
on test machine: vm-kbuild-4G: 4 threads qemu-system-x86_64 -enable-kvm -cpu qemu64,+ssse3 with 4G memory
caused below changes:
[ 666.729855] XFS (vdd): unknown mount option [nosuchopt].
FYI, raw QEMU command line is:
qemu-system-x86_64 -enable-kvm -cpu qemu64,+ssse3 -kernel /pkg/linux/x86_64-rhel/gcc-4.9/a08ee40a79653d082911cab9fbeff94baa7714cb/vmlinuz-4.5.0-rc2-00003-ga08ee40 -append 'root=/dev/ram0 user=lkp job=/lkp/scheduled/vm-kbuild-4G-6/bisect_xfstests-4HDD-xfs-generic-quick1-debian-x86_64-2015-02-07.cgz-x86_64-rhel-a08ee40a79653d082911cab9fbeff94baa7714cb-20160513-42424-1y2kak2-1.yaml ARCH=x86_64 kconfig=x86_64-rhel branch=scsi/fixes commit=a08ee40a79653d082911cab9fbeff94baa7714cb BOOT_IMAGE=/pkg/linux/x86_64-rhel/gcc-4.9/a08ee40a79653d082911cab9fbeff94baa7714cb/vmlinuz-4.5.0-rc2-00003-ga08ee40 max_uptime=3600 RESULT_ROOT=/result/xfstests/4HDD-xfs-generic-quick1/vm-kbuild-4G/debian-x86_64-2015-02-07.cgz/x86_64-rhel/gcc-4.9/a08ee40a79653d082911cab9fbeff94baa7714cb/0 LKP_SERVER=inn earlyprintk=ttyS0,115200 systemd.log_level=err debug apic=debug sysrq_always_enabled rcupdate.rcu_cpu_stall_timeout=100 panic=-1 softlockup_panic=1 nmi_watchdog=panic oops=panic load_ramdisk=2 prompt_ramdisk=0 console=ttyS0,115200 console=tty0 vga=normal rw ip=::::vm-kbuild-4G-6::dhcp' -initrd /fs/sdd1/initrd-vm-kbuild-4G-6 -m 4096 -smp 4 -device e1000,netdev=net0 -netdev user,id=net0,hostfwd=tcp::23037-:22 -boot order=nc -no-reboot -watchdog i6300esb -rtc base=localtime -drive file=/fs/sdd1/disk0-vm-kbuild-4G-6,media=disk,if=virtio -drive file=/fs/sdd1/disk1-vm-kbuild-4G-6,media=disk,if=virtio -drive file=/fs/sdd1/disk2-vm-kbuild-4G-6,media=disk,if=virtio -drive file=/fs/sdd1/disk3-vm-kbuild-4G-6,media=disk,if=virtio -drive file=/fs/sdd1/disk4-vm-kbuild-4G-6,media=disk,if=virtio -drive file=/fs/sdd1/disk5-vm-kbuild-4G-6,media=disk,if=virtio -drive file=/fs/sdd1/disk6-vm-kbuild-4G-6,media=disk,if=virtio -pidfile /dev/shm/kboot/pid-vm-kbuild-4G-6 -serial file:/dev/shm/kboot/serial-vm-kbuild-4G-6 -daemonize -display none -monitor null
To reproduce:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
cd lkp-tests
bin/lkp install job.yaml # job file is attached in this email
bin/lkp run job.yaml
Thanks,
Xiaolong
4 years, 11 months
[lkp] [Btrfs] 2be63d5ce9: kmsg.BTRFS_warning(device_dm-#):failed_to_load_free_space_cache_for_block_group#, rebuilding_it_now
by kernel test robot
FYI, we noticed the following commit:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
commit 2be63d5ce929603d4e7cedabd9e992eb34a0ff95 ("Btrfs: fix file loss on log replay after renaming a file and fsync")
on test machine: vm-kbuild-4G: 4 threads qemu-system-x86_64 -enable-kvm -cpu qemu64,+ssse3 with 4G memory
caused below changes:
[ 161.757935] BTRFS warning (device dm-0): block group 29360128 has wrong amount of free space
[ 161.759875] BTRFS warning (device dm-0): failed to load free space cache for block group 29360128, rebuilding it now
[ 161.818413] BTRFS: checking UUID tree
FYI, raw QEMU command line is:
qemu-system-x86_64 -enable-kvm -cpu qemu64,+ssse3 -kernel /pkg/linux/x86_64-rhel/gcc-4.9/2be63d5ce929603d4e7cedabd9e992eb34a0ff95/vmlinuz-4.5.0-rc6-00079-g2be63d5 -append 'root=/dev/ram0 user=lkp job=/lkp/scheduled/vm-kbuild-4G-1/bisect_xfstests-4HDD-btrfs-generic-quick1-debian-x86_64-2015-02-07.cgz-x86_64-rhel-2be63d5ce929603d4e7cedabd9e992eb34a0ff95-20160513-33095-7gu30b-0.yaml ARCH=x86_64 kconfig=x86_64-rhel branch=scsi/fixes commit=2be63d5ce929603d4e7cedabd9e992eb34a0ff95 BOOT_IMAGE=/pkg/linux/x86_64-rhel/gcc-4.9/2be63d5ce929603d4e7cedabd9e992eb34a0ff95/vmlinuz-4.5.0-rc6-00079-g2be63d5 max_uptime=3600 RESULT_ROOT=/result/xfstests/4HDD-btrfs-generic-quick1/vm-kbuild-4G/debian-x86_64-2015-02-07.cgz/x86_64-rhel/gcc-4.9/2be63d5ce929603d4e7cedabd9e992eb34a0ff95/0 LKP_SERVER=inn earlyprintk=ttyS0,115200 systemd.log_level=err debug apic=debug sysrq_always_enabled rcupdate.rcu_cpu_stall_timeout=100 panic=-1 softlockup_panic=1 nmi_watchdog=panic oops=panic load_ramdisk=2 prompt_ramdisk=0 console=ttyS0,115200 console=tty0 vga=normal rw ip=::::vm-kbuild-4G-1::dhcp' -initrd /fs/sdf1/initrd-vm-kbuild-4G-1 -m 4096 -smp 4 -device e1000,netdev=net0 -netdev user,id=net0,hostfwd=tcp::23032-:22 -boot order=nc -no-reboot -watchdog i6300esb -rtc base=localtime -drive file=/fs/sdf1/disk0-vm-kbuild-4G-1,media=disk,if=virtio -drive file=/fs/sdf1/disk1-vm-kbuild-4G-1,media=disk,if=virtio -drive file=/fs/sdf1/disk2-vm-kbuild-4G-1,media=disk,if=virtio -drive file=/fs/sdf1/disk3-vm-kbuild-4G-1,media=disk,if=virtio -drive file=/fs/sdf1/disk4-vm-kbuild-4G-1,media=disk,if=virtio -drive file=/fs/sdf1/disk5-vm-kbuild-4G-1,media=disk,if=virtio -drive file=/fs/sdf1/disk6-vm-kbuild-4G-1,media=disk,if=virtio -pidfile /dev/shm/kboot/pid-vm-kbuild-4G-1 -serial file:/dev/shm/kboot/serial-vm-kbuild-4G-1 -daemonize -display none -monitor null
To reproduce:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
cd lkp-tests
bin/lkp install job.yaml # job file is attached in this email
bin/lkp run job.yaml
Thanks,
Xiaolong
4 years, 11 months
[x86, acpi, cpu] 9ab56e4d05: BUG: unable to handle kernel paging request at 0000000000001b00
by kernel test robot
FYI, we noticed the following commit:
https://github.com/zhuguihua/linux.git workqueue
commit 9ab56e4d05c470f14b023f64ae29d264ed9dc7c3 ("x86, acpi, cpu-hotplug: Set persistent cpuid <-> nodeid mapping when booting.")
on test machine: ivb42: 48 threads Ivytown Ivy Bridge-EP with 64G memory
caused below changes:
+------------------------------------------+------------+------------+
| | dc5867a22b | 9ab56e4d05 |
+------------------------------------------+------------+------------+
| boot_successes | 4 | 0 |
| boot_failures | 0 | 4 |
| BUG:unable_to_handle_kernel | 0 | 4 |
| Oops | 0 | 4 |
| RIP:__alloc_pages_nodemask | 0 | 4 |
| Kernel_panic-not_syncing:Fatal_exception | 0 | 4 |
| backtrace:pcpu_balance_workfn | 0 | 4 |
+------------------------------------------+------------+------------+
[ 10.366201] RAPL PMU: hw unit of domain pp0-core 2^-16 Joules
[ 10.372619] RAPL PMU: hw unit of domain package 2^-16 Joules
[ 10.378938] RAPL PMU: hw unit of domain dram 2^-16 Joules
[ 10.386626] BUG: unable to handle kernel paging request at 0000000000001b00
[ 10.394421] IP: [<ffffffff8117e4c0>] __alloc_pages_nodemask+0x210/0xc10
[ 10.401818] PGD 0
[ 10.404075] Oops: 0000 [#1] SMP
[ 10.407697] Modules linked in:
[ 10.411114] CPU: 20 PID: 407 Comm: kworker/20:1 Not tainted 4.6.0-rc7-00121-g9ab56e4 #1
[ 10.420051] Hardware name: Intel Corporation S2600WP/S2600WP, BIOS SE5C600.86B.02.02.0002.122320131210 12/23/2013
[ 10.431509] Workqueue: events pcpu_balance_workfn
[ 10.436767] task: ffff88100d890000 ti: ffff88100d898000 task.ti: ffff88100d898000
[ 10.445121] RIP: 0010:[<ffffffff8117e4c0>] [<ffffffff8117e4c0>] __alloc_pages_nodemask+0x210/0xc10
[ 10.455230] RSP: 0000:ffff88100d89bc28 EFLAGS: 00010286
[ 10.461159] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000004
[ 10.469122] RDX: 0000000080000000 RSI: 0000000000000d06 RDI: ffffffff81c9f340
[ 10.477085] RBP: ffff88100d89bd40 R08: 0000000000000000 R09: 0000000000000000
[ 10.485048] R10: ffffffff81ca4144 R11: ffffc90000076000 R12: 0000000000000003
[ 10.493012] R13: 0000000000001b00 R14: 0000000000000000 R15: ffff88100d074400
[ 10.500977] FS: 0000000000000000(0000) GS:ffff881013600000(0000) knlGS:0000000000000000
[ 10.510001] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 10.516413] CR2: 0000000000001b00 CR3: 000000103ee06000 CR4: 00000000001406e0
[ 10.524379] Stack:
[ 10.526622] ffffc90000090fff ffffc90000091000 ffff881013002008 0000000000000001
[ 10.534922] 8000000000000163 00000000ffffffff 00000000024082c2 0000000000400000
[ 10.543219] 000000000000001e ffff880ffe24b0c0 ffff88100d89bc88 ffffffff811b7926
[ 10.551518] Call Trace:
[ 10.554253] [<ffffffff811b7926>] ? map_vm_area+0x36/0x50
[ 10.560277] [<ffffffff81198d9e>] pcpu_populate_chunk+0xae/0x340
[ 10.566982] [<ffffffff8119a3d8>] pcpu_balance_workfn+0x578/0x5b0
[ 10.573785] [<ffffffff81094d28>] process_one_work+0x158/0x440
[ 10.580284] [<ffffffff8109596e>] worker_thread+0x4e/0x4c0
[ 10.586406] [<ffffffff818f6b4b>] ? __schedule+0x34b/0x8b0
[ 10.592528] [<ffffffff81095920>] ? rescuer_thread+0x350/0x350
[ 10.599039] [<ffffffff81095920>] ? rescuer_thread+0x350/0x350
[ 10.605549] [<ffffffff8109af24>] kthread+0xd4/0xf0
[ 10.610996] [<ffffffff818fb702>] ret_from_fork+0x22/0x40
[ 10.617021] [<ffffffff8109ae50>] ? kthread_park+0x60/0x60
[ 10.623143] Code: d0 49 8b 04 24 48 85 c0 75 e0 65 ff 0d b2 ee e8 7e eb 8b 31 d2 be 06 0d 00 00 48 c7 c7 40 f3 c9 81 e8 05 2c f2 ff e8 90 8e 77 00 <49> 83 7d 00 00 0f 85 7c fe ff ff 31 c0 e9 6d ff ff ff 0f 1f 44
[ 10.644863] RIP [<ffffffff8117e4c0>] __alloc_pages_nodemask+0x210/0xc10
[ 10.652353] RSP <ffff88100d89bc28>
[ 10.656245] CR2: 0000000000001b00
[ 10.659946] ---[ end trace 13f6fed96ebb30e5 ]---
[ 10.665100] Kernel panic - not syncing: Fatal exception
To reproduce:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
cd lkp-tests
bin/lkp install job.yaml # job file is attached in this email
bin/lkp run job.yaml
Thanks,
Kernel Test Robot
4 years, 11 months
[lkp] [zsmalloc] 44f43e99fe: will-it-scale.scalability +15.0% improvement
by kernel test robot
FYI, we noticed will-it-scale.scalability +15.0% improvement due to commit:
commit 44f43e99fe70833058482d183e99fdfd11220996 ("zsmalloc: fix zs_can_compact() integer overflow")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
in testcase - will-it-scale
on test machine - xps: 8 threads Nehalem with 4G memory
=========================================================================================
compiler/cpufreq_governor/kconfig/rootfs/tbox_group/test/testcase:
gcc-4.9/performance/x86_64-rhel/debian-x86_64-2015-02-07.cgz/xps/write1/will-it-scale
commit:
1e92a61c4c7ed85c1bec037c046e92d6dc762f32
44f43e99fe70833058482d183e99fdfd11220996
1e92a61c4c7ed85c 44f43e99fe70833058482d183e
---------------- --------------------------
fail:runs %reproduction fail:runs
| | |
%stddev %change %stddev
\ | \
1269910 ± 0% -7.7% 1172297 ± 0% will-it-scale.per_process_ops
1219902 ± 0% -7.7% 1125807 ± 0% will-it-scale.per_thread_ops
0.22 ± 2% +15.0% 0.25 ± 0% will-it-scale.scalability
962.50 ± 2% -4.4% 920.00 ± 2% vmstat.system.cs
56.78 ± 7% +99.5% 113.28 ± 53% sched_debug.cpu.load.stddev
0.41 ± 5% +13.7% 0.47 ± 5% sched_debug.cpu.nr_running.stddev
5576 ± 3% +19.1% 6642 ± 4% slabinfo.anon_vma_chain.active_objs
5681 ± 3% +17.9% 6696 ± 4% slabinfo.anon_vma_chain.num_objs
1610 ± 15% +22.5% 1973 ± 4% slabinfo.cred_jar.active_objs
=========================================================================================
compiler/cpufreq_governor/kconfig/rootfs/tbox_group/test/testcase:
gcc-4.9/performance/x86_64-rhel/debian-x86_64-2015-02-07.cgz/xps/writeseek2/will-it-scale
commit:
1e92a61c4c7ed85c1bec037c046e92d6dc762f32
44f43e99fe70833058482d183e99fdfd11220996
1e92a61c4c7ed85c 44f43e99fe70833058482d183e
---------------- --------------------------
fail:runs %reproduction fail:runs
| | |
:4 25% 1:4 kmsg.do_IRQ:#No_irq_handler_for_vector
%stddev %change %stddev
\ | \
768011 ± 0% -8.7% 701413 ± 0% will-it-scale.per_process_ops
660490 ± 0% -7.9% 608530 ± 0% will-it-scale.per_thread_ops
0.06 ± 2% +13.8% 0.07 ± 0% will-it-scale.scalability
702840 ± 11% +56.7% 1101645 ± 11% cpuidle.C1E-NHM.time
23738 ± 4% -7.5% 21947 ± 1% softirqs.RCU
173.21 ± 8% +13.9% 197.33 ± 3% sched_debug.cfs_rq:/.load.max
56.64 ± 8% +24.1% 70.31 ± 3% sched_debug.cfs_rq:/.load.stddev
36.58 ± 5% -12.2% 32.12 ± 4% sched_debug.cpu.cpu_load[3].min
173.21 ± 8% +13.9% 197.33 ± 3% sched_debug.cpu.load.max
56.65 ± 8% +24.1% 70.32 ± 3% sched_debug.cpu.load.stddev
will-it-scale.scalability
0.27 ++-------------------------------------------------------------------+
| O |
0.26 ++ O O |
O O O O O O O O O O |
0.25 ++ O O |
| |
0.24 ++ |
| |
0.23 ++ |
| *...*..|
0.22 ++.*... .*.. *...*.. ..*.. ..*.. ..*.. ..*.. + *
*. *. . .. *. *. .*. *. + |
0.21 ++ * *. *...* |
| |
0.2 ++-------------------------------------------------------------------+
will-it-scale.per_process_ops
1.3e+06 ++---------------------------------------------------------------+
| |
1.28e+06 ++ ..*.. .*
1.26e+06 *+.*...*..*..*..*. *..*..*...*..*..*..*...*..*..*..*...*..*. |
| |
1.24e+06 ++ |
| |
1.22e+06 ++ |
| |
1.2e+06 ++ |
1.18e+06 ++ |
| O O O O O O |
1.16e+06 ++ O O O O |
O O O O |
1.14e+06 ++-O-------------------------------------------------------------+
will-it-scale.per_thread_ops
1.24e+06 ++---------------------------------------------------------------+
| .*
1.22e+06 ++ .*..*.. ..*.. ..*..*.. .*..*..*...*..*. |
*..*...*. *. *..*..*. *..*...*. |
1.2e+06 ++ |
| |
1.18e+06 ++ |
| |
1.16e+06 ++ |
| |
1.14e+06 ++ |
| O O O O |
1.12e+06 ++ O O O O O O O |
O O O O |
1.1e+06 ++---------------------------------------------------------------+
[*] bisect-good sample
[O] bisect-bad sample
To reproduce:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
cd lkp-tests
bin/lkp install job.yaml # job file is attached in this email
bin/lkp run job.yaml
Disclaimer:
Results have been estimated based on internal Intel analysis and are provided
for informational purposes only. Any difference in system hardware or software
design or configuration may affect actual performance.
Thanks,
Xiaolong
4 years, 11 months
[sched/core] 5e1f139af8: BUG: workqueue lockup - pool cpus=0 node=0 flags=0x0 nice=0 stuck for 30s!
by kernel test robot
Greetings,
0day kernel testing robot got the below dmesg and the first bad commit is
https://git.kernel.org/pub/scm/linux/kernel/git/mfleming/linux.git sched/rq-clock
commit 5e1f139af85bc3a88b0fcbf8611c7cdf5fe49489
Author: Matt Fleming <matt(a)codeblueprint.co.uk>
AuthorDate: Fri Apr 29 16:28:32 2016 +0100
Commit: Matt Fleming <matt(a)codeblueprint.co.uk>
CommitDate: Thu May 12 20:24:53 2016 +0100
sched/core: Add debug code to catch missing update_rq_clock()
There's no diagnostic checks for figuring out when we've accidentally
missed update_rq_clock() calls. Let's add some by piggybacking on the
rq_*pin_lock() wrappers.
The idea behind the diagnostic checks is that upon pining rq lock the
rq clock should be updated, via update_rq_clock(), before anybody
reads the clock with rq_clock(). The exception to this rule is when
updates have explicitly been disabled with the rq_clock_skip_update()
optimisation.
There are some functions that only unpin the rq lock in order to grab
some other lock and avoid deadlock. In that case we don't need to
update the clock again and the previous diagnostic state can be
carried over in rq_repin_lock() by saving the state in the rq_flags
context.
Since this patch adds a new clock update flag and some already exist
in rq::clock_skip_update, that field has now been renamed. An attempt
has been made to keep the flag manipulation code small and fast since
it's used in the heart of the __schedule() fast path.
For the !CONFIG_SCHED_DEBUG case the only object code change (other
than addresses) is the following change to the two lines to reset
RQCF_ACT_SKIP inside of __schedule(),
- 41 c7 84 24 f0 08 00 movl $0x0,0x8f0(%r12)
- 00 00 00 00 00
+ 41 83 b4 24 f0 08 00 xorl $0x2,0x8f0(%r12)
+ 00 02
Suggested-by: Peter Zijlstra <peterz(a)infradead.org>
Cc: Ingo Molnar <mingo(a)kernel.org>
Cc: Mike Galbraith <umgwanakikbuti(a)gmail.com>
Cc: Mel Gorman <mgorman(a)techsingularity.net>
Signed-off-by: Matt Fleming <matt(a)codeblueprint.co.uk>
+-----------------------------------------------------------------+------------+------------+-----------------+
| | d058ac5485 | 5e1f139af8 | v4.6-rc7_051314 |
+-----------------------------------------------------------------+------------+------------+-----------------+
| boot_successes | 84 | 2 | 2 |
| boot_failures | 16 | 23 | 11 |
| BUG:kernel_test_crashed | 16 | | |
| BUG:workqueue_lockup-pool_cpus=#node=#flags=#nice=#stuck_for#s | 0 | 23 | 11 |
| BUG:workqueue_lockup-pool_cpus=#node=#flags=#nice=-#stuck_for#s | 0 | 5 | 3 |
| BUG:workqueue_lockup-pool_cpus=#-#flags=#nice=#stuck_for#s | 0 | 1 | 2 |
| INFO:task_blocked_for_more_than#seconds | 0 | 1 | |
| RIP:__default_send_IPI_dest_field | 0 | 1 | |
| RIP:_cond_resched | 0 | 1 | |
| Kernel_panic-not_syncing:hung_task:blocked_tasks | 0 | 1 | |
| backtrace:do_sys_open | 0 | 1 | |
| backtrace:SyS_open | 0 | 1 | |
| backtrace:watchdog | 0 | 1 | |
| backtrace:lock_torture_writer | 0 | 1 | |
+-----------------------------------------------------------------+------------+------------+-----------------+
[ 52.084962] init: tty3 main process ended, respawning
[ 52.087146] init: tty6 main process (603) terminated with status 1
[ 52.088949] init: tty6 main process ended, respawning
[ 60.861888] BUG: workqueue lockup - pool cpus=0 node=0 flags=0x0 nice=0 stuck for 30s!
[ 60.868974] Showing busy workqueues and worker pools:
[ 60.870895] workqueue events: flags=0x0
[ 60.871534] pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=18/256
git bisect start bdd04db0a5e7f78c5e34d2937ad7f89262444f4f 44549e8f5eea4e0a41b487b63e616cb089922b99 --
git bisect bad a2dbc2ed6e44c13eab3085e320eded3272dcdb35 # 18:45 1- 11 Merge 'm68knommu/for-next' into devel-hourly-2016051314
git bisect bad ecfb22a42800c85a6c9fe1a5bfac7a2c89233e75 # 18:50 0- 15 Merge 'linux-review/Ocean-HY1-He/ACPI-Execute-the-_PTS-method-when-system-reboot/20160509-140545' into devel-hourly-2016051314
git bisect bad 9fcbbe83a7a203bb862b9554df9771d703f3a8d7 # 18:54 5- 14 Merge 'linux-review/Sebastian-Frias/Fwd-PATCH-mm-add-config-option-to-select-the-initial-overcommit-mode/20160510-200545' into devel-hourly-2016051314
git bisect good 8d9c3f78cb66958bfd712b0bf1d74707756f1e8f # 18:59 25+ 1 Merge 'perf/perf/urgent' into devel-hourly-2016051314
git bisect good 2f75e6734c9e82b8100ea5fbf3caf4bdf0ba5395 # 19:02 25+ 2 Merge 'm68k/m68k-queue' into devel-hourly-2016051314
git bisect good b8052961a7ec1f18b055d661003e3609c9689959 # 19:06 25+ 1 Merge 'luto/perf/harden' into devel-hourly-2016051314
git bisect bad cb13608e5212bf897cc9d54c940a55ae71025111 # 19:09 1- 13 Merge 'linux-review/Sebastian-Frias/checkpatch-make-the-config-description-warning-more-explicit/20160510-212724' into devel-hourly-2016051314
git bisect bad b854eb91908ec9c4f5ca2a4252c4b48642f95e6f # 19:13 2- 19 Merge 'nf/master' into devel-hourly-2016051314
git bisect bad c5cec417fa63be106e640afee19f47124c49563f # 19:16 3- 17 Merge 'mfleming/sched/rq-clock' into devel-hourly-2016051314
git bisect good db6ea2fb094fb3a6afc36d3e4229bc162638ad24 # 19:19 25+ 3 sched/debug: Print out idle balance values even on !CONFIG_SCHEDSTATS kernels
git bisect good 4eb867651721228ee2eeae142c53378375303e8b # 19:24 25+ 4 Merge branch 'smp/hotplug' into sched/core, to resolve conflicts
git bisect good 20878232c52329f92423d27a60e48b6a6389e0dd # 19:28 25+ 1 sched/loadavg: Fix loadavg artifacts on fully idle and on fully loaded systems
git bisect good 13b21adc9977bdc3aa0b210360ee9ecfa1c80481 # 19:34 25+ 1 sched: Add wrappers for lockdep_(un)pin_lock()
git bisect good d058ac54853d9dd1a3da3fcec8787a51047f539a # 19:38 25+ 2 sched/fair: Push rq lock pin/unpin into idle_balance()
git bisect bad 5e1f139af85bc3a88b0fcbf8611c7cdf5fe49489 # 19:42 0- 16 sched/core: Add debug code to catch missing update_rq_clock()
# first bad commit: [5e1f139af85bc3a88b0fcbf8611c7cdf5fe49489] sched/core: Add debug code to catch missing update_rq_clock()
git bisect good d058ac54853d9dd1a3da3fcec8787a51047f539a # 19:44 75+ 16 sched/fair: Push rq lock pin/unpin into idle_balance()
# extra tests on HEAD of linux-devel/devel-hourly-2016051314
git bisect bad bdd04db0a5e7f78c5e34d2937ad7f89262444f4f # 19:44 0- 11 0day head guard for 'devel-hourly-2016051314'
# extra tests on tree/branch mfleming/sched/rq-clock
git bisect bad 5e1f139af85bc3a88b0fcbf8611c7cdf5fe49489 # 19:46 0- 23 sched/core: Add debug code to catch missing update_rq_clock()
# extra tests with first bad commit reverted
git bisect good 3ba8136bd50fbdc62885f8506f6850c15b95b4ea # 19:53 75+ 5 Revert "sched/core: Add debug code to catch missing update_rq_clock()"
# extra tests on tree/branch linus/master
git bisect good a2ccb68b1e6add42c0bf3ade73cd11c98d32b890 # 19:57 75+ 10 Merge branch 'akpm' (patches from Andrew)
# extra tests on tree/branch linux-next/master
git bisect bad 7fd1a8676b7f573be6aa8072e8fa1d4f1bbf8ea7 # 19:59 63- 4 Add linux-next specific files for 20160513
This script may reproduce the error.
----------------------------------------------------------------------------
#!/bin/bash
kernel=$1
initrd=quantal-core-x86_64.cgz
wget --no-clobber https://github.com/fengguang/reproduce-kernel-bug/raw/master/initrd/$initrd
kvm=(
qemu-system-x86_64
-enable-kvm
-cpu kvm64
-kernel $kernel
-initrd $initrd
-m 300
-smp 2
-device e1000,netdev=net0
-netdev user,id=net0
-boot order=nc
-no-reboot
-watchdog i6300esb
-rtc base=localtime
-serial stdio
-display none
-monitor null
)
append=(
hung_task_panic=1
earlyprintk=ttyS0,115200
systemd.log_level=err
debug
apic=debug
sysrq_always_enabled
rcupdate.rcu_cpu_stall_timeout=100
panic=-1
softlockup_panic=1
nmi_watchdog=panic
oops=panic
load_ramdisk=2
prompt_ramdisk=0
console=ttyS0,115200
console=tty0
vga=normal
root=/dev/ram0
rw
drbd.minor_count=8
)
"${kvm[@]}" --append "${append[*]}"
----------------------------------------------------------------------------
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/lkp Intel Corporation
4 years, 11 months