All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Bruno Dantas <dantas@airpost.net>
Cc: James Prestwood <prestwoj@gmail.com>, iwd@lists.linux.dev
Subject: Re: iwd release 1.30 onwards cannot find available networks
Date: Mon, 12 Dec 2022 19:39:51 +0100	[thread overview]
Message-ID: <1573eff1-c74a-ec1f-9e75-5ce74f77d068@molgen.mpg.de> (raw)
In-Reply-To: <126d2f2b-07ef-fd22-7656-dcd21f3cece0@airpost.net>

Dear Bruno,


Am 12.12.22 um 18:52 schrieb Bruno Dantas:

>> Thanks for taking initiative and bisecting. But its puzzling how
>> this commit could have any effect. The only functional change is
>> removing a pending request when the wiphy goes down, so not related
>> to anything while the device is up/scanning.
> 
> It was my first git bisect, so it is certainly possible that I made a
> mistake. Regardless, the regression definitely appeared in release
> 1.30 and I excluded a regression in ell.

Does reverting the found commit on top of master fix the regression?

     git revert dfcba7c83c60f1a99ecf6f1424e97bf89fcab38e

>> Just to be clear, you are making sure IWD scans prior to calling
>> 'get- networks' right? i.e. station wlan0 scan?
> 
> Yes, but the scan just hangs. I wait a full minute before
> interrupting the scan with Ctrl+c.
> 
>> But assuming IWD is scanning (or trying) we need to see some debug
>> logs for IWD, and best if you could also get an iwmon trace when
>> IWD starts up and issues scans, and when you call get-networks.
>> More info how to do that here:
> 
> No problem. When using latest iwd 2.0, then letting it scan for a
> minute before interrupting, then running get-networks, here is the
> iwmon trace: https://pastebin.com/h7gHrS2w

(I’d prefer, if you attached the output.)

> And "iwd -d" output: https://pastebin.com/2y5hHfWa
> 
> I don't see Alvin's patch in the git commit history yet. Once it's
> been committed, I can recompile iwd 2.0 and test it.

You can save Alvin’s message (Ctrl + s in Mozilla Thunderbird) and apply 
to your git archive with `git am path/to/message` or, as it is a revert, 
just execute:

     git revert 6051a1495227bbe7ba357f6995d4dbe4a4862331

> Please let me know what you think of the iwmon and iwd debug output.

Thank you for helping to debug this.


Kind regards,

Paul

  reply	other threads:[~2022-12-12 18:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-12 16:54 iwd release 1.30 onwards cannot find available networks Bruno Dantas
2022-12-12 17:22 ` James Prestwood
2022-12-12 17:52   ` Bruno Dantas
2022-12-12 18:39     ` Paul Menzel [this message]
2022-12-12 18:58       ` Bruno Dantas
2022-12-12 19:01     ` Denis Kenzior
2022-12-12 19:27       ` Bruno Dantas
2022-12-12 19:38         ` Alvin Šipraga
2022-12-12 20:07           ` Bruno Dantas
2022-12-13 14:42           ` Bruno Dantas
2022-12-13 17:23             ` James Prestwood
2022-12-13 20:15               ` Bruno Dantas
2022-12-13 20:33                 ` James Prestwood
2022-12-13 21:02                   ` Bruno Dantas
2022-12-12 22:00         ` Denis Kenzior
2022-12-12 23:31           ` Bruno Dantas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1573eff1-c74a-ec1f-9e75-5ce74f77d068@molgen.mpg.de \
    --to=pmenzel@molgen.mpg.de \
    --cc=dantas@airpost.net \
    --cc=iwd@lists.linux.dev \
    --cc=prestwoj@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.