From: Naresh Kamboju <naresh.kamboju@linaro.org>
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 15:01:55 +0530 [thread overview]
Message-ID: <CA+G9fYvOrBPW-8pEDayhNaT1J6g1c4z-_zO3V+G1K5xAMb-T3w@mail.gmail.com> (raw)
In-Reply-To: <1277217234.9839643.1572476520526.JavaMail.zimbra@redhat.com>
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
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
next prev parent reply other threads:[~2019-10-31 9:31 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 [this message]
2019-10-31 9:45 ` Jan Stancek
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=CA+G9fYvOrBPW-8pEDayhNaT1J6g1c4z-_zO3V+G1K5xAMb-T3w@mail.gmail.com \
--to=naresh.kamboju@linaro.org \
--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.