Bug 55258 - nouveau failure on resume (reloc wait_idle failed)
Summary: nouveau failure on resume (reloc wait_idle failed)
Status: RESOLVED DUPLICATE of bug 50121
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-23 21:30 UTC by Mr-4
Modified: 2012-12-26 19:39 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Mr-4 2012-09-23 21:30:28 UTC
When I resume from hibernate, I get the following error after which the whole system either grinds to a halt or I am forced to log in and then the system crashes:

kernel: [drm] nouveau 0000:01:00.0: reloc wait_idle failed: -16
kernel: [drm] nouveau 0000:01:00.0: reloc apply: -16
kernel: [drm] nouveau 0000:01:00.0: reloc wait_idle failed: -16
kernel: [drm] nouveau 0000:01:00.0: reloc apply: -16
kernel: [drm] nouveau 0000:01:00.0: reloc wait_idle failed: -16
kernel: [drm] nouveau 0000:01:00.0: reloc apply: -16
kernel: [drm] nouveau 0000:01:00.0: reloc wait_idle failed: -16
kernel: [drm] nouveau 0000:01:00.0: reloc apply: -16

Here is some information on my card you may find useful:

kernel: [drm] nouveau 0000:01:00.0: Detected an NV40 generation card (0x049200a2)
kernel: [drm] nouveau 0000:01:00.0: Checking PRAMIN for VBIOS
kernel: [drm] nouveau 0000:01:00.0: ... BIOS checksum invalid
kernel: [drm] nouveau 0000:01:00.0: Checking PROM for VBIOS
kernel: [drm] nouveau 0000:01:00.0: ... appears to be valid
kernel: [drm] nouveau 0000:01:00.0: Using VBIOS from PROM
kernel: [drm] nouveau 0000:01:00.0: BIT BIOS found
kernel: [drm] nouveau 0000:01:00.0: Bios version 05.71.22.21
kernel: [drm] nouveau 0000:01:00.0: TMDS table version 1.1
kernel: [drm] nouveau 0000:01:00.0: TMDS table script pointers not stubbed
kernel: [drm] nouveau 0000:01:00.0: MXM: no VBIOS data, nothing to do
kernel: [drm] nouveau 0000:01:00.0: DCB version 3.0

The above error happens every 2nd time I resume from hibernate - without fail, like a clockwork. The first time the resume is OK - no problems. The second time resume always fails with the above error.

The nouveau version is 1.0.0 20120316.
Comment 1 Raphaël Droz 2012-12-23 21:55:08 UTC
Happens here, using a NV34 [GeForce FX 5200] on AMD64
suspend works, hibernate works using the console (but didn't try several attempts yet).
But when hibernate resumes X is a bit garbled then I'm stuck.


Dec 23 22:36:47 b1b1 kernel: [  130.943828] EXT4-fs (sda1): re-mounted. Opts: commit=0
Dec 23 22:36:49 b1b1 kernel: [  133.624015] nouveau E[     DRM] reloc wait_idle failed: -16
Dec 23 22:36:49 b1b1 kernel: [  133.624025] nouveau E[     DRM] reloc apply: -16
Dec 23 22:36:49 b1b1 acpid: client connected from 1429[0:0]
Dec 23 22:36:49 b1b1 acpid: 1 client rule loaded
Dec 23 22:36:49 b1b1 kernel: [  133.626369] nouveau  [     DRM] index 0
Dec 23 22:36:49 b1b1 kernel: [  133.663802] nouveau  [     DRM] native mode from largest: 1280x1024@75
Dec 23 22:36:52 b1b1 kernel: [  136.720020] nouveau E[     DRM] reloc wait_idle failed: -16
Dec 23 22:36:52 b1b1 kernel: [  136.720027] nouveau E[     DRM] reloc apply: -16
Dec 23 22:37:01 b1b1 kernel: [  145.725096] nouveau E[     DRM] reloc wait_idle failed: -16
Dec 23 22:37:01 b1b1 kernel: [  145.725109] nouveau E[     DRM] reloc apply: -16
Dec 23 22:37:04 b1b1 kernel: [  148.724012] nouveau E[     DRM] reloc wait_idle failed: -16
Dec 23 22:37:04 b1b1 kernel: [  148.724015] nouveau E[     DRM] reloc apply: -16
Dec 23 22:37:07 b1b1 kernel: [  151.724018] nouveau E[     DRM] reloc wait_idle failed: -16
Dec 23 22:37:07 b1b1 kernel: [  151.724027] nouveau E[     DRM] reloc apply: -16
Dec 23 22:37:08 b1b1 kernel: [  152.467763] SysRq : Emergency Sync

pm_trace wasn't very helpful here (resume *is* successful)
[    0.807743]   Magic number: 0:455:740
[    0.807803]   hash matches drivers/base/power/main.c:645

x11-drivers/xf86-video-nouveau 1.0.4
media-libs/mesa 9.0

maybe related to bug #50121
Comment 2 Raphaël Droz 2012-12-26 17:13:06 UTC
In my case, the issue is solved by the patch from bug #50121
Comment 3 Marcin Slusarz 2012-12-26 19:39:58 UTC

*** This bug has been marked as a duplicate of bug 50121 ***


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.