Intel wireless still randomly drops connection

[Jamie Strandboge]

Like others, my machine suffered from bug #911059, which is basically that at random times the wireless connection drops and then comes back. I tried the 3.3 kernel and that fixed it for a full working day. I then was using 'options iwlwifi 11n_disable=1 swcrypto=1' which also seemed to work. After upgrading to 3.2.0-18.28-generic and removing the iwlwifi options, I still continue to see random drops. The situation is perhaps improved with the new kernel, but I don't have a reliable trigger so it is hard to say.

Filing a new bug at the kernel team's request. Please see bug #911059 for more details.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-18-generic 3.2.0-18.28
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.94-0ubuntu1
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: jamie 2894 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf2520000 irq 45'
   Mixer name : 'Intel IbexPeak HDMI'
   Components : 'HDA:14f15069,17aa2156,00100302 HDA:80862804,17aa21b5,00100000'
   Controls : 14
   Simple ctrls : 6
Card29.Amixer.info:
 Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 6QHT32WW-1.13'
   Mixer name : 'ThinkPad EC 6QHT32WW-1.13'
   Components : ''
   Controls : 1
   Simple ctrls : 1
Card29.Amixer.values:
 Simple mixer control 'Console',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Date: Tue Mar 6 11:52:06 2012
HibernationDevice: RESUME=UUID=c4c5dbc0-d41a-428d-8af4-b680b67dd3dc
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110425.2)
MachineType: LENOVO 5129CTO
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic root=UUID=88689ad2-74b5-442c-9290-8ae60b63e16b ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-18-generic N/A
 linux-backports-modules-3.2.0-18-generic N/A
 linux-firmware 1.71
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: Upgraded to precise on 2012-01-02 (63 days ago)
dmi.bios.date: 02/24/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 6QET64WW (1.34 )
dmi.board.name: 5129CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr6QET64WW(1.34):bd02/24/2011:svnLENOVO:pn5129CTO:pvrThinkPadX201s:rvnLENOVO:rn5129CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 5129CTO
dmi.product.version: ThinkPad X201s
dmi.sys.vendor: LENOVO

[Jamie Strandboge (jdstrand)]

Per kernel team's request, I should try linux-backports-modules-cw-3.3-precise-generic from https://launchpad.net/ubuntu/precise/+package/linux-backports-modules-cw-3.3-3.2.0-18-generic. I will do that now.

[Jamie Strandboge (jdstrand)]

Running with linux-backports-modules-cw-3.3 I have not had any dropouts for 2 days.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Gerhard Aigner (gerhard-aigner)]

I suffering from this bug with kernel 3.2.0-18 on 12.04, but the proposed "solution" of installing linux-backports-modules-cw-3.3-precise-generic didn't help me. Might be useful: https://bugzilla.redhat.com/show_bug.cgi?id=787446

[Jamie Strandboge (jdstrand)]

It seems that while linux-backports-modules-cw-3.3 helped some, I still see random disconnects. Going back to using:
options iwlwifi 11n_disable=1 swcrypto=1

I will try this for a few days and report back.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Joseph Salisbury (jsalisbury)]

Hi Jamie,

There are some wireless fixes in 3.2.0-19.30. It would be great if you could test the latest kernel and report back.

[Jamie Strandboge (jdstrand)]

Thanks, I have been running it since yesterday but am not comfortable saying it is fixed yet, but will report back.

[Jamie Strandboge (jdstrand)]

I have not seen these issues in several days and am going to mark this as Fix Released. If I see them again, I will re-open.

[David Planella (dpm)]

Al 23/03/12 17:05, En/na Jamie Strandboge ha escrit:
> I have not seen these issues in several days and am going to mark this
> as Fix Released. If I see them again, I will re-open.

Just a quick note that I was also affected by this follow-up bug and I
haven't seen it happening in several days, either.

[Manuel Carro (mcarro)]

Jamie,

I followed the thread and I am not sure I know the packages / versions you installed to get rid of the disconnections. Would you be so kind of giving a summary? I'll try to install and report. Thanks a lot!

[Anmar Oueja (anmar)]

Jamie: I have the same problem as yours and I still exhibit the same problem. If you can answer Manuel , I would greatly appreciate it.

[Andreas Hasenack (ahasenack)]

I also still have random disconnects with kernel 3.2.0-21-generic-pae #34, I'm back to disabling wifi-n.

[Joseph Salisbury (jsalisbury)]

@Andreas, @Anmar, and @Manuel

Did you just start hitting this bug after upgrading to 3.2.0-21-generic-pae #34?

[Joseph Salisbury (jsalisbury)]

@Jamie,

