From: "Ryll, Jan (GED-SDD2)" <Jan.Ryll@bshg.com>
To: JH <jupiter.hce@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
connman <connman@lists.01.org>
Subject: RE: Strange inconsistant WiFi network behaviour
Date: Wed, 29 Jan 2020 10:40:28 +0000 [thread overview]
Message-ID: <c76ff8bb50164eeb86feeb2eba76beac@bshg.com> (raw)
In-Reply-To: <CAA=hcWTEnYraPy5Un7a7ryeDBJmf0KoCU2VoJjr5LJWtbc9j_g@mail.gmail.com>
Hi,
there are WiFi routers like AVM which are implement the WiFi Stack in a stricter way than other routers or other WiFi chips-firmware.
I mention this cause weh ad some issue with a cypress wifi firmware which leads to "sometimes" disconnect from routers. And we figured out that this was mostly the case with AVM. We are in contact with AVM in it turns out that the AVM router work proberly. The issues was with the cypress chipset firmware. Now we are in contact with cypress and they accepted the issue.
So it is not always a connman problem :-) .
Best regards
Jan
-----Original Message-----
From: JH <jupiter.hce@gmail.com>
Sent: Wednesday, January 29, 2020 10:22 AM
To: linux-wireless <linux-wireless@vger.kernel.org>; connman <connman@lists.01.org>
Subject: Strange inconsistant WiFi network behaviour
Hi,
I have 2 iMX6 devices running uBlox Lily WiFi, mrvl firmware sd8801_uapsta.bin in kernel 4.19.75. In my office, a WiFi router is just 1 meter away, the WiFi signal should not be a problem. One device could connect to the WiFi router well and stably, one could not, here were error messages:
[ 408.990029] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameters
.....................
[56.986414] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start :
Invalid Sched_scan parameter
connmand[13469]:
../connman-1.35/src/service.c:preferred_tech_add_by_type() type 5 service 0x119120 Telstra
connmand[13469]: ../connman-1.35/src/service.c:auto_connect_service()
preferred 1 sessions 0 reason auto
connmand[13469]: ../connman-1.35/src/ntp.c:send_timeout() send timeout
2 (retries 0)
connmand[13469]:
../connman-1.35/plugins/ofono.c:netreg_update_strength() /ubloxqmi_2 Strength 80
connmand[13469]: ../connman-1.35/src/ntp.c:send_timeout() send timeout
4 (retries 1)
connmand[13469]: ../connman-1.35/plugins/wifi.c:throw_wifi_scan()
device 0x118da8 0x116c78
connmand[13469]:
../connman-1.35/src/device.c:connman_device_ref_debug() 0x118da8 ref 4 by ../connman-1.35/plugins/wifi.c:1214:throw_wifi_scan()
connmand[13469]:
../connman-1.35/src/device.c:connman_device_set_scanning() device
0x118da8 scanning 1
connmand[13469]:
../connman-1.35/src/technology.c:__connman_technology_scan_started()
device 0x118da8
connmand[13469]: ../connman-1.35/plugins/wifi.c:autoscan_timeout() interval 27
connmand[13469]: ../connman-1.35/plugins/wifi.c:interface_state() wifi
0x11a7c8 interface state 4
connmand[13469]: ../connman-1.35/plugins/wifi.c:scan_started()
connmand[13469]: ../connman-1.35/src/rtnl.c:rtnl_message() NEWLINK len
56 type 16 flags 0x0000 seq 0 pid 0
connmand[13469]: ../connman-1.35/plugins/wifi.c:scan_finished()
connmand[13469]: ../connman-1.35/plugins/wifi.c:interface_state() wifi
0x11a7c8 interface state 3
Both devices were installed the same firmware and software, if it was firmware / software issues, both would not be able to connect to WiFi, as one device could connect to the office WiFi router well, it could not the WiFi router problem either.
If I move the faulty one to my home, it could connect to my home WiFi, so the device does not have WiFi problem, that is really confusing, what could cause that kind problem and how to debug and fix it?
Thank you.
Kind regards,
- jh
_______________________________________________
connman mailing list -- connman@lists.01.org To unsubscribe send an email to connman-leave@lists.01.org
next prev parent reply other threads:[~2020-01-29 10:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 9:21 Strange inconsistant WiFi network behaviour JH
2020-01-29 9:27 ` Emil Petersky
2020-01-29 10:40 ` Ryll, Jan (GED-SDD2) [this message]
2020-01-30 0:04 ` JH
2020-01-30 1:33 ` JH
2020-01-30 8:28 ` Emil Petersky
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=c76ff8bb50164eeb86feeb2eba76beac@bshg.com \
--to=jan.ryll@bshg.com \
--cc=connman@lists.01.org \
--cc=jupiter.hce@gmail.com \
--cc=linux-wireless@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).