Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1457626 - F26 Beta crashes on login with Wayland on nouveau
Summary: F26 Beta crashes on login with Wayland on nouveau
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 26
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: RejectedBlocker https://fedoraproject...
Depends On:
Blocks: F26BetaBlocker
TreeView+ depends on / blocked
 
Reported: 2017-06-01 05:08 UTC by Mike Ruckman
Modified: 2018-05-29 12:31 UTC (History)
19 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-29 12:31:35 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
grant: journalctl -b -2 (457.59 KB, application/x-gzip)
2017-07-13 21:29 UTC, Grant Boyle 		no flags Details
Bootlog with drm.debug=14 on nVidia Quadro 4000 (no problem occured) (189.90 KB, text/plain)
2017-07-14 07:27 UTC, Rainer Koenig 		no flags Details
Bootlog with drm.debug=14 on nVidia Quadro 4000 (problem occured) (163.51 KB, text/plain)
2017-07-14 07:28 UTC, Rainer Koenig 		no flags Details
drm.debug=14 GeForce GTX 960 (285.05 KB, text/plain)
2017-07-16 06:44 UTC, Jacek Ziemiański 		no flags Details
Bootlog for Fedora 26 on GTX760 with drm.debug=14 (177.27 KB, application/gzip)
2017-07-18 05:23 UTC, Evan Wang 		no flags Details
View All

Description Mike Ruckman 2017-06-01 05:08:33 UTC 
Description of problem:
gnome-shell locks up upon login to a wayland session with F26 Beta. Doesn't happen when using Xorg.

Version-Release number of selected component (if applicable):
xorg-x11-drv-nouveau-1.0.15-1.fc26.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Install F26 Beta 1.3 (via any means, netinst, live, etc.)
2. Log in to created account

Actual results:
gnome-shell hangs; frozen screen.

Expected results:
Being presented with a working Gnome session.

Additional info:
relevant log line:

Jun 01 00:50:07 localhost.localdomain kernel: nouveau 0000:01:00.0: fifo: read fault at 0000011000 engine 07 [HOST0] client 06 [HOST] reason 0c [UNSUPPORTED_KIND] on channel 25 [007c893000 Xwayland[3512]]

Journal is here: https://paste.fedoraproject.org/paste/UJD3xAtTzgfpAJygYeGP5V5M1UNdIGYhyRLivL9gydE=
Comment 1 Mike Ruckman 2017-06-01 05:23:38 UTC 
Output of `lspci | grep VGA`:

01:00.0 VGA compatible controller: NVIDIA Corporation GM206 [GeForce GTX 960] (rev a1)

but works fine on another machine:

01:00.0 VGA compatible controller: NVIDIA Corporation GK107GLM [Quadro K1000M] (rev a1)"

Proposing as a blocker as a violation of the following Beta criterion: "No part of any release-blocking desktop's panel (or equivalent) configuration may crash on startup or be entirely non-functional."

This being a blocker is largely based on if other gfx cards hit this issue and how widespread the issue is. It's bad if you hit it, but hopefully few people hit it.
Comment 2 Stephen Gallagher 2017-06-01 12:11:00 UTC 
I'm -1 to blocking on this; If anyone else can reproduce it, I'd suggest making it a Common Bug with a workaround of "Select GNOME on Xorg at login". It's not a particularly onerous workaround.

I'm +1 FE should a fix turn up and we have to respin for any other reason.
Comment 3 Adam Williamson 2017-06-01 16:53:28 UTC 
Yeah, unless we have definite indication this is affecting a lot of systems I'm -1. It's a bit late to figure that out, also.
Comment 4 Daniel 2017-06-02 13:39:48 UTC 
I’ve got the GeForce GTX 960 (same card) and can confirm that I can’t log in with the Nouveau driver. Works with the proprietary driver via RPM Fusion, so I didn’t dwell on it.
Comment 5 Adam Williamson 2017-06-02 21:16:27 UTC 
Discussed at 2017-06-01 Fedora 26 Beta Go/No-Go meeting #2, acting as a blocker review meeting: https://meetbot-raw.fedoraproject.org/fedora-meeting-2/2017-06-01/f26-beta-go-no-go-meeting.2017-06-01-17.00.log.html . Rejected as a blocker on the basis that there's no particular indication this is a widespread issue at present, it seems likely to be quite hardware-specific.
Comment 6 Couret Charles-Antoine 2017-06-13 17:45:20 UTC 
No issue with nVidia Quadro 1000M and nouveau driver.
Comment 7 Barry Fishman 2017-06-15 13:21:55 UTC 
Also seen with Arch Linux after Gnome 3.24 upgrade.  Does not seem
to effect the GDM login screen.  My Current workaround is to disable wayland in the /etc/gdm/custom.conf file.
Comment 8 Rainer Koenig 2017-07-12 12:38:23 UTC 
Add me to the list: nVidia Qaudro K4200 is also affected by this bug in the current released version of Fedora 26.

Thanks to Barry Fishmann for pointing out the custom.conf file. Was able to login from gdm after uncommenting the line for disabling Wayland on gdm and then selecting "Gnome on Xorg". Without modyfing the custom.conf file even selecting "Gnome on Xorg" will crash. 

Side note: This information should have found its way into the release notes.
Comment 9 Colin J Thomson 2017-07-12 18:25:40 UTC 
Also being hit with this running Plasma, reverting back to Xorg is fine:
02:00.0 VGA compatible controller: NVIDIA Corporation GK107 [GeForce GTX 650] (rev a1)
Xorg-x11-drv-nouveau-1.0.15-1.fc26.x86_64
Comment 10 Adam Williamson 2017-07-12 20:51:57 UTC 
Can folks commenting on this please specify precisely what graphics card they have - I like the format from 'lspci -nn', as it gives the precise PCI ID - and confirm whether they're actually seeing the same log messages as Mike did? Thanks.
Comment 11 Evan Wang 2017-07-13 01:58:46 UTC 
I have the same issue after upgrading to Fedora 26:

01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1)

