iwlagn degrades quickly during normal wifi session
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Fix Released
|
High
|
|||
Release Notes for Ubuntu |
Fix Released
|
High
|
Unassigned | ||
linux-firmware (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
Maverick |
Won't Fix
|
Undecided
|
Unassigned | ||
Natty |
Won't Fix
|
Undecided
|
Unassigned | ||
module-init-tools (Ubuntu) |
Fix Released
|
High
|
Tim Gardner | ||
Maverick |
Fix Released
|
High
|
Leann Ogasawara | ||
Natty |
Fix Released
|
High
|
Tim Gardner |
Bug Description
I recently upgraded my lucid laptop (thinkpad X200s) to maverick. I found after the reboot that my wireless degrades after about 8 hours of ordinary use. I had 45% packet loss direct to my WAP, and this was easily cleared up by doing "modprobe -r iwlagn; modprobe iwlagn" as root.
I'd not be so quick to file this except that Paul Collins told me that he'd seen the same behavior from upstream 2.6.35.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-
Regression: Yes
Reproducible: Yes
ProcVersionSign
Uname: Linux 2.6.35-19-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
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/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf2620000 irq 47'
Mixer name : 'Conexant CX20561 (Hermosa)'
Components : 'HDA:14f15051,
Controls : 14
Simple ctrls : 7
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'
Mixer name : 'ThinkPad EC 7XHT22WW-1.04'
Components : ''
Controls : 1
Simple ctrls : 1
Card29.
Simple mixer control 'Console',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Date: Sun Sep 5 11:24:24 2010
EcryptfsInUse: Yes
HibernationDevice: RESUME=
MachineType: LENOVO 7465CTO
ProcCmdLine: root=UUID=
ProcEnviron:
LC_COLLATE=C
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageV
SourcePackage: linux
WpaSupplicantLog:
dmi.bios.date: 06/25/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 6DET55WW (3.05 )
dmi.board.name: 7465CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 7465CTO
dmi.product.
dmi.sys.vendor: LENOVO
Related branches
Changed in ubuntu-release-notes: | |
importance: | Undecided → High |
affects: | linux (Ubuntu Maverick) → linux-firmware (Ubuntu Maverick) |
Changed in ubuntu-release-notes: | |
status: | New → Fix Released |
Changed in linux-firmware (Ubuntu Natty): | |
milestone: | maverick-updates → natty-alpha-1 |
Changed in linux-firmware (Ubuntu Natty): | |
milestone: | natty-alpha-1 → natty-alpha-2 |
Changed in linux: | |
status: | Unknown → Confirmed |
Changed in linux-firmware (Ubuntu Natty): | |
milestone: | natty-alpha-2 → ubuntu-11.04-beta |
Changed in linux: | |
importance: | Unknown → High |
tags: |
added: regression-release removed: regression-potential |
Changed in module-init-tools (Ubuntu Natty): | |
assignee: | Leann Ogasawara (leannogasawara) → Tim Gardner (timg-tpi) |
milestone: | ubuntu-10.10 → none |
status: | Fix Released → In Progress |
Changed in module-init-tools (Ubuntu Natty): | |
milestone: | none → ubuntu-11.04-beta-2 |
Changed in module-init-tools (Ubuntu Natty): | |
status: | In Progress → Fix Committed |
Changed in module-init-tools (Ubuntu Natty): | |
status: | Fix Committed → Fix Released |
Changed in linux-firmware (Ubuntu Natty): | |
milestone: | ubuntu-11.04-beta-1 → ubuntu-11.04-beta-2 |
Changed in linux: | |
status: | Confirmed → Fix Released |
As Nick says, I ran into a problem with these symptoms on an X200, bb342f59067d0d8 3cec9b766e
with the same type of wireless adapter. I tried both 2.6.35 and
2.6.35.2 at the time. Commit 3ee378d7e0dfdb9
from 2.6.35.4, which I see is included in the most recent maverick
kernel upload (2.6.35-20.29; binaries pending publication when I
checked), doesn't look immediately inapplicable, so I'm trying out
vanilla 2.6.35.4 to see if I run into the problem again.