WARNING: at /build/buildd/linux-2.6.32/drivers/net/wireless/iwlwifi/iwl-tx.c:1169 iwl_tx_cmd_complete+0x133/0x170 [iwlcore]()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
automatic error report
ProblemType: KernelOops
DistroRelease: Ubuntu 10.04
Package: linux-image-
Regression: Yes
Reproducible: No
ProcVersionSign
Uname: Linux 2.6.32-19-generic x86_64
NonfreeKernelMo
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
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 0xf6ffc000 irq 21'
Mixer name : 'SigmaTel STAC9228'
Components : 'HDA:83847616,
Controls : 28
Simple ctrls : 18
Date: Wed Apr 7 16:24:25 2010
Failure: oops
Frequency: This has only happened once.
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
MachineType: Dell Inc. XPS M1530
ProcCmdLine: BOOT_IMAGE=
RelatedPackageV
SourcePackage: linux
Title: WARNING: at /build/
dmi.bios.date: 11/19/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 0XR148
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: XPS M1530
dmi.sys.vendor: Dell Inc.
tags: | added: kj-triage |
I seem to be getting the same problem. There are no symptoms explained above, so let me tell you what happens to my machine:
Occasionally on suspend and resume, Network Manager won't connect to wireless networks, and if I try to do so manually then it just says "device not ready" under the Wireless section.
This doesn't happen on every suspend/resume, and there doesn't seem to be much of a pattern to it, happens around once every 1-2 weeks I'd say (I barely ever reboot unless I have to)
Previously in the Lucid cycle I was able to fix the problem with "sudo rmmod iwlagn && sleep 5 && sudo modprobe iwlagn" and this would then make the device available again and Network Manager reconnect. I don't remember which kernel was running then, I believe this worked in -16 and -17.
However, it seems that in -18 and -19 doing the above command doesn't fix the problem, and instead just brings up the apport window to submit a problem report to Launchpad and kerneloops.org. To fix the problem under these later kernels, I have to reboot the machine and then wireless works again.
Apport suggested that I test with upstream kernels, which I'm happy to do (I'm going to go and install it now), but the fairly low frequency of this issue means it may be 2-3 weeks before I can say whether it's working properly or not...