From nobody Sat Dec 31 17:57:51 2022 X-Original-To: freebsd-current@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 4Nkqbz3BTrz2kwqm for ; Sat, 31 Dec 2022 17:58:07 +0000 (UTC) (envelope-from obiwac@gmail.com) Received: from mail-ej1-x630.google.com (mail-ej1-x630.google.com [IPv6:2a00:1450:4864:20::630]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Nkqby50dcz3Nms; Sat, 31 Dec 2022 17:58:06 +0000 (UTC) (envelope-from obiwac@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=MMhRDvjK; spf=pass (mx1.freebsd.org: domain of obiwac@gmail.com designates 2a00:1450:4864:20::630 as permitted sender) smtp.mailfrom=obiwac@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-ej1-x630.google.com with SMTP id ud5so58231408ejc.4; Sat, 31 Dec 2022 09:58:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=e8goITse2Ja0Y1uZZmPuSwjIw93UXnfLW3Q04smbW8k=; b=MMhRDvjKjflxdEgV6mWkiIgcX5b1hBy5Q3fEqTJNhHBZbrS7Eow9Dm4F9xxlas6zHe x2BdF6JKOQ9BTVa9A+2pcAfmzF0SzVH5SftCoz2UzMW2oSPI3idWz/wHRZDgAOmk6tqC L89LyAlKvOXi9zpXjcz8QyAOSYhqiUj9DfrMcZuuUwMrO5foFzMvwAGEV3aTPQ/PALVg 7U6dfBwn0wN13zHq7NJJhWCAe9qBlswks0zW5OyRXrjZMKQauOlHEZ61ER/QUVMUExta th+DTOUCua+H+nNlRSfUI5MzHX0eSjxyZbKvCiJ4aRUKt+ahX/wwtg2usEXdZI3If8tb yXEg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=e8goITse2Ja0Y1uZZmPuSwjIw93UXnfLW3Q04smbW8k=; b=5R5AEuorWZ3lqC0q2XDWkJSUqQ8nyA/GXed+lOjJkF6R/OSgTUBCRXU/VXacaBilxR bV5gYijqcPQf76GPCOrLcSTSn4oaDK77dSyb6F/HiNPc3d2cosJONWZGaOp02QT8knbB 4TxmIZJxWmTLYQzrTOU21VQrkrA8OHsaYAN728wUadJbTsl685BCtnu9U2ArdAuAOGIJ yvAVRISvKKyEsI3WpY1GbhDCiNPG8egGLkj0qEO7JqL4L2TkuhR3IhHv7Z5Q7zzgTpRz QHM+7v0AjPjJJwqPALSxJygCfbDXgOkvJMEoOzdwOHGAjFZo6CX5nJ/tR3Zs8gW05lea ssuQ== X-Gm-Message-State: AFqh2krl8Xhp7bvOawJPodYrqfrZixfjdVMlV9eOjuTLdniunO+71S9e xzahE9KNa9In/NCOyl09fpH09uLu0UsUSHDZXtqIRCMbDWk= X-Google-Smtp-Source: AMrXdXtakdxBSW8m1KcQffjVp6gAoHBx9nAMR6ewIr4DE+O8GyJVnSshPrhaUFmmgd5YbKNbXe3Akel7UdY8BPLLc3Q= X-Received: by 2002:a17:906:9402:b0:781:fcf6:e73a with SMTP id q2-20020a170906940200b00781fcf6e73amr1940966ejx.352.1672509485054; Sat, 31 Dec 2022 09:58:05 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 From: obiwac Date: Sat, 31 Dec 2022 18:57:51 +0100 Message-ID: Subject: i915: RCS timing out when being idled To: freebsd-current@freebsd.org Cc: manu@freebsd.org Content-Type: multipart/alternative; boundary="000000000000bd7e9d05f12375cd" X-Spamd-Result: default: False [-3.98 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.98)[-0.976]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_TLS_LAST(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::630:from]; MID_RHS_MATCH_FROMTLD(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_NONE(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-Rspamd-Queue-Id: 4Nkqby50dcz3Nms X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N --000000000000bd7e9d05f12375cd Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hey, I didn't find a more appropriate mailing list to post to, so here it goes: I'm running what is essentially FreeBSD-CURRENT on an Asus C300 Chromebook (iGPU, gen 7). Building branch 5.10-lts (or HEAD on main for that matter) of drm-kmod and loading i915kms results in a wedged GPU, after a call to intel_gt_wait_for_idle fails in __engines_record_defaults in drivers/gpu/drm/i915/gt/intel_gt.c. It fails waiting for the RCS0 engine; not loading a new context to it (i.e. adding a few 'if (id =3D=3D RCS0) continue;' lines to ignore it) allows the= GPU to continue initialisation without wedging. This isn't ideal though because the RCS ends up unhappy after a bit of load and the GPU hangs (RCS engine crashes) :P I guess the issues (the wedging and the hang) could be unrelated but I have a strong suspicion they are. I've been trying to understand how the whole i915 stuff is architectured for a couple days now (Intel's vocabulary is very confusing ngl), but there are a few things I can't really wrap my head around, which leads me asking for help debugging here =F0=9F=98=84 Is there anything else I can try in terms of troubleshooting/anyone else I can contact for help? If not I wouldn't really mind attempting to understand everything through-and-through and fix the issue myself, if there was someone I could ask for a couple short explanations on bits of the driver ;) Last I checked, everything was working well with drm-tip on Linux. Kind regards and a happy new year, Aymeric =F0=9F=A5=82 --000000000000bd7e9d05f12375cd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hey,

<= div dir=3D"auto">I didn't find a more appropriate mailing list to post = to, so here it goes:

I&#= 39;m running what is essentially FreeBSD-CURRENT on an Asus C300 Chromebook= (iGPU, gen 7).

Building= branch 5.10-lts (or HEAD on main for that matter) of drm-kmod and loading = i915kms results in a wedged GPU, after a call to intel_gt_wait_for_idle fai= ls in __engines_record_defaults in drivers/gpu/drm/i915/gt/intel_gt.c.

It fails waiting for the RCS= 0 engine; not loading a new context to it (i.e. adding a few 'if (id = =3D=3D RCS0) continue;' lines to ignore it) allows the GPU to continue = initialisation without wedging. This isn't ideal though because the RCS= ends up unhappy after a bit of load and the GPU hangs (RCS engine crashes)= :P

I guess the issues (= the wedging and the hang) could be unrelated but I have a strong suspicion = they are.

I've been = trying to understand how the whole i915 stuff is architectured for a couple= days now (Intel's vocabulary is very confusing ngl), but there are a f= ew things I can't really wrap my head around, which leads me asking for= help debugging here =F0=9F=98=84

Is there anything else I can try in terms of troubleshooting/anyo= ne else I can contact for help? If not I wouldn't really mind attemptin= g to understand everything through-and-through and fix the issue myself, if= there was someone I could ask for a couple short explanations on bits of t= he driver ;)

Last I checked, everything wa= s working well with drm-tip on Linux.

Kind=C2=A0regards and a happy new year,
Ay= meric =F0=9F=A5=82
--000000000000bd7e9d05f12375cd--