BUG: scheduling while atomic: swapper/0/0x10000200
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Low
|
Unassigned |
Bug Description
Я не читаю и не пишу по английски.
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
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/pcmC0D6c: Slmodemd 1106 F...m slmodemd
/dev/snd/pcmC0D6p: Slmodemd 1106 F...m slmodemd
CRDA: Error: [Errno 2] Нет такого файла или каталога
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 22'
Mixer name : 'Realtek ALC660-VD'
Components : 'HDA:10ec0660,
Controls : 18
Simple ctrls : 12
Date: Wed Feb 24 19:24:16 2010
DistroRelease: Ubuntu 10.04
Failure: oops
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: ASUSTeK Computer Inc. F3Sv
NonfreeKernelMo
Package: linux-image-
ProcCmdLine: BOOT_IMAGE=
ProcVersionSign
Regression: Yes
RelatedPackageV
Reproducible: Yes
SourcePackage: linux
TestedUpstream: Yes
Title: BUG: scheduling while atomic: swapper/
Uname: Linux 2.6.32-14-generic i686
dmi.bios.date: 01/18/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 208
dmi.board.
dmi.board.name: F3Sv
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: F3Sv
dmi.product.
dmi.sys.vendor: ASUSTeK Computer Inc.
First, I'm sorry but I only speak English. I hope you will be able to translate the following as necessary.
Please install the kernel at http:// people. canonical. com/~cndougla/ sched_trace/. Reboot into it, then do the following:
# echo function >/sys/kernel/ debug/tracing/ current_ tracer debug/tracing/ options/ latency- format debug/tracing/ tracing_ enabled
# ech0 1 >/sys/kernel/
# echo 1 >/sys/kernel/
Then do whatever you need to trigger the issue. If you don't know how to trigger the issue, you can continue using the computer until the bug is triggered, but it may run a little slower. Once the bug has been triggered, do:
# cat /sys/kernel/ debug/tracing/ trace | bzip2 >/tmp/trace.bz2
Finally, attach the trace.bz2 file to this bug so we can take a look.
Thanks