I've confirmed that I have the same error as Mike
nouveau 0000:01:00.0: fifo: read fault at 0000011000 engine 07 [HOST0] client 06 [HOST] reason 0c [UNSUPPORTED_KIND] on channel 27 [007e218000 Xwayland[1964]
Comment 12 Rainer Koenig 2017-07-13 07:03:24 UTC 
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK104GL [Quadro K4200] [10de:11b4] (rev a1)

nouveau 0000:01:00.0: fifo: read fault at 0000011000 engine 07 [HOST0] client 06 [HOST] reason 0c [UNSUPPORTED_KIND] on channel 25 [00fe140000 Xwayland[2197]]

If I can find time in the next days I will try out other workstation graphic cards from nVidia. Have a lot of them in my lab...
Comment 13 Rainer Koenig 2017-07-13 12:28:47 UTC 
Ok. Did some iterations over all lose graphic cards that I found in my lab.

This are the cards that prove to work (work as "you can login from gdm and get your Gnome desktop):

WORKING GRAPHIC CARDS:
=======================
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK107GL [Quadro K2000] [10de:0ffe] (rev a1)
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK106GL [Quadro K4000] [10de:11fa] (rev a1)
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK107GL [Quadro K420] [10de:0ff3] (rev a1)
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK110GL [Quadro K5200] [10de:103c] (rev a1)
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF119 [NVS 310] [10de:107d] (rev a1)
04:00.0 VGA compatible controller [0300]: NVIDIA Corporation G98 [Quadro NVS 450] [10de:06fa] (rev a1)
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK107 [NVS 510] [10de:0ffd] (rev a1)
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK107GL [Quadro 410] [10de:0fff] (rev a1)

Then I have one card, that ends up in the desktop, but mouse and keyboard are terribly slow: 

GRAPHIC CARD WITH PROBLEM:
==========================
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM204GL [Quadro M4000] [10de:13f1] (rev a1)

If I look at dmesg for this card it shows a nouveau timeout:
[    4.332604] WARNING: CPU: 0 PID: 395 at drivers/gpu/drm/nouveau/nvkm/engine/gr/gf100.c:1499 gf100_gr_init_ctxctl+0x86a/0x9c0 [nouveau]
[    4.332605] nouveau 0000:01:00.0: timeout
[    4.332605] Modules linked in: nouveau(+) mxm_wmi i2c_algo_bit drm_kms_helper ttm e1000e drm crc32c_intel ptp pps_core wmi video i2c_hid
[    4.332640]  ? nv04_timer_read+0x48/0x60 [nouveau]
[    4.332656]  ? nvkm_mm_free+0xae/0x1e0 [nouveau]
[    4.332676]  gf100_gr_init_ctxctl+0x86a/0x9c0 [nouveau]
[    4.332695]  gm200_gr_init+0x6d5/0x710 [nouveau]
[    4.332710]  gf100_gr_init_+0x55/0x60 [nouveau]
[    4.332727]  nvkm_gr_init+0x17/0x20 [nouveau]
[    4.332742]  nvkm_engine_init+0x68/0x1f0 [nouveau]
[    4.332757]  nvkm_subdev_init+0xb0/0x200 [nouveau]
[    4.332770]  nvkm_engine_ref+0x4f/0x70 [nouveau]
[    4.332783]  nvkm_ioctl_new+0x2b4/0x300 [nouveau]
[    4.332800]  ? nvkm_fifo_chan_dtor+0xe0/0xe0 [nouveau]
[    4.332817]  ? gf100_gr_init_fw.isra.8+0x50/0x50 [nouveau]
[    4.332830]  nvkm_ioctl+0x118/0x280 [nouveau]
[    4.332849]  nvkm_client_ioctl+0x12/0x20 [nouveau]
[    4.332862]  nvif_object_ioctl+0x41/0x50 [nouveau]
[    4.332875]  nvif_object_init+0xc8/0x120 [nouveau]
[    4.332894]  nvc0_fbcon_accel_init+0x5b/0x920 [nouveau]
[    4.332912]  nouveau_fbcon_create+0x4a2/0x610 [nouveau]
[    4.332933]  nouveau_fbcon_init+0x105/0x170 [nouveau]
[    4.332950]  ? nouveau_bo_move_init+0xb2/0xf0 [nouveau]
[    4.332965]  nouveau_drm_load+0x22b/0x8d0 [nouveau]
[    4.332992]  nouveau_drm_probe+0x1d7/0x260 [nouveau]
[    4.333025]  nouveau_drm_init+0x1e0/0x1000 [nouveau]
[    4.333046] nouveau 0000:01:00.0: gr: init failed, -16
[    4.335579] nouveau 0000:01:00.0: DRM: allocated 1680x1050 fb: 0x60000, bo ffff9b7c442b6800
[    4.336403] fbcon: nouveaufb (fb0) is primary device
[    4.829100] nouveau 0000:01:00.0: fb0: nouveaufb frame buffer device
[    4.832447] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 0
[   47.453338] nouveau 0000:01:00.0: gr: FECS falcon already acquired by gr!
[   47.453386] nouveau 0000:01:00.0: gr: init failed, -16
[   85.647572] nouveau 0000:01:00.0: gr: FECS falcon already acquired by gr!
[   85.647575] nouveau 0000:01:00.0: gr: init failed, -16

Then I have some cards that are locking up the screen, but are still reachable via SSH:

GRAPHIC CARDS THAT DO NOT WORK:
===============================
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK104GL [Quadro K5000] [10de:11ba] (rev a1)

dmesg log is flooded with those patterns:
[  253.815239] nouveau 0000:01:00.0: fifo: PBDMA0: 80004000 [GPPTR SIGNATURE] ch 29 [00fda80000 Xwayland[1759]] subc 0 mthd 0000 data 00000000


01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF100GL [Quadro 4000] [10de:06dd] (rev a3)

Famous last words from dmesg:
[    2.632501] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 0
[   74.865197] nouveau 0000:01:00.0: fifo: read fault at 0000011000 engine 07 [PFIFO] client 06 [PFIFO] reason 0c [INVALID_STORAGE_TYPE] on channel 26 [007e9c3000 Xwayland[1747]]
[   74.865200] nouveau 0000:01:00.0: fifo: fifo engine fault on channel 26, recovering...
[   74.865235] nouveau 0000:01:00.0: Xwayland[1747]: channel 26 killed!

01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF100GL [Quadro 5000] [10de:06d9] (rev a3)

Famous last words from dmesg:
[    2.653191] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 0
[   67.343548] nouveau 0000:01:00.0: fifo: read fault at 0000011000 engine 07 [PFIFO] client 06 [PFIFO] reason 0a [COMPRESSED_SYSRAM] on channel 24 [009e983000 Xwayland[1678]]
[   67.343551] nouveau 0000:01:00.0: fifo: fifo engine fault on channel 24, recovering...
[   67.343582] nouveau 0000:01:00.0: Xwayland[1678]: channel 24 killed!


That's all for the moment.
Comment 14 Adam Williamson 2017-07-13 15:51:47 UTC 
Thanks a lot for all the feedback, Rainer, it's very helpful. I'm gonna try and track down a nouveau developer to look at all those and decide which are separate bugs and where they should be filed. Thanks again!
Comment 15 Adam Williamson 2017-07-13 15:56:22 UTC 
Oh, it would also be helpful if affected folks could boot with 'drm.debug=14' kernel arg, reproduce the problem, and *attach* (not pastebin) their journal from that boot. That should give us more detailed error messages.
Comment 16 Leslie Satenstein 2017-07-13 17:09:15 UTC 
Fedora 26 release version. Both live install and network install.

I am running Fedora Gnome 3.24 with several extensions.

On login, gnome-shell appears dead.  Actually by running top, it appears that the shell is in a loop (tight loop?) and cpu for that core is at 99.5%.  

Killing the gnome-shell suddenly restarts the shell, and logon completes.

PROBLEM IS BOTH WITH GNOME-ORG and GNOME Wayland.

Please escallate from BETA to Released version
Comment 17 Adam Williamson 2017-07-13 17:10:58 UTC 
Leslie, your problem doesn't sound anything like the bug described here. Please file it separately, with useful data.
Comment 18 Grant Boyle 2017-07-13 21:26:23 UTC 
I see something similar:

After upgrading to Fedora 26, the login screen works as expected but after logging in, the desktop freezes on a blank screen or, sometimes, a random coloured noise pattern or a strangely coloured version of the desktop background.

I tried to downgrade to 25 but that wasn't happening...

The workaround that got my GUI back:

/etc/gdm/custom.conf
[daemon]
WaylandEnable=false

Additonal Information:

lspci -nn | grep VGA
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1)

I'll try drm.debug...
Comment 19 Grant Boyle 2017-07-13 21:29:22 UTC 
Created attachment 1297881 [details]
grant: journalctl -b -2
Comment 20 Adam Williamson 2017-07-14 00:39:33 UTC 
To be clear: we really need to precisely identify what issues people are hitting, and separate them properly. If we just wind up with a giant bug for "absolutely everyone who has an NVIDIA card and has to disable Wayland for some reason", that's no good - it won't get any of the problems *fixed*, it'll just wind up as a dumping ground for stories.

So, in order to actually get things fixed, we really need folks to at least check the journal and see if they see the same errors as the original reporter, and if not, please file your bug *separately*. Thanks!
Comment 21 Rainer Koenig 2017-07-14 07:27:21 UTC 
Created attachment 1298145 [details]
Bootlog with drm.debug=14 on nVidia Quadro 4000 (no problem occured)

Tried to reproduce the problem I encountered with the Quadro 4000 and drm.debug=14, but this time no error occured. I include that boot log anyway, because on the next attempt to reproduce the problem it occured again.
Comment 22 Rainer Koenig 2017-07-14 07:28:44 UTC 
Created attachment 1298146 [details]
Bootlog with drm.debug=14 on nVidia Quadro 4000 (problem occured)

2nd attempt to reproduce the problem on Quadro 4000 with drm.debug=14, this time SUCCESSFUL, the problem occured. So you have a good and a bad log to compare.
Comment 23 Rainer Koenig 2017-07-14 07:32:42 UTC 
Adam, just uploaded 2 boot logs with Quadro 4000 and drm.debug=14. The first attempt didn't reproduce the problem, on the second attempt the problem showed up again. Could be some timing/initialization whatever problem. A third attempt without the drm.debug=14 boot parameter reproduced the error immediately. So by debugging we change something that makes the problem occur only sporadically. 
If you need more tests to be done let me know, I keep this machine as it is for the moment so we can dig deeper into it if necessary.
Comment 24 Jacek Ziemiański 2017-07-16 06:41:55 UTC 
Hi, i have the same problem with card:

01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1)
Comment 25 Jacek Ziemiański 2017-07-16 06:44:58 UTC 
Created attachment 1299246 [details]
drm.debug=14 GeForce GTX 960

