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 105814] New: Frequent Xorg lockups with GT710 after rad or write faults
Date: Fri, 30 Mar 2018 01:49:11 +0000	[thread overview]
Message-ID: <bug-105814-8800@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 105814
           Summary: Frequent Xorg lockups with GT710 after rad or write
                    faults
           Product: xorg
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
          Reporter: zarniwhoop-XZoyATsUNX5Wk0Htik3J/w@public.gmane.org
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org

This is my second problem on my new machine (ryzen, GT710 (GK208B) - I needed a
vga connector), linux-4.15.12, gcc-7.3.0, glibc-2.27, mesa-17.3.7,
xorg-server-1.19.6, mouveau-1.0.15).

I am seeing frequent lockups in X (keyboard and mouse not working, but
MagicSysRQ works). Arguably this is similar to #104448, but I'm using "regular"
glibc.

There is no particular pattern to when this bug bites - the first time, I had
just built icewm, rerun startx, and was evaluating the various themes. Later, I
was installing firefox extension ublock-origin. As with the other bug I just
raised (105813) I tried using the modesetting Xorg driver instead of nouveau,
but the problem occurred again (left it compiling, came back to a frozen
xscreensaver). After that I turned off xscreensaver and it has now been up for
perhaps 2 hours, but will maybe go down again soon ;-(

From these failures I have extracted the following from my syslog, several (but
not all) show UNSUPPORTED_KIND. The 'scheduled for recovery' messages imply it
might self-correct, but it doesn't seem to.

Mar 28 18:50:05 origin kernel: [ 7715.267689] nouveau 0000:26:00.0: fifo:
FB_FLUSH_TIMEOUT
Mar 28 18:50:05 origin kernel: [ 7715.273911] nouveau 0000:26:00.0: fifo: write
fault at 0003228000 engine 1b [CE2] client 18 [GR_CE] reason 0c
[UNSUPPORTED_KIND] on channel 2 [003fbfa000 Xorg[22520]]
Mar 28 18:50:05 origin kernel: [ 7715.273921] nouveau 0000:26:00.0: fifo:
channel 2: killed
Mar 28 18:50:05 origin kernel: [ 7715.273923] nouveau 0000:26:00.0: fifo:
runlist 0: scheduled for recovery
Mar 28 18:50:05 origin kernel: [ 7715.273934] nouveau 0000:26:00.0: fifo:
engine 0: scheduled for recovery
Mar 28 18:50:05 origin kernel: [ 7715.273938] nouveau 0000:26:00.0: fifo:
engine 6: scheduled for recovery
Mar 28 18:50:05 origin kernel: [ 7715.273965] nouveau 0000:26:00.0:
Xorg[22520]: channel 2 killed!

Mar 28 19:33:30 origin kernel: [ 2215.090852] nouveau 0000:26:00.0: fifo: read
fault at 000171c000 engine 1b [CE2] client 18 [GR_CE] reason 02 [PTE] on
channel 2 [003fbfa000 Xorg[1576]]
Mar 28 19:33:30 origin kernel: [ 2215.090861] nouveau 0000:26:00.0: fifo:
channel 2: killed
Mar 28 19:33:30 origin kernel: [ 2215.090863] nouveau 0000:26:00.0: fifo:
runlist 0: scheduled for recovery
Mar 28 19:33:30 origin kernel: [ 2215.090873] nouveau 0000:26:00.0: fifo:
engine 0: scheduled for recovery
Mar 28 19:33:30 origin kernel: [ 2215.090877] nouveau 0000:26:00.0: fifo:
engine 6: scheduled for recovery
Mar 28 19:33:30 origin kernel: [ 2215.090891] nouveau 0000:26:00.0: Xorg[1576]:
channel 2 killed!

Mar 28 22:27:26 origin kernel: [ 3793.782622] nouveau 0000:26:00.0: fifo:
CHSW_ERROR 00000004
Mar 28 22:27:27 origin kernel: [ 3794.949062] nouveau 0000:26:00.0: fifo:
CHSW_ERROR 00000002
Mar 28 22:27:27 origin kernel: [ 3794.949066] nouveau 0000:26:00.0: fifo:
FB_FLUSH_TIMEOUT
Mar 28 22:27:27 origin kernel: [ 3795.465905] nouveau 0000:26:00.0: fifo:
CHSW_ERROR 00000002
Mar 28 22:27:27 origin kernel: [ 3795.465909] nouveau 0000:26:00.0: fifo:
FB_FLUSH_TIMEOUT
Mar 28 22:27:27 origin kernel: [ 3795.532524] nouveau 0000:26:00.0: fifo:
FB_FLUSH_TIMEOUT
Mar 28 22:27:27 origin kernel: [ 3795.537738] nouveau 0000:26:00.0: fifo: read
fault at 0001f08000 engine 1b [CE2] client 18 [GR_CE] reason 0c
[UNSUPPORTED_KIND] on channel 2 [003fbfa000 Xorg[1290]]
Mar 28 22:27:27 origin kernel: [ 3795.537745] nouveau 0000:26:00.0: fifo:
channel 2: killed
Mar 28 22:27:27 origin kernel: [ 3795.537747] nouveau 0000:26:00.0: fifo:
runlist 0: scheduled for recovery
Mar 28 22:27:27 origin kernel: [ 3795.537757] nouveau 0000:26:00.0: fifo:
engine 0: scheduled for recovery
Mar 28 22:27:27 origin kernel: [ 3795.537761] nouveau 0000:26:00.0: fifo:
engine 6: scheduled for recovery

Mar 29 21:19:49 origin kernel: [13387.804276] nouveau 0000:26:00.0: fifo: read
fault at 0004740000 engine 1b [CE2] client 18 [GR_CE] reason 0c
[UNSUPPORTED_KIND] on channel 2 [003fbfa000 Xorg[1343]]
Mar 29 21:19:49 origin kernel: [13387.804286] nouveau 0000:26:00.0: fifo:
channel 2: killed
Mar 29 21:19:49 origin kernel: [13387.804289] nouveau 0000:26:00.0: fifo:
runlist 0: scheduled for recovery
Mar 29 21:19:49 origin kernel: [13387.804299] nouveau 0000:26:00.0: fifo:
engine 0: scheduled for recovery
Mar 29 21:19:49 origin kernel: [13387.804303] nouveau 0000:26:00.0: fifo:
engine 6: scheduled for recovery
Mar 29 21:19:49 origin kernel: [13387.804308] nouveau 0000:26:00.0: Xorg[1343]:
channel 2 killed!

(that last one was using modesetting, the others were using the Xorg nouveau
driver).

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

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

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

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

             reply	other threads:[~2018-03-30  1:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-30  1:49 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-105814-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2019-12-04  9:37   ` [Bug 105814] Frequent Xorg lockups with GT710 after rad or write faults 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-105814-8800@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.