Bug 1452697 - Xorg lockup when docking
Summary: Xorg lockup when docking
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-19 13:31 UTC by Robert Story
Modified: 2018-01-02 09:20 UTC (History)
5 users (show)

Fixed In Version: xorg-x11-drv-nouveau-1.0.15-2.fc25
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:53:06 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
annotate /var/log/messages (84.99 KB, text/plain)
2017-05-19 13:31 UTC, Robert Story
no flags Details
annotated Xorg (35.64 KB, text/plain)
2017-05-19 13:32 UTC, Robert Story
no flags Details
dnf update that broke docking (45.56 KB, text/plain)
2017-05-19 13:56 UTC, Robert Story
no flags Details
latest attempt (27.45 KB, text/plain)
2017-06-02 21:04 UTC, Robert Story
no flags Details

Description Robert Story 2017-05-19 13:31:34 UTC
Created attachment 1280427 [details]
annotate /var/log/messages

Description of problem:
After a recent update, undocking my Lenovo ThinkPad P50 would crash Xorg (see bz#1451009). After downgrading xorg-x11-drv-nouveau, undocking works. However, docking again results in a frozen screen (with exception of mouse). After a VT switch and return to VT1, not even the mouse works.

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

How reproducible:
Every time.

Steps to Reproduce:
1. Log in while docked
2. undock
3. dock

Actual results:
Xorg lockup

Expected results:
Normal operation

Additional info:

************** Login ******************
May 19 08:16:40 titan kernel: nouveau 0000:01:00.0: DRM: resuming kernel object tree...
May 19 08:16:40 titan kernel: nouveau 0000:01:00.0: DRM: resuming client object trees...
May 19 08:16:40 titan kernel: nouveau 0000:01:00.0: DRM: resuming display...
May 19 08:16:40 titan kernel: nouveau 0000:01:00.0: DRM: resuming console...

*************** Undock *****************
May 19 08:17:16 titan kernel: nouveau 0000:01:00.0: disp: 0x64a8[0]: INIT_GENERIC_CONDITON: unknown 0x07
May 19 08:17:21 titan kernel: nouveau 0000:01:00.0: DRM: suspending console...
May 19 08:17:21 titan kernel: nouveau 0000:01:00.0: DRM: suspending display...
May 19 08:17:21 titan kernel: nouveau 0000:01:00.0: DRM: evicting buffers...
May 19 08:17:21 titan kernel: nouveau 0000:01:00.0: DRM: waiting for kernel channels to go idle...
May 19 08:17:21 titan kernel: nouveau 0000:01:00.0: DRM: suspending client object trees...
May 19 08:17:21 titan kernel: nouveau 0000:01:00.0: DRM: suspending kernel object tree...

***************** Dock ********************
May 19 08:17:56 titan kernel: nouveau 0000:01:00.0: DRM: resuming kernel object tree...
May 19 08:17:56 titan kernel: nouveau 0000:01:00.0: priv: HUB0: 614900 00800000 (1d408200)
May 19 08:17:56 titan kernel: nouveau 0000:01:00.0: DRM: resuming client object trees...
May 19 08:17:56 titan kernel: nouveau 0000:01:00.0: DRM: resuming display...
May 19 08:17:56 titan kernel: nouveau 0000:01:00.0: DRM: resuming console...
May 19 08:17:58 titan kernel: nouveau 0000:01:00.0: gr: TRAP ch 2 [00ff7d7000 Xorg[13526]]
May 19 08:17:58 titan kernel: nouveau 0000:01:00.0: gr: GPC0/TPC0/TEX: 80000041
May 19 08:17:58 titan kernel: nouveau 0000:01:00.0: gr: GPC0/TPC1/TEX: 80000041
May 19 08:17:58 titan kernel: nouveau 0000:01:00.0: gr: GPC0/TPC2/TEX: 80000041
May 19 08:17:58 titan kernel: nouveau 0000:01:00.0: gr: GPC0/TPC3/TEX: 80000041
May 19 08:17:58 titan kernel: nouveau 0000:01:00.0: gr: GPC0/TPC4/TEX: 80000041
May 19 08:17:58 titan kernel: nouveau 0000:01:00.0: fifo: read fault at 0008000000 engine 00 [GR] client 04 [GPC0/T1_1] reason 02 [PTE] on channel 2 [00ff7d7000 Xorg[13526]]
May 19 08:17:58 titan kernel: nouveau 0000:01:00.0: fifo: gr engine fault on channel 2, recovering...
May 19 08:18:09 titan kernel: asynchronous wait on fence nouveau:Xorg[13526]:4a14 timed out
May 19 08:18:21 titan kernel: asynchronous wait on fence nouveau:Xorg[13526]:4a19 timed out
May 19 08:18:31 titan kernel: asynchronous wait on fence nouveau:Xorg[13526]:4a1a timed out
May 19 08:18:43 titan kernel: asynchronous wait on fence nouveau:Xorg[13526]:4a1b timed out
May 19 08:21:02 titan kernel: nouveau 0000:01:00.0: Xorg[13526]: failed to idle channel 2 [Xorg[13526]]
May 19 08:21:17 titan kernel: nouveau 0000:01:00.0: Xorg[13526]: failed to idle channel 2 [Xorg[13526]]
May 19 08:21:17 titan kernel: nouveau 0000:01:00.0: disp: 0x64a8[0]: INIT_GENERIC_CONDITON: unknown 0x07
May 19 08:21:17 titan kernel: ------------[ cut here ]------------
May 19 08:21:17 titan kernel: WARNING: CPU: 7 PID: 13653 at drivers/gpu/drm/nouveau/nouveau_bo.c:137 nouveau_bo_del_ttm+0x7f/0x90 [nouveau]
May 19 08:21:17 titan kernel: Modules linked in: lp parport hid_plantronics rfcomm ccm xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute bridge ip6table_security ip6table_raw ip6table_mangle ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 iptable_security iptable_raw iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c ebtable_filter ebtables ip6table_filter ip6_tables cmac bnep dm_crypt vfat fat btusb btrtl btbcm uvcvideo btintel bluetooth videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_realtek kvm_intel iwlmvm snd_hda_codec_generic kvm mac80211 snd_hda_intel
May 19 08:21:17 titan kernel: snd_hda_codec irqbypass crct10dif_pclmul snd_hda_core crc32_pclmul mei_wdt iTCO_wdt snd_hwdep iTCO_vendor_support ghash_clmulni_intel snd_seq intel_cstate intel_uncore intel_rapl_perf iwlwifi snd_seq_device snd_pcm rtsx_pci_ms ie31200_edac cfg80211 joydev memstick mei_me snd_timer i2c_i801 mei intel_pch_thermal edac_core shpchp thinkpad_acpi snd soundcore tpm_crb rfkill tpm_tis tpm_tis_core tpm nfsd auth_rpcgss nfs_acl lockd grace sunrpc mmc_block 8021q garp stp llc mrp nouveau i915 rtsx_pci_sdmmc mmc_core mxm_wmi ttm i2c_algo_bit drm_kms_helper e1000e drm crc32c_intel nvme ptp serio_raw rtsx_pci pps_core nvme_core wmi video fjes
May 19 08:21:17 titan kernel: CPU: 7 PID: 13653 Comm: InputThread Tainted: G        W       4.10.14-200.fc25.x86_64 #1
May 19 08:21:17 titan kernel: Hardware name: LENOVO 20EQS59X00/20EQS59X00, BIOS N1EET65W (1.38 ) 02/09/2017
May 19 08:21:17 titan kernel: Call Trace:
May 19 08:21:17 titan kernel: dump_stack+0x63/0x86
May 19 08:21:17 titan kernel: __warn+0xcb/0xf0
May 19 08:21:17 titan kernel: warn_slowpath_null+0x1d/0x20
May 19 08:21:17 titan kernel: nouveau_bo_del_ttm+0x7f/0x90 [nouveau]
May 19 08:21:17 titan kernel: ttm_bo_release_list+0xcb/0x210 [ttm]
May 19 08:21:17 titan kernel: ttm_bo_release+0x198/0x240 [ttm]
May 19 08:21:17 titan kernel: ttm_bo_unref+0x24/0x30 [ttm]
May 19 08:21:17 titan kernel: nouveau_gem_object_del+0x94/0xf0 [nouveau]
May 19 08:21:17 titan kernel: drm_gem_object_free+0x29/0x70 [drm]
May 19 08:21:17 titan kernel: drm_gem_object_unreference_unlocked+0x3a/0xa0 [drm]
May 19 08:21:17 titan kernel: drm_gem_object_handle_unreference_unlocked+0x65/0xb0 [drm]
May 19 08:21:17 titan kernel: drm_gem_object_release_handle+0x53/0x90 [drm]
May 19 08:21:17 titan kernel: idr_for_each+0xb0/0x110
May 19 08:21:17 titan kernel: ? drm_gem_object_handle_unreference_unlocked+0xb0/0xb0 [drm]
May 19 08:21:17 titan kernel: ? drm_fb_release+0x16b/0x190 [drm]
May 19 08:21:17 titan kernel: drm_gem_release+0x20/0x30 [drm]
May 19 08:21:17 titan kernel: drm_release+0x34c/0x3a0 [drm]
May 19 08:21:17 titan kernel: __fput+0xdf/0x1e0
May 19 08:21:17 titan kernel: ____fput+0xe/0x10
May 19 08:21:17 titan kernel: task_work_run+0x80/0xa0
May 19 08:21:17 titan kernel: do_exit+0x2c8/0xb80
May 19 08:21:17 titan kernel: ? pick_next_task_fair+0x113/0x4d0
May 19 08:21:17 titan kernel: ? __switch_to+0x227/0x460
May 19 08:21:17 titan kernel: do_group_exit+0x47/0xb0
May 19 08:21:17 titan kernel: get_signal+0x289/0x630
May 19 08:21:17 titan kernel: do_signal+0x37/0x690
May 19 08:21:17 titan kernel: ? wake_up_q+0x80/0x80
May 19 08:21:17 titan kernel: exit_to_usermode_loop+0x76/0xb0
May 19 08:21:17 titan kernel: syscall_return_slowpath+0xaa/0xb0
May 19 08:21:17 titan kernel: entry_SYSCALL_64_fastpath+0xa7/0xa9
May 19 08:21:17 titan kernel: RIP: 0033:0x7f9f54fe5573
May 19 08:21:17 titan kernel: RSP: 002b:00007f9f47fc7f20 EFLAGS: 00000293 ORIG_RAX: 00000000000000e8
May 19 08:21:17 titan kernel: RAX: fffffffffffffffc RBX: 00000000031f8198 RCX: 00007f9f54fe5573
May 19 08:21:17 titan kernel: RDX: 0000000000000100 RSI: 00007f9f47fc7f30 RDI: 0000000000000024
May 19 08:21:17 titan kernel: RBP: 00000000031f8198 R08: 0000000000000000 R09: 00007f9f40008900
May 19 08:21:17 titan kernel: R10: 00000000ffffffff R11: 0000000000000293 R12: 00000000031f81d0
May 19 08:21:17 titan kernel: R13: 00007ffd88deef6f R14: 00007f9f47fc99c0 R15: 00007f9f47fc9700
May 19 08:21:17 titan kernel: ---[ end trace 3e2c2f8fcc436ff4 ]---

Comment 1 Robert Story 2017-05-19 13:32:16 UTC
Created attachment 1280428 [details]
annotated Xorg

Comment 2 Robert Story 2017-05-19 13:38:05 UTC
Note: first dock works if you boot/login while undocked. It's docking after undocking (while logged in).

Comment 3 Robert Story 2017-05-19 13:56:39 UTC
Created attachment 1280430 [details]
dnf update that broke docking

dnf log from last update. prior to this update, on kernel 4.10.8-200.fc25.x86_64, both docking and undocking multiple times a day worked great.

Comment 4 Fedora Update System 2017-05-19 15:00:23 UTC
xorg-x11-drv-nouveau-1.0.15-2.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-0031ce08bf

Comment 5 Robert Story 2017-05-19 15:36:07 UTC
tried 1.0.15-2, same bad behaviour.

Comment 6 Ben Skeggs 2017-05-19 15:43:01 UTC
If you boot the older kernel, do things work as expected?

Comment 7 Robert Story 2017-05-19 20:30:12 UTC
I didn't try it with 1.0.15-2, but did after downgrading to 1.0.13. It didn't help. Something else that got upgraded must factor into it. I just haven't had time to figure out what it might be.

Comment 8 Ben Skeggs 2017-05-20 00:47:52 UTC
(In reply to Robert Story from comment #7)
> I didn't try it with 1.0.15-2, but did after downgrading to 1.0.13. It
> didn't help. Something else that got upgraded must factor into it. I just
> haven't had time to figure out what it might be.

Can you try it again with 1.0.15-2?  There are multiple factors at play here.  I suspect your upgrade from 4.9->4.10 kernel is responsible for the errors in your kernel log at least.

Comment 9 Fedora Update System 2017-05-20 22:31:56 UTC
xorg-x11-drv-nouveau-1.0.15-2.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-0031ce08bf

Comment 10 Fedora Update System 2017-05-23 00:41:10 UTC
xorg-x11-drv-nouveau-1.0.15-2.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.

Comment 11 Robert Story 2017-06-02 21:04:20 UTC
Created attachment 1284529 [details]
latest attempt

Still happening to me. An initial dock/undock works, but the next dock locks up. No stack trace in messages this time, though. Testing done after yum update this morning to all current packages.

[root@titan ~]# rpm -qa xorg-x11-drv-nouveau
xorg-x11-drv-nouveau-1.0.15-2.fc25.x86_64

[root@titan ~]# uname -a
Linux titan.int.futz.org 4.11.3-200.fc25.x86_64 #1 SMP Thu May 25 19:03:07 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Comment 12 Fedora End Of Life 2017-11-16 19:51:37 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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 13 Fedora End Of Life 2017-12-12 10:53:06 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.

Comment 14 Arnaud Lacombe 2018-01-02 09:07:21 UTC
Just happened randomly on an up-to-date Fedora 27. No docking involved, just "normal" desktop use in a dual GPU setup. Mouse responsive, but everything else dead. Killing Xorg "fixed" the issue.

some info...

/% rpm -qa xorg-x11-drv-nouveau
xorg-x11-drv-nouveau-1.0.15-3.fc27.x86_64

~/% uname -a
Linux hanoli 4.14.8-300.fc27.x86_64 #1 SMP Wed Dec 20 19:00:18 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Comment 15 Arnaud Lacombe 2018-01-02 09:20:34 UTC
Some relevant information in the dmesg buffer:

[271587.979780] nouveau 0000:01:00.0: gr: TRAP ch 2 [007f955000 Xorg[1473]]
[271587.979789] nouveau 0000:01:00.0: gr: GPC0/TPC0/TEX: 80000041
[271587.979794] nouveau 0000:01:00.0: gr: GPC0/TPC1/TEX: 80000041
[271587.979797] nouveau 0000:01:00.0: gr: GPC0/TPC2/TEX: 80000041
[271587.979801] nouveau 0000:01:00.0: gr: GPC0/TPC3/TEX: 80000041
[271587.979804] nouveau 0000:01:00.0: gr: GPC0/TPC4/TEX: 80000041
[271587.979814] nouveau 0000:01:00.0: fifo: read fault at 0001af4000 engine 00 [GR] client 07 [GPC0/T1_2] reason 02 [PTE] on channel 2 [007f955000 Xorg[1473]]
[271587.979819] nouveau 0000:01:00.0: fifo: channel 2: killed
[271587.979821] nouveau 0000:01:00.0: fifo: runlist 0: scheduled for recovery
[271587.979824] nouveau 0000:01:00.0: fifo: engine 0: scheduled for recovery
[271587.979830] nouveau 0000:01:00.0: fifo: engine 5: scheduled for recovery
[271587.979859] nouveau 0000:01:00.0: Xorg[1473]: channel 2 killed!
[271638.386491] asynchronous wait on fence nouveau:Xorg[1473]:284f8b timed out
[271688.050038] asynchronous wait on fence nouveau:Xorg[1473]:284f90 timed out
[271737.201617] asynchronous wait on fence nouveau:Xorg[1473]:284fa2 timed out
[271787.377169] asynchronous wait on fence nouveau:Xorg[1473]:284fa6 timed out


Note You need to log in before you can comment on or make changes to this bug.