WARNING: at /build/buildd/linux-2.6.38/drivers/gpu/drm/radeon/radeon_fence.c:248 radeon_fence_wait 0x36f/0x3e0 radeon
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Came up when I came back to my computer after leaving it unattended. The system had not gone into suspend, but video had turned itself off.
ProblemType: KernelOops
DistroRelease: Ubuntu 11.04
Package: linux-image-
Regression: No
Reproducible: No
ProcVersionSign
Uname: Linux 2.6.38-7-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/seq: timidity 1828 F.... timidity
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf0e00000 irq 52'
Mixer name : 'Realtek ALC889A'
Components : 'HDA:10ec0885,
Controls : 26
Simple ctrls : 14
Date: Tue Mar 29 16:59:29 2011
Failure: oops
Frequency: This has only happened once.
HibernationDevice: RESUME=
MachineType: Apple Computer, Inc. MacPro1,1
ProcKernelCmdLine: root=UUID=
RelatedPackageV
linux-
linux-
linux-firmware 1.49
SourcePackage: linux
Title: WARNING: at /build/
UpgradeStatus: Upgraded to natty on 2011-03-20 (9 days ago)
WpaSupplicantLog:
dmi.bios.date: 07/02/07
dmi.bios.vendor: Apple Computer, Inc.
dmi.bios.version: MP11.88Z.
dmi.board.
dmi.board.name: Mac-F4208DC8
dmi.board.vendor: Apple Computer, Inc.
dmi.board.version: PVT
dmi.chassis.
dmi.chassis.type: 2
dmi.chassis.vendor: Apple Computer, Inc.
dmi.chassis.
dmi.modalias: dmi:bvnAppleCom
dmi.product.name: MacPro1,1
dmi.product.
dmi.sys.vendor: Apple Computer, Inc.
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 #728923, 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.