[DragonFlyBSD - Bug #3200] master: weston screen freezes

2019-11-07 Thread bugtracker-admin
Issue #3200 has been updated by peeter. OK the issue with the name of the thread is a non-issue: the name is a null terminated string, so "weston\000launcher\000" = "weston", and the trailing "launcher" shows it's a child of weston-launcer, exactly as it should be. Peeter --

[DragonFlyBSD - Bug #3200] master: weston screen freezes

2019-10-30 Thread bugtracker-admin
Issue #3200 has been updated by peeter. I may have a theory about what is going on. - "weston" is waiting for "drmev" which is owned by "ithread16 2" - "ithread16 2" is waiting for "lwq" which is owned by "weston" - It might seem that there is a slight confusion with the latter statement.

[DragonFlyBSD - Bug #3200] master: weston screen freezes

2019-10-26 Thread bugtracker-admin
Issue #3200 has been updated by peeter. OK I haven't printed out the lock info that the "ithread16 2" is trying to acquire in frame 3. Will do this next time. (I believe I printed it out, but it was "lwe", not "drmev" that "ithread16 2" was trying to acquire in frame 3 in the lockmgr().)

[DragonFlyBSD - Bug #3200] master: weston screen freezes

2019-10-25 Thread bugtracker-admin
Issue #3200 has been updated by peeter. File weston-drmev-bug-2.md added I attach the backtraces. 1 - the weston thread is trying acquire a lock which is held by "ithread16 2" 2 - in the "ithread16 2" backtrace, the lock has been acquired in do_intel_finish_page_flip: 10919:

[DragonFlyBSD - Bug #3200] master: weston screen freezes

2019-10-24 Thread bugtracker-admin
Issue #3200 has been updated by dillon. So far ftigeot has not had any luck reproducing it, but there's almost enough information in the bug report to track the issue down. What we have in your original backtrace is that it's stuck trying to acquire a lock, which means that some other thread

[DragonFlyBSD - Bug #3200] master: weston screen freezes

2019-10-23 Thread bugtracker-admin
Issue #3200 has been updated by peeter. I seem to have forgotten to specify how to reproduce the situation: Create a minimalistic ~/.config/weston.ini --- [core] backend=drm-backend.so modules=xwayland.so --- Then start weston with % weston-launch -- --use-pixman >& log/weston.0.log Click

[DragonFlyBSD - Bug #3200] master: weston screen freezes

2019-08-07 Thread bugtracker-admin
Issue #3200 has been updated by peeter. The machine is intel i7 skylake (i7-6700). Bug #3200: master: weston screen freezes http://bugs.dragonflybsd.org/issues/3200#change-13774 * Author: peeter * Status: New * Priority: Normal * Assignee: * Category:

[DragonFlyBSD - Bug #3200] master: weston screen freezes

2019-08-07 Thread bugtracker-admin
Issue #3200 has been updated by peeter. OK this bug has now become my daily companion. Can't find the deadlock. Bug #3200: master: weston screen freezes http://bugs.dragonflybsd.org/issues/3200#change-13773 * Author: peeter * Status: New * Priority: