public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Thorsten Leemhuis (regressions address)"
	<regressions@leemhuis.info>
Subject: Re: [Intel-gfx] alderlake crashes (random memory corruption?) with 6.0 i915 / ucode related
Date: Mon, 17 Oct 2022 11:30:45 +0300	[thread overview]
Message-ID: <87a65usvgq.fsf@intel.com> (raw)
In-Reply-To: <355dde1c-91e3-13b5-c8e8-75c9b9779b4f@redhat.com>

On Thu, 13 Oct 2022, Hans de Goede <hdegoede@redhat.com> 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?

BR,
Jani.


-- 
Jani Nikula, Intel Open Source Graphics Center

  parent reply	other threads:[~2022-10-17  8:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-13 20:33 alderlake crashes (random memory corruption?) with 6.0 i915 / ucode related Hans de Goede
2022-10-15 14:25 ` Hans de Goede
2022-10-17  8:17   ` [Intel-gfx] " Tvrtko Ursulin
2022-10-17  8:30 ` Jani Nikula [this message]
2022-10-17  8:32   ` Hans de Goede
2022-10-17  8:39   ` Jani Nikula
2022-10-17 10:48     ` Hans de Goede
2022-10-17 11:19       ` Thorsten Leemhuis
2022-10-17 13:14         ` Hans de Goede
2022-10-17 13:35           ` Jani Nikula
2022-10-17 14:32             ` Hans de Goede
2022-10-18 10:32               ` Ville Syrjälä
2022-10-17 11:40       ` Jani Nikula

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=87a65usvgq.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=hdegoede@redhat.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@leemhuis.info \
    /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