boot log with drm.debug=14

journalctl -b -1 -o short-monotonic --no-hostname -t kernel
Comment 26 Adam Williamson 2017-07-17 22:42:56 UTC 
Thanks a lot for the debug logs, folks.

I spoke to one of the devs who thinks that we should at least treat all cases which show 'fifo: read fault' as potentially related for now, even if the 'reason' differs, so please, if you see such 'fifo: read fault' messages in your case, keep following this bug (and attach debug logs if you can). I'll do what I can to get some attention on fixing it.
Comment 27 Adam Williamson 2017-07-17 22:44:48 UTC 
Oh - forgot to mention, if someone has time to try out some different kernel builds and try to narrow down as far as possible when this issue appeared, it'd be very helpful. You can find various kernel builds on Koji:

https://koji.fedoraproject.org/koji/packageinfo?packageID=8

Usually kernels can shared across fairly close releases without any trouble, so you should be able to boot fc24 and fc25 kernels to test older kernel versions, and fc27 kernels to test newer kernel versions. If we can narrow down the window in which the issue appeared as far as possible, it'll help with debugging.

Thanks folks!
Comment 28 Evan Wang 2017-07-18 05:23:03 UTC 
Created attachment 1300247 [details]
Bootlog for Fedora 26 on GTX760 with drm.debug=14

In this run, it managed to load the desktop (initially pixelated with odd colors but it corrected itself) but shortly after I started an application it crashed.
Comment 29 Joseph D. Wagner 2017-07-22 22:45:13 UTC 
I have:

01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1)

but I didn't have any problems when I booted from the Live DVD.

Are there steps to reproduce this problem, so I can tell if impacts me?

