Comment # 5
on bug 93017
from Yaroslav Halchenko
reporting on "success": after new patched kernel installation and some ugprades (kept crashing gnome not kernel, so had to upgrade), caused the stall with a bit different but overall similar traceback (full output of journalctl for that boot is attached): Nov 20 10:04:38 hopa kernel: [drm:intel_hdmi_detect] [CONNECTOR:53:HDMI-A-2] Nov 20 10:04:38 hopa kernel: ffff88043c187858 0000000000000001 ffffffff81555c51 ffff88043c678080 Nov 20 10:04:38 hopa kernel: Call Trace: Nov 20 10:04:38 hopa kernel: [<ffffffff8108678d>] ? wq_worker_sleeping+0xd/0x90 Nov 20 10:04:38 hopa kernel: [<ffffffff81555835>] ? __schedule+0x505/0x8f0 Nov 20 10:04:38 hopa kernel: [<ffffffff81555c51>] ? schedule+0x31/0x80 Nov 20 10:04:38 hopa kernel: [<ffffffff8107209c>] ? do_exit+0x72c/0xa90 Nov 20 10:04:38 hopa kernel: [<ffffffff810175ec>] ? oops_end+0x9c/0xd0 Nov 20 10:04:38 hopa kernel: [drm:intel_hdmi_detect] Live status not up! Nov 20 10:04:38 hopa kernel: [drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:53:HDMI-A-2] disconnected Nov 20 10:04:38 hopa kernel: [<ffffffff8155b5d8>] ? general_protection+0x28/0x30 Nov 20 10:04:38 hopa kernel: [<ffffffff8140689f>] ? reservation_object_test_signaled_rcu+0xcf/0x220 Nov 20 10:04:38 hopa kernel: [<ffffffff81406ef9>] ? reservation_object_wait_timeout_rcu+0x219/0x260 Nov 20 10:04:38 hopa kernel: [<ffffffffa0832b29>] ? ttm_bo_wait+0x29/0x50 [ttm] Nov 20 10:04:38 hopa kernel: [<ffffffffa0833207>] ? ttm_bo_cleanup_refs_and_unlock+0x27/0x170 [ttm] Nov 20 10:04:38 hopa kernel: [<ffffffffa083340f>] ? ttm_bo_delayed_delete+0xbf/0x200 [ttm] Nov 20 10:04:38 hopa kernel: [<ffffffffa0833567>] ? ttm_bo_delayed_workqueue+0x17/0x40 [ttm] Nov 20 10:04:38 hopa kernel: [<ffffffff810856ff>] ? process_one_work+0x19f/0x3d0 Nov 20 10:04:38 hopa kernel: [<ffffffff8108597d>] ? worker_thread+0x4d/0x450 Nov 20 10:04:38 hopa kernel: [<ffffffff81085930>] ? process_one_work+0x3d0/0x3d0 Nov 20 10:04:38 hopa kernel: [<ffffffff8108b47d>] ? kthread+0xbd/0xe0 Nov 20 10:04:38 hopa kernel: [<ffffffff8108b3c0>] ? kthread_create_on_node+0x170/0x170 Nov 20 10:04:38 hopa kernel: [<ffffffff8155984f>] ? ret_from_fork+0x3f/0x70 Nov 20 10:04:38 hopa kernel: [<ffffffff8108b3c0>] ? kthread_create_on_node+0x170/0x170 Nov 20 10:04:38 hopa kernel: Code: 48 c7 c7 b2 07 80 81 e8 83 39 fe ff e9 bf fe ff ff 0f 1f 40 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 8b 87 40 04 00 00 <48> 8b 40 d8 c3 0f 1f 44 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f Nov 20 10:04:38 hopa kernel: RIP [<ffffffff8108ba2c>] kthread_data+0xc/0x20 Nov 20 10:04:38 hopa kernel: RSP <ffff88043c187b98> Nov 20 10:04:38 hopa kernel: CR2: ffffffffffffffd8 Nov 20 10:04:38 hopa kernel: ---[ end trace 01c0854cd2e7cf2f ]--- Nov 20 10:04:38 hopa kernel: Fixing recursive fault but reboot is needed! To stall it, I had both displays connected where 2nd one was just mirroring the first one. And I have turned off the 2nd display which caused all the mess what could be the next step? ;-) BTW -- with this recent upgrade, now two attached monitors are also seen as an extended desktop (3840x1200) which never happened before, and actually works quite nicely. but then also caused crash (no traceback was recorded and I didn't have remote session attached) using the same trick of turning the 2nd display off
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
