Hi Denis,

> iwd doesn't do anything on sleep (it isn't even aware of sleep).  So it is
> up to the kernel driver to do the right thing.  Maybe it isn't?  You'll
> have to ask the kernel / driver / firmware people for your hardware.
thanks a lot for the answer. I'll contact the kernel / driver / firmware people
for my hardware.

> Some network managers (like NM) will explicitly IFDOWN wireless interfaces
> on suspend and bring them up on resume.  This isn't cost free and we'd
> rather not do this.
Would it make sense to do this optionally if a new config option were
explicitly set? Or do you think this is the wrong layer or wrong approach to
do so?

> You can also try to run run iwmon in order to capture what is happening on
> the nl80211 API level when entering / leaving suspend.  The driver people
> might be interested in this information.
I was monitoring with iwmon for the last days whenever the computer was in
use, but so far the problem did not occur again (it occurs during normal
operation, I just have the feeling that the probability is highest some
minutes after waking up from suspend).

The only thing I got was a segfault from iwmon once, so it's now running with
valgrind. This is, however, probably an unrelated issue, if it should repeat
at all.

Thanks again
Patrick