Send connman mailing list submissions to
connman@lists.01.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.01.org/mailman/listinfo/connman
or, via email, send a message with subject or body 'help' to
connman-requ...@lists.01.org
You can reach the person managing the list at
connman-ow...@lists.01.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of connman digest..."
Today's Topics:
1. Re: Error "wifi: No carrier" only to connman (Daniel Wagner)
2. Re: break instead of continue in
__connman_service_disconnect_all()? (Daniel Wagner)
3. Re: Error "wifi: No carrier" only to connman (Julien Massot)
4. Re: Error "wifi: No carrier" only to connman (Jun Nie)
5. Re: Error "wifi: No carrier" only to connman (Jun Nie)
6. Re: Error "wifi: No carrier" only to connman (Daniel Wagner)
7. Re: Error "wifi: No carrier" only to connman (Jun Nie)
----------------------------------------------------------------------
Message: 1
Date: Wed, 6 Mar 2019 09:49:01 +0100
From: Daniel Wagner <w...@monom.org>
To: Jun Nie <jun....@linaro.org>
Cc: connman@lists.01.org
Subject: Re: Error "wifi: No carrier" only to connman
Message-ID: <c1bb572e-7a8c-c9ed-d58d-365097e99...@monom.org>
Content-Type: text/plain; charset=utf-8
Hi Jun,
On 05.03.19 05:25, Jun Nie wrote:
> I always see this issue after board boot up. After disable/enable
> wifi, wait for several minutes, then disable/enable wifi, it works. It
> is not due to rfkill or kernel driver issue, because "iwlist wlan0
> scan" command works well after board boot up while connmanctl has
> issue. Does anyone happen to know this issue? The version is 1.36 with
> some patches at:
> https://github.com/openembedded/openembedded-core/tree/master/meta/recipes-connectivity/connman/connman
Usually such problems are hardware/driver related. It is a bit difficult
to say what is happening from your description. Could you provide the
log files (see README how to do it)?
One thing you could also try is to use a different WiFi interface if
possible, e.g. an USB WiFi dongle. Just for testing obviously :)
Thanks,
DAniel
------------------------------
Message: 2
Date: Wed, 6 Mar 2019 09:57:29 +0100
From: Daniel Wagner <w...@monom.org>
To: Henrik Persson <henrik.pers...@verisure.com>
Cc: "connman@lists.01.org" <connman@lists.01.org>
Subject: Re: break instead of continue in
__connman_service_disconnect_all()?
Message-ID: <d6034e52-a417-ff04-07e6-dac26afb0...@monom.org>
Content-Type: text/plain; charset=utf-8
Hi Henrik,
On 05.03.19 11:03, Henrik Persson wrote:
> Reading through the code trying to debug another issue I stumbled upon what I
> think is a bug
> in __connman_service_disconnect_all(). It doesn't seem to be used anywhere,
> but..still seems
> like the break in that for loop is not doing what you want it to do if you're
> supposed to disconnect
> all connected services.
>
> diff --git a/src/service.c b/src/service.c
> index f6fe81bf..ffaebcc3 100644
> --- a/src/service.c
> +++ b/src/service.c
> @@ -6536,7 +6536,7 @@ int __connman_service_disconnect_all(void)
> service = iter->data;
>
> if (!is_connected(service->state))
> - break;
> + continue;
>
> services = g_slist_prepend(services, service);
> }
The service list is sorted so that online/ready services are always at
the beginning of the list. If we see the first non online/ready service
we should be done with looking at the list. That's why we break out the
loop early.
Well, this is the precondition we count on. If it doesn't hold then we
have a bug somewhere else.
Thanks,
Daniel
------------------------------
Message: 3
Date: Wed, 6 Mar 2019 13:03:25 +0100
From: Julien Massot <jmas...@softbankrobotics.com>
To: Daniel Wagner <w...@monom.org>
Cc: Jun Nie <jun....@linaro.org>, connman <connman@lists.01.org>
Subject: Re: Error "wifi: No carrier" only to connman
Message-ID:
<CADGp=qe6ajn64jarlgzmnbjsjffjnkeejvyzbq_fhsqymdw...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Hi
> Usually such problems are hardware/driver related. It is a bit difficult
> to say what is happening from your description. Could you provide the
> log files (see README how to do it)?
>
> One thing you could also try is to use a different WiFi interface if
> possible, e.g. an USB WiFi dongle. Just for testing obviously :)
May also be a communication issue with wpa_supplicant.
Julien
--
*This email and any attachment thereto are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you are not the intended recipient, please be advised that disclosing,
copying, distributing or taking any action in reliance on the contents of
this email is strictly prohibited. In such case, please immediately advise
the sender, and delete all copies and attachment from your system.
This
email shall not be construed and is not tantamount to an offer, an
acceptance of offer, or an agreement by SoftBank Robotics Europe on any
discussion or contractual document whatsoever. No employee or agent is
authorized to represent or bind SoftBank Robotics Europe to third parties
by email, or act on behalf of SoftBank Robotics Europe by email, without
express written confirmation by SoftBank Robotics Europe? duly authorized
representatives.
*
*Ce message ?lectronique et ?ventuelles pi?ces
jointes sont confidentiels, et exclusivement destin?s ? la personne ou
l'entit? ? qui ils sont adress?s.
Si vous n'?tes pas le destinataire vis?,
vous ?tes pri? de ne pas divulguer, copier, distribuer ou prendre toute
d?cision sur la foi de ce message ?lectronique. Merci d'en aviser
imm?diatement l'exp?diteur et de supprimer toutes les copies et ?ventuelles
pi?ces jointes de votre syst?me.
Ce message ?lectronique n'?quivaut pas ?
une offre, ? une acceptation d?offre, ou ? un accord de SoftBank Robotics
Europe sur toute discussion ou document contractuel quel qu?il soit, et ne
peut ?tre interpr?t? comme tel. Aucun employ? ou agent de SoftBank Robotics
Europe n'est autoris? ? repr?senter ou ? engager la soci?t? par email, ou ?
agir au nom et pour le compte de la soci?t? par email, sans qu?une
confirmation ?crite soit donn?e par le repr?sentant l?gal de SoftBank
Robotics Europe ou par toute autre personne ayant re?u d?l?gation de
pouvoir appropri?e.
*
**
------------------------------
Message: 4
Date: Wed, 6 Mar 2019 21:36:10 +0800
From: Jun Nie <jun....@linaro.org>
To: Daniel Wagner <w...@monom.org>
Cc: connman@lists.01.org
Subject: Re: Error "wifi: No carrier" only to connman
Message-ID:
<CABymUCMYyvg3xgt4qiRnSVTJmWxvNSi=wxspxorc9bhzx6m...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Daniel Wagner <w...@monom.org> ?2019?3?6??? ??4:49???
>
> Hi Jun,
>
> On 05.03.19 05:25, Jun Nie wrote:
> > I always see this issue after board boot up. After disable/enable
> > wifi, wait for several minutes, then disable/enable wifi, it works. It
> > is not due to rfkill or kernel driver issue, because "iwlist wlan0
> > scan" command works well after board boot up while connmanctl has
> > issue. Does anyone happen to know this issue? The version is 1.36 with
> > some patches at:
> > https://github.com/openembedded/openembedded-core/tree/master/meta/recipes-connectivity/connman/connman
>
> Usually such problems are hardware/driver related. It is a bit difficult
> to say what is happening from your description. Could you provide the
> log files (see README how to do it)?
>
> One thing you could also try is to use a different WiFi interface if
> possible, e.g. an USB WiFi dongle. Just for testing obviously :)
I do not have USB WiFi dongle in hand, will try it later. For log,
you can find it here. I observe the line:
"__connman_device_request_scan() device 0x141b568 err -67", which is
ENOLINK error. But iwlist command works well when error appear. Do you
have any idea? Thank you in advance!
https://paste.ubuntu.com/p/948CCwnCpB/
>
> Thanks,
> DAniel
------------------------------
Message: 5
Date: Wed, 6 Mar 2019 21:37:14 +0800
From: Jun Nie <jun....@linaro.org>
To: Julien Massot <jmas...@softbankrobotics.com>
Cc: Daniel Wagner <w...@monom.org>, connman <connman@lists.01.org>
Subject: Re: Error "wifi: No carrier" only to connman
Message-ID:
<CABymUCNT7TBqoDGd=ph53obgt-gyqyqrvpaydnhtkkrty4n...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Julien Massot <jmas...@softbankrobotics.com> ?2019?3?6??? ??8:03???
>
> Hi
> > Usually such problems are hardware/driver related. It is a bit difficult
> > to say what is happening from your description. Could you provide the
> > log files (see README how to do it)?
> >
> > One thing you could also try is to use a different WiFi interface if
> > possible, e.g. an USB WiFi dongle. Just for testing obviously :)
>
> May also be a communication issue with wpa_supplicant.
How to validate whether it is due to wpa_supplicant communication?
>
> Julien
>
> --
>
>
> *This email and any attachment thereto are confidential and intended
> solely for the use of the individual or entity to whom they are addressed.
>
> If you are not the intended recipient, please be advised that disclosing,
> copying, distributing or taking any action in reliance on the contents of
> this email is strictly prohibited. In such case, please immediately advise
> the sender, and delete all copies and attachment from your system.
> This
> email shall not be construed and is not tantamount to an offer, an
> acceptance of offer, or an agreement by SoftBank Robotics Europe on any
> discussion or contractual document whatsoever. No employee or agent is
> authorized to represent or bind SoftBank Robotics Europe to third parties
> by email, or act on behalf of SoftBank Robotics Europe by email, without
> express written confirmation by SoftBank Robotics Europe? duly authorized
> representatives.
> *
>
>
>
> *Ce message ?lectronique et ?ventuelles pi?ces
> jointes sont confidentiels, et exclusivement destin?s ? la personne ou
> l'entit? ? qui ils sont adress?s.
> Si vous n'?tes pas le destinataire vis?,
> vous ?tes pri? de ne pas divulguer, copier, distribuer ou prendre toute
> d?cision sur la foi de ce message ?lectronique. Merci d'en aviser
> imm?diatement l'exp?diteur et de supprimer toutes les copies et ?ventuelles
> pi?ces jointes de votre syst?me.
> Ce message ?lectronique n'?quivaut pas ?
> une offre, ? une acceptation d?offre, ou ? un accord de SoftBank Robotics
> Europe sur toute discussion ou document contractuel quel qu?il soit, et ne
> peut ?tre interpr?t? comme tel. Aucun employ? ou agent de SoftBank Robotics
> Europe n'est autoris? ? repr?senter ou ? engager la soci?t? par email, ou ?
> agir au nom et pour le compte de la soci?t? par email, sans qu?une
> confirmation ?crite soit donn?e par le repr?sentant l?gal de SoftBank
> Robotics Europe ou par toute autre personne ayant re?u d?l?gation de
> pouvoir appropri?e.
> *
>
> **
------------------------------
Message: 6
Date: Wed, 6 Mar 2019 15:31:59 +0100
From: Daniel Wagner <w...@monom.org>
To: Jun Nie <jun....@linaro.org>
Cc: connman@lists.01.org
Subject: Re: Error "wifi: No carrier" only to connman
Message-ID: <35552507-a866-abe7-a75b-0bdd8c5a8...@monom.org>
Content-Type: text/plain; charset=utf-8
> I do not have USB WiFi dongle in hand, will try it later. For log,
> you can find it here. I observe the line:
> "__connman_device_request_scan() device 0x141b568 err -67", which is
> ENOLINK error. But iwlist command works well when error appear. Do you
> have any idea? Thank you in advance!
> https://paste.ubuntu.com/p/948CCwnCpB/
ENOLINK might indicate that the device is not powered:
static int device_scan(enum connman_service_type type,
struct connman_device *device,
bool force_full_scan)
{
struct connman_device_scan_params params;
if (!device->driver || !device->driver->scan)
return -EOPNOTSUPP;
if (!device->powered)
return -ENOLINK;
memset(¶ms, 0, sizeof(params));
params.type = type;
params.force_full_scan = force_full_scan;
return device->driver->scan(device, ¶ms);
}
Can you check what ConnMan thinks about the device status?
Thanks,
Daniel
------------------------------
Message: 7
Date: Wed, 6 Mar 2019 22:38:20 +0800
From: Jun Nie <jun....@linaro.org>
To: Daniel Wagner <w...@monom.org>
Cc: connman <connman@lists.01.org>
Subject: Re: Error "wifi: No carrier" only to connman
Message-ID:
<cabymucnrmo_aygw86b8mtsg2h+byaqqnzch283hn1ps9onj...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Daniel Wagner <w...@monom.org> ?2019?3?6??? ??10:32???
>
> > I do not have USB WiFi dongle in hand, will try it later. For log,
> > you can find it here. I observe the line:
> > "__connman_device_request_scan() device 0x141b568 err -67", which is
> > ENOLINK error. But iwlist command works well when error appear. Do you
> > have any idea? Thank you in advance!
> > https://paste.ubuntu.com/p/948CCwnCpB/
>
> ENOLINK might indicate that the device is not powered:
>
> static int device_scan(enum connman_service_type type,
> struct connman_device *device,
> bool force_full_scan)
> {
> struct connman_device_scan_params params;
>
> if (!device->driver || !device->driver->scan)
> return -EOPNOTSUPP;
>
> if (!device->powered)
> return -ENOLINK;
>
> memset(¶ms, 0, sizeof(params));
> params.type = type;
> params.force_full_scan = force_full_scan;
>
> return device->driver->scan(device, ¶ms);
> }
>
> Can you check what ConnMan thinks about the device status?
>
This is status from connman when iwlist still works well for wifi. It
seems no power issue, right?
root@mbed-linux-os-5224:~# connmanctl state
State = idle
OfflineMode = False
SessionMode = False
root@mbed-linux-os-5224:~# connmanctl scan wifi
Error /net/connman/technology/wifi: No carrier
I observed there is device_pending_reset() called after disable/enable
cycle before failure scan case, so I collect another round log to
check it. On boot up, I see device_pending_reset() after
disable/enable wifi. After several minutes, I run disable/enable cycle
again and scan works well and did not see this line anymore. Seems it
is power related logic issue, but not real power issue because iwlist
works. Full log is in past M6cdKZjCBF.
src/device.c:__connman_device_request_scan() device 0x1c9bb88 err -67
https://paste.ubuntu.com/p/M6cdKZjCBF/
> Thanks,
> Daniel
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
connman@lists.01.org
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 41, Issue 5
**************************************
