Some additional notes after testing for a while...

The crashing behavior doesn't occur consistently in the same way.
Sometimes the Bluetooth crashes with the Wifi, while sometimes it
recovers fine and continues to work while the Wifi doesn't. In addition,
it seems that the Wifi crash breaks NetworkManager as well- when I try
to plug in a USB WiFi card, the networks show up but give me the
following error in dmesg whenever the usb adapter tries to connect:

[21857.875157] wlx002129e30688: authenticate with 8e:15:44:a9:86:22
[21857.924545] wlx002129e30688: send auth to 8e:15:44:a9:86:22 (try 1/3)
[21857.926882] wlx002129e30688: authenticated
[21863.316129] wlx002129e30688: authenticate with 8e:15:44:a9:85:f8
[21863.371861] wlx002129e30688: send auth to 8e:15:44:a9:85:f8 (try 1/3)
[21863.374438] wlx002129e30688: authenticated
[21868.376165] wlx002129e30688: aborting authentication with 8e:15:44:a9:85:f8 
by local choice (Reason: 3=DEAUTH_LEAVING)
[21868.740813] wlx002129e30688: authenticate with 8e:15:44:a9:82:fa
[21868.788615] wlx002129e30688: send auth to 8e:15:44:a9:82:fa (try 1/3)
[21868.790444] wlx002129e30688: authenticated
[21873.795552] wlx002129e30688: aborting authentication with 8e:15:44:a9:82:fa 
by local choice (Reason: 3=DEAUTH_LEAVING)

This repeats until it gives up trying to connect. Yet, tethering to my
Android phone over USB DOES usually work. Restarting the NetworkManager
service has no effect on the wifi issue.

@jsalisbury: This issue has persisted across kernel versions and Ubuntu
versions. I had the same issue on 16.10, as well as Arch when I used it,
upgrade or not. I'm not ruling out a regression however, but frankly I
have no qualifications to say what the issue is caused by. If I have
time (and I get desperate enough) I'll try 16.04 and 14.04 and let you
know if it's still present there.

I'll test the 4.11 kernel this weekend, in the meantime, I'll upload
some more dmesg outputs.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1684213

Title:
  Intel Wireless 7260 often crashes

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS 
enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses 
Intel 7260 wifi, rev. bb:
  01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

  Software: Ubuntu Mate 17.04, upgraded from 16.10. Currently,
  everything (kernel, firmware, etc.) is stock. Issue has persisted
  across multiple installations.

  Bug: Wifi/Bluetooth crashes and refuses to come back up, even after
  multiple reboots. Issue persists across distros (Arch, Ubuntu, etc.)

  When the wireless (Bluetooth and WiFi) works, it works flawlessly. However, 
upon boot, it is not uncommon for the wireless to stop working within two 
minutes of login time. Curiously, the GUI usually still shows being 
"connected", though trying to change anything with the wifi shows otherwise. 
Other times, upon system resume when wireless was previously working, the GUI 
will show "device not ready" and refuse to continue. Dmesg shows the following:
  [  423.814823] Bluetooth: hci0 command 0x1403 tx timeout
  [  424.172973] iwlwifi 0000:01:00.0: Failed to wake NIC for hcmd
  [  424.173062] iwlwifi 0000:01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  424.173067] iwlwifi 0000:01:00.0: Scan failed! ret -5
  [  425.194487] iwlwifi 0000:01:00.0: Failed to wake NIC for hcmd
  [  425.194589] iwlwifi 0000:01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  425.194593] iwlwifi 0000:01:00.0: Scan failed! ret -5

  Solution: Rebooting doesn't fix the problem. Perhaps a different
  firmware version will work better? Configuration settings? etc.?
  Unknown.

  Thanks ahead of time for the help. Let me know if there's anything you
  need/commands I should run/solutions I can attempt.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  bmueller   1669 F.... pulseaudio
  CurrentDesktop: MATE
  Date: Wed Apr 19 10:34:11 2017
  InstallationDate: Installed on 2017-04-13 (6 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:07dc Intel Corp.
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Gnawty
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=45b1dd3f-10df-4a28-904c-74c694ef75a5 ro quiet splash vt.handoff=7
  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
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (2 days ago)
  dmi.bios.date: 08/16/2015
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/16/2015:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Gnawty
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1684213/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to