From nobody Mon Sep 6 18:37:39 2021 X-Original-To: freebsd-x11@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 8343617B770B for ; Mon, 6 Sep 2021 18:37:46 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4H3HFk37Dzz3C7n; Mon, 6 Sep 2021 18:37:46 +0000 (UTC) (envelope-from jbeich@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1630953466; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=jUOYRAiTVsjmCPhYZpusBYbWA0d6jidMAnnh9qLjvdE=; b=hRrTAE3j3aJfhW49j0INidoUCUhcMA5JJX8P+oVq9yAsATq80mdtRlfPbns1a75IsrhUVh BYiu97MPooruzmzlpu/ZSPQbhOBVHXmFix62s7MYMyM4gV0lc6AbMEE9YGRJIy9jNbt5AO OFMdvwwzXuZZl9gte9YRnQsiukwv8ag6hPrwoR9jGIn9wwKoE34H03mRIOfvP/kVZ/i8Zr eQwtYbrMU7YTAuG00P5aoZjmDI6x5BtiXEj4aXNxqSWDa6eECTz9f6ttRtCGIDR9rao/bz uQ+0P/7adsHhiwMxPEnHeBMo406FjNw4IIocRNrZ3MOw9IJp5MZa0zHBtlHCSQ== Received: by freefall.freebsd.org (Postfix, from userid 1354) id 486FED00; Mon, 6 Sep 2021 18:37:46 +0000 (UTC) From: Jan Beich To: pete@nomadlogic.org Cc: freebsd-x11@freebsd.org Subject: Re: Issues with Chromium/Vulkan after upgrading vulkan to 1.2.190 References: Date: Mon, 06 Sep 2021 20:37:39 +0200 In-Reply-To: (Pete Wright via freebsd-x's message of "Mon, 6 Sep 2021 10:11:12 -0700") Message-ID: <8s09-zh1o-wny@FreeBSD.org> List-Id: X11 List-Archive: https://lists.freebsd.org/archives/freebsd-x11 List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-x11@freebsd.org X-BeenThere: freebsd-x11@freebsd.org MIME-Version: 1.0 Content-Type: text/plain ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1630953466; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=jUOYRAiTVsjmCPhYZpusBYbWA0d6jidMAnnh9qLjvdE=; b=jLHJDn8GhyzPWEvPIbbZB+I3eIjuiijq8tv3qBY9VqkdqSzBaY3fr4p60nor+IFzvezlKn 00zdJsKpkFOz3/hXNVUdKfKYtBlovQFvTkPFzyLfATnbsaq2SkuevR/s288ry979sofOC4 nW7bpaGX/0LKYkD2BRHZU1wCusRwlJKBp1SZy6cucfGkdqAxIYsxwlxJyp8/RVd0Pdggbu UnXGNvLoeqPQ/sBdvmgoDSynRkGCqiX9SAigmaVQicurQSnmfuO5SwD2RlINsHinwexYUS msr24fOmnVRhCQQwPjXtMtO/84zUoMdCQmcnwREGQq8uo6uVPYvo/72T1bzqFw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1630953466; a=rsa-sha256; cv=none; b=YJaW8Xp1m2UMrnKls1KMoS1voFbXLsKWNdcSQgOiTrscVi/cYWUtRHwJj7oyfsuAr16EAu ZL56cZQ7VNFE0B62Fpadg9pUCvW+AXieJpvLlvOtc/8Xfn4BptQFk/oKgVsBzQOeWA1jN2 7s8gfUudXs4k7i48hv7os8f230G0jbaYTglpKYRHqV0kq6Wyy5u06GI3HvMWeAzk/lxpFH 3KkLDKxr5OZvmlP0gztSiJbYKF2y+qxSvtiRIyyN005sIBJHKXgtIbBa3q11YbKpIB/uR3 kcX+UxdIG+t9zjs4SW5PRxJhARCI6PyBNLpWAry+61h/YWPl2oHcCIKtkVye4A== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N Pete Wright writes: > hey there - > i am having an issue running chrome on an i915 intel system under > current after upgrading my vulkan packages to v1.2.190. Upgrading from which version? v1.2.189 or earlier one? Besides, Chromium 92 doesn't enable Vulkan renderer by default. > $ vulkaninfo > ERROR at > /wrkdirs/usr/ports/graphics/vulkan-tools/work/Vulkan-Tools-1.2.190/vulkaninfo/vulkaninfo.h:248:vkGetPhysicalDeviceSurfacePresentModesKHR > failed with ERROR_UNKNOWN Did you try to reboot? Sometimes GPU is wedged without triggering GPU reset. Does vulkaninfo and vkcube-display work fine on KMS console (e.g., ttyv0)? > this was working before i upgraded to latest packages (which vulkan > 1.2.190 were part of), curious if others are seeing similar behavior, > or if there is some additional debugging i can do on my end? I can't reproduce on Skylake with i915kms from drm-current-kmod with either mesa-dri or mesa-devel. Tested with chromium-92.0.4515.159_1 after enabling Vulkan in about://flags and confirming Vulkan is used by adjusting environ(7) with VK_INSTANCE_LAYERS=VK_LAYER_MESA_overlay. Can you reproduce after downgrading just vulkan-headers + vulkan-loader? vulkan-loader alone v1.2.189 -> v1.2.190 only had one functional change https://github.com/KhronosGroup/Vulkan-Loader/commit/5661252091f2 while the rest are in tests which aren't hooked in ports/ yet. For debugging the following may provide some clues: $ vidcontrol -s 1 /tmp/vulkainfo.drm-debug.log