[ASUS ZENBOOK UX32VD] Wifi failure to connect regression.

[Dave Chiluk]

3.13.0-29-generic works 3.13.0-30 results in the following errors

Jun 23 20:53:15 colt kernel: [ 5.862854] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
Jun 23 20:53:15 colt kernel: [ 5.869441] iwlwifi 0000:03:00.0: Radio type=0x2-0x1-0x0
Jun 23 20:53:15 colt kernel: [ 5.967202] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jun 23 20:53:15 colt kernel: [ 5.967478] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jun 23 20:53:15 colt kernel: [ 5.972410] ip6_tables: (C) 2000-2006 Netfilter Core Team
Jun 23 20:53:15 colt kernel: [ 6.644363] Bridge firewalling registered
Jun 23 20:53:16 colt kernel: [ 6.816877] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jun 23 20:53:16 colt kernel: [ 6.865773] IPv6: ADDRCONF(NETDEV_UP): virbr0: link is not ready
Jun 23 20:53:18 colt kernel: [ 9.196680] wlan0: authenticate with 94:0c:6d:fe:2e:d6
Jun 23 20:53:18 colt kernel: [ 9.201356] wlan0: send auth to 94:0c:6d:fe:2e:d6 (try 1/3)
Jun 23 20:53:18 colt kernel: [ 9.305248] wlan0: send auth to 94:0c:6d:fe:2e:d6 (try 2/3)
Jun 23 20:53:18 colt kernel: [ 9.307338] wlan0: authenticated
Jun 23 20:53:18 colt kernel: [ 9.307545] wlan0: waiting for beacon from 94:0c:6d:fe:2e:d6
Jun 23 20:53:21 colt kernel: [ 12.654570] wlan0: authenticate with 94:0c:6d:fe:2e:d6
Jun 23 20:53:21 colt kernel: [ 12.656770] wlan0: send auth to 94:0c:6d:fe:2e:d6 (try 1/3)
Jun 23 20:53:21 colt kernel: [ 12.659369] wlan0: authenticated
Jun 23 20:53:21 colt kernel: [ 12.659583] wlan0: waiting for beacon from 94:0c:6d:fe:2e:d6
Jun 23 20:53:25 colt kernel: [ 16.446479] wlan0: authenticate with 94:0c:6d:fe:2e:d6
Jun 23 20:53:25 colt kernel: [ 16.449055] wlan0: send auth to 94:0c:6d:fe:2e:d6 (try 1/3)
Jun 23 20:53:25 colt kernel: [ 16.451708] wlan0: authenticated
Jun 23 20:53:25 colt kernel: [ 16.451816] wlan0: waiting for beacon from 94:0c:6d:fe:2e:d6
Jun 23 20:53:30 colt kernel: [ 20.751118] wlan0: authenticate with 94:0c:6d:fe:2e:d6
Jun 23 20:53:30 colt kernel: [ 20.753892] wlan0: send auth to 94:0c:6d:fe:2e:d6 (try 1/3)
Jun 23 20:53:30 colt kernel: [ 20.756151] wlan0: authenticated
Jun 23 20:53:30 colt kernel: [ 20.756311] wlan0: waiting for beacon from 94:0c:6d:fe:2e:d6
Jun 23 20:53:46 colt kernel: [ 37.251795] wlan0: authenticate with 94:0c:6d:fe:2e:d6
Jun 23 20:53:46 colt kernel: [ 37.254521] wlan0: send auth to 94:0c:6d:fe:2e:d6 (try 1/3)
Jun 23 20:53:46 colt kernel: [ 37.256537] wlan0: authenticated
Jun 23 20:53:46 colt kernel: [ 37.256922] wlan0: waiting for beacon from 94:0c:6d:fe:2e:d6
Jun 23 20:53:59 colt kernel: [ 50.574868] wlan0: authenticate with 94:0c:6d:fe:2e:d6
Jun 23 20:53:59 colt kernel: [ 50.577201] wlan0: send auth to 94:0c:6d:fe:2e:d6 (try 1/3)
Jun 23 20:53:59 colt kernel: [ 50.579460] wlan0: authenticated
Jun 23 20:53:59 colt kernel: [ 50.579761] wlan0: waiting for beacon from 94:0c:6d:fe:2e:d6
Jun 23 20:54:11 colt kernel: [ 62.361021] wlan0: authenticate with 94:0c:6d:fe:2e:d6
Jun 23 20:54:11 colt kernel: [ 62.363445] wlan0: send auth to 94:0c:6d:fe:2e:d6 (try 1/3)
Jun 23 20:54:11 colt kernel: [ 62.366190] wlan0: authenticated
Jun 23 20:54:11 colt kernel: [ 62.366336] wlan0: waiting for beacon from 94:0c:6d:fe:2e:d6
Jun 23 20:54:24 colt kernel: [ 75.684454] wlan0: authenticate with 94:0c:6d:fe:2e:d6
Jun 23 20:54:24 colt kernel: [ 75.686745] wlan0: send auth to 94:0c:6d:fe:2e:d6 (try 1/3)
Jun 23 20:54:24 colt kernel: [ 75.692039] wlan0: authenticated
Jun 23 20:54:24 colt kernel: [ 75.692169] wlan0: waiting for beacon from 94:0c:6d:fe:2e:d6
Jun 23 20:54:36 colt kernel: [ 87.367947] wlan0: authenticate with 94:0c:6d:fe:2e:d6
Jun 23 20:54:36 colt kernel: [ 87.370284] wlan0: send auth to 94:0c:6d:fe:2e:d6 (try 1/3)
Jun 23 20:54:36 colt kernel: [ 87.372230] wlan0: authenticated
Jun 23 20:54:36 colt kernel: [ 87.372356] wlan0: waiting for beacon from 94:0c:6d:fe:2e:d6
Jun 23 20:54:49 colt kernel: [ 100.691218] wlan0: authenticate with 94:0c:6d:fe:2e:d6
Jun 23 20:54:49 colt kernel: [ 100.693585] wlan0: send auth to 94:0c:6d:fe:2e:d6 (try 1/3)

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-30-generic 3.13.0-30.54
ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
Uname: Linux 3.13.0-30-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: chiluk 2171 F.... pulseaudio
CurrentDesktop: Unity
Date: Mon Jun 23 20:58:34 2014
InstallationDate: Installed on 2014-01-07 (167 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140106)
MachineType: ASUSTeK COMPUTER INC. UX32VD
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic.efi.signed root=UUID=292a06f6-464a-49e4-a244-2c2d668f33b7 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-30-generic N/A
 linux-backports-modules-3.13.0-30-generic N/A
 linux-firmware 1.127.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/29/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX32VD.214
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX32VD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX32VD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Dave Chiluk, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available from the very top line at the top of the page (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-3.16-rc2

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Tim Gardner (timg-tpi)]

