Dear Maintainer, a new version of "twm" (1.0.12) fixes following: (II) [KMS] Kernel modesetting enabled. xinit: connection to X server lost waiting for X server to shut down (II) Server terminated successfully (0). Closing log file. ------------[ cut here ]------------ WARNING: CPU: 1 PID: 1877 at drivers/gpu/drm/ttm/ttm_bo.c:356 ttm_bo_release+0x30c/0x330 [ttm] Modules linked in: nft_reject_ipv4 nf_reject_ipv4 nft_reject nft_ct nf_log_syslog nft_log radeon drm_ttm_helper ttm drm_display_helper drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops CPU: 1 PID: 1877 Comm: Xorg Not tainted 6.0.2-1 #1 Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./E350N WIN8, BIOS F3 01/18/2013 RIP: 0010:ttm_bo_release+0x30c/0x330 [ttm] Code: 00 e8 88 96 39 e1 48 8b 43 e8 eb a7 be 03 00 00 00 e8 18 b1 23 e1 e9 f7 fd ff ff e8 0e 74 39 e1 e9 ed fd ff ff 4c 89 e0 eb 89 <0f> 0b 48 83 7b 20 00 0f 84 27 fd ff ff 0f 0b e9 20 fd ff ff 0f 0b RSP: 0018:ffffc900005abd98 EFLAGS: 00010202 RAX: 0000000000000000 RBX: ffff888100f655c8 RCX: 0000000000000000 RDX: 0000000000000002 RSI: ffffffff81da8c49 RDI: ffff888100f655c8 RBP: ffff888100f65478 R08: 0000000000000064 R09: ffff88810078e960 R10: ffffc900005abe68 R11: 0000000000000001 R12: ffff888100f5c6f0 R13: ffff88810006c7a0 R14: ffff8881007c6f00 R15: ffff888104a306d8 FS: 00007f9f64a09a80(0000) GS:ffff88813c300000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f9f64a77008 CR3: 000000000200c000 CR4: 00000000000006e0 Call Trace: <TASK> ? fsnotify_grab_connector+0x3e/0x70 radeon_bo_unref+0x15/0x30 [radeon] radeon_gem_object_free+0x2b/0x50 [radeon] drm_gem_dmabuf_release+0x31/0x50 dma_buf_release+0x35/0x90 __dentry_kill+0xf0/0x160 __fput+0xd3/0x240 task_work_run+0x57/0x90 do_exit+0x274/0x8d0 do_group_exit+0x28/0x90 __x64_sys_exit_group+0xf/0x10 do_syscall_64+0x3a/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f9f644d6459 Code: Unable to access opcode bytes at RIP 0x7f9f644d642f. RSP: 002b:00007ffcdcc26a98 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7 RAX: ffffffffffffffda RBX: 00007f9f645f09e0 RCX: 00007f9f644d6459 RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000000 RBP: 0000000000000000 R08: fffffffffffffc78 R09: 00007f9f645fbb00 R10: 27c3fa55cc3ade70 R11: 0000000000000246 R12: 00007f9f645f09e0 R13: 0000000000000000 R14: 00007f9f645f5ec8 R15: 00007f9f645f5ee0 </TASK> ---[ end trace 0000000000000000 ]---
The new version did not fix the observed behaviour.
----- Original Message ----- | From: "Bjarni Ingi Gislason" <bjarniig@simnet.is> | To: 1022006@bugs.debian.org | Cc: "Bjarni Ingi Gislason" <bingigis@simnet.is> | Sent: Sunday, March 5, 2023 4:24:44 PM | Subject: Bug#1022006: Acknowledgement (New version fixes a warning) | The new version did not fix the observed behaviour. For the given bug-report, I don't recall any relevant changes.
The indication of a bug disappeared after updating the following: Start-Date: 2023-07-18 10:50:11 Commandline: apt-get upgrade Upgrade: libnftnl11:amd64 (1.2.5-1, 1.2.6-1), libctf-nobfd0:amd64 (2.40.90.20230705-1, 2.40.90.20230714-2), libbinutils:amd64 (2.40.90.20230705-1, 2.40.90.20230714-2), libfreetype6:amd64 (2.12.1+dfsg-5, 2.13.0+dfsg-1), binutils-x86-64-linux-gnu:amd64 (2.40.90.20230705-1, 2.40.90.20230714-2), binutils-doc:amd64 (2.40.90.20230705-1, 2.40.90.20230714-2), libctf0:amd64 (2.40.90.20230705-1, 2.40.90.20230714-2), rsyslog:amd64 (8.2306.0-1, 8.2306.0-2), binutils-common:amd64 (2.40.90.20230705-1, 2.40.90.20230714-2), libsframe1:amd64 (2.40.90.20230705-1, 2.40.90.20230714-2), libgprofng0:amd64 (2.40.90.20230705-1, 2.40.90.20230714-2), libharfbuzz0b:amd64 (6.0.0+dfsg-3, 8.0.1-1), xterm:amd64 (383-1, 384-1), binutils:amd64 (2.40.90.20230705-1, 2.40.90.20230714-2) End-Date: 2023-07-18 10:51:01
This was a one time without the similar output in the first e-mail. So the behaviour is unchanged. Happens after this sequence of commands: xinit & firefox-esr einstein exit (from einstein) exit (from twm) [pushing the return key returns to the shell]