[PM] 83d542a1f8: BUG:sleeping_function_called_from_invalid_context_at_kernel/locking/mutex.c
by kernel test robot
FYI, we noticed the following commit (built with gcc-7):
commit: 83d542a1f8a4df21275c873e9cde97cd49862f9d ("[PATCH 2/2] PM-runtime: allow userspace to monitor runtime_status changes")
url: https://github.com/0day-ci/linux/commits/Akinobu-Mita/PM-runtime-Document...
in testcase: boot
on test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 4G
caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
+-----------------------------------------------------------------------------+------------+------------+
| | 403a5ea4a9 | 83d542a1f8 |
+-----------------------------------------------------------------------------+------------+------------+
| boot_successes | 12 | 0 |
| boot_failures | 0 | 36 |
| BUG:sleeping_function_called_from_invalid_context_at_kernel/locking/mutex.c | 0 | 36 |
+-----------------------------------------------------------------------------+------------+------------+
If you fix the issue, kindly add following tag
Reported-by: kernel test robot <rong.a.chen(a)intel.com>
[ 3.341692] BUG: sleeping function called from invalid context at kernel/locking/mutex.c:255
[ 3.342796] in_atomic(): 1, irqs_disabled(): 1, pid: 1, name: swapper/0
[ 3.342796] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.3.0-rc6-00242-g83d542a1f8a4d #1
[ 3.342796] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1 04/01/2014
[ 3.342796] Call Trace:
[ 3.342796] dump_stack+0x67/0x8e
[ 3.342796] ___might_sleep+0xf8/0x109
[ 3.342796] mutex_lock+0x1c/0x3b
[ 3.342796] kernfs_find_and_get_ns+0x22/0x55
[ 3.342796] sysfs_notify+0x22/0x6e
[ 3.342796] rpm_suspend+0x2c4/0x50e
[ 3.342796] __pm_runtime_idle+0x69/0x84
[ 3.342796] scsi_add_host_with_dma+0x1c2/0x296
[ 3.342796] virtscsi_probe+0x379/0x43c
[ 3.342796] virtio_dev_probe+0x139/0x1bf
[ 3.342796] really_probe+0x19c/0x361
[ 3.342796] ? set_debug_rodata+0x11/0x11
[ 3.342796] driver_probe_device+0xd9/0x10e
[ 3.342796] device_driver_attach+0x3b/0x53
[ 3.342796] __driver_attach+0x112/0x11a
[ 3.342796] ? device_driver_attach+0x53/0x53
[ 3.342796] ? device_driver_attach+0x53/0x53
[ 3.342796] bus_for_each_dev+0x71/0xa3
[ 3.342796] bus_add_driver+0x129/0x1d8
[ 3.342796] ? hptiop_module_init+0x34/0x34
[ 3.342796] driver_register+0x99/0xcb
[ 3.342796] ? hptiop_module_init+0x34/0x34
[ 3.342796] init+0x7a/0xc0
[ 3.342796] do_one_initcall+0x97/0x1b4
[ 3.342796] kernel_init_freeable+0x236/0x2cf
[ 3.342796] ? rest_init+0xc6/0xc6
[ 3.342796] kernel_init+0xa/0xff
[ 3.342796] ret_from_fork+0x3a/0x50
[ 3.434435] ata_piix 0000:00:01.1: version 2.13
[ 3.436051] scsi 0:0:1:0: Direct-Access QEMU QEMU HARDDISK 2.5+ PQ: 0 ANSI: 5
[ 3.445018] scsi host1: ata_piix
[ 3.445843] scsi 0:0:1:10: Direct-Access QEMU QEMU HARDDISK 2.5+ PQ: 0 ANSI: 5
[ 3.447702] scsi host2: ata_piix
[ 3.455245] scsi 0:0:1:9: Direct-Access QEMU QEMU HARDDISK 2.5+ PQ: 0 ANSI: 5
[ 3.456948] ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc080 irq 14
[ 3.464605] scsi 0:0:1:8: Direct-Access QEMU QEMU HARDDISK 2.5+ PQ: 0 ANSI: 5
[ 3.467114] ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc088 irq 15
[ 3.467187] MACsec IEEE 802.1AE
[ 3.475785] scsi 0:0:1:7: Direct-Access QEMU QEMU HARDDISK 2.5+ PQ: 0 ANSI: 5
[ 3.478412] pcnet32: pcnet32.c:v1.35 21.Apr.2008 tsbogend(a)alpha.franken.de
[ 3.481462] scsi 0:0:1:6: Direct-Access QEMU QEMU HARDDISK 2.5+ PQ: 0 ANSI: 5
[ 3.486427] Atheros(R) L2 Ethernet Driver - version 2.2.3
[ 3.491281] scsi 0:0:1:5: Direct-Access QEMU QEMU HARDDISK 2.5+ PQ: 0 ANSI: 5
[ 3.494578] Copyright (c) 2007 Atheros Corporation.
[ 3.499451] scsi 0:0:1:4: Direct-Access QEMU QEMU HARDDISK 2.5+ PQ: 0 ANSI: 5
[ 3.503431] dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
[ 3.507849] scsi 0:0:1:3: Direct-Access QEMU QEMU HARDDISK 2.5+ PQ: 0 ANSI: 5
[ 3.511572] v1.01-e (2.4 port) Sep-11-2006 Donald Becker <becker(a)scyld.com>
[ 3.511572] http://www.scyld.com/network/drivers.html
[ 3.517004] scsi 0:0:1:2: Direct-Access QEMU QEMU HARDDISK 2.5+ PQ: 0 ANSI: 5
[ 3.520772] uli526x: ULi M5261/M5263 net driver, version 0.9.3 (2005-7-29)
[ 3.530391] scsi 0:0:1:1: Direct-Access QEMU QEMU HARDDISK 2.5+ PQ: 0 ANSI: 5
[ 3.534103] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
[ 3.546964] e100: Copyright(c) 1999-2006 Intel Corporation
[ 3.550088] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
[ 3.553538] e1000: Copyright (c) 1999-2006 Intel Corporation.
[ 3.576790] random: fast init done
[ 3.583910] sd 0:0:1:0: Attached scsi generic sg0 type 0
[ 3.586427] sd 0:0:1:0: Power-on or device reset occurred
[ 3.586561] scsi 0:0:1:10: Attached scsi generic sg1 type 0
[ 3.591667] sd 0:0:1:10: Power-on or device reset occurred
[ 3.593490] PCI Interrupt Link [LNKC] enabled at IRQ 10
[ 3.594410] scsi 0:0:1:9: Attached scsi generic sg2 type 0
[ 3.600416] sd 0:0:1:9: Power-on or device reset occurred
[ 3.600975] scsi 0:0:1:8: Attached scsi generic sg3 type 0
[ 3.605490] sd 0:0:1:8: Power-on or device reset occurred
[ 3.605599] scsi 0:0:1:7: Attached scsi generic sg4 type 0
[ 3.610565] sd 0:0:1:7: Power-on or device reset occurred
[ 3.610676] scsi 0:0:1:6: Attached scsi generic sg5 type 0
[ 3.613047] sd 0:0:1:0: [sda] 536870912 512-byte logical blocks: (275 GB/256 GiB)
[ 3.615617] scsi 0:0:1:5: Attached scsi generic sg6 type 0
[ 3.622123] sd 0:0:1:6: Power-on or device reset occurred
[ 3.622229] scsi 0:0:1:4: Attached scsi generic sg7 type 0
[ 3.624603] sd 0:0:1:5: Power-on or device reset occurred
[ 3.624711] sd 0:0:1:0: [sda] Write Protect is off
[ 3.624712] sd 0:0:1:0: [sda] Mode Sense: 63 00 00 08
[ 3.624832] sd 0:0:1:4: Power-on or device reset occurred
[ 3.624892] sd 0:0:1:10: [sdb] 536870912 512-byte logical blocks: (275 GB/256 GiB)
[ 3.627546] sd 0:0:1:10: [sdb] Write Protect is off
[ 3.630466] scsi 0:0:1:3: Attached scsi generic sg8 type 0
[ 3.632346] sd 0:0:1:10: [sdb] Mode Sense: 63 00 00 08
[ 3.635260] scsi 0:0:1:2: Attached scsi generic sg9 type 0
[ 3.637318] sd 0:0:1:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 3.641393] scsi 0:0:1:1: Attached scsi generic sg10 type 0
[ 3.643551] sd 0:0:1:3: Power-on or device reset occurred
[ 3.646351] sd 0:0:1:2: Power-on or device reset occurred
[ 3.654689] ata2.01: NODEV after polling detection
[ 3.666877] sd 0:0:1:1: Power-on or device reset occurred
[ 3.669532] sd 0:0:1:9: [sdc] 536870912 512-byte logical blocks: (275 GB/256 GiB)
[ 3.672324] sd 0:0:1:2: [sdj] 536870912 512-byte logical blocks: (275 GB/256 GiB)
[ 3.673929] sd 0:0:1:8: [sdd] 536870912 512-byte logical blocks: (275 GB/256 GiB)
[ 3.677760] sd 0:0:1:10: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 3.681647] sd 0:0:1:9: [sdc] Write Protect is off
[ 3.688485] sd 0:0:1:9: [sdc] Mode Sense: 63 00 00 08
[ 3.690948] sd 0:0:1:7: [sde] 536870912 512-byte logical blocks: (275 GB/256 GiB)
[ 3.691036] sd 0:0:1:2: [sdj] Write Protect is off
To reproduce:
# build kernel
cd linux
cp config-5.3.0-rc6-00242-g83d542a1f8a4d .config
make HOSTCC=gcc-7 CC=gcc-7 ARCH=x86_64 olddefconfig prepare modules_prepare bzImage
git clone https://github.com/intel/lkp-tests.git
cd lkp-tests
bin/lkp qemu -k <bzImage> job-script # job-script is attached in this email
Thanks,
Rong Chen
9 months
[x86/alternatives, jump_label] 72b31377bd: WARNING:at_arch/x86/kernel/jump_label.c:#__jump_label_set_jump_code
by kernel test robot
FYI, we noticed the following commit (built with gcc-7):
commit: 72b31377bd60b8cab549a83c79639ed8c811aee5 ("x86/alternatives,jump_label: Provide better text_poke() batching interface")
https://kernel.googlesource.com/pub/scm/linux/kernel/git/peterz/queue.git x86/ftrace
in testcase: rcutorture
with following parameters:
runtime: 300s
test: cpuhotplug
torture_type: rcu
test-description: rcutorture is rcutorture kernel module load/unload test.
test-url: https://www.kernel.org/doc/Documentation/RCU/torture.txt
on test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 4G
caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
+---------------------------------------------------------------------------+------------+------------+
| | 80f767293e | 72b31377bd |
+---------------------------------------------------------------------------+------------+------------+
| boot_successes | 0 | 0 |
| boot_failures | 4 | 4 |
| BUG:kernel_hang_in_boot_stage | 4 | 3 |
| dmesg.RIP:__jump_label_set_jump_code | 4 | 4 |
| dmesg.WARNING:at_arch/x86/kernel/jump_label.c:#__jump_label_set_jump_code | 4 | 4 |
+---------------------------------------------------------------------------+------------+------------+
If you fix the issue, kindly add following tag
Reported-by: kernel test robot <rong.a.chen(a)intel.com>
[ 0.000000] WARNING: CPU: 0 PID: 0 at arch/x86/kernel/jump_label.c:47 __jump_label_set_jump_code+0x63/0x121
[ 0.000000] Modules linked in:
[ 0.000000] CPU: 0 PID: 0 Comm: swapper Tainted: G W 5.3.0-rc6-00121-g72b31377bd60b #1
[ 0.000000] RIP: 0010:__jump_label_set_jump_code+0x63/0x121
[ 0.000000] Code: c6 44 24 0f 00 48 8b 68 48 74 21 83 ce ff 48 c7 c7 58 0d c6 b1 e8 3a fa 0e 00 85 c0 75 0e 48 c7 c7 08 28 93 b1 e8 4a e4 0f 00 <0f> 0b 48 63 43 04 c6 05 b0 e4 e8 01 e9 8d 44 03 ff 2b 03 29 d8 45
[ 0.000000] RSP: 0000:ffffffffb1c03e58 EFLAGS: 00010082 ORIG_RAX: 0000000000000000
[ 0.000000] RAX: 0000000000000024 RBX: ffffffffb1a33688 RCX: ffffffffb0537efe
[ 0.000000] RDX: 0000000000000000 RSI: ffffffffb1c28800 RDI: ffffffffb0535562
[ 0.000000] RBP: ffffffffb1604784 R08: 0000000000000001 R09: 000000000000000c
[ 0.000000] R10: ffffffffb1c03eb0 R11: 0000000000000001 R12: 0000000000000000
[ 0.000000] R13: 0000000000000001 R14: 0000000000000000 R15: 0000000000000000
[ 0.000000] FS: 0000000000000000(0000) GS:ffffffffb1c51000(0000) knlGS:0000000000000000
[ 0.000000] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 0.000000] CR2: ffff8880000145d0 CR3: 0000000106dff000 CR4: 00000000000406a0
[ 0.000000] Call Trace:
[ 0.000000] ? __jump_label_transform+0xc/0x3d
[ 0.000000] ? jump_label_init+0x8d/0x10f
[ 0.000000] ? 0xffffffffb0400000
[ 0.000000] ? setup_arch+0xb9/0x896
[ 0.000000] ? start_kernel+0x8b/0x795
[ 0.000000] ? load_ucode_bsp+0x16d/0x1a1
[ 0.000000] ? secondary_startup_64+0xa4/0xb0
[ 0.000000] irq event stamp: 0
[ 0.000000] hardirqs last enabled at (0): [<0000000000000000>] 0x0
[ 0.000000] hardirqs last disabled at (0): [<0000000000000000>] 0x0
[ 0.000000] softirqs last enabled at (0): [<0000000000000000>] 0x0
[ 0.000000] softirqs last disabled at (0): [<0000000000000000>] 0x0
[ 0.000000] ---[ end trace f68728a0d30543a5 ]---
To reproduce:
git clone https://github.com/intel/lkp-tests.git
cd lkp-tests
bin/lkp qemu -k <bzImage> job-script # job-script is attached in this email
Thanks,
Rong Chen
9 months
[btrfs] 96a85793d6: BUG:kernel_NULL_pointer_dereference, address
by kernel test robot
FYI, we noticed the following commit (built with gcc-7):
commit: 96a85793d686c4db3ef9963429dea95d00467222 ("btrfs: Use iomap_dio_rw for performing direct I/O writes")
https://github.com/goldwynr/linux btrfs-iomap
in testcase: ltp
with following parameters:
disk: 1HDD
fs: btrfs
test: ltp-aiodio.part2
test-description: The LTP testsuite contains a collection of tools for testing the Linux kernel and related features.
test-url: http://linux-test-project.github.io/
on test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 8G
caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
+---------------------------------------------+------------+------------+
| | ac1ce96393 | 96a85793d6 |
+---------------------------------------------+------------+------------+
| boot_successes | 4 | 0 |
| boot_failures | 0 | 6 |
| BUG:kernel_NULL_pointer_dereference,address | 0 | 6 |
| Oops:#[##] | 0 | 6 |
| RIP:btrfs_submit_direct[btrfs] | 0 | 6 |
| Kernel_panic-not_syncing:Fatal_exception | 0 | 6 |
+---------------------------------------------+------------+------------+
If you fix the issue, kindly add following tag
Reported-by: kernel test robot <rong.a.chen(a)intel.com>
[ 33.005610] BUG: kernel NULL pointer dereference, address: 0000000000000010
[ 33.007896] #PF: supervisor write access in kernel mode
[ 33.009646] #PF: error_code(0x0002) - not-present page
[ 33.011375] PGD 0 P4D 0
[ 33.012583] Oops: 0002 [#1] SMP PTI
[ 33.013979] CPU: 1 PID: 2466 Comm: aiodio_sparse Not tainted 5.3.0-rc5-00012-g96a85793d686c #1
[ 33.016378] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1 04/01/2014
[ 33.018803] RIP: 0010:btrfs_submit_direct+0x24e/0x650 [btrfs]
[ 33.020654] Code: 5d 41 5c 41 5d 41 5e 41 5f c3 49 c7 46 40 60 2f 61 c0 65 48 8b 04 25 c0 6b 01 00 48 8b 90 b0 0b 00 00 48 8b 43 20 48 03 43 10 <48> 89 42 10 48 89 42 08 e9 66 fe ff ff 83 7c 24 40 01 41 8b 55 28
[ 33.025825] RSP: 0018:ffffb1694037f900 EFLAGS: 00010206
[ 33.027647] RAX: 0000000000010000 RBX: ffff89c600ecc360 RCX: 0000000000000000
[ 33.029809] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff89c600ecc3c0
[ 33.031975] RBP: 0000000000000001 R08: ffff89c67fd300c0 R09: ffff89c547c03500
[ 33.034129] R10: 0000000000002000 R11: ffff89c5d75b0000 R12: ffff89c5d7c621b0
[ 33.036265] R13: ffff89c5d8250c00 R14: ffff89c5dce17bb0 R15: 0000000000000000
[ 33.038413] FS: 00007fda242ca700(0000) GS:ffff89c67fd00000(0000) knlGS:0000000000000000
[ 33.040741] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 33.042648] CR2: 0000000000000010 CR3: 0000000198bf0000 CR4: 00000000000406e0
[ 33.044822] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 33.046986] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[ 33.049131] Call Trace:
[ 33.050436] ? bio_iov_iter_get_pages+0x1c4/0x290
[ 33.052145] iomap_dio_submit_bio+0x72/0x90
[ 33.054555] iomap_dio_bio_actor+0x1c4/0x3f0
[ 33.056169] ? iomap_dio_bio_actor+0x3f0/0x3f0
[ 33.057814] iomap_apply+0xd4/0x170
[ 33.059304] iomap_dio_rw+0x2cf/0x410
[ 33.060798] ? iomap_dio_bio_actor+0x3f0/0x3f0
[ 33.062456] ? __x64_sys_io_cancel+0x180/0x180
[ 33.064129] ? cap_inode_need_killpriv+0x1a/0x30
[ 33.065813] ? security_inode_need_killpriv+0x22/0x40
[ 33.067614] ? btrfs_dio_iomap_write+0x2e/0x100 [btrfs]
[ 33.069429] btrfs_dio_iomap_write+0x2e/0x100 [btrfs]
[ 33.071207] ? current_time+0x47/0x80
[ 33.072725] btrfs_file_write_iter+0x2d8/0x490 [btrfs]
[ 33.074500] aio_write+0x109/0x1a0
[ 33.075944] ? handle_mm_fault+0xdd/0x220
[ 33.077487] ? __do_page_fault+0x310/0x520
[ 33.079050] ? io_submit_one+0x5c0/0xbf0
[ 33.080545] ? __might_fault+0x2b/0x30
[ 33.081998] io_submit_one+0x5c0/0xbf0
[ 33.083440] ? async_page_fault+0x3e/0x50
[ 33.084909] ? __x64_sys_io_submit+0x9e/0x1c0
[ 33.086436] ? __might_fault+0x2b/0x30
[ 33.087837] __x64_sys_io_submit+0x9e/0x1c0
[ 33.089314] ? do_syscall_64+0x5b/0x1f0
[ 33.090740] ? __ia32_compat_sys_io_submit+0x1b0/0x1b0
[ 33.092391] do_syscall_64+0x5b/0x1f0
[ 33.093761] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 33.095406] RIP: 0033:0x7fda23c93717
[ 33.096749] Code: 00 75 08 8b 47 0c 39 47 08 74 08 e9 c3 ff ff ff 0f 1f 00 31 c0 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 b8 d1 00 00 00 0f 05 <c3> 0f 1f 84 00 00 00 00 00 b8 d2 00 00 00 0f 05 c3 0f 1f 84 00 00
[ 33.101690] RSP: 002b:00007ffe1ad07068 EFLAGS: 00000202 ORIG_RAX: 00000000000000d1
[ 33.103854] RAX: ffffffffffffffda RBX: 000055c4bd8190d0 RCX: 00007fda23c93717
[ 33.105904] RDX: 000055c4bd819050 RSI: 0000000000000010 RDI: 00007fda242d4000
[ 33.107958] RBP: 000055c4bd8190d0 R08: 0000000000000000 R09: 0000000000010201
[ 33.109969] R10: 000000000000000f R11: 0000000000000202 R12: 0000000000010000
[ 33.111963] R13: 000055c4bd90b400 R14: 00007fda242ca698 R15: 0000000000000010
[ 33.113942] Modules linked in: loop btrfs xor zstd_decompress zstd_compress raid6_pq libcrc32c dm_mod intel_rapl_msr intel_rapl_common crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sr_mod cdrom sg ata_generic pata_acpi bochs_drm drm_vram_helper ttm ppdev drm_kms_helper syscopyarea sysfillrect sysimgblt snd_pcm fb_sys_fops aesni_intel crypto_simd snd_timer drm snd cryptd glue_helper soundcore joydev pcspkr ata_piix serio_raw libata i2c_piix4 floppy parport_pc parport ip_tables
[ 33.124944] CR2: 0000000000000010
[ 33.126351] ---[ end trace 4102d180f6818476 ]---
To reproduce:
# build kernel
cd linux
cp config-5.3.0-rc5-00012-g96a85793d686c .config
make HOSTCC=gcc-7 CC=gcc-7 ARCH=x86_64 olddefconfig prepare modules_prepare bzImage modules
make HOSTCC=gcc-7 CC=gcc-7 ARCH=x86_64 INSTALL_MOD_PATH=<mod-install-dir> modules_install
cd <mod-install-dir>
find lib/ | cpio -o -H newc --quiet | gzip > modules.cgz
git clone https://github.com/intel/lkp-tests.git
cd lkp-tests
bin/lkp qemu -k <bzImage> -m modules.cgz job-script # job-script is attached in this email
Thanks,
Rong Chen
9 months
[KVM] e08571e819: WARNING:at_drivers/gpu/drm/drm_vblank.c:#drm_wait_one_vblank[drm]
by kernel test robot
FYI, we noticed the following commit (built with gcc-7):
commit: e08571e819dca343b575bf0dcd89a28637b43ba0 ("[PATCH] KVM: lapic: restart counter on change to periodic mode")
url: https://github.com/0day-ci/linux/commits/Matt-delco/KVM-lapic-restart-cou...
in testcase: kvm-unit-tests
with following parameters:
ucode: 0x27
on test machine: 8 threads Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz with 8G memory
caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
If you fix the issue, kindly add following tag
Reported-by: kernel test robot <rong.a.chen(a)intel.com>
2019-09-02 22:45:10 ./run_tests.sh
[31mFAIL[0m apic-split (53 tests, 2 unexpected failures)
[32mPASS[0m ioapic-split (19 tests)
[31mFAIL[0m apic (53 tests, 2 unexpected failures)
[32mPASS[0m ioapic (19 tests)
[32mPASS[0m smptest (1 tests)
[32mPASS[0m smptest3 (1 tests)
[32mPASS[0m vmexit_cpuid
[32mPASS[0m vmexit_vmcall
[32mPASS[0m vmexit_mov_from_cr8
[32mPASS[0m vmexit_mov_to_cr8
[32mPASS[0m vmexit_inl_pmtimer
[32mPASS[0m vmexit_ipi
[32mPASS[0m vmexit_ipi_halt
[32mPASS[0m vmexit_ple_round_robin
[32mPASS[0m vmexit_tscdeadline
[32mPASS[0m vmexit_tscdeadline_immed
[32mPASS[0m access
[33mSKIP[0m smap (0 tests)
[33mSKIP[0m pku (0 tests)
[32mPASS[0m asyncpf (1 tests)
[32mPASS[0m emulator (125 tests, 2 skipped)
[32mPASS[0m eventinj (13 tests)
[32mPASS[0m hypercall (2 tests)
[32mPASS[0m idt_test (4 tests)
[32mPASS[0m memory (8 tests)
[32mPASS[0m msr (12 tests)
[32mPASS[0m pmu (67 tests)
[31mFAIL[0m vmware_backdoors (11 tests, 5 unexpected failures)
[32mPASS[0m port80
[32mPASS[0m realmode
[32mPASS[0m s3
[32mPASS[0m sieve
[32mPASS[0m syscall (2 tests)
[32mPASS[0m tsc (3 tests)
[32mPASS[0m tsc_adjust (5 tests)
[32mPASS[0m xsave (17 tests)
[32mPASS[0m rmap_chain
[33mSKIP[0m svm (0 tests)
[33mSKIP[0m taskswitch (i386 only)
[33mSKIP[0m taskswitch2 (i386 only)
[32mPASS[0m kvmclock_test
[32mPASS[0m pcid (3 tests)
[32mPASS[0m umip (21 tests)
[32mPASS[0m vmx (7308 tests, 5 expected failures, 5 skipped)
[33mSKIP[0m ept (0 tests)
[33mSKIP[0m vmx_eoi_bitmap_ioapic_scan (1 tests, 1 skipped)
[33mSKIP[0m vmx_hlt_with_rvi_test (1 tests, 1 skipped)
[33mSKIP[0m vmx_apicv_test (2 tests, 2 skipped)
[32mPASS[0m vmx_apic_passthrough_thread (8 tests)
[32mPASS[0m vmx_vmcs_shadow_test (142218 tests)
[32mPASS[0m debug (11 tests)
[32mPASS[0m hyperv_synic (1 tests)
[33mSKIP[0m hyperv_connections (1 tests, 1 skipped)
[32mPASS[0m hyperv_stimer (12 tests)
[32mPASS[0m hyperv_clock
[32mPASS[0m intel_iommu (11 tests)
To reproduce:
git clone https://github.com/intel/lkp-tests.git
cd lkp-tests
bin/lkp install job.yaml # job file is attached in this email
bin/lkp run job.yaml
Thanks,
Rong Chen
9 months
[KVM] e08571e819: kvm-unit-tests.apic.fail
by kernel test robot
FYI, we noticed the following commit (built with gcc-7):
commit: e08571e819dca343b575bf0dcd89a28637b43ba0 ("[PATCH] KVM: lapic: restart counter on change to periodic mode")
url: https://github.com/0day-ci/linux/commits/Matt-delco/KVM-lapic-restart-cou...
in testcase: kvm-unit-tests
with following parameters:
ucode: 0x27
on test machine: 8 threads Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz with 8G memory
caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
If you fix the issue, kindly add following tag
Reported-by: kernel test robot <rong.a.chen(a)intel.com>
2019-09-02 22:45:10 ./run_tests.sh
[31mFAIL[0m apic-split (53 tests, 2 unexpected failures)
[32mPASS[0m ioapic-split (19 tests)
[31mFAIL[0m apic (53 tests, 2 unexpected failures)
[32mPASS[0m ioapic (19 tests)
[32mPASS[0m smptest (1 tests)
[32mPASS[0m smptest3 (1 tests)
[32mPASS[0m vmexit_cpuid
[32mPASS[0m vmexit_vmcall
[32mPASS[0m vmexit_mov_from_cr8
[32mPASS[0m vmexit_mov_to_cr8
[32mPASS[0m vmexit_inl_pmtimer
[32mPASS[0m vmexit_ipi
[32mPASS[0m vmexit_ipi_halt
[32mPASS[0m vmexit_ple_round_robin
[32mPASS[0m vmexit_tscdeadline
[32mPASS[0m vmexit_tscdeadline_immed
[32mPASS[0m access
[33mSKIP[0m smap (0 tests)
[33mSKIP[0m pku (0 tests)
[32mPASS[0m asyncpf (1 tests)
[32mPASS[0m emulator (125 tests, 2 skipped)
[32mPASS[0m eventinj (13 tests)
[32mPASS[0m hypercall (2 tests)
[32mPASS[0m idt_test (4 tests)
[32mPASS[0m memory (8 tests)
[32mPASS[0m msr (12 tests)
[32mPASS[0m pmu (67 tests)
[31mFAIL[0m vmware_backdoors (11 tests, 5 unexpected failures)
[32mPASS[0m port80
[32mPASS[0m realmode
[32mPASS[0m s3
[32mPASS[0m sieve
[32mPASS[0m syscall (2 tests)
[32mPASS[0m tsc (3 tests)
[32mPASS[0m tsc_adjust (5 tests)
[32mPASS[0m xsave (17 tests)
[32mPASS[0m rmap_chain
[33mSKIP[0m svm (0 tests)
[33mSKIP[0m taskswitch (i386 only)
[33mSKIP[0m taskswitch2 (i386 only)
[32mPASS[0m kvmclock_test
[32mPASS[0m pcid (3 tests)
[32mPASS[0m umip (21 tests)
[32mPASS[0m vmx (7308 tests, 5 expected failures, 5 skipped)
[33mSKIP[0m ept (0 tests)
[33mSKIP[0m vmx_eoi_bitmap_ioapic_scan (1 tests, 1 skipped)
[33mSKIP[0m vmx_hlt_with_rvi_test (1 tests, 1 skipped)
[33mSKIP[0m vmx_apicv_test (2 tests, 2 skipped)
[32mPASS[0m vmx_apic_passthrough_thread (8 tests)
[32mPASS[0m vmx_vmcs_shadow_test (142218 tests)
[32mPASS[0m debug (11 tests)
[32mPASS[0m hyperv_synic (1 tests)
[33mSKIP[0m hyperv_connections (1 tests, 1 skipped)
[32mPASS[0m hyperv_stimer (12 tests)
[32mPASS[0m hyperv_clock
[32mPASS[0m intel_iommu (11 tests)
To reproduce:
git clone https://github.com/intel/lkp-tests.git
cd lkp-tests
bin/lkp install job.yaml # job file is attached in this email
bin/lkp run job.yaml
Thanks,
Rong Chen
9 months
[btrfs] 77e52739c2: xfstests.generic.299.fail
by kernel test robot
FYI, we noticed the following commit (built with gcc-7):
commit: 77e52739c26212c5fcf0e2ed1b39c768c672ab50 ("btrfs: basic direct read operation")
https://github.com/goldwynr/linux btrfs-iomap
in testcase: xfstests
with following parameters:
disk: 4HDD
fs: btrfs
test: generic-299
test-description: xfstests is a regression test suite for xfs and other files ystems.
test-url: git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git
on test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 4G
caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
If you fix the issue, kindly add following tag
Reported-by: kernel test robot <rong.a.chen(a)intel.com>
2019-09-02 20:29:32 export TEST_DIR=/fs/vda
2019-09-02 20:29:32 export TEST_DEV=/dev/vda
2019-09-02 20:29:32 export FSTYP=btrfs
2019-09-02 20:29:32 export SCRATCH_MNT=/fs/scratch
2019-09-02 20:29:32 mkdir /fs/scratch -p
2019-09-02 20:29:32 export SCRATCH_DEV_POOL="/dev/vdb /dev/vdc /dev/vdd"
2019-09-02 20:29:32 echo generic/299
2019-09-02 20:29:32 ./check generic/299
FSTYP -- btrfs
PLATFORM -- Linux/x86_64 vm-snb-4G-6786b19c1799 5.3.0-rc5-00008-g77e52739c2621 #1 SMP Mon Sep 2 19:41:14 CST 2019
MKFS_OPTIONS -- /dev/vdb
MOUNT_OPTIONS -- /dev/vdb /fs/scratch
generic/299 [failed, exit status 1]- output mismatch (see /lkp/benchmarks/xfstests/results//generic/299.out.bad)
--- tests/generic/299.out 2019-09-02 18:49:26.000000000 +0800
+++ /lkp/benchmarks/xfstests/results//generic/299.out.bad 2019-09-02 20:29:44.484282090 +0800
@@ -3,3 +3,5 @@
Run fio with random aio-dio pattern
Start fallocate/truncate loop
+failed: '/usr/bin/fio /tmp/1262.fio'
+(see /lkp/benchmarks/xfstests/results//generic/299.full for details)
...
(Run 'diff -u /lkp/benchmarks/xfstests/tests/generic/299.out /lkp/benchmarks/xfstests/results//generic/299.out.bad' to see the entire diff)
Ran: generic/299
Failures: generic/299
Failed 1 of 1 tests
To reproduce:
# build kernel
cd linux
cp config-5.3.0-rc5-00008-g77e52739c2621 .config
make HOSTCC=gcc-7 CC=gcc-7 ARCH=x86_64 olddefconfig prepare modules_prepare bzImage modules
make HOSTCC=gcc-7 CC=gcc-7 ARCH=x86_64 INSTALL_MOD_PATH=<mod-install-dir> modules_install
cd <mod-install-dir>
find lib/ | cpio -o -H newc --quiet | gzip > modules.cgz
git clone https://github.com/intel/lkp-tests.git
cd lkp-tests
bin/lkp qemu -k <bzImage> -m modules.cgz job-script # job-script is attached in this email
Thanks,
Rong Chen
9 months
[btrfs] 3ae92b3782: xfstests.generic.269.fail
by kernel test robot
FYI, we noticed the following commit (built with gcc-7):
commit: 3ae92b3782182d282a92573abe95c96d34ca6e73 ("btrfs: change the minimum global reserve size")
https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next.git master
in testcase: xfstests
with following parameters:
disk: 4HDD
fs: btrfs
test: generic-group13
test-description: xfstests is a regression test suite for xfs and other files ystems.
test-url: git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git
on test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 4G
caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
If you fix the issue, kindly add following tag
Reported-by: kernel test robot <rong.a.chen(a)intel.com>
2019-08-31 20:14:07 export TEST_DIR=/fs/vda
2019-08-31 20:14:07 export TEST_DEV=/dev/vda
2019-08-31 20:14:07 export FSTYP=btrfs
2019-08-31 20:14:07 export SCRATCH_MNT=/fs/scratch
2019-08-31 20:14:07 mkdir /fs/scratch -p
2019-08-31 20:14:07 export SCRATCH_DEV_POOL="/dev/vdb /dev/vdc /dev/vdd"
2019-08-31 20:14:07 sed "s:^:generic/:" //lkp/benchmarks/xfstests/tests/generic-group13 | grep -F -f merged_ignored_files
2019-08-31 20:14:07 sed "s:^:generic/:" //lkp/benchmarks/xfstests/tests/generic-group13 | grep -v -F -f merged_ignored_files
2019-08-31 20:14:07 ./check generic/252 generic/253 generic/254 generic/255 generic/256 generic/257 generic/258 generic/260 generic/263 generic/264 generic/265 generic/266 generic/267 generic/268 generic/269 generic/270 generic/271
FSTYP -- btrfs
PLATFORM -- Linux/x86_64 vm-snb-4G-3c3aae657790 5.3.0-rc6-00130-g3ae92b3782182 #1 SMP Sat Aug 31 20:03:43 CST 2019
MKFS_OPTIONS -- /dev/vdb
MOUNT_OPTIONS -- /dev/vdb /fs/scratch
generic/252 3s
generic/253 1s
generic/254 1s
generic/255 1s
generic/256 98s
generic/257 1s
generic/258 0s
generic/260 [not run] FITRIM not supported on /fs/scratch
generic/263 33s
generic/264 [not run] xfs_io funshare failed (old kernel/wrong fs?)
generic/265 2s
generic/266 2s
generic/267 3s
generic/268 1s
generic/269 _check_btrfs_filesystem: filesystem on /dev/vdb is inconsistent
(see /lkp/benchmarks/xfstests/results//generic/269.full for details)
generic/270 [not run] disk quotas not supported by this filesystem type: btrfs
generic/271 1s
Ran: generic/252 generic/253 generic/254 generic/255 generic/256 generic/257 generic/258 generic/260 generic/263 generic/264 generic/265 generic/266 generic/267 generic/268 generic/269 generic/270 generic/271
Not run: generic/260 generic/264 generic/270
Failures: generic/269
Failed 1 of 17 tests
To reproduce:
# build kernel
cd linux
cp config-5.3.0-rc6-00130-g3ae92b3782182 .config
make HOSTCC=gcc-7 CC=gcc-7 ARCH=x86_64 olddefconfig prepare modules_prepare bzImage modules
make HOSTCC=gcc-7 CC=gcc-7 ARCH=x86_64 INSTALL_MOD_PATH=<mod-install-dir> modules_install
cd <mod-install-dir>
find lib/ | cpio -o -H newc --quiet | gzip > modules.cgz
git clone https://github.com/intel/lkp-tests.git
cd lkp-tests
bin/lkp qemu -k <bzImage> -m modules.cgz job-script # job-script is attached in this email
Thanks,
Rong Chen
9 months
Some questions on 0-day
by Dmitry Vyukov
Hello 0-day devs,
[Hope I figures correct email addresses]
I have some questions regarding state of 0-day project to better
understand state of upstream kernel testing.
1. What kernel configs does 0-day bot use? In particular I am
interested in various runtime debugging features. Is there a list of
all configs? I've found one in a recent "[bpf] 9fe4f05d33:
kernel_selftests.bpf.test_verifier.fail" report, but it does not
include CONFIG_KASAN, though I am sure 0-day uses KASAN. So is it a
different config? Or the config was "minimized" to exclude KASAN since
it was not relevant for the failure? I am interested in the following
debug features: KASAN, LOCKDEP, KMEMLEAK, FAULT_INJECTION,
DEBUG_OBJECTS, DEBUG_VM. Are these used? Any other notable debug
features that are used?
2. What tests are being run? Is there a list somewhere?
I know that 0-day now runs a pretty extensive set of tests. But is
there any quantitative qualification? Are you done with onboarding
more test suites? Or
you want to onboard more? How would you estimate your progress on test
onboarding? Is it 10%, 50% or 90%?
3. On a related note, do you know test code coverage? Are there
reports available?
4. As far as I understand there is no automated reporting and a human
is involved in sending of each report. Is it correct? What is the
reason? You want to double-check? It's not automated? Something else?
5. Do you intercept all incoming upstream patches or you know that
some are missing? If you don't intercept all, what are the main
sources? I know some people send pull requests to Linus from their
github trees and these may skip most of the common process.
6. Does it happen that 0-day fails to parse/apply a patch? I mean things
like parsing problems when 0-day just can't make sense out of the email
text, or when you can't figure out base tree/branch.
7. As far as I understand 0-day has some heuristics to figure out base
git repo/branch. How frequently do they fail? How much tuning and
maintenance does this require?
8. What are your major pain points? Or where time is going to? Major TODO items?
9. How many people are working on 0-day? Or taking into account the
project started long time ago, more relevant question is probably:
what is the estimation of engineer-years spent on 0-day? Are there any
major areas where the human time goes?
Thanks in advance
9 months