Dave - I'm concerned that one of the patches in the i40e backport might have impacted iwlwifi. Can you perform a bisect between Ubuntu-3.13.0-29.53 and Ubuntu-3.13.0-30.54 ?

[Dave Chiluk (chiluk)]

@Tim - This was noticed at a meeting room that I don't go to very often.

I will do my best. It should be noted that arges who was running Utopic was also seeing the same issue on his T420. (I'm not sure what specific kernel version that was though).

[guysoft (guysoft)]

Hey,
I have disconnections problems too on Zenbook UX32VD with iwlwifi. Ubuntu 14.04.

 Will test here

[penalvch (penalvch)]

guysoft, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

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

[guysoft (guysoft)]

Hey,
I am on 3.14.4-031404-generic. But when I try running `ubuntu-bug linux` i get:
"It appears you are currently running a mainline kernel. It would be better to report this bug upstream at http://bugzilla.kernel.org/ so that the upstream kernel developers are aware of the issue. If you'd still like to file a bug against the Ubuntu kernel, please boot with an official Ubuntu kernel and re-file".

[penalvch (penalvch)]

guysoft, please again see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1333487/comments/7 .

[Dave Chiluk (chiluk)]

So upon further investigation, this issue appears to be more access point/timing related than kernel specific. Once I connect to the access point using an older kernel, any of the new kernels will also work.

Very odd. Not really sure how to proceed on this one.

[guysoft (guysoft)]

Hey,
I am on 3.14.4-031404-generic. But when I try running `ubuntu-bug linux` i get:
"It appears you are currently running a mainline kernel. It would be better to report this bug upstream at http://bugzilla.kernel.org/ so that the upstream kernel developers are aware of the issue. If you'd still like to file a bug against the Ubuntu kernel, please boot with an official Ubuntu kernel and re-file". How do I get around that?

Also @dave that's not the same behaviour I get here. I get the problem with all my known access points.

[Seth Forshee (sforshee)]

On Thu, Aug 21, 2014 at 04:37:05PM -0000, guysoft wrote:
> Hey,
> I am on 3.14.4-031404-generic. But when I try running `ubuntu-bug linux` i get:
> "It appears you are currently running a mainline kernel. It would be better to report this bug upstream at http://bugzilla.kernel.org/ so that the upstream kernel developers are aware of the issue. If you'd still like to file a bug against the Ubuntu kernel, please boot with an official Ubuntu kernel and re-file". How do I get around that?

The mainline builds are only for testing and are not supported, which is
why you're getting that message. If you want to file a bug you'll need
to switch back to the official Ubuntu kernels.

[Dave Chiluk (chiluk)]

This appears to have been resolved with more recent kernels, or revisions of the firmware on the routers where I was having issue. Since I don't control the router, it's a bit hard to tell. So I'm closing this as fixed released for now.