nvcc bug (CUDA compiler) Used -deviceemu command which allow me to run a simulated graphiccard on a machine without a nVidia graphiccard that support CUDA
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
When I runs the simulation Ubuntu comes with an error - a popup window tells that Ubuntu had detected a kernel failure.
I cannot much more about the failure :-(
ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'ICH6'/'Intel ICH6 with AD1981B at irq 17'
Mixer name : 'Analog Devices AD1981B'
Components : 'AC97a:41445374'
Controls : 34
Simple ctrls : 23
CurrentDmesg:
[ 29.926170] [drm] Setting GART location based on new memory map
[ 29.927981] [drm] Loading R400 Microcode
[ 29.928059] [drm] Num pipes: 2
[ 29.928068] [drm] writeback test succeeded in 1 usecs
[ 38.208021] eth1: no IPv6 routers present
Date: Thu Jan 7 14:36:52 2010
DistroRelease: Ubuntu 9.10
Failure: oops
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Lsusb:
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Package: linux-image-
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.24
RfKill:
SourcePackage: linux
Tags: kernel-oops
Title: WARNING: at /build/
Uname: Linux 2.6.31-14-generic i686
dmi.bios.date: 09/09/2005
dmi.bios.vendor: Phoenix
dmi.bios.version: AVD-F05
dmi.board.version: Not Applicable
dmi.chassis.
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.
dmi.modalias: dmi:bvnPhoenix:
dmi.product.
Hi jesper,
The warning reported here typically indicates that it took longer for your system to resume from suspend than expected. I believe there is a 5 sec barrier which your system likely exceeded. Typically you'll see something similar to "PM: resume devices took 8.664 seconds" in your dmesg output when this happens. A patch to prevent this warning has been applied via bug 464552. As a result I'm marking this as a duplicate to bug 464552. Please continue to track this issue at that report. Thanks!
[This is an automated message. Apologies if it has reached you inappropriately.]