168c:003e Call trace connecting to 802.11ac/5GHz

[Corey]

What is expected is when I connect my laptop to my Samsung Galaxy Note Edge (Android 5.0.1, Build LRX22C.N915VVRU2BOJ7) 802.11ac/5GHz access point, it connects.

What happens instead is that there is a kernel call trace as per:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1538673/+attachment/4563481/+files/log.txt

then NetworkManager times out the connection.

WORKAROUND: Use the phone's hotspot on 2.4GHz.

---
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: polomoto 1168 F.... pulseaudio
 /dev/snd/controlC1: polomoto 1168 F.... pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 15.10
HibernationDevice: RESUME=UUID=5018c1c5-f5d2-45e3-a3da-4e74bd9b9131
InstallationDate: Installed on 2016-01-22 (4 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Micro-Star International Co., Ltd. GS60 2QE
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-25-generic.efi.signed root=UUID=b7920bb6-c35c-43c5-82be-c195753bc15f ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-25-generic N/A
 linux-backports-modules-4.2.0-25-generic N/A
 linux-firmware 1.149.3
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: wily
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
Uname: Linux 4.2.0-25-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 09/15/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E16H5IMS.104
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MS-16H5
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:0.B
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16H5IMS.104:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS602QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H5:rvrREV0.B:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: GS60 2QE
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

[Brad Figg (brad-figg)]

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

apport-collect 1538673

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.

[Corey (barnwell9)]

apport information

[Corey (barnwell9)]

apport information

[Corey (barnwell9)]

apport information

[Corey (barnwell9)]

apport information

[Corey (barnwell9)]

apport information

[Corey (barnwell9)]

apport information

[Corey (barnwell9)]

apport information

[Corey (barnwell9)]

apport information

[Corey (barnwell9)]

apport information

[Corey (barnwell9)]

apport information

[Corey (barnwell9)]

apport information

[Corey (barnwell9)]

apport information

[Corey (barnwell9)]

apport information

[Corey (barnwell9)]

Thank you for finding that, a few days ago that page was empty.

1)
E16H5IMS.10H
07/28/2015

2) There was no improvement, the firmware still crashes attempting to connect to a wireless ac network.

[Corey (barnwell9)]

Also the log that is linked in the original post now is neither from my laptop nor a laptop with this wifi card. I'm not sure if that was intentional or not.

[penalvch (penalvch)]

Corey, it's the log you provided in your Description. So, if the information in the Description was provided by you unintentionally, please feel free to delete the attachment.

Despite this, in order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

[Corey (barnwell9)]

The log in the attachment is not what I had in the description originally, you can see this by viewing the original description, but if its not helping anyone anyway I will just remove it.

The bug was not fixed upstream, will add tags

[Corey (barnwell9)]

I think you meant laptop not phone,

MSI
GS60-2QE
Ubuntu Gnome 15.10
BIOS E16H5IMS.10H

[Corey (barnwell9)]

I'm sorry that part slipped my mind?

Samsung
Galaxy Note Edge
Android 5.0.1
And I'm not sure what you mean by firmware, if you mean kernel its 3.10.40

[Corey (barnwell9)]

Oh so then its just 5.0.1, I just bundled that with the OS, my bad.

[Corey (barnwell9)]

Ooooooh ok I got it, sorry its been a long day.

The build number is LRX22C.N915VVRU2BOJ7

[penalvch (penalvch)]

Corey, the issue you are reporting is an upstream one. Could you please report this problem following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing list (TO Johannes Berg, CC linux-wireless, and Kalle Valo)?

Please provide a direct URL to your post to the mailing list when it becomes available so that it may be tracked.

Thank you for your understanding.

[Corey (barnwell9)]

Chris, I have the email ready to send but I can't seem to figure out where to find the email addresses for Johannes Berg and Kalle Valo. Could you advise where I could find those?