BUG: scheduling while atomic: swapper/0/0x10000200

Bug #527176 reported by Ashendel
8
This bug affects 1 person
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/controlC0: Slmodemd 1106 F.... slmodemd
                      ashendel 1779 F.... pulseaudio
 /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,10431339,00100001 HDA:10573055,10431316,00100700'
   Controls : 18
   Simple ctrls : 12
Date: Wed Feb 24 19:24:16 2010
DistroRelease: Ubuntu 10.04
Failure: oops
HibernationDevice: RESUME=UUID=4856c506-8a20-4fa9-9f19-babf4c4a6397
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
NonfreeKernelModules: nvidia
Package: linux-image-2.6.32-14-generic 2.6.32-14.20
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-14-generic root=UUID=8208359e-0659-4226-a337-4c1f24136b0c ro quiet splash
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
Regression: Yes
RelatedPackageVersions: linux-firmware 1.30
Reproducible: Yes
SourcePackage: linux
TestedUpstream: Yes
Title: BUG: scheduling while atomic: swapper/0/0x10000200
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.asset.tag: ATN12345678901234567
dmi.board.name: F3Sv
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr208:bd01/18/2008:svnASUSTeKComputerInc.:pnF3Sv:pvr1.0:rvnASUSTeKComputerInc.:rnF3Sv:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: F3Sv
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

Revision history for this message
Ashendel (ashendel) wrote :
Revision history for this message
Chase Douglas (chasedouglas) wrote :

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
# ech0 1 >/sys/kernel/debug/tracing/options/latency-format
# echo 1 >/sys/kernel/debug/tracing/tracing_enabled

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

Changed in linux (Ubuntu):
status: New → Incomplete
importance: Undecided → Low
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.