All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH v2] drm/i915: Fix invalid access to ACPI _DSM objects
Date: Thu, 8 Apr 2021 19:56:06 +0300	[thread overview]
Message-ID: <YG81picGSzpb84fU@intel.com> (raw)
In-Reply-To: <s5h1rbk7n29.wl-tiwai@suse.de>

On Thu, Apr 08, 2021 at 06:34:06PM +0200, Takashi Iwai wrote:
> On Thu, 08 Apr 2021 09:51:18 +0200,
> Takashi Iwai wrote:
> > 
> > On Wed, 07 Apr 2021 23:28:48 +0200,
> > Ville Syrjälä wrote:
> > > 
> > > Oh, could you ask the bug reporter to attach an acpidump to the
> > > bug? Might be good to have that stuff on record somewhere if/when
> > > someone wants to actually figure out what's going on here.
> > 
> > OK, I'll ask.
> 
> Available at
>   acpidump: https://susepaste.org/59777448
>   hwinfo: https://susepaste.org/86284020

Those will apparently expire real soon. I took local copies out
of morbid curiosity, but that's not going to help anyone else 
in the future. I rather wish bug reporting tools would flat out
refuse to accept any pastebin links.

-- 
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH v2] drm/i915: Fix invalid access to ACPI _DSM objects
Date: Thu, 8 Apr 2021 19:56:06 +0300	[thread overview]
Message-ID: <YG81picGSzpb84fU@intel.com> (raw)
In-Reply-To: <s5h1rbk7n29.wl-tiwai@suse.de>

On Thu, Apr 08, 2021 at 06:34:06PM +0200, Takashi Iwai wrote:
> On Thu, 08 Apr 2021 09:51:18 +0200,
> Takashi Iwai wrote:
> > 
> > On Wed, 07 Apr 2021 23:28:48 +0200,
> > Ville Syrjälä wrote:
> > > 
> > > Oh, could you ask the bug reporter to attach an acpidump to the
> > > bug? Might be good to have that stuff on record somewhere if/when
> > > someone wants to actually figure out what's going on here.
> > 
> > OK, I'll ask.
> 
> Available at
>   acpidump: https://susepaste.org/59777448
>   hwinfo: https://susepaste.org/86284020

Those will apparently expire real soon. I took local copies out
of morbid curiosity, but that's not going to help anyone else 
in the future. I rather wish bug reporting tools would flat out
refuse to accept any pastebin links.

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2021-04-08 16:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-02  8:23 [Intel-gfx] [PATCH v2] drm/i915: Fix invalid access to ACPI _DSM objects Takashi Iwai
2021-04-02  8:23 ` Takashi Iwai
2021-04-02  8:39 ` [Intel-gfx] ✗ Fi.CI.DOCS: warning for drm/i915: Fix invalid access to ACPI _DSM objects (rev2) Patchwork
2021-04-02  9:05 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-04-02 10:27 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-04-07 16:34 ` [Intel-gfx] [PATCH v2] drm/i915: Fix invalid access to ACPI _DSM objects Ville Syrjälä
2021-04-07 16:34   ` Ville Syrjälä
2021-04-07 16:56   ` Takashi Iwai
2021-04-07 16:56     ` Takashi Iwai
2021-04-07 21:28     ` Ville Syrjälä
2021-04-07 21:28       ` Ville Syrjälä
2021-04-08  7:51       ` Takashi Iwai
2021-04-08  7:51         ` Takashi Iwai
2021-04-08 16:34         ` Takashi Iwai
2021-04-08 16:34           ` Takashi Iwai
2021-04-08 16:56           ` Ville Syrjälä [this message]
2021-04-08 16:56             ` Ville Syrjälä
2021-04-08 17:29             ` Takashi Iwai
2021-04-08 17:29               ` Takashi Iwai

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=YG81picGSzpb84fU@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tiwai@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.