I have an Intel processor on a UEFI system booted in secure mode.
Comment 30 Johnny B. Goode 2017-07-23 13:59:20 UTC 
My system is:
01:00.0 VGA compatible controller: NVIDIA Corporation GM206 [GeForce GTX 950] (rev a1)
Box, no optimus. Intel graphic on chip but disabled in BIOS.

Very good problem description is here:
https://bugzilla.redhat.com/show_bug.cgi?id=1471986

Graphic system is hard freezing, no mouse no keyboard and power switch not working. But ssh working without problems. I can log in from other machines.

1. I upgraded system from F25 to F26 so there was no problem to try booting from previous working kernels:
kernel-4.11.6-201.fc25.x86_64 and kernel-4.11.9-200.fc25.x86_64 - no differences
2. Tried with xorg-x11-drv-nouveau-1.0.15-2.fc25.x86_64 - no difference
3. Tried with earlier linux-firmware-20170313-72.git695f2d6d.fc26 - nothing.

On other distribution (Gentoo) I can work with all 4.11 kernel and 4.12.x on Wayland but with Gnome 3.22, so for me this is no kernel problem. Probably graphic system gdm/gnome/mesa/egl.

Some logs:
Jul 16 11:35:08 desktop2 kernel: [  549.533843] nouveau 0000:01:00.0: fifo: read fault at 0000011000 engine 07 [HOST0] client 06 [HOST] reason 0c [UNSUPPORTED_KIND] on channel 27 [007cdf9000 Xwayland[3042]]
Jul 16 11:35:08 desktop2 kernel: [  549.533854] nouveau 0000:01:00.0: fifo: channel 27: killed
Jul 16 11:35:08 desktop2 kernel: [  549.533856] nouveau 0000:01:00.0: fifo: runlist 0: scheduled for recovery
Jul 16 11:35:08 desktop2 kernel: [  549.533862] nouveau 0000:01:00.0: Xwayland[3042]: channel 27 killed!
Jul 16 11:35:08 desktop2 kernel: [  549.749179] nouveau 0000:01:00.0: fifo: read fault at 0008000000 engine 1b [CE2] client 18 [GR_CE] reason 0c [UNSUPPORTED_KIND] on channel 15 [007ddbf000 systemd-logind[710]]
Jul 16 11:35:08 desktop2 kernel: [  549.749187] nouveau 0000:01:00.0: fifo: channel 15: killed
Jul 16 11:35:08 desktop2 kernel: [  549.749189] nouveau 0000:01:00.0: fifo: runlist 0: scheduled for recovery
Jul 16 11:35:08 desktop2 kernel: [  549.749192] nouveau 0000:01:00.0: fifo: engine 7: scheduled for recovery
Jul 16 11:35:08 desktop2 kernel: [  549.749202] nouveau 0000:01:00.0: systemd-logind[710]: channel 15 killed!
Jul 16 11:35:09 desktop2 kernel: [  551.077351] nouveau 0000:01:00.0: fifo: read fault at 5d55d45000 engine 1f [] client 07 [HOST_CPU] reason 0d [REGION_VIOLATION] on channel -1 [0000000000 unknown]
Jul 16 11:35:09 desktop2 kernel: [  551.078407] nouveau 0000:01:00.0: fifo: PBDMA0: 80064000 [GPPTR PBPTR PBENTRY SIGNATURE] ch 28 [007c322000 Xwayland[3042]] subc 0 mthd 0000 data 00000000
Jul 16 11:35:09 desktop2 kernel: [  551.078428] nouveau 0000:01:00.0: fifo: PBDMA0: 00064000 [GPPTR PBPTR PBENTRY] ch 28 [007c322000 Xwayland[3042]] subc 0 mthd 0000 data 00000000
Jul 16 11:35:09 desktop2 kernel: [  551.078446] nouveau 0000:01:00.0: fifo: PBDMA0: 00064000 [GPPTR PBPTR PBENTRY] ch 28 [007c322000 Xwayland[3042]] subc 0 mthd 0000 data 00000000
Jul 16 11:35:09 desktop2 kernel: [  551.078465] nouveau 0000:01:00.0: fifo: PBDMA0: 00024000 [GPPTR PBPTR] ch 28 [007c322000 Xwayland[3042]] subc 0 mthd 0000 data 00000000
Jul 16 11:35:09 desktop2 kernel: [  551.078478] nouveau 0000:01:00.0: fifo: PBDMA0: 00024000 [GPPTR PBPTR] ch 28 [007c322000 Xwayland[3042]] subc 0 mthd 0000 data 00000000
Jul 16 11:35:09 desktop2 kernel: [  551.078489] nouveau 0000:01:00.0: fifo: PBDMA0: 00024000 [GPPTR PBPTR] ch 28 [007c322000 Xwayland[3042]] subc 0 mthd 0000 data 00000000
Jul 16 11:35:09 desktop2 kernel: [  551.078501] nouveau 0000:01:00.0: fifo: PBDMA0: 00024000 [GPPTR PBPTR] ch 28 [007c322000 Xwayland[3042]] subc 0 mthd 0000 data 00000000
Jul 16 11:35:09 desktop2 kernel: [  551.078513] nouveau 0000:01:00.0: fifo: PBDMA0: 00024000 [GPPTR PBPTR] ch 28 [007c322000 Xwayland[3042]] subc 0 mthd 0000 data 00000000
Jul 16 11:35:09 desktop2 kernel: [  551.078525] nouveau 0000:01:00.0: fifo: PBDMA0: 00024000 [GPPTR PBPTR] ch 28 [007c322000 Xwayland[3042]] subc 0 mthd 0000 data 00000000
Jul 16 11:35:09 desktop2 kernel: [  551.078538] nouveau 0000:01:00.0: fifo: PBDMA0: 00024000 [GPPTR PBPTR] ch 28 [007c322000 Xwayland[3042]] subc 0 mthd 0000 data 00000000
........
Jul 16 11:36:04 desktop2 kernel: [  605.674077] nouveau 0000:01:00.0: fifo: PBDMA0: 00024000 [GPPTR PBPTR] ch 28 [007c322000 Xwayland[3042]] subc 0 mthd 0000 data 00000000

