dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Hellström (Intel)" <thomas_os@shipmail.org>
To: "Daniel Vetter" <daniel.vetter@ffwll.ch>,
	"Christian König" <christian.koenig@amd.com>,
	linux-graphics-maintainer@vmware.com
Cc: DRI Development <dri-devel@lists.freedesktop.org>
Subject: vmwgfx leaking bo pins?
Date: Thu, 11 Mar 2021 11:46:12 +0100	[thread overview]
Message-ID: <09ebc5cf-3e2c-d233-2c58-ff4d72e01297@shipmail.org> (raw)

Hi,

I tried latest drm-fixes today and saw a lot of these: Fallout from ttm 
rework?

/Thomas

[  298.404788] WARNING: CPU: 1 PID: 3839 at 
drivers/gpu/drm/ttm/ttm_bo.c:512 ttm_bo_release+0x2b5/0x300 [ttm]
[  298.404795] Modules linked in: nls_utf8 isofs rfcomm tun bridge stp 
llc ip6table_nat ip6table_mangle ip6table_raw ip6table_security 
iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 libcrc32c nf_defrag_ipv4 
iptable_mangle iptable_raw iptable_security ip_set nfnetlink 
ip6table_filter ip6_tables iptable_filter cmac bnep vsock_loopback 
vmw_vsock_virtio_transport_common vmw_vsock_vmci_transport vsock 
snd_seq_midi snd_seq_midi_event intel_rapl_msr snd_ens1371 
snd_ac97_codec ac97_bus vmw_balloon intel_rapl_common snd_seq rapl 
snd_pcm btusb btrtl btbcm btintel bluetooth joydev gameport snd_timer 
snd_rawmidi snd_seq_device rfkill snd ecdh_generic vmw_vmci ecc 
soundcore i2c_piix4 auth_rpcgss sunrpc ip_tables vmwgfx drm_kms_helper 
cec ttm e1000 crct10dif_pclmul crc32_pclmul crc32c_intel 
ghash_clmulni_intel drm mptspi serio_raw scsi_transport_spi mptscsih 
mptbase ata_generic pata_acpi uas usb_storage fuse
[  298.404837] CPU: 1 PID: 3839 Comm: thunderbird Tainted: G        
W         5.12.0-rc2+ #42
[  298.404839] Hardware name: VMware, Inc. VMware Virtual Platform/440BX 
Desktop Reference Platform, BIOS 6.00 07/29/2019
[  298.404840] RIP: 0010:ttm_bo_release+0x2b5/0x300 [ttm]
[  298.404845] Code: e8 a0 f3 35 ce e9 da fd ff ff 49 8b 7e 90 b9 30 75 
00 00 31 d2 be 01 00 00 00 e8 c6 17 36 ce 49 8b 46 e0 eb 9e 48 89 e8 eb 
99 <0f> 0b 41 c7 86 94 00 00 00 00 00 00 00 49 8d 76 08 31 d2 4c 89 ef
[  298.404847] RSP: 0018:ffffb24a43ef3bd0 EFLAGS: 00010202
[  298.404848] RAX: 0000000000000001 RBX: 0000000000000000 RCX: 
0000000000000001
[  298.404850] RDX: 0000000000000001 RSI: 0000000000000246 RDI: 
ffffffffc03c50e8
[  298.404851] RBP: ffff9ad4429f2620 R08: 0000000000000001 R09: 
ffff9ad4429f2000
[  298.404852] R10: ffff9ad48664e090 R11: 0000000000000000 R12: 
ffff9ad4e71371d0
[  298.404852] R13: ffff9ad4e7137000 R14: ffff9ad4e7137168 R15: 
ffff9ad48710f4c0
[  298.404854] FS:  00007fc6d9ae4780(0000) GS:ffff9ad576e40000(0000) 
knlGS:0000000000000000
[  298.404855] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  298.404857] CR2: 00007fc6c6740000 CR3: 00000001a4eac004 CR4: 
00000000003706e0
[  298.404864] Call Trace:
[  298.404866]  vmw_resource_release+0x131/0x1f0 [vmwgfx]
[  298.404878]  vmw_context_cotables_unref.isra.0+0x6f/0xa0 [vmwgfx]
[  298.404891]  vmw_resource_release+0x16a/0x1f0 [vmwgfx]
[  298.404901]  vmw_user_context_base_release+0x31/0x50 [vmwgfx]
[  298.404912]  ttm_release_base+0x7f/0xc0 [vmwgfx]
[  298.404922]  ttm_ref_object_release+0xde/0xf0 [vmwgfx]
[  298.404931]  ttm_ref_object_base_unref+0x8e/0xb0 [vmwgfx]
[  298.404940]  ? vmw_dx_context_unbind+0x1e0/0x1e0 [vmwgfx]
[  298.404951]  drm_ioctl_kernel+0xaa/0xf0 [drm]
[  298.404974]  drm_ioctl+0x20f/0x3a0 [drm]
[  298.404991]  ? vmw_dx_context_unbind+0x1e0/0x1e0 [vmwgfx]
[  298.405003]  ? selinux_file_ioctl+0x135/0x230
[  298.405006]  ? drm_version+0x90/0x90 [drm]
[  298.405023]  vmw_generic_ioctl+0xab/0x150 [vmwgfx]
[  298.405033]  __x64_sys_ioctl+0x83/0xb0
[  298.405035]  do_syscall_64+0x33/0x40
[  298.405038]  entry_SYSCALL_64_after_hwframe+0x44/0xae
[  298.405041] RIP: 0033:0x7fc6d9be15db
[  298.405042] Code: 89 d8 49 8d 3c 1c 48 f7 d8 49 39 c4 72 b5 e8 1c ff 
ff ff 85 c0 78 ba 4c 89 e0 5b 5d 41 5c c3 f3 0f 1e fa b8 10 00 00 00 0f 
05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 6d b8 0c 00 f7 d8 64 89 01 48
[  298.405044] RSP: 002b:00007ffc8ce6de98 EFLAGS: 00000246 ORIG_RAX: 
0000000000000010
[  298.405046] RAX: ffffffffffffffda RBX: 00007ffc8ce6dee0 RCX: 
00007fc6d9be15db
[  298.405048] RDX: 00007ffc8ce6dee0 RSI: 0000000040086448 RDI: 
0000000000000007
[  298.405049] RBP: 0000000040086448 R08: 0000000000000000 R09: 
0000000000000000
[  298.405050] R10: 0000000000000000 R11: 0000000000000246 R12: 
00007fc6d98e0000
[  298.405051] R13: 0000000000000007 R14: 00007fc6d98ea3b0 R15: 
00007fc6c671f800
[  298.405053] ---[ end trace c628fb3ea8b5aa96 ]---

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2021-03-11 10:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11 10:46 Thomas Hellström (Intel) [this message]
2021-03-11 11:32 ` AW: vmwgfx leaking bo pins? Koenig, Christian
2021-03-11 12:36   ` Thomas Hellström (Intel)
2021-03-11 21:07 ` Zack Rusin
2021-03-11 22:35   ` Thomas Hellström (Intel)
2021-03-11 23:02     ` Zack Rusin
2021-03-12  8:13       ` Christian König
2021-03-12 10:06       ` Thomas Hellström (Intel)
2021-03-15 17:57         ` Zack Rusin
2021-03-15 20:38           ` Daniel Vetter
2021-03-15 22:35             ` Thomas Hellström (Intel)
2021-03-17  1:51               ` Zack Rusin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=09ebc5cf-3e2c-d233-2c58-ff4d72e01297@shipmail.org \
    --to=thomas_os@shipmail.org \
    --cc=christian.koenig@amd.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-graphics-maintainer@vmware.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox