Bug 87436 - INVALID_STATE [UNK05] chid 0 mthd 0x0080 data 0x00000000
Summary: INVALID_STATE [UNK05] chid 0 mthd 0x0080 data 0x00000000
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: 7.7 (2012.06)
Hardware: Other All
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
Depends on:
Reported: 2014-12-18 11:06 UTC by Laurent Bigonville
Modified: 2019-12-04 08:52 UTC (History)
6 users (show)

See Also:
i915 platform:
i915 features:

dmesg output (21.29 KB, text/plain)
2014-12-18 11:06 UTC, Laurent Bigonville
no flags Details
full dmesg (117.81 KB, text/plain)
2014-12-18 11:29 UTC, Laurent Bigonville
no flags Details
full dmesg output, really (257.54 KB, text/plain)
2014-12-18 13:02 UTC, Laurent Bigonville
no flags Details
F-21_journalctl_grep_nouveau (41.36 KB, text/plain)
2014-12-21 19:29 UTC, Pavel Malyshev
no flags Details
Complete dmesg (72.35 KB, text/plain)
2015-05-06 13:46 UTC, Michael Mercier
no flags Details
journal_grep_nouveau (258.84 KB, text/plain)
2015-05-06 13:53 UTC, Michael Mercier
no flags Details

Description Laurent Bigonville 2014-12-18 11:06:07 UTC
Created attachment 110978 [details]
dmesg output


On my debian unstable (kernel 3.18, nouveau driver: 1.0.11, xserver:, I'm seeing the following messages in dmesg:

[ 2699.275904] nouveau E[   PDISP][0000:01:00.0] INVALID_STATE [UNK05] chid 0 mthd 0x0080 data 0x00000000
[ 2699.275909] nouveau E[   PDISP][0000:01:00.0] Core:
[ 2699.275915] nouveau E[   PDISP][0000:01:00.0]        0x0084: 0x02580320 -> 0x00000000
[ 2699.275921] nouveau E[   PDISP][0000:01:00.0]        0x0088: 0xf0000000
[ 2699.275923] nouveau E[   PDISP][0000:01:00.0] Core - DAC 0:

This looks like bug #85160 or bug #84203 but the proposed patches on these bugs seems to be integrated on the version of the kernel I'm using
Comment 1 Roy 2014-12-18 11:14:27 UTC
Please post the full dmesg output, rather than filtered on nouveau.
Comment 2 Laurent Bigonville 2014-12-18 11:29:05 UTC
Created attachment 110979 [details]
full dmesg
Comment 3 Roy 2014-12-18 11:39:47 UTC
(In reply to Laurent Bigonville from comment #2)
> Created attachment 110979 [details]
> full dmesg

Unfortunately the start of the log (containing, amongst others, the full kernel version and kernel parameters) have fallen off. Could you paste them as well please?

One thing I did notice is that, other than for bug #84203, you were not attempting to resume from suspend when the error occured. What was the action you performed about 45 minutes after boot? Did you plug in a monitor, or disable one, or change your resolution?
Comment 4 Laurent Bigonville 2014-12-18 13:02:13 UTC
Created attachment 110987 [details]
full dmesg output, really

third time's a charm...

I don't remember doing anything special regarding the video output at that time, just running dmesg after updating my kernel to see if the wifi disconnections messages were gone (as you can see they aren't, but that's an other story).

I didn't notice any functional issues after seeing these messages, but I still thought it was interesting to report them...
Comment 5 Roy 2014-12-18 23:09:34 UTC
It is, looks all good. When was this problem introduced? Do you feel this is a regression? If so, do you think you can do a kernel bisect to find the exact commit that introduced this problem?
Comment 6 Pavel Malyshev 2014-12-21 19:28:06 UTC
I'm running Fedora 21 with:
kernel: 3.17.6-300.fc21.x86_64

I have:
01:00.0 VGA compatible controller: NVIDIA Corporation G86M [GeForce 8400M GS] (rev a1)

I've caught this one:
[0000:01:00.0] INVALID_STATE [UNK05] chid 0 mthd 0x0080 data 0x00000000
[0000:01:00.0] Core:
[0000:01:00.0] 	0x0084: 0x019e02e2 -> 0x00000000
[0000:01:00.0] 	0x0088: 0xf0000000 

Screen hung (was not updated) but I was able to login to the box over SSH.

Not sure if it the same bug. Let me know if I need to open another one.

Attached: journalctl -ab1 | grep -i nouveau
Comment 7 Pavel Malyshev 2014-12-21 19:29:10 UTC
Created attachment 111128 [details]
Comment 8 Johan Vervloet 2015-04-23 09:13:53 UTC
I have the same issue on Fedora 22 beta. My graphical controller is

01:00.0 VGA compatible controller: NVIDIA Corporation GT215GLM [Quadro FX 1800M] (rev a2)
Comment 9 Michael Mercier 2015-05-06 13:46:14 UTC
Created attachment 115592 [details]
Complete dmesg
Comment 10 Michael Mercier 2015-05-06 13:52:31 UTC
I have the same problem on Arch Linux. Some information:

uname -a
Linux laptours 4.0.1-1-ARCH #1 SMP PREEMPT Wed Apr 29 12:00:26 CEST 2015 x86_64 GNU/Linux

Packages versions:
xf86-video-nouveau 1.0.11-3
mesa 10.5.4-1
xorg-server 1.17.1-5

I already have posted my dmesg.

I sometimes get a complete xorg freeze. I post the journalctl output grep with nouveau
Comment 11 Michael Mercier 2015-05-06 13:53:28 UTC
Created attachment 115593 [details]
Comment 12 rcoe 2015-09-11 15:31:30 UTC
I see this issue as well. 
I'm not sure if it's related to the issue I'm having with resuming after suspend after N resumes.
I've started counting the number of suspend resume cycles.
On the 21st resume, I got this message today.
[997713.432479] nouveau  [     DRM] resuming console...
[997713.432546] nouveau E[   PDISP][0000:01:00.0] INVALID_STATE 
[UNK05] chid 0 mthd 0x0080 data 0x00000000

linux 4.1.4
VGA compatible controller: NVIDIA Corporation GF108GLM [NVS 5200M] (rev a1)
Comment 13 Martin Peres 2019-12-04 08:52:59 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/156.

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.