Is this issue still fixed for you, and have you upgraded to 3.2.0-21-generic-pae #34?

[Andreas Hasenack (ahasenack)]

@Joseph, at first I suspected so. But then I booted into the previous kernel and the problem was still there, so I disabled wifi-n and booted back into 3.2.0-21-generic-pae #34. Now, I can't be sure what the previous kernel was (before the upgrade), I might have skipped a release, but the "old" one I have installed now is boot/vmlinuz-3.2.0-20-generic-pae.

[Manuel Carro (mcarro)]

In anwer to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/948235/comments/14 (Andreas Hasenack): how are you disabling 11n? I have added /etc/modprobe.d/local.conf with contents

options iwlwifi swcrypto=1 11n_disable=1

Is there a way to ensure that the options have been parsed and sent to the kernel module? Also, I am experiencing disconnections with a WAP which has no 'n' capabilities. That is consistent with having disabled 'n' capabilities and experiencing connection dropping. So my problem might (only might - I am not sure) be not due to 'n' being enabled.

[Manuel Carro (mcarro)]

In answer to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/948235/comments/15 (Joseph Salisbury): I was experiencing disconnections since previous 3.2.0 versions (maybe since 3.2.0-16 or so?)

[Jamie Strandboge (jdstrand)]

Dropped connections are back after upgrade to the following kernel:

$ cat /proc/version_signature
Ubuntu 3.2.0-21.34-generic 3.2.13

Then doing a cold reboot. With the previous 3.2.0-20.32, I did have a couple of disconnects, but this was over the course of a week or so and I wasn't sure if it was something else.

[Jamie Strandboge (jdstrand)]

Since several people are affected by this, I am ging to mark this back to 'Confirmed'. Please instruct if you want to handle this bug differently.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Joseph Salisbury (jsalisbury)]

Can folks affected by this bug test the latest Precise kernel(3.2.0-22.35
) and report back if the connection drops still happen?

[Manuel Carro (mcarro)]

@ Joseph Salisbury: I tested yesterday and the connection drops. It
is actually worst in my case: it does not even connect, or it does
connect and the connection drops immediately. BTW this has been
happening since some versions ago.

I am wondering if I am testing with an adequate setup. I am running
Oneiric. I download the kernel from

git://kernel.ubuntu.com/ubuntu/ubuntu-precise.git

and compile with

fakeroot debian/rules clean
fakeroot debian/rules binary-headers binary-generic

Is there anything special I should do / install? I have a Dell
Latitude E6510 with a Centrino N 6200 WiFi adapter.

Best!

[Andreas Hasenack (ahasenack)]

I upgraded to 3.2.0-22.35 on precise. Will need a few days to get a good feeling about the wifi state. So far, no drops.

[Joseph Salisbury (jsalisbury)]

@Manuel,

The latest Precise kernel is actually already built and can be downloaded from(Look under Builds for your particular arch):

https://launchpad.net/ubuntu/+source/linux/3.2.0-22.35

Can you try a pre-built kernel and see if you still have issues?

[Andreas Hasenack (ahasenack)]

Didn't work for me already, the connection was very bad in voice and video calls. I'm back to wifi-g.

[Manuel Carro (mcarro)]

I am sorry to say it didn't work for me. It does not manage to connect. Note: I only installed the image and the headers - not all the rest of the packages which were produced by the build.

BTW, what puzzles me is that the ubuntu 12.04 Beta from 4 days ago does boot and connect in the very same machine with no apparent problems.

[Jamie Strandboge (jdstrand)]

Booted into 3.2.0-22.35-generic. Will report back after a few days.

[krutoileshii (krutoileshii)]

3.2.0-22.24 still has this problem. can't test 3.2.0-22.35 until the sources are in the repos as i need to compile other drivers first.

the only difference for me is that it's on the rt2800 hardware.

happens on about hourly basis.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Jamie Strandboge (jdstrand)]

FYI, I have been running 3.2.0-22.35-generic for several days without 'options iwlwifi 11n_disable=1 swcrypto=1'. Initially I did have some problems and then came across https://bugzilla.redhat.com/show_bug.cgi?id=753482 which is a bug in network manager in some IPv6 environments that have a buggy radvd. I made some changes to my radvd.conf file and things have been solid. Please consider the bug resolved on my end at this point, unless I comment again. Unfortunately, I know that bug #911059 affected me and was fixed. I'm guessing I hit two bugs one after the other which showed identical symptoms, but I can't say for sure at this point when the kernel portion of the bug was fixed.

[Joseph Salisbury (jsalisbury)]

Thanks, Jamie. I will mark this bug as "Fix released". If other folks have issues, I would recommend opening a new bug, so we can gather your hardware specific information.