WARNING: at /build/buildd/linux-2.6.32/net/wireless/core.c:614 wdev_cleanup_work+0xe9/0x110 [cfg80211]()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
After the last 10.04 Beta kernel update (-19), this message appears after resume from suspend.
ProblemType: KernelOops
DistroRelease: Ubuntu 10.04
Package: linux-image-
Regression: Yes
Reproducible: Yes
ProcVersionSign
Uname: Linux 2.6.32-19-generic x86_64
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
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
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 0xdb400000 irq 22'
Mixer name : 'Intel G45 DEVIBX'
Components : 'HDA:10ec0275,
Controls : 8
Simple ctrls : 4
Date: Fri Apr 2 17:53:53 2010
Failure: oops
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
MachineType: Sony Corporation VPCS111FM
ProcCmdLine: BOOT_IMAGE=
RelatedPackageV
SourcePackage: linux
Title: WARNING: at /build/
dmi.bios.date: 12/16/2009
dmi.bios.vendor: INSYDE
dmi.bios.version: R0270Q3
dmi.board.
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.
dmi.modalias: dmi:bvnINSYDE:
dmi.product.name: VPCS111FM
dmi.product.
dmi.sys.vendor: Sony Corporation
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.