mwifiex_pcie causes the system to hang

[MagnusPI]

Every now andthen mwifiex_pcie causes the system to hang.
The only way to restart is taking the power off.
The relevant prt ofsyslog is in attachment.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-extra-3.13.0-32-generic 3.13.0-32.57
ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
Uname: Linux 3.13.0-39-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: igor 1921 F.... pulseaudio
                      igor 2106 F.... pulseaudio
 /dev/snd/controlC0: igor 1921 F.... pulseaudio
                      igor 2106 F.... pulseaudio
CurrentDesktop: KDE
Date: Thu Nov 20 07:45:27 2014
HibernationDevice: RESUME=UUID=c1e2014a-0531-41bd-9695-abc7feccbbd1
InstallationDate: Installed on 2014-11-15 (4 days ago)
InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Microsoft Corporation Surface Pro 3
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic.efi.signed root=UUID=b2de8eed-7a94-41a5-9876-54a489902f23 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-39-generic N/A
 linux-backports-modules-3.13.0-39-generic N/A
 linux-firmware 1.127.8
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/27/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3.11.0250
dmi.board.asset.tag: 0
dmi.board.name: Surface Pro 3
dmi.board.vendor: Microsoft Corporation
dmi.board.version: 1
dmi.chassis.asset.tag: 0
dmi.chassis.type: 9
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: 1
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.11.0250:bd09/27/2014:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1:
dmi.product.name: Surface Pro 3
dmi.product.version: 1
dmi.sys.vendor: Microsoft Corporation

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.18 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'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-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/v3.18-rc5-vivid/

[MagnusPI (ipesando)]

I tried the latest upstream kernel as you suggested and until now the bug has not shown up again.
The feeling is that the connection is a little more sluggish but it works.
tags: 'kernel-fixed-upstream'.

[penalvch (penalvch)]

MagnusPI, the next step is to fully reverse commit bisect from kernel 3.13 to 3.18-rc5 in order to identify the last bad commit, followed immediately by the first good one. Once this commit has been identified, then it may be reviewed as a candidate for backporting into your release. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ? Please note, finding adjacent kernel versions is not fully commit bisecting.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[MagnusPI (ipesando)]

Bisect 6 good [DIR] v3.14-rc1-trusty/ 03-Feb-2014 02:22
Bisect 3 bad [DIR] v3.13.11.11-trusty/ 11-Nov-2014 19:20

Is it worth doing fully commit bisecting since the "good" kernel is more or less the next one?
BTW I believe the bug is connected with the power mangement.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]