[lab-baylibre][dra7xx-evm] network instabilities

Fixed

Activity

Show:

Kevin Hilman 
November 19, 2018 at 5:39 PM

So, IIUC, the systemd test will fail if both network interfaces are connected to the same LAN?

And, the disconnecting the 2nd interface makes things work again?

If that's the case, then this is now fixed in lab-baylibre and this can be closed.

 

 

Corentin Labbe 
November 15, 2018 at 11:26 AM

I didnt saw that the mmc problem was on your DUT. Anyway the data have disappear so I cannot rerun the same job.

How did you generated it ?

Corentin Labbe 
November 15, 2018 at 8:51 AM

The problem seems related to our lab, I have resubmited the same job on both dra7 and only our dra7 do this.

I have unwired eth1 and the problem disapear.

BUT we have another problem with the mmc https://lava.automotivelinux.org/scheduler/job/1235

 

Jan-Simon Moeller 
November 14, 2018 at 1:49 PM

Well ...

https://lava.automotivelinux.org/scheduler/job/1151

also.

I'm not saying its the wire right now.

We might trigger this due to a ptest running:

[ 104.122000] audit: type=1701 audit(1542028091.089:6): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=System pid=2798 comm=\"test-path-util\" exe=\"/usr/lib/systemd/ptest/tests/test-path-util\" sig=6

Looks like the systemd ptest triggers the network to go flakey.

{{}}

Can you try that manually ? Aka boot an image with ptest enabled, then run the systemd ptest manually

{{}}

{{}}

ptest-runner systemd  should be the command.

 

Corentin Labbe 
November 14, 2018 at 1:22 PM

i have verified that both interface are well wired.

The problem seems only on eth1 and happen only on one job.

Could you resend it ? (I dont know if I have the right to do so)

 

Details

Assignee

Reporter

Labels

Contract ID

Priority

Created November 12, 2018 at 9:42 PM
Updated January 23, 2019 at 3:31 AM
Resolved December 17, 2018 at 3:55 PM