Received: by 2002:a25:1506:0:0:0:0:0 with SMTP id 6csp1397279ybv; Thu, 6 Feb 2020 03:22:24 -0800 (PST) X-Google-Smtp-Source: APXvYqzTQSwwmKaDp14KhKKfLv/6XeRgIdoun6zlEs8WARNydNK8pcuIsozGUS+ik7UDEj1GkP7H X-Received: by 2002:a9d:6e98:: with SMTP id a24mr29038207otr.53.1580988144561; Thu, 06 Feb 2020 03:22:24 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1580988144; cv=none; d=google.com; s=arc-20160816; b=rvKamK0h2VLxHZupAWSWehw9A+1/R+gYW0a7fKvEo9cRz4ilhB3G/OZ+U0n5gcJgBh GEKR222z5B2hUDTXA9FzB6xPxlFmwYROAb0MRm0NwkOtULHKBSrskXIQqFCXwsp7atuM yCdcabl01SjAmeZFhjru87PVMDlNN1nKnz/p9Z7UqcfD/L4G1i9RrEm7fFNriHNpw+tA GRXsmzQ3a4ZpBBTOTC2ekB696NGqTXTTbCNEYpdnMnODVmNTZxHJlSgSeFgCSCOeE3jt xEraufffgBFy6xh48Hb39ucbmTR68Nx+Fl2xULNNuMtQJhNSPuAK7Bo6Hn57YWWvJZ9q qPGA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature; bh=NfptxjaStYrkEGbe/gRNZpHFhG9VdM3zlMBB+L7NlbA=; b=KM4gBm45FGduA8giVFylv8QAk++JAXqNrYUMML40QtLKEJEWgdvNEGf3T82RPEsdyX jg1rymogRrd4nPjIviIruWt4FHrvEXqZO6iLPfvCLGrXAGY9Zjily2+IjiEP48YR0SCo a2PGK4F4Oys2Pl3qUV6tizifSDlrNRePKJn+CorD1onxtMsFdDTfo/uocppggUNA/nkP 6vxrP7FNyk8lkThnlki9Bl0bcLkaEVG8/zsW9lo6UNKLFi8tnOL9eQpZlIhCwMfLVS8t XJvAbcObHYmAAYUHCPtX+nRAZ3IC/uBfbxGPfaKry/iK/9KR1u0bSj3HV3W3ZiW8cc3R RAMA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=aK8mQQ7N; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d2si1641416ote.9.2020.02.06.03.22.06; Thu, 06 Feb 2020 03:22:24 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=aK8mQQ7N; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727502AbgBFLIR (ORCPT + 99 others); Thu, 6 Feb 2020 06:08:17 -0500 Received: from mail-io1-f52.google.com ([209.85.166.52]:40365 "EHLO mail-io1-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727473AbgBFLIR (ORCPT ); Thu, 6 Feb 2020 06:08:17 -0500 Received: by mail-io1-f52.google.com with SMTP id x1so5838232iop.7 for ; Thu, 06 Feb 2020 03:08:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=NfptxjaStYrkEGbe/gRNZpHFhG9VdM3zlMBB+L7NlbA=; b=aK8mQQ7N+LiJWLXTB/ZA59FCckRgTP4BbvZu4evNDbQGA17KBO0giVjoWUVliHUT5a O5uNgGcZoAmN3Se46pbzkLoSp8yRcSnENkHIbIznwlciVY1pvnXn2aYqbUXiSOUfF4OH nPQJCjFU/GNbYH1LK8TUC10J2a58HP19eYb1H2M5Qpt2urrLiqgcRKfpYxrcDyV0RmSg eT/9P0kG2JMkkAORDyNRw6ecST2VzertnOcf/iUYAnuULIDTvgUbIS1QKuMjhSW81a63 2QojjiwkfJMvHhnzCfRwY5M2IOXsFVT53nBz9geMZA0pt8JDMTixpiiXPHvXfQs8LzT9 yrvA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=NfptxjaStYrkEGbe/gRNZpHFhG9VdM3zlMBB+L7NlbA=; b=rOlRNnIBy0flKWqcqB+4CwZDKsgzIVZ7zLMZvsKRDDOkAA1GfFNCiQHtSsF/4xsqR8 K3GUHuyyXmBB+k2vH/aiShpgZMF6++aDRtVlxW85ysgnRorVXN+xWCQIC95sINpLaCqA 5ykL7qXWaaz22lprE26DlCXb1nnEZXdmgxwxFlGj2XeeYiZ3DhET3P0bb350zrofsTDS 6DK3LlgrSiRjYhDH01tD2F9sEjoP3VVmxrPRpT3Af1FJWOBq0QarXDVkyap5ezHfCk5b dzwPtSZUcyjcS8MWnwKL5doZkKQjwkZ9MFlJau/r1QaOnBQBzH42n6igfR3Khy1oqZG2 5MHg== X-Gm-Message-State: APjAAAVTbSdDIFciLiAZ1mELw/q/w6/2pdKBJ+0swbP3cNJl40VNQDL+ 4Eicl7XqHmZWvi7f5SS125jRrT+BzWbMg5CHBOC6inwo17w= X-Received: by 2002:a02:6055:: with SMTP id d21mr34700826jaf.21.1580987296827; Thu, 06 Feb 2020 03:08:16 -0800 (PST) MIME-Version: 1.0 Received: by 2002:ad5:5d0d:0:0:0:0:0 with HTTP; Thu, 6 Feb 2020 03:08:16 -0800 (PST) In-Reply-To: <20200204081435.zhzqtsnrcgkzhpdw@beryllium.lan> References: <20200204081435.zhzqtsnrcgkzhpdw@beryllium.lan> From: JH Date: Thu, 6 Feb 2020 22:08:16 +1100 Message-ID: Subject: Re: Failed to can wifi Invalid Sched_scan parameters To: Daniel Wagner Cc: linux-wireless , connman Content-Type: text/plain; charset="UTF-8" Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org Hi Daniel, On 2/4/20, Daniel Wagner wrote: > The 'Invalid Sched_scan parameters' indicates, wpa_supplicant is > providing the wrong parameters. Best thing is to monitor between > wpa_supplicant and kernel the netlink messages. iwmon is an excellent > tool for this. Thanks for the tip, I did not realize that connman is actually heavily relied on wpa_supplicant, if I restarted wpa_supplicant, most of time it popped up mwifiex_sdio messages, then the WiFi could be up: $ systemctl restart wpa_supplicant [ 371.617417] mwifiex_sdio mmc0:0001:1: info: 2 [ 371.647545] mwifiex_sdio mmc0:0001:1: info: associated to bssid 34:08:04:12:y [ 371.726667] IPv6: ADDRCONF(NETDEV_CHANGE): mlan0: link becomes ready [ 371.772758] mwifiex_sdio mmc0:0001:1: CMD_RESP: cmd 0x23f error, result=0x2 But sometime when I restated wpa_supplicant, that message did not come, the WiFi network was still down. How is mwifiex_sdio related to wpa_supplicant? Why it is nondeterministic, sometime restart wpa_supplicant could bring mwifiex_sdio and WiFi up, something it couldn't? I think mwifiex_sdio is the lowest layer to interact to WiFi modem, in which circumstance it could bring WiFi modem up and in which circumstance it couldn't? That is far too unstable, I always thought I could rely on connman for WiFi connection stability, but it seems that beyond connman capacity, so what I can do when the WiFi is not up when restart wpa_supplicant could not fix it? Thank you very much Daniel. Kind regards, - jh