Wlroots: sway/wlroots hang with nouveau spam in logs after upgrade

Created on 28 Jun 2021  路  8Comments  路  Source: swaywm/wlroots

After upgrading sway from 1.6 to 1.6.1 and wlroots from 1.13.0 to 1.14.0, I'm getting nouveau error spam in dmesg. It happens after sway starts and I launch firefox:

2021-06-28T07:58:21.121808-07:00 localhost kernel: [  126.779168] nouveau 0000:01:00.0: DRM: bo 0000000019986f93 pinned elsewhere: 0x00000001 vs 0x00000002

After that everything just hangs, although responds to input (I can blindly type swaymsg exit).

WLR_DRM_NO_MODIFIERS=1 is set. Kernel version 5.12.12_1
Prior to the package upgrade, everything worked as expected.

Attached debug log.
sway.log

bug backendrm

Most helpful comment

All 8 comments

In wlroots logs:

00:00:05.476 [DEBUG] [wlr] [backend/drm/legacy.c:93] connector DP-2: drmModeSetCursor failed: Device or resource busy

In dmesg:

juil. 03 10:02:39 LN-TW-01 kernel: nouveau 0000:01:00.0: DRM: Moving pinned object 00000000e0ba99fc!
juil. 03 10:02:39 LN-TW-01 kernel: nouveau 0000:01:00.0: DRM: bo 000000009718d4c6 pinned elsewhere: 0x00000001 vs 0x00000002
juil. 03 10:02:39 LN-TW-01 kernel: nouveau 0000:01:00.0: DRM: bo 000000009718d4c6 pinned elsewhere: 0x00000001 vs 0x00000002
juil. 03 10:02:39 LN-TW-01 kernel: nouveau 0000:01:00.0: DRM: bo 000000009718d4c6 pinned elsewhere: 0x00000001 vs 0x00000002
juil. 03 10:02:39 LN-TW-01 kernel: nouveau 0000:01:00.0: DRM: bo 000000009718d4c6 pinned elsewhere: 0x00000001 vs 0x00000002

I am experiencing the same issue. I went through a git bisect session since last working version (0.13), the commit that is introducing the regression is: https://github.com/swaywm/wlroots/commit/6c3d080e25e56404228ad7704eed43e40fa0c623.

That commit is about the cursor. That would make sense to me, since for me it seemed to appear after the cursor image was changed.

@emersion I can confirm that #3021 fixes the issue (writing this very comment from ff on an external monitor with nouveau, your branch runs smoothly overall).

Thanks for fixing this so quickly :+1:

I've confirmed it works as well :+1:

Fixed here, thank you very much

Fixed for me as well, thank you very much!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

fwSmit picture fwSmit  路  4Comments

ddevault picture ddevault  路  5Comments

luispabon picture luispabon  路  4Comments

ddevault picture ddevault  路  5Comments

p-hamann picture p-hamann  路  4Comments