[net] 6fd0d0dede: hwsim.ap_ht40_5ghz_switch.fail
by kernel test robot
Greeting,
FYI, we noticed the following commit (built with gcc-9):
commit: 6fd0d0deded94645d8cb96f93c26ad55cd92f6a5 ("[PATCH net-next] net: sch_generic: aviod concurrent reset and enqueue op for lockless qdisc")
url: https://github.com/0day-ci/linux/commits/Yunsheng-Lin/net-sch_generic-avi...
base: https://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git 10eb4667946068e34f0cde1485f030aa68c89275
in testcase: hwsim
version: hwsim-x86_64-6eb6cf0-1_20200619
with following parameters:
group: hwsim-03
ucode: 0x21
on test machine: 8 threads Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz with 16G 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>
2020-09-05 21:47:27 ./run-tests.py ap_ht40_5ghz_switch
DEV: wlan0: 02:00:00:00:00:00
DEV: wlan1: 02:00:00:00:01:00
DEV: wlan2: 02:00:00:00:02:00
APDEV: wlan3
APDEV: wlan4
START ap_ht40_5ghz_switch 1/1
Test: HT40 co-ex scan on 5 GHz switching pri/sec channel
Starting AP wlan4
Starting AP wlan3
Connect STA wlan0 to AP
wlan0: Country code not reset back to 00: is US
wlan0: Country code cleared back to 00
FAIL ap_ht40_5ghz_switch 3.614883 2020-09-05 21:47:31.016291
passed 0 test case(s)
skipped 0 test case(s)
failed tests: ap_ht40_5ghz_switch
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
5 months, 3 weeks
[mac80211_hwsim] 8cafe19852: hwsim.fst_ap_config_default.fail
by kernel test robot
Greeting,
FYI, we noticed the following commit (built with gcc-9):
commit: 8cafe19852d95d6494cbd8c1ae24dbd621588a91 ("[PATCH v2 21/22] mac80211_hwsim: indicate support for S1G")
url: https://github.com/0day-ci/linux/commits/Thomas-Pedersen/add-support-for-...
base: https://git.kernel.org/cgit/linux/kernel/git/jberg/mac80211-next.git master
in testcase: hwsim
version: hwsim-x86_64-6eb6cf0-1_20200619
with following parameters:
group: hwsim-19
ucode: 0x21
on test machine: 8 threads Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz with 16G 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>
2020-09-05 17:49:30 ./run-tests.py fst_ap_config_default
DEV: wlan0: 02:00:00:00:00:00
DEV: wlan1: 02:00:00:00:01:00
DEV: wlan2: 02:00:00:00:02:00
APDEV: wlan3
APDEV: wlan4
START fst_ap_config_default 1/1
Test: FST AP configuration default parameters
kill_pid: pidfile logs/current/myhostapd.pid does not exist - try again after a second
kill_pid: pidfile logs/current/myhostapd.pid does not exist - could not kill the process
hostapd didn't start with valid config parameters
Traceback (most recent call last):
File "./run-tests.py", line 531, in main
t(dev, apdev, params)
File "/lkp/benchmarks/hwsim/tests/hwsim/test_fst_config.py", line 406, in test_fst_ap_config_default
raise Exception("hostapd didn't start with valid config parameters")
Exception: hostapd didn't start with valid config parameters
FAIL fst_ap_config_default 1.201026 2020-09-05 17:49:31.626224
passed 0 test case(s)
skipped 0 test case(s)
failed tests: fst_ap_config_default
2020-09-05 17:49:31 ./run-tests.py fst_ap_config_good
DEV: wlan0: 02:00:00:00:00:00
DEV: wlan1: 02:00:00:00:01:00
DEV: wlan2: 02:00:00:00:02:00
APDEV: wlan3
APDEV: wlan4
START fst_ap_config_good 1/1
Test: FST AP configuration good parameters
kill_pid: pidfile logs/current/myhostapd.pid does not exist - try again after a second
kill_pid: pidfile logs/current/myhostapd.pid does not exist - could not kill the process
hostapd didn't start with valid config parameters
Traceback (most recent call last):
File "./run-tests.py", line 531, in main
t(dev, apdev, params)
File "/lkp/benchmarks/hwsim/tests/hwsim/test_fst_config.py", line 400, in test_fst_ap_config_good
raise Exception("hostapd didn't start with valid config parameters")
Exception: hostapd didn't start with valid config parameters
FAIL fst_ap_config_good 1.214574 2020-09-05 17:49:32.968016
passed 0 test case(s)
skipped 0 test case(s)
failed tests: fst_ap_config_good
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
5 months, 3 weeks
[PATCH] syscall/ptrace08: Simplify the test.
by Cyril Hrubis
The original test was attempting to crash the kernel by setting a
breakpoint on do_debug kernel function which, when triggered, caused an
infinite loop in the kernel. The problem with this approach is that
kernel internal function names are not stable at all and the name was
changed recently, which made the test fail for no good reason.
So this patch changes the test to read the breakpoint address back
instead, which also means that we can drop the /proc/kallsyms parsing as
well.
Signed-off-by: Cyril Hrubis <chrubis(a)suse.cz>
CC: Andy Lutomirski <luto(a)kernel.org>
CC: Peter Zijlstra <peterz(a)infradead.org>
CC: Thomas Gleixner <tglx(a)linutronix.de>
CC: Alexandre Chartre <alexandre.chartre(a)oracle.com>
---
testcases/kernel/syscalls/ptrace/ptrace08.c | 120 ++++++++++----------
1 file changed, 60 insertions(+), 60 deletions(-)
diff --git a/testcases/kernel/syscalls/ptrace/ptrace08.c b/testcases/kernel/syscalls/ptrace/ptrace08.c
index 591aa0dd2..5587f0bbb 100644
--- a/testcases/kernel/syscalls/ptrace/ptrace08.c
+++ b/testcases/kernel/syscalls/ptrace/ptrace08.c
@@ -5,8 +5,17 @@
*
* CVE-2018-1000199
*
- * Test error handling when ptrace(POKEUSER) modifies debug registers.
- * Even if the call returns error, it may create breakpoint in kernel code.
+ * Test error handling when ptrace(POKEUSER) modified x86 debug registers even
+ * when the call returned error.
+ *
+ * When the bug was present we could create breakpoint in the kernel code,
+ * which shoudn't be possible at all. The original CVE caused a kernel crash by
+ * setting a breakpoint on do_debug kernel function which, when triggered,
+ * caused an infinite loop. However we do not have to crash the kernel in order
+ * to assert if kernel has been fixed or not. All we have to do is to try to
+ * set a breakpoint, on any kernel address, then read it back and check if the
+ * value has been set or not.
+ *
* Kernel crash partially fixed in:
*
* commit f67b15037a7a50c57f72e69a6d59941ad90a0f0f
@@ -26,69 +35,42 @@
#include "tst_safe_stdio.h"
#if defined(__i386__) || defined(__x86_64__)
-#define SYMNAME_SIZE 256
-#define KERNEL_SYM "do_debug"
-static unsigned long break_addr;
static pid_t child_pid;
-static void setup(void)
-{
- int fcount;
- char endl, symname[256];
- FILE *fr = SAFE_FOPEN("/proc/kallsyms", "r");
-
- /* Find address of do_debug() in /proc/kallsyms */
- do {
- fcount = fscanf(fr, "%lx %*c %255s%c", &break_addr, symname,
- &endl);
-
- if (fcount <= 0 && feof(fr))
- break;
-
- if (fcount < 2) {
- fclose(fr);
- tst_brk(TBROK, "Unexpected data in /proc/kallsyms %d",
- fcount);
- }
-
- if (fcount >= 3 && endl != '\n')
- while (!feof(fr) && fgetc(fr) != '\n');
- } while (!feof(fr) && strcmp(symname, KERNEL_SYM));
-
- SAFE_FCLOSE(fr);
-
- if (strcmp(symname, KERNEL_SYM))
- tst_brk(TBROK, "Cannot find address of kernel symbol \"%s\"",
- KERNEL_SYM);
-
- if (!break_addr)
- tst_brk(TCONF, "Addresses in /proc/kallsyms are hidden");
-
- tst_res(TINFO, "Kernel symbol \"%s\" found at 0x%lx", KERNEL_SYM,
- break_addr);
-}
+#if defined(__x86_64__)
+# define KERN_ADDR_MIN 0xffff800000000000
+# define KERN_ADDR_MAX 0xffffffffffffffff
+# define KERN_ADDR_BITS 64
+#elif defined(__i386__)
+# define KERN_ADDR_MIN 0xc0000000
+# define KERN_ADDR_MAX 0xffffffff
+# define KERN_ADDR_BITS 32
+#endif
-static void debug_trap(void)
+static void setup(void)
{
- /* x86 instruction INT1 */
- asm volatile (".byte 0xf1");
+ /*
+ * When running in compat mode we can't pass 64 address to ptrace so we
+ * have to skip the test.
+ */
+ if (tst_kernel_bits() != KERN_ADDR_BITS)
+ tst_brk(TCONF, "Cannot pass 64bit kernel address in compat mode");
}
static void child_main(void)
{
raise(SIGSTOP);
- /* wait for SIGCONT from parent */
- debug_trap();
exit(0);
}
-static void run(void)
+static void ptrace_try_kern_addr(unsigned long kern_addr)
{
int status;
- pid_t child;
- child = child_pid = SAFE_FORK();
+ tst_res(TINFO, "Trying address 0x%lx", kern_addr);
+
+ child_pid = SAFE_FORK();
if (!child_pid)
child_main();
@@ -103,22 +85,41 @@ static void run(void)
(void *)offsetof(struct user, u_debugreg[7]), (void *)1);
/* Return value intentionally ignored here */
- ptrace(PTRACE_POKEUSER, child_pid,
+ TEST(ptrace(PTRACE_POKEUSER, child_pid,
(void *)offsetof(struct user, u_debugreg[0]),
- (void *)break_addr);
+ (void *)kern_addr));
+
+ if (TST_RET != -1) {
+ tst_res(TFAIL, "ptrace() breakpoint with kernel addr succeeded");
+ } else {
+ if (TST_ERR == EINVAL) {
+ tst_res(TPASS | TTERRNO,
+ "ptrace() breakpoint with kernel addr failed");
+ } else {
+ tst_res(TFAIL | TTERRNO,
+ "ptrace() breakpoint on kernel addr should return EINVAL, got");
+ }
+ }
+
+ unsigned long addr;
+
+ addr = ptrace(PTRACE_PEEKUSER, child_pid,
+ (void*)offsetof(struct user, u_debugreg[0]), NULL);
+
+ if (addr == kern_addr)
+ tst_res(TFAIL, "Was able to set breakpoint on kernel addr");
SAFE_PTRACE(PTRACE_DETACH, child_pid, NULL, NULL);
SAFE_KILL(child_pid, SIGCONT);
child_pid = 0;
+ tst_reap_children();
+}
- if (SAFE_WAITPID(child, &status, 0) != child)
- tst_brk(TBROK, "Received event from unexpected PID");
-
- if (!WIFSIGNALED(status))
- tst_brk(TBROK, "Received unexpected event from child");
-
- tst_res(TPASS, "Child killed by %s", tst_strsig(WTERMSIG(status)));
- tst_res(TPASS, "We're still here. Nothing bad happened, probably.");
+static void run(void)
+{
+ ptrace_try_kern_addr(KERN_ADDR_MIN);
+ ptrace_try_kern_addr(KERN_ADDR_MAX);
+ ptrace_try_kern_addr(KERN_ADDR_MIN + (KERN_ADDR_MAX - KERN_ADDR_MIN)/2);
}
static void cleanup(void)
@@ -133,7 +134,6 @@ static struct tst_test test = {
.setup = setup,
.cleanup = cleanup,
.forks_child = 1,
- .taint_check = TST_TAINT_W | TST_TAINT_D,
.tags = (const struct tst_tag[]) {
{"linux-git", "f67b15037a7a"},
{"CVE", "2018-1000199"},
--
2.26.2
5 months, 4 weeks
[btrfs] c0aaf9b7a1: ltp: stuck at diotest4
by kernel test robot
Greeting,
FYI, we noticed the following commit (built with gcc-9):
commit: c0aaf9b7a114f6b75e0da97be7d99c102347a751 ("btrfs: switch to iomap_dio_rw() for dio")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
in testcase: ltp
with following parameters:
disk: 1HDD
fs: btrfs
test: dio-00
ucode: 0x21
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: 8 threads Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz with 16G 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 <oliver.sang(a)intel.com>
in attached kmsg.xz for c0aaf9b7a1
user :notice: [ 74.917829] diotest03 0 TINFO : 3 testblocks 100 iterations with 1 children completed
user :notice: [ 74.919689] <<<execution_status>>>
user :notice: [ 74.921486] initiation_status="ok"
user :notice: [ 74.924044] duration=3 termination_type=exited termination_id=0 corefile=no
user :notice: [ 74.925798] cutime=1 cstime=4
user :notice: [ 74.927515] <<<test_end>>>
user :notice: [ 74.929115] <<<test_start>>>
user :notice: [ 74.930985] tag=dio04 stime=1598784407
user :notice: [ 74.932697] cmdline="diotest4" <----- start to stuck after diotest4 starting
user :notice: [ 74.934268] contacts=""
user :notice: [ 74.935860] analysis=exit
user :notice: [ 74.937556] <<<test_output>>>
user :notice: [ 90.977611] IPMI BMC is not supported on this machine, skip bmc-watchdog setup!
user :notice: [ 3690.978134] Sun Aug 30 11:47:43 UTC 2020 detected soft_timeout <----- until soft_timeout (1h) detected by robot
below is from attached parent kmsg-b77407c36a.xz
user :notice: [ 74.876938] diotest03 0 TINFO : 3 testblocks 100 iterations with 1 children completed
user :notice: [ 74.878759] <<<execution_status>>>
user :notice: [ 74.880533] initiation_status="ok"
user :notice: [ 74.883052] duration=3 termination_type=exited termination_id=0 corefile=no
user :notice: [ 74.884734] cutime=1 cstime=2
user :notice: [ 74.886381] <<<test_end>>>
user :notice: [ 74.887971] <<<test_start>>>
user :notice: [ 74.889798] tag=dio04 stime=1598804724
user :notice: [ 74.891494] cmdline="diotest4"
user :notice: [ 74.893005] contacts=""
user :notice: [ 74.894584] analysis=exit
user :notice: [ 74.896235] <<<test_output>>>
user :notice: [ 74.898323] diotest4 1 TPASS : Negative Offset <----- diotest4 start to run ...
user :notice: [ 74.900214] diotest4 2 TPASS : removed
...
user :notice: [ 74.941552] diotest4 0 TINFO : 15 testblocks completed <----- ... and finish quickly
user :notice: [ 74.943551] <<<execution_status>>>
user :notice: [ 74.945461] initiation_status="ok"
user :notice: [ 74.948140] duration=0 termination_type=exited termination_id=0 corefile=no
user :notice: [ 74.950018] cutime=0 cstime=0
user :notice: [ 74.951775] <<<test_end>>>
user :notice: [ 74.953532] <<<test_start>>>
user :notice: [ 74.955426] tag=dio05 stime=1598804724
user :notice: [ 74.957168] cmdline="diotest5"
...
user :notice: [ 388.377363] INFO: ltp-pan reported all tests PASS <----- all ltp test finish within 388s
user :notice: [ 388.378190] LTP Version: 20200515-110-gd2768c84e
user :notice: [ 388.379916] ###############################################################
user :notice: [ 388.380922] Done executing testcases.
user :notice: [ 388.382040] LTP Version: 20200515-110-gd2768c84e
user :notice: [ 388.383625] ###############################################################
except kernel, there is no test env changes between parent and c0aaf9b7a1.
the kconfig used for parent and c0aaf9b7a1 is identical as attached.
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,
Oliver Sang
5 months, 4 weeks
[kmap] ca4e92cbbd: BUG:sleeping_function_called_from_invalid_context_at_mm/page_alloc.c
by kernel test robot
Greeting,
FYI, we noticed the following commit (built with gcc-9):
commit: ca4e92cbbd71828aaf5d096330b3b154950c7740 ("kmap: Add stray access protection for device pages")
https://github.com/weiny2/linux-kernel.git lm-pks-pmem-for-5.10-v1
in testcase: suspend-stress
with following parameters:
mode: mem
iterations: 10
on test machine: 4 threads Broadwell 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 <lkp(a)intel.com>
kern :err : [ 211.228336] BUG: sleeping function called from invalid context at mm/page_alloc.c:4822
kern :err : [ 211.228441] in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 203, name: systemd-udevd
kern :warn : [ 211.228549] CPU: 2 PID: 203 Comm: systemd-udevd Not tainted 5.9.0-rc2-00061-gca4e92cbbd718 #1
kern :warn : [ 211.228658] Hardware name: /NUC5i3RYB, BIOS RYBDWi35.86A.0363.2017.0316.1028 03/16/2017
kern :warn : [ 211.228760] Call Trace:
kern :warn : [ 211.228800] dump_stack+0x57/0x80
kern :warn : [ 211.228848] ___might_sleep.cold+0x87/0x95
kern :warn : [ 211.228905] __alloc_pages_nodemask+0x22d/0x360
kern :warn : [ 211.229025] vm_alloc_page+0x14a/0x220 [i915]
kern :warn : [ 211.229100] ? __alloc_pages_nodemask+0x18c/0x360
kern :warn : [ 211.229224] setup_page_dma+0x12/0x80 [i915]
kern :warn : [ 211.229335] gen8_ppgtt_create+0x16b/0x400 [i915]
kern :warn : [ 211.229473] i915_ppgtt_create+0x85/0xa0 [i915]
kern :warn : [ 211.229582] intel_gt_init+0x12d/0x5e0 [i915]
kern :warn : [ 211.229686] ? fw_domains_get+0xe9/0x1a0 [i915]
kern :warn : [ 211.229749] ? sched_clock+0x5/0x20
kern :warn : [ 211.229842] ? gen6_read32+0xa0/0x200 [i915]
kern :warn : [ 211.229944] ? gen6_read32+0xa0/0x200 [i915]
kern :warn : [ 211.230057] i915_gem_init+0x131/0x1c0 [i915]
kern :warn : [ 211.230161] i915_driver_probe+0x289/0x500 [i915]
kern :warn : [ 211.230231] ? _cond_resched+0x19/0x40
kern :warn : [ 211.230283] ? mutex_lock+0x21/0x40
kern :warn : [ 211.230371] i915_pci_probe+0x54/0x140 [i915]
kern :warn : [ 211.230433] local_pci_probe+0x42/0x80
kern :warn : [ 211.230486] ? _cond_resched+0x19/0x40
kern :warn : [ 211.230538] pci_device_probe+0x107/0x1c0
kern :warn : [ 211.230596] really_probe+0x1ca/0x420
kern :warn : [ 211.230647] driver_probe_device+0x61/0x160
kern :warn : [ 211.230706] device_driver_attach+0x53/0x60
kern :warn : [ 211.230768] __driver_attach+0x8a/0x160
kern :warn : [ 211.230823] ? device_driver_attach+0x60/0x60
kern :warn : [ 211.230882] ? device_driver_attach+0x60/0x60
kern :warn : [ 211.230939] bus_for_each_dev+0x78/0xc0
kern :warn : [ 211.230990] bus_add_driver+0x14d/0x200
kern :warn : [ 211.231041] driver_register+0x6c/0xc0
kern :warn : [ 211.231092] ? 0xffffffffc043c000
kern :warn : [ 211.231185] i915_init+0x5d/0x70 [i915]
kern :warn : [ 211.231241] do_one_initcall+0x46/0x204
kern :warn : [ 211.231295] ? _cond_resched+0x19/0x40
kern :warn : [ 211.231348] ? kmem_cache_alloc_trace+0x3fe/0x480
kern :warn : [ 211.231412] ? do_init_module+0x23/0x220
kern :warn : [ 211.231466] do_init_module+0x5c/0x220
kern :warn : [ 211.231516] load_module+0x10c3/0x1240
kern :warn : [ 211.231568] ? new_sync_read+0x114/0x1a0
kern :warn : [ 211.231623] ? ima_post_read_file+0xf0/0x100
kern :warn : [ 211.231683] ? __do_sys_finit_module+0xaa/0x120
kern :warn : [ 211.231744] __do_sys_finit_module+0xaa/0x120
kern :warn : [ 211.231805] do_syscall_64+0x33/0x40
kern :warn : [ 211.231856] entry_SYSCALL_64_after_hwframe+0x44/0xa9
kern :warn : [ 211.231925] RIP: 0033:0x7f022682d229
kern :warn : [ 211.231976] Code: 00 f3 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 3f 4c 2b 00 f7 d8 64 89 01 48
kern :warn : [ 211.232215] RSP: 002b:00007ffc33248468 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
kern :warn : [ 211.232316] RAX: ffffffffffffffda RBX: 00005592502b9d60 RCX: 00007f022682d229
kern :warn : [ 211.232408] RDX: 0000000000000000 RSI: 00007f0227146265 RDI: 0000000000000014
kern :warn : [ 211.232499] RBP: 00007f0227146265 R08: 0000000000000000 R09: 00007ffc332489e0
kern :warn : [ 211.232590] R10: 0000000000000014 R11: 0000000000000246 R12: 0000000000000000
kern :warn : [ 211.232682] R13: 00005592502b2700 R14: 0000000000020000 R15: 000055924eb37cbc
kern :err : [ 211.233371] BUG: scheduling while atomic: systemd-udevd/203/0x00000005
kern :warn : [ 211.233462] Modules linked in: sd_mod x86_pkg_temp_thermal t10_pi intel_powerclamp sg coretemp i915(+) kvm_intel kvm intel_gtt drm_kms_helper irqbypass crct10dif_pclmul syscopyarea crc32_pclmul crc32c_intel sysfillrect ghash_clmulni_intel sysimgblt rapl intel_cstate fb_sys_fops ahci intel_uncore libahci joydev drm mei_me libata ir_rc6_decoder mei rc_rc6_mce nuvoton_cir rc_core video intel_pmc_core acpi_pad ip_tables
kern :warn : [ 211.233965] CPU: 2 PID: 203 Comm: systemd-udevd Tainted: G W 5.9.0-rc2-00061-gca4e92cbbd718 #1
kern :warn : [ 211.234099] Hardware name: /NUC5i3RYB, BIOS RYBDWi35.86A.0363.2017.0316.1028 03/16/2017
kern :warn : [ 211.234210] Call Trace:
kern :warn : [ 211.234255] dump_stack+0x57/0x80
kern :warn : [ 211.234308] __schedule_bug.cold+0x47/0x54
kern :warn : [ 211.234370] __schedule+0x702/0x860
kern :warn : [ 211.234424] ? common_interrupt+0x9b/0x180
kern :warn : [ 211.234485] ? wait_for_completion+0x86/0x120
kern :warn : [ 211.234548] schedule+0x6e/0x100
kern :warn : [ 211.234598] schedule_timeout+0x268/0x300
kern :warn : [ 211.234658] ? wait_for_completion+0x86/0x120
kern :warn : [ 211.234721] wait_for_completion+0xba/0x120
kern :warn : [ 211.234784] __flush_work+0x146/0x200
kern :warn : [ 211.234841] ? worker_attach_to_pool+0xa0/0xa0
kern :warn : [ 211.235005] flush_submission+0x39/0x80 [i915]
kern :warn : [ 211.235151] intel_gt_retire_requests_timeout+0x63/0x420 [i915]
kern :warn : [ 211.235301] ? __i915_sw_fence_complete+0x13d/0x1e0 [i915]
kern :warn : [ 211.235446] intel_gt_wait_for_idle+0x2f/0x80 [i915]
kern :warn : [ 211.235585] intel_gt_init+0x268/0x5e0 [i915]
kern :warn : [ 211.235724] i915_gem_init+0x131/0x1c0 [i915]
kern :warn : [ 211.235851] i915_driver_probe+0x289/0x500 [i915]
kern :warn : [ 211.235924] ? _cond_resched+0x19/0x40
kern :warn : [ 211.235982] ? mutex_lock+0x21/0x40
kern :warn : [ 211.236100] i915_pci_probe+0x54/0x140 [i915]
kern :warn : [ 211.236170] local_pci_probe+0x42/0x80
kern :warn : [ 211.236227] ? _cond_resched+0x19/0x40
kern :warn : [ 211.236284] pci_device_probe+0x107/0x1c0
kern :warn : [ 211.236345] really_probe+0x1ca/0x420
kern :warn : [ 211.236401] driver_probe_device+0x61/0x160
kern :warn : [ 211.236463] device_driver_attach+0x53/0x60
kern :warn : [ 211.236524] __driver_attach+0x8a/0x160
kern :warn : [ 211.236581] ? device_driver_attach+0x60/0x60
kern :warn : [ 211.236644] ? device_driver_attach+0x60/0x60
kern :warn : [ 211.236706] bus_for_each_dev+0x78/0xc0
kern :warn : [ 211.236763] bus_add_driver+0x14d/0x200
kern :warn : [ 211.236820] driver_register+0x6c/0xc0
kern :warn : [ 211.236875] ? 0xffffffffc043c000
kern :warn : [ 211.236992] i915_init+0x5d/0x70 [i915]
kern :warn : [ 211.237053] do_one_initcall+0x46/0x204
kern :warn : [ 211.237113] ? _cond_resched+0x19/0x40
kern :warn : [ 211.237173] ? kmem_cache_alloc_trace+0x3fe/0x480
kern :warn : [ 211.237242] ? do_init_module+0x23/0x220
kern :warn : [ 211.237301] do_init_module+0x5c/0x220
kern :warn : [ 211.237358] load_module+0x10c3/0x1240
kern :warn : [ 211.237414] ? new_sync_read+0x114/0x1a0
kern :warn : [ 211.237474] ? ima_post_read_file+0xf0/0x100
kern :warn : [ 211.237538] ? __do_sys_finit_module+0xaa/0x120
kern :warn : [ 211.237604] __do_sys_finit_module+0xaa/0x120
kern :warn : [ 211.237671] do_syscall_64+0x33/0x40
kern :warn : [ 211.237725] entry_SYSCALL_64_after_hwframe+0x44/0xa9
kern :warn : [ 211.237799] RIP: 0033:0x7f022682d229
kern :warn : [ 211.237854] Code: 00 f3 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 3f 4c 2b 00 f7 d8 64 89 01 48
kern :warn : [ 211.238105] RSP: 002b:00007ffc33248468 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
kern :warn : [ 211.238211] RAX: ffffffffffffffda RBX: 00005592502b9d60 RCX: 00007f022682d229
kern :warn : [ 211.238309] RDX: 0000000000000000 RSI: 00007f0227146265 RDI: 0000000000000014
kern :warn : [ 211.238407] RBP: 00007f0227146265 R08: 0000000000000000 R09: 00007ffc332489e0
kern :warn : [ 211.238505] R10: 0000000000000014 R11: 0000000000000246 R12: 0000000000000000
kern :warn : [ 211.238602] R13: 00005592502b2700 R14: 0000000000020000 R15: 000055924eb37cbc
kern :err : [ 211.239194] BUG: scheduling while atomic: systemd-udevd/203/0x00000002
kern :warn : [ 211.239288] Modules linked in: sd_mod x86_pkg_temp_thermal t10_pi intel_powerclamp sg coretemp i915(+) kvm_intel kvm intel_gtt drm_kms_helper irqbypass crct10dif_pclmul syscopyarea crc32_pclmul crc32c_intel sysfillrect ghash_clmulni_intel sysimgblt rapl intel_cstate fb_sys_fops ahci intel_uncore libahci joydev drm mei_me libata ir_rc6_decoder mei rc_rc6_mce nuvoton_cir rc_core video intel_pmc_core acpi_pad ip_tables
kern :warn : [ 211.239800] CPU: 3 PID: 203 Comm: systemd-udevd Tainted: G W 5.9.0-rc2-00061-gca4e92cbbd718 #1
kern :warn : [ 211.239935] Hardware name: /NUC5i3RYB, BIOS RYBDWi35.86A.0363.2017.0316.1028 03/16/2017
kern :warn : [ 211.240047] Call Trace:
kern :warn : [ 211.240095] dump_stack+0x57/0x80
kern :warn : [ 211.240149] __schedule_bug.cold+0x47/0x54
kern :warn : [ 211.240213] __schedule+0x702/0x860
kern :warn : [ 211.240267] ? wait_for_completion+0x86/0x120
kern :warn : [ 211.240332] schedule+0x6e/0x100
kern :warn : [ 211.240381] schedule_timeout+0x268/0x300
kern :warn : [ 211.240441] ? check_preempt_curr+0x54/0x60
kern :warn : [ 211.240503] ? ttwu_do_wakeup+0x1e/0x180
kern :warn : [ 211.240563] ? wait_for_completion+0x86/0x120
kern :warn : [ 211.240627] wait_for_completion+0xba/0x120
kern :warn : [ 211.240692] cpuhp_issue_call+0x8f/0x100
kern :warn : [ 211.240752] __cpuhp_state_add_instance_cpuslocked+0x8f/0x100
kern :warn : [ 211.240836] __cpuhp_state_add_instance+0x59/0xc0
kern :warn : [ 211.241006] i915_pmu_register+0x57b/0x6e0 [i915]
kern :warn : [ 211.241146] i915_driver_probe+0x2eb/0x500 [i915]
kern :warn : [ 211.241218] ? _cond_resched+0x19/0x40
kern :warn : [ 211.241275] ? mutex_lock+0x21/0x40
kern :warn : [ 211.241388] i915_pci_probe+0x54/0x140 [i915]
kern :warn : [ 211.241455] local_pci_probe+0x42/0x80
kern :warn : [ 211.241512] ? _cond_resched+0x19/0x40
kern :warn : [ 211.241569] pci_device_probe+0x107/0x1c0
kern :warn : [ 211.241631] really_probe+0x1ca/0x420
kern :warn : [ 211.241687] driver_probe_device+0x61/0x160
kern :warn : [ 211.241750] device_driver_attach+0x53/0x60
kern :warn : [ 211.241812] __driver_attach+0x8a/0x160
kern :warn : [ 211.241869] ? device_driver_attach+0x60/0x60
kern :warn : [ 211.241933] ? device_driver_attach+0x60/0x60
kern :warn : [ 211.241998] bus_for_each_dev+0x78/0xc0
kern :warn : [ 211.242056] bus_add_driver+0x14d/0x200
kern :warn : [ 211.242113] driver_register+0x6c/0xc0
kern :warn : [ 211.242171] ? 0xffffffffc043c000
kern :warn : [ 211.242289] i915_init+0x5d/0x70 [i915]
kern :warn : [ 211.242349] do_one_initcall+0x46/0x204
kern :warn : [ 211.242407] ? _cond_resched+0x19/0x40
kern :warn : [ 211.242465] ? kmem_cache_alloc_trace+0x3fe/0x480
kern :warn : [ 211.242534] ? do_init_module+0x23/0x220
kern :warn : [ 211.242593] do_init_module+0x5c/0x220
kern :warn : [ 211.242650] load_module+0x10c3/0x1240
kern :warn : [ 211.242707] ? new_sync_read+0x114/0x1a0
kern :warn : [ 211.242767] ? ima_post_read_file+0xf0/0x100
kern :warn : [ 211.242832] ? __do_sys_finit_module+0xaa/0x120
kern :warn : [ 211.242898] __do_sys_finit_module+0xaa/0x120
kern :warn : [ 211.242964] do_syscall_64+0x33/0x40
kern :warn : [ 211.243018] entry_SYSCALL_64_after_hwframe+0x44/0xa9
kern :warn : [ 211.243091] RIP: 0033:0x7f022682d229
kern :warn : [ 211.243146] Code: 00 f3 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 3f 4c 2b 00 f7 d8 64 89 01 48
kern :warn : [ 211.243398] RSP: 002b:00007ffc33248468 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
kern :warn : [ 211.243504] RAX: ffffffffffffffda RBX: 00005592502b9d60 RCX: 00007f022682d229
kern :warn : [ 211.243604] RDX: 0000000000000000 RSI: 00007f0227146265 RDI: 0000000000000014
kern :warn : [ 211.243703] RBP: 00007f0227146265 R08: 0000000000000000 R09: 00007ffc332489e0
kern :warn : [ 211.243803] R10: 0000000000000014 R11: 0000000000000246 R12: 0000000000000000
kern :warn : [ 211.243903] R13: 00005592502b2700 R14: 0000000000020000 R15: 000055924eb37cbc
kern :debug : [ 211.245769] calling acpi_cpufreq_init+0x0/0x1000 [acpi_cpufreq] @ 206
kern :debug : [ 211.245870] initcall acpi_cpufreq_init+0x0/0x1000 [acpi_cpufreq] returned -17 after 0 usecs
kern :info : [ 211.248249] [drm] Initialized i915 1.6.0 20200715 for 0000:00:02.0 on minor 0
kern :debug : [ 211.248980] calling rapl_init+0x0/0x1000 [intel_rapl_common] @ 226
kern :debug : [ 211.249111] initcall rapl_init+0x0/0x1000 [intel_rapl_common] returned 0 after 36 usecs
kern :info : [ 211.251605] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
kern :info : [ 211.252071] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6
kern :debug : [ 211.252317] calling intel_rapl_msr_driver_init+0x0/0x1000 [intel_rapl_msr] @ 220
kern :info : [ 211.252488] intel_rapl_common: Found RAPL domain package
kern :info : [ 211.252566] intel_rapl_common: Found RAPL domain core
kern :info : [ 211.252639] intel_rapl_common: Found RAPL domain uncore
kern :info : [ 211.252714] intel_rapl_common: Found RAPL domain dram
kern :debug : [ 211.255050] initcall i915_init+0x0/0x70 [i915] returned 0 after 2476 usecs
kern :debug : [ 211.259622] initcall intel_rapl_msr_driver_init+0x0/0x1000 [intel_rapl_msr] returned 0 after 7024 usecs
kern :debug : [ 211.266758] calling acpi_cpufreq_init+0x0/0x1000 [acpi_cpufreq] @ 207
kern :debug : [ 211.266859] initcall acpi_cpufreq_init+0x0/0x1000 [acpi_cpufreq] returned -17 after 0 usecs
kern :debug : [ 211.285869] calling acpi_cpufreq_init+0x0/0x1000 [acpi_cpufreq] @ 212
kern :debug : [ 211.285971] initcall acpi_cpufreq_init+0x0/0x1000 [acpi_cpufreq] returned -17 after 0 usecs
kern :info : [ 211.399737] fbcon: i915drmfb (fb0) is primary device
kern :info : [ 211.433505] Console: switching to colour frame buffer device 240x67
kern :info : [ 211.458987] i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device
kern :info : [ 211.475422] systemd-udevd[203]: segfault at 5592502b3830 ip 00007f02267c0958 sp 00007ffc33248d60 error 7 in libc-2.24.so[7f0226749000+195000]
kern :info : [ 211.475701] Code: 48 89 50 18 48 89 42 10 0f 87 4c 05 00 00 4d 01 fd 48 8b 45 68 48 8d 55 58 48 3b 50 18 0f 85 da 06 00 00 49 81 fd ff 03 00 00 <48> 89 43 10 48 89 53 18 76 10 48 c7 43 20 00 00 00 00 48 c7 43 28
kern :err : [ 217.903885] x86/PAT: bmc-watchdog:498 map pfn expected mapping type uncached-minus for [mem 0xa2ee2000-0xa2ee2fff], got write-back
kern :err : [ 217.904824] x86/PAT: bmc-watchdog:498 map pfn expected mapping type uncached-minus for [mem 0xa2352000-0xa2352fff], got write-back
kern :err : [ 217.905119] x86/PAT: bmc-watchdog:498 map pfn expected mapping type uncached-minus for [mem 0xa2352000-0xa2352fff], got write-back
kern :err : [ 217.906024] x86/PAT: bmc-watchdog:498 map pfn expected mapping type uncached-minus for [mem 0xa2352000-0xa2352fff], got write-back
kern :err : [ 217.906423] x86/PAT: bmc-watchdog:498 map pfn expected mapping type uncached-minus for [mem 0xa2352000-0xa2352fff], got write-back
kern :err : [ 217.907029] x86/PAT: bmc-watchdog:498 map pfn expected mapping type uncached-minus for [mem 0xa2352000-0xa2352fff], got write-back
kern :err : [ 217.907491] x86/PAT: bmc-watchdog:498 map pfn expected mapping type uncached-minus for [mem 0xa2352000-0xa2352fff], got write-back
kern :err : [ 217.908091] x86/PAT: bmc-watchdog:498 map pfn expected mapping type uncached-minus for [mem 0xa2352000-0xa2352fff], got write-back
kern :err : [ 217.908512] x86/PAT: bmc-watchdog:498 map pfn expected mapping type uncached-minus for [mem 0xa2352000-0xa2352fff], got write-back
kern :err : [ 217.909108] x86/PAT: bmc-watchdog:498 map pfn expected mapping type uncached-minus for [mem 0xa2352000-0xa2352fff], got write-back
kern :err : [ 217.909517] x86/PAT: bmc-watchdog:498 map pfn expected mapping type uncached-minus for [mem 0xa2352000-0xa2352fff], got write-back
kern :err : [ 217.910020] x86/PAT: bmc-watchdog:498 map pfn expected mapping type uncached-minus for [mem 0xa2ee2000-0xa2ee2fff], got write-back
kern :err : [ 217.910791] x86/PAT: bmc-watchdog:498 map pfn expected mapping type uncached-minus for [mem 0xa2352000-0xa2352fff], got write-back
kern :err : [ 217.911277] x86/PAT: bmc-watchdog:498 map pfn expected mapping type uncached-minus for [mem 0xa2352000-0xa2352fff], got write-back
kern :err : [ 217.912056] x86/PAT: bmc-watchdog:498 map pfn expected mapping type uncached-minus for [mem 0xa2352000-0xa2352fff], got write-back
kern :err : [ 217.912499] x86/PAT: bmc-watchdog:498 map pfn expected mapping type uncached-minus for [mem 0xa2352000-0xa2352fff], got write-back
kern :err : [ 217.913094] x86/PAT: bmc-watchdog:498 map pfn expected mapping type uncached-minus for [mem 0xa2352000-0xa2352fff], got write-back
kern :err : [ 217.913506] x86/PAT: bmc-watchdog:498 map pfn expected mapping type uncached-minus for [mem 0xa2352000-0xa2352fff], got write-back
kern :err : [ 217.914099] x86/PAT: bmc-watchdog:498 map pfn expected mapping type uncached-minus for [mem 0xa2352000-0xa2352fff], got write-back
kern :err : [ 217.914495] x86/PAT: bmc-watchdog:498 map pfn expected mapping type uncached-minus for [mem 0xa2352000-0xa2352fff], got write-back
kern :err : [ 217.915086] x86/PAT: bmc-watchdog:498 map pfn expected mapping type uncached-minus for [mem 0xa2352000-0xa2352fff], got write-back
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,
lkp
5 months, 4 weeks
[x86/smpboot] 5373549352: suspend-stress.fail
by kernel test robot
Greeting,
FYI, we noticed the following commit (built with gcc-9):
commit: 537354935297045556789de8d8ee2d3221b49ace ("x86/smpboot: Setup TSS for starting AP")
https://git.kernel.org/cgit/linux/kernel/git/joro/linux.git sev-es-client-tip-5.9
in testcase: suspend-stress
with following parameters:
mode: mem
iterations: 10
on test machine: 4 threads Broadwell 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>
current commit log:
test started
parent commit log:
SUSPEND RESUME TEST STARTED
Suspend to mem 1/10:
...
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
5 months, 4 weeks
[btrfs] 07f94dcaa6: xfstests.generic.062.fail
by kernel test robot
Greeting,
FYI, we noticed the following commit (built with gcc-9):
commit: 07f94dcaa6065f95777fcc9717043b5c677cef71 ("[PATCH 1/1] btrfs: Track subdirectories in nlink")
url: https://github.com/0day-ci/linux/commits/Nikolay-Borisov/Basic-subdir-tra...
base: https://git.kernel.org/cgit/linux/kernel/git/kdave/linux.git for-next
in testcase: xfstests
with following parameters:
disk: 4HDD
fs: btrfs
test: generic-group14
ucode: 0x28
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: 8 threads Intel(R) Core(TM) i7-4790 v3 @ 3.60GHz with 6G 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>
2020-09-01 13:44:05 export TEST_DIR=/fs/sda1
2020-09-01 13:44:05 export TEST_DEV=/dev/sda1
2020-09-01 13:44:05 export FSTYP=btrfs
2020-09-01 13:44:05 export SCRATCH_MNT=/fs/scratch
2020-09-01 13:44:05 mkdir /fs/scratch -p
2020-09-01 13:44:05 export SCRATCH_DEV_POOL="/dev/sda2 /dev/sda3 /dev/sda4"
2020-09-01 13:44:05 sed "s:^:generic/:" //lkp/benchmarks/xfstests/tests/generic-group14 | grep -F -f merged_ignored_files
2020-09-01 13:44:05 sed "s:^:generic/:" //lkp/benchmarks/xfstests/tests/generic-group14 | grep -v -F -f merged_ignored_files
2020-09-01 13:44:05 ./check generic/020 generic/062 generic/095 generic/128 generic/163 generic/195 generic/226 generic/257 generic/290 generic/322 generic/354 generic/384 generic/419 generic/452 generic/491 generic/526 generic/556 generic/586
FSTYP -- btrfs
PLATFORM -- Linux/x86_64 lkp-hsw-d02 5.9.0-rc2-00114-g07f94dcaa6065f #1 SMP Fri Aug 28 09:51:12 CST 2020
MKFS_OPTIONS -- /dev/sda2
MOUNT_OPTIONS -- /dev/sda2 /fs/scratch
generic/020 0s
generic/062 _check_btrfs_filesystem: filesystem on /dev/sda2 is inconsistent
(see /lkp/benchmarks/xfstests/results//generic/062.full for details)
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
6 months
[block] b216a023b9: mdadm-selftests./lkp/benchmarks/mdadm-selftests/tests/07layouts.fail
by kernel test robot
Greeting,
FYI, we noticed the following commit (built with gcc-9):
commit: b216a023b9936afc5a2d979a4ba718073fdefe49 ("block: keep a block_device reference for each hd_struct")
git://git.infradead.org/users/hch/block.git bdev-inode
in testcase: mdadm-selftests
testcase version: mdadm-selftests-x86_64-5d518de-1_20200717
with following parameters:
disk: 1HDD
test_prefix: 07layout
ucode: 0x21
on test machine: 4 threads Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz with 4G 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>
2020-09-01 12:58:06 mkdir -p /var/tmp
2020-09-01 12:58:06 mke2fs -t ext3 -b 4096 -J size=4 -q /dev/sda3
2020-09-01 12:59:07 mount -t ext3 /dev/sda3 /var/tmp
sed -e 's/{DEFAULT_METADATA}/1.2/g' \
-e 's,{MAP_PATH},/run/mdadm/map,g' mdadm.8.in > mdadm.8
/usr/bin/install -D -m 644 mdadm.8 /usr/share/man/man8/mdadm.8
/usr/bin/install -D -m 644 mdmon.8 /usr/share/man/man8/mdmon.8
/usr/bin/install -D -m 644 md.4 /usr/share/man/man4/md.4
/usr/bin/install -D -m 644 mdadm.conf.5 /usr/share/man/man5/mdadm.conf.5
/usr/bin/install -D -m 644 udev-md-raid-creating.rules /lib/udev/rules.d/01-md-raid-creating.rules
/usr/bin/install -D -m 644 udev-md-raid-arrays.rules /lib/udev/rules.d/63-md-raid-arrays.rules
/usr/bin/install -D -m 644 udev-md-raid-assembly.rules /lib/udev/rules.d/64-md-raid-assembly.rules
/usr/bin/install -D -m 644 udev-md-clustered-confirm-device.rules /lib/udev/rules.d/69-md-clustered-confirm-device.rules
/usr/bin/install -D -m 755 mdadm /sbin/mdadm
/usr/bin/install -D -m 755 mdmon /sbin/mdmon
Testing on linux-5.9.0-rc3-00066-gb216a023b9936 kernel
/lkp/benchmarks/mdadm-selftests/tests/07layouts... FAILED - see /var/tmp/07layouts.log and /var/tmp/fail07layouts.log for details
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
6 months
Re: [kthread] 2e7d8748eb: last_state.is_incomplete_run
by Chen, Rong A
Thanks for the input, we do detect this on this commit but not its parent.
It may be merged into a wrong base branch or something else that
we are not aware of. And it's kind difficulty now for us to provide a
reproduction step for kexec issue, we will consider this further.
Best Regards,
Rong Chen
On 8/27/2020 11:49 AM, qianli zhao wrote:
> I did not see any exceptions related to my changes,the corresponding
> macro CONFIG_DEBUG_OBJECTS_KTHREAD is not enabled,so i think the issue
> has nothing to do with my changes
>
> Thanks
>
> On Thu, 20 Aug 2020 at 14:26, kernel test robot <rong.a.chen(a)intel.com> wrote:
>> Greeting,
>>
>> FYI, we noticed the following commit (built with gcc-9):
>>
>> commit: 2e7d8748eba7e32150cbd4f57129ea77d1255892 ("[RFC V2] kthread: add object debug support")
>> url: https://github.com/0day-ci/linux/commits/Qianli-Zhao/kthread-add-object-d...
>> base: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git fb893de323e2d39f7a1f6df425703a2edbdf56ea
>>
>> in testcase: boot
>>
>> on test machine: 8 threads Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz with 16G memory
>>
>> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
>>
>>
>>
>> kernel boot failed by kexec:
>>
>> user :notice: [32m[ +0.371313] [0m [33mLKP [0m: kexec loading...
>> user :notice: [32m[ +0.007118] [0mkexec --noefi -l /opt/rootfs/tmp/pkg/linux/x86_64-rhel-8.3/gcc-9/2e7d8748eba7e32150cbd4f57129ea77d1255892/vmlinuz-5.8.0-12610-g2e7d8748eba7e --initrd=/opt/rootfs/tmp/initrd-concatenated
>>
>>
>>
>>
>> Thanks,
>> Rong Chen
>>
6 months
[dyndbg] 70f06a871f: kernel_BUG_at_lib/dynamic_debug.c
by kernel test robot
Greeting,
FYI, we noticed the following commit (built with gcc-9):
commit: 70f06a871f5d40ca8f977eb412358ab03b6804da ("[PATCH v3 3/3] dyndbg: fix problem parsing format="foo bar"")
url: https://github.com/0day-ci/linux/commits/Jim-Cromie/dyndbg-cleanups-for-5...
base: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git f75aef392f869018f78cfedf3c320a6b3fcfda6b
in testcase: kernel-selftests
with following parameters:
group: kselftests-livepatch
test-description: The kernel contains a set of "self tests" under the tools/testing/selftests/ directory. These are intended to be small unit tests to exercise individual code paths in the kernel.
test-url: https://www.kernel.org/doc/Documentation/kselftest.txt
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):
+------------------------------------------+------------+------------+
| | 12aeaa9439 | 70f06a871f |
+------------------------------------------+------------+------------+
| boot_successes | 6 | 2 |
| boot_failures | 0 | 4 |
| kernel_BUG_at_lib/dynamic_debug.c | 0 | 4 |
| invalid_opcode:#[##] | 0 | 4 |
| RIP:ddebug_exec_query | 0 | 4 |
| Kernel_panic-not_syncing:Fatal_exception | 0 | 4 |
+------------------------------------------+------------+------------+
If you fix the issue, kindly add following tag
Reported-by: kernel test robot <lkp(a)intel.com>
[ 78.796907] kernel BUG at lib/dynamic_debug.c:267!
[ 78.799930] invalid opcode: 0000 [#1] PREEMPT SMP PTI
[ 78.801632] CPU: 1 PID: 1068 Comm: test-livepatch. Tainted: G K 5.9.0-rc3-00003-g70f06a871f5d4 #1
[ 78.803877] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014
[ 78.805929] RIP: 0010:ddebug_exec_query+0x684/0x760
[ 78.807642] Code: 0f 85 c0 08 00 00 4c 89 7c 24 28 e9 2d fc ff ff 4c 89 fe 48 8d 7c 24 10 e8 a9 f8 ff ff 85 c0 0f 84 18 fc ff ff e9 c1 07 00 00 <0f> 0b 8b 15 ac 37 e2 02 85 d2 0f 85 c1 00 00 00 45 31 e4 48 c7 c6
[ 78.812169] RSP: 0018:ffffb325411c7d78 EFLAGS: 00010246
[ 78.815411] RAX: 000000000000003d RBX: ffff9f4dab69286c RCX: 0000000000000000
[ 78.821166] RDX: 000000000000003d RSI: ffff9f4dab692868 RDI: ffff9f4dab69286c
[ 78.823160] RBP: 0000000000000004 R08: ffff9f4dab69286e R09: 0000000000000001
[ 78.825172] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000004
[ 78.827212] R13: 0000000000000004 R14: 0000000000000000 R15: 0000000000000000
[ 78.829228] FS: 00007f024c29c740(0000) GS:ffff9f4e77d00000(0000) knlGS:0000000000000000
[ 78.831343] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 78.833243] CR2: 00007f024c45c8a0 CR3: 0000000168360000 CR4: 00000000000406e0
[ 78.835312] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 78.837371] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[ 78.839398] Call Trace:
[ 78.840935] ? __might_fault+0x36/0x80
[ 78.842574] ddebug_exec_queries+0x6a/0x100
[ 78.844322] ddebug_proc_write+0x4e/0x80
[ 78.845985] full_proxy_write+0x56/0x80
[ 78.847621] vfs_write+0xec/0x240
[ 78.849189] ksys_write+0x68/0xe0
[ 78.850738] do_syscall_64+0x33/0x40
[ 78.852347] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 78.854106] RIP: 0033:0x7f024c389504
[ 78.855634] Code: 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b3 0f 1f 80 00 00 00 00 48 8d 05 f9 61 0d 00 8b 00 85 c0 75 13 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 c3 0f 1f 00 41 54 49 89 d4 55 48 89 f5 53
[ 78.860364] RSP: 002b:00007fff5962d2b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
[ 78.864609] RAX: ffffffffffffffda RBX: 00000000000000bc RCX: 00007f024c389504
[ 78.866696] RDX: 00000000000000bc RSI: 00005582ce63dcd0 RDI: 0000000000000001
[ 78.868751] RBP: 00005582ce63dcd0 R08: fffffffffffffff0 R09: 00007f024c419e80
[ 78.870832] R10: 00005582ce63dd8c R11: 0000000000000246 R12: 00007f024c45b760
[ 78.872933] R13: 00000000000000bc R14: 00007f024c456760 R15: 00000000000000bc
[ 78.875077] Modules linked in: intel_rapl_msr intel_rapl_common snd_pcm sr_mod cdrom sg crct10dif_pclmul ppdev crc32_pclmul snd_timer bochs_drm crc32c_intel ata_generic ghash_clmulni_intel snd pata_acpi drm_vram_helper aesni_intel drm_ttm_helper crypto_simd ttm cryptd ata_piix glue_helper soundcore joydev pcspkr serio_raw parport_pc libata parport ipmi_devintf ipmi_msghandler floppy i2c_piix4 ip_tables [last unloaded: test_klp_atomic_replace]
[ 78.889926] ---[ end trace aae1acea69a78e4f ]---
To reproduce:
# build kernel
cd linux
cp config-5.9.0-rc3-00003-g70f06a871f5d4 .config
make HOSTCC=gcc-9 CC=gcc-9 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,
lkp
6 months