Thanks for the report. I'd like to profile avahi using perf to get information on what functions are being executed. Could you run the following commands to generate such data?
If you are unsure about any of this feel free to ask.
And then upload the resulting avahi-perf.script.txt and avahi-perf.report.txt for analysis.
You'll want to make sure avahi is using 100%+ CPU at the time you do this.
Lastly from the same bootup, can you please collect the log info from journalctl:
journalctl -u avahi-daemon --no-pager --no-tail > avahi-journal.txt
Thanks for reporting the bug! Hopefully we can figure it out.
In the mean time if you want to disable avahi you can try this:
sudo systemctl disable avahi-daemon.socket avahi-daemon
sudo systemctl stop avahi-daemon.socket avahi-daemon
Hi Matt,
Thanks for the report. I'd like to profile avahi using perf to get information on what functions are being executed. Could you run the following commands to generate such data?
If you are unsure about any of this feel free to ask.
echo "deb http:// ddebs.ubuntu. com $(lsb_release -cs) main restricted universe multiverse" | sudo tee -a /etc/apt/ sources. list.d/ ddebs.list dbgsym- keyring linux-cloud- tools-generic common3- dbgsym libavahi- core7-dbgsym libavahi- glib1-dbgsym libc6-dbgsym libcap2-dbgsym libdaemon0-dbgsym libdbus-1-3-dbgsym libecore- avahi1- dbgsym libexpat1-dbgsym libgcrypt20-dbgsym libgpg- error0- dbgsym liblz4-1-dbgsym liblzma5-dbgsym libnss- systemd- dbgsym libsystemd0-dbgsym
sudo apt update
sudo apt install linux-tools-generic ubuntu-
sudo apt update
sudo apt install avahi-daemon-dbgsym libavahi-
then to record a profile:
sudo perf record -p $(cat /run/avahi- daemon/ pid) -g -- sleep 60
This will exit after 60 seconds, then generate perf script output:
sudo perf script > avahi-perf. script. txt report. txt
sudo perf report -n --stdio > avahi-perf.
And then upload the resulting avahi-perf. script. txt and avahi-perf. report. txt for analysis.
You'll want to make sure avahi is using 100%+ CPU at the time you do this.
Lastly from the same bootup, can you please collect the log info from journalctl:
journalctl -u avahi-daemon --no-pager --no-tail > avahi-journal.txt
Thanks for reporting the bug! Hopefully we can figure it out.
In the mean time if you want to disable avahi you can try this:
sudo systemctl disable avahi-daemon.socket avahi-daemon
sudo systemctl stop avahi-daemon.socket avahi-daemon
(to re-enable change to start and enable)
Regards,
Trent