From: Arnd Bergmann <arnd@arndb.de>
To: Christian Zigotzky <chzigotzky@xenosoft.de>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
Jakub Kicinski <kuba@kernel.org>,
Christophe Leroy <christophe.leroy@c-s.fr>,
DTML <devicetree@vger.kernel.org>,
Darren Stevens <darren@stevens-zone.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linuxppc-dev@ozlabs.org, "contact@a-eon.com" <contact@a-eon.com>,
"R.T.Dickinson" <rtd2@xtra.co.nz>, Christoph Hellwig <hch@lst.de>,
mad skateman <madskateman@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Christian Zigotzky <info@xenosoft.de>
Subject: Re: Latest Git kernel: avahi-daemon[2410]: ioctl(): Inappropriate ioctl for device
Date: Fri, 7 Feb 2020 17:08:06 +0000 [thread overview]
Message-ID: <CAK8P3a39L5i4aEbKe9CiW6unbioL=T8GqXC007mXxUu+_j84FA@mail.gmail.com> (raw)
In-Reply-To: <42888ad2-71e0-6d03-ddff-3de6f0ee5d43@xenosoft.de>
On Fri, Feb 7, 2020 at 3:34 PM Christian Zigotzky
<chzigotzky@xenosoft.de> wrote:
>
> Hello Arnd,
>
> We regularly compile and test Linux kernels every day during the merge
> window. Since Thursday last week we have very high CPU usage because of
> the avahi daemon on our desktop Linux systems (Ubuntu, Debian etc). The
> avahi daemon produces a lot of the following log message. This generates
> high CPU usage.
>
> Error message: avahi-daemon[2410]: ioctl(): Inappropriate ioctl for device
>
> strace /usr/sbin/avahi-daemon:
>
Thanks a lot for the detailed analysis, with this I immediately saw
what went wrong in my
original commit and I sent you a fix. Please test to ensure that this
correctly addresses
the problem.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Christian Zigotzky <chzigotzky@xenosoft.de>
Cc: DTML <devicetree@vger.kernel.org>,
Darren Stevens <darren@stevens-zone.net>,
mad skateman <madskateman@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linuxppc-dev@ozlabs.org, "contact@a-eon.com" <contact@a-eon.com>,
"R.T.Dickinson" <rtd2@xtra.co.nz>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Christoph Hellwig <hch@lst.de>,
Christian Zigotzky <info@xenosoft.de>
Subject: Re: Latest Git kernel: avahi-daemon[2410]: ioctl(): Inappropriate ioctl for device
Date: Fri, 7 Feb 2020 17:08:06 +0000 [thread overview]
Message-ID: <CAK8P3a39L5i4aEbKe9CiW6unbioL=T8GqXC007mXxUu+_j84FA@mail.gmail.com> (raw)
In-Reply-To: <42888ad2-71e0-6d03-ddff-3de6f0ee5d43@xenosoft.de>
On Fri, Feb 7, 2020 at 3:34 PM Christian Zigotzky
<chzigotzky@xenosoft.de> wrote:
>
> Hello Arnd,
>
> We regularly compile and test Linux kernels every day during the merge
> window. Since Thursday last week we have very high CPU usage because of
> the avahi daemon on our desktop Linux systems (Ubuntu, Debian etc). The
> avahi daemon produces a lot of the following log message. This generates
> high CPU usage.
>
> Error message: avahi-daemon[2410]: ioctl(): Inappropriate ioctl for device
>
> strace /usr/sbin/avahi-daemon:
>
Thanks a lot for the detailed analysis, with this I immediately saw
what went wrong in my
original commit and I sent you a fix. Please test to ensure that this
correctly addresses
the problem.
Arnd
next prev parent reply other threads:[~2020-02-07 17:08 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-26 11:52 [PATCH] of: Add OF_DMA_DEFAULT_COHERENT & select it on powerpc Michael Ellerman
2020-01-26 11:52 ` Michael Ellerman
2020-01-27 7:22 ` Ulf Hansson
2020-01-27 7:22 ` Ulf Hansson
2020-01-31 10:40 ` Michael Ellerman
2020-01-31 10:40 ` Michael Ellerman
2020-02-02 0:08 ` Latest Git kernel: avahi-daemon[2410]: ioctl(): Inappropriate ioctl for device Christian Zigotzky
2020-02-02 0:08 ` Christian Zigotzky
2020-02-02 4:37 ` Randy Dunlap
2020-02-02 4:37 ` Randy Dunlap
2020-02-02 8:19 ` Christophe Leroy
2020-02-02 15:02 ` Christian Zigotzky
2020-02-03 17:53 ` Jakub Kicinski
2020-02-03 17:53 ` Jakub Kicinski
2020-02-05 13:03 ` Christian Zigotzky
2020-02-05 13:03 ` Christian Zigotzky
2020-02-05 14:36 ` Christian Zigotzky
2020-02-06 4:35 ` Michael Ellerman
2020-02-06 4:35 ` Michael Ellerman
2020-02-06 14:28 ` Christian Zigotzky
2020-02-06 14:28 ` Christian Zigotzky
2020-02-08 12:36 ` Michael Ellerman
2020-02-08 12:36 ` Michael Ellerman
2020-02-07 14:34 ` Christian Zigotzky
2020-02-07 14:34 ` Christian Zigotzky
2020-02-07 17:08 ` Arnd Bergmann [this message]
2020-02-07 17:08 ` Arnd Bergmann
2020-02-08 6:59 ` Christian Zigotzky
2020-02-08 6:59 ` Christian Zigotzky
2020-02-08 16:08 ` Christian Zigotzky
2020-02-08 16:08 ` Christian Zigotzky
2020-01-27 17:30 ` [PATCH] of: Add OF_DMA_DEFAULT_COHERENT & select it on powerpc Frank Rowand
2020-01-27 17:30 ` Frank Rowand
2020-01-28 14:26 ` Rob Herring
2020-01-28 14:26 ` Rob Herring
2020-01-31 10:40 ` Michael Ellerman
2020-01-31 10:40 ` Michael Ellerman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAK8P3a39L5i4aEbKe9CiW6unbioL=T8GqXC007mXxUu+_j84FA@mail.gmail.com' \
--to=arnd@arndb.de \
--cc=christophe.leroy@c-s.fr \
--cc=chzigotzky@xenosoft.de \
--cc=contact@a-eon.com \
--cc=darren@stevens-zone.net \
--cc=devicetree@vger.kernel.org \
--cc=hch@lst.de \
--cc=info@xenosoft.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=madskateman@gmail.com \
--cc=mpe@ellerman.id.au \
--cc=netdev@vger.kernel.org \
--cc=rtd2@xtra.co.nz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.