[lkp] [x86, perf] 68c3d26413: WARNING: CPU: 0 PID: 1 at arch/x86/kernel/cpu/perf_event_intel.c:1820 intel_pmu_handle_irq+0x481/0x4a0()
by kernel test robot
FYI, we noticed the below changes on
https://github.com/0day-ci/linux Andi-Kleen/x86-perf-Use-a-new-PMU-ack-sequence-on-Skylake/20151016-074238
commit 68c3d26413417b69cde6b4e6661f29dbf40fb65a ("x86, perf: Use a new PMU ack sequence on Skylake")
+---------------------------------------------------------------------------+------------+------------+
| | e9363deeb2 | 68c3d26413 |
+---------------------------------------------------------------------------+------------+------------+
| boot_successes | 11 | 15 |
| boot_failures | 0 | 8 |
| WARNING:at_arch/x86/kernel/cpu/perf_event_intel.c:#intel_pmu_handle_irq() | 0 | 8 |
| backtrace:dev_printk | 0 | 2 |
| backtrace:pci_pm_init | 0 | 2 |
| backtrace:acpi_bus_scan | 0 | 8 |
| backtrace:acpi_scan_init | 0 | 8 |
| backtrace:acpi_init | 0 | 8 |
| backtrace:kernel_init_freeable | 0 | 8 |
+---------------------------------------------------------------------------+------------+------------+
[ 1.503050] pci 0000:00:00.0: [8086:3406] type 00 class 0x060000
[ 1.509793] pci 0000:00:00.0: PME# supported from D0 D3hot D3cold
[ 1.515028] ------------[ cut here ]------------
[ 1.515032] WARNING: CPU: 0 PID: 1 at arch/x86/kernel/cpu/perf_event_intel.c:1820 intel_pmu_handle_irq+0x481/0x4a0()
[ 1.515033] perfevents: irq loop stuck!
[ 1.515034] Modules linked in:
[ 1.515035] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.3.0-rc4-00237-g68c3d26 #1
[ 1.515036] Hardware name: Intel Corporation S5520UR/S5520UR, BIOS S5500.86B.01.00.0050.050620101605 05/06/2010
[ 1.515038] ffffffff81b7a038 ffff8801e9a05b58 ffffffff81403b62 ffff8801e9a05ba0
[ 1.515039] ffff8801e9a05b90 ffffffff810757c6 ffff8801e9a0bfc0 0000000000000064
[ 1.515040] ffff88035e881000 0000000000000040 ffff8801e9a0c1c0 ffff8801e9a05bf0
[ 1.515040] Call Trace:
[ 1.515048] <NMI> [<ffffffff81403b62>] dump_stack+0x4b/0x69
[ 1.515051] [<ffffffff810757c6>] warn_slowpath_common+0x86/0xc0
[ 1.515052] [<ffffffff8107584c>] warn_slowpath_fmt+0x4c/0x50
[ 1.515053] [<ffffffff81034071>] intel_pmu_handle_irq+0x481/0x4a0
[ 1.515057] [<ffffffff8102a8d6>] perf_event_nmi_handler+0x26/0x40
[ 1.515060] [<ffffffff81019260>] nmi_handle+0x80/0x120
[ 1.515061] [<ffffffff81019784>] default_do_nmi+0x44/0x120
[ 1.515062] [<ffffffff81019942>] do_nmi+0xe2/0x130
[ 1.515065] [<ffffffff818b1921>] end_repeat_nmi+0x1a/0x1e
[ 1.515068] [<ffffffff8141035c>] ? delay_tsc+0x2c/0x70
[ 1.515069] [<ffffffff8141035c>] ? delay_tsc+0x2c/0x70
[ 1.515070] [<ffffffff8141035c>] ? delay_tsc+0x2c/0x70
[ 1.515072] <<EOE>> [<ffffffff814102c7>] __const_udelay+0x27/0x30
[ 1.515075] [<ffffffff81511ecc>] wait_for_xmitr+0x2c/0xa0
[ 1.515077] [<ffffffff81511f5c>] serial8250_console_putchar+0x1c/0x30
[ 1.515078] [<ffffffff81511f40>] ? wait_for_xmitr+0xa0/0xa0
[ 1.515079] [<ffffffff8150b5f3>] uart_console_write+0x33/0x60
[ 1.515082] [<ffffffff81514590>] serial8250_console_write+0xc0/0x270
[ 1.515084] [<ffffffff810951d1>] ? atomic_notifier_call_chain+0x21/0x30
[ 1.515087] [<ffffffff81503fd1>] ? vt_console_print+0x231/0x3d0
[ 1.515088] [<ffffffff8150fb46>] univ8250_console_write+0x26/0x30
[ 1.515090] [<ffffffff810cba06>] call_console_drivers+0xf6/0x100
[ 1.515092] [<ffffffff810cce5a>] console_unlock+0x2fa/0x4d0
[ 1.515093] [<ffffffff810cd3f2>] vprintk_emit+0x3c2/0x540
[ 1.515096] [<ffffffff815488a4>] dev_vprintk_emit+0xb4/0x210
[ 1.515099] [<ffffffff8147ee7d>] ? acpi_os_signal_semaphore+0x73/0x83
[ 1.515102] [<ffffffff814c0f5d>] ? acpi_ut_release_mutex+0xb4/0xbc
[ 1.515104] [<ffffffff814b3d16>] ? acpi_get_data_full+0x7d/0x90
[ 1.515105] [<ffffffff81482fa0>] ? __acpi_match_device+0x64/0x117
[ 1.515106] [<ffffffff81548a3e>] dev_printk_emit+0x3e/0x40
[ 1.515109] [<ffffffff8175a9f3>] ? raw_pci_read+0x23/0x40
[ 1.515110] [<ffffffff81548a86>] __dev_printk+0x46/0x90
[ 1.515111] [<ffffffff81548b1d>] dev_printk+0x4d/0x50
[ 1.515113] [<ffffffff814486c0>] pci_pm_init+0x1c0/0x220
[ 1.515115] [<ffffffff81443044>] pci_device_add+0xb4/0x180
[ 1.515116] [<ffffffff8144319c>] pci_scan_single_device+0x8c/0xb0
[ 1.515117] [<ffffffff81443213>] pci_scan_slot+0x53/0x110
[ 1.515118] [<ffffffff814443b8>] pci_scan_child_bus+0x38/0x150
[ 1.515120] [<ffffffff817594a0>] pci_acpi_scan_root+0x290/0x5e0
[ 1.515122] [<ffffffff8148a242>] acpi_pci_root_add+0x3b0/0x49f
[ 1.515123] [<ffffffff81ec77cd>] ? acpi_sleep_proc_init+0x2a/0x2a
[ 1.515125] [<ffffffff8148573b>] acpi_bus_attach+0xd4/0x171
[ 1.515126] [<ffffffff81485795>] acpi_bus_attach+0x12e/0x171
[ 1.515127] [<ffffffff81485795>] acpi_bus_attach+0x12e/0x171
[ 1.515129] [<ffffffff814858c6>] acpi_bus_scan+0x5c/0x67
[ 1.515130] [<ffffffff81ec7bf2>] acpi_scan_init+0x5b/0x190
[ 1.515131] [<ffffffff81ec7a36>] acpi_init+0x269/0x286
[ 1.515133] [<ffffffff81002123>] do_one_initcall+0xb3/0x1d0
[ 1.515135] [<ffffffff81e7c14e>] kernel_init_freeable+0x1c1/0x24e
[ 1.515137] [<ffffffff818a29c0>] ? rest_init+0x90/0x90
[ 1.515138] [<ffffffff818a29ce>] kernel_init+0xe/0xe0
[ 1.515139] [<ffffffff818af71f>] ret_from_fork+0x3f/0x70
[ 1.515140] [<ffffffff818a29c0>] ? rest_init+0x90/0x90
[ 1.515142] ---[ end trace 01fce7d27e4440f8 ]---
[ 1.515143]
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,
Ying Huang
6 years, 6 months
[lkp] [of] db59ef4cdc:
by kernel test robot
FYI, we noticed the below changes on
https://github.com/pantoniou/linux-beagle-track-mainline.git bbb-overlays
commit db59ef4cdc3261322ea61686e714b571ef709484 ("of: unittest: Unit-tests for target root overlays.")
We found some OF unittests errors in kernel log, while the line marked
with + is new after this commit. This is intended? Or should be fixed?
[ 10.536161] overlay_is_topmost: #5 clashes #6 @/testcase-data/overlay-node/test-bus/test-unittest8
[ 10.541601] overlay_removal_is_ok: overlay #5 is not topmost
[ 10.542464] of_overlay_destroy: removal check failed for overlay #5
[ 10.566327] find_target_node_direct: target "/testcase-data/overlay-node/test-bus/test-unittest18" not under target_root "/testcase-data/overlay-node/test-bus/test-unittest19"
[ 10.570260] __of_overlay_create: of_build_overlay_info() failed for tree@/testcase-data/overlay19
[ 10.609190] ### dt-test ### end of unittest - 152 passed, 0 failed
Thanks,
Ying Huang
6 years, 6 months
[sched] 4183fdd831: WARNING: CPU: 0 PID: 3 at kernel/sched/fair.c:260 update_stats_wait_end()
by kernel test robot
Greetings,
0day kernel testing robot got the below dmesg and the first bad commit is
https://github.com/0day-ci/linux Joonwoo-Park/sched-fix-incorrect-wait-time-and-wait-count-statistics/20151027-094629
commit 4183fdd83194ded503e1cec873556dd560f43dd4
Author: Joonwoo Park <joonwoop(a)codeaurora.org>
AuthorDate: Mon Oct 26 18:44:48 2015 -0700
Commit: 0day robot <fengguang.wu(a)intel.com>
CommitDate: Tue Oct 27 09:46:30 2015 +0800
sched: fix incorrect wait time and wait count statistics
On 10/25/2015 03:26 AM, Peter Zijlstra wrote:
> On Sat, Oct 24, 2015 at 10:23:14PM -0700, Joonwoo Park wrote:
>> @@ -1069,7 +1069,7 @@ static struct rq *move_queued_task(struct rq *rq, struct task_struct *p, int new
>> {
>> lockdep_assert_held(&rq->lock);
>>
>> - dequeue_task(rq, p, 0);
>> + dequeue_task(rq, p, DEQUEUE_MIGRATING);
>> p->on_rq = TASK_ON_RQ_MIGRATING;
>> set_task_cpu(p, new_cpu);
>> raw_spin_unlock(&rq->lock);
>
>> @@ -5656,7 +5671,7 @@ static void detach_task(struct task_struct *p, struct lb_env *env)
>> {
>> lockdep_assert_held(&env->src_rq->lock);
>>
>> - deactivate_task(env->src_rq, p, 0);
>> + deactivate_task(env->src_rq, p, DEQUEUE_MIGRATING);
>> p->on_rq = TASK_ON_RQ_MIGRATING;
>> set_task_cpu(p, env->dst_cpu);
>> }
>
> Also note that on both sites we also set TASK_ON_RQ_MIGRATING -- albeit
> late. Can't you simply set that earlier (and back to QUEUED later) and
> test for task_on_rq_migrating() instead of blowing up the fastpath like
> you did?
>
Yes it's doable. I also find it's much simpler.
Please find patch v2. I verified v2 does same job as v1 by comparing sched_stat_wait time with sched_switch - sched_wakeup timestamp.
Thanks,
Joonwoo
From 98d615d46211a90482a0f9b7204265c54bba8520 Mon Sep 17 00:00:00 2001
From: Joonwoo Park <joonwoop(a)codeaurora.org>
Date: Mon, 26 Oct 2015 16:37:47 -0700
Subject: [PATCH v2] sched: fix incorrect wait time and wait count statistics
At present scheduler resets task's wait start timestamp when the task
migrates to another rq. This misleads scheduler itself into reporting
less wait time than actual by omitting time spent for waiting prior to
migration and also more wait count than actual by counting migration as
wait end event which can be seen by trace or /proc/<pid>/sched with
CONFIG_SCHEDSTATS=y.
Carry forward migrating task's wait time prior to migration and
don't count migration as a wait end event to fix such statistics error.
In order to determine whether task is migrating mark task->on_rq with
TASK_ON_RQ_MIGRATING while dequeuing and enqueuing due to migration.
To: Ingo Molnar <mingo(a)kernel.org>
To: Peter Zijlstra <peterz(a)infradead.org>
Cc: linux-kernel(a)vger.kernel.org
Signed-off-by: Joonwoo Park <joonwoop(a)codeaurora.org>
+---------------------------------------------------------+------------+------------+------------+
| | 8a5ec90292 | 4183fdd831 | d9e738c64e |
+---------------------------------------------------------+------------+------------+------------+
| boot_successes | 63 | 0 | 0 |
| boot_failures | 0 | 22 | 13 |
| WARNING:at_kernel/sched/fair.c:#update_stats_wait_end() | 0 | 22 | 13 |
| backtrace:smpboot_thread_fn | 0 | 22 | 13 |
+---------------------------------------------------------+------------+------------+------------+
[ 13.294261] Write protecting the kernel text: 10680k
[ 13.294701] Write protecting the kernel read-only data: 3756k
[ 13.300215] ------------[ cut here ]------------
[ 13.300615] WARNING: CPU: 0 PID: 3 at kernel/sched/fair.c:260 update_stats_wait_end+0x23/0x30()
[ 13.301499] CPU: 0 PID: 3 Comm: ksoftirqd/0 Not tainted 4.3.0-rc6-00788-g4183fdd #326
[ 13.302140] 00000000 00000000 90839e74 8129fbbd 90839ea4 81040e38 81d34fa4 00000000
[ 13.302864] 00000003 81d3637c 00000104 81066f03 81066f03 8b061f80 81e355fc 8b061f88
[ 13.303571] 90839eb4 81040f0b 00000009 00000000 90839ebc 81066f03 90839ed0 81066f73
[ 13.304284] Call Trace:
[ 13.304491] [<8129fbbd>] dump_stack+0x16/0x19
[ 13.304859] [<81040e38>] warn_slowpath_common+0x78/0xb0
[ 13.305295] [<81066f03>] ? update_stats_wait_end+0x23/0x30
[ 13.305802] [<81066f03>] ? update_stats_wait_end+0x23/0x30
[ 13.306300] [<81040f0b>] warn_slowpath_null+0x1b/0x20
[ 13.306716] [<81066f03>] update_stats_wait_end+0x23/0x30
[ 13.307208] [<81066f73>] set_next_entity+0x63/0xb0
[ 13.307608] [<810689a0>] pick_next_task_fair+0x140/0x190
[ 13.308051] [<81a67607>] __schedule+0x197/0x670
[ 13.308428] [<81a67b2e>] schedule+0x1e/0x40
[ 13.308783] [<8105edc3>] smpboot_thread_fn+0x153/0x1c0
[ 13.309208] [<8105ec70>] ? sort_range+0x20/0x20
[ 13.309591] [<8105b1d0>] kthread+0xa0/0xc0
[ 13.309943] [<81a6c768>] ret_from_kernel_thread+0x20/0x34
[ 13.310052] [<8105b130>] ? __kthread_parkme+0x80/0x80
[ 13.310052] ---[ end trace 3701210986adb17b ]---
[ 13.312264] random: init urandom read with 21 bits of entropy available
git bisect start d9e738c64efcbf03c53aae94700121e3c705fb65 7379047d5585187d1288486d4627873170d0005a --
git bisect bad 267c986ef9603ec9154b819a5ec1207ee72798aa # 10:44 0- 4 Merge 'hwmon/watchdog-next' into devel-catchup-201510271010
git bisect good 9679d92f0c1227c4f7817a5c5b15de2d09a48422 # 10:47 21+ 0 0day base guard for 'devel-catchup-201510271010'
git bisect bad bd7029bca5adf9c5c22be0ae375cd7f570e1c6c7 # 10:55 0- 9 Merge 'linux-review/Joonwoo-Park/sched-fix-incorrect-wait-time-and-wait-count-statistics/20151027-094629' into devel-catchup-201510271010
git bisect good 28fd0254ab20b4f7c1897dd562cd0f12468368e5 # 11:03 22+ 0 Merge branch 'locking/core'
git bisect good 987d16d60b38382ab5914459be380f9a020b03d6 # 11:08 22+ 0 Merge branch 'ras/core'
git bisect good 1b9b556081cbc68c6bf5a8e540899171cecb12dc # 11:15 22+ 0 Merge branch 'x86/apic'
git bisect good d58edcaab85edb3b1b72c0fee753d219cb4cee98 # 11:25 22+ 0 Merge branch 'x86/debug'
git bisect good 2043d3d0c2ffb6afb71074df3f76a7bf179a31d6 # 11:30 22+ 0 Merge branch 'x86/headers'
git bisect good 2d1c7748fbf393f7078d1fd3d03a48f13753e01d # 11:37 22+ 0 Merge branch 'x86/mm'
git bisect good f7d27c35ddff7c100d7a98db499ac0040149ac05 # 11:44 22+ 0 x86/mm, kasan: Silence KASAN warnings in get_wchan()
git bisect good d1f0f6c72c14af8a27a6549e0623f7cd61805e83 # 11:50 22+ 0 x86/intel-mid: Make intel_mid_ops static
git bisect good 8a5ec90292d4a7e5b133fd8d91ea3d1ddb9c2bff # 11:56 22+ 0 Merge branch 'x86/urgent'
git bisect bad 4183fdd83194ded503e1cec873556dd560f43dd4 # 11:59 0- 22 sched: fix incorrect wait time and wait count statistics
# first bad commit: [4183fdd83194ded503e1cec873556dd560f43dd4] sched: fix incorrect wait time and wait count statistics
git bisect good 8a5ec90292d4a7e5b133fd8d91ea3d1ddb9c2bff # 12:02 63+ 0 Merge branch 'x86/urgent'
# extra tests with DEBUG_INFO
git bisect bad 4183fdd83194ded503e1cec873556dd560f43dd4 # 12:06 0- 1 sched: fix incorrect wait time and wait count statistics
# extra tests on HEAD of linux-devel/devel-catchup-201510271010
git bisect bad d9e738c64efcbf03c53aae94700121e3c705fb65 # 12:06 0- 13 0day head guard for 'devel-catchup-201510271010'
# extra tests on tree/branch linux-review/Joonwoo-Park/sched-fix-incorrect-wait-time-and-wait-count-statistics/20151027-094629
git bisect bad 4183fdd83194ded503e1cec873556dd560f43dd4 # 12:07 0- 22 sched: fix incorrect wait time and wait count statistics
# extra tests with first bad commit reverted
git bisect good ee09e41c8647fc6e519783ec8b833de4c154d7f9 # 12:11 66+ 0 Revert "sched: fix incorrect wait time and wait count statistics"
# extra tests on tree/branch linus/master
git bisect good 858e904bd71dd0057a548d6785d94ce5ec4aeabd # 12:14 63+ 0 Merge tag 'iommu-fixes-v4.3-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu
# extra tests on tree/branch linux-next/master
git bisect good 6dcf94ff0c9e28e5790799e53641dd256745f425 # 12:18 65+ 0 Add linux-next specific files for 20151022
This script may reproduce the error.
----------------------------------------------------------------------------
#!/bin/bash
kernel=$1
initrd=quantal-core-i386.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
6 years, 6 months
[lkp] [x86] 0941ca402a: BUG: unable to handle kernel NULL pointer dereference at (null)
by kernel test robot
FYI, we noticed the below changes on
https://github.com/0day-ci/linux Borislav-Petkov/x86-Kill-notsc/20151018-222323
commit 0941ca402ab984dbc24d27df4def1a0aa4f082b1 ("x86: Kill notsc")
+--------------------------------------------------------+----------+------------+
| | v4.3-rc5 | 0941ca402a |
+--------------------------------------------------------+----------+------------+
| boot_successes | 3515 | 17 |
| boot_failures | 50 | 8 |
| invoked_oom-killer:gfp_mask=0x | 17 | |
| RIP:native_queued_spin_lock_slowpath | 7 | |
| Kernel_panic-not_syncing:softlockup:hung_tasks | 7 | |
| backtrace:lock_torture_writer | 7 | |
| drm:gen8_irq_handler[i915]] | 25 | |
| Mem-Info | 16 | |
| Out_of_memory:Kill_process | 16 | |
| backtrace:SyS_ioctl | 10 | |
| backtrace:SyS_write | 4 | |
| backtrace:do_wait | 2 | |
| backtrace:SyS_wait4 | 2 | |
| backtrace:_do_fork | 1 | |
| backtrace:SyS_clone | 1 | |
| backtrace:do_execveat_common | 1 | |
| backtrace:SyS_execve | 1 | |
| backtrace:vfs_read | 1 | |
| backtrace:SyS_read | 1 | |
| WARNING:at_fs/xfs/xfs_file.c:#xfs_file_dio_aio_write() | 3 | |
| backtrace:vfs_write | 3 | |
| BUG:kernel_early-boot_hang | 5 | |
| BUG:kernel_test_crashed | 2 | |
| BUG:kernel_test_oversize | 2 | |
| BUG:unable_to_handle_kernel | 0 | 8 |
| Oops | 0 | 8 |
| RIP:native_sched_clock | 0 | 8 |
| Kernel_panic-not_syncing:Fatal_exception | 0 | 8 |
| backtrace:sched_clock | 0 | 8 |
| backtrace:init_idle | 0 | 8 |
| backtrace:sched_init | 0 | 8 |
+--------------------------------------------------------+----------+------------+
[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.000000] Memory: 12095664K/12522424K available (8908K kernel code, 1731K rwdata, 4068K rodata, 1872K init, 1884K bss, 426760K reserved, 0K cma-reserved)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=24, Nodes=2
[ 0.000000] BUG: unable to handle kernel NULL pointer dereference at (null)
[ 0.000000] IP: [<ffffffff8101eec0>] native_sched_clock+0x30/0x70
[ 0.000000] PGD 0
[ 0.000000] Oops: 0000 [#1] SMP
[ 0.000000] Modules linked in:
[ 0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 4.3.0-rc5-00001-g0941ca4 #1
[ 0.000000] Hardware name: Intel Corporation S5520UR/S5520UR, BIOS S5500.86B.01.00.0050.050620101605 05/06/2010
[ 0.000000] task: ffffffff81cc2500 ti: ffffffff81cb0000 task.ti: ffffffff81cb0000
[ 0.000000] RIP: 0010:[<ffffffff8101eec0>] [<ffffffff8101eec0>] native_sched_clock+0x30/0x70
[ 0.000000] RSP: 0000:ffffffff81cb3ec0 EFLAGS: 00010046
[ 0.000000] RAX: 0000000000000000 RBX: ffffffff81cc2500 RCX: 0000004ccc5ef82e
[ 0.000000] RDX: 0000004c00000000 RSI: 0000000000000000 RDI: ffffffff81cc27f8
[ 0.000000] RBP: ffffffff81cb3ec0 R08: 0000000000000000 R09: ffff8801e9410240
[ 0.000000] R10: ffffffff81e521c0 R11: 0000000000010e00 R12: 0000000000000018
[ 0.000000] R13: ffff8801e9a17380 R14: ffffffff81cc2fc4 R15: 0000000000000000
[ 0.000000] FS: 0000000000000000(0000) GS:ffff8801e9a00000(0000) knlGS:0000000000000000
[ 0.000000] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 0.000000] CR2: 0000000000000000 CR3: 0000000001cbb000 CR4: 00000000000006b0
[ 0.000000] Stack:
[ 0.000000] ffffffff81cb3ed0 ffffffff8101ef7b ffffffff81cb3f10 ffffffff810a14ac
[ 0.000000] 0000000000000082 ffff88036fcd7380 0000000000000018 ffff88036fcd7530
[ 0.000000] 0000000000000018 0000000000017380 ffffffff81cb3f50 ffffffff81e9e9a4
[ 0.000000] Call Trace:
[ 0.000000] [<ffffffff8101ef7b>] sched_clock+0xb/0x10
[ 0.000000] [<ffffffff810a14ac>] init_idle+0x5c/0x1a0
[ 0.000000] [<ffffffff81e9e9a4>] sched_init+0x48e/0x4ed
[ 0.000000] [<ffffffff81e7ad5f>] start_kernel+0x235/0x463
[ 0.000000] [<ffffffff81e7a120>] ? early_idt_handler_array+0x120/0x120
[ 0.000000] [<ffffffff81e7a4d7>] x86_64_start_reservations+0x2a/0x2c
[ 0.000000] [<ffffffff81e7a60f>] x86_64_start_kernel+0x136/0x145
[ 0.000000] Code: 83 e4 f0 0f 31 48 c1 e2 20 48 89 d1 48 09 c1 65 ff 05 ad ce fe 7e 65 48 8b 35 bd 59 ff 7e 65 48 8b 05 bd 59 ff 7e 48 39 c6 75 17 <8b> 06 48 f7 e1 48 0f ac d0 0a 48 03 46 08 65 ff 0d 83 ce fe 7e
[ 0.000000] RIP [<ffffffff8101eec0>] native_sched_clock+0x30/0x70
[ 0.000000] RSP <ffffffff81cb3ec0>
[ 0.000000] CR2: 0000000000000000
[ 0.000000] ---[ end trace effcdd0592152294 ]---
[ 0.000000] 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,
Ying Huang
6 years, 6 months
[lkp] [mm, x86] 11e9fe5277: BUG: unable to handle kernel paging request at 0000000000001b08
by Huang Ying
FYI, we noticed the below changes on
https://github.com/jiangliu/linux.git test/memoryless_v7_2
commit 11e9fe52773abf7a9a66a6c93c54abeb218b48bb ("mm, x86: Enable
memoryless node to better support CPU/memory hotplug")
+------------------------------------------+------------+------------+
> | a006b58ac4 | 11e9fe5277 |
+------------------------------------------+------------+------------+
> boot_successes | 15 | 0 |
> boot_failures | 0 | 16 |
> BUG:unable_to_handle_kernel | 0 | 16 |
> Oops | 0 | 16 |
> RIP:__alloc_pages_nodemask | 0 | 16 |
> Kernel_panic-not_syncing:Fatal_exception | 0 | 16 |
> backtrace:_do_fork | 0 | 16 |
+------------------------------------------+------------+------------+
[ 0.108000] ..... host bus clock speed is 1000.0085 MHz.
[ 0.108069] smpboot: CPU0: Intel Core i7 9xx (Nehalem Class Core i7)
(family: 0x6, model: 0x1a, stepping: 0x3)
[ 0.116056] Performance Events: unsupported p6 CPU model 26 no PMU
driver, software events only.
[ 0.120108] BUG: unable to handle kernel paging request at
0000000000001b08
[ 0.124000] IP: [<ffffffff811b8e3e>]
__alloc_pages_nodemask+0xbc/0x870
[ 0.124000] PGD 0
[ 0.124000] Oops: 0000 [#1] SMP
[ 0.124000] Modules linked in:
[ 0.124000] CPU: 0 PID: 2 Comm: kthreadd Not tainted 4.3.0-rc4-00072
-g11e9fe5 #1
[ 0.124000] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),
BIOS Debian-1.8.2-1 04/01/2014
[ 0.124000] task: ffff8800129b8c40 ti: ffff8800129f4000 task.ti:
ffff8800129f4000
[ 0.124000] RIP: 0010:[<ffffffff811b8e3e>] [<ffffffff811b8e3e>]
__alloc_pages_nodemask+0xbc/0x870
[ 0.124000] RSP: 0000:ffff8800129f7a68 EFLAGS: 00010246
[ 0.124000] RAX: 0000000000000000 RBX: 0000000000201210 RCX:
0000000000000000
[ 0.124000] RDX: 0000000080000000 RSI: 0000000000001b00 RDI:
ffffffff81ec8413
[ 0.124000] RBP: ffff8800129f7b48 R08: 00000000000012d0 R09:
ffff8800129ba4c0
[ 0.124000] R10: 00000000002012d0 R11: ffff8800129b8c40 R12:
00000000002012d0
[ 0.124000] R13: 0000000000000002 R14: 0000000000000000 R15:
ffff8800129b8c40
[ 0.124000] FS: 0000000000000000(0000) GS:ffff880013800000(0000)
knlGS:0000000000000000
[ 0.124000] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 0.124000] CR2: 0000000000001b08 CR3: 000000000220b000 CR4:
00000000000006f0
[ 0.124000] Stack:
[ 0.124000] 0000000000000000 0000000000000000 0000000000000000
0000000000000000
[ 0.124000] 0000000000000000 0000000000000000 0000000000000000
0000000000000000
[ 0.124000] 0000000000000000 0000000000000000 0000000000000000
0000000000001b00
[ 0.124000] Call Trace:
[ 0.124000] [<ffffffff811f417d>] alloc_pages_current+0xc2/0xe1
[ 0.124000] [<ffffffff811faf53>] new_slab+0xd6/0x438
[ 0.124000] [<ffffffff811fcbe0>] __slab_alloc+0x416/0x59c
[ 0.124000] [<ffffffff8110ea04>] ? alloc_pid+0x2a/0x3fb
[ 0.124000] [<ffffffff811b8f37>] ?
__alloc_pages_nodemask+0x1b5/0x870
[ 0.124000] [<ffffffff81079267>] ? kvm_clock_read+0x25/0x2e
[ 0.124000] [<ffffffff811fce0f>] kmem_cache_alloc+0xa9/0x1cd
[ 0.124000] [<ffffffff811fce0f>] ? kmem_cache_alloc+0xa9/0x1cd
[ 0.124000] [<ffffffff8110ea04>] ? alloc_pid+0x2a/0x3fb
[ 0.124000] [<ffffffff8110ea04>] alloc_pid+0x2a/0x3fb
[ 0.124000] [<ffffffff811fcdac>] ? kmem_cache_alloc+0x46/0x1cd
[ 0.124000] [<ffffffff810f4581>] ? copy_process+0x81d/0x1844
[ 0.124000] [<ffffffff810f4e96>] copy_process+0x1132/0x1844
[ 0.124000] [<ffffffff8111ed45>] ? update_curr+0x70/0xf4
[ 0.124000] [<ffffffff81110543>] ?
kthread_create_on_node+0x18a/0x18a
[ 0.124000] [<ffffffff810418ad>] ? __switch_to+0x42f/0x493
[ 0.124000] [<ffffffff810f5701>] _do_fork+0x7d/0x30b
[ 0.124000] [<ffffffff81a36fbd>] ? __schedule+0x612/0x8b8
[ 0.124000] [<ffffffff810f59b8>] kernel_thread+0x29/0x2b
[ 0.124000] [<ffffffff81110efd>] kthreadd+0x1d5/0x225
[ 0.124000] [<ffffffff81110d28>] ? kthread_create_on_cpu+0x60/0x60
[ 0.124000] [<ffffffff81a3abaf>] ret_from_fork+0x3f/0x70
[ 0.124000] [<ffffffff81110d28>] ? kthread_create_on_cpu+0x60/0x60
[ 0.124000] Code: 5d 84 80 e3 10 89 45 d0 74 18 31 d2 be 8d 0c 00 00
48 c7 c7 13 84 ec 81 e8 1c dc f5 ff e8 96 e6 87 00 48 8b b5 78 ff ff ff
31 c0 <48> 83 7e 08 00 0f 84 9a 07 00 00 8a 4d 8c b0 01 d3 e0 48 98 48
[ 0.124000] RIP [<ffffffff811b8e3e>]
__alloc_pages_nodemask+0xbc/0x870
[ 0.124000] RSP <ffff8800129f7a68>
[ 0.124000] CR2: 0000000000001b08
[ 0.124000] ---[ end trace 27656104190f863a ]---
[ 0.124000] Kernel panic - not syncing: Fatal exception
Thanks,
Ying Huang
6 years, 6 months
[lkp] [vivid] bcd56c5678: BUG: unable to handle kernel NULL pointer dereference at 0000003c
by kernel test robot
FYI, we noticed the below changes on
git://linuxtv.org/hverkuil/media_tree.git sdrout
commit bcd56c567886b1ff0d2569d9cfe056ebbdad59c1 ("vivid: wip for sdr output")
[ 123.619858] evbug: Connected device: input1 (AT Translated Set 2 keyboard at isa0060/serio0/input0)
[ 123.662942] isa i2c-pca-isa.0: Please specify I/O base
[ 123.682577] vivid-000: using single planar format API
[ 123.690945] BUG: unable to handle kernel NULL pointer dereference at 0000003c
[ 123.691050] IP: [<4104ff19>] __lock_acquire+0x72/0xd33
[ 123.691050] *pde = 00000000
[ 123.691050] Oops: 0000 [#1]
[ 123.691050] CPU: 0 PID: 1 Comm: swapper Not tainted 4.3.0-rc1-00148-gbcd56c5 #2
[ 123.691050] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Debian-1.8.2-1 04/01/2014
[ 123.691050] task: 40011000 ti: 40022000 task.ti: 40022000
[ 123.691050] EIP: 0060:[<4104ff19>] EFLAGS: 00010002 CPU: 0
[ 123.691050] EIP is at __lock_acquire+0x72/0xd33
[ 123.691050] EAX: 00000046 EBX: 00000246 ECX: 00000000 EDX: 00000000
[ 123.691050] ESI: 0000003c EDI: 40011000 EBP: 40023d70 ESP: 40023d14
[ 123.691050] DS: 007b ES: 007b FS: 0000 GS: 00e0 SS: 0068
[ 123.691050] CR0: 8005003b CR2: 0000003c CR3: 02420000 CR4: 00000690
[ 123.691050] Stack:
[ 123.691050] 00000002 40023d24 41005feb 00000002 40023d30 41006475 00000000 40023d5c
[ 123.691050] 41045751 00000000 00000000 cc8dfb3f 00000001 40011428 00000001 40011428
[ 123.691050] 40023d6c 4104f530 4224d940 4224d940 00000246 0000003c 00000000 40023da0
[ 123.691050] Call Trace:
[ 123.691050] [<41005feb>] ? paravirt_sched_clock+0x9/0xd
[ 123.691050] [<41006475>] ? sched_clock+0x9/0xc
[ 123.691050] [<41045751>] ? sched_clock_local+0xe/0x10c
[ 123.691050] [<4104f530>] ? __lock_is_held+0x2d/0x43
[ 123.691050] [<41050eac>] lock_acquire+0x5e/0x7f
[ 123.691050] [<4173768d>] ? v4l2_ctrl_handler_setup+0x20/0xbe
[ 123.691050] [<41b17268>] mutex_lock_nested+0x48/0x2fd
[ 123.691050] [<4173768d>] ? v4l2_ctrl_handler_setup+0x20/0xbe
[ 123.691050] [<4173768d>] ? v4l2_ctrl_handler_setup+0x20/0xbe
[ 123.691050] [<41b18868>] ? __mutex_unlock_slowpath+0xf5/0xfd
[ 123.691050] [<4173768d>] v4l2_ctrl_handler_setup+0x20/0xbe
[ 123.691050] [<417447f8>] vivid_probe+0xc9f/0x171a
[ 123.691050] [<415b1695>] platform_drv_probe+0x3a/0x78
[ 123.691050] [<415b074f>] driver_probe_device+0xd1/0x1fa
[ 123.691050] [<415b08bb>] __driver_attach+0x43/0x5f
[ 123.691050] [<415af48b>] bus_for_each_dev+0x4e/0x6b
[ 123.691050] [<415b0a46>] driver_attach+0x14/0x16
[ 123.691050] [<415b0878>] ? driver_probe_device+0x1fa/0x1fa
[ 123.691050] [<415afaac>] bus_add_driver+0xb8/0x18a
[ 123.691050] [<415b0f0b>] driver_register+0x6f/0xa4
[ 123.691050] [<415b1e3d>] __platform_driver_register+0x3b/0x3d
[ 123.691050] [<423a7d31>] vivid_init+0x21/0x39
[ 123.691050] [<423a7d10>] ? viacam_driver_init+0x11/0x11
[ 123.691050] [<42375c35>] do_one_initcall+0x15e/0x16d
[ 123.691050] [<4237545b>] ? repair_env_string+0x12/0x54
[ 123.691050] [<4103ecab>] ? parse_args+0x18e/0x264
[ 123.691050] [<42375dc7>] kernel_init_freeable+0x183/0x200
[ 123.691050] [<41b147d2>] kernel_init+0x8/0xb0
[ 123.691050] [<41b1a060>] ret_from_kernel_thread+0x20/0x30
[ 123.691050] [<41b147ca>] ? rest_init+0x10e/0x10e
[ 123.691050] Code: 83 3d 00 ec c0 42 00 0f 85 97 00 00 00 68 45 c4 f6 41 68 5e 15 f6 41 68 11 0c 00 00 eb 6a 83 3d a8 c9 24 42 00 0f 84 80 00 00 00 <81> 3e 00 ea 42 42 b8 00 00 00 00 0f 45 45 0c 89 45 0c 83 fa 01
[ 123.691050] EIP: [<4104ff19>] __lock_acquire+0x72/0xd33 SS:ESP 0068:40023d14
[ 123.691050] CR2: 000000000000003c
[ 123.691050] ---[ end trace f7bd198a8c34c9de ]---
[ 123.691050] Kernel panic - not syncing: Fatal exception
Thanks,
Ying Huang
6 years, 6 months
[lkp] [drm] 6a9b928d41: WARNING: CPU: 0 PID: 1 at drivers/gpu/drm/drm_crtc.c:3598 drm_property_create+0x11f/0x140()
by kernel test robot
FYI, we noticed the below changes on
https://github.com/0day-ci/linux Shashank-Sharma/Color-Management-for-DRM-framework/20151020-202959
commit 6a9b928d4149ae2b195a2c13d55bf9c59a98c40c ("drm: Create Color Management query properties")
+--------------------------------------------------------------+------------+------------+
| | 44325dcfed | 6a9b928d41 |
+--------------------------------------------------------------+------------+------------+
| boot_successes | 15 | 0 |
| boot_failures | 0 | 11 |
| WARNING:at_drivers/gpu/drm/drm_crtc.c:#drm_property_create() | 0 | 11 |
| backtrace:drm_property_create | 0 | 11 |
| backtrace:drm_mode_config_init | 0 | 11 |
| backtrace:bochs_kms_init | 0 | 11 |
| backtrace:__pci_register_driver | 0 | 11 |
| backtrace:drm_pci_init | 0 | 11 |
| backtrace:bochs_init | 0 | 11 |
| backtrace:kernel_init_freeable | 0 | 11 |
+--------------------------------------------------------------+------------+------------+
[ 3.088019] [TTM] Zone kernel: Available graphics memory: 80722 kiB
[ 3.089216] [TTM] Initializing pool allocator
[ 3.090150] ------------[ cut here ]------------
[ 3.091098] WARNING: CPU: 0 PID: 1 at drivers/gpu/drm/drm_crtc.c:3598 drm_property_create+0x11f/0x140()
[ 3.093218] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.3.0-rc3-00447-g6a9b928 #1
[ 3.109890] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Debian-1.8.2-1 04/01/2014
[ 3.111674] 00000000 00000000 cb46fcdc c155c5a2 00000000 cb46fd10 c104e132 c2a474cc
[ 3.123017] 00000000 00000001 c2b4b4ac 00000e0e c173509f 00000e0e c173509f c9bc55a0
[ 3.127796] c9bb2e1c c2ab39c1 cb46fd20 c104e21b 00000009 00000000 cb46fd3c c173509f
[ 3.130073] Call Trace:
[ 3.130723] [<c155c5a2>] dump_stack+0x4b/0x79
[ 3.131648] [<c104e132>] warn_slowpath_common+0x82/0xc0
[ 3.132726] [<c173509f>] ? drm_property_create+0x11f/0x140
[ 3.142859] [<c173509f>] ? drm_property_create+0x11f/0x140
[ 3.150987] [<c104e21b>] warn_slowpath_null+0x1b/0x20
[ 3.152008] [<c173509f>] drm_property_create+0x11f/0x140
[ 3.153109] [<c1739b42>] drm_mode_config_init+0x502/0x570
[ 3.161237] [<c189395a>] bochs_kms_init+0x1a/0x120
[ 3.162235] [<c18927ac>] bochs_load+0x6c/0x90
[ 3.163154] [<c172d76e>] drm_dev_register+0x9e/0xb0
[ 3.164333] [<c172f864>] drm_get_pci_dev+0x74/0x1c0
[ 3.165326] [<c1892710>] bochs_pci_probe+0x70/0xa0
[ 3.166349] [<c15b157f>] pci_device_probe+0x7f/0xf0
[ 3.167365] [<c257b5d0>] ? _raw_spin_unlock+0x10/0x30
[ 3.168421] [<c18a37d6>] ? devices_kset_move_last+0x56/0xa0
[ 3.169539] [<c18a7c99>] driver_probe_device+0x139/0x490
[ 3.170608] [<c15b1242>] ? pci_match_device+0xc2/0xf0
[ 3.171670] [<c18a8079>] __driver_attach+0x89/0x90
[ 3.172645] [<c18a7ff0>] ? driver_probe_device+0x490/0x490
[ 3.193865] [<c18a6017>] bus_for_each_dev+0x47/0x80
[ 3.194873] [<c18a8159>] driver_attach+0x19/0x20
[ 3.203879] [<c18a7ff0>] ? driver_probe_device+0x490/0x490
[ 3.204979] [<c18a6a37>] bus_add_driver+0x1d7/0x280
[ 3.206013] [<c2e2b409>] ? qxl_init+0x43/0x43
[ 3.206938] [<c2e2b409>] ? qxl_init+0x43/0x43
[ 3.207865] [<c18a87c4>] driver_register+0x54/0xe0
[ 3.208877] [<c15b161e>] __pci_register_driver+0x2e/0x40
[ 3.209917] [<c172fa9a>] drm_pci_init+0xea/0x110
[ 3.210885] [<c2e2b409>] ? qxl_init+0x43/0x43
[ 3.211836] [<c2e2b41b>] bochs_init+0x12/0x14
[ 3.223822] [<c2dfccad>] do_one_initcall+0x17f/0x192
[ 3.224847] [<c2dfc4fa>] ? repair_env_string+0x12/0x54
[ 3.225890] [<c10668ef>] ? parse_args+0x1ef/0x4f0
[ 3.226878] [<c107302b>] ? __might_sleep+0x3b/0xc0
[ 3.227862] [<c2dfce24>] kernel_init_freeable+0x164/0x1e1
[ 3.228968] [<c2dfce24>] ? kernel_init_freeable+0x164/0x1e1
[ 3.230078] [<c25733bb>] kernel_init+0xb/0xe0
[ 3.231002] [<c106f75a>] ? schedule_tail+0x2a/0xa0
[ 3.232018] [<c257bc41>] ret_from_kernel_thread+0x21/0x30
[ 3.253128] [<c25733b0>] ? rest_init+0x80/0x80
[ 3.263116] ---[ end trace 067054755672de5e ]---
[ 3.264122] ------------[ cut here ]------------
Thanks,
Ying Huang
6 years, 6 months
[VSOCK] 10ea221658: INFO: trying to register non-static key.
by kernel test robot
Greetings,
0day kernel testing robot got the below dmesg and the first bad commit is
https://github.com/0day-ci/linux Jorgen-Hansen/VSOCK-sock_put-wasn-t-safe-to-call-in-interrupt-context/20151021-195643
commit 10ea22165889c160c983e221760c4b2921fa005f
Author: Jorgen Hansen <jhansen(a)vmware.com>
AuthorDate: Wed Oct 21 04:53:56 2015 -0700
Commit: 0day robot <fengguang.wu(a)intel.com>
CommitDate: Wed Oct 21 19:56:45 2015 +0800
VSOCK: sock_put wasn't safe to call in interrupt context
In the vsock vmci_transport driver, sock_put wasn't safe to call
in interrupt context, since that may call the vsock destructor
which in turn calls several functions that should only be called
from process context. This change defers the callling of these
functions to a worker thread. All these functions were
deallocation of resources related to the transport itself.
Furthermore, an unused callback was removed to simplify the
cleanup.
Multiple customers have been hitting this issue when using
VMware tools on vSphere 2015.
Also added a version to the vmci transport module (starting from
1.0.2.0-k since up until now it appears that this module was
sharing version with vsock that is currently at 1.0.1.0-k).
Reviewed-by: Aditya Asarwade <asarwade(a)vmware.com>
Reviewed-by: Thomas Hellstrom <thellstrom(a)vmware.com>
Signed-off-by: Jorgen Hansen <jhansen(a)vmware.com>
+----------------------------------------+------------+------------+-----------------+
| | 1099f86044 | 10ea221658 | v4.3-rc6_102202 |
+----------------------------------------+------------+------------+-----------------+
| boot_successes | 910 | 293 | 42 |
| boot_failures | 0 | 17 | 2 |
| INFO:trying_to_register_non-static_key | 0 | 17 | 2 |
| backtrace:do_group_exit | 0 | 12 | 2 |
| backtrace:SyS_exit_group | 0 | 12 | 2 |
| Out_of_memory:Kill_process | 0 | 1 | |
| page_allocation_failure:order:#,mode | 0 | 1 | |
| warn_alloc_failed+0x | 0 | 1 | |
| Mem-Info | 0 | 1 | |
| backtrace:ring_buffer_consumer_thread | 0 | 1 | |
+----------------------------------------+------------+------------+-----------------+
[child1:496] mq_unlink (241) returned ENOSYS, marking as inactive.
[child1:496] uid changed! Was: 0, now 2147483394
Bailing main loop. Exit reason: UID changed.
[ 53.674274] INFO: trying to register non-static key.
[ 53.675023] the code is fine but needs lockdep annotation.
[ 53.675023] turning off the locking correctness validator.
[ 53.675023] CPU: 1 PID: 461 Comm: trinity-main Not tainted 4.3.0-rc6-00106-g10ea221 #1
[ 53.675023] 0000000000000000 ffff880009797bc0 ffffffff812a7c13 0000000000000000
[ 53.675023] ffff880009797c30 ffffffff8111a6cb ffff880009797ff0 0000000000000000
[ 53.675023] 0000000000000046 ffff880009797c28 000000008111a031 ffffffff81e106e0
[ 53.675023] Call Trace:
[ 53.675023] [<ffffffff812a7c13>] dump_stack+0x4b/0x63
[ 53.675023] [<ffffffff8111a6cb>] register_lock_class+0x161/0x31a
[ 53.675023] [<ffffffff8111b576>] __lock_acquire+0xf4/0x542
[ 53.675023] [<ffffffff8111bcfb>] lock_acquire+0xa4/0x11b
[ 53.675023] [<ffffffff81c32a06>] ? vmci_transport_destruct+0x20/0xbd
[ 53.675023] [<ffffffff81c40202>] _raw_spin_lock_bh+0x33/0x42
[ 53.675023] [<ffffffff81c32a06>] ? vmci_transport_destruct+0x20/0xbd
[ 53.675023] [<ffffffff81c32a06>] vmci_transport_destruct+0x20/0xbd
[ 53.675023] [<ffffffff81c30257>] vsock_sk_destruct+0x17/0x5f
[ 53.675023] [<ffffffff81a0c042>] sk_destruct+0x1f/0x15b
[ 53.675023] [<ffffffff81a0c1fe>] __sk_free+0x80/0xa6
[ 53.675023] [<ffffffff81a0c297>] sk_free+0x18/0x1a
[ 53.675023] [<ffffffff81c2f98f>] sock_put+0x10/0x12
[ 53.675023] [<ffffffff81c30e64>] __vsock_release+0x11b/0x15e
[ 53.675023] [<ffffffff81c30ebd>] vsock_release+0x16/0x29
[ 53.675023] [<ffffffff81a09479>] sock_release+0x19/0x65
[ 53.675023] [<ffffffff81a094d7>] sock_close+0x12/0x16
[ 53.675023] [<ffffffff811cfc68>] __fput+0x138/0x20b
[ 53.675023] [<ffffffff811cfd71>] ____fput+0xe/0x10
[ 53.675023] [<ffffffff810f80a5>] task_work_run+0x6a/0x93
[ 53.675023] [<ffffffff810dff52>] do_exit+0x4ee/0xb2e
[ 53.675023] [<ffffffff810e062f>] do_group_exit+0x67/0xe4
[ 53.675023] [<ffffffff810e06c0>] SyS_exit_group+0x14/0x14
[ 53.675023] [<ffffffff81c40ab6>] entry_SYSCALL_64_fastpath+0x16/0x7a
[watchdog] [467] Watchdog exiting
git bisect start 24ef915bc831256daeeab348b7792ce94949e6a8 7379047d5585187d1288486d4627873170d0005a --
git bisect bad 5df0024b1e0d9bfb210867d02c7fc7dc1e377552 # 05:03 37- 2 Merge 'nf/master' into devel-hourly-2015102202
git bisect bad 4911f4acd02699f14bb2db70b0aeba9e4ac0d537 # 05:17 148- 1 Merge 'linux-review/Zefir-Kurtisi/ath9k-fix-phyerror-codes/20151020-202150' into devel-hourly-2015102202
git bisect bad 9eca62a54d4d04c0be91cf5263de97bff45a6acd # 05:31 8- 1 Merge 'snitzer/wip' into devel-hourly-2015102202
git bisect bad faf630a594897df1913d3ce8558343ecc16de980 # 05:46 27- 1 Merge 'linux-review/Guilherme-G-Piccoli/Enable-MSI-MSI-X-caps-and-disable-MSI-interrupts-at-PCI-probe-time-code-move/20151021-221849' into devel-hourly-2015102202
git bisect good 453b2a6d0389adf1a114d6927a47cfcf81ffcdf9 # 06:06 307+ 0 Merge 'hid/for-next' into devel-hourly-2015102202
git bisect good 0ef86d90815e455bf0539ec08fabf31bad57dcd0 # 06:21 305+ 0 Merge 'linux-review/Suravee-Suthikulpanit/PCI-ACPI-Setting-up-DMA-coherency-for-PCI-device-from-_CCA-attribute/20151021-235930' into devel-hourly-2015102202
git bisect good 5246058bb053223e4ab5e74b10181c59346934ea # 06:36 301+ 1 Merge 'sound/topic/hw-constraint-single' into devel-hourly-2015102202
git bisect bad 175246062bb9b7a27d62c788bdf380ff303289cc # 06:52 9- 1 Merge 'linux-review/Jorgen-Hansen/VSOCK-sock_put-wasn-t-safe-to-call-in-interrupt-context/20151021-195643' into devel-hourly-2015102202
git bisect good 0c4188c0e39b44588fd0ac88ec9f5c31136fbdd4 # 07:03 309+ 0 Merge 'linux-review/Karsten-Keil/ISDN-fix-OOM-condition-for-sending-queued-I-Frames/20151021-202945' into devel-hourly-2015102202
git bisect good 75b1209636fd9847bde88c9121adb81b30bc2aee # 07:16 306+ 0 Merge 'asoc/fix/da7219' into devel-hourly-2015102202
git bisect bad 10ea22165889c160c983e221760c4b2921fa005f # 07:24 1- 1 VSOCK: sock_put wasn't safe to call in interrupt context
# first bad commit: [10ea22165889c160c983e221760c4b2921fa005f] VSOCK: sock_put wasn't safe to call in interrupt context
git bisect good 1099f86044111e9a7807f09523e42d4c9d0fb781 # 07:46 910+ 0 Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net
# extra tests with DEBUG_INFO
git bisect bad 10ea22165889c160c983e221760c4b2921fa005f # 07:52 52- 7 VSOCK: sock_put wasn't safe to call in interrupt context
# extra tests on HEAD of linux-devel/devel-hourly-2015102202
git bisect bad 24ef915bc831256daeeab348b7792ce94949e6a8 # 07:52 0- 2 0day head guard for 'devel-hourly-2015102202'
# extra tests on tree/branch linux-review/Jorgen-Hansen/VSOCK-sock_put-wasn-t-safe-to-call-in-interrupt-context/20151021-195643
git bisect bad 10ea22165889c160c983e221760c4b2921fa005f # 07:53 0- 17 VSOCK: sock_put wasn't safe to call in interrupt context
# extra tests with first bad commit reverted
git bisect good 25963bf38262c9c2b5f5210c6f8c79ea1dd45b95 # 08:19 902+ 0 Revert "VSOCK: sock_put wasn't safe to call in interrupt context"
# extra tests on tree/branch linus/master
git bisect good 8a70dd2669200ce83255ed8c5ebef7e59f9e8707 # 08:43 909+ 0 Merge tag 'for-linus-20151021' of git://git.infradead.org/intel-iommu
# extra tests on tree/branch linux-next/master
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
6 years, 6 months
[lkp] [sched/numa] b52da86e0a: -1.4% will-it-scale.per_thread_ops
by kernel test robot
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
commit b52da86e0ad58f096710977fcda856fd84da9233 ("sched/numa: Fix task_tick_fair() from disabling numa_balancing")
=========================================================================================
tbox_group/testcase/rootfs/kconfig/compiler/cpufreq_governor/test:
nhm4/will-it-scale/debian-x86_64-2015-02-07.cgz/x86_64-rhel/gcc-4.9/performance/readseek1
commit:
e2bf1c4b17aff25f07e0d2952d8c1c66643f33fe
b52da86e0ad58f096710977fcda856fd84da9233
e2bf1c4b17aff25f b52da86e0ad58f096710977fcd
---------------- --------------------------
%stddev %change %stddev
\ | \
1868374 ± 0% -1.4% 1843108 ± 0% will-it-scale.per_thread_ops
0.57 ± 0% +14.1% 0.65 ± 10% will-it-scale.scalability
14052 ± 0% -29.6% 9896 ± 0% will-it-scale.time.minor_page_faults
161.75 ± 45% -53.2% 75.75 ± 23% cpuidle.C1E-NHM.usage
14052 ± 0% -29.6% 9896 ± 0% time.minor_page_faults
6943 ± 0% -100.0% 0.00 ± -1% proc-vmstat.numa_hint_faults
6943 ± 0% -100.0% 0.00 ± -1% proc-vmstat.numa_hint_faults_local
7780 ± 0% -100.0% 0.00 ± -1% proc-vmstat.numa_pte_updates
1.19 ± 4% -14.1% 1.02 ± 4% perf-profile.cpu-cycles.__fget_light.sys_lseek.entry_SYSCALL_64_fastpath
5.47 ± 1% -11.8% 4.83 ± 2% perf-profile.cpu-cycles.entry_SYSCALL_64
1.17 ± 6% -16.7% 0.98 ± 12% perf-profile.cpu-cycles.fsnotify.vfs_read.sys_read.entry_SYSCALL_64_fastpath
1.70 ± 4% -15.0% 1.45 ± 4% perf-profile.cpu-cycles.shmem_file_llseek.sys_lseek.entry_SYSCALL_64_fastpath
5.39 ± 1% -12.8% 4.70 ± 5% perf-profile.cpu-cycles.sys_lseek.entry_SYSCALL_64_fastpath
116.50 ± 14% -35.4% 75.25 ± 13% sched_debug.cfs_rq[2]:/.load
95126 ± 8% +17.5% 111795 ± 10% sched_debug.cpu#0.nr_load_updates
2464 ± 6% -39.4% 1494 ± 29% sched_debug.cpu#2.curr->pid
116.50 ± 14% -35.4% 75.25 ± 13% sched_debug.cpu#2.load
1243 ± 2% +50.4% 1870 ± 22% sched_debug.cpu#3.curr->pid
17134 ± 29% +7834.3% 1359530 ±110% sched_debug.cpu#4.nr_switches
17204 ± 29% +7802.5% 1359602 ±110% sched_debug.cpu#4.sched_count
4538 ± 78% +12299.8% 562734 ±119% sched_debug.cpu#4.sched_goidle
950401 ± 4% -7.9% 875553 ± 4% sched_debug.cpu#7.avg_idle
nhm4: Nehalem
Memory: 4G
proc-vmstat.numa_pte_updates
8000 ++---------------------------------------------------*---*-*-----*-*-+
| * * *.* *
7000 ++ : |
| : |
| : |
6000 ++ : |
| : |
5000 ++ : |
| : |
4000 ++ : |
| : |
| : |
3000 ++ : |
*.*.*.*.*.*.*.*.*.*.*.*.*.*.*.*.*..*.*.*.*.*.*.*.* |
2000 ++-------------------------------------------------------------------+
proc-vmstat.numa_hint_faults
7000 ++-------------------------------------------------*-*-*-*-*-*-*-*-*-*
| : |
6000 ++ : |
| : |
| : |
5000 ++ : |
| : |
4000 ++ : |
| : |
3000 ++ : |
| : |
| : |
2000 ++ : |
*.*.*.*.*.*.*.*.*.*.*.*.*.*.*.*.*..*.*.*.*.*.*.*.* |
1000 ++-------------------------------------------------------------------+
proc-vmstat.numa_hint_faults_local
7000 ++-------------------------------------------------*-*-*-*-*-*-*-*-*-*
| : |
6000 ++ : |
| : |
| : |
5000 ++ : |
| : |
4000 ++ : |
| : |
3000 ++ : |
| : |
| : |
2000 ++ : |
*.*.*.*.*.*.*.*.*.*.*.*.*.*.*.*.*..*.*.*.*.*.*.*.* |
1000 ++-------------------------------------------------------------------+
[*] 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,
Ying Huang
6 years, 6 months
[lkp] [string] 3fda0fa0f5: BUG: KASan: out of bounds access in strscpy+0xc2/0x290 at addr ffff880016b83ee0
by kernel test robot
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.core/strings
commit 3fda0fa0f5ed4ef634e043c65709482aea0a37f6 ("string: Improve the generic strlcpy() implementation")
+------------------------------------------------------+------------+------------+
| | 314edb34c9 | 3fda0fa0f5 |
+------------------------------------------------------+------------+------------+
| boot_successes | 15 | 11 |
| boot_failures | 0 | 4 |
| BUG:KASan:out_of_bounds_access | 0 | 4 |
| BUG_kmalloc-#(Not_tainted):kasan:bad_access_detected | 0 | 4 |
| INFO:Slab#objects=#used=#fp=0x(null)flags= | 0 | 4 |
| INFO:Object#@offset=#fp= | 0 | 4 |
| backtrace:vfs_write | 0 | 4 |
| backtrace:SyS_write | 0 | 4 |
+------------------------------------------------------+------------+------------+
Failed to configure loopback device: Operation not supported
Using cgroup controller name=systemd. File system hierarchy is at /sys/fs/cgroup/systemd.
[ 57.599568] ==================================================================
[ 57.600517] BUG: KASan: out of bounds access in strscpy+0xc2/0x290 at addr ffff880016b83ee0
[ 57.601541] Read of size 8 by task systemd/1
[ 57.602068] =============================================================================
[ 57.603081] BUG kmalloc-64 (Not tainted): kasan: bad access detected
[ 57.603907] -----------------------------------------------------------------------------
[ 57.603907]
[ 57.607113] Disabling lock debugging due to kernel taint
[ 57.607113] INFO: Slab 0xffffea00005ae0c0 objects=64 used=64 fp=0x (null) flags=0x4000000000000080
[ 57.607113] INFO: Object 0xffff880016b83ec0 @offset=3776 fp=0x7379732f62696c2f
[ 57.607113]
[ 57.607113] Bytes b4 ffff880016b83eb0: 64 2f 73 6f 63 2f 78 74 65 6e 73 61 00 00 00 00 d/soc/xtensa....
[ 57.607113] Object ffff880016b83ec0: 2f 6c 69 62 2f 73 79 73 74 65 6d 64 2f 73 79 73 /lib/systemd/sys
[ 57.607113] Object ffff880016b83ed0: 74 65 6d 64 2d 63 67 72 6f 75 70 73 2d 61 67 65 temd-cgroups-age
[ 57.607113] Object ffff880016b83ee0: 6e 74 00 00 00 00 00 00 a0 95 bf 3f 00 88 ff ff nt.........?....
[ 57.607113] Object ffff880016b83ef0: 00 00 00 00 00 00 00 00 e7 60 49 f8 07 00 00 00 .........`I.....
[ 57.607113] CPU: 0 PID: 1 Comm: systemd Tainted: G B 4.3.0-rc4-00262-g3fda0fa #1
[ 57.607113] 0000000000001000 ffff88002e86fb80 ffffffff8133a029 ffff88002e86fbb0
[ 57.607113] ffffffff81198982 ffff88002e801b00 ffffea00005ae0c0 ffff880016b83ec0
[ 57.607113] 0000000000000020 ffff88002e86fbd8 ffffffff8119de31 ffff88002e86fc68
[ 57.607113] Call Trace:
[ 57.607113] [<ffffffff8133a029>] dump_stack+0x19/0x20
[ 57.607113] [<ffffffff81198982>] print_trailer+0xd2/0x120
[ 57.607113] [<ffffffff8119de31>] object_err+0x31/0x40
[ 57.607113] [<ffffffff8119fa4d>] kasan_report_error+0x1dd/0x400
[ 57.607113] [<ffffffff811a0053>] kasan_report+0x33/0x40
[ 57.607113] [<ffffffff813467a2>] ? strscpy+0xc2/0x290
[ 57.607113] [<ffffffff8119ec44>] __asan_load8+0x64/0xa0
[ 57.607113] [<ffffffff813467a2>] strscpy+0xc2/0x290
[ 57.607113] [<ffffffff81346984>] strlcpy+0x14/0x60
[ 57.607113] [<ffffffff81115d77>] cgroup_release_agent_write+0x67/0xa0
[ 57.607113] [<ffffffff811150d1>] cgroup_file_write+0x81/0x1d0
[ 57.607113] [<ffffffff81115050>] ? allocate_cgrp_cset_links+0xf0/0xf0
[ 57.607113] [<ffffffff81227fea>] kernfs_fop_write+0x18a/0x210
[ 57.607113] [<ffffffff811b6127>] __vfs_write+0x57/0x170
[ 57.607113] [<ffffffff810cea15>] ? percpu_down_read+0x55/0x90
[ 57.607113] [<ffffffff811b92e0>] ? __sb_start_write+0xc0/0xe0
[ 57.607113] [<ffffffff811b92e0>] ? __sb_start_write+0xc0/0xe0
[ 57.607113] [<ffffffff811b695c>] vfs_write+0xec/0x240
[ 57.607113] [<ffffffff811b75bd>] SyS_write+0x5d/0xc0
[ 57.607113] [<ffffffff81acacef>] entry_SYSCALL_64_fastpath+0x12/0x76
[ 57.607113] Memory state around the buggy address:
Thanks,
Ying Huang
6 years, 6 months