WARNING: at /build/buildd/linux-2.6.32/net/wireless/core.c:614 wdev_cleanup_work+0xa7/0xd0 [cfg80211]()

[napster]

1

ProblemType: KernelOops
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
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: napster 1663 F.... pulseaudio
 /dev/snd/pcmC0D0p: napster 1663 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0x92400000 irq 22'
   Mixer name : 'Conexant CX20561 (Hermosa)'
   Components : 'HDA:14f15051,103c30d9,00100000'
   Controls : 13
   Simple ctrls : 7
Date: Wed Mar 24 07:35:56 2010
DistroRelease: Ubuntu 10.04
Failure: oops
HibernationDevice: RESUME=UUID=3a53b137-c48f-4d93-a3cc-6989c3c8d5ea
MachineType: Hewlett-Packard Compaq Presario C700 Notebook PC
Package: linux-image-2.6.32-16-generic
ProcCmdLine: root=UUID=ee2c5d20-94f2-4dc4-9b75-bbf9ac3faf02 ro quiet splash
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
Regression: Yes
RelatedPackageVersions: linux-firmware 1.33
Reproducible: Yes
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
TestedUpstream: Yes
Title: WARNING: at /build/buildd/linux-2.6.32/net/wireless/core.c:614 wdev_cleanup_work+0xa7/0xd0 [cfg80211]()
Uname: Linux 2.6.32-16-generic i686
WifiSyslog:

[Mynk (mr-mynk)]

I got the same problem when trying to get the wireless to work. I have seen issues with my wireless in the last few days.

[Gabe Gorelick (gabegorelick)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 528688, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.