We have moved to a new Sailfish OS Forum. Please start new discussions there.
2

2.1.4.13 - WiFI goes "down" and 'ifconfig' in terminal hangs

asked 2018-02-23 13:55:29 +0300

ihjort gravatar image

updated 2018-02-23 14:01:58 +0300

Hello!

three times I have had to restart my Sony X because there is some problem with WLAN. I have used the phone with Sailfish X since GA and I haven't had any problems like this before the upgrade, and now three times in less than a week after upgrade.

Problem description:

After upgrade to 2.1.4.13 Sailfish X has intermitten WLAN problems that requires a reboot.

  • Error in "settings" -> "WLAN"

"Network is not available. Please restart device"

No errors seen in messages/dmesg

  • What fails

Traffic using WLAN

Can't use the WLAN shortcut to control WLAN

'ifconfig' in a terminal hangs, "ctrl-c" doesn't work

"settings" -> "Utilities" -> "restart network subsystem" takes a long time and says it worked but WLAN doesn't work.

  • What works Can start applications as normal

The phone is not getting warm

SMS/Phone works

Extra information:

A restart of the device is needed and I have to use the Power button + Volume up at the same time to boot it again.

Note: The led goes RED when I power it off

Is this a new or known problem ?

edit retag flag offensive close delete

Comments

Hi.

Do you know if you're using a special configuration ? Also, when you talk about messages/dmesg do you mean journalctl?

Regards.

Pasko ( 2018-02-24 22:24:38 +0300 )edit

Hello,

I haven't changed anything in my network or configuration prior to the first error. I use a mesh network, (Deco M5 TP-link, ver 1.4.15), and since installation early January I haven't had any issues prior to the upgrade.

No special settings at all on Jolla or TP-link side , normal DHCP.

For information I run the 'dmesg' command in a terminal to see if I can get any trace of errors prior to the hang, so far nothing. I don't know what log(s) to check for errors like this, any help would be appreciated.

Cheers, Henrik

ihjort ( 2018-02-26 13:48:42 +0300 )edit

Hi.

In order to see detailed logs you may want to run:

journalctl -l -f

as root.

Regards.

Pasko ( 2018-02-28 00:03:30 +0300 )edit

Thanks for the help Pasko.

I have used the command and seen some errors, can't say if they are related.

One error I saw in dmesg as root was

-->

dhd_wait_pend8021x: TIMEOUT

clearpad clearpad: (clearpad_process_irq:4152) no work, interrupt=[0x00]

INTERNAL ERROR: FIRMWARE HALTED : set BUS DOWN

<--

Then a lot of "Console" information, looks like a stack trace and a "TRAP 4)

ihjort ( 2018-03-02 00:03:11 +0300 )edit

Hi.

I have confronted your logs with my logs and I don't have the

INTERNAL ERROR: FIRMWARE HALTED : set BUS DOWN

messages.

Maybe this is a hardware problem?. I would still try two more things (maybe you have done it already):

1.- Delete and recreate again your WLAN configuration

2.- Use the CSD app to test your WLAN functionalities, although I think this only tests WLAN scanning....

I hope this helps.

Regards.

Pasko ( 2018-03-02 09:44:44 +0300 )edit

1 Answer

Sort by » oldest newest most voted
1

answered 2019-05-28 19:45:09 +0300

Sunny gravatar image

Most likely your WiFi infrastructure has 802.11v/k enabled, see https://together.jolla.com/question/205934/sailfishx-303-wifi-firmware-crash/

The only solution I know is to disable those assisted roaming extensions.

edit flag offensive delete publish link more

Comments

Very likely as I avoided the problem when using a single AP and not my Mesh,(3 x AP as one network), one. We guessed "Avoding FAST TRANSITION (802.11r)" was the fix.

But it can be any of them: "802.11k, 802.11v and 802.11r are all standards designed to create a more seamless roaming experience for wireless clients."

Cheers, Henrik

ihjort ( 2019-05-28 20:16:23 +0300 )edit
Login/Signup to Answer

Question tools

Follow
2 followers

Stats

Asked: 2018-02-23 13:55:29 +0300

Seen: 709 times

Last updated: May 28 '19