iwlagn driver crashes in Intel 6300 when using 802.11n router

Bug #604175 reported by Bonne Eggleston
28
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I have an Intel Ultimate-N 6300 wifi card in a Dell E4310. It works perfectly fine with an 802.11g router, but causes constant dropouts with an 802.11n router (Linksys WRT610n).

The card connects to the access point fine and works well for a while. Usually under load it then stops working and a bunch of errors are printed to dmesg. After asking it to reconnect it usually works again for a while. This only appears to occur when connecting to an 802.11n router, and occurs using both 2.4GHz and 5GHz specra.

I have tested 2.6.35-rc4 from mainline (maverick build) and it has the same effect.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-23-generic 2.6.32-23.37
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-23-generic x86_64
AlsaVersion:
 Advanced Linux Sound Architecture Driver Version 1.0.23.
 Compiled on Jun 14 2010 for kernel 2.6.32-23-generic (SMP).
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: bonne 2076 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf5460000 irq 37'
   Mixer name : 'Intel G45 DEVIBX'
   Components : 'HDA:111d7605,10280410,00100104 HDA:80862804,80860101,00100000'
   Controls : 26
   Simple ctrls : 14
Date: Sun Jul 11 14:51:17 2010
HibernationDevice: RESUME=UUID=2d2a285b-d565-4b04-af6d-553c9adb5cd2
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
MachineType: Dell Inc. Latitude E4310
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-23-generic root=UUID=26b21ced-d78f-412f-bd9c-a238649ed40e ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_AU.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34.1
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
dmi.bios.date: 05/28/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A02
dmi.board.name: 0XG3JF
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA02:bd05/28/2010:svnDellInc.:pnLatitudeE4310:pvr0001:rvnDellInc.:rn0XG3JF:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E4310
dmi.product.version: 0001
dmi.sys.vendor: Dell Inc.

Revision history for this message
Bonne Eggleston (bonne) wrote :
Revision history for this message
Bonne Eggleston (bonne) wrote :

There are a bunch of backtraces in WifiSyslog.txt (including some from each of the two kernels I tested).

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Bonne,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Bonne Eggleston (bonne) wrote :

As reported in the first post, I have tested kernel 2.6.35-020635rc4-generic from the mainline repository which is listed as v2.6.35-rc4-maverick there. The same results are obtained with this kernel.

tags: removed: needs-upstream-testing
Revision history for this message
Saint DanBert (saintdanbert) wrote :

Running iwlagn v1.3.27-ks on Lucid (v10.04) I get at least one, if not several, driver crashes every eight to ten hours. This system runs the 2.6.32-24-generic-pae edition of the linux kernel.

Running iwlagn v1.3.27-ks on Jaunty (v9.04) everything wifi seems to work quite well.
This system runs the 2.6.28-19-generic edition of the linux kernel.

When I say "crash" I mean that:
** outwardly, the network seems to be running -- netmanager or wicd show connected, radio is on, etc
** ping fails to connect to anything
** dig fails to find any DNS server
** browser times out on all link attempts, etc
** armed with the above symptoms, I can check the logs and find the problems
** I must reboot to wake up the wifi network so I suspect that the driver and firmware are "hosed"

~~~ 0;-Dan

Revision history for this message
Saint DanBert (saintdanbert) wrote :

By the way, in both cases, I run the /lib/firmware/iwlwifi-4965-ucode-228.61.2.24/iwlwifi-4965-2.ucode on the Intel hardware.

~~~ 0;-Dan

Revision history for this message
Saint DanBert (saintdanbert) wrote :

Here is a copy of contents from a recent /var/log/syslog. There is more than one "crash" and system restart.
I've added blank lines to aid read-ability. See Attached file.
~~~ 0;-Dan

Revision history for this message
BenQ (benq70) wrote :

I am experiencing the same issue with similar log entries as Saint DanBert.

Dell Latitude 4310

Linux latte 2.6.32-24-generic #42-Ubuntu SMP Fri Aug 20 14:21:58 UTC 2010 x86_64 GNU/Linux

Revision history for this message
BenQ (benq70) wrote :

CORRECTION: Dell Latitude E6410

Revision history for this message
Bonne Eggleston (bonne) wrote :

I think this bug could be very similar to this one:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/630748

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.