iovisor / iovisor/bcc

softirqs fails to run

Open
#851 3 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
C
Stars
22.7k
Forks
4.1k
Avg merge
5d 13h
Merged PRs (30d)
3

Description

When running softirqs, I run into the following exception.

This issue is seen on Debian, with Debian packaged bpfcc.

```
rs@learner:~$ sudo softirqs
write(/sys/kernel/debug/tracing/kprobe_events, "p:kprobes/p_blk_iopoll_softirq blk_iopoll_softirq") failed: No such file or directory
c_void_p(None)
Traceback (most recent call last):
File "/usr/sbin/softirqs", line 118, in
b.attach_kprobe(event=softirqfunc, fn_name="trace_start")
File "/usr/lib/python2.7/dist-packages/bcc/__init__.py", line 419, in attach_kprobe
raise Exception("Failed to attach BPF to kprobe")
Exception: Failed to attach BPF to kprobe
2016-12-12 / 18:08:38 ♒♒♒ ☹ => 1
rrs@learner:~$ sudo ls -l /sys/kernel/debug/tracing/kprobe_events
-rw-r--r-- 1 root root 0 Dec 11 18:49 /sys/kernel/debug/tracing/kprobe_events
2016-12-12 / 18:09:04 ♒♒♒ ☺
```

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing `sudo softirqs` on Debian with the Debian-packaged bpfcc and inspect the reported write to `/sys/kernel/debug/tracing/kprobe_events`. Compare the failing `blk_iopoll_softirq` kprobe setup with the `softirqs` entry point shown in the traceback. Done means the command attaches its probes and runs without the reported exception.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, python
Domain
observability-sre, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.