Ubuntu
linux package

QCA9377 WIFI does not work

Bug #1683577 reported by Dehuan Xin
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

My laptop, acer E5-575-53EJ, sometimes boots without wifi connection being detected.
Restarting the network-manager sometimes fixes the problem.

dmesg | grep ath shows the kernel log.

The system finishes booting at 12.x seconds with no wifi connections. Network-manager is restarted around 3x seconds and connection is established around 78.x seconds.
Then firmware crashed at 624 seconds, followed by a successful recovery.

At 915.x seconds a suspend is attempted, followed by a restart of network-manager scheduled by systemd. Connect was lost.

Launching Wicd network manager recovers the connection, but the network-manager shows nothing.

Ubuntu: 17.04,
kernel: 4.10.0-19-generic
Firmware:
I tired the qca firmware at https://github.com/kvalo/ath10k-firmware/tree/master/QCA9377/hw1.0 .
all three files have the same md5 as the one installed by default.
Hardware:
02:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31)
[ 0.177594] pci 0000:02:00.0: [168c:0042] type 00 class 0x028000
[ 0.177626] pci 0000:02:00.0: reg 0x10: [mem 0xb1000000-0xb11fffff 64bit]
[ 0.177800] pci 0000:02:00.0: PME# supported from D0 D3hot D3cold
[ 0.177871] pci 0000:02:00.0: System wakeup disabled by ACPI

Additional info: When this laptop was running 1.23 bios, linux has reported repeated PCIE errors. I upgraded bios to 1.25 and PCIE errors are gone, however wifi does not improve.