Next:
Jul 18 17:40:04 desktop2 kernel: [  126.814961] nouveau 0000:01:00.0: fifo: read fault at 0008000000 engine 1b [CE2] client 18 [GR_CE] reason 0c [UNSUPPORTED_KIND] on channel 15 [007ddbf000 systemd-logind[701]]
Jul 18 17:40:04 desktop2 kernel: [  126.814970] nouveau 0000:01:00.0: fifo: channel 15: killed
Jul 18 17:40:04 desktop2 kernel: [  126.814972] nouveau 0000:01:00.0: fifo: runlist 0: scheduled for recovery
Jul 18 17:40:04 desktop2 kernel: [  126.814976] nouveau 0000:01:00.0: fifo: engine 7: scheduled for recovery
Jul 18 17:40:04 desktop2 kernel: [  126.814982] nouveau 0000:01:00.0: systemd-logind[701]: channel 15 killed!
Jul 18 17:40:37 desktop2 kernel: [  160.251661] nouveau 0000:01:00.0: fifo: read fault at 5555555000 engine 1f [] client 07 [HOST_CPU] reason 0d [REGION_VIOLATION] on channel -1 [0000000000 unknown]
Jul 18 17:40:37 desktop2 kernel: [  160.251668] nouveau 0000:01:00.0: fifo: PBDMA0: 80044000 [GPPTR PBENTRY SIGNATURE] ch 28 [007c322000 Xwayland[1756]] subc 5 mthd 1554 data 55555555
Jul 18 17:40:37 desktop2 kernel: [  160.251680] nouveau 0000:01:00.0: fifo: PBDMA0: 00044000 [GPPTR PBENTRY] ch 28 [007c322000 Xwayland[1756]] subc 0 mthd 0000 data 00000000
Jul 18 17:40:37 desktop2 kernel: [  160.251692] nouveau 0000:01:00.0: fifo: PBDMA0: 00044000 [GPPTR PBENTRY] ch 28 [007c322000 Xwayland[1756]] subc 0 mthd 0000 data 00000000
Jul 18 17:40:37 desktop2 kernel: [  160.251703] nouveau 0000:01:00.0: fifo: PBDMA0: 00044000 [GPPTR PBENTRY] ch 28 [007c322000 Xwayland[1756]] subc 0 mthd 0000 data 00000000
Jul 18 17:40:37 desktop2 kernel: [  160.251715] nouveau 0000:01:00.0: fifo: PBDMA0: 00004000 [GPPTR] ch 28 [007c322000 Xwayland[1756]] subc 0 mthd 0000 data 00000000
Jul 18 17:40:37 desktop2 kernel: [  160.251726] nouveau 0000:01:00.0: fifo: PBDMA0: 00004000 [GPPTR] ch 28 [007c322000 Xwayland[1756]] subc 0 mthd 0000 data 00000000
Jul 18 17:40:37 desktop2 kernel: [  160.251738] nouveau 0000:01:00.0: fifo: PBDMA0: 00004000 [GPPTR] ch 28 [007c322000 Xwayland[1756]] subc 0 mthd 0000 data 00000000
Jul 18 17:40:37 desktop2 kernel: [  160.251749] nouveau 0000:01:00.0: fifo: PBDMA0: 00004000 [GPPTR] ch 28 [007c322000 Xwayland[1756]] subc 0 mthd 0000 data 00000000
Jul 18 17:40:37 desktop2 kernel: [  160.251761] nouveau 0000:01:00.0: fifo: PBDMA0: 00004000 [GPPTR] ch 28 [007c322000 Xwayland[1756]] subc 0 mthd 0000 data 00000000
Jul 18 17:40:37 desktop2 kernel: [  160.251773] nouveau 0000:01:00.0: fifo: PBDMA0: 00004000 [GPPTR] ch 28 [007c322000 Xwayland[1756]] subc 0 mthd 0000 data 00000000
Jul 18 17:40:37 desktop2 kernel: [  160.251784] nouveau 0000:01:00.0: fifo: PBDMA0: 00004000 [GPPTR] ch 28 [007c322000 Xwayland[1756]] subc 0 mthd 0000 data 00000000
Jul 18 17:40:37 desktop2 kernel: [  160.251796] nouveau 0000:01:00.0: fifo: PBDMA0: 00004000 [GPPTR] ch 28 [007c322000 Xwayland[1756]] subc 0 mthd 0000 data 00000000
Jul 18 17:40:37 desktop2 kernel: [  160.251807] nouveau 0000:01:00.0: fifo: PBDMA0: 00004000 [GPPTR] ch 28 [007c322000 Xwayland[1756]] subc 0 mthd 0000 data 00000000
Jul 18 17:40:37 desktop2 kernel: [  160.251819] nouveau 0000:01:00.0: fifo: PBDMA0: 00004000 [GPPTR] ch 28 [007c322000 Xwayland[1756]] subc 0 mthd 0000 data 00000000
Jul 18 17:40:37 desktop2 kernel: [  160.251830] nouveau 0000:01:00.0: fifo: PBDMA0: 00004000 [GPPTR] ch 28 [007c322000 Xwayland[1756]] subc 0 mthd 0000 data 00000000
Jul 18 17:40:37 desktop2 kernel: [  160.251842] nouveau 0000:01:00.0: fifo: PBDMA0: 00004000 [GPPTR] ch 28 [007c322000 Xwayland[1756]] subc 0 mthd 0000 data 00000000
........
Jul 18 17:41:32 desktop2 kernel: [  214.884254] nouveau 0000:01:00.0: fifo: PBDMA0: 00004000 [GPPTR] ch 28 [007c322000 Xwayland[1756]] subc 0 mthd 0000 data 00000000

