[lkp-robot] [net] 3416099d53: net/core/dev.c:#suspicious_rcu_dereference_protected()usage

2018-05-20 Thread kernel test robot
-openwrt-ia32-19, MAC , kernel 4.17.0-rc4-01248-g3416099 1, serial console /dev/ttyS0 [ 27.410153] Kernel tests: Boot OK! [ 27.410153] LKP: waiting for network... [ 28.230718] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [ 28.233430] IPv6: ADDRCONF(NETDEV_CHANGE): et

[page_frag_cache] 47b0eaa4b5: BUG:unable_to_handle_kernel

2018-03-16 Thread kernel test robot
| 8 | | Kernel_panic-not_syncing:Fatal_exception | 0 | 8 | +--+++ [9.277582] BUG: unable to handle kernel NULL pointer dereference at 0010 [9.278874] IP: page_frag_alloc+0xd/0x99 [9.2

[net] ba4f5b62a2: kernel_BUG_at_net/socket.c

2018-02-24 Thread kernel test robot
rnel_panic-not_syncing:Fatal_exception | 0 | 6 | +--+++ [0.054820] kernel BUG at net/socket.c:293! [0.055261] invalid opcode: [#1] PREEMPT [0.055574] CPU: 0 PID: 1 Comm: swapper Not tainted 4.16.0-rc2-0014

[fw_cfg] c8bf448ff3: kernel_BUG_at_arch/x86/mm/physaddr.c

2018-02-01 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: c8bf448ff3899860de51fbae61a43619c912ddf2 ("fw_cfg: do DMA read operation") https://git.kernel.org/cgit/linux/kernel/git/mst/vhost.git vhost in testcase: boot on test machine: qemu-system-x86_64 -enable-kvm -m 420M ca

[lkp-robot] [socket] 3bc58b1a49: BUG:using__this_cpu_add()in_preemptible[#]code:krfcommd

2017-11-16 Thread kernel test robot
email Thanks, Xiaolong # # Automatically generated file; DO NOT EDIT. # Linux/x86_64 4.14.0-rc7 Kernel Configuration # CONFIG_64BIT=y CONFIG_X86_64=y CONFIG_X86=y CONFIG_INSTRUCTION_DECODER=y CONFIG_OUTPUT_FORMAT="elf64-x86-64" CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defco

bd2e1bcd9a: BUG:sleeping_function_called_from_invalid_context_at_mm/slab.h

2017-11-06 Thread kernel test robot
exec/gcc-6/bd2e1bcd9a94fc6b6298185901d11b93a425c0d2/modules.cgz ) cat "${initrds[@]}" > /fs/sdc1/initrd-vm-lkp-wsx03-4G-1 kvm=( qemu-system-x86_64 -enable-kvm -cpu host -kernel /pkg/linux/x86_64-kexec/gcc-6/bd2e1bcd9a94fc6b6298185901d11b93a425c0d2/vmlinuz-4.14.0-rc7-00137-g

[lkp-robot] [irda] 66d98e78e4: BUG:unable_to_handle_kernel

2017-08-30 Thread kernel test robot
v_add_pack| 0 | 12 | | Kernel_panic-not_syncing:Fatal_exception| 0 | 12 | +-+++ [0.227015] BUG: unable to handle kernel NULL pointer dereference at 0004 [0.

[lkp-robot] [lib] e859afe1ee: kernel_BUG_at_lib/test_rhashtable.c

2017-07-26 Thread kernel test robot
FYI, we noticed the following commit: commit: e859afe1ee0c5ae981c55387ccd45eba258a7842 ("lib: test_rhashtable: fix for large entry counts") https://git.kernel.org/cgit/linux/kernel/git/davem/net.git master in testcase: boot on test machine: qemu-system-x86_64 -enable-kvm -m 420M ca

[rhashtable] 6d684e5469: Kernel panic - not syncing: rtnetlink_init: cannot initialize rtnetlink

2017-04-27 Thread kernel test robot
Greetings, 0day kernel testing robot got the below dmesg and the first bad commit is https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git master commit 6d684e54690caef45cf14051ddeb7c71beeb681b Author: Herbert Xu <herb...@gondor.apana.org.au> AuthorDate: Thu Apr 27 13

[lkp-robot] [rhashtable ] df7008bdd5: Kernel_panic-not_syncing:rtnetlink_init:cannot_initialize_rtnetlink

2017-04-27 Thread kernel test robot
ator-dummy: no parameters [0.098851] regulator-dummy: Failed to create debugfs directory [0.098851] regulator-dummy: Failed to create debugfs directory [0.100650] NET: Registered protocol family 16 [0.100650] NET: Registered protocol family 16 [0.101854] Kernel panic - n

6f58284e66: BUG: kernel hang in boot stage

2017-04-10 Thread kernel test robot
Greetings, 0day kernel testing robot got the below dmesg and the first bad commit is https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master commit 6f58284e666261162b2c95fdd8608f5e247e9a38 Merge: 7fd97bca bf74b20 Author: Stephen Rothwell <s...@canb.auug.org.au> Auth

[bpf] 9d876e79df: BUG: unable to handle kernel paging request at 653a8346

2017-02-26 Thread kernel test robot
Greetings, 0day kernel testing robot got the below dmesg and the first bad commit is https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master commit 9d876e79df6a2f364b9f2737eacd72ceb27da53a Author: Daniel Borkmann <dan...@iogearbox.net> AuthorDate: Tue Feb 21 16:09:3

[lkp-robot] [xdp] 543d41bf78: INFO:suspicious_RCU_usage

2017-02-12 Thread kernel test robot
x60,0x64 irq 12 To reproduce: git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git cd lkp-tests bin/lkp qemu -k job-script # job-script is attached in this email Thanks, Xiaolong # # Automatically generated file; DO NOT EDIT. # Linux/i386 4

[lkp-robot] [rhashtable] 60be2ebf32: INFO:suspicious_RCU_usage

2017-02-08 Thread kernel test robot
failed to execute /sbin/v86d [ 257.126137] uvesafb: make sure that the v86d helper is installed and executable [ 257.126137] uvesafb: make sure that the v86d helper is installed and executable To reproduce: git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-t

[lkp-robot] [net] 5e2f2bdf34: BUG:unable_to_handle_kernel

2017-02-05 Thread kernel test robot
andom: uci: uninitialized urandom read (6 bytes read) [ 14.025067] random: uci: uninitialized urandom read (6 bytes read) [ 14.100439] sysctl (464) used greatest stack depth: 6480 bytes left [ 14.371523] BUG: unable to handle kernel NULL pointer dereference at 0178 [ 14.372723] IP: rt6_fill_

[lkp-robot] [ipv6] 31cdaa587d: BUG:sleeping_function_called_from_invalid_context_at_kernel/locking/mutex.c

2017-01-24 Thread kernel test robot
TC configured in localtime, applying delta of 480 minutes to system time. [5.775578] NET: Registered protocol family 10 [5.778339] BUG: sleeping function called from invalid context at kernel/locking/mutex.c:752 [5.779426] in_atomic(): 1, irqs_disabled(): 0, pid: 1, name: systemd [5.780127]

[lkp-robot] [net] a1a22c1206: BUG:unable_to_handle_kernel

2017-01-22 Thread kernel test robot
FYI, we noticed the following commit: commit: a1a22c12060e4b9c52f45d4b3460f614e00162a2 ("net: ipv6: Keep nexthop of multipath route on admin down") https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git master in testcase: trinity with following parameters: run

[net] bf7d953378: BUG:sleeping_function_called_from_invalid_context_at_kernel/locking/mutex.c

2017-01-06 Thread kernel test robot
bytes read) [9.004266] random: uci: uninitialized urandom read (6 bytes read) [9.379490] BUG: sleeping function called from invalid context at kernel/locking/mutex.c:232 [9.383499] in_atomic(): 1, irqs_disabled(): 0, pid: 1816, name: dropbearkey [9.386025] CPU: 0 PID: 1816 Comm: dropbearkey N

[lkp-developer] [page_pool] 50a8fe7622: kernel_BUG_at_mm/slub.c

2017-01-05 Thread kernel test robot
| 4 | +--+++ [0.00] .text : 0xc100 - 0xc188d0b7 (8756 kB) [0.00] Checking if this processor honours the WP bit even in supervisor mode...Ok. [0.00] [ cut here ] [0.00] kernel BUG at mm/slub.c:349! [

[lkp] [net] 50d4a9ef15: INFO:suspicious_RCU_usage

2016-11-22 Thread kernel test robot
20.190554] --- [ 20.196388] kernel/sched/core.c:7729 Illegal context switch in RCU-bh read-side critical section! [ 20.210614] [ 20.210614] other info that might help us debug this: [ 20.210614] [ 20.221405] [ 20.221405] rcu_scheduler_active = 1, debug

[lkp] [net] af1fee9821: BUG:spinlock_trylock_failure_on_UP_on_CPU

2016-11-06 Thread kernel test robot
FYI, we noticed the following commit: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git master commit af1fee98219992ba2c12441a447719652ed7e983 ("net: phy: Add support for Microsemi VSC 8530/40 Fast Ethernet PHY") in testcase: boot on test machine: qemu-system-x86_

[lkp] [netfilter] 68263ddb47: WARNING: CPU: 0 PID: 1225 at net/netfilter/nf_conntrack_seqadj.c:232 nf_ct_seq_offset+0x7a/0x9a

2016-09-16 Thread kernel test robot
| 1 | +--+++ [ 22.475640] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [ 22.602089] Kernel tests: Boot OK! [ 23.465616] [ cut here ] [ 23.466477] WARNING: CPU: 0 PID: 1225 at net

[lkp] [net] 70a8118a03: BUG: workqueue leaked lock or atomic: kworker/0:1/0x00000000/28

2016-09-16 Thread kernel test robot
Thanks, Xiaolong # # Automatically generated file; DO NOT EDIT. # Linux/x86_64 4.8.0-rc4 Kernel Configuration # CONFIG_64BIT=y CONFIG_X86_64=y CONFIG_X86=y CONFIG_INSTRUCTION_DECODER=y CONFIG_OUTPUT_FORMAT="elf64-x86-64" CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig&

[lkp] [net/netpolicy] 19e7d15d66: EIP: [] netpolicy_unregister+0x23a/0x28a SS:ESP 0068:ceb19d94

2016-08-16 Thread kernel test robot
exit_group| 0 | 9 | +-+++ [ 60.668086] BUG: unable to handle kernel NULL pointer dereference at 05e4 [ 60.668237] IP: [] netpolicy_unregister+0x23a/0x28a [ 60.668

[perf core] c5dfd78eb7: BUG: unable to handle kernel NULL pointer dereference at 00000c40

2016-06-24 Thread kernel test robot
Greetings, 0day kernel testing robot got the below dmesg and the first bad commit is https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master commit c5dfd78eb79851e278b7973031b9ca363da87a7e Author: Arnaldo Carvalho de Melo <a...@redhat.com> AuthorDate: Thu Apr 21 12

Re: [PATCH 15/17] sky2: only disable 88e8056 on some boards

2007-05-15 Thread kernel
Observations. - The problem may not be sky2 specific. I have diskless nodes where too many can NOT 1) reliably DHCP an IP number from the server 2) and if the pxelinux.cfg/default loads, it is not certain if the kernel or the initrd would tftp transfer. There are two of 12 diskless

Re: [PATCH] sky2: re-enable 88E8056 for most motherboards

2007-05-13 Thread kernel
/ Motherboard / Products_Overview.aspx?ProductID=2388 Observations. - The problem may not be sky2 specific. I have diskless nodes where too many can NOT 1) reliably DHCP an IP number from the server 2) and if the pxelinux.cfg/default loads, it is not certain if the kernel or the initrd