BUG: scheduling while atomic: gnome-session/1313/0x10000001
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
kernel bug
ProblemType: KernelOops
DistroRelease: Ubuntu 10.10
Package: linux-image-
Regression: Yes
Reproducible: Yes
ProcVersionSign
Uname: Linux 2.6.35-16-generic i686
NonfreeKernelMo
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
CRDA: Error: [Errno 2] Нет такого файла или каталога
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfa000000 irq 44'
Mixer name : 'Realtek ALC662 rev1'
Components : 'HDA:10ec0662,
Controls : 34
Simple ctrls : 18
Card1.Amixer.info:
Card hw:1 'CA0106'/'Audigy SE [SB0570] at 0xd000 irq 18'
Mixer name : 'CA0106'
Components : ''
Controls : 35
Simple ctrls : 18
Date: Fri Aug 20 18:05:23 2010
Failure: oops
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
ppp0 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. P31-S3G
ProcCmdLine: BOOT_IMAGE=
RelatedPackageV
RfKill:
SourcePackage: linux
Title: BUG: scheduling while atomic: gnome-session/
dmi.bios.date: 09/14/2007
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F1
dmi.board.name: P31-S3G
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSof
dmi.product.name: P31-S3G
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
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 620810, 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. Feel free to continue to report any other bugs you may find.