And one, recorded after successful log-in in wayland session, made after log-out session. Of course the next log-in was impossible.
Jul 20 19:34:16 desktop2 kernel: [ 1589.883556] nouveau 0000:01:00.0: gr: FECS 00000001
Jul 20 19:34:16 desktop2 kernel: [ 1589.883561] nouveau 0000:01:00.0: gr: 409000 - done 00000300
Jul 20 19:34:16 desktop2 kernel: [ 1589.883567] nouveau 0000:01:00.0: gr: 409000 - stat 00000002 00000000 00000001 00000000
Jul 20 19:34:16 desktop2 kernel: [ 1589.883573] nouveau 0000:01:00.0: gr: 409000 - stat 00080420 00000000 00000001 00000000
Jul 20 19:34:16 desktop2 kernel: [ 1589.883576] nouveau 0000:01:00.0: gr: 502000 - done 00000300
Jul 20 19:34:16 desktop2 kernel: [ 1589.883583] nouveau 0000:01:00.0: gr: 502000 - stat 00000001 00000000 00000001 00000000
Jul 20 19:34:16 desktop2 kernel: [ 1589.883590] nouveau 0000:01:00.0: gr: 502000 - stat 00080426 00000000 00000000 00000000
Jul 20 19:34:16 desktop2 kernel: [ 1589.883592] nouveau 0000:01:00.0: gr: 50a000 - done 00000300
Jul 20 19:34:16 desktop2 kernel: [ 1589.883598] nouveau 0000:01:00.0: gr: 50a000 - stat 00000001 00000000 00000001 00000000
Jul 20 19:34:16 desktop2 kernel: [ 1589.883605] nouveau 0000:01:00.0: gr: 50a000 - stat 00080436 00000000 00000000 00000000
Jul 20 19:34:16 desktop2 kernel: [ 1589.903231] nouveau 0000:01:00.0: gr: FECS 00000001
Jul 20 19:34:16 desktop2 kernel: [ 1589.903235] nouveau 0000:01:00.0: gr: 409000 - done 00000300
Jul 20 19:34:16 desktop2 kernel: [ 1589.903239] nouveau 0000:01:00.0: gr: 409000 - stat 00000002 00000000 00000001 00000000
Jul 20 19:34:16 desktop2 kernel: [ 1589.903243] nouveau 0000:01:00.0: gr: 409000 - stat 00080420 00000000 00000001 00000000
Jul 20 19:34:16 desktop2 kernel: [ 1589.903244] nouveau 0000:01:00.0: gr: 502000 - done 00000300
Jul 20 19:34:16 desktop2 kernel: [ 1589.903249] nouveau 0000:01:00.0: gr: 502000 - stat 00000001 00000000 00000001 00000000
Jul 20 19:34:16 desktop2 kernel: [ 1589.903253] nouveau 0000:01:00.0: gr: 502000 - stat 00080426 00000000 00000000 00000000
Jul 20 19:34:16 desktop2 kernel: [ 1589.903255] nouveau 0000:01:00.0: gr: 50a000 - done 00000300
Jul 20 19:34:16 desktop2 kernel: [ 1589.903259] nouveau 0000:01:00.0: gr: 50a000 - stat 00000001 00000000 00000001 00000000
Jul 20 19:34:16 desktop2 kernel: [ 1589.903264] nouveau 0000:01:00.0: gr: 50a000 - stat 00080436 00000000 00000000 00000000
Jul 20 19:34:24 desktop2 kernel: [ 1597.421505] nouveau 0000:01:00.0: gr: FECS 00000001
Jul 20 19:34:24 desktop2 kernel: [ 1597.421509] nouveau 0000:01:00.0: gr: 409000 - done 00000300
Jul 20 19:34:24 desktop2 kernel: [ 1597.421513] nouveau 0000:01:00.0: gr: 409000 - stat 00000002 00000000 00000001 00000000
Jul 20 19:34:24 desktop2 kernel: [ 1597.421517] nouveau 0000:01:00.0: gr: 409000 - stat 00080420 00000000 00000001 00000000
Jul 20 19:34:24 desktop2 kernel: [ 1597.421519] nouveau 0000:01:00.0: gr: 502000 - done 00000300
Jul 20 19:34:24 desktop2 kernel: [ 1597.421524] nouveau 0000:01:00.0: gr: 502000 - stat 00000001 00000000 00000001 00000000
Jul 20 19:34:24 desktop2 kernel: [ 1597.421529] nouveau 0000:01:00.0: gr: 502000 - stat 00080426 00000000 00000000 00000000
Jul 20 19:34:24 desktop2 kernel: [ 1597.421530] nouveau 0000:01:00.0: gr: 50a000 - done 00000300
Jul 20 19:34:24 desktop2 kernel: [ 1597.421535] nouveau 0000:01:00.0: gr: 50a000 - stat 00000001 00000000 00000001 00000000
Jul 20 19:34:24 desktop2 kernel: [ 1597.421540] nouveau 0000:01:00.0: gr: 50a000 - stat 00080436 00000000 00000000 00000000
........
Jul 20 19:34:24 desktop2 kernel: [ 1597.422568] nouveau 0000:01:00.0: fifo: write fault at 0000013000 engine 07 [HOST0] client 07 [HOST_CPU] reason 02 [PTE] on channel 5 [007f23d000 Xwayland[1458]]
Jul 20 19:34:24 desktop2 kernel: [ 1597.422575] nouveau 0000:01:00.0: fifo: channel 5: killed
Jul 20 19:34:24 desktop2 kernel: [ 1597.422577] nouveau 0000:01:00.0: fifo: runlist 0: scheduled for recovery
Jul 20 19:34:24 desktop2 kernel: [ 1597.422581] nouveau 0000:01:00.0: Xwayland[1458]: channel 5 killed!
Jul 20 19:34:24 desktop2 kernel: [ 1597.422653] nouveau 0000:01:00.0: gr: FECS 00000001
Jul 20 19:34:24 desktop2 kernel: [ 1597.422655] nouveau 0000:01:00.0: gr: 409000 - done 00000300
Jul 20 19:34:24 desktop2 kernel: [ 1597.422659] nouveau 0000:01:00.0: gr: 409000 - stat 00000002 00000000 00000001 00000000
Jul 20 19:34:24 desktop2 kernel: [ 1597.422664] nouveau 0000:01:00.0: gr: 409000 - stat 00080420 00000000 00000001 00000000
Jul 20 19:34:24 desktop2 kernel: [ 1597.422666] nouveau 0000:01:00.0: gr: 502000 - done 00000300
Jul 20 19:34:24 desktop2 kernel: [ 1597.422670] nouveau 0000:01:00.0: gr: 502000 - stat 00000001 00000000 00000001 00000000
Jul 20 19:34:24 desktop2 kernel: [ 1597.422675] nouveau 0000:01:00.0: gr: 502000 - stat 00080426 00000000 00000000 00000000
Jul 20 19:34:24 desktop2 kernel: [ 1597.422677] nouveau 0000:01:00.0: gr: 50a000 - done 00000300
Jul 20 19:34:24 desktop2 kernel: [ 1597.422681] nouveau 0000:01:00.0: gr: 50a000 - stat 00000001 00000000 00000001 00000000
Jul 20 19:34:24 desktop2 kernel: [ 1597.422686] nouveau 0000:01:00.0: gr: 50a000 - stat 00080436 00000000 00000000 00000000
Jul 20 19:34:24 desktop2 kernel: [ 1597.423758] nouveau 0000:01:00.0: gr: FECS 00000001
Jul 20 19:34:24 desktop2 kernel: [ 1597.423760] nouveau 0000:01:00.0: gr: 409000 - done 00000300
Jul 20 19:34:24 desktop2 kernel: [ 1597.423764] nouveau 0000:01:00.0: gr: 409000 - stat 00000002 00000000 00000001 00000000
Jul 20 19:34:24 desktop2 kernel: [ 1597.423768] nouveau 0000:01:00.0: gr: 409000 - stat 00080420 00000000 00000001 00000000
Jul 20 19:34:24 desktop2 kernel: [ 1597.423770] nouveau 0000:01:00.0: gr: 502000 - done 00000300
Jul 20 19:34:24 desktop2 kernel: [ 1597.423774] nouveau 0000:01:00.0: gr: 502000 - stat 00000001 00000000 00000001 00000000
Jul 20 19:34:24 desktop2 kernel: [ 1597.423779] nouveau 0000:01:00.0: gr: 502000 - stat 00080426 00000000 00000000 00000000
Jul 20 19:34:24 desktop2 kernel: [ 1597.423781] nouveau 0000:01:00.0: gr: 50a000 - done 00000300
Jul 20 19:34:24 desktop2 kernel: [ 1597.423785] nouveau 0000:01:00.0: gr: 50a000 - stat 00000001 00000000 00000001 00000000
Jul 20 19:34:24 desktop2 kernel: [ 1597.423790] nouveau 0000:01:00.0: gr: 50a000 - stat 00080436 00000000 00000000 00000000
........
Jul 20 19:34:24 desktop2 kernel: [ 1597.482668] nouveau 0000:01:00.0: fifo: write fault at 0000013000 engine 07 [HOST0] client 07 [HOST_CPU] reason 02 [PTE] on channel 14 [007e4ec000 Xwayland[1458]]
Jul 20 19:34:24 desktop2 kernel: [ 1597.482672] nouveau 0000:01:00.0: fifo: channel 14: killed
Jul 20 19:34:24 desktop2 kernel: [ 1597.482674] nouveau 0000:01:00.0: fifo: runlist 0: scheduled for recovery
Jul 20 19:34:24 desktop2 kernel: [ 1597.482678] nouveau 0000:01:00.0: Xwayland[1458]: channel 14 killed!
Jul 20 19:34:24 desktop2 kernel: [ 1597.482749] nouveau 0000:01:00.0: gr: FECS 00000001
Jul 20 19:34:24 desktop2 kernel: [ 1597.482751] nouveau 0000:01:00.0: gr: 409000 - done 00000300
Jul 20 19:34:24 desktop2 kernel: [ 1597.482754] nouveau 0000:01:00.0: gr: 409000 - stat 00000002 00000000 00000001 00000000
Jul 20 19:34:24 desktop2 kernel: [ 1597.482758] nouveau 0000:01:00.0: gr: 409000 - stat 00080420 00000000 00000001 00000000
Jul 20 19:34:24 desktop2 kernel: [ 1597.482759] nouveau 0000:01:00.0: gr: 502000 - done 00000300
Jul 20 19:34:24 desktop2 kernel: [ 1597.482763] nouveau 0000:01:00.0: gr: 502000 - stat 00000001 00000000 00000001 00000000
Jul 20 19:34:24 desktop2 kernel: [ 1597.482767] nouveau 0000:01:00.0: gr: 502000 - stat 00080426 00000000 00000000 00000000
Jul 20 19:34:24 desktop2 kernel: [ 1597.482769] nouveau 0000:01:00.0: gr: 50a000 - done 00000300
Jul 20 19:34:24 desktop2 kernel: [ 1597.482774] nouveau 0000:01:00.0: gr: 50a000 - stat 00000001 00000000 00000001 00000000
Jul 20 19:34:24 desktop2 kernel: [ 1597.482779] nouveau 0000:01:00.0: gr: 50a000 - stat 00080436 00000000 00000000 00000000
Jul 20 19:34:24 desktop2 kernel: [ 1597.483851] nouveau 0000:01:00.0: gr: FECS 00000001
Jul 20 19:34:24 desktop2 kernel: [ 1597.483853] nouveau 0000:01:00.0: gr: 409000 - done 00000300
Jul 20 19:34:24 desktop2 kernel: [ 1597.483857] nouveau 0000:01:00.0: gr: 409000 - stat 00000002 00000000 00000001 00000000
Jul 20 19:34:24 desktop2 kernel: [ 1597.483860] nouveau 0000:01:00.0: gr: 409000 - stat 00080420 00000000 00000001 00000000
Jul 20 19:34:24 desktop2 kernel: [ 1597.483862] nouveau 0000:01:00.0: gr: 502000 - done 00000300
Jul 20 19:34:24 desktop2 kernel: [ 1597.483866] nouveau 0000:01:00.0: gr: 502000 - stat 00000001 00000000 00000001 00000000
Jul 20 19:34:24 desktop2 kernel: [ 1597.483871] nouveau 0000:01:00.0: gr: 502000 - stat 00080426 00000000 00000000 00000000
Jul 20 19:34:24 desktop2 kernel: [ 1597.483872] nouveau 0000:01:00.0: gr: 50a000 - done 00000300
Jul 20 19:34:24 desktop2 kernel: [ 1597.483877] nouveau 0000:01:00.0: gr: 50a000 - stat 00000001 00000000 00000001 00000000
Jul 20 19:34:24 desktop2 kernel: [ 1597.483881] nouveau 0000:01:00.0: gr: 50a000 - stat 00080436 00000000 00000000 00000000
........
Jul 20 19:34:24 desktop2 kernel: [ 1597.489362] nouveau 0000:01:00.0: gr: FECS 00000001
Jul 20 19:34:24 desktop2 kernel: [ 1597.489364] nouveau 0000:01:00.0: gr: 409000 - done 00000300
Jul 20 19:34:24 desktop2 kernel: [ 1597.489367] nouveau 0000:01:00.0: gr: 409000 - stat 00000002 00000000 00000001 00000000
Jul 20 19:34:24 desktop2 kernel: [ 1597.489371] nouveau 0000:01:00.0: gr: 409000 - stat 00080420 00000000 00000001 00000000
Jul 20 19:34:24 desktop2 kernel: [ 1597.489372] nouveau 0000:01:00.0: gr: 502000 - done 00000300
Jul 20 19:34:24 desktop2 kernel: [ 1597.489377] nouveau 0000:01:00.0: gr: 502000 - stat 00000001 00000000 00000001 00000000


