From: Michael Ellerman <mpe@ellerman.id.au> To: Christian Zigotzky <chzigotzky@xenosoft.de>, Jakub Kicinski <kuba@kernel.org> Cc: 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> Subject: Re: Latest Git kernel: avahi-daemon[2410]: ioctl(): Inappropriate ioctl for device Date: Sat, 08 Feb 2020 23:36:34 +1100 [thread overview] Message-ID: <87imkh1cj1.fsf@mpe.ellerman.id.au> (raw) In-Reply-To: <f438e4ed-7746-1d80-6d72-455281884a1e@xenosoft.de> Christian Zigotzky <chzigotzky@xenosoft.de> writes: > On 06 February 2020 at 05:35 am, Michael Ellerman wrote: >> Christian Zigotzky <chzigotzky@xenosoft.de> writes: >>> Kernel 5.5 PowerPC is also affected. >> I don't know what you mean by that. What sha are you talking about? >> >> I have a system with avahi running and everything's fine. >> >> # grep use- /etc/avahi/avahi-daemon.conf >> use-ipv4=yes >> use-ipv6=yes >> >> # systemctl status -l --no-pager avahi-daemon >> ● avahi-daemon.service - Avahi mDNS/DNS-SD Stack >> Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled) >> Active: active (running) since Thu 2020-02-06 14:55:34 AEDT; 38min ago >> Main PID: 1884 (avahi-daemon) >> Status: "avahi-daemon 0.7 starting up." >> CGroup: /system.slice/avahi-daemon.service >> ├─1884 avahi-daemon: running [mpe-ubuntu-le.local] >> └─1888 avahi-daemon: chroot helper >> >> Feb 06 14:55:34 mpe-ubuntu-le avahi-daemon[1884]: Registering new address record for fe80::5054:ff:fe66:2a19 on eth0.*. >> Feb 06 14:55:34 mpe-ubuntu-le avahi-daemon[1884]: Registering new address record for 10.61.141.81 on eth0.IPv4. >> Feb 06 14:55:34 mpe-ubuntu-le avahi-daemon[1884]: Registering new address record for ::1 on lo.*. >> Feb 06 14:55:34 mpe-ubuntu-le avahi-daemon[1884]: Registering new address record for 127.0.0.1 on lo.IPv4. >> Feb 06 14:55:34 mpe-ubuntu-le systemd[1]: Started Avahi mDNS/DNS-SD Stack. >> Feb 06 14:55:35 mpe-ubuntu-le avahi-daemon[1884]: Server startup complete. Host name is mpe-ubuntu-le.local. Local service cookie is 3972418141. >> Feb 06 14:55:38 mpe-ubuntu-le avahi-daemon[1884]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::5054:ff:fe66:2a19. >> Feb 06 14:55:38 mpe-ubuntu-le avahi-daemon[1884]: Joining mDNS multicast group on interface eth0.IPv6 with address fd69:d75f:b8b5:61:5054:ff:fe66:2a19. >> Feb 06 14:55:38 mpe-ubuntu-le avahi-daemon[1884]: Registering new address record for fd69:d75f:b8b5:61:5054:ff:fe66:2a19 on eth0.*. >> Feb 06 14:55:38 mpe-ubuntu-le avahi-daemon[1884]: Withdrawing address record for fe80::5054:ff:fe66:2a19 on eth0. >> >> # uname -r >> 5.5.0-gcc-8.2.0 >> >> >> The key question is what ioctl is it complaining about. You should be >> able to find that via strace. >> >> cheers >> > Hello Michael, > > Sorry it isn't true that the kernel 5.5 is also affected. A Power Mac G5 > user told me that but this isn't correct. I compiled and tested the > stable kernel 5.5.1 and 5.5.2 today and both kernels don't have the > issue with the avahi daemon. OK good to know. > Could you please also test the latest Git kernel? That's literally all I ever do. The problem here is you didn't tell me you were running a big endian distro, which uses compat mode. In hindsight I should have thought of that. Now that I know that, I can reproduce the bug: Feb 08 23:31:12 mpe-ubuntu-be avahi-daemon[24819]: ioctl(): Inappropriate ioctl for device Feb 08 23:31:12 mpe-ubuntu-be avahi-daemon[24819]: ioctl(): Inappropriate ioctl for device Feb 08 23:31:12 mpe-ubuntu-be avahi-daemon[24819]: ioctl(): Inappropriate ioctl for device Feb 08 23:31:12 mpe-ubuntu-be avahi-daemon[24819]: ioctl(): Inappropriate ioctl for device But it seems you've already identified the problem commit, thanks for bisecting. I'm sure Arnd will be able to fix it now that you've identified the problematic commit. cheers > strace /usr/sbin/avahi-daemon > > ... > poll([{fd=4, events=POLLIN}, {fd=16, events=POLLIN}, {fd=15, > events=POLLIN}, {fd=14, events=POLLIN}, {fd=13, events=POLLIN}, {fd=12, > events=POLLIN}, {fd=11, events=POLLIN}, {fd=10, events=POLLIN}, {fd=9, > events=POLLIN}, {fd=8, events=POLLIN}, {fd=6, events=POLLIN}], 11, 65) = > 2 ([{fd=12, revents=POLLIN}, {fd=9, revents=POLLIN}]) > ioctl(12, FIONREAD, 0xffba6f24) = -1 ENOTTY (Inappropriate ioctl > for device) > write(2, "ioctl(): Inappropriate ioctl for"..., 39ioctl(): Inappropriate > ioctl for device) = 39 > write(2, "\n", 1 > ) = 1 > ... > > Thanks, > Christian
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <mpe@ellerman.id.au> To: Christian Zigotzky <chzigotzky@xenosoft.de>, Jakub Kicinski <kuba@kernel.org> Cc: DTML <devicetree@vger.kernel.org>, Darren Stevens <darren@stevens-zone.net>, mad skateman <madskateman@gmail.com>, "netdev@vger.kernel.org" <netdev@vger.kernel.org>, 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> Subject: Re: Latest Git kernel: avahi-daemon[2410]: ioctl(): Inappropriate ioctl for device Date: Sat, 08 Feb 2020 23:36:34 +1100 [thread overview] Message-ID: <87imkh1cj1.fsf@mpe.ellerman.id.au> (raw) In-Reply-To: <f438e4ed-7746-1d80-6d72-455281884a1e@xenosoft.de> Christian Zigotzky <chzigotzky@xenosoft.de> writes: > On 06 February 2020 at 05:35 am, Michael Ellerman wrote: >> Christian Zigotzky <chzigotzky@xenosoft.de> writes: >>> Kernel 5.5 PowerPC is also affected. >> I don't know what you mean by that. What sha are you talking about? >> >> I have a system with avahi running and everything's fine. >> >> # grep use- /etc/avahi/avahi-daemon.conf >> use-ipv4=yes >> use-ipv6=yes >> >> # systemctl status -l --no-pager avahi-daemon >> ● avahi-daemon.service - Avahi mDNS/DNS-SD Stack >> Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled) >> Active: active (running) since Thu 2020-02-06 14:55:34 AEDT; 38min ago >> Main PID: 1884 (avahi-daemon) >> Status: "avahi-daemon 0.7 starting up." >> CGroup: /system.slice/avahi-daemon.service >> ├─1884 avahi-daemon: running [mpe-ubuntu-le.local] >> └─1888 avahi-daemon: chroot helper >> >> Feb 06 14:55:34 mpe-ubuntu-le avahi-daemon[1884]: Registering new address record for fe80::5054:ff:fe66:2a19 on eth0.*. >> Feb 06 14:55:34 mpe-ubuntu-le avahi-daemon[1884]: Registering new address record for 10.61.141.81 on eth0.IPv4. >> Feb 06 14:55:34 mpe-ubuntu-le avahi-daemon[1884]: Registering new address record for ::1 on lo.*. >> Feb 06 14:55:34 mpe-ubuntu-le avahi-daemon[1884]: Registering new address record for 127.0.0.1 on lo.IPv4. >> Feb 06 14:55:34 mpe-ubuntu-le systemd[1]: Started Avahi mDNS/DNS-SD Stack. >> Feb 06 14:55:35 mpe-ubuntu-le avahi-daemon[1884]: Server startup complete. Host name is mpe-ubuntu-le.local. Local service cookie is 3972418141. >> Feb 06 14:55:38 mpe-ubuntu-le avahi-daemon[1884]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::5054:ff:fe66:2a19. >> Feb 06 14:55:38 mpe-ubuntu-le avahi-daemon[1884]: Joining mDNS multicast group on interface eth0.IPv6 with address fd69:d75f:b8b5:61:5054:ff:fe66:2a19. >> Feb 06 14:55:38 mpe-ubuntu-le avahi-daemon[1884]: Registering new address record for fd69:d75f:b8b5:61:5054:ff:fe66:2a19 on eth0.*. >> Feb 06 14:55:38 mpe-ubuntu-le avahi-daemon[1884]: Withdrawing address record for fe80::5054:ff:fe66:2a19 on eth0. >> >> # uname -r >> 5.5.0-gcc-8.2.0 >> >> >> The key question is what ioctl is it complaining about. You should be >> able to find that via strace. >> >> cheers >> > Hello Michael, > > Sorry it isn't true that the kernel 5.5 is also affected. A Power Mac G5 > user told me that but this isn't correct. I compiled and tested the > stable kernel 5.5.1 and 5.5.2 today and both kernels don't have the > issue with the avahi daemon. OK good to know. > Could you please also test the latest Git kernel? That's literally all I ever do. The problem here is you didn't tell me you were running a big endian distro, which uses compat mode. In hindsight I should have thought of that. Now that I know that, I can reproduce the bug: Feb 08 23:31:12 mpe-ubuntu-be avahi-daemon[24819]: ioctl(): Inappropriate ioctl for device Feb 08 23:31:12 mpe-ubuntu-be avahi-daemon[24819]: ioctl(): Inappropriate ioctl for device Feb 08 23:31:12 mpe-ubuntu-be avahi-daemon[24819]: ioctl(): Inappropriate ioctl for device Feb 08 23:31:12 mpe-ubuntu-be avahi-daemon[24819]: ioctl(): Inappropriate ioctl for device But it seems you've already identified the problem commit, thanks for bisecting. I'm sure Arnd will be able to fix it now that you've identified the problematic commit. cheers > strace /usr/sbin/avahi-daemon > > ... > poll([{fd=4, events=POLLIN}, {fd=16, events=POLLIN}, {fd=15, > events=POLLIN}, {fd=14, events=POLLIN}, {fd=13, events=POLLIN}, {fd=12, > events=POLLIN}, {fd=11, events=POLLIN}, {fd=10, events=POLLIN}, {fd=9, > events=POLLIN}, {fd=8, events=POLLIN}, {fd=6, events=POLLIN}], 11, 65) = > 2 ([{fd=12, revents=POLLIN}, {fd=9, revents=POLLIN}]) > ioctl(12, FIONREAD, 0xffba6f24) = -1 ENOTTY (Inappropriate ioctl > for device) > write(2, "ioctl(): Inappropriate ioctl for"..., 39ioctl(): Inappropriate > ioctl for device) = 39 > write(2, "\n", 1 > ) = 1 > ... > > Thanks, > Christian
next prev parent reply other threads:[~2020-02-08 12:36 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 [this message] 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 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=87imkh1cj1.fsf@mpe.ellerman.id.au \ --to=mpe@ellerman.id.au \ --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=kuba@kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linuxppc-dev@ozlabs.org \ --cc=madskateman@gmail.com \ --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: linkBe 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.