From mboxrd@z Thu Jan  1 00:00:00 1970
Content-Type: multipart/mixed; boundary="===============8085947219343223105=="
MIME-Version: 1.0
From: 1148d778-20a8-4ab0-96b7-24572ddab965 at simplelogin.co
To: iwd at lists.01.org
Subject: Re: iwd fails to create device
Date: Tue, 31 May 2022 18:39:51 +0000
Message-ID: <20220531183951.2010.25659@ml01.vlan13.01.org>
In-Reply-To: fcf4e3fa19e68156e95e379fafe59a0929c32a76.camel@gmail.com

--===============8085947219343223105==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

> It would be great if you could get some iwmon logs when this happens.
> Hopefully it happens frequent enough you can get a capture. More info
> about how to do that can be found here:
> =

> https://iwd.wiki.kernel.org/debugging

Sure, but it doesn't happen very frequently. I'm not sure about how to appr=
oach debugging for this, should I try to restart iwd when it happens? Maybe=
 doing this the issue is not triggered. Having iwmon logging all time seems=
 a bit too much, no?

I could try to reproduce it somehow because it's mostly after a reboot when=
 it happens.
--===============8085947219343223105==--