"EVO Push buffer channel allocation failed" after suspend/resume
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nvidia-graphics-drivers-180 (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: xorg
This happens after a suspend/resume cycle only. That is, everything works fine until I suspend and then resume. On the resume, Xorg crashes with:
(EE) NVIDIA(0): EVO Push buffer channel allocation failed
(EE) NVIDIA(0): *** Aborting ***
(EE) NVIDIA(0): Failed to allocate EVO DMA push buffer
(EE) NVIDIA(0): *** Aborting ***
Backtrace:
0: X(xorg_
1: X(xf86SigHandle
2: [0x52c400]
Saw signal 11. Server aborting.
Segmentation fault
Trying to start Xorg again yields:
X.Org X Server 1.6.4
Release Date: 2009-9-27
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-23-server i686 Ubuntu
Current Operating System: Linux brian-laptop 2.6.31-19-generic #56-Ubuntu SMP Thu Jan 28 01:26:53 UTC 2010 i686
Kernel command line: root=/dev/
Build Date: 14 November 2009 05:48:26PM
xorg-server 2:1.6.4-2ubuntu4.1 (buildd@)
Before reporting problems, check http://
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/
(==) Using config file: "/etc/X11/
NVIDIA: could not open the device file /dev/nvidia0 (Input/output error).
(EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device PCI:1:0:0.
(EE) NVIDIA(0): Please check your system's kernel log for additional error
(EE) NVIDIA(0): messages and refer to Chapter 8: Common Problems in the
(EE) NVIDIA(0): README for additional information.
(EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device!
NVIDIA: could not open the device file /dev/nvidia0 (Input/output error).
(EE) NVIDIA(1): Failed to initialize the NVIDIA graphics device PCI:1:0:0.
(EE) NVIDIA(1): Please check your system's kernel log for additional error
(EE) NVIDIA(1): messages and refer to Chapter 8: Common Problems in the
(EE) NVIDIA(1): README for additional information.
(EE) NVIDIA(1): Failed to initialize the NVIDIA graphics device!
(EE) Screen(s) found, but none have a usable configuration.
Fatal server error:
no screens found
Please consult the The X.Org Foundation support
at http://
for help.
Please also check the log file at "/var/log/
ddxSigGiveUp: Closing log
with the following added to dmesg as a result:
[ 1209.459632] NVRM: RmInitAdapter failed! (0x26:0x38:1096)
[ 1209.459640] NVRM: rm_init_adapter(0) failed
[ 1213.604892] NVRM: RmInitAdapter failed! (0x26:0x38:1096)
[ 1213.604907] NVRM: rm_init_adapter(0) failed
ProblemType: Bug
Architecture: i386
Date: Mon Feb 22 14:08:26 2010
DistroRelease: Ubuntu 9.10
MachineType: TOSHIBA TECRA M9
NonfreeKernelMo
Package: xorg 1:7.4+3ubuntu10
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: root=/dev/
ProcEnviron:
LANG=en_CA.UTF-8
SHELL=/bin/bash
ProcVersionSign
RelatedPackageV
xserver-xorg 1:7.4+3ubuntu10
libgl1-mesa-glx 7.6.0-1ubuntu4
libdrm2 2.4.14-1ubuntu1
xserver-
xserver-
SourcePackage: xorg
Uname: Linux 2.6.31-19-generic i686
dmi.bios.date: 10/01/2007
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 1.50
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.
dmi.modalias: dmi:bvnTOSHIBA:
dmi.product.name: TECRA M9
dmi.product.
dmi.sys.vendor: TOSHIBA
fglrx: Not loaded
system:
distro: Ubuntu
architecture: i686kernel: 2.6.31-19-generic
xkbcomp:
Error: command ['xkbcomp', ':0', '-w0', '-'] failed with exit code 1: Error: Cannot open display ":0"
affects: | xorg (Ubuntu) → nvidia-graphics-drivers-180 (Ubuntu) |
tags: | added: karmic |
This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?
If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under natty, please tag the bug 'natty'
so it's easier for us to track.