[PATCH v2 12/12] tests: P2PS channel handling

[Peer, Ilan]

> -----Original Message-----
> From: hostap-bounces at lists.shmoo.com [mailto:hostap-
> bounces at lists.shmoo.com] On Behalf Of Peer, Ilan
> Sent: Monday, October 12, 2015 16:35
> To: Jouni Malinen
> Cc: hostap at lists.shmoo.com
> Subject: RE: [PATCH v2 12/12] tests: P2PS channel handling
> 
> 
> 
> > -----Original Message-----
> > From: Jouni Malinen [mailto:j at w1.fi]
> > Sent: Sunday, October 11, 2015 19:16
> > To: Peer, Ilan
> > Cc: hostap at lists.shmoo.com
> > Subject: Re: [PATCH v2 12/12] tests: P2PS channel handling
> >
> > On Thu, Oct 08, 2015 at 12:36:07PM +0300, Ilan Peer wrote:
> > > Add tests to verify proper handling of channel considerations in
> > > P2PS PD.
> >
> > > diff --git a/tests/hwsim/test_p2ps.py b/tests/hwsim/test_p2ps.py
> >
> > > +def test_p2ps_channel_both_connected_same(dev, apdev):
> > > +    """P2PS connection with P2PS method - stations connected on
> > > +same
> > channel"""
> >
> > This fails for me every time even when run as a single test case with
> > vm- run.sh. This is with unmodified test scripts and configuration.
> > The failure is
> > "Exception: P2P-GROUP-STARTED timeout on 02:00:00:00:00:00".
> > It looks like dev[0] has some strange issues with scan when trying to
> > join the group. This happens when processing the "P2P_CONNECT
> > 42:00:00:00:01:00 12345670 p2ps persistent join" command. This sends a
> > scan triger to the driver and that command seems to succeed and there
> > is even a scan trigger event indicating that the scan started.
> > However, the test script times out after ten seconds of not having seen scan
> results.
> >
> 
> I thought that I've eliminated this when using the same frequency for the
> listen channel and operating frequency (got clean results on 2 different
> setups and VM). I'll try to have another look at this in mac80211_hwsim.
> 

FWIW, I was not able to reproduce the 10 seconds timeout. Scanning on all the channels
while associated takes around 5.5 seconds, as mac80211 toggles between the
operating channel (dwell for 200 msec) and the scan channels. Even when stressing
the system (using the 'stress' utility) the worst scan time I got was less than 6 seconds. 

Regards,

Ilan.