From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 67507C4332F for ; Mon, 17 Oct 2022 08:39:29 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230119AbiJQIj1 (ORCPT ); Mon, 17 Oct 2022 04:39:27 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53562 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230057AbiJQIjZ (ORCPT ); Mon, 17 Oct 2022 04:39:25 -0400 Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 35412313 for ; Mon, 17 Oct 2022 01:39:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1665995961; x=1697531961; h=from:to:subject:in-reply-to:references:date:message-id: mime-version; bh=uoiZlUOykZD9BywQS8wXNJeQY6o145UYMfFjg+AoJFk=; b=O3Sij6CIiN9QGIy4nH0JeARN6NRN/6606HEWYSbkSCX61blO8hqCxvca SkLQ331S6SRB4KKl3nxWJaWbt1KxkKnRmTUketINs4CKir6Zoh4+Vz/4K 7DwBzX0AStsFvQVeu2wG6TrUbg4h4s+DKTEScmIXNXXi+SgC4R5Y1rNTy yIBrlYVutBYPy79b5QDS0LmCS+7PdjleQf2F7er/8iYfusMPQKktIAkeZ fI7nvuR3wpZtDqHz+hElbvgrFovBI0Hkrauzb9sIvWRmWPJ12586d9Z/w Ju3N5CTJITpu+Du2okkmm8NHM7GiVbEUnUh7wUFWG7O0gQ7CoNnDsz8ts Q==; X-IronPort-AV: E=McAfee;i="6500,9779,10502"; a="307400181" X-IronPort-AV: E=Sophos;i="5.95,191,1661842800"; d="scan'208";a="307400181" Received: from orsmga006.jf.intel.com ([10.7.209.51]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 17 Oct 2022 01:39:20 -0700 X-IronPort-AV: E=McAfee;i="6500,9779,10502"; a="606047281" X-IronPort-AV: E=Sophos;i="5.95,191,1661842800"; d="scan'208";a="606047281" Received: from cgarnier-mobl1.ger.corp.intel.com (HELO localhost) ([10.252.44.27]) by orsmga006-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 17 Oct 2022 01:39:18 -0700 From: Jani Nikula To: Hans de Goede , intel-gfx , Linux Kernel Mailing List , "Thorsten Leemhuis (regressions address)" Subject: Re: [Intel-gfx] alderlake crashes (random memory corruption?) with 6.0 i915 / ucode related In-Reply-To: <87a65usvgq.fsf@intel.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo References: <355dde1c-91e3-13b5-c8e8-75c9b9779b4f@redhat.com> <87a65usvgq.fsf@intel.com> Date: Mon, 17 Oct 2022 11:39:57 +0300 Message-ID: <877d0ysv1e.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 17 Oct 2022, Jani Nikula wrote: > On Thu, 13 Oct 2022, Hans de Goede wrote: >> With 6.0 the following WARN triggers: >> drivers/gpu/drm/i915/display/intel_bios.c:477: >> >> drm_WARN(&i915->drm, min_size == 0, >> "Block %d min_size is zero\n", section_id); > > What's the value of section_id that gets printed? I'm guessing this is [1] fixed by commit d3a7051841f0 ("drm/i915/bios: Use hardcoded fp_timing size for generating LFP data pointers") in v6.1-rc1. I don't think this is the root cause for your issues, but I wonder if you could try v6.1-rc1 or drm-tip and see if we've fixed the other stuff already too? BR, Jani. [1] https://gitlab.freedesktop.org/drm/intel/-/issues/6592 -- Jani Nikula, Intel Open Source Graphics Center