* [LTP] LTP: accept02: BROK: accept02.c:52: setsockopt(6, 0, 42, 0xffff9c56df78, 136) failed: ENODEV (19)
@ 2019-10-30 6:17 Naresh Kamboju
2019-10-30 23:02 ` Jan Stancek
0 siblings, 1 reply; 4+ messages in thread
From: Naresh Kamboju @ 2019-10-30 6:17 UTC (permalink / raw)
To: ltp
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 ?
hikey arm64 output log,
tst_test.c:1118: INFO: Timeout per run is 0h 15m 00s
tst_buffers.c:55: INFO: Test is using guarded buffers
accept02.c:127: INFO: Starting listener on port: 35903
safe_net.c:186: BROK: accept02.c:52: setsockopt(6, 0, 42,
0xffff9c56df78, 136) failed: ENODEV (19)
qemu_x86_64 output log,
tst_test.c:1118: INFO: Timeout per run is 0h 15m 00s
tst_buffers.c:55: INFO: Test is using guarded buffers
accept02.c:127: INFO: Starting listener on port: 47245
safe_net.c:186: BROK: accept02.c:52: setsockopt(6, 0, 42,
0x7f5397ca3f78, 136) failed: ENODEV (19)
Test results comparison,
https://qa-reports.linaro.org/lkft/linux-mainline-oe/tests/ltp-syscalls-tests/accept02
Full test log,
https://lkft.validation.linaro.org/scheduler/job/976363
https://lkft.validation.linaro.org/scheduler/job/977681
Best regards
Naresh Kamboju
^ permalink raw reply [flat|nested] 4+ messages in thread
* [LTP] LTP: accept02: BROK: accept02.c:52: setsockopt(6, 0, 42, 0xffff9c56df78, 136) failed: ENODEV (19)
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
0 siblings, 1 reply; 4+ messages in thread
From: Jan Stancek @ 2019-10-30 23:02 UTC (permalink / raw)
To: ltp
----- 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
>
> hikey arm64 output log,
>
> tst_test.c:1118: INFO: Timeout per run is 0h 15m 00s
> tst_buffers.c:55: INFO: Test is using guarded buffers
> accept02.c:127: INFO: Starting listener on port: 35903
> safe_net.c:186: BROK: accept02.c:52: setsockopt(6, 0, 42,
> 0xffff9c56df78, 136) failed: ENODEV (19)
>
> qemu_x86_64 output log,
>
> tst_test.c:1118: INFO: Timeout per run is 0h 15m 00s
> tst_buffers.c:55: INFO: Test is using guarded buffers
> accept02.c:127: INFO: Starting listener on port: 47245
> safe_net.c:186: BROK: accept02.c:52: setsockopt(6, 0, 42,
> 0x7f5397ca3f78, 136) failed: ENODEV (19)
>
> Test results comparison,
> https://qa-reports.linaro.org/lkft/linux-mainline-oe/tests/ltp-syscalls-tests/accept02
>
> Full test log,
> https://lkft.validation.linaro.org/scheduler/job/976363
> https://lkft.validation.linaro.org/scheduler/job/977681
>
> Best regards
> Naresh Kamboju
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* [LTP] LTP: accept02: BROK: accept02.c:52: setsockopt(6, 0, 42, 0xffff9c56df78, 136) failed: ENODEV (19)
2019-10-30 23:02 ` Jan Stancek
@ 2019-10-31 9:31 ` Naresh Kamboju
2019-10-31 9:45 ` Jan Stancek
0 siblings, 1 reply; 4+ messages in thread
From: Naresh Kamboju @ 2019-10-31 9:31 UTC (permalink / raw)
To: ltp
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* [LTP] LTP: accept02: BROK: accept02.c:52: setsockopt(6, 0, 42, 0xffff9c56df78, 136) failed: ENODEV (19)
2019-10-31 9:31 ` Naresh Kamboju
@ 2019-10-31 9:45 ` Jan Stancek
0 siblings, 0 replies; 4+ messages in thread
From: Jan Stancek @ 2019-10-31 9:45 UTC (permalink / raw)
To: ltp
----- 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
>
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2019-10-31 9:45 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox