Subject=Re: Re: dbus_p2p_discovery sometimes fails

[Vasyl Vavrychuk]

Maybe the reason of test fail is following. It is illustrated by the logs:

[   66.888443] ieee80211 phy1: mac80211_hwsim_config (freq=2462(2462 -
0)/noht idle=0 ps=0 smps=static)
...
[   67.776312] ieee80211 phy0: mac80211_hwsim_config (freq=2462(2462 -
0)/noht idle=0 ps=0 smps=static)
[   67.840486] ieee80211 phy0: mac80211_hwsim_tx, probe request
02:00:00:00:00:00 -> ff:ff:ff:ff:ff:ff
[   67.848227] ieee80211 phy1: ieee80211_tasklet_handler, IEEE80211_RX_MSG
[   67.896994] ieee80211 phy0: mac80211_hwsim_config (freq=2412(2412 -
0)/noht idle=0 ps=0 smps=static)
[   68.152654] ieee80211 phy1: mac80211_hwsim_tx, probe response
02:00:00:00:01:00 -> 02:00:00:00:00:00
[   68.152677] ieee80211 phy1: mac80211_hwsim_tx, probe response ack = 0

There phy0 is doing p2p_find and phy1 is doing p2p_listen. It seems
that machine where test runs is too slow and phy0 just switches to the
next frequency before receiving probe response from phy1.
This issue is reproducible when I run dbus_p2p_discovery in virtual
machine using additional vm-run.sh. So it is slow. Do you think it is
fair explanation?