Bug 4609 - Wi-fi does not works after waking up
: Wi-fi does not works after waking up
Status: CONFIRMED
Product: Desktop Bugs
Classification: ROSA Desktop
Component: Main Packages
: Fresh
: x86_64 Linux
: Normal normal
: ---
Assigned To: Eugene Shatokhin
: ROSA Linux Bugs
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-10-31 23:45 MSK by Alexander
Modified: 2016-01-30 22:49 MSK (History)
2 users (show)

See Also:
RPM Package:
ISO-related:
Bad POT generating:
Upstream:


Attachments
journalctl -ab (33.25 KB, text/plain)
2014-11-16 11:51 MSK, Alexander
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander 2014-10-31 23:45:11 MSK
Description of problem:

Wi-Fi is not working after waking up.

Version-Release number of selected component (if applicable):
Linux home 3.14.22-nrj-desktop-3rosa
ROSA Desktop Fresh R4 release 2014.1 for x86_64

How reproducible:

Always

Steps to Reproduce:
1. Go to suspend
2. Wake up PC

After waking up ifconfig display wlan0 inteface, but there is no ip address. Network manager nor dhclient cannot obtain IP address. I tried to do 'ifconfig wlan0 down/up' but it does not help.

Wi-Fi is USB adapter TP-Link

[    4.649478] usb 6-1: new high-speed USB device number 2 using ehci-pci
[    4.773745] usb 6-1: New USB device found, idVendor=0bda, idProduct=8178
[    4.773748] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    4.773749] usb 6-1: Product: USB WLAN
[    4.773751] usb 6-1: Manufacturer: 802.11n
[    4.773752] usb 6-1: SerialNumber: 00e04c000001
Comment 1 Eugene Shatokhin 2014-11-05 12:13:47 MSK
(Можно по-русски, если так удобнее.)

First of all, please upload the hardware info and the logs using our hw-probe tool:

1) install hw-probe if it is not already installed;
2) run as root (replace "<PC_NAME>" below with the name of your computer or with any other name you like):
   hw-probe -all -upload -id <PC_NAME>

hw-probe will output the URL of the uploaded data - please post it here.

It is better to do all that after the problem happens (you will likely need a wired connection to the net in that case). 

Alternatively, you can invoke hw-probe while the WiFi is still working. Then, after the problem happens, please save the output of 'journalctl -ab' as root and attach it here.
Comment 2 Alexander 2014-11-16 11:51:56 MSK
Created attachment 3475 [details]
journalctl -ab
Comment 3 Alexander 2014-11-16 11:55:09 MSK
Ок, по-русски.

hw-probe до сна: http://hw.rosalinux.ru/index.php?probe=8e9008d12e

После сна не получилось, сети нет, подключиться по кабелю возможности нет. В аттаче хвост вывода journalctl -ab


Сейчас симптомы немного изменились. После просыпания адаптер МОЖЕТ ПОЛУЧИТЬ АДРЕС, даже запустив wireshark я вижу, что роутер выдаёт адрес, затем, если я пускаю куда-нибудь пинг, то вижу arp пакет, идущий на роутер и роутер отвечает, дальше обмен трафико не идёт. Пинг не проходит. Не пингуется не только интернет и роутер, но даже и соседи в локальной сети. При отключении адаптера и переподключении его снова, он опять успешно получает адрес, однако всё тоже самое, пинга нет, связи нет.
Comment 4 Eugene Shatokhin 2014-11-27 20:03:50 MSK
Если снова проявится, попробуйте перезапустить службу "NetworkManager" (под root):

systemctl restart NetworkManager.service

Пока надёжно воспроизвести проблему не получается, но время от времени что-то похожее наблюдаю на разных системах. Обычно перезапуск "NetworkManager" помогал. Возможно, где-то в нём дело.
Comment 5 Alexander 2014-12-07 10:20:51 MSK
Попробовал. Не помогает.
Comment 6 Zombie Ryushu 2016-01-30 11:02:22 MSK
This affects Wired Networks too. Its not isolated to Wireless networks. I have to go into Network Manager, Check and Uncheck enable networking for the LAN Connection to come back up.
Comment 7 Eugene Shatokhin 2016-01-30 12:49:32 MSK
(In reply to comment #6)
> This affects Wired Networks too. Its not isolated to Wireless networks. I
> have to go into Network Manager, Check and Uncheck enable networking for the
> LAN Connection to come back up.

Logs or hw-probe data = ? Steps to reproduce = ? Other details = ?

Such problems can be caused by a variety of different issues, and are not necessarily the same as for the issue reported here originally.
Comment 8 Zombie Ryushu 2016-01-30 18:56:41 MSK
The Kernel in use is 4.1.15
ROSA Desktop Fresh R7
The driver module is alx
01:00.0 Ethernet controller: Qualcomm Atheros QCA8171 Gigabit Ethernet (rev 10)

All you need to do is run pm-suspend from the command line. It will reproduce this issue.
Comment 9 Eugene Shatokhin 2016-01-30 22:31:44 MSK
(In reply to comment #8)
> The Kernel in use is 4.1.15
> ROSA Desktop Fresh R7
> The driver module is alx
> 01:00.0 Ethernet controller: Qualcomm Atheros QCA8171 Gigabit Ethernet (rev
> 10)
> 
> All you need to do is run pm-suspend from the command line. It will
> reproduce this issue.

Yes, it is a separate issue. 

The problem is, alx is no longer maintained by Qualcomm/Atheros, all fixes are made by the enthusiasts now, like the fix for #6410.
Comment 10 Zombie Ryushu 2016-01-30 22:49:53 MSK
I think this is more of a generic suspend issue. Ubuntu has reported similar issues. 

http://www.techytalk.info/ubuntu-fix-network-stopped-working-after-resume-from-sleep/comment-page-2/