From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 93629] [NVE6] complete system freeze, PGRAPH engine fault on channel 2, SCHED_ERROR [ CTXSW_TIMEOUT ]
Date: Wed, 27 Apr 2016 09:22:28 +0000 [thread overview]
Message-ID: <bug-93629-8800-0QIrCZwNRP@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-93629-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1521 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=93629
--- Comment #18 from Alexandre Courbot <gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
Compiled and booted a 3.10 kernel in order to attempt a bisect, but the issue
showed up on that version as well:
[ 95.424646] nouveau E[ PGRAPH][0000:01:00.0] GPC ch 7 [0x000027f563
Xorg[1698]]:
[ 95.424659] nouveau E[ PGRAPH][0000:01:00.0] GPC0/TP0/MP trap:
INVALID_OPCODE
[ 95.424671] nouveau E[ PGRAPH][0000:01:00.0] GPC2/TP0/MP trap:
INVALID_OPCODE
[ 95.424805] nouveau E[ PGRAPH][0000:01:00.0] GPC ch 7 [0x000027f563
Xorg[1698]]:
[ 95.424813] nouveau E[ PGRAPH][0000:01:00.0] GPC1/TP0/MP trap:
INVALID_OPCODE
[ 95.424826] nouveau E[ PGRAPH][0000:01:00.0] GPC2/TP1/MP trap:
INVALID_OPCODE
[ 99.750909] nouveau W[ PFIFO][0000:01:00.0] unknown status 0x00000100
[ 102.082998] nouveau E[ PGRAPH][0000:01:00.0] ROP0 ch 5 [0x000027f71f
Xorg[1698]] 0x80000000 0x80000001
[ 102.083000] nouveau E[ PGRAPH][0000:01:00.0] ROP1 ch 5 [0x000027f71f
Xorg[1698]] 0x80000000 0x80000001
[ 102.083000] nouveau E[ PGRAPH][0000:01:00.0] ROP2 ch 5 [0x000027f71f
Xorg[1698]] 0x80000000 0x80000001
[ 104.045757] nouveau W[ PFIFO][0000:01:00.0] unknown status 0x00000100
[ 108.340607] nouveau W[ PFIFO][0000:01:00.0] unknown status 0x00000100
Using the external firmware, I cannot reproduce the problem on this kernel
either. So it seems like the NVE6 firmware has a long-standing bug.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2349 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2016-04-27 9:22 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 14:01 [Bug 93629] New: [NVE6] complete system freeze, PGRAPH engine fault on channel 2, SCHED_ERROR [ CTXSW_TIMEOUT ] bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-93629-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2016-01-07 14:02 ` [Bug 93629] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-07 14:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-07 14:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-07 14:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-07 14:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-07 14:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-08 11:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-20 19:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-20 19:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-20 19:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-20 19:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-20 19:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-20 19:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-05 13:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-06 2:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-13 16:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-13 17:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-15 12:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-27 9:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2016-05-11 4:46 ` bugzilla-daemon-C9EPM1l/obmE5N/NCR/djmD2FQJk+8+b
2016-05-11 15:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-12 23:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-13 10:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-13 14:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-13 14:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-13 16:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-13 17:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-13 18:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-16 8:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-17 16:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-06-25 12:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-04 18:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-04 18:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-27 14:39 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-29 10:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-21 16:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-26 0:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-08-24 15:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-09-02 6:16 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-11-18 18:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-11-21 23:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-11-21 23:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-31 11:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-31 11:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-31 11:40 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-31 11:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-31 11:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-31 12:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-31 12:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-01-25 0:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-05-27 9:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-11-06 16:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-08 22:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-08 22:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-08 11:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-08 11:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 9:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-93629-8800-0QIrCZwNRP@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox