From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] LTP: accept02: BROK: accept02.c:52: setsockopt(6, 0, 42, 0xffff9c56df78, 136) failed: ENODEV (19)
Date: Thu, 31 Oct 2019 05:45:10 -0400 (EDT) [thread overview]
Message-ID: <2064120052.9903608.1572515110815.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CA+G9fYvOrBPW-8pEDayhNaT1J6g1c4z-_zO3V+G1K5xAMb-T3w@mail.gmail.com>
----- Original Message -----
> Hi Jan,
>
> On Thu, 31 Oct 2019 at 04:32, Jan Stancek <jstancek@redhat.com> wrote:
> >
> >
> >
> > ----- Original Message -----
> > > LTP syscall accept02 test failed intermittently on hikey arm64 device,
> > > qemu_x86_64 and qemu_i386.
> > >
> > > Do you see this intermittent failure at your end ?
> >
> > I'm not. What does the network look like on these systems?
> > Is there a default route? Is 224.0.0.0 reachable?
> >
> > Can you check with?
> >
> > # ip route
> > # ip route get 224.0.0.0
>
> on qemu_x86_64,
>
> + ip route
> + ip route get 224.0.0.0
> RTNETLINK answers: Network is unreachable
That looks like one plausible explanation. I get same failure when I drop default gw:
# uname -r
5.4.0-rc5
# ./accept02
tst_test.c:1118: INFO: Timeout per run is 0h 05m 00s
tst_buffers.c:55: INFO: Test is using guarded buffers
accept02.c:127: INFO: Starting listener on port: 41919
accept02.c:71: PASS: Multicast group was not copied: EADDRNOTAVAIL (99)
# ip r del default via ...
# ./accept02
tst_test.c:1118: INFO: Timeout per run is 0h 05m 00s
tst_buffers.c:55: INFO: Test is using guarded buffers
accept02.c:127: INFO: Starting listener on port: 36517
safe_net.c:186: BROK: accept02.c:52: setsockopt(3, 0, 42, 0x7f1d25aebf78, 136) failed: ENODEV (19)
Not sure why that would be intermittent though. Is it possible
that you sometimes start tests before network is up?
>
>
> on hickey device,
> + ip route
> default via 10.66.16.1 dev eth0 proto dhcp metric 100
> 10.66.16.0/23 dev eth0 proto kernel scope link src 10.66.16.28 metric 100
> + ip route get 224.0.0.0
> multicast 224.0.0.0 dev eth0 src 10.66.16.28 uid 0
> cache <mc>
>
> Link,
> https://lkft.validation.linaro.org/scheduler/job/987925#L609
>
> - Naresh
>
prev parent reply other threads:[~2019-10-31 9:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 6:17 [LTP] LTP: accept02: BROK: accept02.c:52: setsockopt(6, 0, 42, 0xffff9c56df78, 136) failed: ENODEV (19) Naresh Kamboju
2019-10-30 23:02 ` Jan Stancek
2019-10-31 9:31 ` Naresh Kamboju
2019-10-31 9:45 ` Jan Stancek [this message]
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=2064120052.9903608.1572515110815.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=ltp@lists.linux.it \
/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.