Please update this information with new not working graphic cards. Not much people understanding chip names.
https://fedoraproject.org/wiki/Common_F26_bugs#Wayland_sessions_crash_on_start_on_some_NVIDIA_graphics_cards.2C_logs_show_fifo:_read_fault_error
Comment 31 Johnny B. Goode 2017-07-23 16:28:04 UTC 
And another one:
https://bugzilla.redhat.com/show_bug.cgi?id=1462065
Comment 32 Ben Skeggs 2017-07-25 06:10:09 UTC 
A fix for this issue has been identified.  The patch is currently sitting in drm-fixes (commit 38bcb208f60924a031b9f809f7cd252ea4a94e5f), and Cc'd stable.  Hopefully it'll quickly make its way into the next 4.11.x release.
Comment 33 Johnny B. Goode 2017-07-25 14:15:04 UTC 
Do You think - next Fedora kernel 4.11.x release? because kernel 4.11 is EOL
https://lwn.net/Articles/728526/
Where we can look at this patch?
Comment 34 Stephen Gallagher 2017-07-25 14:30:49 UTC 
(In reply to Johnny B. Goode from comment #33)
> Do You think - next Fedora kernel 4.11.x release? because kernel 4.11 is EOL
> https://lwn.net/Articles/728526/
> Where we can look at this patch?

Fedora is right in the middle of building 4.12.3 right now for updates-testing (sometime this week). Presumably if that patch goes upstream, it will hit 4.12 rather than 4.11.
Comment 35 Ben Skeggs 2017-07-25 20:20:45 UTC 
(In reply to Stephen Gallagher from comment #34)
> (In reply to Johnny B. Goode from comment #33)
> > Do You think - next Fedora kernel 4.11.x release? because kernel 4.11 is EOL
> > https://lwn.net/Articles/728526/
> > Where we can look at this patch?
> 
> Fedora is right in the middle of building 4.12.3 right now for
> updates-testing (sometime this week). Presumably if that patch goes
> upstream, it will hit 4.12 rather than 4.11.

Yeah, my apologies!  I wasn't aware of 4.11 being EOL until after I sent the patches to stable.
Comment 36 David 2017-08-09 06:56:18 UTC 
Hello, I've got GeForce GTX 760's and they are affected by this bug.
I'd really like to go back to using Wayland on our workstations for security reasons.

Can anybody confirm that the fix will be in the 4.12 kernel when it's released?

I note that it's been worked on for two weeks, which seems like a while.  Any rough idea of when it might be available?  (I'm sorry I'm not across the rest of the project.)

Thanks!
Comment 37 Joseph D. Wagner 2017-08-09 09:58:45 UTC 
I too have a GeForce GTX 760, but it does not appear to be impacted by the problem, at least not when I boot off of the live dvd.

I have yet to see steps to reproduce this problem, so I can tell if impacts me.  (Intel processor on a UEFI system booted in secure mode).
Comment 38 Johnny B. Goode 2017-08-14 09:43:00 UTC 
I can confirm that Fedora testing kernel 4.12.5-300.fc26.x86_64 is free of this bug.
Thank You.

For Fedora users:
https://fedoraproject.org/wiki/How_to_test_updates
Comment 39 Adam Williamson 2017-08-14 22:31:35 UTC 
Can others please test with that kernel and report? Thanks.
Comment 40 Jacek Ziemiański 2017-08-16 15:47:42 UTC 
I update kernel in fedora 26 to 4.12.5-300.fc26.x86_64, I can login to gnome with wayland, everything seems to work ok.

Thanks.
Comment 41 David 2017-08-19 04:02:04 UTC 
Yes, the latest production kernel 4.12.5-300.fc26.x86_64 resolves the problem for me also.
Comment 42 Bluexin 2017-12-07 19:32:49 UTC 
I'm getting an issue that seems like it's the same (similar logs) but doesn't happen when logging in, only when starting certain applications.
Here's a log :

Dec 07 01:10:48 bluexin.fedora kernel: nouveau 0000:24:00.0: fifo: read fault at 00029f6000 engine 1b [CE2] client 18 [GR_CE] reason 02 [PTE] on channel 26 [007dad1000 Xwayland[2456]]
Dec 07 01:10:48 bluexin.fedora kernel: nouveau 0000:24:00.0: fifo: channel 26: killed
Dec 07 01:10:48 bluexin.fedora kernel: nouveau 0000:24:00.0: fifo: runlist 0: scheduled for recovery
Dec 07 01:10:48 bluexin.fedora kernel: nouveau 0000:24:00.0: fifo: engine 0: scheduled for recovery
Dec 07 01:10:48 bluexin.fedora kernel: nouveau 0000:24:00.0: fifo: engine 7: scheduled for recovery
Dec 07 01:10:48 bluexin.fedora kernel: nouveau 0000:24:00.0: Xwayland[2456]: channel 26 killed!

Using 4.13.16-302.fc27.x86_64
(I already had this issue in the past, but didn't use Fedora in a while on this computer -- don't remember the versions)

With NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1)

Should I file another bug report? I'll try with xorg in a bit.
Comment 43 Bluexin 2017-12-07 21:14:09 UTC 
Is probably caused by said apps using older versions of lwjgl.
Disabling Wayland caused a "native call crash", pointing to the nouveau driver with a segfault.

So I guess the issue is different after all '^'
Comment 44 Fedora End Of Life 2018-05-03 08:12:32 UTC 
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Comment 45 Fedora End Of Life 2018-05-29 12:31:35 UTC 
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.
Note You need to log in before you can comment on or make changes to this bug.