System hard locks intermittently on login. This is as close as I've been able to get to a backtrace. Since it is intermittent, I've had no luck getting this bisected. IF I get past login, everything is fine for the remainder of the session - or at least, I've never had any issues, and I've had some very extended sessions. Linux 4.9.0-GTW2+ #123 SMP Sat Dec 17 19:39:34 EST 2016 x86_64 GNU/Linux Dec 17 19:40:10 ringle kernel: worker_thread+0x4b/0x510 Dec 17 19:40:10 ringle kernel: kthread+0x101/0x140 Dec 17 19:40:10 ringle kernel: ? process_one_work+0x450/0x450 Dec 17 19:40:10 ringle kernel: ? kthread_create_on_node+0x40/0x40 Dec 17 19:40:10 ringle kernel: ret_from_fork+0x2a/0x40 Dec 17 19:40:10 ringle kernel: Code: ff ff ff 74 58 48 8d 7d c0 44 89 ea 4c 89 e6 e8 1d 36 ff ff 48 8b 43 08 48 8d 55 c0 48 89 df 48 8d b0 80 37 00 00 e8 c6 2e fc ff <48> 8b 50 78 48 85 d2 74 04 83 6a 20 01 48 89 c7 e8 41 71 fc ff Dec 17 19:40:10 ringle kernel: RIP: intel_unpin_fb_obj+0x5a/0xb0 RSP: ffffc90003483dd8 Dec 17 19:40:10 ringle kernel: CR2: 0000000000000078 Dec 17 19:40:10 ringle kernel: ---[ end trace 54f93fd89be4561f ]---
I can reproduce this. I reported this on IRC on Dec 07. The BUG() seems to be in this line: lockdep_assert_held(&vma->obj->base.dev->struct_mutex); What I got as answers were "just the messenger" and "there's a few bug reports with trying to unpin an absent vma".
Changing to High since this freezes the machine while logging in.
*** This bug has been marked as a duplicate of bug 98829 ***
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.