scope: eBPF tracking causes panic on Ubuntu kernel 4.4.0-119

Full kernel version: 4.4.0-119-generic #143-Ubuntu SMP We were previously running 4.4.0-116-generic #140-Ubuntu SMP with no problems

Workaround:

Disable eBPF connection tracking with --probe.ebpf.connections=false

Panic details

panic.txt

About this issue

Original URL
State: closed
Created 6 years ago
Reactions: 1
Comments: 15 (9 by maintainers)

Commits related to this issue

ebpf: check for known faulty Ubuntu kernel The Ubuntu Xenial update to kernel 4.4.0-119.143 from 4.4.0-116.140 did include a regression in the eBPF code. A basic `bpf_map_lookup_elem` call as found i... — committed to kinvolk-archives/scope by schu 6 years ago
ebpf: check for known faulty Ubuntu kernel The Ubuntu Xenial update to kernel 4.4.0-119.143 from 4.4.0-116.140 did include a regression in the eBPF code. A basic `bpf_map_lookup_elem` call as found i... — committed to kinvolk-archives/scope by schu 6 years ago
ebpf: check for known faulty Ubuntu kernel The Ubuntu Xenial update to kernel 4.4.0-119.143 from 4.4.0-116.140 did include a regression in the eBPF code. A basic `bpf_map_lookup_elem` call as found i... — committed to kinvolk-archives/scope by schu 6 years ago
ebpf: check for known faulty Ubuntu kernel The Ubuntu Xenial update to kernel 4.4.0-119.143 from 4.4.0-116.140 did include a regression in the eBPF code. A basic `bpf_map_lookup_elem` call as found i... — committed to kinvolk-archives/scope by schu 6 years ago
ebpf: update check for known faulty Ubuntu kernels With c75700fe04251b6d93240fb36ec423ed22b5d59d we added code to detect Ubuntu Xenial kernels with a regression in the eBPF subsystem in order to gent... — committed to kinvolk-archives/scope by schu 6 years ago
ebpf: update check for known faulty Ubuntu kernels With c75700fe04251b6d93240fb36ec423ed22b5d59d we added code to detect Ubuntu Xenial kernels with a regression in the eBPF subsystem in order to gent... — committed to lilic/scope by schu 6 years ago

Most upvoted comments

I tried it with just Scope, no Kubernetes or other stuff: Before:

$ uname -a
Linux bryan-dev2 4.4.0-101-generic #124-Ubuntu SMP Fri Nov 10 18:29:59 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
$ scope launch
ebba7e65f5940c0eca410ca8f3d89f4839963ea5d1f0d52f79f5325a8762b50a
Scope probe started
Weave Scope is listening at the following URL(s):
  * http://10.240.0.2:4040/

After:

$ uname -a
Linux bryan-dev2 4.4.0-119-generic #143-Ubuntu SMP Mon Apr 2 16:08:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
$ scope launch
0a3b2a7a3580f2100f2374e334eea104a1f6f3371659de905db99c98942b1257
Scope probe started
ERRO[0002] error getting events from daemon: unexpected EOF 
sh: ../sysdeps/nptl/fork.c:156: __libc_fork: Assertion `THREAD_GETMEM (self, tid) != ppid' failed.
Aborted
[machine is unresponsive]

bboreham on Apr 10, 2018

It’d be interesting to also have the known to work version so one can look at the list of commits that found their way in.

dlespiau on Apr 5, 2018