All of lore.kernel.org
 help / color / mirror / Atom feed
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: Sat, 02 Sep 2017 06:16:06 +0000	[thread overview]
Message-ID: <bug-93629-8800-xRo60QI0oO@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-93629-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


[-- Attachment #1.1: Type: text/plain, Size: 3295 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=93629

--- Comment #38 from Robb Ebright <robbt-UEAdIY/G9B/YtjvyW6yDsg@public.gmane.org> ---
I ran into a similar bug with a recent Debian install. It occurs only when I
plugged in a monitor into the DVI port. It works fine with the HDMI port as I'm
using it to type. But it freezes with the following error.

I'm installing the proprietary drivers so but I wanted to provide this
confirmation/documentation in case it is helpful to anyone trying to solve
this. In an ideal world I would use the free software drivers as well but there
is evidently some issue with the software that is causing it to crash.


1 23:07:09 dragonpunk /usr/lib/gdm3/gdm-x-session[787]: (II) systemd-logind:
got pause for 226:0
Sep  1 23:07:09 dragonpunk /usr/lib/gdm3/gdm-x-session[787]: (II)
systemd-logind: got pause for 13:67
Sep  1 23:07:09 dragonpunk /usr/lib/gdm3/gdm-x-session[787]: (II)
systemd-logind: got pause for 13:66
Sep  1 23:07:09 dragonpunk /usr/lib/gdm3/gdm-x-session[787]: (II)
systemd-logind: got pause for 13:64
Sep  1 23:07:09 dragonpunk /usr/lib/gdm3/gdm-x-session[787]: (II)
systemd-logind: got pause for 13:65
Sep  1 23:07:09 dragonpunk /usr/lib/gdm3/gdm-x-session[787]: (II)
systemd-logind: got pause for 13:68
Sep  1 23:07:09 dragonpunk kernel: [74586.320157] nouveau 0000:01:00.0: fifo:
write fault at 000031d000 engine 05 [BAR3] client 08 [BAR_WRITE] reason 02
[PAGE_NOT_PRESENT] on channel -1 [003ff35000 unknown]
Sep  1 23:07:09 dragonpunk kernel: [74586.320169] nouveau 0000:01:00.0: fifo:
INTR 08000000
Sep  1 23:07:09 dragonpunk kernel: [74586.825813] nouveau 0000:01:00.0: gr:
TRAP ch 2 [003fd30000 systemd-logind[448]]
Sep  1 23:07:09 dragonpunk kernel: [74586.825826] nouveau 0000:01:00.0: gr:
GPC0/TPC0/TEX: 80000041
Sep  1 23:07:09 dragonpunk kernel: [74586.825834] nouveau 0000:01:00.0: gr:
GPC0/TPC1/TEX: 80000041
Sep  1 23:07:09 dragonpunk kernel: [74586.825846] nouveau 0000:01:00.0: gr:
GPC1/TPC0/TEX: 80000041
Sep  1 23:07:09 dragonpunk kernel: [74586.825854] nouveau 0000:01:00.0: gr:
GPC1/TPC2/TEX: 80000041
Sep  1 23:07:09 dragonpunk kernel: [74586.825866] nouveau 0000:01:00.0: fifo:
read fault at 0002f61000 engine 00 [PGRAPH] client 01 [GPC1/TEX] reason 02
[PAGE_NOT_PRESENT] on channel 2 [003fd30000 systemd-logind[448]]
Sep  1 23:07:09 dragonpunk kernel: [74586.825868] nouveau 0000:01:00.0: fifo:
gr engine fault on channel 2, recovering...
Sep  1 23:07:09 dragonpunk kernel: [74586.881742] nouveau 0000:01:00.0: fifo:
write fault at 0000278000 engine 00 [PGRAPH] client 0f [GPC0/PROP] reason 02
[PAGE_NOT_PRESENT] on channel 3 [003fc83000 Xwayland[602]]
Sep  1 23:07:09 dragonpunk kernel: [74586.881746] nouveau 0000:01:00.0: fifo:
gr engine fault on channel 3, recovering...
Sep  1 23:07:48 dragonpunk gnome-shell[566]: Failed to apply DRM plane
transform 0: Invalid argument
Sep  1 23:08:06 dragonpunk gnome-shell[566]: Failed to apply DRM plane
transform 0: Invalid argument
Sep  1 23:08:06 dragonpunk gnome-shell[566]: Failed to apply DRM plane
transform 0: Invalid argument
Sep  1 23:08:19 dragonpunk gnome-shell[566]: Failed to apply DRM plane
transform 0: Invalid argument

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 4133 bytes --]

[-- Attachment #2: Type: text/plain, Size: 154 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2017-09-02  6:16 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
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 [this message]
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-xRo60QI0oO@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.