[ 1.917547] ath10k_pci 0000:02:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[ 2.196931] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:02:00.0.bin failed with error -2
[ 2.196945] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/cal-pci-0000:02:00.0.bin failed with error -2
[ 2.198777] ath10k_pci 0000:02:00.0: qca9377 hw1.1 target 0x05020001 chip_id 0x003821ff sub 11ad:08a6
[ 2.198779] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[ 2.199128] ath10k_pci 0000:02:00.0: firmware ver WLAN.TF.1.0-00267-1 api 5 features ignore-otp crc32 79cea2c7
[ 2.264639] ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 93da0176
[ 4.066350] ath10k_pci 0000:02:00.0: htt-ver 3.1 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[ 4.071835] ath: EEPROM regdomain: 0x69
[ 4.071835] ath: EEPROM indicates we should expect a direct regpair map
[ 4.071837] ath: Country alpha2 being used: 00
[ 4.071837] ath: Regpair used: 0x69
[ 4.076946] ath10k_pci 0000:02:00.0 wlp2s0: renamed from wlan0
[ 8.562060] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
[ 12.760910] ath: EEPROM regdomain: 0x8348
[ 12.760911] ath: EEPROM indicates we should expect a country code
[ 12.760912] ath: doing EEPROM country->regdmn map search
[ 12.760913] ath: country maps to regdmn code: 0x3a
[ 12.760914] ath: Country alpha2 being used: US
[ 12.760914] ath: Regpair used: 0x3a
[ 12.760915] ath: regdomain 0x8348 dynamically updated by country IE
[ 22.051491] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
[ 22.052023] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
[ 22.052471] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
[ 22.092738] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
[ 22.195128] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
[ 32.478247] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
[ 39.400234] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
[ 50.115130] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
[ 50.577978] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
[ 55.781520] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
[ 55.884352] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
[ 63.402603] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
[ 68.063646] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
[ 68.526311] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
[ 76.300734] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
[ 76.557875] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
[ 79.876632] ath: EEPROM regdomain: 0x8348
[ 79.876632] ath: EEPROM indicates we should expect a country code
[ 79.876633] ath: doing EEPROM country->regdmn map search
[ 79.876633] ath: country maps to regdmn code: 0x3a
[ 79.876634] ath: Country alpha2 being used: US
[ 79.876634] ath: Regpair used: 0x3a
[ 79.876635] ath: regdomain 0x8348 dynamically updated by country IE
[ 624.156177] ath10k_pci 0000:02:00.0: firmware crashed! (uuid bf526e81-5227-4645-969c-085d34525169)
[ 624.156238] ath10k_pci 0000:02:00.0: qca9377 hw1.1 target 0x05020001 chip_id 0x003821ff sub 11ad:08a6
[ 624.156255] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[ 624.158628] ath10k_pci 0000:02:00.0: firmware ver WLAN.TF.1.0-00267-1 api 5 features ignore-otp crc32 79cea2c7
[ 624.160240] ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 93da0176
[ 624.160262] ath10k_pci 0000:02:00.0: htt-ver 3.1 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[ 624.162288] ath10k_pci 0000:02:00.0: firmware register dump:
[ 624.162294] ath10k_pci 0000:02:00.0: [00]: 0x05020001 0x000015B3 0x00985B3A 0x00955B31
[ 624.162297] ath10k_pci 0000:02:00.0: [04]: 0x00985B3A 0x00060730 0x00000004 0x00000000
[ 624.162301] ath10k_pci 0000:02:00.0: [08]: 0x00955A00 0x00438A0C 0x004510FC 0x00420970
[ 624.162304] ath10k_pci 0000:02:00.0: [12]: 0x00000009 0x00000000 0x00952CD0 0x00952CE6
[ 624.162307] ath10k_pci 0000:02:00.0: [16]: 0x00952CC4 0x0091080D 0x00000000 0x00000000
[ 624.162310] ath10k_pci 0000:02:00.0: [20]: 0x40985B3A 0x0040E788 0x00400000 0x00421888
[ 624.162313] ath10k_pci 0000:02:00.0: [24]: 0x809BF546 0x0040E7E8 0x00426470 0xC0985B3A
[ 624.162316] ath10k_pci 0000:02:00.0: [28]: 0x809B90D8 0x0040E958 0x00000018 0x0042EA0C
[ 624.162319] ath10k_pci 0000:02:00.0: [32]: 0x809B859A 0x0040E9A8 0x0040E9CC 0x00428D74
[ 624.162322] ath10k_pci 0000:02:00.0: [36]: 0x8091D252 0x0040E9C8 0x00000000 0x00000001
[ 624.162325] ath10k_pci 0000:02:00.0: [40]: 0x809EDD7B 0x0040EA78 0x00437544 0x00429428
[ 624.162328] ath10k_pci 0000:02:00.0: [44]: 0x809EB6A6 0x0040EA98 0x00437544 0x00000001
[ 624.162332] ath10k_pci 0000:02:00.0: [48]: 0x80911210 0x0040EAE8 0x00000010 0x004041D0
[ 624.162335] ath10k_pci 0000:02:00.0: [52]: 0x80911154 0x0040EB28 0x00400000 0x00000000
[ 624.162337] ath10k_pci 0000:02:00.0: [56]: 0x8091122D 0x0040EB48 0x00000000 0x00400600
[ 626.151981] ath10k_pci 0000:02:00.0: device successfully recovered
[ 915.588782] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
[ 915.589236] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
[ 915.590017] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
[ 915.590411] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
[ 915.656260] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
[ 927.591541] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
[ 927.694493] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
[ 932.042186] ath: EEPROM regdomain: 0x8348
[ 932.042186] ath: EEPROM indicates we should expect a country code
[ 932.042187] ath: doing EEPROM country->regdmn map search
[ 932.042187] ath: country maps to regdmn code: 0x3a
[ 932.042188] ath: Country alpha2 being used: US
[ 932.042188] ath: Regpair used: 0x3a
[ 932.042188] ath: regdomain 0x8348 dynamically updated by country IE
[ 933.156208] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
[ 933.156738] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
[ 933.224851] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
[ 933.327286] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
[ 939.611019] ath: EEPROM regdomain: 0x8348
[ 939.611022] ath: EEPROM indicates we should expect a country code
[ 939.611023] ath: doing EEPROM country->regdmn map search
[ 939.611025] ath: country maps to regdmn code: 0x3a
[ 939.611027] ath: Country alpha2 being used: US
[ 939.611028] ath: Regpair used: 0x3a
[ 939.611030] ath: regdomain 0x8348 dynamically updated by country IE
---
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: dxin 1759 F.... pulseaudio
CurrentDesktop: Unity:Unity7
DistroRelease: Ubuntu 17.04
HibernationDevice: RESUME=UUID=3a61dd24-2c20-464b-bf52-79af9b66e9ad
InstallationDate: Installed on 2017-02-25 (52 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04f2:b571 Chicony Electronics Co., Ltd
 Bus 001 Device 002: ID 04ca:3015 Lite-On Technology Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire E5-575
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=da6f0c60-1c1e-4491-b7f7-95bea77d1c2e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-19-generic N/A
 linux-backports-modules-4.10.0-19-generic N/A
 linux-firmware 1.164
Tags: zesty
Uname: Linux 4.10.0-19-generic x86_64
UpgradeStatus: Upgraded to zesty on 2017-04-15 (4 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/03/2017
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.25
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Ironman_SK
dmi.board.vendor: Acer
dmi.board.version: V1.25
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.25:bd03/03/2017:svnAcer:pnAspireE5-575:pvrV1.25:rvnAcer:rnIronman_SK:rvrV1.25:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire E5-575
dmi.product.version: V1.25
dmi.sys.vendor: Acer
---
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: dxin 1759 F.... pulseaudio
CurrentDesktop: Unity:Unity7
DistroRelease: Ubuntu 17.04
HibernationDevice: RESUME=UUID=3a61dd24-2c20-464b-bf52-79af9b66e9ad
InstallationDate: Installed on 2017-02-25 (52 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04f2:b571 Chicony Electronics Co., Ltd
 Bus 001 Device 002: ID 04ca:3015 Lite-On Technology Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire E5-575
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=da6f0c60-1c1e-4491-b7f7-95bea77d1c2e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-19-generic N/A
 linux-backports-modules-4.10.0-19-generic N/A
 linux-firmware 1.164
Tags: zesty
Uname: Linux 4.10.0-19-generic x86_64
UpgradeStatus: Upgraded to zesty on 2017-04-15 (4 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/03/2017
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.25
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Ironman_SK
dmi.board.vendor: Acer
dmi.board.version: V1.25
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.25:bd03/03/2017:svnAcer:pnAspireE5-575:pvrV1.25:rvnAcer:rnIronman_SK:rvrV1.25:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire E5-575
dmi.product.version: V1.25
dmi.sys.vendor: Acer
---
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity:Unity7
DistroRelease: Ubuntu 17.04
InstallationDate: Installed on 2017-02-25 (52 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
Package: linux (not installed)
Tags: zesty
Uname: Linux 4.11.0-041100rc7-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: Upgraded to zesty on 2017-04-15 (4 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

See original description
Revision history for this message
Dehuan Xin (dxin) wrote :
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1683577/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Brian Murray (brian-murray)
affects: ubuntu → linux (Ubuntu)
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1683577

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc7

Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Dehuan Xin (dxin) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected zesty
description: updated
Revision history for this message
Dehuan Xin (dxin) wrote : CRDA.txt

apport information

Revision history for this message
Dehuan Xin (dxin) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Dehuan Xin (dxin) wrote : IwConfig.txt

apport information

Revision history for this message
Dehuan Xin (dxin) wrote : JournalErrors.txt

apport information

Revision history for this message
Dehuan Xin (dxin) wrote : Lspci.txt

apport information

Revision history for this message
Dehuan Xin (dxin) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Dehuan Xin (dxin) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Dehuan Xin (dxin) wrote : ProcEnviron.txt

apport information

Revision history for this message
Dehuan Xin (dxin) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Dehuan Xin (dxin) wrote : ProcModules.txt

apport information

Revision history for this message
Dehuan Xin (dxin) wrote : PulseList.txt

apport information

Revision history for this message
Dehuan Xin (dxin) wrote : RfKill.txt

apport information

Revision history for this message
Dehuan Xin (dxin) wrote : UdevDb.txt

apport information

Revision history for this message
Dehuan Xin (dxin) wrote : WifiSyslog.txt

apport information

description: updated
Revision history for this message
Dehuan Xin (dxin) wrote : AlsaInfo.txt

apport information

Revision history for this message
Dehuan Xin (dxin) wrote : CRDA.txt

apport information

Revision history for this message
Dehuan Xin (dxin) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Dehuan Xin (dxin) wrote : IwConfig.txt

apport information

Revision history for this message
Dehuan Xin (dxin) wrote : JournalErrors.txt

apport information

Revision history for this message
Dehuan Xin (dxin) wrote : Lspci.txt

apport information

Revision history for this message
Dehuan Xin (dxin) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Dehuan Xin (dxin) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Dehuan Xin (dxin) wrote : ProcEnviron.txt

apport information

Revision history for this message
Dehuan Xin (dxin) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Dehuan Xin (dxin) wrote : ProcModules.txt

apport information

Revision history for this message
Dehuan Xin (dxin) wrote : PulseList.txt

apport information

Revision history for this message
Dehuan Xin (dxin) wrote : RfKill.txt

apport information

Revision history for this message
Dehuan Xin (dxin) wrote : UdevDb.txt

apport information

Revision history for this message
Dehuan Xin (dxin) wrote : WifiSyslog.txt

apport information

Revision history for this message
Dehuan Xin (dxin) wrote :

More info on the system log:
At 12.xx secs, system boots into desktop with wifi automatically connected and works find.
At 118, 145,225 seconds, three attempts are made to re-connect to the same wifi ssid. First two are successful. The wifi adapter disappears from the network-manager after the third.
At 330 seconds ethernet cable is connected to submit the system log.

After the system log is sent, at 880 seconds after boot, a USB 802.11/b/g/n adapter was connected and detected by kernel but does not show up in network-manager:

869.724515] usb 1-4: new high-speed USB device number 4 using xhci_hcd
[ 869.882786] usb 1-4: New USB device found, idVendor=148f, idProduct=3070
[ 869.882793] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 869.882798] usb 1-4: Product: 802.11 n WLAN
[ 869.882802] usb 1-4: Manufacturer: Ralink
[ 869.882806] usb 1-4: SerialNumber: 1.0
[ 870.024988] usb 1-4: reset high-speed USB device number 4 using xhci_hcd
[ 870.176022] ieee80211 phy1: rt2x00_set_rt: Info - RT chipset 3070, rev 0201 detected
[ 870.188292] ieee80211 phy1: rt2x00_set_rf: Info - RF chipset 0005 detected
[ 870.189040] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
[ 870.190525] usbcore: registered new interface driver rt2800usb
[ 870.203530] rt2800usb 1-4:1.0 wlxe84e0604557e: renamed from wlan0
[ 870.231315] IPv6: ADDRCONF(NETDEV_UP): wlxe84e0604557e: link is not ready
[ 870.231355] ieee80211 phy1: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin'
[ 870.235687] ieee80211 phy1: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.36
[ 870.623403] IPv6: ADDRCONF(NETDEV_UP): wlxe84e0604557e: link is not ready
[ 871.048160] IPv6: ADDRCONF(NETDEV_UP): wlxe84e0604557e: link is not ready

Revision history for this message
Dehuan Xin (dxin) wrote :

Hi,Joseph,

This installation of 17.04 is an upgrade from 16.10.
I did not use 16.10 as much as I'm using 17.04 now so I can not confirm the WIFI drops out equally as frequently as 17.04 during regular usage.

However I confirm that 16.10 has the same problem that wifi disappears from network-manager after a suspend/wakeup cycle. At that time I have not tried restarting network-manager but had to reboot if I needed wifi after sleep/wakeup. That did not affect me much then because I used wired network and bluetooth most of the time then.

Dehuan

Revision history for this message
Dehuan Xin (dxin) wrote : JournalErrors.txt

apport information

description: updated
Revision history for this message
Dehuan Xin (dxin) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Dehuan Xin (dxin) wrote : ProcEnviron.txt

apport information

Revision history for this message
Dehuan Xin (dxin) wrote :

Comments on the latest apport info:
System boots into 4.11rc7 kernel.
After boot, both QCA9377 and USB WIFI are detected by network-manager but both are "device not ready" status.
No wifi connections.

Revision history for this message
Dehuan Xin (dxin) wrote :

With 4.11rc7 kernel:
1) Ubuntu boots with wifi in "device not ready" status.
2) Restarting network-manager recovers both adapters.
3) After sleep/wakeup cycle, both wifi adapters enters "device not ready" again.

I reported the same problem is filed at upstream:
https://bugzilla.kernel.org/show_bug.cgi?id=195463

To post a comment you must log in.